Oracle Fusion Receivables Integration
Integration with Receivables lets you create and settle claims against receipts for deductions or overpayments. You must enable Channel Revenue Management in your Receivables application for this.
How to Enable the Integration
-
With roles having the required access, navigate to the Setup and Maintenance work area.
-
Offering: Financials
-
Functional Area: Receivables
-
Task: Manage Receivables System Options
-
-
Search for and select your business unit.
-
Click the Cash Processing tab.
-
Select the Enable channel revenue management integration check box.
-
Click Save.
Standardize Claim Reasons
Some customers may have their own set of reason codes for raising a dispute or short paying you. You can standardize your customer claim reasons by translating the reason for the dispute provided by your customers to a standard set of reason codes. You can create a mapping between your claim reasons and those provided by your customers, which can be used to automatically categorize the reason for the claim. This mapping can be created in the Manage Customer Trade Profiles page. This streamlines the initial classification of claims for immediate visibility into queues of work. This translation is supported in Lockbox, in the Receivables integration, in the Manual Claim UI, and in the channelCustomerClaims REST service.
Manage Transaction Types
The accounting for settlement is handled by Receivables, driven through the Channel mappings to Receivables transactions and activities. For credit memos and invoices, Receivables performs the subledger accounting based on the Receivables transactions and activities created by Channel Revenue Management settlement.
- Claim Type setup for a deduction includes a one to one mapping to a Receivables credit memo transaction type.
- Claim Type setup for an overpayment includes a one to one mapping to a Receivables invoice transaction type.
- Claim Reason setup for a deduction includes a one to one mapping to a Receivables credit memo reason.
You can manage transaction types here:
- Offering: Financials
- Functional Area: Customer Billing
- Task: Manage Transaction Types
Manage Transaction Sources
Configure the predefined transaction source, Channel Revenue Management, which is available as the transaction source for the receivables credit memo or invoices created during settlement of a claim.
-
Offering: Financials
-
Functional Area: Customer Billing
-
Task: Manage Transaction Sources
Manage Receivables Activities
The accounting for claim investigation is derived from the receivables activity associated with the claim investigation application. Configure the predefined receivables activity for the activity type Channel Claim Investigation available under Manage Receivables Activities. Add the Activity GL Account for your business unit.
-
Offering: Financials
-
Functional Area: Receivables
-
Task: Manage Receivables Activities
Date Population in Receivables upon Settlement
-
Receipt Application Date
-
Will be the same as Override Transaction Date if it's a future date and after the Receipt Date.
-
Else, if Override Transaction Date isn't set, and Claim Accounting Date is a future date and after the Receipt Date, then Receipt Application Date will be the Claim Accounting Date.
-
Else, if the Receipt Date is in the future, then Receipt Application Date will be the Receipt Date.
-
Else it will be the System Date (settlement system date).
For example, System Date = May 28
-
Override Transaction Date = 5th June, Receipt Date = 4th June
Then Receipt Application Date = 5th June
-
Override Transaction Date = 3rd June, Receipt Date = 6th June
Then Receipt Application Date = 6th June
-
Override Transaction Date =1st May, Receipt Date = 2nd May
Then Receipt Application Date = 28th May
-
-
Receipt Application Accounting Date
-
Will be the same as Claim Accounting Date, if it's a future date and after the Receipt Accounting Date.
-
Else, if the Receipt Accounting Date is in the future, then Receipt Application Accounting Date will be the Receipt Accounting Date.
-
Else it will be the System Date (settlement system date).
For example, System Date = May 28
-
Claim Accounting Date = 5th June, Receipt Accounting Date = 4th June
Then Receipt Application Accounting Date = 5th June
-
Claim Accounting Date = 3rd June, Receipt Accounting Date = 6th June
Then Receipt Application Accounting Date = 6th June
-
Claim Accounting Date =1st May, Receipt Accounting Date = 2nd May
Then Receipt Application Accounting Date = 28th May
-
Privileges for Quick Links to Receivables Transactions
You must assign these privileges to users to enable them to view the Receivables transactions directly from Channel Revenue Management.
This table contains the privileges required for a user to view the Receivables transactions directly from Channel Revenue Management.
Privilege |
Usage |
Code |
Description |
Assigned to Duty Role |
---|---|---|---|---|
View Receivables Activities Data |
DATA |
AR_VIEW_RECEIVABLES_ACTIVITIES_DATA |
View Receivables activities data. |
Channel Claims Manager |
View Receivables Credit Memo |
Function |
AR_VIEW_RECEIVABLES_CREDIT_MEMO |
View a Receivables receipt. |
Channel Claims Management Duty |
View Receivables Invoice |
Function |
AR_VIEW_RECEIVABLES_INVOICE |
View a Receivables invoice. |
Channel Claims Management Duty |
View Receivables Receipt |
Function |
AR_VIEW_RECEIVABLES_RECEIPT |
View a Receivables credit memo. |
Channel Claims Management Duty |