AP Differences Document Final

Oracle Release 12 Accounts Payable (AP)

Differences Document

PwC

Oracle R12 – Accounts Payable Differences Document 1

Contents Document Summary................................................................................................................................. 2 Configuration/Functionality Changes ...................................................................................................... 3

Additional/Changed R12 Accounts Payable Functionality.................................................................. 3 Configuration Benchmarking............................................................................................................... 6

Payables Setup.................................................................................................................................. 6 Invoice.......................................................................................................................................... 6 Payments ...................................................................................................................................... 9 Calendar ..................................................................................................................................... 15 Currency ..................................................................................................................................... 15 Options ....................................................................................................................................... 15 Categories................................................................................................................................... 34

Profile Options ....................................................................................................................................... 35 Standard Reports .................................................................................................................................... 37


Document Summary The purpose of this document is to document PwC’s understanding of the any functionality, configuration or reports in the Oracle Release 12 (R12) ERP system Accounts Payable module. The document will benchmark the functionality available in R11 (11i) against R12 to understand any changes that will have to be made to PwC Oracle Training, Practice Aids/Control Matrices and the OracleGATE tool. This document is not a comprehensive list of all configuration changes and new functionality available in R12. The items documented are those that were considered to be of relevance to PwC for Financial Audit Support and Consulting purposes. Please note that R11 installs often have been significantly tailored and that tailoring may have additional impact not noted in this document.


Configuration/Functionality Changes This section will provide a brief overview of any new or changed functionality in the module. Where possible/relevant, a process flowchart will show the typical high level process within the module. It will also identify if R12 will provide any additional functionality to the user that may be of interest from both a financial audit and consulting perspective. Additional/Changed R12 Accounts Payable Functionality Financial Impact: Accounts Receivable / Accounts Payable Netting When a trading partner is both a customer and a supplier, the organisation may choose to offset open receivables’ against open payables’ items. Netting Agreements add trading partner terms as well as deploying company controls. A selection program automatically pulls information from Oracle Receivables and Oracle Payables taking into consideration discounts, late fees, and withholding taxes prior to determining the final netting amount. A review process and trading partner approval afford further verification to support the netting event. Financing: Advances and Progressive Contract Financing Advances are generally one-time prepayments made before work on the contract begins while contract financing infuses money to the supplier as work progresses. Oracle Payables ensures that the amounts financed are recovered by automatically applying financing to subsequent invoices per the specific terms captured in the purchase order. Operational Impact: Multi-Org Access Control Multi-Org Access Control enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing them to access, process, and report on data for an unlimited number of operating units within a single applications responsibility. This increases the productivity of Shared Service Centers for users no longer have to switch applications responsibilities when processing transactions for multiple operating units at a time. Data security is still maintained using security profiles that are defined for a list of operating units and determine the data access privileges for a user. With enhanced Multi-Org Access Control feature in Oracle Payables, access to transactional data for multiple operating units is now available to users with a single responsibility. By leveraging this feature in a shared services environment, companies can achieve significant savings in operating costs without compromising data security. Users can use the Oracle Applications Multiple Organization Support feature to use multiple ledgers for one Payables installation. They can then assign a unique ledger (with its unique calendar, chart of accounts, and ledger currency) to each organization they define. When organisations assign responsibilities using function security they can limit a user to one organization's ledger. In addition to its original title, the organization name is displayed in the header of reports also. With the Multiple Organization Support feature organisations can segregate transactions by operating unit but they can still choose to share certain information, such as supplier information, between organizations so the information needs to be entered only once.


Legal Entities The new Legal Entity architecture provides the ability to model an enterprise’s legal organizational structure and define rules and attributes specific to legal entities. With adoption of the Legal Entity architecture, Oracle Payables captures transactional data within the context of legal entity owning this data, thus enabling better, more streamlined statutory compliance. In Oracle Payables, Legal Entities is visible explicitly on payables' transactions. Subledger Accounting Oracle Payables leverages Oracle Subledger Accounting to provide detailed, fully auditable accounting representations of Payables transactions. Via a flexible rules-based methodology, users can easily create and modify their accounting policies, rapidly implement changing external or regulatory requirements with a minimum of disruption, and create multiple representations of transactions to meet fiscal and management reporting needs simultaneously. See the Oracle Subledger Accounting practice aid for further details. Enhanced Invoice Approval Includes Line Level Approval With the introduction of Invoice Lines, users are able to further extend their approval policy granularity in Oracle Approvals Management for individual lines of an invoice. Notification details are targeted to the level of approval required and embedded with a view of the invoice including summary amounts, essential line information, approver sequence, and attachments. Approvers of invoices submitted without a purchase order can enter accounting details as they approve. Introduction of Invoice Lines Oracle Payables incorporates Invoice Lines into the invoice model. Adding Invoice Lines is a key architectural change, which enables Oracle Payables to better model the paper or electronic business document yet maintain key features that exist at the invoice distributions level. Merged into the current invoice transaction business flows, Invoice Lines supports the representation of the goods or services as well as tax, freight, and other charges as lines with distributions tied to each line. Additional fields record attributes such as serial numbers and item descriptions. This feature offers the ability for line level approval and matching between an invoice line and a purchase order shipment pay item, or receipt. Furthermore, it facilitates the capture and transfer of additional, pertinent information to and from Oracle Projects and Oracle Assets.


Typical Payables Process Flow


Configuration Benchmarking This section will contain details of the benchmark completed between the available functionality in R11 (11i) and R12 and will provide comment to help the reader understand any new configuration/settings (including Oracle Profile Options defined in the SA module) and whether this is relevant to PwC from an audit and/or consulting perspective. An example of how this will be laid out is included below for Payables Module Document Type Settings. Payables Setup

Invoice Payment Terms - N/A Distribution Sets - N/A Tolerances

Setting Available

Options In R11? If new for R12,

what is it? Relevant

Invoice Tolerances Template Name Text Yes N/A A/C Description Text Yes N/A A/C Type LOV No Yes

Choose either Goods or Services. Goods represent quantity based tolerances

A/C


Setting Available Options

In R11? If new for R12, what is it?

Relevant

and Services represents amount based tolerances.

% Tolerance Ordered Text Yes N/A A/C Ordered Hold Name Check Box Yes N/A A/C Max. Tolerance Ordered

Text Yes N/A A/C

Max. Tol. Ordered Hold Name

Check Box Yes N/A A/C

% Tolerance Received

Text Yes N/A A/C

Received Hold Name Check Box Yes N/A A/C Max. Tolerance Received

Text Yes N/A A/C

Max. Tol. Received Hold Name


Exchange Rate Tolerance Amount

Text Yes N/A A/C

Exchange Rate Hold Name


Shipment Tolerance Amount

Text Yes N/A A/C

Shipment Tolerance Hold Name


Total Amount Text Yes N/A A/C Total Amount Hold Name


Note: Tax Tolerances are no longer available in R12 in the Invoice Tolerance Template form.


Invoice Hold and Release Names

Setting Available



Name LOV Yes N/A A/C Description Text Yes N/A A/C Type LOV Yes N/A A/C Accounting Allowed Check Box Yes N/A A/C Manual Release Allowed Check Box Yes N/A A/C Inactive On LOV Yes N/A A/C Holds Workflow Options Initiate Workflow Check Box No Y or N to

enable workflow

C

Notify After Days Text No Days after the workflow will

notify

C

Remind After Days Text No Days after the workflow will remid the user

C

Hold Instruction Text No Days the hold instruction will remain active

C

Note: The Holds Workflow Options is the new functionality added in R12. Approval Workflow Oracle Approvals Management (AME) is a self-service Web application that enables the organisation to define business rules governing the process for approving transactions in Oracle applications that have integrated AME. Approval Process Oracle Approvals Management (AME) provides a parallel approval process. The approval parallelization shortens the time that a transaction's approval process requires. The approval


process time is reduced as AME imposes a hierarchical (tree) structure on the transaction's approver list, and enables each part of the tree at a given level to progress through its notification-approval cycle in parallel. A transaction's approval process can have two components: • List of approvers • Set of productions

Payments

Interest Rates - N/A Bank Charges - N/A Bank and Bank Branches - N/A Bank Accounts - N/A Payment Administrator


Setting Available

Options In R11? If new for R12, what is it? Relevant

Payment Setup System Security Options

XML No Set security options for encryption, masking, and credit card control.

A/C

Validations XML No View validations that can be assigned to formats or disbursement payment methods.

A/C

Create or update Oracle XML Publisher templates for payment formats or reporting formats. Many such formats are seeded in Oracle XML Publisher.

XML No Create and register format templates needed for payment processing.

C

Formats XML Yes N/A C Transmission Configurations

XML No Review transmission protocols and add parameter values to create configurations.

C

Payment Systems

XML No Define the external organizations that process funds capture and disbursement transactions.

C

Disbursement Setup Payment Method

XML Yes N/A C

Payment Method Defaulting Rules

XML No Create and maintain rules for how payment methods should default on documents to be paid.

C

Codes Bank Instruction Codes

XML No Define codes required by format specifications for instructions to the bank.

C

Delivery Channel Codes

XML No Define codes required by format specifications for delivery channel instructions.

C

Payment Reason Codes

XML No Define codes required by format specifications for payment reasons.

C

Payment Process Profiles

XML No Create profiles for payment processing. The profiles contain all the rules about how payments are created and disbursed.

C

Disbursement System Options

XML No Review and set system options used in the disbursement process.

C


Payment Setup > System Security Options

System security options enable the organisation to set security options for payment instrument encryption, masking, and credit card control. These options are used for both funds capture and funds disbursement processes. Payments uses the settings to handle security issues, such as encrypting payment instrument sensitive data, payment instrument masking, and credit card owner verification controls. Setting Up the Wallet Payments perform system key management using features from Oracle Wallet Manager. The wallet is a file, which stores the system key. The contents of the wallet file are managed by Oracle Wallet Manager. Storing the system key in the wallet file provides greater security for the encrypted payment instrument data since the system key resides outside the Payments database. The purpose of setting up the wallet in the Wallet Setup page is to: • specify the location of the wallet file • define the password for the wallet file • specify whether to generate the system key manually or let the system do it Defining the Wallet File Password To define the password for the wallet file in the Wallet Setup page, enter any string. This password is used to encrypt the wallet file. Specifying or Generating the System Key File Location In the Wallet Setup page, the organisation can provide the system key by specifying the location of the system key file or the organisation can let the system generate the system key for the organisation. In either case, the specified or generated key is put into the wallet file and encrypted with the password the organisation provides. Encrypting Payment Instruments In the System Security Options setup page, the organisation specifies whether they want to enable or disable encryption of payment instruments and whether they wish the encryption to occur immediately when new payment instruments are registered or be performed on a regularly scheduled basis for performance reasons.


Masking Payment Instruments In the System Security Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display. For example, a credit card number of XXXX8012 represents a display of the last four digits and a masking of all the rest. These settings specify masking for payment instrument numbers in the user interfaces of many applications. Verifying Credit Card Owners This option enables the organisation to require users to enter the credit card security code and/or credit card statement billing address. This information is passed to the payment system, which in turn, checks with the credit card issuer to confirm the credit card owner's security code and/or statement billing address. Setting Up Transmission Configurations A transmission configuration implements a specific transmission protocol, which allows the delivery of a transaction to a specific payment system or financial institution. Setting Available



Payment Instrument Text No Credit Card and Bank

A/C

Payment Instrument - Enabled List No The instrument is enabled (Yes

or No)

A/C

Payment Instrument - Type List No The encryption of the payment

type is Immediate or

Scheduled

A/C

Wallet File List No The wallet is a file, which stores the system key. The contents of the wallet file are managed by Oracle Wallet Manager. Storing the system key in the wallet file provides greater security for the encrypted payment instrument data since the system key resides outside the Payments database.

N/A

Payment Instrument Masking Credit Card Masking Setting List No

In the System Security

C




Relevant

Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display.

Number of Digits to Display List No In the System Security Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display.

N/A

External Bank Account Masking Setting

List No In the System Security Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display.

C

Number of Digits to Display List No In the System Security Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display.

N/A

Credit Card Verification Control Require Security Code Entry List No

This option C




Relevant

enables the organisation to require users to enter the credit card security code and/or credit card statement billing address. This information is passed to the payment system, which in turn, checks with the credit card issuer to confirm the credit card owner's security code and/or statement billing address.

Require Statement Billing Address Entry

List No This option enables the organisation to require users to enter the credit card security code and/or credit card statement billing address. This information is passed to the payment system, which in turn, checks with the credit card issuer to confirm the credit card owner's security code and/or statement billing address.

N/A


Calendar Special Calendar - Refer to Oracle R12 GL Differences Document Aging Periods

Accounting Types - Refer to Oracle R12 GL Differences Document Periods - Refer to Oracle R12 GL Differences Document Accounting Periods - Refer to Oracle R12 GL Differences Document

Currency Define - Refer to Oracle R12 GL Differences Document

Tax - Refer to Oracle R12 Tax Document

Options Financial Options

Setting Available

Options In R11? If new for R12, what is

it? Relevant

Financial Options Operating Unit LOV No

Operating Unit A/C

Accounting Future Period Text Yes N/A A/C GL Accounts - Liability LOV Yes N/A A/C GL Accounts - Prepayment LOV Yes N/A A/C GL Accounts - Future Dated Payment LOV Yes N/A A/C GL Accounts - Discount Taken LOV Yes N/A A/C PO Rate Variance Gain LOV Yes N/A A/C PO Rate Variance Loss LOV Yes N/A A/C Expense Clearing LOV Yes N/A A/C




Relevant

Miscellaneous LOV Yes N/A A/C Retainage LOV No Retainage is the act

of withholding a portion of a payment until a substantial portion or all of the work is completed. It is a common practice in project-based construction and public sector service procurement contracts and is generally used in projects with a high value or with long-term contracts. A portion of a progress payment is generally withheld by the buying organization until all work in the contract is complete and accepted. The percentage withheld is negotiated, defined in the contract, and is based on the risk factors involved. These risk factors include the performance and reliability of the supplier.

A/C


Setting Available Options In

R11? If new for R12,


Financial Options Supplier - Purchasing RFQ Only Site Check Box Yes N/A C Ship-To Location LOV Yes N/A C Bill-To Location LOV Yes N/A C Inventory Organization LOV Yes N/A C Ship Via LOV Yes N/A C FOB LOV Yes N/A C Freight Terms LOV Yes N/A C

Note: The RFQ Only Site in 11.5.10 was under "Supplier-Entry" tab under Financial Options.




Relevant

Financial Options Encumbrance User Requisition Encumbrance


Reserve at Completion Check Box Yes N/A A/C Use PO Encumbrance Check Box Yes N/A A/C



Relevant

Financial Options Tax VAT Registration - Member State

LOV Yes N/A N/A

VAT Registration Number Text Yes N/A N/A Note: The Recoverable tax options are moved to Tax Module in R12.




Relevant

Financial Options Human Resources Business Group LOV Yes N/A C Expense Reimbursement Address

List Yes N/A C

Use Approval Hierarchies Check Box Yes N/A A/C Employee Number Method LOV Yes N/A A/C Next Automatic Number Text Yes N/A C

Payable System Setup




Relevant

Payables System Setup Supplier Supplier Number Entry List Yes N/A A/C Supplier Number Type List Yes N/A A/C Next Automatic Number Text Yes N/A C Control - Invoice Match Option

List Yes N/A A/C

Hold Unmatched Invoices Check Box Yes N/A A/C Payment Invoice Currency LOV Yes N/A A/C Payment Pay Group LOV Yes N/A C Term Date Basis List Yes N/A C Pay Date Basis List Yes N/A C Payment Terms LOV Yes N/A C Always Take Discount Check Box Yes N/A A/C Create Interest Invoices Check Box Yes N/A C

Note: Refer to Supplier under Payables Options in 11.5.10


Payables Options Accounting Option



Relevant

Payables Options Operating Unit LOV No

Operating Unit A/C

Accounting Option Payment Accounting - When Payment Is Issued


Payment Accounting - When Payment Is Clears


Account for Gain/Loss - When Payment is Issued


Account for Gain/Loss - When Payment Clears


Future Dated Payment Account Source - From Payment Document

Check Box Yes N/A C

Future Dated Payment Account Source - From Supplier Site

Check Box Yes N/A C

Automatic Offset Method • None • Balancing • Account

Radio Button

Yes N/A C

Discount Method • System Account • Prorate Expense

Radio Button

No N/A C



In R11? If new for R12, Relevant what is it?

• Prorate Tax Interest

• System Account • Prorate Across

Invoices

Radio Button

Yes N/A C

Prepayment Account • From Supplier

Site • From Purchase

Order

Radio Button

Yes N/A C

Currency



Relevant

Currency Use Multiple Currencies Check Box Yes N/A A/C Require Exchange Rate Entry Check Box Yes N/A A/C Calculate User Exchange Rate


Exchange Rate Type Check Box Yes N/A A/C GL Accounts - Realized Gain LOV Yes N/A A/C GL Accounts - Realized Loss LOV Yes N/A A/C GL Accounts - Rounding LOV Yes N/A A/C


Tax Reporting



Relevant

Tax Reporting Combined Filing Program Check Box Yes N/A C Use Pay Site Tax Region Check Box Yes N/A C Income Tax Region LOV Yes N/A C


Invoice


In R11? If new for R12, what is it? Relevant

Invoice Confirm Date as Invoice Number

Check Box

Yes N/A C

Allow Online Validation

Check Box

Yes N/A C

Allow Document Category Override

Check Box

Yes N/A C

Allow Adjustments to Paid Invoices

Check Box

Yes N/A A/C

Recalculate Scheduled Payment

Check Box

Yes N/A C

Allow Remit-To Account Override

Check Box

Yes N/A C

Receipt Acceptance Days

Text Yes N/A C

GL Date Basis • Invoice

Date • System

Date • Goods

Received / Invoice Date

• Goods Received / System

Radio Button

Yes N/A A/C



In R11? If new for R12, what is it? Relevant

Date Freight Account LOV Yes N/A C Tax Tolerance - Tax Variance

Text No Tax %. For Sales, Offset, and user-defined tax types, Payables Invoice Validation verifies that within the tolerance entered here, each tax distribution amount equals the sum of the distributions that are taxable by the tax code, multiplied by the tax rate of the tax code. Payables Invoice Validation applies a Tax Variance hold to the invoice if it is not within the tolerance specified.

C

Tax Amount Range Text No Tax Amount Range. The amount of variance allowed between the actual invoice tax amount and the invoice calculated tax amount.

C

Prepayment Payment Terms

LOV Yes N/A C

Settlement Days Text Yes N/A C Tax Difference Accounts

LOV No Account used to post any tax differences to

C


Approval


Setting Available Options In

R11? If new for R12, what is it? Relevant

Approval Use Invoice Approval Workflow

Check Box No Use Invoice Approval Workflow. Enable this option if the organisation wants to use the Invoice Approval Workflow feature to automate their invoice approval process. The workflow determines if an invoice needs any individuals to approve payment of the entire invoice (document) or invoice line, and if so, automatically routes the invoice to designated approvers who then approve or reject the invoice document or line. When they enable this option, almost all invoices must be processed by the Invoice Approval Workflow.

A/C

Allow Force Approval Check Box No Allow Force Approval. Enable this option if the organisation uses the Invoice Approval Workflow Program and want to allow accounts payable processors to override the workflow and manually approve invoices or invoice lines. Use the Invoice Actions window to manually approve the invoice document or the Force Line Approval check box to manually approve the invoice line. For example, they might want to force approve an invoice if the Invoice Approval Workflow does not complete for an invoice, or if they have authority to pay an invoice without using the workflow process.

A/C

Require Validation Before Approval

Check Box No Require Validation Before Approval. If the organisation enable this option, then Invoice Approval Workflow does not select any invoice for processing unless the invoice status is validated. They might want to enable this option if they need the Invoice Validation process to create tax distributions for an invoice before approvers review it. They cannot enable this option unless they first enable the Use Invoice Approval Workflow Payables option

A/C

Require Accounting Before Approval

Check Box No Require Accounting Before Approval. If they enable this

A/C


Setting Available Options In R11?

If new for R12, what is it? Relevant

option, then Invoice Approval Workflow does not select any invoice for processing unless the invoice status is accounted. The validation process always runs before the accounting process.


Matching


In R11?

If new for R12, what is it? Relevant

Matching Allow Final Matching Check Box Yes N/A A/C Allow Distribution Level Matching


Allow Matching Account Override


Transfer PO Descriptive Flexfield Column


Good Tolerances LOV No Goods Tolerances. The tolerance template used for goods tolerances.

A/C

Services Tolerances LOV No Services Tolerances. The tolerance template used for services tolerances.

A/C


Interest



Relevant

Interest Allow Interest Invoices Check Box Yes N/A C Minimum Interest Amount Text Yes N/A C Interest Invoice Accounts - Expense

LOV Yes N/A C

Interest Invoice Accounts - Liability

LOV Yes N/A C


Expense Report



Relevant

Expense Report Default Template LOV Yes N/A C Apply Advances Check Box Yes N/A C Automatically Create Employee in Supplier

Check Box Yes N/A C

Payment Terms LOV Yes N/A C Pay Group LOV Yes N/A C Payment Priority Text Yes N/A C Hold Unmatched Expense Reports

Check Box Yes N/A C


Payment



Relevant

Payment Discount - Exclude Tax From Discount Calculation

Check Box Yes No C

Single Payment - Allow Pre-Date

Check Box Yes No A/C

Single Payment - Allow Void and Reissue

Check Box Yes No C

Single Payment - Allow Address Change

Check Box Yes No C

Enable Bank Charge Deduction from Payment

Check Box No Enable Bank Charge Deduction from Payment

C

Deduct Bank Charge from Payment

Check Box No Deduct Bank Charge from Payment

C


Withholding Tax



Relevant

Withholding Tax Use Withholding Tax Check Box Yes N/A C Allow Manual Withholding Check Box Yes N/A C Tax Group LOV Yes N/A C Apply Withholding Tax Radio

Button Yes N/A C

Include Income Tax Type on Withholding Distributions

Check Box Yes N/A C

Withholding Amount Basis - Include Discount Amount

Check Box Yes N/A C

Withholding Amount Basis - Include Tax Amount

Check Box Yes N/A C

Create Withholding Invoice Radio Button

Yes N/A C


Reports



Relevant

Reports Sort By Alternate Field Check Box Yes N/A C

User Operating Unit Preferences - N/A

Categories Category Sets - Refer to Oracle R12 Inventory Differences Document Category Codes - Refer to Oracle R12 Inventory Differences Document Default Category Sets - Refer to Oracle R12 Inventory Differences Document Category Accounts - Refer to Oracle R12 Inventory Differences Document Accounting Setups - Refer to Oracle R12 GL Differences Document & Oracle R12 Subledger Accounting Document


Profile Options New for R12

Profile Option Name Description Relevant

AP: Invoice Approval Workflow User

Identify user used for system approvals or rejections in Payables Invoice Approval Workflow

A/C

OIE:Carry Advances Forward Based on business requirements there will be a mechanism for the customer to decide whether or not an advance amount can be carried forward for subsequent use in expense reports.

C

OIE:Enable Advances Based on business requirements there will be a mechanism for the customer to decide whether User/Auditor/Both are allowed to apply the advances.

C

OIE:Enable Cost Center Enables the Cost Center field. C OIE:Enable Expense Allocation Splitting

Enables users to split allocations C

OIE:Enable Expense Allocations Enables accounting segment override at the line level C OIE:Enable Project Allocations Enables the Oracle Projects integration feature of Internet

Expenses. C

OIE:Enable Project Expenditure Organization

Enables Project Expenditure Organization C

Payments


IBY: ECAPP URL Replace the machine and port with the names of the actual machine and the actual port where the Oracle Payments ECServlet is installed.

C

IBY: Outbound Payment Payer ID

Select from the list of values displayed, the payee in Oracle Payments issuing the payment order to the bank. The organisation can set this only at the site level. They need to define this to send transactions from Oracle Payables to Oracle Payments.

C

IBY: Default Payee for BR Remittance

Select from the list of values displayed, the payee in Oracle Payments remitting the Bills Receivable. They can set this only at the site level. They need to define this to send BR remittance batch from Oracle Receivables to Oracle Payments.

C

IBY: Wallet Location Location of the Oracle Wallet. C

IBY: Wallet Password Password to open the Oracle Wallet. C

Note: A = Audit Relevant, C = Consulting Relevant


Removed in R12


OIE:Enable Line Level Accounting

Enables accounting segment override at the line level C

OIE:Enable Projects Enables the Oracle Projects integration feature of Self-Service Expenses and displays Project # and Task # fields that are enterable

C

Tax: Allow Override of Tax Recovery Rate

Allow or disallow override of assigned tax recovery rate C



Standard Reports This section defines the relevant standard reports which are available in R12 and provides comment to help the reader understand what the report will show the Oracle User and why it is relevant to our audit/consulting work. New Reports for R12

Report Name Description Relevant Stop Payments Report Use the Stop Payments Report to review all current

stop payments. Payables does not list any stop payments which were initiated, but then released, or voided at a later time. Payables sorts the report by bank, bank account, payment document, and document number. Payables subtotals the amount for each payment document and displays the cumulative total for each bank account.

A/C

Update Matured Bills Payable Status

After the organisation submits the Update Matured Bills Payable Status process, Oracle Payables prints the Matured Bills Payable Report. This report shows the bills payable that the program successfully updated. The report also shows in the Exceptions section any payments that the program selected, but did not update.

C

Bills Payable Maturity Date Report

Use this report to review the amounts and maturity dates of bills payable that have not yet matured. This can help the organisation estimate cash needs by showing the amounts of bills payable due to mature on a specific date. Note that this report uses only the payment's maturity date, and does not use information from Oracle Cash Management to identify whether the payment has actually cleared the bank. Data is grouped by maturity date for bills payable within a bank account, with subtotals for all payments in that bank account that have the same maturity date. Totals are for all payments for all accounts with the same currency and maturity date. If an exchange rate is not defined between the payment currency and the bank account currency, the subtotal for that maturity date does not include those amounts, and the report notifies of this.

C

Scheduled Payment Selection Report

The payment process request automatically initiates the Scheduled Payment Selection Report where they can see the selected scheduled payments. This report enables the organisation to: • Review invoices selected in a pay run. • Review invoice selection criteria. • Determine immediate cash requirements for the pay run. • Review credits missed to consider adding those to the pay run or dropping the associated invoices from the pay run. • Review available prepayments to consider removing applicable invoices from the pay run. • Review unselected invoices to determine how well

A/C


Report Name Description Relevant the payment process request template is selecting the right invoices and if critical invoices were not selected, whether to take action to add them to the pay run.


Date post:	12-Oct-2014
Category:	Documents
Upload:	anishokm2992
View:	104 times
Download:	4 times

AP Differences Document Final

Documents