Oracle Fusion AR Transaction Approval Setup – Step-by-Step Guide (2025)

Learn how to configure Accounts Receivable (AR) transaction approvals in Oracle Fusion Cloud. Step-by-step setup for AR invoice approval workflow with roles, rules, and sources.

 

What Is AR Transaction Approval in Oracle Fusion Cloud?

Oracle Fusion Cloud ERP now supports workflow approvals for AR transactions such as invoices and credit memos. This newly introduced feature—Receivables Transaction Review and Control—helps organizations ensure that all receivables undergo appropriate validation before being finalized or sent to customers.

 

By enabling this feature, finance teams gain:

• Improved financial control
• Stronger audit compliance
• Automated approval workflows

Let’s dive into the full step-by-step setup process to configure this powerful capability in Oracle Fusion AR.

 

Step-by-Step: Configure AR Transaction Approval Workflow in Oracle Fusion Cloud

Step 1:  Set Up Receivables Transaction Sources

Navigation: Setup and Maintenance → Manage Transaction Sources

Action: Create or edit your AR transaction source.

Key Field – Completion Action:

No Control: No approval required

Role-Based Control: Approval based on user roles

User-Based Control: Approval based on specific user assignments

External Control: Used for external approval management

 

Best Practice: Use Role-Based or User-Based Control for internal automated approvals.

 

Step 2: Define Transaction Types with Control Settings

Navigation: Setup and Maintenance → Manage Transaction Types

 Action: Assign the correct Completion Action that matches your source setting.

Remember: The combination of transaction source and type determines whether an AR transaction requires approval before completion.

 

Step 3: Configure Approval Rules via Spreadsheet (User or Role-Based)

Oracle provides a spreadsheet-based tool to define custom approval rules.

Navigation: Setup and Maintenance → Manage User-Defined Rules for Receivables

Action: Download and configure the "Receivables Transaction Approval Rules" Excel template.

 Sheets to Fill:

User-Based Control: Assign approvers per transaction amount, BU, etc.

Role-Based Control: Route approvals based on predefined roles and logic.

Once configured, upload the Excel file to activate your approval rules.

Step 4: Assign Required Security Roles and Privileges

Make sure the right users have the privileges to approve AR transactions.

Key Roles:

Approve Receivables Transaction – AR_APPROVE_RECEIVABLES_TRANSACTION_PRIV

 

Force Approve Receivables Transaction – AR_FORCE_APPROVE_RECEIVABLES_TRANSACTION_PRIV

 

Setup Batch Source – AR_SET_UP_RECEIVABLES_BATCH_SOURCE_PRIV

Assign these using the Security Console in Oracle Fusion.

 

Step 5: Use the AR Approval Process in the Billing Work Area

Once everything is configured:

•  Create an invoice or credit memo manually.
•  Submit the transaction – status changes to Pending Approval.
•  Approver Notification – Approver gets a notification or sees it in the worklist.

 Take Action – Approver can:

•  Approve the transaction
•  Request Rework
•  Add Comments

Transactions cannot be posted, printed, or sent to customers until approved.

 

Benefits of AR Transaction Approvals in Oracle Fusion

Secure & Controlled AR Process

• Ensure no unapproved transactions are processed or reported.

 Clear Audit Trail

• Maintain a detailed history of who approved what and when.

 Faster Month-End Close

• Automate validation to speed up period close without sacrificing accuracy.

 Improved Transparency

• Approvers get visibility into transaction amounts, sources, and context.

 

FAQs – AR Approval Workflow in Oracle Cloud ERP

Q1: Can I automate approval thresholds by amount or BU?

Yes. Use the approval rules spreadsheet to define dynamic conditions by BU, amount, transaction type, etc.

 

Q2: What happens if the transaction isn’t approved in time?

It remains in “Pending Approval” and is excluded from posting or customer communications.

 

Q3: Can this process be used for imported transactions?

No, it applies only to manually created invoices and credit memos.

 

The new Oracle Fusion AR Transaction Approval feature is a game-changer for finance teams aiming for compliance, automation, and control. By following the correct configuration steps above, you’ll streamline your AR process and strengthen internal governance.

 

 Oracle Fusion Receivables Prepayments: Complete Guide to Setup, Create & Apply

Managing customer advance payments efficiently is a cornerstone of robust financial operations in Oracle Fusion Cloud Applications. The Prepayments feature in Oracle Fusion Receivables (AR) offers a powerful way to handle customer deposits and advance payments, ensuring accurate financial records and streamlined cash application processes.

This comprehensive guide will walk you through everything you need to know about Oracle AR Prepayments, from essential system configurations to the step-by-step processes for creating and applying these advance payments, and critically, understanding their accounting impact. Whether you're a functional consultant, an AR specialist, or an auditor, this post will help you master customer prepayments in Oracle Cloud.

Understanding Prepayments in Oracle Fusion Receivables

In Oracle Fusion Receivables, a prepayment represents an amount received from a customer before an actual invoice is issued for goods or services. These are essentially customer advance payments or deposits. Effectively managing these ensures accurate recognition of revenue, proper liability tracking, and seamless application against future invoices.

Why are Prepayments Important?

• Cash Flow Management: Companies can secure funds upfront for future sales or services.
• Customer Commitment: Advance payments signify a customer's commitment to a future purchase.
• Compliance: Proper handling ensures compliance with revenue recognition standards, as the payment is initially recognized as a liability.
• Operational Efficiency: Streamlines the process of applying cash once the actual invoice is generated, reducing manual reconciliation.

Essential Configurations for Oracle AR Prepayments

Before creating and applying prepayments, certain configurations are essential:

1. Create Prepayment Receivables Activities

Receivables Activities define the accounting for non-invoice-related transactions, including prepayments. You need a specific activity to account for prepayment applications.

• Navigation Path: Navigate to Setup and Maintenance > Search for "Manage Receivables Activities."
• Key Fields to Configure:
  • Name: E.g., "Prepayment Application," "Customer Deposit."
  • Activity Type: Select "Prepayment."
  • GL Account: Define the liability account (e.g., Unearned Revenue or Customer Deposits) that will be credited when a prepayment is recorded. This account will be debited when the prepayment is applied to an invoice.
  • Status: Active.

2. Define Prepayment Transaction Types

Transaction types control the characteristics and accounting of your receivables transactions. For prepayments, you'll need a specific transaction type.

• Navigation Path: Navigate to Setup and Maintenance > Search for "Manage Transaction Types."
• Key Fields to Configure:
  • Name: E.g., "Prepayment Invoice," "Customer Advance."
  • Class: Select "Prepayment." This is crucial.
  • Receivables Account: This will typically be the same Unearned Revenue or Customer Deposits liability account used in the Receivables Activity.
  • Natural Application Only: Enable this if you only want to apply prepayments to transactions with the same currency.
  • Post to GL: Ensure this is enabled for accounting impact.
  • Status: Active.

3. Establish Prepayment Transaction Sources

Transaction sources specify how transactions are imported or manually entered. While not always exclusive to prepayments, you'll use an existing or create a specific source for your prepayment transactions.

• Navigation Path: Navigate to Setup and Maintenance > Search for "Manage Transaction Sources."
• Key Fields to Configure:
• Name: E.g., "AR Prepayment Manual," "AR AutoInvoice Prepayments."
• Type: "Manual" or "Import."
• Standard Transaction Type: Link to your defined Prepayment Transaction Type.
• AutoInvoice Import Template (if Type is Import): Specify if you plan to use AutoInvoice.

Step-by-Step: Creating Prepayment Invoices in Oracle Cloud

Once your configurations are complete, you can begin creating prepayment invoices for your customers.

Manual Prepayment Invoice Creation

This method is suitable for individual or low-volume customer advance payments.

1. Navigate: Go to Receivables > Billing (or Accounts Receivable > Create Transaction).
2. Select Business Unit: Choose the appropriate Business Unit.
3. Choose Transaction Type: Select the Prepayment Transaction Type you configured (e.g., "Prepayment Invoice").
4. Enter Customer Details: Provide the customer name and other relevant customer information.
5. Enter Line Item:
   • Add a line item. The line type will typically default to "Line."
   • Enter the prepayment amount.
   • The revenue account will default to the liability account defined in the Transaction Type.
6. Complete Transaction: Add any additional details as required by your business process.
7. Save and Complete: Save the transaction and then "Complete" it to make it ready for posting.

Automated Creation via AutoInvoice

a) Download and populate the AutoInvoiceImportTemplate with prepayment invoice data.

b) Generate a CSV file and upload it using the Load Interface File for Import process.

c) Run the Import Receivables Transactions Using AutoInvoice process to create the prepayment  invoices.

This approach is ideal for bulk processing of prepayments.

Applying Prepayments to Standard Invoices in receivables

Once a prepayment invoice is created, it can be applied to standard invoices to offset amounts due.

Manual Application

Navigate to Billing > Create Transaction and create the standard invoice.

a) Click on Apply Prepayments.

b) Search for the relevant prepayment invoice, enter the amount to apply, and confirm.

c) Review the application and complete the transaction.

This process reduces the outstanding balance of the standard invoice by the applied prepayment amount. 

Automated Application via AutoInvoice

Prepare the AutoInvoiceImportTemplate with both the standard invoice lines and negative prepayment lines.

Ensure that the descriptive flexfields match between the prepayment and standard invoice lines.

Upload the data and run the Import Receivables Transactions Using AutoInvoice process.

This method is efficient for applying multiple prepayments across various invoices.

Accounting Impact of Prepayments in Oracle Fusion Receivables

Understanding the accounting entries is fundamental to grasping how prepayments function in Oracle Fusion Receivables. Prepayments initially represent a liability until they are earned or applied to an invoice.

Here's a breakdown of the typical accounting impact:

1.When the Prepayment Invoice is Created (Receivable Prepayment is Debited, Unearned Revenue is Credited):

Debit: Receivables Account (from your AR Transaction Type for Prepayment)

Credit: Unearned Revenue / Customer Deposits (Liability Account from your AR Transaction Type for Prepayment)

 2.When Payment is Received for the Prepayment Invoice (Cash is Debited,       Receivable Prepayment is Credited):

Debit: Cash / Bank Clearing Account

Credit: Receivables Account (from your AR Transaction Type for Prepayment)

 3.When the Prepayment is Applied to a Standard Invoice (Unearned Revenue is     Debited, Receivables Account is Credited for the Standard Invoice):

Debit: Unearned Revenue / Customer Deposits (Liability Account from your Receivables Activity for Prepayment)

Credit: Receivables Account (for the Standard Invoice)

Key Considerations

Currency: Prepayment transactions are processed only in the ledger currency.

Invoice Lines: Each prepayment invoice can have only one line.

Application Scope: Prepayments can only be applied to invoices within the same business unit and customer account.

Accounting Impact: Prepayment accounting entries are maintained separately and do not affect revenue accounts until applied.

Prepayment in oracle fusion receivables || How to create Prepayment in receivables || Setups for prepayment in oracle