Overview of Payable Transactions in Oracle Fusion Applications

This article will discuss an overview of Payable Transactions in Oracle Fusion Applications. Before you can create Payable transactions in Oracle Fusion Applications, make sure all configurations are complete. Check out a separate article "Overview of Payables Configurations in Oracle Fusion Applications" for more information on the configurations.

Once everything is configured, you may proceed to create payables transactions in multiple approaches. There are four approaches to create a Payables Invoice:

Manual

1. Manual Invoice created from the Payables Work Area - allows you to create invoices by using an invoice work area within the application. There is a dedicated user interface where you can navigate and you can start recording your invoices by capturing header level information, line level information, and distribution level information.
2. Integrated Imaging
3. Manual Invoice created from Spreadsheets - Oracle provides functionality to upload invoices in bulk using Spreadsheets with the use of File-Based Data Import (FBDI) templates. This allows the user to be more efficient in getting their invoices in the application. Check out the video demonstration below on how to create invoices from an Excel Spreadsheet:

Self-Service

1. Matched Invoices - This involves a process where you can match the invoices against purchase orders or maybe against receipts, depending on what type of matching level you are going to use.
2. Unmatched Invoices - Invoices that are not matched to purchase orders can be routed to workflow approval rules that you configure
3. Advanced Shipment Notices (ASNs) - A document which allows you to generate invoices automatically, which will be created when supplier create an ASN for drop shipments.

Automated

1. Integrated Imaging - This will use Oracle Integrated Invoice Imaging solution to support integrated imaging of scanned invoices for paperless processing and routing. It then uses the import process to match to purchase order or receipts. If it's a PO based invoice, you can view invoice information including invoice status, installments, holds, payments, and applied prepayments against these invoices as well. You can also drill down to the original purchase order or receipt if required. And if errors are found during the process, manual intervention may be required to resolve the import errors.
2. Self-Billed - In the application we have a feature called Evaluated Receipt Settlement, also known as Pay-On-Receipt. You can use the Pay On Receipt feature to help you in automatically generating an invoice the moment you create a receipt against a purchase order. You can use the predefined jobs, schedule them, and enable your supplier for Pay On Receipt functionality. When you do that, the moment you will create a receipt against a purchase order, based on the scheduled jobs system will automatically keep on creating an invoice against those receipts which you can access from the Payables application. Apart from that, we have also got something called Return to Supplier feature, or sometimes called as Return to Vendor (RTV). This basically helps you in automatically generating a debit memo the moment you create an RTV transaction in the Purchasing application. The moment you create an RTV transaction, that becomes the base to automatically generate a debit memo in the Payables application.
3. Expense Reports - Expense reports are Invoices created from Employee Expenses that need to be reimbursed to them. It can be either done electronically through their registers bank accounts or in the form of a physically printed check. Whenever the expense reports are approved by both the manager as well as the Payables team, they become eligible for import into the Payables application. There is a job which you need to submit to export the expense reports from the Expense application into the Payables application, because from the Expense application you cannot directly process the payments. The type of invoice that is used for these expense reports is now known as Payment Requests. Whenever you will export the invoice from Expenses to the Payables application, you need to search with the invoice type as Payment Request. 
4. Customer Refunds - Similar to Expense Reports, customer refunds can be triggered whenever there are any credit balance in Receivables that require a refund. Once approved, they will flow to Payments as Payment Requests.
5. Inter-company invoices - An intercompany transaction that requires invoicing is imported to Payables for payment processing for internal suppliers

Electronic

1. Business to Business (B2B) Web Service - Used to import invoices in an electronic format via a Web Service

Check out a separate article for more information on how to create Expense reports: Creating an Expense Report in Oracle Fusion Applications or check out the below step-by-step video demonstration:

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/
Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)