Oracle Accounts Payable (AP)

Oracle Accounts Payable is part of the Oracle E-Business Suite. Oracle Payables ensures invoices are properly authorised and helps suppliers to be paid on time, avoiding late payment charges and loss of supplier goodwill. It is tightly integrated with the Oracle Purchasing and iExpenses modules and is the key module of the Procure-To-Pay (P2P) cycle.

Invoices

Invoices can be manually entered or imported from a legacy or external system using an invoice import facility. Oracle Payables supports Multi-Org and each responsibility has a profile option specifying the default operating unit. All invoices are automatically recorded against the specific operating unit.

To proceed to payment, an invoice must follow an approvals workflow which is defined and customised for each implementation.

Taxes

Distribution lines can be associated with tax codes. Tax codes are specific to an operating unit and Oracle supports Recoverable, Non-Recoverable and VAT taxes. Tax codes can be customised to meet the business and financial regulatory requirements specific to each territory.

Oracle automatically calculates the tax lines for each invoice.

Terms

Each invoice needs to have "terms". This identifies when the invoice needs to be paid (e.g. 30 days) and what kind of discounts can be applied against invoices, (e.g. 2% discount if paid within 10 days). Terms are specific to an operating unit.

Payments

Payments can be created in batches or individually by hand. Batch payments are easy to create and allow multiple invoices to be paid using the Selection, Confirm, Format, and Payment processes.

The Selection process identifies all the invoices to be processed and the Confirm process allows business operations to confirm the selected invoices are to be paid. The Format process formats the checks and the Payment process records the payments against each invoice.

Related Modules

Oracle Payables is integrated with Oracle Fixed Assets, Purchasing and iExpenses modules. Invoices can be directly created out of Purchase Orders. The iExpenses Self Service module allows employees and contingent workers to create invoices for their Travel and Subsistence expenses.

Project Team

One of the biggest P2P implementations covers 23 countries with 12 different currencies and 8 different languages. For each country rollout a typical team size, for a country with an average level of complexity, was:

• » 2 Functional - To understand the business and perform GAP analysis
• » 3 Technical - To develop and implement the customisations, perform conversions etc
• » 2 Testers - To test the customisations and solutions

Links - Oracle Payables