Oracle Release 12 Accounts Payable (AP)

Differences Document

PwC

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

Oracle R12 Accounts Payable

Differences Document

Document Summary
The purpose of this document is to document PwCs 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.

Oracle R12 Accounts Payable

Differences 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. Oracle R12 Accounts Payable 3 Differences Document

Legal Entities The new Legal Entity architecture provides the ability to model an enterprises 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.

Oracle R12 Accounts Payable

Differences Document

Typical Payables Process Flow

Oracle R12 Accounts Payable

Differences Document

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 Invoice Tolerances Template Name Text Description Text Type LOV

In R11?

If new for R12, what is it? N/A N/A Yes

Relevant

Yes Yes No

A/C A/C A/C

Choose either Goods or Services. Goods represent quantity based tolerances Oracle R12 Accounts Payable 6 Differences Document

Setting

Available Options

In R11?

If new for R12, what is it?

Relevant

and Services represents amount based tolerances.

% Tolerance Ordered Ordered Hold Name Max. Tolerance Ordered Max. Tol. Ordered Hold Name % Tolerance Received Received Hold Name Max. Tolerance Received Max. Tol. Received Hold Name Exchange Rate Tolerance Amount Exchange Rate Hold Name Shipment Tolerance Amount Shipment Tolerance Hold Name Total Amount Total Amount Hold Name Text Check Box Text Check Box Text Check Box Text Check Box Text Check Box Text Check Box Text Check Box Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A A/C A/C A/C A/C A/C A/C A/C A/C A/C A/C A/C A/C A/C A/C

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

Oracle R12 Accounts Payable

Differences Document

Invoice Hold and Release Names

Setting Name Description Type Accounting Allowed Manual Release Allowed Inactive On Holds Workflow Options Initiate Workflow

Available Options LOV Text LOV Check Box Check Box LOV Check Box

In R11? Yes Yes Yes Yes Yes Yes No

If new for R12, what is it? N/A N/A N/A N/A N/A N/A Y or N to enable workflow Days after the workflow will notify Days after the workflow will remid the user Days the hold instruction will remain active

Relevant A/C A/C A/C A/C A/C A/C C

Notify After Days

Text

No

Remind After Days

Text

No

Hold Instruction

Text

No

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 Oracle R12 Accounts Payable Differences Document 8

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

Oracle R12 Accounts Payable

Differences Document

Setting Payment Setup

Available Options XML

In R11?

If new for R12, what is it?

Relevant

System Security Options Validations

No

XML

No

Create or update Oracle XML Publisher templates for payment formats or reporting formats. Many such formats are seeded in Oracle XML Publisher. Formats Transmission Configurations Payment Systems

XML

No

Set security options for encryption, masking, and credit card control. View validations that can be assigned to formats or disbursement payment methods. Create and register format templates needed for payment processing.

A/C

A/C

XML XML

Yes No

N/A

XML

No

Review transmission protocols and add parameter values to create configurations. Define the external organizations that process funds capture and disbursement transactions.
N/A

C C

Disbursement Setup XML Payment Method XML Payment Method Defaulting Rules Codes XML Bank Instruction Codes XML Delivery Channel Codes Payment Reason Codes Payment Process Profiles
XML

Yes No

C C

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

No

No

No

XML

No

Disbursement System Options

XML

No

Define codes required by format specifications for instructions to the bank. Define codes required by format specifications for delivery channel instructions. Define codes required by format specifications for payment reasons. Create profiles for payment processing. The profiles contain all the rules about how payments are created and disbursed. Review and set system options used in the disbursement process. 10

Oracle R12 Accounts Payable

Differences Document

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. Oracle R12 Accounts Payable Differences Document 11

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 Options Text List In R11? No No If new for R12, what is it? Credit Card and Bank The instrument is enabled (Yes or No) The encryption of the payment type is Immediate or Scheduled 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. Relevant A/C A/C

Payment Instrument Payment Instrument - Enabled Payment Instrument - Type

List

No

A/C

Wallet File

List

No

N/A

Payment Instrument Masking Credit Card Masking Setting Oracle R12 Accounts Payable

List

No In the System Security

12

Differences Document

Setting

Available Options

In R11?

If new for R12, what is it? Options setup page, credit card numbers and external bank account numbers can be masked by selecting the number of digits to mask and display. 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.

Relevant

Number of Digits to Display

List

No

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.

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 Oracle R12 Accounts Payable

List

No This option

13

Differences Document

Setting

Available Options

In R11?

If new for R12, what is it? 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. 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.

Relevant

Require Statement Billing Address Entry

List

No

N/A

Oracle R12 Accounts Payable

14

Differences Document

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 Financial Options Operating Unit Accounting Future Period GL Accounts - Liability GL Accounts - Prepayment GL Accounts - Future Dated Payment GL Accounts - Discount Taken PO Rate Variance Gain PO Rate Variance Loss Expense Clearing

Available Options LOV

In R11?

If new for R12, what is it?

Relevant

No Operating Unit

A/C

Text LOV LOV LOV LOV LOV LOV LOV

Yes Yes Yes Yes Yes Yes Yes Yes

N/A N/A N/A N/A N/A N/A N/A N/A

A/C A/C A/C A/C A/C A/C A/C A/C

Oracle R12 Accounts Payable

15

Differences Document

Setting Miscellaneous Retainage

Available Options LOV LOV

In R11? Yes No

If new for R12, what is it? N/A

Relevant A/C A/C

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 longterm 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.

Oracle R12 Accounts Payable

16

Differences Document

Setting Financial Options Supplier - Purchasing RFQ Only Site Ship-To Location Bill-To Location Inventory Organization Ship Via FOB Freight Terms

Available Options

In R11?

If new for R12, what is it?

Relevant

Check Box LOV LOV LOV LOV LOV LOV

Yes Yes Yes Yes Yes Yes Yes

N/A N/A N/A N/A N/A N/A N/A

C C C C C C C

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

Oracle R12 Accounts Payable

17

Differences Document

Setting Financial Options Encumbrance User Requisition Encumbrance Reserve at Completion Use PO Encumbrance

Available Options

In R11?

If new for R12, what is it?

Relevant

Check Box Check Box Check Box

Yes Yes Yes

N/A N/A N/A

A/C A/C A/C

Setting Financial Options Tax VAT Registration - Member State VAT Registration Number

Available Options

In R11?

If new for R12, what is it?

Relevant

LOV Text

Yes Yes

N/A N/A

N/A N/A

Note: The Recoverable tax options are moved to Tax Module in R12.

Oracle R12 Accounts Payable

18

Differences Document

Setting Financial Options Human Resources Business Group Expense Reimbursement Address Use Approval Hierarchies Employee Number Method Next Automatic Number

Available Options

In R11?

If new for R12, what is it?

Relevant

LOV List Check Box LOV Text

Yes Yes Yes Yes Yes

N/A N/A N/A N/A N/A

C C A/C A/C C

Payable System Setup

Oracle R12 Accounts Payable

19

Differences Document

Setting Payables System Setup Supplier Supplier Number Entry Supplier Number Type Next Automatic Number Control - Invoice Match Option Hold Unmatched Invoices Payment Invoice Currency Payment Pay Group Term Date Basis Pay Date Basis Payment Terms Always Take Discount Create Interest Invoices

Available Options

In R11?

If new for R12, what is it?

Relevant

List List Text List Check Box LOV LOV List List LOV Check Box Check Box

Yes

Yes
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

A/C A/C C A/C A/C A/C C C C C A/C C

Note: Refer to Supplier under Payables Options in 11.5.10

Oracle R12 Accounts Payable

20

Differences Document

Payables Options Accounting Option

Setting Payables Options Operating Unit 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 Future Dated Payment Account Source - From Supplier Site Automatic Offset Method None Balancing Account Discount Method System Account Prorate Expense

Available Options LOV

In R11?

If new for R12, what is it?

Relevant

No Operating Unit

A/C

Check Box Check Box Check Box Check Box Check Box

Yes

N/A

A/C A/C A/C A/C C

Yes
Yes Yes Yes

N/A N/A N/A N/A N/A N/A

Check Box

Yes

Radio Button

Yes

Radio Button

No

N/A

Oracle R12 Accounts Payable

21

Differences Document

Setting Interest Prorate Tax

Available Options Radio Button

In R11?

If new for R12, what is it?

Relevant

Yes

N/A

System Account Prorate Across Invoices Prepayment Account From Supplier Site From Purchase Order

Radio Button

Yes

N/A

Currency

Setting Currency Use Multiple Currencies Require Exchange Rate Entry Calculate User Exchange Rate Exchange Rate Type GL Accounts - Realized Gain GL Accounts - Realized Loss GL Accounts - Rounding

Available Options Check Box Check Box Check Box Check Box LOV LOV LOV

In R11?

If new for R12, what is it? N/A N/A N/A N/A N/A N/A N/A

Relevant

Yes Yes Yes Yes Yes Yes Yes

A/C A/C A/C A/C A/C A/C A/C

Oracle R12 Accounts Payable

22

Differences Document

Tax Reporting

Setting Tax Reporting Combined Filing Program Use Pay Site Tax Region Income Tax Region

Available Options Check Box Check Box LOV

In R11?

If new for R12, what is it? N/A N/A N/A

Relevant

Yes Yes Yes

C C C

Oracle R12 Accounts Payable

23

Differences Document

Invoice

Setting Invoice Confirm Date as Invoice Number Allow Online Validation Allow Document Category Override Allow Adjustments to Paid Invoices Recalculate Scheduled Payment Allow Remit-To Account Override Receipt Acceptance Days GL Date Basis Invoice Date System Date Goods Received / Invoice Date Goods Received / System

Available Options Check Box Check Box Check Box Check Box Check Box Check Box Text Radio Button

In R11?

If new for R12, what is it?

Relevant

Yes Yes Yes Yes Yes Yes Yes Yes

N/A N/A N/A N/A N/A N/A N/A N/A

C C C A/C C C C A/C

Oracle R12 Accounts Payable

24

Differences Document

Setting Date Freight Account Tax Tolerance - Tax Variance

Available Options LOV Text

In R11?

If new for R12, what is it?

Relevant

Yes No

N/A

Tax Amount Range

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. Tax Amount Range. The amount of variance allowed between the actual invoice tax amount and the invoice calculated tax amount.
N/A N/A Account used to post any tax differences to

C C

Prepayment Payment Terms Settlement Days Tax Difference Accounts

LOV Text LOV

Yes Yes No

C C C

Oracle R12 Accounts Payable

25

Differences Document

Approval

Oracle R12 Accounts Payable

26

Differences Document

Setting Approval Use Invoice Approval Workflow

Available Options

In R11? No

If new for R12, what is it?

Relevant

Check Box

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. 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. 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 Require Accounting Before Approval. If they enable this

A/C

Allow Force Approval

Check Box

No

A/C

Require Validation Before Approval

Check Box

No

A/C

Require Accounting Before Approval

Check Box

No

A/C

Oracle R12 Accounts Payable

27

Differences Document

Setting

Available Options

In R11?

If new for R12, what is it? 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.

Relevant

Oracle R12 Accounts Payable

28

Differences Document

Matching

Setting Matching Allow Final Matching Allow Distribution Level Matching Allow Matching Account Override Transfer PO Descriptive Flexfield Column Good Tolerances Services Tolerances

Available Options Check Box Check Box Check Box Check Box LOV LOV

In R11? Yes Yes Yes Yes No No

If new for R12, what is it?

Relevant

N/A N/A N/A N/A Goods Tolerances. The tolerance template used for goods tolerances. Services Tolerances. The tolerance template used for services tolerances.

A/C A/C A/C A/C A/C A/C

Oracle R12 Accounts Payable

29

Differences Document

Interest

Setting Interest Allow Interest Invoices Minimum Interest Amount Interest Invoice Accounts Expense Interest Invoice Accounts Liability

Available Options Check Box

In R11?

If new for R12, what is it? N/A N/A N/A N/A

Relevant

Text LOV LOV

Yes Yes Yes Yes

C C C C

Oracle R12 Accounts Payable

30

Differences Document

Expense Report

Setting Expense Report Default Template Apply Advances Automatically Create Employee in Supplier Payment Terms Pay Group Payment Priority Hold Unmatched Expense Reports

Available Options LOV

In R11?

If new for R12, what is it? N/A N/A N/A N/A N/A N/A N/A

Relevant

Check Box Check Box LOV LOV Text Check Box

Yes Yes Yes Yes Yes Yes Yes

C C C C C C C

Oracle R12 Accounts Payable

31

Differences Document

Payment

Setting Payment Discount - Exclude Tax From Discount Calculation Single Payment - Allow PreDate Single Payment - Allow Void and Reissue Single Payment - Allow Address Change Enable Bank Charge Deduction from Payment

Available Options Check Box Check Box Check Box Check Box Check Box

In R11?

If new for R12, what is it? No No No No Enable Bank Charge Deduction from Payment Deduct Bank Charge from Payment

Relevant

Yes Yes Yes Yes No

C A/C C C C

Deduct Bank Charge from Payment

Check Box

No

Oracle R12 Accounts Payable

32

Differences Document

Withholding Tax

Setting Withholding Tax Use Withholding Tax Allow Manual Withholding Tax Group Apply Withholding Tax Include Income Tax Type on Withholding Distributions Withholding Amount Basis Include Discount Amount Withholding Amount Basis Include Tax Amount Create Withholding Invoice

Available Options Check Box Check Box LOV Radio Button Check Box Check Box Check Box Radio Button

In R11?

If new for R12, what is it? N/A N/A N/A N/A N/A N/A N/A N/A

Relevant

Yes Yes Yes Yes Yes Yes Yes Yes

C C C C C C C C

Oracle R12 Accounts Payable

33

Differences Document

Reports

Setting Reports Sort By Alternate Field

Available Options Check Box

In R11?

If new for R12, what is it? N/A

Relevant

Yes

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

Oracle R12 Accounts Payable

34

Differences Document

Profile Options
New for R12 Profile Option Name
AP: Invoice Approval Workflow User OIE:Carry Advances Forward

Description
Identify user used for system approvals or rejections in Payables Invoice Approval Workflow 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. Based on business requirements there will be a mechanism for the customer to decide whether User/Auditor/Both are allowed to apply the advances. Enables the Cost Center field. Enables users to split allocations Enables accounting segment override at the line level Enables the Oracle Projects integration feature of Internet Expenses. Enables Project Expenditure Organization

Relevant
A/C C

OIE:Enable Advances

OIE:Enable Cost Center OIE:Enable Expense Allocation Splitting OIE:Enable Expense Allocations OIE:Enable Project Allocations OIE:Enable Project Expenditure Organization

C C C C C

Payments Profile Option Name

IBY: ECAPP URL

Description
Replace the machine and port with the names of the actual machine and the actual port where the Oracle Payments ECServlet is installed. 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. 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. Location of the Oracle Wallet. Password to open the Oracle Wallet.

Relevant
C

IBY: Outbound Payment Payer ID

IBY: Default Payee for BR Remittance

IBY: Wallet Location IBY: Wallet Password

C C

Note: A = Audit Relevant, C = Consulting Relevant

Oracle R12 Accounts Payable

35

Differences Document

Removed in R12 Profile Option Name OIE:Enable Line Level Accounting OIE:Enable Projects Description Enables accounting segment override at the line level Relevant C

Tax: Allow Override of Tax Recovery Rate

Enables the Oracle Projects integration feature of Self- C Service Expenses and displays Project # and Task # fields that are enterable Allow or disallow override of assigned tax recovery rate C

Note: A = Audit Relevant, C = Consulting Relevant

Oracle R12 Accounts Payable

36

Differences Document

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 Stop Payments Report

Update Matured Bills Payable Status

Bills Payable Maturity Date Report

Scheduled Payment Selection Report

Description 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. 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. 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. 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 37

Relevant A/C

A/C

Oracle R12 Accounts Payable

Differences Document

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.

Note: A = Audit Relevant, C = Consulting Relevant

Oracle R12 Accounts Payable

38

Differences Document