Using Receivables Credit To Cash
Using Receivables Credit To Cash
Cloud
20A
Oracle Financials Cloud
Using Receivables Credit to Cash
20A
Part Number F24536-02
Copyright © 2011, 2020, Oracle and/or its aliates. All rights reserved.
Authors: Robert MacIsaac, Wallace Gardipe, Carol Ann Lapeyrouse, Sampriti Singharoy, Reshma Shaik, Naini Khajanchi, Vineeta Kumar
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please report
them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition
Regulation and agency-specic supplemental regulations. As such, use, duplication, disclosure, modication, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license
terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use
in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
The business names used in this documentation are ctitious, and are not intended to identify any real companies currently or previously in existence.
Oracle Financials Cloud
Using Receivables Credit to Cash
Contents
Preface i
Preface
This preface introduces information sources that can help you use the application.
Help
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the Oracle
Help Center to nd guides and videos.
Watch: This video tutorial shows you how to nd and use help.
You can also read about it instead.
Additional Resources
• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partner
community, and other users.
Conventions
The following table explains the text conventions used in this guide.
Convention Meaning
boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.
monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.
i
Oracle Financials Cloud Preface
Using Receivables Credit to Cash
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.
Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.
Contacting Oracle
ii
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Before you can complete a Receivables transaction, you must ensure that you have entered all required information.
The information required to complete a transaction diers depending on the transaction class.
When you complete a Receivables transaction, this action creates payment schedules based on the payment terms
and transaction date that you specied. If the transaction type on the transaction has Open Receivables set to Yes,
Receivables includes the transaction in the standard aging and collection process. If you later change the transaction
type to one with Open Receivables set to No, Receivables removes this transaction from the standard aging and
collection process.
1
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• The credit memo must satisfy the requirements for a standard invoice.
• You must enter at least one credit memo line and specify revenue account assignments for each line.
• You must specify a valid receivable account.
• If your credit memo is crediting tax, you must specify valid tax accounts.
• If your credit memo is crediting freight, you must specify valid freight accounts.
Note: You can't change a credit memo that you entered against an invoice or debit memo from Complete to
Incomplete if you entered another credit memo against an item after the initial credit memo. You also can't
change a credit memo that you entered against an invoice or debit memo from Incomplete to Complete if you
entered and completed another credit memo against an item after the initial credit memo.
Invoice Distributions
Invoice distributions are the default revenue account assignments for each line of the invoice. The AutoAccounting
process derives the default revenue accounts for the invoice after invoice entry. You can review or update the
distributions for an invoice in the Edit Distributions window.
The default accounting that AutoAccounting creates is considered interim accounting only. Use the Create Receivables
Accounting program to actually create accounting entries in subledger accounting. Receivables uses predened
setup in subledger accounting so that the Create Receivables Accounting program accepts the default accounts that
AutoAccounting derives without change.
If you are reviewing distributions for an invoice that uses a revenue scheduling rule, you must run Revenue Recognition
before you can review and update accounting distributions. The revenue scheduling rule recognizes revenue over
multiple general ledger periods.
One or more rows can refer to the same transaction line, depending on the distributions. You can change the
transaction account assigned to each distribution, but you can't create new lines or delete existing lines. If you change
a row that has already posted to general ledger, Receivables doesn't alter the posted entry, but instead creates
adjustments through additional accounting entries.
The default percent amount of each invoice line assigned to a transaction account is 100 percent, unless
AutoAccounting is based on salesperson and the salesperson assignment is split. In this case, the eld reects the split
and you can either accept this percentage or enter another one.
Related Topics
• Example of Deriving Accounting Flexeld Segments in AutoAccounting
2
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Refer to these guidelines for entering and updating invoice line information:
• Inventory Items
• Unit Price
• Tax Inclusive Amounts
• Updates to Tax Lines
Inventory Items
If you enter an inventory item, you can enter a warehouse name to indicate the ship-from location for the item. If
AutoAccounting is based on standard lines, you can use the inventory item and warehouse name to create accounting
exeld information. For example, you use multiple inventory organizations and set up AutoAccounting to create the
revenue account based on standard lines. AutoAccounting uses the item and warehouse that you enter here to create
the product segment of your revenue account.
Unit Price
Enter the unit price for the invoice line item. You can enter a positive or a negative number. The default value for the
unit price is zero for tax and freight lines.
If you enter a memo line item, the default unit price is the unit list price dened for the memo line. You can accept this
price or enter the actual selling price. If the currency of the invoice is dierent from the ledger currency, the formula for
calculating the default unit price is (Standard Price / Currency Conversion Rate).
Related Topics
• AutoAccounting Account Types and Segment Values
• What happens if I make the transaction line inclusive of tax
• Considerations for Seing Up Tax Rates
• Example of Additional Tax Determining Factors on a Receivables Transaction Line
3
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Note: This rule type provides the most precise revenue recognition schedule. Use rules of this type
in cases where you must meet strict revenue accounting standards for partial accounting periods.
Rules of this type require a rule start and end date during invoice entry. If the invoice is imported with a rule of
this type, then both dates are required by AutoInvoice.
This rule type uses the total revenue amount for the line in conjunction with the number of days in the rule
duration period, including both start and end date, to calculate the daily revenue rate. This calculation is:
Daily Revenue Rate = Total Revenue / Number of Days (Total Rule Duration Period)
This rule type can accurately calculate the revenue for each period in the revenue recognition schedule. This
calculation is:
• The Daily Revenue Rate, Partial Periods rule type uses a daily revenue rate to accurately calculate the revenue
for partial periods only. This rule provides you with an even, prorated revenue distribution across the full
periods of the schedule.
Rules of this type also require both a start and end date to enable the calculation of the daily revenue rate.
• The Fixed Schedule rule type requires both a period type (such as weekly or monthly) and the number of
periods over which to recognize revenue. The revenue is then evenly divided across the periods.
4
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
You can update the percentage of revenue recognized in each period, but the percentage for the entire
schedule must always total 100. For example, if you dene a revenue scheduling rule with a period type of
monthly that spans four periods, and you accept the prorated revenue distribution, Receivables recognizes 25
percent of the transaction revenue in each of the four months.
If you select a period type of Specic Date for a xed schedule rule, you can set specic accounting dates
on which to recognize revenue. When you specify a date for one period, then all other periods also require a
specic accounting date.
• The Variable Schedule rule type also requires a period type, but not the number of periods. The number of
periods is calculated automatically either when you enter a transaction manually or import using AutoInvoice.
When you dene a variable schedule revenue scheduling rule, you can optionally specify what percentage of
revenue you want to recognize in the rst period. The remaining revenue is then prorated over the number of
periods that you specify when the transaction is created.
This table illustrates the various revenue recognition schedules that Receivables calculates using each of the rule types.
Accounting Period Days in Period Daily Revenue Daily Revenue Fixed Variable
Date Rate, All Rate, Partial Schedule Schedule
Periods Periods
• If the revenue scheduling rule is Daily Revenue Rate, All Periods, then Receivables calculates the daily
revenue rate ($900 / 90 days = $10) and uses the rate to calculate the revenue in each period. Receivables uses
the nal period to catch up with any rounding issues.
• If the revenue scheduling rule is Daily Revenue Rate, Partial Periods, then Receivables uses the daily revenue
rate to calculate the revenue for only the partial periods. The full periods receive equal revenue distributions.
• If the revenue scheduling rule is Fixed Schedule, then Receivables uses the rule denition and divides the
revenue equally across the number of periods specied in the rule.
• If the revenue scheduling rule is Variable Schedule, then you specify the number of periods during invoice
entry, and optionally specify the percentage of revenue to recognize in the rst period. Receivables evenly
5
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
distributes the revenue balance over the remaining periods. In this example, 20 percent of the total revenue is
recognized in the rst period out of a total of four periods.
• Conversion Date: The date that applies to the conversion rate for the foreign currency.
• Conversion Type:
◦ Corporate: Used to standardize rates for a company. This is generally a standard market rate determined
by senior nancial management for use throughout the enterprise.
◦ Spot: Used to perform conversion based on the rate on a specic date. The rate applies to the immediate
delivery of a currency.
◦ User: Used when you enter a foreign currency for a receipt and you haven't dened a daily conversion
rate for the foreign currency. If you select this conversion type, you must enter the conversion rate.
Note: If you select a conversion type of Corporate or Spot, Receivables veries that a rate exists for
the date that you enter, and you can't update the conversion rate. Receivables doesn't validate rates
for the User conversion type.
• Conversion Rate: The conversion rate to use. You can have multiple currency conversion rates for the
same date. If not, the conversion type that you entered provides the default rate. You dene your non-user
conversion rates in the Daily Rates window. If you entered a conversion type other than User, Receivables
veries that a rate exists for the conversion date that you entered.
• If the Inverse Conversion Rate eld is not displayed, the ledger currency amount is calculated as: Ledger
Currency = Foreign Currency * Rate.
• If the Inverse Conversion Rate eld is displayed, the ledger currency amount is calculated as: Ledger Currency
= Foreign Currency / Rate.
You can change the conversion type, rate date, and conversion rate of a foreign currency receipt, even after it is
transferred to general ledger.
You can't adjust the conversion rate of a foreign currency transaction on a completed invoice. You can alternatively
incomplete the invoice, adjust the conversion rate, then complete the invoice again. If you can't incomplete the
invoice, either because the invoice is paid, posted, printed, or has had a receipt applied against it, you must reverse
the transaction (delete it, credit it, or change the transaction type to one that has the Open Receivable and Post to GL
options set to No), then recreate the transaction at the new rate.
6
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Related Topics
• Guidelines for Creating Conversion Rate Types
• Examples of Using Conversion Rate Types in a Journal
Note: You can't update installments on transactions with balance forward billing payment terms.
When you update an installment due date, this recalculates the days late and due days for the installment based on the
new due date.
The amount you update on any installment must be greater than the amount already applied to the installment. For
example, if the original installment amount is $50 and the customer paid $20, you can update the row amount by $20 or
greater.
If you adjust the installment amount downwards, the adjustment can't be greater than the unpaid portion of the
installment.
7
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
To add an installment:
1. In the Review Installments window, click the plus (+) icon.
2. The new installment appears with the sequence number incremented.
3. Enter the due date and original amount for the new installment.
To delete an installment:
1. In the Review Installments window, select the installment that you want.
2. Click the delete (x) icon to delete the installment.
3. The sequence numbers of the other installments are reset after you click the Save and Close buon.
Note: You can delete any installment that doesn't have a payment against it. You can't delete the rst
installment, or installments that are paid, credited, adjusted, or in dispute.
The total of all installment amounts after any updates must equal the transaction entered amount. Any late charges or
penalties are recalculated after any installment updates.
As required by certain countries, the structured payment reference appears on all communications between suppliers
and customers related to the processing of payments against specic transactions. This includes the supplier invoices,
and all related remiances, bank transfers, and bank statements and reconciliation.
You can use the Edit and Review Transaction pages to update the structured payment reference on a transaction until
you print the transaction. After printing a transaction, which is equivalent to customer delivery, the structured payment
reference is a permanent part of the transaction and can't be updated.
Note: You can only print the structured payment reference on transactions belonging to customer accounts
with the Preferred Delivery Method set to Paper or Email. XML transaction delivery does not include the
structured payment reference.
8
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The View Transaction page is accessible from the Review Customer Account Details page and from General Ledger.
You can refer to the structured payment reference in the View Transaction page to identify the transaction for related
customer service activities.
If you intend to apply the receipt to a specic transaction, enter the transaction structured payment reference.
Note: You can update the structured payment reference on a receipt until the receipt is successfully
reconciled in Cash Management either manually or using the Automatic Reconciliation process.
• Use the structured payment reference as search criteria in the Application Reference window to search and
select transactions for receipt application.
Note: An exact match of structured payment references is not required to apply the receipt to a
particular transaction.
• If you want structured payment references copied from transactions to receipts, you must set the Number of
Receipts Rule on the automatic receipt method to One per Invoice.
• The selement le generated by Payments includes the structured payment references.
• If you are manually entering an automatic receipt, select an automatic receipt method and enter the structured
payment reference in the receipt header.
Related Topics
• Guidelines for Applying Receipts and On-Account Credit Memos
• Can I manually enter an automatic receipt
9
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Use these APIs in the PL/SQL code you write in the anonymous code block of the delivered Load Extension Aributes
for XML Transactions BIP data model. The Load Extension Aributes for XML Transactions BIP report process runs as
part of the Generate and Transfer XML Transactions process.
The extension aributes for Receivables transactions are computed and loaded into the AR_EXTENSION_ATTRIBUTES
table during XML creation and delivery, once you congure the Load Extension Aributes for XML Transactions BIP
data model to compute and load extension aributes using the API arp_util.insert_ar_extension_aributes. The API
arp_util.update_ready_for_xml_ag sets RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY to Y.
Any errors encountered during the loading of extension aributes into the AR_EXTENSION_ATTRIBUTES table appear
in the report output of the Load Extension Aributes for XML Transactions BIP process.
To add user-dened aributes to OAGIS 10.1 XML transactions, complete these steps:
1. Log in to Oracle Fusion BI Publisher Enterprise using the xml p server URL for a user with the BI Administrator
Role.
2. Navigate to the Data Models folder in the BI Publisher Enterprise Catalog.
3. Select the Load Extension Aributes for XML Transactions data model.
4. In the Diagram tab, click the gear icon and select Edit Data Set.
5. In the Edit Data Set window, complete the required elds.
6. In the SQL Query section, write your PL/SQL code to compute and load the extension aributes for your
transactions.
7. Ensure that your PL/SQL code sets RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY
to Y for transactions after the extension aributes are inserted. The API to set this is
arp_util.update_ready_for_xml_ag.
8. Save your work.
When you have nished dening your extension aributes and completed creating the Receivables transactions to
deliver in XML format, run the Generate and Transfer XML Transactions process to deliver these transactions.
API Signatures
The signatures of the APIs are available in the delivered data model for the Load Extension Aributes for XML
Transactions BIP report process.
The signature of the API arp_util.insert_ar_extension_aributes to insert user-dened aributes into the
AR_EXTENSION_ATTRIBUTES table is as follows:
10
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
In this case EXTENSION_ATTR_TBL_TYPE is a PL/SQL table of the EXTENSION_ATTRIBUTE_RECORD record type. The
denition of the EXTENSION_ATTRIBUTE_RECORD record type is as follows:
TYPE EXTENSION_ATTRIBUTE_RECORD IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.EXTN_ENTITY_ID
%type, ASSOCIATED_EXTN_ENTITY_ID1 AR_EXTENSION_ATTRIBUTES.ASSOCIATED_EXTN_ENTITY_ID1%type,
ASSOCIATED_EXTN_ENTITY_ID2 AR_EXTENSION_ATTRIBUTES.ASSOCIATED_EXTN_ENTITY_ID2%type,ENTITY_TYPE_CODE
AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%type,PROCESS_TYPE_CODE AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE
%type,ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type,ATTRIBUTE_VALUE
AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
In this case EXT_ATTR_TBL_FR_UPDATE is a PL/SQL table of the EXT_ATTR_RECORD_FR_UPDATE record type. The
denition of the EXT_ATTR_RECORD_FR_UPDATE record type is as follows:
TYPE EXT_ATTR_RECORD_FR_UPDATE IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.EXTN_ENTITY_ID
%type, ENTITY_TYPE_CODE AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%type, PROCESS_TYPE_CODE
AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE%type, ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME
%type, NEW_ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type, NEW_ATTRIBUTE_VALUE
AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
p_xml_ready_ag IN VARCHAR2,
11
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Use the Manage Failed Collaboration Messages page to review the error details of transactions with the XML
delivery status Delivery Failed.
Note: If a Receivables XML transaction remains in the Delivery In Progress status for more than two hours,
the status of the transaction is updated to Delivery Failed by the next run of the Generate and Transfer XML
Transactions process. You can reprocess XML transactions marked as Delivery Failed by the running the
Generate and Transfer XML Transactions process with the Transactions Included parameter set to Failed
Transactions.
The CBOD acknowledgment codes appear in the XML Delivery Status column in this way:
• Document Received corresponds to Success.
• Document Not Received corresponds to Error.
• Unknown Acknowledgment Code corresponds to Other.
If a customer trading partner wants to send a status code other than one of these three, you can map customer codes to
one of the three statuses using the Manage Conrmation Codes page of the Manage B2B Trading Partners task in the
Collaboration Messaging work area.
12
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
◦ Error Type displays the category of delivery error: Outbound Processing Error, Document Retrieval, or
Inbound Processing Error.
◦ Error Subtype displays the specic delivery error.
This table displays for each Error Type and Error Subtype the corrective action to use:
Outbound Processing Error Application Partner Document status is 1. Navigate to the Collaboration
Disabled Messaging Framework work area.
2. Open the Manage Customer
Account Collaboration
Conguration page and search for
the customer account.
3. Set the Association
Status to Enabled for the
PROCESS_INVOICE_OUT
document.
4. Rerun the Generate and Transfer
XML Transactions process with the
Transactions Included parameter
set to Failed Transactions.
Outbound Processing Error External Partner Document not found 1. Navigate to the Collaboration
Messaging Framework work area.
2. Open the Manage B2B Trading
Partners page and search for the
trading partner.
3. Dene the PROCESS_INVOICE_OUT
document for this trading partner.
4. Rerun the Generate and Transfer
XML Transactions process with the
Transactions Included parameter
set to Failed Transactions.
Outbound Processing Error External Partner Message not found 1. Navigate to the Collaboration
Messaging Framework work area.
2. Open the Manage B2B Trading
Partners page and search for the
trading partner.
3. Dene the
PROCESS_INVOICE_COLLAB_MSG_OUT
message for this trading partner.
13
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Outbound Processing Error Application Partner Document status is 1. Navigate to the Collaboration
Hold Messaging Framework work area.
2. Open the Manage Customer
Account Collaboration
Conguration page and search for
the customer account.
3. Set the Association
Status to Enabled for the
PROCESS_INVOICE_OUT
document.
4. Open the Manage Undelivered
Collaboration Messages page and
search for the XML transaction.
5. Reprocess the XML transaction.
Outbound Processing Error External Service Invocation Failure 1. Navigate to the Collaboration
Messaging Framework work area.
2. Open the Manage Undelivered
Collaboration Messages page and
search for the XML transaction.
3. Review the error description and x
the Web service URL, if that is the
reason for the error.
4. Reprocess the XML transaction.
Outbound Processing Error External Partner Document status is not 1. Navigate to the Collaboration
Active Messaging Framework work area.
2. Open the Manage B2B Trading
Partners page and search for the
trading partner.
3. Set the PROCESS_INVOICE_OUT
document status to Active for this
trading partner.
4. Open the Manage Undelivered
Collaboration Messages page and
search for the XML transaction.
5. Reprocess the XML transaction.
Outbound Processing Error External Partner Message status is not 1. Navigate to the Collaboration
Active Messaging Framework work area.
14
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Outbound Processing Error Application Service Invocation Failure 1. Navigate to the Collaboration
Messaging Framework work area.
2. Open the Manage Undelivered
Collaboration Messages page and
search for the XML transaction.
3. Reprocess the XML transaction.
Document Retrieval Application Partner Document not found 1. Navigate to the Collaboration
Messaging Framework work area.
2. Open the Manage Customer
Account Collaboration
Conguration page and search for
the customer account.
3. Associate the
PROCESS_INVOICE_OUT document
to the customer account.
4. Rerun the Generate and Transfer
XML Transactions process with the
Transactions Included parameter
set to Failed Transactions.
Inbound Processing Error Unidentied Message Type 1. Ensure that the type in the
BusinessObjectDocument tag of
the CBOD XML sent by the external
partner is ConrmBODType.
2. The existing document cannot be
reprocessed. The inbound CBOD
15
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Related Topics
• Reprocess Undelivered Messages
Report Output
The report prints one line for each debit item and summarizes all of the activity associated with each item in the entered
currency.
This table describes the report headings in the Billing History Report.
Transaction Balance Due The balance due after each activity against the transaction.
Activity Applied Amount The amount of each payment against the transaction.
Activity Credited Amount The amount of each credit against the transaction.
This table describes the row heading in the Billing History Report.
Total for Currency The totals for all transaction activity in the entered currency.
16
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
However, even with these seings enabled, it is still possible to have missing document numbers. For example, a
rollback of your database can cause missing document numbers. When you roll back a transaction after a document
number was assigned, the document number is removed. When you resume entering data for the transaction, a new
sequence number is assigned.
Report Parameters
Report Type
Sequence Name
Report Output
This table describes the important column headings in the Document Number Audit Report.
Status
The status of the missing document number:
• Entered: Both the Audit table and the Transaction table have an entry for this document
number.
• Not Entered: No entry for this document number exists in either the Audit table or the
Transaction table.
17
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Deleted: The Audit table contains an entry for this document number but the
Transaction table does not.
Overview
The Invoices Posted to Suspense Report provides a listing of all transactions that have revenue amounts posted to
suspense accounts.
Key Insights
The report groups and prints revenue amounts by the company or balancing segment of the accounting exeld,
postable status, and currency.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Accounting
Who uses this report? Financial Manager after a run of the Import AutoInvoice process, whenever you use a suspense
general ledger account.
When do I use this report? To review a list of transactions, where revenue amounts are posted to suspense accounts
when the imported transaction line amounts do not agree with the Price * Quantity calculated
amount.
What can I do with this report? Schedule to run following a run of the Import AutoInvoice process.
18
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
FAQ Answer
• The amount specied on a transaction line does not match the value of (Price * Quantity).
• The Create Clearing option on the transaction source is enabled.
The report groups and prints revenue amounts by the company or balancing segment of the accounting exeld,
postable status, and currency.
Run this report after importing transactions using AutoInvoice, or during your account reconciliation activities.
Report Output
This table describes important column headings in the Invoices Posted to Suspense Report.
19
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table describes important row headings in the Invoices Posted to Suspense Report.
Company The company or balancing segment of the accounting exeld for this group of transactions.
Postable The post to general ledger status for this group of transactions.
Currency The currency for this group of transactions. The report prints a new page for each currency.
Total for Class The total amount for transactions belonging to a transaction class.
Total for Currency The total amount for transactions in the designated entered currency.
Total for Postable The total accounted amount for all transactions that posted to the general ledger.
Total for Company The total accounted amount for all transactions belonging to the designated company.
20
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Overview
The Transaction Details Report lists all of the information that was entered for each of your transactions.
Key Insights
The report provides, for each transaction, complete header and line information, tax information, freight information,
sales credits, revenue accounting, account sets, and transaction exeld.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Billing
21
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
FAQ Answer
When do I use this report? When you need to see all the details related to specic transactions.
To run the report, you must select a business unit and range of transactions. You can also limit the report to
transactions belonging to a certain transaction class.
Report Output
This table describes important row headings in the Transaction Details Report.
Credit Method for Rules The method the credit memo uses to adjust the revenue accounts of an invoice that uses
invoicing and revenue scheduling rules.
Credit Method for Installments The method the credit memo uses to credit invoices with installments.
This table describes the revenue accounts column headings in the Transaction Details Report.
22
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Line Number The transaction line item number that refers to the revenue account. One transaction line item
can be distributed to many revenue accounts.
Percentage The percentage of the transaction line amounts that is associated to this revenue account.
Amount The amount of the line item distributed to this revenue account.
Accounting Flexeld The revenue account for the line item distribution.
Accounting Date The accounting period when the line item distribution will be posted to general ledger.
Posted Accounting Date The date the line item distribution has posted to general ledger, if applicable.
Revenue Scheduling Rule The revenue scheduling rule associated to the transaction line, if applicable.
This table describes the account sets column headings in the Transaction Details Report.
Line Number The transaction line number to which this account set is applied.
Percentage The percentage of the transaction line amounts that is associated with this account.
Revenue Scheduling Rule The revenue scheduling rule associated to the transaction line, if applicable.
23
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Overview
The Transaction Register lets you review customer transactions by business unit and accounting period.
Key Insights
The report includes all transactions that increase or decrease the customer outstanding balance for the specied period.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Period Close
Who uses this report? • Financial Specialist reviewing activity for the period.
• Financial Manager during period close processing.
When do I use this report? • When you need a listing of customer transactions.
24
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
FAQ Answer
Transaction Register
Use the Transaction Register to review your customer transactions by business unit and accounting period. The report
includes all transactions that increase or decrease the customer outstanding balance for the specied period.
You can optionally review transactions that update customer balances but do not post to the general ledger by seing
the Post to General Ledger Eligible parameter to No. Use this parameter option for your transactions that are
imported into Receivables from non-Oracle billing systems that post directly to the general ledger. When you import
these transactions into Receivables, the Post to GL option on the transaction types assigned to these transactions is not
enabled, because they are already accounted in the general ledger. Receivables is then used to track these transactions
for payment and collection purposes.
Run the Transaction Register according to your customer account review requirements. You can also use this report to
assist in reconciliation to the general ledger when a standalone report is needed.
Transaction Currency
Transaction Class
• Yes: Transactions eligible for posting to the general ledger. The Post to GL option on the transaction types
assigned to these transactions is enabled.
• No: Transactions that do not post to the general ledger. The Post to GL option on the transaction types
assigned to these transactions is not enabled.
Report Output
The report groups transactions by transaction class and accounting date, and provides subtotals by transaction class
and business unit.
25
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Transaction Entered Amount The amount of the transaction in the transaction currency.
Transaction Accounted Amount The accounted amount of the transaction in the ledger currency.
[Transaction Class] Total Total accounted amount for each transaction class.
[Business Unit] Total Total accounted amount for each business unit.
Related Topics
• Options for Posted and Non-Posted Activities using Transaction Types
• Guidelines for Using the Receivables to General Ledger Reconciliation Report
Revenue is recognized according to the revenue scheduling rule assigned to the invoice line. Revenue scheduling rules
determine the number of periods and percentage of total revenue to record in each accounting period.
Note: You must enter an invoicing rule if you want to assign a revenue scheduling rule to line items, or if an
item or memo line is assigned a default revenue scheduling rule.
26
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If the transaction involves more than one customer or entity, you can use the available sections to identify each party to
the transaction. The invoice identies these customers:
• Ship-to customer: The party who receives the goods or services billed on the invoice.
• Bill-to customer: The party who is billed for the goods or services.
• Sold-to customer: The party with whom the sale of the goods or services is identied. For example, similar
goods are sold to dierent outlets of the same retail organization.
• Paying customer: The party who actually pays for the goods or services. For example, a primary customer
might pay for related invoices belonging to dierent parties.
27
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Updating the default tax exemption handling value at the transaction level does not change the value on existing lines.
If the transaction already contained transaction lines when you updated the default tax exemption handling value, these
lines retain their existing tax exemption handling values.
If the Receivables system option Allow transaction deletion is enabled, then voiding an existing transaction removes
the document number.
How can I use social networking to quickly resolve a customer complaint about an
invoice?
Use the Social link on the Review Transaction: Invoice page to invite others to a conversation to address the complaint.
For example, you conrm that the customer was overcharged for a line item on the invoice. You need management
approval to make an adjustment to the invoice.
1. Click Social to open Oracle Social Network. Click the Share buon, or click Join if collaboration has already
been initiated.
2. Create a new related conversation.
The details of your exchange are recorded within the context of this particular invoice.
3. Invite the billing manager to join the conversation and mark it so as to get his or her aention.
Your manager asks you to conrm the adjustment with the salesperson.
4. Invite the salesperson to join the conversation.
Even though the salesperson does not have access to the application, he or she does have access to Oracle
Social Network Cloud Service. The salesperson joins the conversation and agrees to the adjustment.
5. From the Actions menu, select Manage Adjustments to create the adjustment that you all agreed upon.
28
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Depending on your job role and permissions, you can access social networking features for the following Receivables
activities:
• Transactions
• Standard receipts
• Adjustments
• Revenue adjustments
Related Topics
• What does social networking have to do with my job
Generate invoices for a bill plan by running the Generate Recurring Billing Data program. This program loads invoice
lines into the AutoInvoice interface tables. You then run Import AutoInvoice to group invoice lines into invoices per bill
plan and bill plan period, and import the invoices into Receivables.
Use the Manage Recurring Bill Plans page to search for and review your bill plans and to create a duplicate bill plan. Use
the Edit Recurring Bill Plan page to update an individual bill plan to reect changes to the terms of a contract.
Use the Manage Transactions and Review Transaction pages to search for and review the transactions created by a bill
plan. Use the Review Installments window to review and update unpaid installments on an invoice generated by a bill
plan, according to the changes requested by your customer.
Use the Review Recurring Bill Plan History page to review and track changes made to a bill plan or bill plan lines. This
includes changes to items and memo lines, transaction dates, and pricing.
29
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
30
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
12. In the Grouping Rule eld, select the grouping rule to use to group invoice lines into invoices.
13. Ensure that Oracle CPQ Cloud Integration is not enabled.
14. Complete the remaining seings according to your requirements, and save.
Receivables provides the predened transaction type Invoice. This transaction type appears by default on the Create
Recurring Bill Plan page. You can set up additional Invoice transaction types for use with recurring bill plans according
to your needs.
If necessary, you can inactivate a bill plan, and then reactivate it at a later time. When a bill plan is reactivated, the next
run of the Generate Recurring Billing Data process creates transactions for all applicable billing periods, including the
periods during which the bill plan was inactive.
Contract Dates
The contract dates determine the length of the entire contract reected by the bill plan. These dates should span the
creation and delivery of all transactions belonging to the contract.
The default contract start date is the system date, and the default contract end date is one year later. You can update
these dates according to the requirements of the contract. The contract end date should include the last date that a
transaction is created.
31
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If you don't use the Second Transaction D ate and Second Billing Period Start Date elds, then the remaining
transactions in the bill plan are created according to the value in the Billing Frequency eld. For example, if the rst
transaction date is January 1, and the billing frequency is Monthly, then all transactions in the bill plan are created on
the rst day of the month.
For example, a contract began on January 1 with a billing frequency of Monthly and transactions to be created the rst
of the month, but the rst transaction is to be issued on January 15. You enter a rst transaction date of January 15 to
create a transaction for the partial period of January 15-31. You then enter a second transaction date of February 1 for
the second and all subsequent transactions to be created on the rst day of the month.
The rst billing period start date is the same as the contract start date. By default, each subsequent billing period begins
according to the contract start date and the value in the Billing Frequency eld. For example, if the contract start date
is January 1 and the billing frequency is Quarter, then the second billing period start date is April 1.
If you enter a date in the Second Billing Period Start Date eld, this becomes the start date of the second billing
period. The subsequent billing periods begin according to the second billing period start date and the value in the
Billing Frequency eld.
For example, if the contract start date is January 1 and the billing frequency is Quarter, and you enter a second billing
period start date of February 1, then the rst billing period was January 1-31. The second billing period will be February 1
- April 30.
32
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Create Recurring Bill Plan page: Important seings for creating a bill plan include:
◦ Transaction Source eld: Use the predened transaction source ORA_RecurringBilling or enter an
Imported transaction source dened for use with bill plans.
◦ Transaction Type eld: Use the predened transaction type Invoice or enter an Invoice transaction type
dened for use with bill plans.
◦ Billing Frequency eld: Select the billing frequency for the bill plan. Receivables generates invoices
based on the billing frequency and the transaction and billing period dates.
◦ Bill plan dates:
• Contract date elds: Enter the start and end dates of the contract. The contract start date is
the date of the rst billing period. The contract end date indicates the end of the contract and
therefore the bill plan. You can't generate invoices after the contract end date.
• First Transaction Date eld: Enter the date of the rst transaction created by the bill plan. This
date must be within the rst billing period. Remaining transactions are generated and dated
according to this date plus billing frequency, unless you use the Second Transaction Date and
Second Billing Period Start Date elds.
• Second Transaction Date eld: If necessary, enter a date for the second and all subsequent
transactions created by the bill plan. Remaining transactions are generated and dated according to
this date plus billing frequency.
• Second Billing Period Start Date eld: If necessary, enter a date for the remaining billing periods
in the bill plan. Remaining billing periods are dated according to this date plus billing frequency.
◦ Customer tab: Enter the bill-to customer for the bill plan. If necessary, enter a dierent ship-to customer.
◦ Payment tab:
• Payment Terms eld: Enter the payment terms for the bill plan, if not already populated when you
selected the bill-to customer.
• Receipt Method eld: Enter the receipt method to use to apply receipts to invoices generated by
the bill plan.
• If the payment method is credit card or bank account transfer, complete the necessary elds for
the payment instrument.
◦ Miscellaneous tab:
• Legal Entity eld: If necessary, enter the legal entity for this bill plan.
• Generate Bill option: Ensure that the Generate Bill option is enabled.
◦ Lines section: Enter the invoice lines to appear on each invoice. You must enter at least one invoice line
to save the bill plan.
1. Create a bill plan that reects the details of the contract with your customer.
2. Run the Generate Recurring Billing Data program. The program:
a. Selects all bill plans that are active on the date of the program submission.
b. Identies bill plans eligible for invoicing based on the transaction date and billing frequency.
c. Generates invoice lines for these bill plans according to the details of each bill plan.
d. Uploads the invoice lines to the AutoInvoice lines interface table (RA_INTERFACE_LINES_ALL).
33
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
a. Groups invoice lines into invoices per customer, bill plan name, and bill plan period.
b. Groups the invoice lines that failed the AutoInvoice import process.
4. If necessary, correct the errors in the invoice lines and resubmit Import AutoInvoice.
Note: Any updates to invoice lines apply to this invoice only. AutoInvoice does not apply these
updates to the bill plan itself.
5. Run the Print Transactions program to print the bill plan invoice and send it to your customer.
Once you generate transactions for a bill plan, the aributes that you can update are restricted, and all changes are
tracked in the recurring bill plan history, except for updates to special instructions or descriptive exelds.
Note: Updates to a recurring bill plan aect future-generated transactions only. You can't use the bill plan to
modify transactions already generated by the bill plan.
If necessary, you can temporarily inactivate a bill plan, for example, to renegotiate terms of the contract or decide upon
a new end date for the contract. While the bill plan is inactive:
After you reactivate the bill plan and make any necessary updates, the next run of the Generate Recurring Billing Data
program generates all transactions that had not been generated since the bill plan was inactivated.
For example, a year-long contract began on January 1 with a billing frequency of Monthly. The rst invoice was
generated on January 1, but the bill plan was inactivated on January 20. After negotiations, the bill plan was reactivated
on March 15. The next run of the Generate Recurring Billing Data program generates invoices for February and March.
34
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Changes include inactivating the aribute, updating the start and end dates, or updating details of the aribute that
are incompatible with a bill plan. For example, the employment information of a salesperson assigned to invoice lines
might change. Or, you might change the contract end date of a bill plan beyond the end date of the transaction source
or transaction type assigned to the bill plan.
In these and similar cases, you must replace the related elds with appropriate aributes. Ensure that the new aribute
is active for the duration of the bill plan, and is otherwise compatible with the bill plan.
If necessary, you can expose the New Price and Eective From elds on an invoice line by selecting them from the
View menu: View > Columns > Line Information > New Price and Eective From.
35
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For example, the rst transaction date of a bill plan is January 1, with a billing frequency of Monthly. If you
change the price of a line item on February 10 with an eective date of February 15, the transaction generated
on March 1 will consider the new price of the line item for the entire month of February, not just February 15-28.
The Generate Recurring Billing Data process looks for active bill plans using the parameters you selected and identies
the bill plans eligible for invoicing. A bill plan is eligible for invoicing if the rst transaction date (or second transaction
date, if used) is on or after the system date and within the billing period.
For example:
• BillPlan1 was created on January 1 with a transaction date of the rst of the month and a billing frequency of
Monthly.
• BillPlan2 was created on January 1 with a transaction date of the rst of the month and a billing frequency of
Weekly.
• BillPlan3 was created on February 1 with a transaction date of the fteenth (15th) of the month and a billing
frequency of Quarterly.
• The Generate Recurring Billing Data process is scheduled to run on the 5th of every month.
• BillPlan1: Generates invoice lines for a single invoice for the month of February.
• BillPlan2: Generates invoice lines for four invoices: the nal three weeks of January and the rst week of
February.
• BillPlan3: Does not generate invoice lines.
After generating invoice lines, the process uploads the lines to the AutoInvoice lines interface table
(RA_INTERFACE_LINES_ALL).
36
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Use the AutoInvoice workbook to correct bill plan invoice line errors and resubmit the process. These factors apply to
updates to bill plan invoice lines:
• The AutoInvoice workbook only contains bill plan invoice lines that ended in error. It doesn't include invoice
lines from bill plans that remain unprocessed.
• Any updates that you make to invoice lines generated by a bill plan using the AutoInvoice workbook apply to
these transactions only and are not reected in the bill plan itself.
• Avoid updates to invoice lines that would change the necessary details of the invoice.
Once you create recurring bill plan invoices from invoice lines, you can use the Print Receivables Transactions process
to print and deliver invoices to your customers.
a. Search for transactions belonging to a bill plan using the Bill Plan Name eld in the Advanced Search
section.
b. Click a transaction number to open the Review Transaction page.
1. From the Review Transaction page, click the Show More link in the General Information section.
2. Click the Miscellaneous tab.
3. The Recurring Bill Plan Name eld identies the bill plan that generated the transaction.
The Bill Plan Period eld identies the billing period for the transaction.
If the terms of the contract with your customer change, you can update the bill plan itself to reect these changes in
future transactions.
If applicable to the renegotiated terms of the customer contract, you can also update the installments on transactions
already generated by the bill plan.
Tip: If you want to update installments on bill plan transactions, enable the Allow change to printed
transactions option in Receivables system options for the applicable business units. Updates to bill plan
transaction installments can only occur after the transactions are printed and sent to the customer.
37
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
What's the dierence between the transaction dates and the billing period dates?
The transaction dates are the dates invoices are generated for the bill plan by a run of the Generate Recurring Billing
Data program.
The program generates invoices in either of these ways, depending on whether you use the second transaction date:
If the rst invoice is for a partial period, you can enter a rst transaction start date later than the contract start
date but within the rst billing period.
38
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Manage AutoInvoice
AutoInvoice Import and External Data
You can import transaction data from Project and Distributed Order Orchestration, and from non-Oracle nancial
systems, to create transactions in Receivables using AutoInvoice.
Use the AutoInvoice le-based data import spreadsheet to import external transaction data. The transaction data you
import is temporarily stored in these AutoInvoice interface tables:
• AR_INTERFACE_CONTS_ALL
• RA_INTERFACE_LINES_ALL
• RA_INTERFACE_SALESCREDITS_ALL
• RA_INTERFACE_DISTRIBUTIONS_ALL
The AutoInvoice le-based data import spreadsheet and the Load Interface File for Import scheduled process are both
part of the External Integration Services for Oracle Cloud.
Related Topics
• Overview of External Data Integration Services for Oracle Cloud
• File Based Data Import for Oracle Financials Cloud
Standard Validations
AutoInvoice performs these standard validations on all data:
• Setup Values Dened: Ensures that the values pertaining to your setup are already dened in Receivables or in
other related applications.
• Transaction Numbering: Manages transaction numbering according to the transaction source and ensures that
the document number, if supplied, is unique within the associated document sequence type.
39
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Currency Precision: Ensures that the amount and the accounted amount have the correct precision for a given
currency, as dened in General Ledger. The precision is the number of digits after the decimal point normally
used in transactions for the given currency.
• Cross Validation: Ensures that certain column values agree with each other. These values can be within an
interface table or between multiple interface tables.
If the Receipt Handling for Credits option is not enabled, then AutoInvoice evaluates credit memos using standard
invoice validation:
• If the transaction type assigned to the invoice allows natural application only, then AutoInvoice rejects the
credit memo. You must unapply the receipt from the credited invoice and rerun AutoInvoice to successfully
import the credit memo.
• If the transaction type assigned to the invoice allows overapplication, then AutoInvoice imports the credit
memo and the invoice is overapplied until you unapply the receipt from the credited invoice.
Related Topics
• How AutoInvoice Validates Imported Transactions
40
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
After you have completed the template, upload it using the Load Interface File for Import process:
1. In the Import Process eld, select Import AutoInvoice.
2. In the Data File eld, enter the completed template.
3. The Load Interface File for Import process uploads the data to the AutoInvoice interface tables.
After you transfer your transaction data to the AutoInvoice interface tables using the AutoInvoice le-based data
import spreadsheet, the Import AutoInvoice process selects data from the interface tables and creates transactions in
Receivables. During the import process, Receivables rejects transactions with invalid information to ensure the integrity
of your data.
AutoInvoice transfers transaction data from the interface tables to these Receivables tables:
• RA_BATCHES_ALL
• RA_CUSTOMER_TRX _ALL
• RA_CUSTOMER_TRX_LINES _ALL
• RA_CUST_TRX_LINE_GL_DIST_ALL
• RA_CUST_TRX_LINE_SALESREPS_ALL
• AR_PAYMENT_SCHEDULES_ALL
• AR_RECEIVABLE_APPLICATIONS_ALL
• AR_ADJUSTMENTS_ALL
41
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• AutoAccounting: You must set up AutoAccounting, even if you only use AutoInvoice to create transactions and
pass distribution lines through the import process.
• Item Validation Organization Receivables system option: You must set this Receivables system option for
AutoInvoice to function correctly, even if you don't plan to use inventory items.
• Conversion rates: If necessary, dene the conversion rates that you need for your transactions in General
Ledger.
If a transaction uses conversion rates, AutoInvoice uses the rate on the conversion date, if one is provided.
Otherwise, AutoInvoice determines the conversion rate using the transaction date.
◦ Receipt Handling for Credits option: Enable this option if you want AutoInvoice to automatically
evaluate imported credits for receipt handling.
◦ AutoInvoice Options section: Use the seings in this section to modify details of the import process.
◦ Import Information section: Use the seings in this section to indicate how AutoInvoice validates
imported data.
• AutoInvoice grouping rule: Dene an AutoInvoice grouping rule to identify the transaction aributes that must
be identical in order to group transaction lines on the same transaction.
You can assign an AutoInvoice grouping rule to the Imported transaction source. If you don't assign a grouping
rule to the transaction source, AutoInvoice derives the grouping rule to assign to the transaction.
• AutoInvoice line ordering rule: Dene an AutoInvoice line ordering rule to organize the transaction lines
belonging to a transaction created by the grouping rule in a specic order. You assign the line ordering rule to
the AutoInvoice grouping rule that is used for the import process.
• Business Unit parameter: Use the optional Business Unit parameter of the Import AutoInvoice process to
specify which business unit to process imported transactions for. If you don't enter a value in this parameter,
then Import AutoInvoice processes all transactions in all business units that you have access to.
In the validation phase, AutoInvoice validates all line-level data in the interface tables, and validates additional data that
is not dependent upon a successful grouping. Additional data validations include, for example, validating transaction
types and validating that only one freight account exists for each freight line passed.
In the grouping phase, AutoInvoice groups the validated lines in the interface tables according to the seings of the
active AutoInvoice grouping rule and AutoInvoice line ordering rule, and validates header-level data needed for a
successful grouping.
Tip: If AutoInvoice incorrectly groups transactions, review the details of the AutoInvoice grouping rule, paying
particular aention to the mandatory and optional aributes that are included in the rule.
In the transfer phase, AutoInvoice transfers the grouped transactions to the Receivables tables and validates the
transferred data.
42
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If AutoAccounting for Freight is based on Standard Lines, then you can't import invoices with header level freight. All
freight lines in this case must be associated with a standard line in order for AutoAccounting to determine the account.
If the transaction has a line type of LINE with an inventory item of freight, AutoAccounting uses the revenue scheduling
rules for the freight account rather than the revenue account.
AutoInvoice processes both debit memos with late charge lines and credit memos that are against debit memos with
late charge lines. If LINE_TYPE = CHARGES, AutoInvoice doesn't calculate tax, freight, or sales credits on this line. If
you pass a late charges distribution in RA_INTERFACE_DISTRIBUTIONS_ALL, then the ACCOUNT_CLASS must equal
CHARGES.
In order for AutoInvoice to pass a late charge line, don't enter a value in the following columns in
RA_INTERFACE_LINES_ALL:
• INVOICING_RULE_ID
• INVOICING_RULE_NAME
• ACCOUNTING_RULE_ID
• ACCOUNTING_RULE_NAME
• ACCOUNTING_RULE_DURATION
• RULE_START_DATE
• UOM_CODE
• UOM_NAME
• AMOUNT
If you are passing a debit memo late charge line, then RA_INTERFACE_LINES.QUANTITY must equal 1. If you are
passing a credit memo against a debit memo with a late charge line, then RA_INTERFACE_LINES.QUANTITY must equal
-1 or 1.
Related Topics
• AutoInvoice Grouping Rule Aributes
• How AutoInvoice Validates Imported Transactions
• How AutoInvoice Processes Credited Amounts
43
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
You can also review and correct AutoInvoice errors by downloading the AutoInvoice Lines spreadsheet from the Billing
work area.
A workbook presents existing records for update or deletion only. You can't enter new transaction information into
a workbook. Each column in a given worksheet corresponds to the columns in the respective interface tables. Five
additional columns manage the processing of your updates:
• Changed: Tracks changes made to a given row. The upload only processes rows marked in this column.
• Flagged for Deletion: Indicates rows marked for deletion. When a row is agged for deletion, all the
corresponding lines in all the related tables are also deleted.
• Update Status: Displays the results of each update to the interface tables.
• Number: Displays the row number.
• Import Errors: Displays the import rejection reason.
You can change or delete records in the workbook and click the Save buon at any time. When you save, this updates
the corresponding records in the AutoInvoice interface tables.
44
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Tip: To save changes to a workbook without uploading them to the AutoInvoice tables, use the native Excel
Save and Save As features.
When you have nished updating a workbook, click the Save and Run AutoInvoice buon to display the parameters
for AutoInvoice submission. Once the process is successfully submied, AutoInvoice provides a concurrent request ID.
Related Topics
• AutoInvoice Data Preparation
You can import credit memos against transactions that were already paid. When importing credit memos against
paid transactions, AutoInvoice can evaluate these credits for automatic receipt handling. If an invoice transaction type
doesn't allow overapplication, and the Receipt Handling for Credits option is not enabled on the transaction source,
then AutoInvoice leaves the related credit memo in the interface tables until you unapply the receipt from the invoice.
To create an on-account credit memo, don't populate these columns in the RA_INTERFACE_LINES_ALL table:
• REFERENCE_LINE_ATTRIBUTE1-15
• REFERENCE_LINE_CONTEXT
• REFERENCE_LINE_ID
45
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
When you import credit memos against transactions, AutoInvoice validates that the seing of the Open Receivable
option on the transaction type assigned to the credit memo being imported matches the seing of the Open
Receivable option on the transaction type assigned to the transaction it is crediting. If they don't match, then
AutoInvoice rejects the credit memo.
• If you enter LIFO, AutoInvoice reverses the accounting entries beginning with the last period.
• If you enter PRORATE, AutoInvoice prorates the credit amount across all accounting periods.
• If you enter UNIT, AutoInvoice lets you credit specic quantities, starting with the period specied in the column
RA_INTERFACE_LINES_ALL.LAST_PERIOD_TO_CREDIT and working backward.
If you enter UNIT, then AutoInvoice rejects the credit memo if the credit quantity exceeds the quantity on the
target invoice line.
The credit memo accounting date must be in an Open or Future period, and must be equal to or greater than the
accounting date of the invoice it is crediting.
Credit memos against invoices without rules that are imported through AutoInvoice act in the same way as
those entered manually. If you pass the amount you want to credit, Receivables automatically creates all of the
accounting reversal entries. Receivables also automatically reverses the sales and non-revenue credits assigned to the
salespersons.
The values that you can pass to AutoInvoice for the accounting exeld are either accounting segment values
or account code combination IDs. Use the Accounting Flexeld option in the Accounting section of the Import
Information section of the transaction source assigned to transactions to set the value that you plan to use.
46
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If you pass accounting exeld code combination IDs, you must enter the code combination IDs in the
CODE_COMBINATION_ID column of the RA_INTERFACE_DISTRIBUTIONS_ALL table.
Note: If you want to use the option of AutoInvoice dynamically inserting code combinations, you must pass
segment values.
If you are using event-based revenue management to automatically defer or recognize revenue for imported
transactions, and you want to pass code combination IDs for the applicable transaction lines, then you must ensure that
the OVERRIDE_AUTO_ACCOUNTING_FLAG column of the RA_INTERFACE_LINES_ALL table is set to Yes.
After you dene AutoAccounting, AutoInvoice determines all of your distributions using the account information that
you pass for each transaction line.
If AutoAccounting for the freight account is based on Standard Lines, you can't import invoices with header level
freight. If the transaction has a line type of LINE and an inventory item of freight (FRT), AutoAccounting uses the rules
for the freight type account rather than the revenue type account.
If AutoAccounting is based on Salesperson, then you must pass rows in the RA_INTERFACE_SALESCREDITS_ALL table
for each invoice line in the RA_INTERFACE_LINES_ALL table. This is true even if the Require salesperson Receivables
system option is not enabled.
If you use AutoInvoice, you must dene the Line Transaction Flexeld. Because the Line Transaction Flexeld is unique
for each transaction line, you use the Line Transaction Flexeld to reference and link to other lines. AutoInvoice always
uses the Line Transaction Flexeld structure for both Link-to and Reference information during the import process. You
must explicitly dene the Link-to, Reference, and Invoice Transaction Flexeld structures only if this information is to be
displayed on a page that you have designed.
You can display Invoice Transaction Flexeld information in the Reference column of invoice lists of values. Use the
Reference Field Default Value eld of the Imported transaction source that you will use with the Import AutoInvoice
program to select the Invoice Transaction Flexeld segment that you want to display. For example, if you want to
47
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
reference the order number for imported invoices when using an invoice list of values, you must assign the transaction
exeld segment that holds the order number in the Reference Field Default Value eld of the transaction source
assigned to invoices. The order number then displays in the Reference column of invoice lists of values.
If necessary, you can set the transaction exeld and exeld segments as required:
1. Navigate to the Edit Descriptive Flexeld page for the exeld that you want.
2. In the Context Segment section, enable the Required option.
3. In the Context Sensitive Segments section, enable the Required option for each applicable segment.
4. Complete updates to the exeld according to your requirements and save.
The context that you specify in the INTERFACE_LINE_CONTEXT column of the RA_INTERFACE_LINES_ALL table
determines what information AutoInvoice places in the INTERFACE_LINE_ATTRIBUTE1-15 columns.
Receivables provides contexts for other Oracle Cloud applications that you use with AutoInvoice. If you import
transactions from a legacy system using the AutoInvoice le-based data import spreadsheet, you can dene a new
context for the Line Transaction Flexeld to distinguish these transactions from transactions that originated in Oracle
Cloud applications.
For example, to refer a credit memo to a specic invoice, use the REFERENCE_LINE_ATTRIBUTE1-15 and
REFERENCE_LINE_CONTEXT columns of the credit memo to enter the Line Transaction Flexeld of the invoice.
For example, you might want to import tax and freight charges that are associated with specic transaction lines. If
you want to associate a specic tax line with a specic transaction line, use the LINK_TO_LINE_ATTRIBUTE1-15 and
LINK_TO_LINE_CONTEXT columns of the tax line to enter the Line Transaction Flexeld of the invoice.
For example, if the Line Transaction Flexeld structure has four segments, and the last two segments contain line
level information, dene your Invoice Transaction Flexeld using the rst two segments only. You should also include
segments included in the Invoice Transaction Flexeld in the AutoInvoice grouping rules.
Related Topics
• AutoInvoice Grouping Rule Aributes
• Considerations for Managing Extensible Flexelds
48
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Dene Indexes
Dene non-unique, concatenated indexes on the tables and columns that you use for your Transaction Flexeld header
and line information. The tables and columns are described in this table:
Table Columns
To determine which indexes you might need to create, query your Line Transaction Flexeld and note each context
of this exeld and, for each context, the segments that are enabled using interface line aribute columns from the
RA_INTERFACE_LINES_ALL table.
You can then create non-unique, concatenated indexes for the same interface line aribute columns in the
RA_CUSTOMER_TRX_LINES_ALL and RA_INTERFACE_LINES_ALL tables, and for the same interface header aribute
columns in the RA_CUSTOMER_TRX_ALL table.
If you are importing sales credit and accounting information, then create indexes for the same interface line aribute
columns in the RA_INTERFACE_SALESCREDITS_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL tables.
For best performance, you should create indexes for these four tables:
• RA_CUSTOMER_TRX_ALL
• RA_CUSTOMER_TRX_LINES_ALL
• RA_INTERFACE_LINES_ALL
49
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• RA_INTERFACE_SALESCREDITS_ALL
The indexes that you create should reference the three enabled segments. For example, an index that you create for the
RA_CUSTOMER_TRX_LINES_ALL table might look like this:
CREATE UNIQUE INDEX index_name ON RA_CUSTOMER_TRX_LINES_ALL
(INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1,
INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3);
Note: The context column in indexes is normally optional. However, if you use multiple active contexts
(three or more), then you should include the context column as the rst column in your indexes to improve
performance.
Analysis
If you have only one context dened, then you only need to create one index for each of the four tables. However, if you
have multiple contexts dened, you may want to create multiple indexes per table. Use the example in the following
table to help you decide how to set up your indexes.
Context1 has two aribute columns; Context2 has three aribute columns; and Context3 has two aribute columns.
Context1 and Context2 share two aribute columns.
Sharing Indexes
Dene the combination of indexes that best meets your needs. As indicated in the previous section, you can create
three indexes per table, one for each context, or create just two indexes: one for Context3 and another for Context1. In
the laer case, Context2 would use the same index as Context1, because Context1 and Context2 have the same rst two
aribute columns.
50
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
In other words, if you are using the same, or similar, aribute columns for two or more contexts, then you can optionally
create a single index instead of creating an index for each context.
Note: If a transaction date is not passed for an invoice or debit memo, AutoInvoice uses the derived
accounting date as the transaction date.
51
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• AutoInvoice uses the accounting date provided in the interface table as the invoice accounting date.
• If no accounting date is provided in the interface table, then AutoInvoice uses the earliest revenue scheduling
rule start date of all of the lines belonging to the invoice as the invoice accounting date.
If the invoice uses the In Arrears invoicing rule, AutoInvoice derives an end date for each transaction line based on the
revenue scheduling rule, rule start date, and rule duration. Once AutoInvoice derives the end date for each transaction
line, it takes the latest date and uses it as the invoice accounting date.
AutoInvoice uses the following process to derive the accounting date for invoices with revenue scheduling rules:
1. If the Derive date option on the transaction source is set to No, AutoInvoice uses the value of the Default Date
parameter of the Import AutoInvoice program.
2. If no accounting date is provided in the interface table, and the Derive date option on the transaction source is
set to Yes:
a. AutoInvoice uses the last day of the prior period, if this period has a status of Open.
b. If a prior period with a status of Open doesn't exist, AutoInvoice uses the rst day of the subsequent
period that has a status of Open.
If there is more than one subsequent period with a status of Open, AutoInvoice can't adjust the
accounting date, and the line is rejected.
c. If an Open period doesn't exist, AutoInvoice uses the rst day of the rst subsequent period that has a
status of Future.
If there is more than one subsequent period with a status of Future, or if a future period can't be found,
AutoInvoice can't adjust the accounting date, and the line is rejected.
Credit Memos
If no accounting date is provided in the interface table, AutoInvoice uses either the accounting date of the related
invoice receivable distribution or the Default Date parameter of the Import AutoInvoice program as the accounting
date, whichever is later.
52
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
53
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The Receivables Invoice Service populates the AutoInvoice interface table with the number of invoice lines
necessary to satisfy the details of the recurring order.
Generate Transactions
Run the Import AutoInvoice program to create transactions according to your billing business requirements.
Related Topics
• AutoInvoice Grouping Rule Aributes
Note: Credit card services are currently not available in Oracle Cloud implementations.
The following table provides the name and description of each of these columns:
54
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Credit Card Token Number The token number issued by the tokenization service provider that corresponds to the credit
card number on the transaction. This is a required eld for tokenization import.
First Name of the Credit Card Holder The rst name of the card holder.
Last Name of the Credit Card Holder The last name of the card holder.
Credit Card Issuer Code The code that identies the credit card issuer, as dened by the IBY_ CARD_TYPES lookup.
Masked Credit Card Number The masked format of the credit card number, used where the number is displayed.
Credit Card Authorization Request If available, the authorization request identier received from the tokenization service provider
Identier to authorize the credit card number.
Credit Card Voice Authorization Code If available, the voice authorization code received from the tokenization service provider to
authorize the credit card number.
Note: The authorization code columns are used to import credit card authorization information other than
the Credit Card Token Number. Use either the Credit Card Authorization Request Identier or the Credit
Card Voice Authorization Code column. If you provide values in both columns, the Credit Card Authorization
Request Identier takes precedence.
1. Expose and complete the applicable columns in the AutoInvoice Import template.
2. Run the Load Interface File for Import process for the AutoInvoice Import template to load the transaction data
into the AutoInvoice interface tables.
3. Run the Import AutoInvoice process to load the data into Receivables and create the transactions.
4. Use the Review Transaction page to review the details of each transaction.
Related Topics
• How You Enable Credit Card Tokenization
• How You Create Receipts for Credit Card Transactions with Tokens
55
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
AutoInvoice uses Transaction Flexelds to uniquely identify each transaction that you import into Receivables.
AutoInvoice always uses the Line Transaction Flexeld structure for both the Link-to and Reference information when
importing transactions.
ACCOUNTING_RULE_DURATION
Enter the number of periods in the revenue scheduling rule for this transaction.
If LINE_TYPE = LINE or you are passing header freight, and this transaction uses a revenue scheduling rule with a
variable schedule, you must enter a value in this column.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
Validation
Accounting periods must be dened for the periods of the revenue scheduling rule in GL_PERIODS and
RA_INTERFACE_LINES_ALL.GL_DATE, and RA_INTERFACE_LINES_ALL.RULE_START_DATE must be in a period that
has a status of Open or Future. The value in this column must be a positive integer.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ACCOUNTING_RULE_DURATION
ACCOUNTING_RULE_ID
Enter the revenue scheduling rule ID for this transaction.
If LINE_TYPE = LINE or you are passing header freight, this column is optional. For invoice lines with revenue
scheduling rules, you must enter a value either in this column or in the ACCOUNTING_RULE_NAME column, depending
on the seing of the Revenue Scheduling Rule option (Value, ID, None) in the Import Information section of the
transaction source. If you enter a value in the ACCOUNTING_RULE_NAME column, AutoInvoice enters a corresponding
ID in this column.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the revenue scheduling rule of the transaction
you are crediting.
Validation
Must exist in RA_RULES.RULE_ID and RA_RULES.TYPE = A or ACC_DUR. If LINE_TYPE = CHARGES, then this column
must be null.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ACCOUNTING_RULE_ID
ACCOUNTING_RULE_NAME
Enter the revenue scheduling rule name for this transaction.
56
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = LINE or you are passing header freight, this column is optional. For invoice lines with revenue
scheduling rules, you must enter a value either in this column or in the ACCOUNTING_RULE_ID column, depending
on the seing of the Revenue Scheduling Rule option (Value, ID, None) in the Import Information section of the
transaction source.
If LINE_TYPE = TAX, CHARGES, or if you are passing freight for a specic line, do not enter a value in this column.
For credit memos do not enter a value in this column. AutoInvoice uses the revenue scheduling rule of the transaction
you are crediting.
Validation
Must exist in RA_RULES.NAME and RA_RULES.TYPE = A or ACC_DUR. If LINE_TYPE = CHARGES, then this column must
be null.
Destination
None.
ACCTD_AMOUNT
Do not enter a value. This column is not currently used.
Validation
None.
Destination
None.
AMOUNT
Enter the revenue amount for this transaction.
If LINE_TYPE = LINE and this transaction is neither a freight-only nor a tax-only line, you must enter a value in this
column. If this transaction is a dummy line for freight-only or tax-only, do not enter a value in this column. AutoInvoice
ignores any values you enter in this column if this transaction is a dummy line.
If LINE_TYPE = TAX, a value must be entered in either this column or the TAX_Rate column. Any exemptions must be
factored into either of the two columns.
If LINE_TYPE = FREIGHT and you are passing either header freight or freight for a specic line, you must enter a value
in this column.
If this line has AMOUNT_INCLUDES_TAX set to Yes, the sales credits and line amounts for this column must include tax.
For credit memos and on-account credits, enter the credit amount for this transaction.
Validation
If LINE_TYPE = CHARGES, then this column must be null. AutoInvoice corrects revenue amounts that have an incorrect
currency precision.
57
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
If the Create clearing option on the transaction source is not enabled:
RA_CUSTOMER_TRX_LINES_ALL.REVENUE_AMOUNT and RA_CUSTOMER_TRX_LINES_ALL.EXTENDED_AMOUNT. If
the Create clearing option on the transaction source is enabled: RA_CUSTOMER_TRX_LINES_ALL.REVENUE_AMOUNT.
AMOUNT_INCLUDES_TAX_FLAG
This column controls whether the amount for this transaction line includes tax. If this column is set to Yes, then this line
is assigned to a tax inclusive tax rate code.
AutoInvoice only uses this column if the tax rate code assigned to this line has the Allow Override and Entry of
Inclusive Tax Lines option enabled on the corresponding tax regime.
Populate this column for invoices only. For regular credit memos, AutoInvoice always uses the
AMOUNT_INCLUDES_TAX_FLAG column value from the invoice that you are crediting.
Validation
If this is a tax rate code and the Allow Override and Entry of Inclusive Tax Lines option is not enabled, this should be
equal to either the seing of the Amount Includes Tax option for this tax rate code or null. Additionally, if the Allow
Override and Entry of Inclusive Tax Lines option is not enabled, then the Amount Includes Tax option at the line
level must equal the Allow Override option seing for this tax rate code.
Destination
RA_CUSTOMER_TRX_LINES_ALL.AMOUNT_INCLUDES_TAX_FLAG
APPROVAL_CODE
The payment approval code provided by the credit card issuer to indicate that funds are available from the user
account.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.APPROVAL_CODE
ADDRESS_VERIFICATION_CODE
The credit card address verication code provided by the Payments Server.
Validation
None.
58
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUSTOMER_TRX_ALL.ADDRESS_VERIFICATION_CODE
ASSESSABLE_VALUE
Enter the assessable value of the item on the transaction line.
The assessable value is the price at which a product is valued by a tax authority for a given tax, for tax calculation
purposes.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL
ATTRIBUTE1-15
Enter the Invoice Line Information Flexeld aribute information for this transaction.
Descriptive Flexeld aributes allow you to store additional columns, the contents of which you dene. These columns
are optional.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ATTRIBUTE1-15. To ensure that AutoInvoice accurately groups your imported
invoices, do not include newline or carriage return characters (chr(10) or chr(13)) in Descriptive Flexeld columns.
ATTRIBUTE_CATEGORY
Enter the Invoice Line Information Flexeld category information for this transaction.
Descriptive Flexeld categories allow you to store dierent categories of aributes. This column is optional.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ATTRIBUTE_CATEGORY
59
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
BATCH_SOURCE_NAME
Enter the name of the transaction source for this transaction. AutoInvoice uses the transaction source to determine the
transaction numbering method and the AutoInvoice processing options. You must enter a value in this column.
Validation
Must exist in RA_BATCH_SOURCES_ALL.NAME and RA_BATCH_SOURCES_ALL.BATCH_SOURCE_TYPE = FOREIGN.
Destination
RA_BATCHES_ALL.BATCH_SOURCE_ID and RA_CUSTOMER_TRX_ALL.BATCH_SOURCE_ID.
COMMENTS
Enter comments about this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or your are passing freight for a specic line, do not enter text in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.COMMENTS
CONS_BILLING_NUMBER
Enter the number for this consolidated bill.
A consolidated bill number is used for grouping a set of invoices under one bill.
Validation
Must not already exist in AR_CONS_INV_ALL.CONS_BILLING_NUMBER and
AR_CONS_INV_ALL.CONS_INV_TYPE=MINV.
Destination
AR_CONS_INV_ALL.CONS_BILLING_NUMBER
CONVERSION_DATE
Enter the conversion date for this transaction. If you don't enter a date, AutoInvoice uses the transaction date as the
default. If the currency of the transaction line is the same as the ledger currency, then leave this column null.
60
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For credit memos, AutoInvoice uses the conversion date of the invoice that the credit memo is against, and not the
credit memo transaction date.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.EXCHANGE_DATE
CONVERSION_RATE
Enter the conversion rate for this transaction.
If CONVERSION_TYPE is User, you must enter a value in this column; otherwise do not enter a value. If the currency of
the transaction is the same as the ledger currency, enter User and set CONVERSION_RATE to 1.
Validation
If RA_INTERFACE_LINES_ALL.CONVERSION_TYPE = User, then this column must not be null; otherwise, it must be null.
Destination
RA_CUSTOMER_TRX_ALL.EXCHANGE_RATE
CONVERSION_TYPE
Enter the conversion rate type for this transaction. If the currency of the transaction is the same as the ledger currency,
enter User and set CONVERSION_RATE to 1. You must enter a value in this column.
Validation
Must exist in GL_DAILY_CONVERSION_TYPES.CONVERSION_TYPE.
Destination
RA_CUSTOMER_TRX_ALL.EXCHANGE_RATE_TYPE
CREDIT_METHOD_FOR_ACCT_RULE
Enter the credit method for crediting a transaction that uses a revenue scheduling rule. Valid values are PRORATE, LIFO,
and UNIT.
If this transaction is a credit memo against a transaction that uses a revenue scheduling rule and LINE_TYPE = LINE,
CHARGES, or you are passing header freight, you must enter a value in this column.
If this transaction is a credit memo against a transaction that uses a revenue scheduling rule and
CREDIT_METHOD_FOR_ACCT_RULE = UNIT, then AutoInvoice rejects the credit memo if the credit quantity exceeds
the quantity on the target invoice line.
61
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column. AutoInvoice
ignores any value that you enter in this column. For on-account credits, do not enter a value in this column.
Validation
Must be either PRORATE, LIFO, UNIT, or NULL.
Destination
RA_CUSTOMER_TRX_ALL.CREDIT_METHOD_FOR_RULES
CREDIT_METHOD_FOR_INSTALLMENTS
Enter the credit method for crediting a transaction that uses split payment terms. Valid values are PRORATE, LIFO, and
FIFO.
If this transaction is a credit memo against a transaction that uses split payment terms and LINE_TYPE = LINE,
CHARGES, or you are passing header freight, you can enter a value in this column. If you do not enter a value,
AutoInvoice uses the default value PRORATE.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column. AutoInvoice
ignores any value that you enter in this column. For on-account credits, do not enter a value in this column.
Validation
Must be either PRORATE, LIFO, FIFO, or NULL.
Destination
RA_CUSTOMER_TRX_ALL.CREDIT_METHOD_FOR_INSTALLMENTS
CURRENCY_CODE
Enter the currency for this transaction. You must enter a value in this column.
For credit memos, enter the currency of the invoice that you are crediting.
Validation
Must exist in FND_CURRENCIES.CURRENCY_CODE.
Destination
RA_CUSTOMER_TRX_ALL.INVOICE_CURRENCY_CODE and
AR_PAYMENT_SCHEDULES_ALL.INVOICE_CURRENCY_CODE.
CUSTOMER_BANK_ACCOUNT_ID
Enter the bill-to customer bank account ID for this transaction.
62
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Customer Bank Account option (Value or ID) in the Import Information section of the transaction source, you can
enter a value either in this column or in the CUSTOMER_BANK_ACCOUNT_NAME column. If you enter a value in the
CUSTOMER_BANK_ACCOUNT_NAME column, AutoInvoice enters a corresponding ID in this column.
If the receipt method is of type Automatic and this column is null, AutoInvoice populates a value for you.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_ID. If the receipt method is of type Manual,
RA_INTERFACE_LINES_ALL.CUSTOMER_BANK_ACCOUNT_ID must be null.
Destination
RA_CUSTOMER_TRX_ALL.CUSTOMER_BANK_ACCOUNT_ID
CUSTOMER_BANK_ACCOUNT_NAME
Enter the bill-to customer bank account name for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Customer Bank Account option (Value or ID) in the Import Information section of the transaction source, you can
enter a value either in this column or in the CUSTOMER_BANK_ACCOUNT_ID column.
If the receipt method is of type Automatic and this column is null, AutoInvoice populates a value for you.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NAME. If the receipt method is of type Manual,
RA_INTERFACE_LINES_ALL.CUSTOMER_BANK_ACCOUNT_NAME must be null.
Destination
None.
CUSTOMER_TRX_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using the
AutoInvoice grouping rule.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID, AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_TRX_ID,
RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_ID, and RA_CUST_TRX_LINE_GL_DIST_ALL.CUSTOMER_TRX_ID.
63
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
CUST_TRX_TYPE_ID
Enter the transaction type ID for this transaction.
This column is optional. Depending on the seing of the Transaction Type option (Value or ID) in the
Import Information section of the transaction source, you must enter a value either in this column or in the
CUST_TRX_TYPE_NAME column. If you enter a value in the CUST_TRX_TYPE_NAME column, AutoInvoice enters a
corresponding ID in this column.
For credit memos you must enter the ID of the credit memo transaction type which has been assigned to the
transaction you are crediting.
Validation
Must exist in RA_CUST_TRX_TYPES_ALL.CUST_TRX_TYPE_ID.
Destination
RA_CUSTOMER_TRX_ALL.CUST_TRX_TYPE_ID
CUST_TRX_TYPE_NAME
Enter the transaction type name for this transaction.
This column is optional. Depending on the seing of the Transaction Type option (Value or ID) in the
Import Information section of the transaction source, you must enter a value either in this column or in the
CUST_TRX_TYPE_ID column.
For credit memos, you must enter the name of the credit memo transaction type that is assigned to the transaction you
are crediting.
Validation
RA_CUST_TRX_TYPES_ALL.NAME
Destination
None.
DEFAULT_TAXATION_COUNTRY
Enter the default taxation country.
The default taxation country is the country of taxation for tax calculation purposes.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL
64
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
DESCRIPTION
This is a required column in AutoInvoice. Enter the description for this transaction.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.DESCRIPTION
DOCUMENT_NUMBER
Enter the document sequence number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the creation method for the sequence
numbering of this transaction is Manual, you must enter a value in this column.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the creation method for the sequence
numbering of this transaction is Automatic, do not enter a value in this column. AutoInvoice generates a unique
document sequence number.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
The number must not already exist.
Destination
RA_CUSTOMER_TRX_ALL.DOC_SEQUENCE_VALUE
DOCUMENT_NUMBER_SEQUENCE_ID
This column is used by AutoInvoice and should be left null. AutoInvoice uses this column to store the document
sequence ID for this transaction.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.DOC_SEQUENCE_ID
DOCUMENT_SUB_TYPE
Enter the document scal classication code for the transaction line.
65
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The document scal classication is used to classify transactions that require special documentation to accompany the
transaction for tax purposes, as designated by a tax authority.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL
EXCEPTION_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column when the
transaction has a tax exception.
For credit memos, AutoInvoice enters the tax exception ID of the transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ITEM_EXCEPTION_RATE_ID
EXEMPTION_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column when the
transaction has a tax exemption, either full or partial.
For credit memos, AutoInvoice enters the tax exemption ID of the transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_EXEMPTION_ID
FOB_POINT
Enter the FOB (free on board) point for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the FOB point from the transaction you are
crediting.
66
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
Must exist in AR_LOOKUPS.LOOKUP_CODE, and AR_LOOKUPS.LOOKUP_TYPE = FOB. Must be less than or equal to 30
characters in length.
Destination
RA_CUSTOMER_TRX_ALL.FOB_POINT
GL_DATE
Enter the accounting date for this transaction. The accounting date determines the accounting period that the
transaction is recorded in the general ledger. If the Post to GL option on the transaction type of the transaction being
passed is not enabled, then this column should be null.
If LINE_TYPE = LINE, CHARGES, and you are passing transactions without rules, or you are passing header freight, this
column is optional.
If LINE_TYPE = LINE and you are importing transactions with rules, do not enter a date in this column.
For credit memos, AutoInvoice uses the date you run AutoInvoice, unless the transaction you are crediting is billed in
arrears. In that case, AutoInvoice uses the accounting date of the transaction you are crediting.
Validation
Must be in an Open or Future Enterable accounting period and the period must exist in GL_PERIOD_STATUSES. If the
Post to GL option on the transaction type of the transaction being passed is not enabled, or if the invoice uses the In
Arrears invoicing rule, then the column should be null.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.GL_DATE
HEADER_ ATTRIBUTE1-15
Enter Descriptive Flexeld aribute information for the Transaction Information Flexeld. Descriptive Flexeld aributes
let you store additional columns, the contents of which you dene.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, these columns are optional.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.ATTRIBUTE1-15. To ensure that AutoInvoice accurately groups your imported invoices, do
not include newline or carriage return characters (chr(10) or chr(13)) in these Descriptive Flexeld columns.
67
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
HEADER_ATTRIBUTE_CATEGORY
For the Transaction Information Flexeld, enter Descriptive Flexeld aribute category information which is shared
between this transaction and other transactions. Descriptive Flexeld categories allow you to store dierent categories
of aributes.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter values in these columns.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.ATTRIBUTE_CATEGORY
HEADER_GDF_ATTRIBUTE1-30
Reserved for country-specic functionality.
Validation
Performed by Global Financials.
Destination
RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE1-30
HEADER_GDF_ATTR_CATEGORY
Reserved for country-specic functionality.
Validation
Performed by Global Financials.
Destination
RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE_CATEGORY
INITIAL_CUSTOMER_TRX_ID
This column is used by AutoInvoice and should be left null.
If the transaction is not a credit memo, AutoInvoice enters a value in this column using
RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID.
68
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.INITIAL_CUSTOMER_TRX_ID
INTERCOMPANY_FLAG
This column is used by AutoInvoice to indicate whether a transaction is an intercompany transaction. Valid values are Y
or null.
For intercompany transactions, AutoInvoice calls the appropriate program to derive the Receivables code combination
ID.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES
INTERFACE_LINE_ATTRIBUTE1-15
Enter the Line Transaction Flexeld for this transaction. The Line Transaction Flexeld is a combination of aribute
values that you use to uniquely identify this transaction line in your original system. The reference values you enter
here provide you with an audit trail from Receivables back to your original system. You must enter values for enabled
aributes.
Receivables copies the Line Transaction Flexeld to the Invoice Transaction Flexeld. When you import transactions
with multiple lines using AutoInvoice, the aributes of the rst line from the ordered lines appear in the Invoice
Transaction Flexeld.
Note: Interface lines belonging to the same transaction are ordered by the following SQL clause:
waybill_number||ship_via asc,
ship_date_actual desc
If a transaction has only one line, then the Invoice Transaction Flexeld is the same as the Line Transaction Flexeld.
Validation
Must not already exist together with INTERFACE_LINE_CONTEXT in RA_INTERFACE_LINES_ALL and
RA_CUSTOMER_TRX_LINES_ALL. All enabled aributes for a given INTERFACE_LINE_CONTEXT must have values.
Dierent aribute columns may be enabled depending on the value in the INTERFACE_LINE_CONTEXT column.
Destination
RA_CUSTOMER_TRX_ALL.INTERFACE_HEADER_ATT RIBUTE1-15 and
RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_A TTRIBUTE1-15. To ensure that AutoInvoice accurately groups
69
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
your imported invoices, do not include newline or carriage return characters (chr(10) or chr(13)) in these Descriptive
Flexeld columns.
INTERFACE_LINE_CONTEXT
This is a required column in AutoInvoice. Enter the context of the Line Transaction Flexeld entered in columns
INTERFACE_LINE_ATTRIBUTE1-15. If you pass information with global context, set this column to Global Data Elements.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.INTERFACE_HEADER_CON TEXT and
RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_CONTEXT.
INTERFACE_LINE_GUID
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL
INTERFACE_LINE_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using the
RA_CUSTOMER_TRX_LINES_S sequence.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID
INTERFACE_STATUS
This column is used by AutoInvoice and should be left null. If AutoInvoice sets this column to P, then the line has been
transferred successfully.
70
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
INTERNAL_NOTES
Enter internal notes for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter text in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.INTERNAL_NOTES
INVENTORY_ITEM_ID
Enter the inventory item ID for this transaction.
If LINE_TYPE = LINE or CHARGES, this column is optional. Depending on the seing of the Inventory Item option
(Segment, ID, None) in the Import Information section of the transaction source, you can enter a value either in this
column or a combination of segment values in the MTL_SYSTEM_ITEMS_SEG1-20 column. If you specied Segment on
the transaction source, AutoInvoice enters a corresponding ID in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the value from the transaction you are
crediting.
Validation
Must exist in MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID and MTL_SYSTEM_ITEMS.INVOICE_ENABLED_FLAG = Y.
Destination
RA_CUSTOMER_TRX_LINES_ALL.INVENTORY_ITEM_ID
INVOICING_RULE_ID
Enter the invoicing rule ID for this transaction.
If LINE_TYPE = LINE or you are passing header freight, this column is optional. For invoice lines with rules, you must
enter a value either in this column or in the INVOICING_RULE_NAME column, depending on the seing of the Invoicing
Rule option (Value, ID, None) in the Import Information section of the transaction source. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
71
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For credit memos, do not enter a value in this column. AutoInvoice uses the invoicing rule from the transaction you are
crediting.
Validation
Must exist in RA_RULES.RULE_ID and RA_RULES.RULE_ID = -2 or -3. If you enter an invoicing rule, you must also enter
a revenue scheduling rule. If LINE_TYPE = CHARGES, then this column must be null.
Destination
RA_CUSTOMER_TRX_ALL.INVOICING_RULE_ID
INVOICING_RULE_NAME
Enter the invoicing rule name for this transaction.
If LINE_TYPE = LINE or you are passing header freight, this column is optional. For invoice lines with rules, you must
enter a value either in this column or in the INVOICING_RULE_ID column, depending on the seing of the Invoicing
Rule option (Value, ID, None) in the Import Information section of the transaction source.
If LINE_TYPE = TAX, CHARGES or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the invoicing rule from the transaction you are
crediting.
Validation
Must exist in RA_RULES.RULE_ID and RA_RULES.RULE_ID = -2 or -3. If you enter an invoicing rule, you must also enter
a revenue scheduling rule. If LINE_TYPE = CHARGES, then this column must be null.
Destination
None.
LAST_PERIOD_TO_CREDIT
For credit memos with a credit method of UNIT, enter the last period number from which you want to start crediting.
If this transaction is a credit memo against a transaction that uses a revenue scheduling rule, and LINE_TYPE = LINE,
CREDIT_METHOD_FOR_ACCT_RULE = UNIT, or you are passing header freight, you can enter a value in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column. AutoInvoice
ignores any value that you enter in this column.
Validation
Must be between 0 and the number of periods inclusive in the invoice revenue scheduling rule.
Destination
RA_CUSTOMER_TRX_LINES_ALL.LAST_PERIOD_TO_CREDIT
72
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
LAST_UPDATE_LOGIN
This column is used by AutoInvoice and should be left null. AutoInvoice updates this column when it selects rows from
the RA_INTERFACE_LINES_ALL table for processing.
Validation
None.
Destination
None.
LINE_GDF_ATTRIBUTE1-20
Reserved for country-specic functionality.
Validation
Performed by Global Financials.
Destination
RA_CUSTOMER_TRX_LINES_ALL.GLOBAL_ATTRIBUTE1-20
LINE_GDF_ATTR_CATEGORY
Reserved for country-specic functionality.
Validation
Performed by Global Financials.
Destination
RA_CUSTOMER_TRX_LINES_ALL.GLOBAL_ATTRIBUTE_CATEGORY
LINE_INTENDED_USE
Enter the product intended use code of the transaction line.
The product intended use code identies situations where the intended use of the product is a factor either in tax
determination or the tax recovery rate.
Validation
None.
73
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUSTOMER_TRX_LINES_ALL
LINE_NUMBER
This column is used by AutoInvoice and should be left null. AutoInvoice ignores any values passed in this column, and
always numbers the lines sequentially starting with the number 1 and in the order determined by the line ordering rule.
LINE_TYPE
Enter LINE, TAX, FREIGHT, or CHARGES to specify the line type for this transaction. You must enter a value in this
column.
For credit memos, enter the type of line you are crediting.
Validation
Must be LINE, TAX, FREIGHT, or CHARGES.
Destination
RA_CUSTOMER_TRX_LINES_ALL.LINE_TYPE
LINK_TO_LINE_ATTRIBUTE1-15
Enter the link to your Transaction Flexeld aribute values.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, do not enter values in these columns.
If LINE_TYPE = TAX or you are passing freight for a specic line, you must enter a value. Use link-to-line aributes to
associate this tax or freight line to another transaction line in RA_INTERFACE_LINES_ALL. All tax lines and freight for
specic lines must be associated with a line that has a LINE_TYPE of LINE. Enter the same combination of aribute
values as the transaction that you are associating this transaction with.
For credit memos applied to tax lines, you must use these columns to link your credit memo tax lines to your credit
memo transaction. Similarly, for credit memos applied to freight lines, you must also use these columns to link your
credit memo freight line to your credit memo transaction.
If you are applying a credit memo against a tax line which is linked to a transaction, you must enter a dummy credit
memo transaction with a zero revenue amount and use these columns to link to your credit memo tax line. Similarly,
if you are applying a credit memo against a freight line which is linked to a transaction, you must also enter a dummy
credit memo transaction with a zero revenue amount and use these columns to link to your credit memo freight line.
Validation
The transaction that you link to must have a LINE_TYPE = LINE. You can only link at most one freight line to another
transaction. You cannot link a transaction that has a LINE_TYPE = LINE or CHARGES to another transaction.
74
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
LINK_TO_LINE_CONTEXT
Enter the context name of the Transaction Flexeld data that you entered in
RA_INTERFACE_LINES_ALL.LINK_TO_LINE_ATTRIBUTE1-15.
Validation
None.
Destination
None.
LINK_TO_LINE_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using
RA_INTERFACE_LINES_ALL.LINK_TO_LINE_ATTRIBUTE1-15 and RA_INTERFACE_LINES_ALL.LINK_TO_LINE_CONTEXT.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.LINK_TO_CUST_TRX_LINE_ID
LOCATION_SEGMENT_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column if you are crediting
a sales tax line.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.LOCATION_SEGMENT_ID
MEMO_LINE_ID
Enter the standard memo line ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Memo Line Rule option (Value or ID) in the Import Information section of the transaction source, you can enter
75
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
a value either in this column or in the MEMO_LINE_NAME column. If you specied Value on the transaction source,
AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the memo line from the transaction you are
crediting.
Validation
Must exist in AR_MEMO_LINES_ALL.MEMO_LINE_ID.
Destination
RA_CUSTOMER_TRX_LINES_ALL.MEMO_LINE_ID
MEMO_LINE_NAME
Enter the name of the standard memo line for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Memo Line Rule option (Value or ID) in the Import Information section of the transaction source, you can enter a
value either in this column or in the MEMO_LINE_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the memo line from the transaction you are
crediting.
Validation
Must exist in AR_MEMO_LINES_ALL.NAME.
Destination
None.
MOVEMENT_ID
This column is used to pass movement statistics that are tied to the shipment information and passed through
AutoInvoice.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.MOVEMENT_ID
76
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
MTL_SYSTEM_ITEMS_SEG1-20
Assign a System Item Flexeld value for each segment you enable in Receivables. For example, if you enable six System
Item Flexeld segments, you must enter six values in columns MTL_SYSTEM_ITEMS_SEG1-6. Be sure to enter the
correct segment value. For example, value 01 is not the same as 1.
If LINE_TYPE = LINE or CHARGES, these columns are optional. Depending on the seing of the Inventory Item option
(Segment, ID, None) in the Import Information section of the transaction source you can enter values either in these
columns or in the INVENTORY_ITEM_ID column.
For credit memos, do not enter values in these columns. AutoInvoice uses the values from the transaction you are
crediting.
Validation
Valid combination of System Item Flexeld segment values.
Destination
None.
ORG_ID
Enter the ID of the business unit that this transaction belongs to.
Validation
AutoInvoice imports transactions whose ORG_ID matches the value of the MO: Operating Unit prole option.
Destination
None.
ORIGINAL_GL_DATE
Stores the value of the GL_DATE column before AutoInvoice modies the accounting date. This column is used by
AutoInvoice and should not be populated by the user.
Validation
None.
Destination
None.
77
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
ORIG_SYSTEM_BATCH_NAME
Enter the batch name for this transaction. This column is optional.
AutoInvoice does not perform any validation on this column, but uses the value entered when grouping transactions
into invoices.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.ORIG_SYSTEM_BATCH_NAME
ORIG_SYSTEM_BILL_ADDRESS_ID
Enter the bill-to customer address ID for this transaction. This bill-to customer address ID is for the bill-to customer you
entered in ORIG_SYSTEM_BILL_CUSTOMER_REF or ORIG_SYSTEM_BILL_CUSTOMER_ID column.
If no default remit-to address is specied, then AutoInvoice uses the bill-to address to determine the remit-to address
for the customer. If the remit-to address cannot be determined, then AutoInvoice rejects the transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Bill-to Address option (Value or ID) in the Import Information section of the transaction source, you must
enter a value either in this column or in the ORIG_SYSTEM_BILL_ADDRESS_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADD RESS_ID = HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
and HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and
RA_SITE_USES.SITE_USE_CODE = BILL_TO.
Destination
None.
ORIG_SYSTEM_BILL_ADDRESS_REF
Enter the bill-to customer address reference from your original system. This reference is for the bill-to customer you
entered in the ORIG_SYSTEM_BILL_CUSTOMER_REF or ORIG_SYSTEM_BILL_CUSTOMER_ID column. The reference
value you enter here provides you with an audit trail from Receivables back to your original system.
78
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If no default remit-to address is specied, then AutoInvoice uses the bill-to address to determine the remit-to address
for the customer. If the remit-to address cannot be determined, then AutoInvoice rejects the transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Bill-to Address option (Value or ID) in the Import Information section of the transaction source, you must enter a
value either in this column or in the ORIG_SYSTEM_BILL_ADDRESS_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADD RESS_REF = HZ_PARTY_SITES.ORIG_SYSTEM_REFERENCE and
CUSTOMER_REF = HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE and HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
= HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID =
HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and RA_SITE_USES.SITE_USE_CODE = BILL_TO.
Destination
None.
ORIG_SYSTEM_BILL_CONTACT_ID
Enter the bill-to contact ID for this transaction. This bill-to contact ID must be for the bill-to customer that you entered
in the ORIG_SYSTEM_BILL_CUSTOMER_REF or ORIG_SYSTEM_BILL_CUSTOMER_ID column.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Bill-to Contact option (Value, ID, None) in the Import Information section of the transaction source, you can
enter a value either in this column or in the ORIG_SYSTEM_BILL_CONTACT_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUS TOMER_ID = HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CON TACT_ID = HZ_CUST_SITE_USES.CUSTOMER_SITE_ID.
Destination
RA_CUSTOMER_TRX_ALL.BILL_TO_CONTACT_ID
ORIG_SYSTEM_BILL_CONTACT_REF
Enter the bill-to contact reference from your original system. This reference is for the bill-to customer that you entered
in the ORIG_SYSTEM_BILL_CUSTOMER_REF or ORIG_SYSTEM_BILL_CUSTOMER_ID column. The reference value you
enter here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Bill-to Contact option (Value, ID, None) in the Import Information section of the transaction source, you can enter a
value either in this column or in the ORIG_SYSTEM_BILL_CONTACT_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
79
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUS TOMER_ID = HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CONTACT_REF = RA_CONTACTS.ORIG_SYSTEM_REFERENCE.
Destination
None.
ORIG_SYSTEM_BILL_CUSTOMER_ID
Enter the bill-to customer ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Bill-to Customer option (Value or ID) in the Import Information section of the transaction source, you must enter
a value either in this column or in the ORIG_SYSTEM_BILL_CUSTOMER_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, you must enter the bill-to customer ID or the bill-to customer reference of a related customer of the
transaction you are crediting.
Validation
Must exist in HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
Destination
RA_CUSTOMER_TRX_ALL.BILL_TO_CUSTOMER_ID
ORIG_SYSTEM_ BILL_CUSTOMER_REF
Enter a value you can use to uniquely identify this bill-to customer in your original system. The reference value you
enter here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Bill-to Customer option (Value or ID) in the Import Information section of the transaction source, you must enter a
value either in this column or in the ORIG_SYSTEM_BILL_CUSTOMER_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, you must enter the bill-to customer reference or the bill-to customer ID of a related customer of the
transaction you are crediting.
Validation
Must exist in HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE.
Destination
None.
80
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
ORIG_SYSTEM_SHIP_ADDRESS_ID
Enter the ship-to customer address ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Ship-to Address option (Value, ID, None) in the Import Information section of the transaction source, you can
enter a value either in this column or in the ORIG_SYSTEM_SHIP_ADDRESS_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column; AutoInvoice uses the ship-to address from the transaction you
are crediting.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_ADDRESS_ID = HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
and HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and
HZ_CUST_SITE_USES.SITE_USE_CODE = SHIP_TO.
Destination
None.
ORIG_SYSTEM_SHIP_ADDRESS_REF
Enter a value you can use to uniquely identify this ship-to customer address in your original system. The reference
value you enter here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Ship-to Address option (Value, ID, None) in the Import Information section of the transaction source, you can enter
a value either in this column or in the ORIG_SYSTEM_SHIP_ADDRESS_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column, AutoInvoice uses the ship-to address from the transaction you
are crediting.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_ADDRESS_REF = HZ_PARTY_SITES.ORIG_SYSTEM_REFERENCE
and RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
and HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID = HZ_CUST_ACCT_SITE.CUST_ACCOUNT_ID and
HZ_CUST_ACCT_SITE.CUSTOMER_SITE_ID = HZ_CUST_SITE_USES.CUST_ACCT_SITE_ID and
HZ_CUST_SITE_USES.SITE_USE_CODE = SHIP_TO.
Destination
None.
81
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
ORIG_SYSTEM_SHIP_CONTACT_ID
Enter the ship-to contact ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Ship-to Contact option (Value, ID, None) in the Import Information section of the transaction source, you can
enter a value either in this column or in the ORIG_SYSTEM_SHIP_CONTACT_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to contact from the transaction you
are crediting.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CUSTOMER_ID = HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CONTACT_ID = HZ_CUST_SITE_USES.CUSTOMER_SITE_ID.
Destination
RA_CUSTOMER_TRX_ALL.SHIP_TO_CONTACT_ID
ORIG_SYSTEM_SHIP_CONTACT_REF
Enter a value you can use to uniquely identify this ship-to contact in your original system. The reference value you enter
here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Ship-to Contact option (Value, ID, None) in the Import Information section of the transaction source, you can enter
a value either in this column or in ORIG_SYSTEM_SHIP_CONTACT_ID.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to contact from the transaction you
are crediting.
Validation
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CUSTOMER_ID = HZ_CUST_ACCT_ROLES.CUST_ACCOUNT_ID and
RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_SHIP_CONTACT_REF =
HZ_CUST_ACCOUNT_ROLES.ORIG_SYSTEM_REFERENCE.
Destination
None.
ORIG_SYSTEM_SHIP_CUSTOMER_ ID
Enter the ship-to customer ID for this transaction.
82
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Ship-to Customer option (Value, ID, None) in the Import Information section of the transaction source, you can
enter a value either in this column or in the ORIG_SYSTEM_SHIP_CUSTOMER_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to customer from the transaction you
are crediting.
Validation
Must exist in HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
Destination
RA_CUSTOMER_TRX_ALL.SHIP_TO_CUSTOMER_ID
ORIG_SYSTEM_SHIP_CUSTOMER_REF
Enter a value you can use to uniquely identify this ship-to customer in your original system. The reference value you
enter here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Ship-to Customer option (Value, ID, None) in the Import Information section of the transaction source, you can
enter a value either in this column or in the ORIG_SYSTEM_SHIP_CUSTOMER_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to customer from the transaction you
are crediting.
Validation
Must exist in HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE.
Destination
None.
ORIG_SYSTEM_SOLD_CUSTOMER_ID
Enter the sold-to customer ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Sold-to Customer option (Value or ID) in the Import Information section of the transaction source, you can enter
a value either in this column or in the ORIG_SYSTEM_SOLD_CUSTOMER_REF column. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value. AutoInvoice uses the sold-to customer from the transaction you are crediting.
83
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
Must exist in HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
Destination
RA_CUSTOMER_TRX_ALL.SOLD_TO_CUSTOMER_ID
ORIG_SYSTEM_SOLD_CUSTOMER_REF
Enter a value you can use to uniquely identify this sold-to customer in your original system. The reference value you
enter here provides you with an audit trail from Receivables back to your original system.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Sold-to Customer option (Value or ID) in the Import Information section of the transaction source, you can enter a
value either in this column or in the ORIG_SYSTEM_SOLD_CUSTOMER_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value. AutoInvoice uses the sold-to customer from the transaction you are crediting.
Validation
Must exist in HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE.
Destination
None.
OVERRIDE_AUTO_ACCOUNTING_FLAG
This column controls whether the code combination ID of the Accounting Flexeld for this accounting distribution,
populated by the feeder system, should override AutoAccounting.
Validation
Value should be Y or N.
Destination
RA_CUSTOMER_TRX_LINES_ALL.OVERRIDE_AUTO_ACCOUNTING_FLAG
PAYMENT_SET_ID
This column contains a unique internal ID number that matches prepaid invoices with their prepayment receipts. This
column should be populated only within a prepayments ow.
84
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
Must exist in AR_RECEIVABLE_APPLICATIONS_ALL.PAYMENT_SET_ID.
Destination
RA_CUSTOMER_TRX_LINES_ALL.PAYMENT_SET_ID
PAYING_CUSTOMER_ID
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PAYING_CUSTOMER_ID
PAYING_SITE_USE_ID
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PAYING_SITE_USE_ID
PAYMENT_SERVER_ORDER_NUM
A number that indicates the credit card payment was authorized by the Payments Server.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PAYMENT_SERVER_ORDER_NUM
PREVIOUS_CUSTOMER_TRX_ID
This column is used by AutoInvoice and should be left null.
For credit memos, AutoInvoice enters a value in this column using RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID.
85
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PREVIOUS_CUSTOMER_TRX_ID and RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_ID.
PRIMARY_SALESREP_ID
Enter the primary salesperson ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the Require salesperson Receivables system
option is enabled, you must enter a value either in this column or in the PRIMARY_SALESREP_NUMBER column.
Otherwise this column is optional. The value that you enter here depends on the seing of the Salesperson option
(Number or ID) in the Import Information section of the transaction source. If you specied Number on the transaction
source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in RA_SALESREPS.SALESREP_ID.
Destination
RA_CUSTOMER_TRX_ALL.PRIMARY_SALESREP_ID
PRIMARY_SALESREP_NUMBER
Enter the primary salesperson number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the Require salesperson Receivables system
option is enabled, you must enter a value either in this column or in the PRIMARY_SALESREP_ID column. Otherwise this
column is optional. The value that you enter here depends on the seing of the Salesperson option (Number or ID) in
the Import Information section of the transaction source.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in RA_SALESREPS.SALESREP_NUMBER.
Destination
None.
PRINTING_OPTION
Enter the printing option for this transaction.
86
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. AutoInvoice uses the printing
option that you entered for the transaction type.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.LOOKUP_CODE and AR_LOOKUP.LOOKUP_TYPE = INVOICE_PRINT_OPTIONS.
Destination
RA_CUSTOMER_TRX_ALL.PRINTING_OPTION
PRODUCT_CATEGORY
Enter the product category code of the noninventory item on the transaction line.
The product category code is used to classify noninventory items and items that are not a good that have a tax
requirement for tax determination or tax reporting purposes.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL
PRODUCT_FISC_CLASSIFICATION
Enter the product scal classication code of the inventory item on the transaction line.
The product scal classication is used to classify inventory items that have a tax requirement for tax determination or
tax reporting purposes.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL
PRODUCT_TYPE
Enter the product type code of the inventory item. Valid values are GOODS and SERVICES.
Validation
None.
87
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUSTOMER_TRX_LINES_ALL
PURCHASE_ORDER
Enter the purchase order number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the purchase order number from the
transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PURCHASE_ORDER
PURCHASE_ORDER_DATE
Enter the date of the purchase order for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the purchase order date from the transaction
you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PURCHASE_ORDER_DATE
PURCHASE_ORDER_REVISION
Enter the purchase order revision for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the purchase order revision from the
transaction you are crediting.
88
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PURCHASE_ORDER_REVISION
QUANTITY
If this transaction is an invoice or credit memo line and LINE_TYPE = LINE, or you are passing header freight,
this column is optional. For invoice lines, enter the number of units shipped. For credit memo lines, enter the
number of units you are crediting. If you do not enter a value in this column, AutoInvoice uses AMOUNT as the
EXTENDED_AMOUNT for this transaction. If this transaction is a dummy line for either freight only or tax only,
AutoInvoice ignores the value you enter in this column.
If this is a credit memo line, and LINE_TYPE = LINE and CREDIT_METHOD_FOR_ACCT_RULE = UNIT, then this column
is required.
If this transaction is a credit memo against a transaction that uses a revenue scheduling rule and
CREDIT_METHOD_FOR_ACCT_RULE = UNIT, then AutoInvoice rejects the credit memo if the credit quantity exceeds
the quantity on the target invoice line.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
For debit memo lines with LINE_TYPE = CHARGES, quantity must be 1. For credit memo lines with
LINE_TYPE = CHARGES, this column must be 1 or -1. For credit memo lines with LINE_TYPE = LINE and
CREDIT_METHOD_FOR_ACCT_RULE = UNIT, this column must not be null.
Destination
RA_CUSTOMER_TRX_LINES_ALL.QUANTITY_INVOICED, if this transaction is an invoice line.
RA_CUSTOMER_TRX_LINES_ALL.QUANTITY_CREDITED, if this transaction is a credit memo line.
QUANTITY_ORDERED
Enter the original number of units ordered for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing freight for a specic line, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this eld.
For credit memos, do not enter a value in this column. AutoInvoice uses the quantity ordered from the transaction you
are crediting.
Validation
None.
89
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUSTOMER_TRX_LINES_ALL.QUANTITY_ORDERED
REASON_CODE
Enter the reason code for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Memo Reason option (Value or ID) in the Import Information section of the transaction source, you can enter a
value either in this column or in the REASON_CODE_MEANING column. If you specied Value on the transaction source,
AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.LOOKUP_CODE. This lookup type is either INVOICING_REASON or
CREDIT_MEMO_REASON.
Destination
RA_CUSTOMER_TRX_LINES_ALL.REASON_CODE and RA_CUSTOMER_TRX_ALL.REASON_CODE.
REASON_CODE_MEANING
Enter the meaning of the reason code for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Memo Reason option (Value or ID) in the Import Information section of the transaction source, you can enter a
value either in this column or in the REASON_CODE column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.MEANING. This lookup type is either INVOICING_REASON or CREDIT_MEMO_REASON.
Destination
None.
RECEIPT_METHOD_ID
Enter the receipt method ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Payment Method Rule option (Value or ID) in the Import Information section of the transaction source, you can
90
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
enter a value either in this column or in the RECEIPT_METHOD_NAME column. If you specied Value on the transaction
source, AutoInvoice enters a corresponding ID in this column.
Validation
Must exist in AR_RECEIPT_METHODS.RECEIPT_METHOD_ID and must belong to the bill-to customer or the parent.
Additionally, the receipt method must have at least one bank account in the same currency as the transaction.
Destination
RA_CUSTOMER_TRX_ALL.RECEIPT_METHOD_ID
RECEIPT_METHOD_NAME
Enter the name of the receipt method for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing
of the Payment Method Rule option (Value or ID) in the Import Information section of the transaction source, you can
enter a value either in this column or in the RECEIPT_METHOD_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this eld.
Validation
Must exist in AR_RECEIPT_METHODS.NAME and must belong to the bill-to customer or the parent.
Destination
None.
REFERENCE_LINE_ATTRIBUTE1-15
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and this transaction is a credit memo,
you must enter either the Transaction Flexeld of the transaction line you are crediting in these columns
or the RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the transaction you are crediting in
RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID. Otherwise, do not enter values in these columns.
If LINE_TYPE = TAX and this transaction is a credit memo, you must enter either the Transaction Flexeld of the tax line
you are crediting in these columns or the RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the transaction
tax line you are crediting in RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID. Otherwise, do not enter values in these
columns.
If LINE_TYPE = FREIGHT and this transaction is a credit memo, you must enter either the Transaction Flexeld of the
freight line you are crediting in these columns or the RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the
91
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
transaction freight line you are crediting in RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID. Otherwise, do not enter
values in these columns.
Validation
Must exist in RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_ATTRIBUTE1-15 or
RA_INTERFACE_LINES_ALL.INTERFACE_LINE_ATTRIBUTE1-15.
Destination
None.
REFERENCE_LINE_CONTEXT
Enter the context name of the Transaction Flexeld data entered in
RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ATTRIBUTE1-15. You must enter a value in this column if you entered
values in RA_INTERFACE_LINES_ALL.ATTRIBUTE1-15.
Validation
Must exist in RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_CONTEXT or
RA_INTERFACE_LINES_ALL.INTERFACE_LINE_CONTEXT.
Destination
None.
REFERENCE_LINE_ID
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and this transaction is a credit memo, you must
enter the RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the transaction line you are crediting in this
column or the Transaction Flexeld in the REFERENCE_LINE_ATTRIBUTE1-15 columns. Otherwise, do not enter a value.
If LINE_TYPE = TAX and this transaction is a credit memo, you must enter the
RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the tax line you are crediting in this column or the
Transaction Flexeld in the REFERENCE_LINE_ATTRIBUTE1-15 columns. Otherwise, do not enter a value in this column.
If LINE_TYPE = FREIGHT and this transaction is a credit memo, you must enter the
RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the freight line you are crediting in this column or the
Transaction Flexeld in the REFERENCE_LINE_ATTRIBUTE1-15 columns. Otherwise, do not enter a value in this column.
Validation
Must exist in RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID.
Destination
RA_CUSTOMER_TRX_LINES_ALL.PREVIOUS_CUSTOMER_TRX_LINE_ID if this transaction is a credit memo. Otherwise,
RA_CUSTOMER_TRX_LINES_ALL.INITIAL_CUSTOMER_TRX_LINE_ID.
92
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
RELATED_BATCH_SOURCE_NAME
Enter the name of the transaction source of the document to which this transaction is related.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Related Document option (Number, ID, None) in the Import Information section of the transaction source, you can
enter a value in this column and the related transaction number in the RELATED_TRX_NUMBER column. Or, you can
enter the related customer transaction ID in the RELATED_CUSTOMER_TRX_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
Validation
RA_INTERFACE_LINES_ALL.RELATED_BATCH_SOURCE_NAME = RA_BATCH_SOURCES_ALL.NAME and
RA_INTERFACE_LINES_ALL.RELATED_TRX_NUMBER = RA_CUSTOMER_TRX_ALL.TRX_NUMBER and
RA_BATCH_SOURCES_ALL.BATCH_SOURCE_ID = RA_CUSTOMER_TRX_ALL.BATCH_SOURCE_ID.
Destination
None.
RELATED_CUSTOMER_TRX_ID
Enter the customer transaction ID of the document to which this transaction is related.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Related Document option (Number, ID, None) in the Import Information section of the transaction source, you can
enter a value in this column. Or, you can enter the related transaction number in the RELATED_TRX_NUMBER column
and the related transaction source name in the RELATED_BATCH_SOURCE_NAME column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
Validation
Must exist in RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID.
Destination
RA_CUSTOMER_TRX_ALL.RELATED_CUSTOMER_TRX_ID
RELATED_TRX_NUMBER
Enter the document number to which this transaction is related.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Related Document option (Number, ID, None) in the Import Information section of the transaction source, you can
93
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
enter a value in this column and the related transaction source name in the RELATED_BATCH_SOURCE_NAME column.
Or, you can enter the related customer transaction ID in the RELATED_CUSTOMER_TRX_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
Validation
RA_INTERFACE_LINES_ALL.RELATED_BATCH_SOUR CE_NAME = RA_BATCH_SOURCES_ALL.NAME and
RA_INTERFACE_LINES_ALL.RELATED_TRX_NUMBER = RA_CUSTOMER_TRX_ALL.TRX_NUMBER and
RA_BATCH_SOURCES_ALL.BATCH_SOURCE_ID = RA_CUSTOMER_TRX_ALL.BATCH_SOURCE_ID.
Destination
None.
REQUEST_ID
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
The REQUEST_ID column in RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL,
RA_CUST_TRX_LINE_GL_DIST_ALL, AR_PAYMENT_SCHEDULES_ALL, AR_RECEIVABLE_APPLICATIONS_ALL,
AR_ADJUSTMENTS_ALL and RA_CUST_TRX_LINE_SALESREPS_ALL.
RULE_START_DATE
Enter the start date for the revenue scheduling rule for this transaction.
If LINE_TYPE = LINE or you are passing header freight, this column is optional.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.RULE_START_DATE
RULE_END_DATE
Enter the end date for the revenue scheduling rule for this transaction.
94
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This column is required if the revenue scheduling rule is either Daily Revenue Rate, All Periods or Daily Revenue Rate,
Partial Periods.
If LINE_TYPE = LINE or you are passing header freight, this column is optional.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.RULE_END_DATE
SALES_ORDER
Enter the sales order number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order number from the transaction
you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER
SALES_ORDER_DATE
Enter the date of the sales order for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order date from the transaction you
are crediting.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the revenue order date from the transaction
you are crediting.
95
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_DATE
SALES_ORDER_LINE
Enter the sales order line number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order line number from the
transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_LINE
SALES_ORDER_REVISION
Enter the sales order revision for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order revision from the transaction
you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_REVISION
SALES_ORDER_SOURCE
Enter the source of the sales order for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
96
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For credit memos, do not enter a value in this column. AutoInvoice uses the source of the sales order from the
transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_SOURCE
SALES_TAX_ID
This column is used by AutoInvoice and should be left null.
For credit memos, AutoInvoice uses the sales tax ID of the transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_TAX_ID
SET_OF_BOOKS_ID
Optionally enter the ledger ID for this transaction. If no value exists, then AutoInvoice uses the ledger of the business
unit assigned to Receivables system options.
Validation
Must exist in AR_SYSTEM_PARAMETERS_ALL.SET_OF_BOOKS_ID.
Destination
RA_CUSTOMER_TRX_ALL.SET_OF_BOOKS_ID
SHIP_DATE_ACTUAL
Enter the shipment date for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the earliest shipment date from the transaction
you are crediting.
Validation
None.
97
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUSTOMER_TRX_ALL.SHIP_DATE_ACTUAL
SHIP_VIA
Enter the ship_via code for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship_via code from the transaction you are
crediting.
Validation
ORG_FREIGHT.FREIGHT_CODE = RA_INTERFACE_LINES_ALL.SHIP_VIA and ORG_FREIGHT.ORGANIZATION_ID =
RA_INTERFACE_LINES_ALL.WAREHOUSE_ID. RA_INTERFACE_LINES_ALL.SHIP_VIA must be less than or equal to 25
characters in length.
Destination
RA_CUSTOMER_TRX_ALL.SHIP_VIA
SOURCE_DATA_KEY1-5
Enter line group aributes that link one or more transaction lines into groups.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SOURCE_DATA_KEY1-5
TAX_CODE
Enter the tax rate code for this tax line.
For credit memos, AutoInvoice uses the tax rate code from the transaction you are crediting.
Validation
Must exist in AR_VAT_TAX.TAX_CODE.
98
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
TAX_EXEMPT_FLAG
If LINE_TYPE = LINE, this column is optional. The value you enter here controls how a line is taxed:
• Enter E, if you want AutoInvoice to exempt an invoice line that would normally be taxed and the Allow
Override of Customer Exemptions prole option is set to Yes. If you enter E, you must enter a value in the
TAX_EXEMPT_REASON_CODE or TAX_EXEMPT_REASON_CODE_MEANING column, depending on the seing
of the Memo Reason option (Value or ID) in the Import Information section of the transaction source.
• Enter R, if you want AutoInvoice to force tax on an invoice line, ignoring any exemption certicates that may be
on le.
• Enter S, if you want tax to be calculated as per the normal procedures set up for Receivables transactions.
For all other line types, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.LOOKUP_CODE. Lookup type is TAX_CONTROL_FLAG.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_EXEMPT_FLAG
TAX_EXEMPT_NUMBER
Enter the tax exempt number for this transaction. If LINE_TYPE = LINE and TAX_EXEMPT_FLAG = E, then you can enter
a value in this column. Otherwise, do not enter a value in this column.
For all other line types, do not enter a value in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_EXEMPT_NUMBER
TAX_EXEMPT_REASON_CODE
Enter the tax exempt reason code for this transaction. If LINE_TYPE = LINE and TAX_EXEMPT_FLAG = E, then
depending on the seing of the Memo Reason option (Value or ID) in the Import Information section of the transaction
99
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
source, you must enter a value either in this column or in the TAX_EXEMPT_REASON_CODE_MEANING column. If you
specied Value on the transaction source, AutoInvoice enters a corresponding ID in this column.
For all other line types, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.LOOKUP_CODE. Lookup type is TAX_REASON.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_EXEMPT_REASON_CODE
TAX_EXEMPT_REASON_CODE_MEANING
Enter the tax exempt reason code meaning for this transaction. If LINE_TYPE = LINE and TAX_EXEMPT_FLAG = E, then
depending on the seing of the Memo Reason option (Value or ID) in the Import Information section of the transaction
source, you must enter a value either in this column or in the TAX_EXEMPT_REASON_CODE column. Otherwise, do not
enter a value in this column.
For all other line types, do not enter a value in this column.
Validation
Must exist in AR_LOOKUPS.MEANING. Lookup type is TAX_REASON.
Destination
None.
TAX_PRECEDENCE
Enter the precedence number for this tax line. This column is used to compute tax compounding.
If LINE_TYPE = TAX and you allow compound tax, you can enter a value in this column. Otherwise do not enter a value.
If you are passing freight for a specic line, do not enter a value in this column.
For credit memos, AutoInvoice uses the tax precedence from the transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_PRECEDENCE
100
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
TAX_RATE
Enter the tax rate for this tax line.
If LINE_TYPE = TAX, you must enter a value either in this column or the AMOUNT column. Any exemptions for the tax
lines must be factored into the tax rate.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TAX_RATE
TERM_ID
Enter the payment terms ID for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Payment Terms option (Value or ID) in the Import Information section of the transaction source, you must enter a
value either in this column or in the TERM_NAME column. If you specied Value on the transaction source, AutoInvoice
enters a corresponding ID in this column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
Validation
Must exist in RA_TERMS.TERM_ID.
Destination
RA_CUSTOMER_TRX_ALL.TERM_ID
TERM_NAME
Enter the name of the payment terms for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing of
the Payment Terms option (Value or ID) in the Import Information section of the transaction source, you must enter a
value either in this column or in the TERM_ID column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos and on-account credits, do not enter a value in this column.
101
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
Must exist in RA_TERMS.NAME.
Destination
None.
TRANSLATED_DESCRIPTION
The translated description of this transaction line.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.TRANSLATED_DESCRIPTION
TRX_BUSINESS_CATEGORY
Enter the transaction business category code for the transaction line.
The transaction business category is used to classify transactions and as a determining factor in tax calculation.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL
TRX_DATE
Enter the transaction date for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional:
• If this transaction is an invoice or debit memo line, you can enter the invoice date.
• If this transaction is a credit memo line, you can enter the credit memo date.
If this transaction is an invoice line and uses an In Arrears invoicing rule, do not enter a value in this column.
If you do not enter a transaction date, AutoInvoice uses the accounting date for invoice and debit memo lines.
For credit memo lines, AutoInvoice uses the following hierarchy to determine the transaction date, selecting whichever
date is later:
• Credit memo accounting date.
• Accounting date entered in the run of the Import AutoInvoice program.
102
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.TRX_DATE
TRX_NUMBER
Enter the number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the Automatic transaction numbering option
on the transaction source is not enabled, you must enter a value in this column.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, and the Automatic transaction numbering option
on the transaction source is enabled, do not enter a value in this column. AutoInvoice inserts a unique number in this
column.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
Must not already exist in RA_CUSTOMER_TRX_ALL.TRX_NUMBER and RA_CUSTOMER_TRX_ALL.BATCH_SOURCE_ID.
Destination
RA_CUSTOMER_TRX_ALL.TRX_NUMBER and AR_PAYMENT_SCHEDULES_ALL.TRX_NUMBER.
UOM_CODE
Enter the unit of measure code for this transaction.
If LINE_TYPE = LINE and the line has an item, you must enter a value either in this column or in the UOM_NAME
column. If this a freight-only line, a tax-only line, or a line with no item, this column is optional.
If LINE_TYPE = LINE and you are passing a dummy line for either a tax-only or freight-only line, AutoInvoice ignores
what you enter here.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the unit of measure from the transaction you
are crediting.
Validation
Must exist in MTL_UNITS_OF_MEASURE.UOM_CODE. If LINE_TYPE = CHARGES, then this column must be null.
Destination
RA_CUSTOMER_TRX_LINES_ALL.UOM_CODE
103
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
UOM_NAME
Enter the unit of measure name for this transaction.
If LINE_TYPE = LINE and the line has an item, you must enter a value either in this column or in the UOM_CODE
column. If this a freight-only line, a tax-only line, or a line with no item, this column is optional.
If LINE_TYPE = LINE and you are passing a dummy line for either a tax-only or freight-only line, AutoInvoice ignores
what you enter here.
If LINE_TYPE = TAX, CHARGES, or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the unit of measure from the transaction you
are crediting.
Validation
Must exist in MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE. If LINE_TYPE = CHARGES then this column must be null.
Destination
None.
UNIT_SELLING_PRICE
Enter the selling price per unit for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. If you do not enter a value
in this column, AutoInvoice uses the amount in RA_INTERFACE_LINES_ALL.AMOUNT as the amount/quantity for this
transaction.
If LINE_TYPE = LINE or you are passing header freight, and you are passing a dummy line for either a tax-only or
freight-only line, AutoInvoice ignores the value you enter here.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.UNIT_SELLING_PRICE
UNIT_STANDARD_PRICE
Enter the standard price per unit for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
104
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For credit memos, do not enter a value in this column. AutoInvoice uses the unit standard price from the transaction
you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.UNIT_STANDARD_PRICE
USER_DEFINED_FISC_CLASS
Enter the user-dened scal classication code for the transaction line.
Use the user-dened scal classication code to classify any tax requirement that you cannot dene using existing scal
classication types.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL
USSGL_TRANSACTION_CODE
Enter the transaction code for this transaction. If this transaction is linked to another transaction, you must enter the
same transaction code as the one to which it is linked. This column is optional.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.DEFAULT_USSGL_TRANSACTION_CODE
USSGL_TRANSACTION_CODE_CONTEXT
This column is not currently used by AutoInvoice.
Validation
None.
Destination
None.
105
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
VAT_TAX_ID
This column is used by AutoInvoice and should be left null. If you enter a value in TAX_CODE, AutoInvoice enters a
corresponding ID in this column.
For credit memos, AutoInvoice uses the VAT tax ID of the transaction you are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.VAT_TAX_ID
WAREHOUSE_ID
This column identies the ship-from location and can be used to control taxation. Within the US, the Warehouse ID is
important when calculating state sales tax.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.WAREHOUSE_ID
WAYBILL_NUMBER
Enter the waybill number for this transaction.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter a value in this column.
For credit memos, do not enter a value in this column. AutoInvoice uses the waybill number from the transaction you
are crediting.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.WAYBILL_NUMBER
106
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
the Require salesperson Receivables system option and the Allow sales credits option on the transaction source
determine whether you must enter sales credit information.
If you are importing invoices, debit memos, and on-account credits, and the Require salesperson Receivables system
option is enabled, you must enter sales credit information, regardless of the seing of the Allow sales credits option on
the transaction source.
If you are importing credit memos and the Require salesperson Receivables system option is enabled, entering sales
credit information is optional. If you don't provide sales credit information on the credit memo, AutoInvoice uses the
sales credit information of the invoice it is crediting. If the invoice it is crediting doesn't have sales credit information,
AutoInvoice creates a 100% No Sales Credit line for this invoice. This sales credit line is then used to determine the sales
credit amount for the credit memo.
Regardless of the type of transaction you are importing, if the Require salesperson Receivables system option is not
enabled, but the Allow sales credits option on the transaction source is enabled, you can optionally provide sales
credit information. AutoInvoice validates and passes this information with the transaction. If the Require salesperson
Receivables system option is not enabled and the Allow sales credits option on the transaction source is not enabled,
AutoInvoice ignores any values that you pass.
ATTRIBUTE1-15
Enter the Descriptive Flexeld aribute information for this sales or revenue credit assignment. Descriptive Flexeld
aributes allow you to store additional columns, the contents of which you dene. These columns are optional.
Validation
None.
Destination
RA_CUST_TRX_LINES_SALESREPS_ALL.ATTRIBUTE1-15
ATTRIBUTE_CATEGORY
Enter the Descriptive Flexeld category information for this sales credit assignment. Descriptive Flexeld categories
allow you to store dierent categories of aributes. This column is optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.ATTRIBUTE_CATEGORY
INTERFACE_LINE_ATTRIBUTE1-15
Enter the same Transaction Flexeld for the transaction with which you want to associate this sales or revenue credit
assignment. The values you enter here provide you with an audit trail from Receivables back to your original system.
You must enter a value for each aribute you enabled.
107
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
INTERFACE_LINE_CONTEXT
Enter the context name of the Transaction Flexeld data that you entered in
RA_INTERFACE_SALESCREDITS_ALL.INTERFACE_LINE_ATTRIBUTE1-15. You must enter a value in this column.
Validation
None.
Destination
None.
INTERFACE_LINE_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using
RA_INTERFACE_SALESCREDITS_ALL.INTERFACE_LINE_ATTRIBUTE1-15.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.CUSTOMER_TRX_LINE_ID
INTERFACE_SALESCREDIT_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using the
sequence RA_CUST_TRX_LINE_SALESREPS_S.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.CUST_TRX_LINE_SALESREP_ID
INTERFACE_STATUS
This column is used by AutoInvoice and should be left null.
Validation
None.
108
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
LAST_UPDATE_LOGIN
This column is used by AutoInvoice and should be left null. AutoInvoice updates this column when it selects rows from
the RA_INTERFACE_SALESCREDITS_ALL table for processing.
Validation
None.
Destination
None.
REQUEST_ID
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
None.
SALES_CREDIT_AMOUNT_SPLIT
Enter the sales credit amount for this salesperson. This column is optional. Depending on the seing of the Sales
Credit option (Amount or Percent) in the Import Information section of the transaction source, you must enter either an
amount in this column or a percentage in the SALES_CREDIT_PERCENT_SPLIT column. If you specied Percent in the
transaction source, AutoInvoice calculates an amount for this column.
Validation
If the sales credit type is Quota, the sum of sales credit amounts for a transaction must equal the amount of the
transaction.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.REVENUE_AMOUNT_SPLIT, if the sales credit type is Quota.
RA_CUST_TRX_LINE_SALESREPS_ALL.NON_REVENUE_AMOUNT_SPLIT, if the sales credit type is not Quota.
SALES_CREDIT_PERCENT_SPLIT
Enter the sales credit percentage for this salesperson. This column is optional. Depending on the seing of the Sales
Credit option (Amount or Percent) in the Import Information section of the transaction source, you must enter either a
109
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
percentage in this column or an amount in the SALES_CREDIT_PERCENT_SPLIT column. If you specied Amount in the
transaction source, AutoInvoice calculates a percentage for this column.
Validation
Your sales or revenue credit percentage must be between 0 and 100. If the sales credit type is Quota, the sales credit
percentage for a transaction must add up to 100.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.REVENUE_AMOUNT_SPLIT, if the sales credit type is Quota.
RA_CUST_TRX_LINE_SALESREPS_ALL.NON_REVENUE_AMOUNT_SPLIT, if the sales credit type is not Quota.
SALES_CREDIT_TYPE_ID
Enter the ID of the sales credit type for this sales credit assignment. This column is optional. Depending on the
seing of the Sales Credit Type option (Value or ID) in the Import Information section of the transaction source, you
must enter a value either in this column or in the SALES_CREDIT_TYPE_NAME column. If you specied Value in the
transaction source, AutoInvoice enters a corresponding ID in this column.
Validation
Must exist in SO_SALES_CREDIT_TYPES.SALES_CREDIT_TYPE_ID.
Destination
None.
SALES_CREDIT_TYPE_NAME
Enter the name of the sales credit type for this sales credit assignment. This column is optional. Depending on the
seing of the Sales Credit Type option (Value or ID) in the Import Information section of the transaction source, you
must enter a value either in this column or in the SALES_CREDIT_TYPE_ID column.
Validation
Must exist in SO_SALES_CREDIT_TYPES.NAME.
Destination
None.
SALES_GROUP_ID
Enter the sales organization ID for this sales credit assignment. This column is optional.
Validation
Must exist in JTF_RS_GROUP_USAGES.GROUP_ID and have JTF_RS_GROUP_USAGES.USAGE = SALES.
110
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.REVENUE_SAL ESGROUP_ID or
RA_CUST_TRX_LINE_SALESREPS_ALL.NON_REVENUE_SALESGROUP_ID.
SALESREP_ID
Enter the salesperson ID for this sales credit assignment. This column is optional. Depending on the seing of the
Salesperson option (Number or ID) in the Import Information section of the transaction source, you must enter a
value either in this column or in the SALESREP_NUMBER column. If you specied Number in the transaction source,
AutoInvoice enters a corresponding ID in this column.
Validation
Must exist in RA_SALESREPS.SALESREP_ID.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.SALESREP_ID
SALESREP_NUMBER
Enter the salesperson number for this sales credit assignment. This column is optional. Depending on the seing of the
Salesperson option (Number or ID) in the Import Information section of the transaction source, you must enter a value
either in this column or in the SALESREP_ID column.
Validation
Must exist in RA_SALESREPS.SALESREP_NUMBER.
Destination
None.
If your accounting distributions are for transactions that use revenue scheduling rules, you can only enter percentages.
If you enter amounts, AutoInvoice ignores these values.
If your accounting distributions are for transactions that don't use revenue scheduling rules, you can enter either
percentages or amounts, depending on the value you entered for your transaction source:
• If you enter an amount, AutoInvoice requires that the distribution amounts add up to the amount of the
transaction.
111
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• If you enter a percentage, AutoInvoice requires that the distribution percentages add up to 100 for each
account class that you pass.
ACCOUNT_CLASS
Enter the account class for this accounting distribution. AutoInvoice uses the account class you enter here to determine
the type of account you are supplying for this accounting distribution. You must enter a value for this column.
Validation
Valid values are REV, FREIGHT, TAX, REC, CHARGES, UNBILL, and UNEARN. If the transaction uses the In Advance
invoicing rule, do not enter UNBILL in this column. If the transaction uses the In Arrears invoicing rule, do not enter
UNEARN in this column.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.ACCOUNT_CLASS
ACCTD_AMOUNT
This column is optional. If you selected Amount as the Revenue Account Allocation option on the transaction source,
then AutoInvoice accepts whatever is passed in this column without validation. If this column is null, then AutoInvoice
computes the accounted amount for this distribution line. For imported amounts in the ledger currency, AutoInvoice
rejects the line if you enter a value in the ACCTD_AMOUNT column that doesn't equal the line amount.
Validation
None.
Destination
None.
AMOUNT
Enter the amount for this accounting distribution.
If this accounting distribution is for a transaction that doesn't use a revenue scheduling rule, you must enter a value
either in this column or in the PERCENT column, depending on the value you entered for the Revenue Account
Allocation option on the transaction source. If you specify Percent, AutoInvoice computes the amount in this column.
112
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If this line has AMOUNT_INCLUDES_TAX set to Yes, the sales credits and line amounts for this column must include tax.
Validation
If this transaction doesn't use a revenue scheduling rule, the sum of all distribution amounts for this transaction of a
given line type must equal the amount of the transaction. AutoInvoice corrects amounts that have incorrect currency
precision.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.AMOUNT
ATTRIBUTE1-15
Enter the Descriptive Flexeld aribute information for this accounting distribution. Descriptive Flexeld aributes allow
you to store additional columns, the contents of which you dene. These columns are optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.ATTRIBUTE1-15
ATTRIBUTE_CATEGORY
Enter the Descriptive Flexeld category information for this accounting distribution. Descriptive Flexeld categories
allow you to store dierent categories of aributes. This column is optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.ATTRIBUTE_CATEGORY
CODE_COMBINATION_ID
Enter the code combination ID of the Accounting Flexeld for this accounting distribution.
This column is optional. Depending on the value you selected for the Accounting Flexeld option on the transaction
source, you must either enter a value in this column or enter a combination of segment values in the SEGMENT1-30
column. If you selected Segment on the transaction source, AutoInvoice enters a corresponding ID in this column.
Validation
Must exist in GL_CODE_COMBINATIONS.CODE_COMBINATION_ID.
113
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.COLLECTED_TAX_CCID, if tax is deferred; otherwise,
RA_CUST_TRX_LINE_GL_DIST_ALL.CODE_COMBINATION_ID.
COMMENTS
Enter comments about this accounting distribution. This column is optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.COMMENTS
INTERFACE_DISTRIBUTION_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using the
sequence RA_CUST_TRX_LINE_GL_DIST_S. This is the primary key for RA_INTERFACE_DISTRIBUTIONS_ALL.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.CUST_TRX_LINE_GL_DIST_ID
INTERFACE_LINE_ATTRIBUTE1-15
Enter the same Line Transaction Flexeld for the transaction with which you want to associate this accounting
distribution. You must enter a value for each aribute you enabled for the Line Transaction Flexeld.
Validation
None.
Destination
None.
INTERFACE_LINE_CONTEXT
This is a required column in AutoInvoice. Enter the context of the Line Transaction Flexeld entered in the
INTERFACE_LINE_ATTRIBUTE1-15 column.
114
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
If you pass lines with global context, set this column to Global Data Elements.
Destination
RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_CONTEXT
INTERFACE_LINE_ID
This column is used by AutoInvoice and should be left null. AutoInvoice enters a value in this column using
INTERFACE_LINE_ATTRIBUTE1-15 and INTERFACE_LINE_CONTEXT.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.CUSTOMER_TRX_LINE_ID
INTERFACE_STATUS
This column is used by AutoInvoice and should be left null.
Validation
None.
Destination
None.
INTERIM_TAX_CCID
This column identies the tax account used for deferred tax amounts.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.CODE_COMBINATION_ID
INTERIM_TAX_SEGMENT1-30
Enter an Accounting Flexeld value for each segment you enable in Receivables. This exeld represents the Interim
(deferred) tax account. For example, if you enable six Accounting Flexeld segments, you must enter six values in
columns SEGMENT1-6. Be sure to enter the correct segment value. For example, the value 01 is not the same as 1.
115
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Depending on the value you selected for the Accounting Flexeld option on the transaction source, you must either
enter a combination of segment values here or enter a value in the CODE_COMBINATION_ID column.
Validation
Valid combination of Accounting Flexeld segment values must exist in GL_CODE_COMBINATIONS.
Destination
None.
LAST_UPDATE_LOGIN
This column is used by AutoInvoice and should be left null. AutoInvoice updates this column when it selects rows from
the RA_INTERFACE_DISTRIBUTIONS_ALL table for processing.
Validation
None.
Destination
None.
PERCENT
Enter the percent for this accounting distribution.
If this accounting distribution is for a transaction that doesn't use a revenue scheduling rule, you must enter a value
either in this column or in the AMOUNT column, depending on the value you entered for the Revenue Account
Allocation option on the transaction source. If you specied Amount, AutoInvoice computes the percentage in this
column.
If this accounting distribution is for a transaction that uses a revenue scheduling rule, you must enter a value in this
column.
Validation
The sum of all accounting distribution percentages for a transaction must add up to 100 for an account class.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.PERCENT
REQUEST_ID
This column is used by AutoInvoice and should be left null.
Validation
None.
116
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
SEGMENT1-30
Enter an Accounting Flexeld value for each segment you enable in Receivables. For example, if you enable six
Accounting Flexeld segments, you must enter six values in columns SEGMENT1-6. Be sure to enter the correct
segment value. For example, the value 01 is not the same as 1.
Depending on the value you selected for the Accounting Flexeld option on the transaction source, you must either
enter a combination of segment values here or enter a value in the CODE_COMBINATION_ID column.
Validation
Valid combination of Accounting Flexeld segment values must exist in GL_CODE_COMBINATIONS.
Destination
None.
CONTINGENCY_ID
Identies the revenue contingency, according to this table:
Explicit Acceptance 2
Customer Creditworthiness 3
Doubtful Collectibility 4
Cancellation 7
Refund 9
117
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Forfeitures 10
Impaired Loans 13
Validation
None.
Destination
AR_LINE_CONTS_ALL.CONTINGENCY_ID
EXPIRATION_DATE
Indicates the expiration date of the contingency. For time-based contingencies, enter either the expiration date or
expiration days.
Validation
None.
Destination
AR_LINE_CONTS_ALL.CONTINGENCY_CODE
EXPIRATION_DAYS
Indicates the expiration period of the contingency. For time-based contingencies, enter either the expiration date or
expiration days.
Validation
None.
Destination
AR_LINE_CONTS_ALL.CONTINGENCY_CODE
EXPIRATION_EVENT_DATE
Indicates the expiration of the contingency removal event.
118
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Validation
None.
Destination
AR_LINE_CONTS_ALL.EXPIRATION_EVENT_DATE
INTERFACE_CONTINGENCY_ID
Contingency identier.
Validation
None.
Destination
None.
PARENT_LINE_ID
Identies the original parent order line from Distributed Order Orchestration. Child transaction lines inherit
contingencies from the parent line. You can't update the contingencies on the child transaction lines.
Validation
None.
Destination
None.
INTERFACE_LINE_ID
If both INTERFACE_SALESCREDIT_ID and INTERFACE_DISTRIBUTION_ID are null, then the row in
RA_INTERFACE_LINES_ALL associated with this INTERFACE_LINE_ID failed validation.
Validation
None.
119
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
INTERFACE_SALESCREDIT_ID
If this column is not null, then the row in RA_INTERFACE_SALESCREDITS_ALL associated with this
INTERFACE_SALESCREDIT_ID failed validation.
Validation
None.
Destination
None.
INTERFACE_DISTRIBUTION_ID
If this column is not null, then the row in RA_INTERFACE_DISTRIBUTIONS_ALL associated with this
INTERFACE_DISTRIBUTION_ID failed validation.
Validation
None.
Destination
None.
INVALID_VALUE
The invalid value that failed validation displays in this column, if applicable.
Validation
None.
Destination
None.
LINK_TO_LINE_ID
This column displays the INTERFACE_LINE_ID of the line to which this line that failed validation is linked. For
example, you have a tax line that fails and is linked to an invoice line that fails. In this case, the column stores the
INTERFACE_LINE_ID of the invoice line.
Validation
None.
120
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Destination
None.
MESSAGE_TEXT
The message text is stored in this column.
Validation
None.
Destination
None.
The program deletes both processed records and unprocessed records for the applicable business units:
• Processed records include all records from the interface tables that were validated and successfully imported as
transactions into Receivables. These records have a status of P.
• Unprocessed records include all records that were not successfully transferred to Receivables. Unprocessed
records either have no status, or the status of E, for transaction lines that ended in error and were not
transferred to Receivables.
121
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Present Bill
Print Transactions
Print Receivables Transactions
Use the Print Receivables Transactions process to submit your invoices, credit memos, debit memos, chargebacks, and
balance forward bills for printing. You can print all available transactions, a range of transactions, or new transactions
only.
Business Intelligence (BI) Publisher provides a predened print template for each Receivables transaction class: invoice,
credit memo, debit memo, chargeback, and balance forward bills. By default the Print Receivables Transactions process
uses these predened templates to print transactions. You can create your own versions of these print templates using
the available editing features in BI Publisher.
During a run of the Print Receivables Transactions process, these behaviors apply to transaction aachments:
• If the feature is enabled, a copy of the printed transaction is added to the transaction header as an aachment.
Use the Review Transaction page to view this printed copy.
• If the feature is enabled, aachments to the transaction header can be printed along with the transaction.
Note: You print bills receivable transactions with the Print Bills Receivable process.
The following list describes important parameters of the Print Receivables Transactions process.
Selected Parameters
Business Unit
Print transactions belonging to either a single business unit or all business units.
Transactions to Print
• Printed: Prints only those transactions that have already been printed.
• Unprinted: Prints only those transactions that have never been printed.
• All: Prints both printed and unprinted transactions.
Order By
122
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Customer
• Postal Code
Batch Name
Transaction Class
Print transactions belonging to the specied transaction class only: Invoice, Credit Memo, Debit Memo, Chargeback.
Transaction Type
Print transactions belonging to the specied transaction type only. If you entered a value in the Transaction Class
parameter, then the list of available transaction types is limited to this transaction class.
Customer Class
Print transactions belonging to customers with this classication only, for example, Commercial or Government.
Installment Number
For transactions with split payment terms, you can specify the installment number. To print all installments, do not
enter an installment number.
Print Date
Print transactions for the print date range you specify. The print date is the transaction date, unless you have specied
print lead days on the payment terms, in which case the print date is the number of lead days before the transaction
due date.
Specify whether to only print transactions with open debit items. The default is Yes.
Select the template to use to print transactions for each transaction class or the selected transaction class. The process
uses the default template unless you specify a template that you created.
Specify whether to print itemized tax information for each transaction line.
123
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Heading Description
Purchase Order The purchase order number from your customer for this transaction.
Sales Order The sales order number with which this transaction is associated.
Total The total of all line amounts, tax, and shipping charges for this transaction.
Financial Charges The total of all late and penalty charges applied to the transaction.
Send payment to The remit-to address, where your customers are to send payments against the transaction.
Extended Amount The total amount for an individual line item. This total is the quantity shipped times the unit
price.
Our Reference The number of the transaction that a credit memo credits. This value applies to credit memos
only.
Quantity Shipped The number of units that were shipped and billed for on this transaction.
Related Topics
• Print Bills Receivable Program and Report
124
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Print Transactions
When you run Print Receivables Transactions, the process prints or emails transactions to the designated customer
accounts and sites. Then an Upload Printed Receivables Transactions post process stores a copy of the printed
transaction as an aachment to the transaction.
If the Upload Printed Receivables Transactions post process fails to store copies of any delivered transactions, the next
run of Print Receivables Transactions aempts to store the copies of transactions that did not process successfully in
the previous run.
Note: You can't run the Upload Printed Receivables Transactions process from Scheduled Processes. This is
a post process of Print Receivables Transactions that only runs once you have properly enabled the storing of
printed transactions as aachments.
Use the Review Transaction page to open and review the printed document from the Aachments eld or Aachments
window. The Printed Transaction Copy aachment category is associated with each transaction stored as an
aachment.
Whenever you reprint a transaction, an additional reprinted transaction copy is stored as an aachment. Use the
Aachments window to review the date of each printed aachment.
Related Topics
• Overview of Lookups
• Example of a Standard Lookup
125
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
◦ Enabled: Yes
◦ Start Date: Date this lookup code is active.
◦ Meaning: User-dened explanation of the lookup code/aachment category.
◦ Description: Optional description of the lookup code/aachment category.
• Generate Bill: Set the Generate Bill option to Yes for all transactions that you want to print with their PDF
aachments.
126
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
A run of the Print Receivables Transactions process will print the four invoices with the following aachments:
• Invoice 1000 with Aachment A
• Invoice 1001 with Aachment C
• Invoice 1002 with no aachment
• Invoice 1003 with no aachment
Related Topics
• Aachments
• Overview of Lookups
127
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Note: You can't update transactions that are included on a balance forward bill, regardless of the seing of
the Allow Change to Printed Transactions Receivables system option. Receivables considers inclusion on
a balance forward bill to be a transaction activity, and therefore you can't update a transaction once it has
activity against it.
Related Topics
• What's a balance forward billing cycle
128
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If the billing cycle of the balance forward bill is External (derived from imported transactions), then you must enter a
billing date. The program includes on the bill only those transactions with a billing date on or before the date you enter.
If you change the billing cycle for a customer or group of customers, transactions entered after the change inherit the
payment terms aached to the new billing cycle, but existing transactions retain the old payment terms. During the next
submission of the Create Balance Forward Bill program, existing transactions with no activity against them inherit the
new payment terms, billing date, and due date. Transactions with activity retain their existing payment terms, billing
date, and due date.
If the balance forward bill contains transactions that retain the old payment terms, this may cause an aging discrepancy.
This is because the transactions that don't inherit the new payment terms may have due dates dierent from the other
transactions on the bill. If necessary, you can run the program for one set of payment terms only within the selected
billing cycle.
The program checks payment terms belonging to the account prole for customers enabled for account-
level balance forward billing, and belonging to the site prole (or account prole if no payment terms are
specied at a site) for customers enabled for site-level balance forward billing.
Note: The Create Balance Forward Bill program doesn't select transactions from customers
who are related either by customer or account relationships.
129
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If the transaction has a billing date that is earlier than that of the balance forward bill, the program
includes the transaction if it has no activity.
5. Determine the opening balance of the balance forward bill:
◦ Use the ending balance of the previous billing period as the opening balance of the new bill.
◦ If this is the rst time balance forward billing runs, the opening balance is zero.
6. Calculate the ending balance of the balance forward bill. The calculation accounts for the previous balance, new
transactions, and any activity that occurred during the billing cycle.
Note: The Create Balance Forward Bill program generates a bill even if there is no activity in a billing cycle.
Such a balance forward bill displays the previous balance, zero current activity, and ending balance.
You create a balance forward bill in draft mode, and print and review the contents of the bill. After reviewing the bill:
• If the bill is correct and contains all of the intended transactions, you can either conrm the bill or print the bill
in nal mode.
• If the bill is missing transactions or contains unintended transactions, reject the bill and update the transactions
of the applicable customers.
Parameter Value
Monthly
Billing Cycle
Yes
Print Output
USD
Currency
130
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
These customer prole seings aect the creation of balance forward bills:
• Bill Level:
◦ Account: One balance forward bill is created for all customer sites that have balance forward billing
enabled belonging to this customer account.
◦ Site: A separate balance forward bill is created for each customer site that has balance forward billing
enabled belonging to the customer account.
• Payment Terms: The payment terms assigned to the customer prole must be balance forward billing
payment terms. The balance forward bill includes all transactions assigned these payment terms.
• Override Terms: This options determines whether transactions belonging to the customer or customer site can
use payment terms other than the one assigned to the prole.
1. Review the draft balance forward bill, and review the parameter values that you entered to conrm that they are
correct.
2. If the bill is not correct, run the Conrm Balance Forward Bill process to reject the draft bill.
3. Complete the process parameters as shown in this table:
Parameter Value
4. For each applicable customer account or customer site, conrm the prole seings for balance forward billing.
5. If the Override Terms option on the customer prole is set to Yes, then you can remove transactions from the
bill by assigning these transactions non-balance forward billing payment terms.
These transactions are excluded from the next run of the balance forward bill. Instead an individual document
is printed for each of these transactions.
6. If you want to include additional transactions on the bill, you can update the customer accounts and sites that
are enabled for balance forward billing.
You must assign the same balance forward billing payments terms to these additional accounts and sites.
7. After completing your updates, run the Create Balance Forward Bill process.
131
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Related Topics
• Balance Forward Billing on Customer Accounts and Sites
Related Topics
• Why did AutoInvoice create transactions with duplicate transaction numbers
• Why did AutoInvoice reject transactions
132
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Debit Memo
• Chargeback
• Bills Receivable
• Balance Forward Bill Summary
• Balance Forward Bill Details
You can create your own versions of these print templates using the available editing features in BI Publisher.
Recommendations for modifying a print template include:
• Update the logo on the template to reect your current organization logo.
• Add or remove aributes to and from the template according to your requirements.
• Set your template as the default template in BI Publisher.
The data models provide the source data that is displayed on printed transactions. You can't modify the data models.
You can use the View Print buon on the Review Transaction or View Transaction pages to preview the printed version
of the transaction. If you have not printed the transaction, the preview displays the transaction according to the default
template in BI Publisher. If you have printed the transaction, the preview displays the transaction using the last template
that you used to print the transaction.
For example, if the low and high values in a range are 99 and 100, then Receivables perceives 99 as higher than 100,
and cannot successfully determine a range to use. To resolve this issue, submit your searches in separate batches. For
example, if you are using low and high batch name values, then submit the report for batches 1-999, 1000-1999, and so
on.
133
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
134
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Related Topics
• Natural Application and Overapplication
• Receivables Activity Types
• Creates pending and approved adjustments based on your adjustment approval limits.
• Closes the appropriate items.
You can run the process in preview mode to review the proposed adjustments before updating your open items.
Use the Create Automatic Billing Adjustments process parameters to manage the adjustment of specic sets of
transactions, for example, by remaining amount, due date, transaction type, customer name, or customer account
number.
If you enter a remaining amount or percentage range that exceeds your adjustment approval limits, the Create
Automatic Billing Adjustments process creates these adjustments with a status of Pending Approval. You can refer
these adjustments for approval to an approver with the appropriate limits.
If the remaining amount or percentage range is within your adjustment approval limits, the process automatically
approves these adjustments.
• Approve an adjustment
• Reject an adjustment
• Reverse an adjustment
• Request more information about an adjustment
• Edit an adjustment
• Withdraw an adjustment
Use the Approve Adjustments page or the Adjustments section of the Billing work area to review and update pending
adjustments.
If an adjustment is in the Waiting Approval status, you can approve, reject, or request information. If you approve or
reject the adjustment, this updates the customer account balances accordingly. You can only post adjustments that
have the status Approved or Rejected.
135
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If you need to reverse an approved adjustment, for example, an adjustment approved in error, create a new adjustment
with the same information and amount with the opposite sign to the previous adjustment amount.
You cannot perform any further action on an adjustment with the status Rejected. If necessary, create a new adjustment
to replace the rejected adjustment.
There are two actions that set an adjustment to the status More Research:
• Use the Request Information action to request information about an adjustment before deciding whether to
approve or reject.
• Use the Withdraw action to withdraw an adjustment in the status Waiting Approval that you previously
submied for approval.
You can edit all of the information in an adjustment record that is in the status More Research. This is the only status
that allows edits to all elds.
Credit Memos
Revenue Reversal Rules on Credit Memos
If you are crediting a transaction that uses invoicing and revenue scheduling rules, you must select a revenue reversal
rule.
The revenue reversal rule determines how to manage the reversal of revenue that was recognized when the credited
transaction was created.
• LIFO (Last In First Out): This rule reverses revenue starting with the most recent accounting period, and then
reverses revenue in all prior periods until the credit memo is nished.
• Prorate: This rule reverses revenue by crediting an equal percentage to all account assignments for the
transaction.
• Unit: This rule reverses revenue on the number of units that you specify on a transaction line.
If you select Unit, you must enter a last period to credit, a quantity to credit, and an adjusted unit price on each
applicable line. You cannot enter a credit quantity that is greater than the quantity on the target transaction
line.
• FIFO (First in First Out): This method reduces the remaining balance starting from the rst installment.
136
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• LIFO (Last In First Out): This method reduces the remaining balance starting from the last, or most recent,
installment.
• Prorate: This method credits the installments and prorates them based on the amount remaining for each
installment.
This method uses the formula: Total Credit Amount * (Remaining Line Balance/Total Remaining Balance).
Caution: If the revenue of the credit memo was previously adjusted using the Manage Revenue Adjustments
pages, don't adjust sales credits on the Credit Lines page. You must use the Manage Revenue Adjustments
pages to make any sales credit adjustments.
If you click No, Receivables does not run AutoAccounting, but does save your updates to sales credit information.
Related Topics
• Sales Credits and AutoAccounting
137
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The approver uses the notication window to review the credit request details, review and update credit request
information, and sign o on the review by clicking the Complete buon and sending the review to the next approver.
The approver uses the Review Credit Memo Request page, available from the notication window, to review transaction
and dispute information, update details of the credit request, and enter comments related to the review.
The notication window for the manual credit memo request contains this information:
• Customer account or site.
• Request details, including the original transaction, rebill information, adjustments, and receipts.
• Dispute details, including the dispute amount and dispute reason.
• Approval history.
• Link to the Review Credit Memo Request page.
Use the Review Credit Memo Request page to perform these activities:
• Review the credit request information.
• Review the transaction dispute details and amounts, and the disputed transaction lines (if applicable).
• Use the View Transaction Activities buon to review transaction activities for the original transaction under
dispute.
• Use the Rebill Details section to review and update rebill information:
◦ Rebill Number eld: Enter one or more transaction numbers, separated by commas, to identify the
transaction or transactions to rebill the customer in place of the original disputed transaction.
◦ Rebill Group eld: Select the product under which the rebill takes place.
• View comments from the customer in the Customer eld.
• Enter approver comments in the Internal Comments eld.
Note: The predened template is used by default to present the workow notication. You can use Oracle
BI Publisher to copy and modify this template according to your business requirements and set the modied
template as the new default.
Manage Disputes
Use the Manage Disputes page to enter a customer dispute for all or part of the transaction amount. After you enter
the details of the dispute, use the elds in the Dispute Summary section to record customer comments and your own
internal comments.
138
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
6. In the Dispute Detail section, enter the values that the customer wants to dispute in the Quantity and Amount
elds.
7. In the Dispute Summary section, enter in the Customer Comments eld any information from the customer
related to the dispute.
8. In the Internal Comments eld, enter any information from your internal reviews related to the customer or to
the dispute.
9. Click the Submit buon to submit the dispute to the credit memo approval process.
The customer and internal comments are included for review in each node of the approval process. Approvers
may add to these comments during the dispute review.
After credit memo approval, the customer comments related to the dispute are available for review in the credit memo
created by the dispute.
In addition, during the collections process the Collections agent may enter notes related to transactions under dispute
or to collections activity on specic transaction installments.
139
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Note: If the original dispute was created with the Reverse applications and credit open balance option
enabled to initiate the Credit Memo Rebill process, then that process takes precedence and the unapplication
of receipts process doesn't apply.
To set up credit memo approval to unapply receipts and apply the credit memo:
1. Create a credit memo transaction source with these seings:
◦ Type: Manual
◦ Receipt Handling for Credits: On account
Note: You can also assign these seings to the predened transaction source Credit Memo.
2. In the transaction source assigned to the invoice, select the credit memo transaction source you created, or the
predened transaction source Credit Memo, in the Credit Transaction Source eld.
3. In the transaction source assigned to the invoice, select the transaction type to use in the Standard
Transaction Type eld.
Note: The transaction type you select must have the Natural Application Only option enabled.
You can't use overapplication with credit memo approvals that require the unapplication of receipts.
You can use the receipt history to review a receipt's unapplication and reapplication on the invoice and the credit
request details.
You can directly update account assignments that haven't posted. If you update an account assignment that has
already posted, Receivables doesn't change the original assignment but instead creates two new account assignments:
• The rst assignment osets the original posted account assignment.
• The second assignment records the new amount or account that you have updated.
140
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Invoice Accounting Used for Credit Memos prole option: If this prole option is set to Yes, credit memo
accounting is derived from the accounting of the invoice being credited.
• Standard credit memo or on-account credit memo: On-account credit memos depend on AutoAccounting to
derive account assignments. Standard credit memos depend on AutoAccounting and the seing of the Invoice
Accounting Used for Credit Memos prole option.
• Credit memo revenue reversal rule: This rule aects account assignments on standard credit memos with
revenue scheduling rules.
If this is an on-account credit memo, the default amount is the credit memo line amount, where AutoAccounting for the
revenue account doesn't depend on salesperson. If AutoAccounting does depend on salesperson, Receivables creates
multiple account assignment lines, with one line for each salesperson equal to the amount of the salesperson line.
If this is a standard credit memo against a transaction, then the default amount depends on the seing of the Invoice
Accounting Used for Credit Memos prole option:
• If the Invoice Accounting Used for Credit Memos prole option is set to No, the default amount is calculated
using AutoAccounting in the same manner as on-account credit memos.
• If the Invoice Accounting Used for Credit Memos prole option is set to Yes, and the transaction doesn't use
a revenue scheduling rule, the default amount is an amount from the corresponding invoice distribution line
using the formula: Amount = (Credit Memo Line Amount/Invoice Line Amount) * Invoice Account Assignment
Amount.
• If the Invoice Accounting Used for Credit Memos prole option is set to Yes, and the transaction uses a
revenue scheduling rule, the default amount is calculated according to the seing of the credit memo revenue
reversal rule.
Note: You must run Revenue Recognition before you can review and update distributions on
credited transactions with revenue scheduling rules.
Examples of Accounting for Credit Memos Against Invoices with the In Advance
Invoicing Rule
These examples illustrate the accounting for full and partial credit memos against an invoice that uses the In Advance
invoicing rule.
On 1/1/XX invoice 102 is created with these details:
• Invoice Number = 102
• Invoice Date = 1/1/XX
• Invoice Amount = $100
• Duration = 5 months
• Invoicing Rule = In Advance
• Revenue Scheduling Rule = Fixed Amount, with these details:
◦ Period 1 = $20
◦ Period 2 = $20
◦ Period 3 = $10
141
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
◦ Period 4 = $30
◦ Period 5 = $20
This table shows the accounting entries for invoice 102 over the ve accounting periods:
142
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the reverse accounting entries after the credit memo is applied:
143
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the partial reverse accounting entries after the credit memo is applied, with the computations used to
derive the partial amounts:
144
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the partial and full reverse accounting entries after the credit memo is applied:
Receivables derives the Amount to Credit in each period by multiplying the Net Unit Price for each period by the number
of units to credit (8 in this example). Receivables derives the Net Unit Price by the following formula:
Net Unit Price = (Invoice Amount in this period - any previous credit memos in this period) / Original invoice
quantity
This table shows the Net Unit Price for each period:
145
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the Amount to Credit (Net Unit Price * Units to Credit) in each period as a result of the calculations of
the net unit price in the previous table:
Period 3 $1 * 8 units $8
This table shows the partial reverse accounting entries after the credit memo is applied:
146
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Examples of Accounting for Credit Memos Against Invoices with the In Arrears
Invoicing Rule
These examples illustrate the accounting for full and partial credit memos against an invoice that uses the In Arrears
invoicing rule.
On 1/1/XX invoice 103 is created with these details:
• Invoice Number = 103
• Invoice Date = 1/1/XX
• Invoice Amount = $100
• Duration = 5 months
• Invoicing Rule = In Arrears
• Revenue Scheduling Rule = Fixed Amount, with these details:
◦ Period 1 = $20
◦ Period 2 = $20
◦ Period 3 = $10
◦ Period 4 = $30
◦ Period 5 = $20
This table shows the accounting entries for invoice 103 over the ve accounting periods:
147
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the reverse accounting entries after the credit memo is applied:
148
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
149
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the partial reverse accounting entries after the credit memo is applied, with the computations used to
derive the partial amounts:
150
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This table shows the partial and full reverse accounting entries after the credit memo is applied:
151
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Receivables derives the Amount to Credit in each period by multiplying the Net Unit Price for each period by the number
of units to credit (8 in this example). Receivables derives the Net Unit Price by the following formula:
Net Unit Price = (Invoice Amount in this period - any previous credit memos in this period) / Original invoice
quantity
This table shows the Net Unit Price for each period:
This table shows the Amount to Credit (Net Unit Price * Units to Credit) in each period as a result of the calculations of
the net unit price in the previous table:
This table shows the partial reverse accounting entries after the credit memo is applied:
152
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
2/1/XX $50
3/1/XX $25
4/1/XX $25
153
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
• Scenario 1:
◦ A partial credit memo entered against the invoice with the split term method set to Prorate.
◦ A partial payment entered against the invoice.
◦ Another partial credit memo entered against the invoice.
• Scenario 2:
◦ A partial credit memo entered against the invoice with the split term method set to LIFO.
◦ A partial payment entered against the invoice.
◦ Another partial credit memo entered against the invoice.
• Scenario 3:
◦ A partial credit memo entered against the invoice with the split term method set to FIFO.
◦ A partial payment entered against the invoice.
◦ Another partial credit memo entered against the invoice.
• A partial credit memo for $45 with the split term method set to Prorate.
• A partial payment of $20.
• Another partial credit memo for $20.
Transaction 1: On 1/1/XX a credit memo for $45 is entered against invoice 104. The details are:
To calculate the amount credited per payment schedule, Receivables uses the following formula:
Amount Credited = (Credit Memo Amount/Total Remaining Amount Due) * Amount Due Remaining on this installment
This table shows the calculations for the amount credited for each installment:
154
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
Transaction 2: On 1/15/XX a payment is received for $20. This payment aects the payment schedules of invoice 104, as
shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
Transaction 3: On 1/16/XX another credit memo for $20 is entered against invoice 104. The details are:
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
155
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
Note: The amounts in the Total Amount Credited column are derived from this formula: Total Amount
Credited per installment from Transaction 2 + (Credit Memo Amount/Total Remaining Amount Due from
Transaction 2 * Remaining Amount Due per installment from Transaction 2) The results are rounded to two
decimal places.
Transaction 1: On 1/1/XX a credit memo for $45 is entered against invoice 104. The details are:
• Split term method = LIFO
• Credit memo date = 1/1/XX
• Credit memo amount = $45
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
Transaction 2: On 1/15/XX a payment is received for $20. This payment aects the payment schedules of invoice 104, as
shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
156
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
Transaction 3: On 1/16/XX another credit memo for $20 is entered against invoice 104. The details are:
• Credit memo date = 1/16/XX
• Credit memo amount = $20
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
Transaction 1: On 1/1/XX a credit memo is entered against invoice 104. The details are:
• Split term method = FIFO
• Credit memo date = 1/1/XX
• Credit memo amount = $45
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
157
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
Transaction 2: On 1/15/XX a payment is received for $20. This payment aects the payment schedules of invoice 104, as
shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
Note: When the payment applied on 1/15/XX fully covered the amount due for the rst pay period, the
remainder of the payment is applied to the amount due for the following period.
Transaction 3: On 1/16/XX another credit memo for $20 is entered against invoice 104. The details are:
This credit memo aects the payment schedules of invoice 104, as shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
158
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Overview
The Adjustment Register provides information about approved adjustments that aect transaction balances.
Key Insights
Review both manual and automatic adjustments by customer, adjustment status, adjustment type, or adjustment
reason.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Period Close
Who uses this report? • Financial Specialist to review activity for the period.
• Financial Manager during period close processing.
When do I use this report? When you need a listing of adjustments against customer transactions or to assist the
receivables reconciliation process.
159
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
FAQ Answer
Adjustment Register
Use the Adjustment Register to review both manual and automatic approved adjustments that aect transaction
balances for the selected period.
This is a standalone report that you can use instead of the drill-down report associated with the Receivables to General
Ledger Reconciliation Report. You can optionally use this report to review unapproved and rejected adjustments, or
adjustments that require additional research.
Use the available report parameters to display adjustments by customer, adjustment status, adjustment type, or
adjustment reason.
Report Output
The report output displays adjustment information by business unit and adjustment type for a specied period. Totals
are displayed in the ledger currency.
This table shows the main column headings in the output of the Adjustment Register.
Customer Name and Account The name and account number of the customer, displayed for each applicable adjustment
Number type.
Adjustment Accounted Amount The accounted amount of the adjustment in the ledger currency.
160
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Overview
The AutoAdjustment Preview Report provides information about potential automatic transaction adjustments,
generated after a run of the Create Automatic Billing Adjustments program.
Key Insights
The report includes information about the customer, transaction, adjustment amount, and adjustment status, and
displays the total amount and count for both approved and pending adjustments.
161
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
How do I nd this report? Scheduled Processes - Create Automatic Billing Adjustments
Who uses this report? Financial Manager during period close processing.
When do I use this report? To preview potential transaction adjustments when writing o transaction balances using the
Create Automatic Billing Adjustments program.
The report includes, for each adjustment, information about the customer, transaction, adjustment amount, and
adjustment status. The report displays the total amount and count for both approved and pending adjustments.
Once you're satised with the adjustments that will be generated, you can run the Create Automatic Billing Adjustments
program again with the AutoAdjustments Option parameter set to Create Adjustments.
Report Output
This table describes the column headings in the output of the AutoAdjustment Preview Report. These column headings
are displayed for each adjustment type.
162
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Balance Due The remaining balance due on the transaction after the adjustment.
This table describes the row headings in the output of the AutoAdjustment Preview Report.
Total Approved Adjustments The total amount of approved adjustments for this run of the program.
Total Approved Adjustments Count The total number of approved adjustments for this run of the program.
Total Pending Adjustments The total amount of pending adjustments for this run of the program.
Total Pending Adjustments Count The total number of pending adjustments for this run of the program.
Report Parameters
Order By
Arrange the information in the report by Adjustment Number, Customer, Postal Code or Transaction Number.
163
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
164
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
There is no link between invoices and debit memos. You can use the Cross Reference eld or Special Instructions eld
on the debit memo to maintain reference information pertaining to the debit memo and the original transaction. Special
instructions information appears on the printed debit memo document.
If you want to use a dierent numbering sequence for debit memos, you must set up and use a dierent transaction
source.
If the approval process fails, a review of the related approval group and approval rules may indicate the source of the
problem. For example:
• Verify that the approval group is active in the worklist and dened correctly.
• Conrm the members of the approval group.
165
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Conrm that, for credit memo requests, the appropriate rules are dened in the worklist.
Review Installments
Use the Review Installments window to review the installments on transactions that have split payment terms. Each row
displays the due date, installment amount, and balance due.
If the AR: Update Due Date prole option is set to Yes, you can perform these actions on installments:
• Update the due date on an installment. If you update a due date, this recalculates the days late and due days for
the installment based on the new due date.
• Update the unpaid portion of an installment.
• Add or delete installments.
The Balance Details window displays the total amount of each action aecting a transaction in the Total column and
displays how the line, tax, freight, and charge balances were aected in the Balance row.
166
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Related Topics
• Split Payment Terms and Amounts Due
Receivables Tables
Receivables uses the following tables to store all accounts receivable transaction, receipt, and adjustment activity:
• RA_CUSTOMER_TRX
• RA_CUSTOMER_TRX_LINES
• RA_CUST_TRX_LINE_SALESREPS
• RA_CUST_TRX_LINE_GL_DIST
• AR_PAYMENT_SCHEDULES
• AR_ADJUSTMENTS
• AR_RECEIVABLE_APPLICATIONS
• AR_CREDIT_MEMO_AMOUNTS
• AR_CASH_RECEIPTS
• AR_CASH_RECEIPT_HISTORY
• AR_MISC_CASH_DISTRIBUTIONS
Each table stores information needed for one or more types of transactions, receipts, or adjustments. Each data
element is stored as a unique record, based on the primary key of the table.
The RA_CUSTOMER_TRX table stores invoice, debit memo, and credit memo header information. Each of these
transactions is stored as a unique record, based on the primary key customer_trx_id. The transaction number,
transaction date, and billing customer are stored in the trx_number, trx_date, and bill_to_customer_id columns
respectively.
Additional information stored in this table includes ship-to customer, document sequence number, currency, and a
transaction complete seing. The transaction type for the invoice is stored in the RA_CUST_TRX_TYPES table, but can
be referenced using the foreign key cust_trx_type_id.
167
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• LINE_TYPE column
• EXTENDED_AMOUNT column
The RA_CUSTOMER_TRX_LINES table stores invoice, debit memo, and credit memo line level information.
Each transaction line is stored as a unique record, based on the primary key customer_trx_line_id column. The
customer_trx_id column is a foreign key to the RA_CUSTOMER_TRX table.
The line_type column identies the type of data contained in the record. Valid line types are CHARGES, FREIGHT,
LINE, and TAX. Any record with a line type of TAX or FREIGHT refers to the original invoice line from the
link_to_cust_trx_line_id column, except for header freight transactions. The total amount for each transaction line is
stored in the EXTENDED_AMOUNT column.
The RA_CUST_TRX_LINE_SALESREPS table stores sales credit assignments for invoice lines. Each assignment is stored
as a unique record, based on the primary key cust_trx_line_salesrep_id. If you base your accounting distributions on
sales credits, the sales credit assignments in this table map to the RA_CUST_TRX_LINE_GL_DIST table. The sales_rep_id
column identies the salesperson receiving the credit for this transaction. The customer_trx_line_id column is a foreign
key to the RA_CUSTOMER_TRX_LINES table.
The revenue_amount_split column stores the amount of the invoice line assigned to this salesperson. The
non_revenue_amount_split column stores the amount of the non-header freight and tax lines assigned to this
salesperson. If the sales credits are derived based on a percentage of the transaction line rather than a specic amount,
the revenue_percent_split and non_revenue_percent_split columns store the percentages of the transaction lines
assigned to this salesperson. The prev_cust_trx_line_salesrep_id column references another sales credit assignment to
which the current record is being applied.
The RA_CUST_TRX_LINE_GL_DIST table stores the accounting distribution for invoice, debit memo, and credit memo
transactions. Each distribution is stored as a unique record, based on the primary key cust_trx_line_gl_dist_id. The
customer_trx_line_id column is a foreign key to the RA_CUSTOMER_TRX_LINES table.
The account_class column describes the account type, while the code_combination_id column identies the general
ledger account. Valid account classes are CHARGES, FREIGHT, REC, REV, SUSPENSE, TAX, UNBILL, and UNEARN.
The account_class REC represents the receivable account distribution. The amount column for REC records is equal
to the sum of all invoice lines. Therefore, there is no link to the RA_CUSTOMER_TRX_LINES table and the column
customer_trx_line_id is null for these records. The REC record is linked to the RA_CUSTOMER_TRX table from the
168
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
customer_trx_id column. For all other account classes, credits are represented by positive numbers and debits are
represented by negative numbers.
AR_PAYMENT_SCHEDULES table
Important columns in the AR_PAYMENT_SCHEDULES table include:
• PAYMENT_SCHEDULE_ID column
• AMOUNT_DUE_ORIGINAL column
• AMOUNT_DUE_REMAINING column
• CUSTOMER_TRX_ID column
• CASH_RECEIPT_ID column
• TRX_NUMBER column
• STATUS column
• AMOUNT_APPLIED column
• CLASS column
The AR_PAYMENT_SCHEDULES table stores customer balance information at the transaction level. Each transaction
balance is stored as a unique record, based on the primary key payment_schedule_id. The class column identies the
transaction type and determines which columns to update when a transaction is stored.
For billing transactions, the AR_PAYMENT_SCHEDULES table joins the RA_CUSTOMER_TRX table from
the customer_trx_id column and stores NULL in the cash_receipt_id column. For payment transactions, the
AR_PAYMENT_SCHEDULES table joins the AR_CASH_RECEIPTS table from the cash_receipt_id column and stores
NULL in the customer_trx_id column.
This table illustrates the tables updated for billing and payment transactions:
The status column identies whether the transaction is open or closed, while the trx_number column stores the
transaction number. The amount_applied column stores the sum of all transactions applied to the balance of the
selected transaction. The amount_due_original column equals either the sum of the EXTENDED_AMOUNT column
in the RA_CUSTOMER_TRX_LINES table for the given customer_trx_id or the sum of the amount column in the
AR_CASH_RECEIPTS table for the given cash_receipts_id. The amount_due_remaining column represents the balance
for the selected transaction.
169
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
For the amount_due_original and amount_due_remaining columns, debit items, such as invoices, are stored as positive
numbers, and credit items, such as credit memos and payments, are stored as negative numbers. The current customer
balance is reected by the sum of the amount_due_remaining column for all conrmed payment schedules for a given
customer.
AR_ADJUSTMENTS table
Important columns in the AR_ADJUSTMENTS table include:
• ADJUSTMENT_ID column
• AMOUNT column
• CUSTOMER_TRX_ID column
• TYPE column
• PAYMENT_SCHEDULE_ID column
• CODE_COMBINATION_ID column
The AR_ADJUSTMENTS table stores information about invoice adjustments. Each adjustment is stored as a unique
record, based on the primary key adjustment_id. The amount column stores the amount of the adjustment. Receivables
uses the customer_trx_id and payment_schedule_id to link the adjustment to the adjusted transaction and to update
the amount_due_remaining and amount_adjusted columns of the adjusted transaction payment schedule in the
AR_PAYMENT_SCHEDULES table.
The type column stores a description of the transaction to which the adjustment applies. Valid types include:
• Charges Adjustments
• Freight Adjustments
• Invoice Adjustments
• Line Adjustments
• Tax Adjustments
The code_combination_id column stores the accounting distribution associated with the adjustment transaction.
Receivables Applications
The Receivables tables that manage data for receipt and credit memo applications are:
• AR_RECEIVABLE_APPLICATIONS
• AR_CREDIT_MEMO_AMOUNTS
• AR_CASH_RECEIPTS
• AR_CASH_RECEIPT_HISTORY
• AR_MISC_CASH_DISTRIBUTIONS
170
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• APPLIED_PAYMENT_SCHEDULE_ID column
• APPLIED_CUSTOMER_TRX_ID column
The AR_RECEIVABLE_APPLICATIONS table stores account distributions for receipt and credit memo applications and
maps the application transaction to the applied transaction. Each accounting distribution is stored as a unique record,
based on the primary key receivable_application_id. The payment_schedule_id column links the receipt or credit memo
to its payment schedule in the AR_PAYMENT_SCHEDULES table. The cash_receipt_id column stores the receipt ID
of payment transactions, while the cust_trx_id column, which is not shown, stores the transaction ID for credit memo
transactions. The applied_payment_schedule_id and applied_customer_trx_id columns reference the transaction to
which this record applies.
The status column describes the state of the application transaction. For credit memos, the status is always APP to
identify the credit memo as applied. For receipt transactions, valid status values are APP, UNAPP, UNID, REV, NSF, and
STOP. The code_combination_id column stores the general ledger account for the application transaction, based on the
status. The amount_applied column stores the amount of the receipt or credit memo as a positive value.
The AR_CREDIT_MEMO_AMOUNTS table stores the accounting dates and amounts for credit memos to use when they
are applied to invoices with rules. Each credit memo application date is stored as a unique record, based on the primary
key credit_memo_amount_id. The customer_trx_line_id column references the transaction line to which a credit memo
applies. The gl_date column stores the date the credit memo is applied to the invoice, and the amount column stores
the amount to apply.
The AR_CASH_RECEIPTS table stores a unique record for each receipt, based on the primary key cash_receipt_id. The
status column describes the state of the receipt in relation to customer invoices and balances. Valid status values are:
• UNID: The receipt customer is unidentied, and no customer balance was updated.
• UNAPP: The receipt customer was identied, but the receipt has neither been fully applied to a specic invoice
nor placed on account.
• APP: The entire amount of the receipt was either placed on account or applied to specic customer invoices.
• REV: The receipt was reversed.
• NSF: The receipt was reversed due to insucient funds.
• STOP: The receipt was reversed by a stop payment.
The type column identies the receipt as either CASH or MISC to indicate whether the receipt is a customer payment or
a miscellaneous receipt (not related to a receivables activity). The amount column stores the net amount of the receipt,
while the receipt_number column stores the receipt number.
171
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The AR_CASH_RECEIPT_HISTORY table stores the current status and history of a receipt. Each status change is stored
as a unique transaction, based on the primary key cash_receipt_history_id. The status column describes which step of
the receipt life cycle the receipt has reached. Valid status values are:
• APPROVED: This status is only valid for automatic receipts, and indicates that the receipt was approved for
automatic creation. These record types are never postable.
• CONFIRMED: This status is only valid for automatic receipts, and indicates that the receipt was conrmed by
the customer.
• REMITTED: This status is valid for both manual and automatic receipts, and indicates that the receipt was
remied.
• CLEARED: This status is valid for both manual and automatic receipts, and indicates that the receipt was
cleared.
• REVERSED: This status is valid for both manual and automatic receipts, and indicates that the receipt was
reversed.
As the receipt moves through its life cycle, Receivables inserts a new record into the AR_CASH_RECEIPTS_HISTORY
table with the current_record_ag column set to Y. Receivables also updates the previous record related to this receipt,
by seing the current_record_ag to NULL and by seing the reversal_gl_date. The amount column stores the amount
of the receipt. The cash_receipts_id column links the AR_CASH_RECEIPTS_HISTORY table to the AR_CASH_RECEIPTS
table.
The AR_MISC_CASH_DISTRIBUTIONS table stores the accounting distribution for miscellaneous cash receipts. Each
distribution is stored as a unique record, based on the primary key misc_cash_distribution_id. The distributions are
linked to the receipt by the cash_receipt_id column. The code_combination_id column stores the general ledger account
assigned to this receipt.
Related Topics
• How Transaction Activities are Stored
• How Payment Activities are Stored
172
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
The following sections describe the default accounting entries created when you enter transactions in Receivables using
the Accrual method of accounting. There is a section for each activity:
• Invoices
• Credit Memos and On-Account Credits
• Receipts
• Remiances
• Adjustments
• Debit Memos
• Credit Card Refunds
Invoices
This section describes the default accounting entries for invoices.
When you enter a standard invoice, Receivables creates the following journal entry:
Debit Credit
Receivables None
None Revenue
If you enter an invoice with an In Arrears invoicing rule with a three-month xed duration revenue scheduling rule,
Receivables creates the following journal entries:
Debit Credit
None Revenue
Debit Credit
173
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
None Revenue
Debit Credit
None Revenue
Receivables None
If you enter an invoice with an In Advance invoicing rule, Receivables creates the following journal entries:
Debit Credit
Receivables None
None Revenue
174
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
None Revenue
When you credit an invoice, debit memo, or chargeback, Receivables creates the following journal entry:
Debit Credit
Revenue None
When you enter a credit memo against an installment, you choose one of the following split term methods: LIFO, FIFO,
Prorate. When you enter a credit memo against an invoice with invoicing and revenue scheduling rules, you choose one
of the following revenue reversal rules: LIFO, Prorate, Unit.
If the Invoice Accounting Used for Credit Memos prole option is set to Yes, Receivables credits the accounts of
the original transaction. If this prole option is set to No, Receivables uses AutoAccounting to determine the freight,
receivables, revenue, and tax accounts. Receivables uses the account information for on-account credits that you
specied in your AutoAccounting structure to create your journal entries.
You can update accounting information for your credit memo after it has posted to general ledger. Receivables keeps
the original accounting information as an audit trail while it creates an oseing entry and the new entry.
If you unapply the standard credit memo, Receivables reverses the accounting entries and creates the following journal
entry:
175
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
If the Invoice Accounting Used for Credit Memos prole option is set to No, then when you unapply the standard
credit memo you must enter a Receivable account.
This section describes the default accounting entries for on-account credits.
When you enter an on-account credit, Receivables creates the following journal entry:
Debit Credit
Receivables uses the freight, receivable, revenue, and tax accounts that you specied in your AutoAccounting structure
to create these entries.
Once the on-account credit is applied to an invoice, the following journal entry is created:
Debit Credit
Receipts
This section describes the default accounting entries for receipts.
When you enter a receipt, Receivables creates the following journal entries:
176
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
Cash None
None Receivables
When you fully apply a receipt to an invoice, Receivables creates the following journal entry:
Debit Credit
Cash None
None Receivables
Note: These examples assume that the receipt has a Remiance Method of No Remiance and a Clearance
Method of Directly.
When you enter an unidentied receipt, Receivables creates the following journal entry:
Debit Credit
Cash None
None Unidentied
When you enter an on-account receipt, Receivables creates the following journal entry:
Debit Credit
Cash None
None Unapplied
Unapplied None
None On-Account
177
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
When your receipt includes a discount, Receivables creates the following journal entry:
Debit Credit
Cash None
None Receivables
None Receivables
Receivables uses the default cash, unapplied, unidentied, on-account, unearned, and earned accounts that you
specied under remiance banks for this receipt class.
When you enter a receipt and combine it with an on-account credit (which increases the balance of the receipt),
Receivables creates the following journal entry:
Debit Credit
Cash None
To close the receivable on the credit memo and increase the unapplied cash balance, Receivables creates the following
journal entry:
Debit Credit
Receivables None
When you enter a receipt and combine it with a negative adjustment, Receivables creates the following journal entries:
178
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
Cash None
Write-O None
When you enter a receipt and combine it with a positive adjustment, Receivables creates the following journal entries:
Debit Credit
Cash None
None Write-O
When you write o the unapplied amount on a receipt, Receivables creates the following journal entries:
Debit Credit
None Write-O
When you enter a receipt and combine it with a chargeback, Receivables creates the following journal entries:
Debit Credit
Cash None
179
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
To move funds between receipts, you can apply one receipt to another open receipt. These journal entries illustrate
moving funds from Receipt 1 to Receipt 2:
Debit Credit
After this receipt-to-receipt application completes, Receipt 2 gains additional funds that you can then apply to a debit
item.
You set up a Payment Neing account when dening your receivables activity.
If both receipts are in a foreign currency, however, then you could have an exchange gain or loss when you net the
receipts. The exchange gain or loss is realized on the main receipt (Receipt 2) at the time of receipt application (neing).
If you later adjust the conversion rate on Receipt 1 or 2, the following actions are performed:
• Roll back all accounting for both receipts.
• Recreate the accounting, including the neing application, using the adjusted conversion rate.
• Recalculate the exchange gain or loss on whichever receipt gained the additional funds.
Remiances
This section describes the default accounting entries for remiances.
180
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
When you create a receipt that requires remiance to your bank, Receivables debits the Conrmation account instead
of Cash. An example of a receipt requiring remiance is a check before it is cashed. Receivables creates the following
journal entry when you enter such a receipt:
Debit Credit
Conrmation None
None Receivables
You can then remit the receipt to your remiance bank using one of the two remiance methods: Standard or
Factoring. If you remit your receipt using the standard method of remiance, Receivables creates the following journal
entry:
Debit Credit
Remiance None
None Conrmation
When you clear the receipt, Receivables creates the following journal entry:
Debit Credit
Cash None
None Remiance
If you remit your receipt using the factoring remiance method, Receivables creates the following journal entry:
Debit Credit
Factor None
None Conrmation
181
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
When you clear the receipt, Receivables creates a short-term liability for receipts that mature at a future date. The
factoring process lets you receive cash before the maturity date, and assumes that you are liable for the receipt amount
until the customer pays the balance on the maturity date. When you receive payment, Receivables creates the following
journal entry:
Debit Credit
Cash None
On the maturity date, Receivables reverses the short-term liability and creates the following journal entry:
Debit Credit
None Factor
Adjustments
This section describes the default accounting entries for adjustments.
When you enter a negative adjustment against an invoice, Receivables creates the following journal entry:
Debit Credit
Write-O None
When you enter a positive adjustment against an invoice, Receivables creates the following journal entry:
Debit Credit
None Write-O
182
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
Debit Credit
Debit Memos
This section describes the default accounting entries for debit memos.
When you enter a debit memo, Receivables creates the following journal entries:
Debit Credit
Receivables None
Receivables None
Note: Credit card services are currently not available in Oracle Cloud implementations.
When you unapply a receipt and reapply the receipt to a credit card refund, Receivables creates these journal entries:
Debit Credit
Receivables None
None Unapplied
Unapplied None
183
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
After you apply the receipt to a credit card refund, Receivables automatically creates a negative miscellaneous receipt in
the amount of the refund and creates this journal entry:
Debit Credit
None Cash
When you reverse a credit card refund, either by reversing the negative miscellaneous receipt or by unapplying the
credit card refund activity, Receivables creates this journal entry for the negative miscellaneous receipt:
Debit Credit
Cash None
Receivables creates this journal entry for the original payment receipt:
Debit Credit
None Unapplied
Related Topics
• Examples of Accounting Entries for Bills Receivable Activities
• Receivables Activity Types
• AutoAccounting Account Types and Segment Values
184
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
You receive an invoice payment for $3,000. The invoicing rule is In Advance, and the revenue scheduling rule is 3-
month xed duration. Over the course of three months, your accounting entries are as follows:
January
February
March
You receive an invoice payment for $3,000. The invoicing rule is In Arrears, and the revenue scheduling rule is 3-month
xed duration. Over the course of three months, your accounting entries are as follows:
January
185
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
February
March
186
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
You can use the Receivables Aging by General Ledger Account report and the Receivables to General Ledger
Reconciliation report to review intercompany transactions during reconciliation.
Related Topics
• Guidelines for Using the Receivables to General Ledger Reconciliation Report
• Intercompany Balancing Rules
187
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
• Time zone conversion applies to the application date, accounting date, and unapply accounting date on all
credit memos where the default date is the system date.
• Time zone conversion applies to the remiance batch date and accounting date on all remiance batches
where the default date is the system date.
• Time zone conversion applies to the conversion date and accounting date on all conversion rate updates where
the default date is the system date.
• Time zone is derived from the legal entity associated with the business unit of the receipt or receipt batch.
• If a receipt or receipt batch has both a legal entity derived from the business unit and a legal entity associated
with the remiance bank account, Receivables uses the legal entity derived from the business unit for time
zone conversion.
• These rules apply to standard receipts, miscellaneous receipts, manual and automatic receipt batches, lockbox
receipts, remiance batches, receipt reversals, refunds, on-account applications, credit memo write-os, and
updates to conversion rates.
Related Topics
• What legal entity is assigned to a receipt
Project invoices use the same tax conguration, as dened in Tax, as that used by Receivables. However, nal tax
calculation on Project invoices only takes place after transfer to Receivables. If there are any changes in the tax
conguration between invoice creation in Project and invoice transfer to Receivables, the nal tax calculation may dier
from the estimated calculation on the draft invoice.
Contract Invoices
You can create contract invoices without project information and transfer these invoices to Receivables. You can search
by contract number in Receivables to review these invoices after successful transfer.
188
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
If the Require salesperson Receivables system option is enabled, then you must provide sales credit information on
contract invoices before transfer to Receivables.
Receivables doesn't display accounting for contract invoices after AutoInvoice import. You can only view accounting
after invoices are transferred to subledger accounting.
Invoice Printing
You can print and review invoices in Project before transfer to Receivables. You can also transfer print templates created
in Project to Receivables for printing nal invoices.
Net Invoices
You can create net invoices in Project and transfer these invoices to Receivables. A net invoice combines new invoice
lines with existing credit memos into one invoice. Where applicable, you can use a net invoice to manage existing
credits instead of issuing separate credit memos for each credit item.
After transfer to Receivables, the credited lines appear as separate invoice lines on the invoice.
Note: The Receivables transaction type assigned to a Project net invoice must have a creation sign of Any
Sign, in order to accommodate positive and negative amounts.
189
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
190
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
You can apply all or part of a receipt or on-account credit memo to a single debit item or to several debit items.
For example, a customer may send a single check to pay all of one invoice and part of another invoice. The customer
may also have an on-account credit memo to use with the check to close an open debit item.
Review these guidelines for applying receipts and on-account credit memos to transactions:
• Credit Memo Search
• Transaction Balance for Applications Always Used Prole Option
• Receipt Application on Cross-Customer Transactions
• Foreign Currency Receipts
• On-Account Credit Memos
• Balance Forward Bills
191
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Pay Below: Each customer can pay for its own transactions, and the transactions of all customers that are lower
in the hierarchy (children, grandchildren, and so on).
Related Topics
• Customer Hierarchies and Paying Relationships
• Receipt Application using the Match Receipts By Rule
• Match Receipts By rule: The Match Receipts By rule identies the document type to use to match receipts to
transactions during lockbox and manual receipt processing. There are six document types available to match to
receipts:
◦ Transaction number
◦ Balance forward billing number
◦ Contract number
◦ Purchase order number
◦ Sales order number
◦ Shipping reference, such as a waybill number or packing slip
192
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
You can set Match Receipt By document references at the customer site, customer account, lockbox, and
Receivables system option level. Receivables searches these seings until it nds an exact match or an
approximate match.
• Document Reference Automatic Update: Use the Document reference automatic update for matched
receipts option at the customer site or customer account level to automatically maintain the Match Receipt
By rule. If Receivables matches and applies a receipt for a customer or customer site based on a document
reference dierent from the default seing (or if there was no default seing), this new document reference
becomes the Match Receipt By rule for that customer or site.
• AutoApply: Set the Use AutoApply option for a lockbox or at the Receivables system option level for
manual receipts. If you set this option, AutoApply automatically applies receipts and presents transaction
recommendations based on the AutoMatch rule set, and handles exceptions based on the application
exception rule set.
• AutoMatch Rule Set: The active AutoMatch rule set determines how receipts are applied automatically and
transactions recommended for manual application. You can assign an AutoMatch rule set at the customer site,
customer account, lockbox, and Receivables system option level.
An AutoMatch rule set denes the minimum qualifying percentage score, based on assigned thresholds,
necessary to recommend transactions for receipt application. The rule set also provides string handling
assistance to search for transaction matches against reference strings, such as an invoice number.
• Application Exception Rule Set: The active application exception rule set manages the handling of over and
under payments after receipt application.
For example, you enter an invoice number as the reference number, and the Match Receipt By rule for a customer
site is Transaction Number. Receivables looks for and displays the transactions that most closely match the number
you enter. If there is an exact match, and if the AutoMatch threshold seings allow, Receivables applies the receipt to
the transaction automatically. If there is not an exact match, Receivables displays a list of recommended transactions
according to the AutoMatch thresholds.
If AutoApply is enabled, Receivables presents transaction recommendations in the order of their reference score, as
calculated by the active AutoMatch rule set, such that the closest matches appear rst in the list. Each recommendation
is accompanied by a reason code explaining why the receipt wasn't applied to the transaction automatically. For
example, if a recommendation has the reason Below transaction threshold, this indicates that the receipt wasn't
automatically applied because the transaction reference score didn't meet the minimum threshold required for
automatic application.
When you submit a lockbox, the lockbox process can in many cases match receipts to transactions and apply the
receipts automatically. In cases where receipts are not applied automatically, lockbox generates a list of recommended
transactions for you to complete the receipt application process manually.
When you manually create a standard receipt, use the Submit and AutoApply Now buon to automatically apply the
receipt. Receivables displays either the applications it has made or any recommendations for receipt application. For
proposed recommendations, you can then select the transactions that you want and manually apply the receipt.
After the receipt is applied to the transaction, Receivables updates the receipt and transaction amounts, and displays
any over or under payments for processing according to the details of the application exception rule set.
193
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Related Topics
• When do I use an application exception rule set
• How AutoMatch Recommendations Are Calculated
• Receipt Application using the Match Receipts By Rule
Receipt-to-Receipt Applications
You can apply an open receipt against another open receipt.
You apply a receipt against another open receipt in order to move funds between receipts. Open receipts include
receipts that have either unapplied cash or on-account cash. You can then apply the resulting unapplied receipt balance
to a transaction.
To use receipt-to-receipt applications, you must set up a clearing account under the Receivables activity Payment
Neing to manage the oset of the one receipt against the other.
Both receipts in a receipt-to-receipt application must be in the same currency. If both receipts are in a foreign currency,
the result of the receipt application may be an exchange gain or loss. The exchange gain or loss is realized on the target
receipt at the time of receipt application. If you later adjust the conversion rate on either receipt, the accounting is
rederived using the adjusted conversion rate.
You can unapply a receipt that was applied to another open receipt, provided that neither receipt is drawn negative by
unapplying it.
194
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Write-o Setup
You can set up Receivables both to write o receipt amounts automatically and to present write-o amounts as
recommendations for review and manual update.
If you decide after review to write o a given overpayment or underpayment, you can manually enter a write-o up to
the total amount assigned to both your receipt write-o approval limits and the system-level write-o approval limits.
Automatic Write-os
Use the Create Automatic Receipt Write-os program to automatically write o receipts. You can only use this program
to write o overpayment amounts.
The Create Automatic Receipt Write-os program writes o selected receipts for the designated unapplied amount
or percentage, and closes the receipts. The program checks that the unapplied amount or percentage is within your
approval limits.
You can use the Create Automatic Receipt Write-os program to:
• Schedule periodic write-os as receipt adjustments for small remaining balances.
• Limit write-os by a percentage of the original receipt amount and by the policy of your enterprise.
• Create write-os for specic currencies and customers.
You can also print and review write-os generated by the program before applying them.
The account assigned to the Receivables activity that you select for the program run is the account credited for all write-
o amounts.
If you adjust the conversion rate of a foreign currency receipt, Receivables reverses the write-o with the original
conversion rate and then applies the new conversion rate to the write-o. Receivables reverses the write-o only if the
converted amount does not exceed the system level write-o limit. If the converted amount exceeds the system level
write-o limit, Receivables leaves the write-o amount as unapplied.
195
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Related Topics
• What are the exception rule activities
• Application Exception Rule Conditions and Actions
• Approval Limits Document Types
You can apply receipts to transactions using any currency dened in General Ledger.
196
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Enter the amount to apply to a transaction in the Applied Amount eld. If a conversion rate exists between
the receipt currency and the transaction currency, Receivables populates the Cross Currency Rate eld and
calculates the allocated receipt amount.
• If a conversion rate doesn't exist between the receipt currency and the transaction currency, then either enter
the rate to use to convert the transaction amount to the receipt amount in the Cross Currency Rate eld, or
enter the amount of the receipt to allocate to the transaction in the Allocated Receipt Amount eld.
• Converts the amount applied to the ledger currency and displays the result in the Amount Applied Base eld.
• Updates the balance due in both the transaction currency (Balance Due eld) and the ledger currency (Balance
Due Base eld).
• Calculates the cross currency conversion:
◦ If necessary, Receivables uses the receipt date as the conversion date and the Receivables system option
cross-currency rate type to calculate the rate.
◦ If you enter a conversion rate in the Cross Currency Rate eld, Receivables calculates the allocated
receipt amount.
◦ If you enter the allocated receipt amount, Receivables calculates the cross-currency rate.
• If applicable, calculates the discounts in the transaction currency. If there are transactions in multiple
currencies, Receivables can't display the total discount in a single currency. You can only view the discount for
each application separately.
• If the currencies have a xed-rate relationship, calculates the rounding error amount created by the cross-
currency receipt application.
• Calculates the foreign currency exchange gain or loss:
◦ Receivables determines the transaction amount and the receipt amount in the ledger currency.
◦ Receivables calculates the foreign currency exchange gain or loss in the ledger currency using this
formula:
Receipt Amount (as of the receipt date) - Transaction Amount (as of the transaction date) =
Foreign Exchange Gain or Loss
Allocated Receipt Amount Base - Amount Applied Base = Foreign Exchange Gain or Loss
◦ If a discount has a gain or loss amount, the amount is included in the realized gain and loss calculation
for the item.
Receivables creates multi-currency journal entries each time you apply a receipt in one currency to a transaction in a
dierent currency. When you post these multi-currency journal entries, General Ledger:
197
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
In the second example, you apply a receipt in one currency to three separate invoices, each in a dierent currency.
Receivables creates corresponding journal entries for this amount in both the invoice currency and your ledger
currency, as illustrated in this table:
On JAN-31, you receive a payment of 64 EUR for Invoice 101. Your customer informs you that the entire amount (64
EUR) is a partial payment of 90 CAD for Invoice 101. The corporate conversion rate on JAN-31 is 1 USD = 1.13 EUR. When
you enter the receipt information, Receivables uses this rate to calculate a receipt amount in your ledger currency of
56.64 USD (64 / 1.13 = 56.64).
When you apply the receipt to Invoice 101, Receivables displays the balance due in your ledger currency (Balance Due
Base) and in the invoice currency (Balance Due), as follows:
Following your customer remiance information, you enter a new value of 90 in the Amount Applied eld. Receivables
calculates the amount applied in your ledger currency (Amount Applied Base) and updates the balance due in your
ledger currency (Balance Due Base) and the invoice currency (Balance Due), as follows:
198
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
You then enter the amount of the receipt to apply to this invoice (64 EUR) in the Allocated Receipt Amount eld.
Receivables uses this amount to determine the Cross-Currency Rate of 0.7111111 (64/90). Receivables then determines
the Allocated Receipt Amount Base (in your ledger currency) of 56.64 USD, using the conversion rate as of the receipt
date. Finally, Receivables calculates an Exchange Loss of 3.36 USD.
199
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Your customer provides remiance information, including rate information, as described in this table:
Invoice Number Date Invoice Balance Paid Amount Rate to EUR EUR Remied
Activity totals:
• Total Remied Amount: 250.78 EUR
• On Account: 49.22
• Total Remiance: 300.00 EUR
After you enter and apply the receipt according to the customer remiance information, this is represented as follows:
On NA NA NA NA NA 49.22 6.27 NA
Account
Related Topics
• What happens if I use suspense posting or other options to post an unbalanced journal entry
• Guidelines for Creating Conversion Rate Types
200
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Under this procedure, the credit card issuer credits the customer account for the disputed amount, deducts the amount
from your merchant bank account, and noties you that a credit card chargeback took place.
You record the credit card chargeback as a negative miscellaneous receipt. Because the customer has already received
the refund directly from the credit card issuer, this negative miscellaneous receipt is used only to ensure accurate
accounting and reconciliation.
Note: If you later discover that the chargeback request was invalid, you unapply the credit card chargeback
activity from the receipt and reapply the receipt for the full amount. This automatically reverses the negative
miscellaneous receipt that was originally created when you rst recorded the credit card chargeback.
Related Topics
• Receivables Activity Types
Miscellaneous Receipts
Enter miscellaneous receipts to record cash received that is not related to receivables. This includes non-invoiced items,
such as investments, interest, refunds, and stock sales.
Considerations for miscellaneous receipts include:
• Distributions
• References
201
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Tax
Distributions
The receivables activity that you assign to the miscellaneous receipt determines the default distribution set and
accounting. The distribution set creates the default account distributions for the entered receipt amount.
References
Use the optional Reference section to identify the miscellaneous receipt as a payment, receipt, or remiance.
This table indicates the reference type and corresponding reference number that you can use to identify the
miscellaneous receipt:
Payment Check numbers recorded in Payables wrien from the same bank account as the remiance
account entered for this receipt.
Payment Batch Batch numbers of payment batches created in Payables that have the same bank account as
this receipt.
Receipt Receipt numbers that have the same bank account as this receipt.
Remiance Remiance batch numbers that have the same bank account as this receipt.
Tax
If applicable, the receivables activity assigns a tax rate code to the receipt. The tax rate code is used to account for tax
on miscellaneous receipts and designates the tax account to use for the tax amount.
You can update the tax rate code with another Sales or VAT tax rate code. You can update the tax rate and tax amount if
the tax rate code allows changes to the tax rate.
Related Topics
• Tax Rates Controls and Defaults
202
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Overview
The Applied Receipts Register provides information about all receipt applications that aect your customer balances.
Key Insights
Review receipt applications by customer and receipt batch. The report displays all receipt applications within the
specied date range regardless of check date.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Period Close
Who uses this report? Financial Manager during period close processing.
When do I use this report? When you need a listing of your customer applied receipts or to assist the receivables
reconciliation process.
203
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Review how customer receipts were applied to transactions. Optionally analyze receipts requiring manual application
(Application Exception Reason) to improve automated receipt applications. Use for reconciling to the general ledger
when a standalone report is needed.
The application exception reasons indicate why a receipt application was not made automatically. If you select this
parameter, the report provides a subtotal by application exception reason.
The transaction number that allows selection of all receipts applied to a transaction.
Report Output
The report provides customer receipt application information by business unit and application accounting date for the
specied period:
• The report displays receipt-to-receipt applications as one receipt with a positive application and the other
receipt with a negative application.
• The report displays debit memo reversal receipts as applied receipts, because the transaction is closed by the
debit memo reversal receipt and a new debit memo is created for the amount of the receipt. All other receipt
reversals appear on the Unapplied Receipts Register.
This table describes important columns in the output of the Applied Receipts Register.
204
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Application Accounting Date The accounting date of the receipt application or application reversal.
Entered Applied Amount The receipt amount applied in the entered currency.
Accounted Applied Amount The total amount applied in the ledger currency.
Application Exception Reason The reason that the receipt could not be applied automatically.
This table describes important rows in the output of the Applied Receipts Register.
[Application Exception Reason] Total The subtotal accounted applied amount by each application exception reason.
[Business Unit] Total The subtotal accounted applied amount by business unit.
Grand Total The total of all accounted applied amounts for the report.
Related Topics
• Guidelines for Dening Automatic Receipt Methods
205
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Overview
The Receipts Days Late Analysis Report helps you review the timeliness of your customer payments.
Key Insights
The report provides details of receipt applications against customer transactions for the period you specify.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Manager when analyzing late payments.
206
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
FAQ Answer
When do I use this report? To review the timeliness of your customer payments, including weighted days late calculation,
which indicates the cost to you of overdue payments.
Run this report according to your customer account review business process.
Report Output
The output provides a separate section for each customer account, and a subsection for each transaction entered
currency within the customer account. Payment information within each subsection is sorted by transaction number
and includes the amount of the application, the receipt number, and the days late (payments made in advance are
displayed as a negative number).
The report provides totals for each entered currency per customer account. The totals include a count of average days
late that payment was received and a calculation of the cost to you of past due items. The report does not include any
grand totals, as it does not report in the ledger currency.
Row Headings
Average Days Late
The average number of days late for receipts by customer and currency.
Average Days Late = Sum of Days Late / Total Number of Receipts
Currency:
The transaction entered currencies used by each customer account.
207
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Overview
The Unapplied Receipts Register lets you review detailed information about customer unidentied, on-account and
unapplied payments. This information more accurately indicates how much a customer actually owes you.
Key Insights
The report groups receipts by receipt batch and customer, and provides separate totals by business unit for on-account,
unapplied, and unidentied receipts in the ledger currency, and a grand total for the report.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Period Close
Who uses this report? Financial Manager during period close processing.
When do I use this report? • When you need a listing of your customer unapplied receipts.
• To assist the receivables reconciliation process.
208
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Run the Unapplied Receipts Register according to your customer account review requirements. You can also use this
report to assist with reconciliation to the general ledger when a standalone report is needed.
Receipt Currency
Application Status
Report Output
The report groups receipts by receipt batch and customer, and provides separate totals by business unit for on-account,
unapplied, and unidentied receipts in the ledger currency, and a grand total for the report.
This table describes the report headings in the Unapplied Receipts Register.
Receipt Entered Amount The amount of the receipt in the receipt currency.
Transaction Accounted Amount The accounted amount of the receipt in the ledger currency.
[Business Unit] Total Separate total accounted amounts for on-account, unapplied, and unidentied receipts.
209
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Related Topics
• Guidelines for Using the Receivables to General Ledger Reconciliation Report
If the value that you enter in the Unapplied Amount or Unapplied Amount Percentage parameter exceeds your write-
o approval limit, then the program run ends with no data found.
The report provides separate receipt and write-o totals for each customer and customer account, and nal totals for
the program run.
Use the Write-o Unapplied Receipt Balances Report as part of your customer account review process.
The currency of the receipts that you want to write o. Only receipts with the currency you enter are eligible for write-
o.
Unapplied Amount
The maximum amount that you can write o. The program selects receipts with unapplied amounts less than or equal
to this value that meet the other selection criteria.
The percentage of unapplied amount against the original receipt amount that you can write o. For example, if you
want to write o receipts with an unapplied balance of 5% or less of the original receipt amount, then enter 5.
Receipt Method
Enter a receipt method to limit the selection of receipts to this receipt method only.
Receipt Number
The number of a specic unapplied receipt that you want to write o. If you specied a receipt method, a customer
name, or a customer account number, then you can only select a receipt number belonging to this customer or receipt
method.
Create Write-os
• Generate Report Only: Generate a report without performing the write-o to review the receipts to be
processed using your selection criteria.
• Create Write-o: Submit the Create Automatic Receipt Write-os program to write o receipts according to
your selection criteria, and generate the Write-o Unapplied Receipt Balances Report.
210
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
The receivables activity that determines the general ledger account to use to credit the write-os.
This parameter is required if you set the Create Write-os parameter to Create Write-o.
Application Date
The application date of the write-o to apply to all of the selected receipts.
Accounting Date
The accounting date of the write-o to apply to all of the selected receipts. The date is validated during the program run
to ensure that it is in an Open or Future Open period.
Can I apply payments from a customer site to transactions of the same site?
Yes, you can search for transactions by bill-to site to apply to receipts. In the Edit Receipt page, click the Add Open
Receivables buon to open the Search and Select window. Use the Bill-to Site eld to lter customer transactions by
bill-to site.
If necessary, you can retain the original adjustment record by creating a new adjustment in the transaction or in receipt
details.
211
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Line First - Tax After: Apply the receipt to the open line item amount rst. Apply any remaining receipt amount
in the following order: tax, freight, late charges.
• Line and Tax Prorate: Apply a proportionate amount of the receipt to the open line item amount and the open
tax amount for each line. Apply any remaining receipt amount to freight rst and then to late charges.
• Prorate All: Apply a proportionate amount of the receipt equally to the line, tax, freight, and late charges.
If you apply a receipt that doesn't contain customer information to a transaction, Receivables updates the receipt with
the customer information on the transaction.
The Exception Trends table in the contextual pane tracks for each customer the exception reasons that were used to
mark manual receipts and the number of occurrences of each exception.
You can't unapply a receipt that has adjustments associated with it unless you rst readjust the transaction to its
original amount. In addition, you can't unapply a receipt if there is a chargeback against the transaction and this
chargeback has activity against it, for example, another receipt or credit memo.
You can unapply a receipt that was applied to another open receipt, provided that neither receipt is drawn negative by
unapplying it.
212
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
For example, a customer sends a payment of $75 for a $100 invoice. You apply the receipt to the invoice, and create
a chargeback for the balance due. If the transaction types assigned to the transaction and to the chargeback allow
overapplication, you can enter a chargeback amount greater than the original balance due.
You can edit a chargeback transaction like any other transaction on the Edit Transaction page.
A credit card chargeback is a negative miscellaneous receipt that records a transaction between a credit card issuer
and a cardholder. The credit card issuer credits the customer account for a disputed amount, and deducts the amount
from your bank account. The negative miscellaneous receipt, or credit card chargeback, is created to ensure accurate
accounting and reconciliation for these transactions.
You use automatic receipts for customers with whom you have predened agreements. These agreements let you
collect payments on time for open debit items by transferring funds from the customer bank account or credit card to
your bank account on the receipt maturity date. If necessary, the customer can conrm the automatic receipt batch
before transferring funds.
After an automatic receipt batch is created, you can reapply and reverse automatic receipts in the same way as manual
receipts. To reverse an automatic receipt, it must be approved.
• Receipt Class: Use these seings for the receipt class of the receipt method assigned to each transaction:
• Receipt Method: Use these seings for the receipt method assigned to each transaction:
◦ Receipts inherit transaction numbers option: Set this option to assign the automatic receipt the
number of the transaction to which it is applied. Don't set this option if you want to assign a document
number to each automatic receipt.
◦ Number of Receipts Rule: Rule that determines the number of receipts to create from the transactions
contained in the batch.
213
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
◦ Receipt Maturity Date Rule: Rule that assigns the maturity date to the automatic receipt. The maturity
date is the date to transfer funds from your customer bank or credit card to your remiance bank
account.
The rule uses either the Earliest or the Latest due date of all the selected transactions applied to the
receipt as the receipt maturity date.
◦ Lead Days: The number of days before the transaction due date that a transaction is eligible for
automatic receipt selection. Set the lead days to a high value for:
• Automatic receipts that require conrmation. This allows for the additional time required to send
the receipts to your customer and for the customer to conrm them.
• Factored receipts. Factored receipts are often remied long before their maturity date.
◦ Customer Payment Method: Enter the payment method that the customer uses to remit payment to you.
◦ In the Sequencing section of the Specify Options page of your primary ledger, set the Sequencing By
option to Ledger or Legal Entity.
◦ Optionally enable the Enforce Document Sequencing option for Receivables.
◦ Dene an automatic document sequence and assign this sequence to the document category associated
to the receipt method you plan to use for automatic receipts. The document category is automatically
created when you create a receipt method.
Note: If the receipt method has the Receipts inherit transaction numbers option enabled, and
the Number of Receipts Rule is One per Invoice, then document sequences are not used. Instead,
Receivables uses the transaction numbers as the receipt numbers.
◦ Receipt Method: All transactions must have the same receipt method as the automatic receipt batch.
◦ Customer payment information: All transactions must have dened both a paying customer and
payment instrument information.
• Customer account or site to include in the automatic receipt batch:
◦ Payment Details: Dene payment details, including the payment instruments the customer uses.
◦ Primary receipt methods and payment instruments: Depending on the preferred payment method of
the customer, designate on the customer or site prole one of the credit card or bank account transfer
receipt methods as Primary, and designate a credit card or bank account payment instrument as primary.
◦ AutoReceipts include dispute items option: Use this option on the customer or site prole to determine
whether to include open items in dispute during transaction selection.
◦ Minimum Receipt Amount eld: Use this eld on the customer or site prole to dene an amount in the
batch currency below which the program won't generate automatic receipts.
• Automatic Receipts Receipt Source: Enter a value in the Batch Number Starts After eld. Automatic receipt
batch numbering begins after the number that you enter, for example, if you enter 1000, the rst automatic
receipt batch created is numbered 1001.
• Conversion Rate Type prole option: If you are using automatic receipts to pay foreign currency transactions,
then set this prole option to a value other than User to convert to the ledger currency.
• Remiance Bank Account:
◦ Dene a remiance bank account for the batch receipt method in the batch currency.
214
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
◦ Minimum Receipt Amount eld: Enter an amount below which the program won't generate automatic
receipts.
Caution: The automatic receipt process compares the remiance bank account and customer
prole class minimum receipt amounts and uses the larger of the two when creating automatic
receipts. If both amounts are greater than the receipt total, then the program doesn't create an
automatic receipt batch.
1. Prepare transactions. Ensure that each transaction that you want to include in the batch has paying customer
information and is assigned the appropriate receipt method (credit card or bank account transfer) that you
want to use for automatic receipts.
2. Select transactions and create the batch. Considerations for transaction selection include:
◦ You can enter a range of credit card numbers in the Customer Bank Account elds to create automatic
receipts for transactions marked for payment by credit card.
◦ Receivables checks the customer prole to determine whether to include transactions in dispute.
◦Receivables compares the transaction due date to the batch date and batch lead days to determine
whether a transaction is eligible for automatic receipts. The dierence between the batch date and
transaction date must be less than or equal to the number of lead days.
◦ The transaction total must be greater than or equal to the larger of the two minimum receipt amounts (in
the remiance bank account or customer prole) in order to create an automatic receipt batch.
3. Submit the batch. Receivables creates receipts, according to the receipt rule on the receipt method, to close out
all completed transactions that meet the selection criteria.
4. Review and approve the batch. You can update, delete, and approve the receipts that were created by the
batch.
If you are processing credit card payments, the approval process sends the receipt batch to Payments for credit
card authorization. If authorization is successful, then Payments assigns an approval code to each transaction
and the corresponding receipt is approved. If authorization is not successful, then the receipt is rejected from
the batch.
Note: A receipt can fail authorization if, for example, the credit card number is invalid, the payment
amount exceeds the cardholder credit limit, or the card has been reported lost.
5. Conrm the batch. If necessary, send the automatic receipt batch to your customer for conrmation.
6. Remit receipts. Remit the receipts to your bank:
◦ If you are processing credit card payments, then the remiance process requests transfer of funds from
the credit card issuer to your bank.
◦ If you are processing bank account transfers, then the remiance process requests transfer of funds
from the customer bank account to your bank.
Related Topics
• What's the dierence between the various customers
• Requirements for Completing a Receivables Transaction
• Remiance Bank Accounts on Receipt Methods
215
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
When you create an automatic receipt batch, the process applies receipts to customer transactions and transfers funds
from the customer bank account or credit card to your bank account on the receipt maturity date.
This topic provides additional information about the following aspects of the automatic receipt process:
• Discounts and Automatic Receipts
• Start and End Date Ranges
• Remiance Bank Information
• Document Sequences
• Bill-to Sites and Automatic Receipts
• Payment of Related Transactions
• Automatic Receipts System Options
You can't use discounts with automatic receipts that require conrmation by the customer. Alternatively, you can dene
an Earned Discount receivables activity and create an adjustment to reduce the balance on transactions by the discount
amount. You then charge the adjusted amount to this receivables activity discount account.
For example, if you assign a receipt method with a date range of 01-SEP-18 to 30-SEP-18 to one of your customers, you
can't choose this receipt method if you enter an invoice for this customer on 01-OCT-18.
The automatic receipt process usually assigns to the receipt the primary remiance bank account associated with
the receipt method and currency of the transaction. The one exception to this is if a non-primary remiance bank
216
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
account belonging to the same receipt method uses the same currency as the customer bank account. In this case, the
automatic receipt process uses this remiance bank account instead.
This matching of your remiance bank account to a customer bank account in the same currency helps you both to
avoid bank charges and to expedite funds transfer.
You can update remiance bank information for an automatic receipt under these conditions:
• Receipt status is Conrmed.
• Unapplied and On-Account general ledger accounts of the remiance bank are the same account.
Document Sequences
If you plan to assign a unique document number to each automatic receipt, you must enable document sequencing at
the appropriate ledger or legal entity level.
To enable document sequencing:
• At the ledger level: Set the Sequential Numbering prole option to Always Used or Partially Used.
• At the legal entity level: In the Sequencing section of the primary ledger options setup, set the Sequencing By
option to Legal Entity, and set the enforce options according to your requirements.
Yes No No
• If the system option is set to No and the customer doesn't have a primary bill-to site dened, Receivables
creates the automatic receipt without assigning a bill-to site.
• If the system option is set to Yes and the customer doesn't have a primary bill-to site dened, Receivables
doesn't create the automatic receipt.
217
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
If you want one customer to pay for transactions billed to another customer, you must do one of the following tasks:
• Enable the Allow payment of unrelated transactions Receivables system option.
• Dene a paying relationship between the two customers.
Then, when entering or updating transactions for automatic receipt processing, you must enter the bill-to customer
name and site, and the paying customer bank information.
Use the Invoices per Commit and Receipts per Commit elds to enter values large enough to avoid intermediate saves
in the program. Enter values that can handle your largest automatic receipt and remiance batches.
To help determine the values to use, refer to the end of the log le of your largest automatic receipt batch and
remiance batch to see the number of receipts marked for the batch. You can later reduce these numbers if you run out
of rollback segments.
Related Topics
• When are receipts required for a bill-to site
• What's the dierence between an account relationship and a paying relationship
• Guidelines for Managing Document Sequences
• Ledger and Legal Entity Document Sequencing in Receivables
You can remove transactions from the batch. Transactions that you remove are available for selection the next time you
submit the automatic receipt creation program. If applicable, you can also update conversion rate information.
You can delete an automatic receipt batch that has the status Creation Completed without approving it. When you
delete a batch, all of the transactions in the batch become available for selection the next time you submit the automatic
receipt creation program.
You can update the bank name, bank branch, and customer bank account associated with each of the transactions in
the batch. Updates to bank information are limited to selecting a new customer bank or bank account for a transaction
that is assigned to either this customer or the primary customers of this customer. In addition, this bank must have a
bank account in the same currency as the automatic receipt batch.
Once you approve the batch, Receivables creates the automatic receipts that don't require conrmation according to
the Number of Receipts Rule on the receipt method and closes the transactions they are paying.
Note: Receipts that require conrmation close transactions only when they are conrmed by the customer.
218
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
When you remit an approved automatic receipt batch, your remiance bank uses the batch maturity date to determine
when to transfer the funds from your customer bank account to your remiance bank account. Receivables uses the
Receipt Maturity Date Rule on the receipt method to determine the maturity date on the approved receipts.
When a customer conrms the automatic receipt batch, they may provide a conrmation number for each receipt. Enter
this number in the available reference or comment eld. This number is passed to your remiance bank, which can then
forward it to the customer bank. This helps your customers to reconcile their accounts.
If the receipt class of the receipt method assigned to an automatic receipt or automatic receipt batch requires
conrmation, you must conrm the receipt or receipt batch once it has been approved by your customer. Receipts
that require conrmation automatically close the invoices for which they were created when you conrm them. After
conrming the automatic receipt batch, you can create a remiance batch to initiate the transfer of funds for each
receipt.
You can make these updates to an automatic receipt batch before you conrm it:
• Transactions selected to apply to the receipt.
• Conversion rate information.
• Receipt maturity date.
• Your remiance bank.
• Customer bank account information.
You can only change the approved amounts for your receipt applications if the receipt isn't conrmed. Once conrmed,
Receivables automatically applies the receipt and updates the balance of the transactions to which it is applied.
219
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Use the Manage Reversal Reason to Category Mappings setup task to map the ISO rejection codes with corresponding
reversal categories.
• Reversal le - pain message 002.001.03. This message provides technical details of the reversals that are
needed to reverse a receipt.
• Bank statement les CAMT-053.
220
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Related Topics
• How Selement Batches Are Processed
How You Create Receipts for Credit Card Transactions with Tokens
Use the Create Automatic Receipt process to create receipts for tokenized credit card transactions.
Note: Credit card services are currently not available in Oracle Cloud implementations.
You import tokenized credit card transactions using AutoInvoice. Once the transactions are successfully imported into
Receivables, you can prepare transactions for receipt creation. Review and if necessary complete these tasks:
• Create a credit card automatic receipt method.
• Review imported transactions.
• Create automatic receipts and remiance.
221
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Receipt Method: Receipt Maturity Date Rule: Select the Receipt Maturity Date Rule Earliest.
• Receipt Method: Customer Payment Method: Select the Customer Payment Method Credit Card.
• If the imported transaction includes authorization, then you can't update the receipt method or credit card
information.
• If the imported transaction doesn't include authorization, then you can update the receipt method or credit card
information.
• If the credit card security code was required to process the transaction, then you can't update the receipt
method or credit card information.
• Review and, if necessary, update the paying customer assigned to the transaction.
• Automatic Receipt Method: Ensure that all transactions are assigned the credit card receipt method that you
will use for the automatic receipt batch.
• Paying Customer: Ensure that all transactions are assigned the same paying customer during automatic receipt
processing.
• Fully Applied Receipts: Ensure that receipts are fully applied before creating the remiance batch.
222
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Reverse Receipts
Considerations for Reversing Receipts
Reverse a receipt when your customer stops payment on a receipt or if a receipt comes from an account with
insucient funds.
Considerations for reversing receipts include:
• Receipts Eligible for Reversal
• Receipt Reversal Process
• Reversal Categories and Reasons
You can reverse a receipt that was applied to transactions with adjustments or chargebacks, provided the adjustments
and chargebacks haven't posted to general ledger.
Note: If a chargeback posted to general ledger, then you must create a debit memo reversal instead.
The reversal reasons are user-dened reference information that describe why a particular category of reversal took
place.
223
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• You are reversing a receipt from which you have created a chargeback, and this chargeback has had activity
against it, such as another receipt, a credit memo, or an adjustment.
• You are reversing a receipt with a remied credit card refund application.
• You are reversing a receipt (Receipt A) that was applied to another receipt (Receipt B), if the reversal would
draw the balance of Receipt B negative.
Note: You can't create a debit memo reversal for a miscellaneous receipt.
If you are using manual document numbering, enter a unique document number for this reversal. If you are using
automatic numbering, Receivables assigns a unique document number to the new debit memo.
When you create a debit memo reversal, Receivables generates the line item from the predened memo line.
Receivables creates this line on the debit memo:
Debit memo for reversal of payment {PAYMENT_NUMBER}
224
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
The cash account used depends on the status of the receipt at the time of the creation of the debit memo reversal. For
example, if the receipt was remied, then the cash account is the same as the remied account assigned to the receipt
method of the receipt.
When you create a debit memo reversal, Receivables creates these two entries:
1. The rst entry decreases the cash account.
Receivables already recognized revenue on the original transaction. To avoid overstating the cash and revenue
accounts, Receivables doesn't create an additional entry to revenue but instead assigns the cash account to the
revenue line on the debit memo.
2. The second entry creates the new receivable.
When the original receipt was applied, Receivables closed the transactions and their associated receivables. You
must therefore establish a new receivable to track the new debit item.
Related Topics
• Receivables Accrual Accounting Entries
Overview
The Reversed Receipts Report lets you review receipt reversals by reversal date and remiance bank.
225
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Key Insights
The report displays results and total receipts by bank, customer or reversal reason. You can optionally review specic
receipts according to the parameters that you specify.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Manager when analyzing causes of reversals.
When do I use this report? To review receipt reversals by reversal date and remiance bank, and categorize by stop
payments, insucient funds, and receipts entered in error.
Use this report in conjunction with your customer payment processing processes.
Reversal Category
Reversal Reason
226
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
If you selected a reversal category, review receipt reversals for this reversal reason within a reversal category only.
Receipt Type
Standard or Factoring.
If reviewing debit memo reversals, enter the debit memo reversal number.
Report Output
The column order and subtotals depend on the value of the Subtotal by parameter: Bank, Customer or Reversal
Reason.
This table describes the column headings in the Reversed Receipts Report.
Reversal Reason The specic reason within a category why a receipt was reversed.
Debit Memo Reversal Number The number of the debit memo that records a debit memo reversal for the receipt.
Receipt Entered Amount The amount of the receipt in the entered currency.
227
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Receipt Accounted Amount The amount of the receipt in the ledger currency.
This table describes the row headings in the Reversed Receipts Report.
[Remiance Bank Name] Total Total of all reversed receipts for a remiance bank in the ledger currency.
[Reversal Reason] Total: Total of all reversed receipts for a reversal reason in the ledger currency.
[Customer Name] Total Total of all reversed receipts for a paying customer in the ledger currency.
Total Receipt Accounted Amount Grand total of all reversed receipts in the ledger currency.
228
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• A chargeback was created against the receipt and the chargeback posted.
• A credit card refund was issued for the receipt and the corresponding negative miscellaneous receipt was
already remied.
• The receipt is applied to another receipt and the reversal would cause a negative balance on the other receipt.
You can't initiate a debit memo reversal if any of the following are true:
Manage Lockbox
Lockbox Standard Receipt Import Process
Use the lockbox standard receipt import both to create receipts in Receivables from data supplied by your remiance
bank and to apply the receipts to customer transactions.
• Import Data: Lockbox reads and formats the data from your bank le into the interface table from the data
uploaded using the FBDI template.
• Validate Data: Receivables validates the data in the interface table for compatibility, then transfers the data to
the receipts tables.
• Post Receipts: Receivables applies the receipts to transactions and updates the customer balances.
You can submit these steps individually or at the same time. After you post lockbox receipts, Receivables treats these
receipts like any other receipts: you can reverse and reapply them, and apply any unapplied, unidentied, or on-account
amounts.
229
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Import
You use the Process Receipts Through Lockbox: Import program to read and format data from the bank le into the
AR_PAYMENTS_INTERFACE_ALL table using the data uploaded from the FBDI template.
Receivables uses the lockbox transmission format that you specify in the Process Receipts Through
Lockbox: Import program submission to ensure that data is correctly transferred from the bank le into the
AR_PAYMENTS_INTERFACE_ALL table. The transmission format contains information such as the customer account
number, bank account number, the amount of each receipt to apply, and transaction numbers to which to apply each
receipt.
Validate
The validation process includes these checks:
230
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Columns in the AR_PAYMENTS_INTERFACE_ALL table reference the correct values and columns in
Receivables.
If the receipt and transaction currencies are dierent, Receivables also requires specic application information to
determine the conversion rate between the two currencies.
Receivables transfers the receipts that pass validation to the AR_INTERIM_CASH_RECEIPTS_ALL and
AR_INTERIM_CASH_RCPT_LINES_ALL interface tables. At this point, you can optionally review receipts and change how
they are to be applied before posting.
Use the Process Receipts Through Lockbox: Report to review all pass and fail validations for a lockbox transmission.
Receipts that fail validation remain in the AR_PAYMENTS_INTERFACE_ALL table until you manually correct the import
errors. You can then resubmit the validation step for these receipts.
Post
Use the Post Receipt Batch program to post lockbox receipt batches that have passed import and validation.
When you process a lockbox receipt batch, Receivables matches receipts to transactions and applies the receipts
automatically. In cases where receipts are not applied automatically, Receivables generates a list of recommended
transactions for receipt application to complete the process manually.
Related Topics
• Overview of External Data Integration Services for Oracle Cloud
• File Based Data Import for Oracle Financials Cloud
When all three values are present in the transmission le, lockbox ensures that the amounts are consistent before
importing the receipt, by verifying that these calculations are true:
amount_applied * trans_to_receipt_rate = amount_applied_from
If the receipt and transaction currencies have a xed rate relationship, the lockbox transmission le only requires either
the Transaction Amount Applied or the Receipt Amount Applied to apply the receipt.
If the receipt and transaction currencies don't have a xed rate relationship, the lockbox transmission le must either
contain the conversion rate or be able to determine the conversion rate in order to apply the receipt.
231
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
If both the conversion rate and either the Transaction Amount Applied or the Receipt Amount Applied are missing,
lockbox uses the seing of the Cross Currency Rate Type system option to either derive the rate and the other missing
value or reject the receipt.
This table shows how lockbox processes conversion rates and receipt application based on dierent combinations of
information provided in the bank transmission le:
• Conversion Rate Validate that all values are correct. • If all values are correct, apply the
• Transaction Amount Applied receipt.
• Receipt Amount Applied • If one or more values are incorrect,
reject the receipt.
• Transaction Amount Applied Calculate the conversion rate to use or Apply the receipt.
• Receipt Amount Applied derive the rate from general ledger.
• Conversion Rate
• Transaction Amount Applied or
Receipt Amount Applied
The result of adding the invoice amounts and converting the total is:
232
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Although this method is mathematically correct, lockbox uses a dierent procedure to calculate remiance amounts.
This procedure is as follows:
1. Convert each transaction to the receipt currency.
2. Add the amounts in the receipt currency.
3. Remit the sum as the Receipt Amount Applied (amount_applied_from).
Using the same invoices and conversion rate, the result of this procedure is as follows:
Transaction * Rate = Amount (in receipt currency)
The Receipt Amount Applied (amount_applied_from) as entered in the bank transmission le is 2582.87, but lockbox
calculates the Receipt Amount Applied as 2582.88. As a result of this discrepancy, lockbox leaves .01 unapplied and one
of the invoices remains open.
To avoid these potential discrepancies, it is recommended that you establish business procedures with your customers
to ensure that remiance amounts are calculated using the same method as lockbox.
Transmission Name
• If you set the New Transmission parameter to Yes, enter a new transmission name.
• If you set the New Transmission parameter to No, enter the name of the lockbox transmission that you are
resubmiing.
Submit Import
• Yes: To import a new bank le. You must also enter the data le, control le, and transmission format
information for the new bank le.
• No: To resubmit an existing lockbox transmission.
Data File
233
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
The bank le to import. You must include the le extension. For example: /home/ar/lockbox/bofa9101.dat.
Submit Validation
• Yes: To validate a new bank le or to revalidate a previously imported bank le.
• No: To skip the validation process.
Lockbox
The number of the lockbox to validate. If you set the Submit Validation parameter to Yes and the lockbox number is
not specied in your bank le, then you must enter a lockbox number.
Accounting Date
Enter the accounting date to use to post the receipt and batch records in this lockbox transmission to the general
ledger. If you set the Submit Validation parameter to Yes, then you must enter an accounting date.
• If you dened the accounting date in the lockbox as Constant Date, enter an accounting date.
• If you dened the accounting date in the lockbox as Deposit Date or Import Date, then the program uses either
of these dates as the accounting date.
Report Format
• All: Include all records processed in the Validation section of the report.
• Rejects Only: Include only the records that failed validation.
234
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Enter the number of AutoMatch workers submied from lockbox, if there are any unresolved references from the
lockbox validation.
Report Output
The report is divided into two sections:
• Import: Displays the total number of records that were imported into the interface tables successfully.
• Validation: Provides details for each record and the total amount and number of receipts in each lockbox
transmission.
The Import section of the report is generated when you submit the lockbox import step. The report prints a line at the
end of the Import section informing you of any rejected or discarded les.
The Validation section of the report is generated if you set the Submit Validation parameter to Yes. Use this section of
the report to see the number of records that pass or fail validation. You can also see the total amount and number of
receipts in each lockbox transmission.
Use the Manage Lockbox Transmission page to review and edit records that failed validation.
Column Detail
Record Count Summary
The number of records for this transmission and their corresponding statuses.
Transmission
The deposit date, bank origination number, deposit time, destination account, and the following transmission
information:
Lockbox Records
The lockbox record information for each record processed. The lockbox information includes the number of
receipts in the lockbox that met the criteria for each category.
Batch Records
The receipt batch information for each batch in the bank le, if you include batches as part of your transmission
format. Lockboxes may contain several receipt batches. Receipt batch information includes the receipt batch
name, the total number of receipts in the batch, the total receipt amount, currency, and the deposit date and
accounting date for the receipt batch.
Record Details
The details of each record and the status of that record.
235
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Note: If you run the Validation report for Rejects Only, the report includes only records in error and their
corresponding error statuses.
Related Topics
• How Lockbox File Transmissions Are Validated
Process Refunds
How You Issue Manual Refunds
You can issue manual refunds for both credit card and non-credit card transactions. Depending on your
implementation, you can also issue refunds for overpayments on transactions.
236
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Note: Credit card services are currently not available in Oracle Financials Cloud implementations.
• You can't refund more than either the original receipt amount or the remaining unapplied amount.
• You can only refund original receipts that were either remied or cleared.
• You can't issue a credit card refund unless the customer payment was made by credit card.
If the refund is by bank account transfer, you must enter the customer bank account.
3. Save the refund and receipt.
Receivables sends a refund request to Payables, which in turn validates the refund information and sends a payment
request to Payments.
237
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
If you are correcting a payment to an incorrect credit card number, then after you issue the credit card refund, assign
the correct credit card number to the transaction as the payment instrument and run the Create Automatic Receipts
program to create a payment for the transaction.
If you decide after review to refund an overpayment, you can manually issue a refund up to the total amount assigned
to your refund approval limits.
Related Topics
• Payment Requests
• Application Exception Rule Conditions and Actions
You issue a credit card refund against the unapplied receipt amount to generate a negative miscellaneous receipt. You
then run the Create Automatic Remiances program to process this negative receipt to transfer the funds from your
account back to the credit card of your customer.
◦ Dene formats
◦ Dene payment systems
◦ Dene system security options
◦ Integrate external payment systems
◦ Dene credit card brands
◦ Dene funds capture payment methods
◦ Dene funds capture process proles
◦ Dene internal payees
• Credit Card Refund Receivables Activity: Dene a Credit Card Refund Receivables activity. This activity identies
the general ledger clearing account to use to clear credit card refunds.
• Credit Card Refund Reversal Reason Lookups: Dene lookup values to indicate the reasons for credit card
refunds.
• Credit Card Transaction Receipt Class: On the original credit card transactions, use a receipt class with a
creation method of Automatic.
238
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Credit Card Transaction Remiance Method: On the original credit card transactions, use a receipt class
with a remiance method of Standard. When you refund these payments, the credit card refund (negative
miscellaneous receipt) inherits the remiance method from the original receipt.
Payments initiates a refund even if the credit card has expired, because expired credit cards are usually reissued
with a new expiration date. If a credit card has expired and was not reissued, then the credit card issuer declines the
transaction and Payments reverses the refund.
Note: Unlike the credit card payment process, the refund process doesn't require authorization to transfer
funds back to the customer credit card. If you want to approve credit card refunds before processing, dene
refund approvals as part of your business process.
If you make a mistake while initiating a credit card refund, you can correct the error in one of two ways, depending on
whether the negative miscellaneous receipt was approved and remied.
If the negative miscellaneous receipt was not approved and remied, perform either of these steps:
• Unapply the credit card refund application line from the receipt. Receivables reverses the negative
miscellaneous receipt and creates the necessary journal entries.
• Change the amount that you want to apply to the credit card refund application. Receivables reverses the
original negative miscellaneous receipt and creates a new negative miscellaneous receipt for the correct
amount.
If the negative miscellaneous receipt was approved and remied, perform either of these steps:
• If the funds were transferred to the customer account, create a debit memo to bill to your customer for the
balance due.
• If the funds were not transferred to the customer account, reverse the negative miscellaneous receipt. This
action unapplies the refund from the original payment. If necessary, you can apply a new refund application to
the original payment.
If the negative miscellaneous receipt was not approved and remied, reversing the receipt unapplies the credit card
refund lines on the receipt and reverses the associated negative miscellaneous receipt.
If the negative miscellaneous receipt was approved and remied, reversing the receipt doesn't automatically unapply
the credit card refund application because Receivables assumes that the receipt was already refunded. In this case,
when you reverse the original receipt, you must create a debit memo reversal.
If neither the original payment nor the refund seled, then you can reverse the actual credit card refund (the negative
miscellaneous receipt) and the payment in order to reconcile with your bank. Reversing a negative miscellaneous
receipt automatically unapplies the refund from the original receipt. You can then reverse the original receipt, which
reopens the transaction.
Related Topics
• Remiance Methods and Clearance Methods
239
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
You can only use automated receipt handling for credits with approved credit memos. You must ensure that you set up
your feeder systems with business processes that support this assumption.
240
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
If the credit memo is ineligible due to one of these conditions, AutoInvoice processes the credit memo using standard
validation. This way you can evaluate the appropriateness of the credit request before taking action.
For refund requests, AutoInvoice automatically places on account the amount of a refund request if one of the following
conditions exits:
Related Topics
• AutoInvoice Data Preparation
When you enter a foreign currency credit card refund, Receivables creates a negative miscellaneous receipt in the
foreign currency using the same rate as the original receipt. During reconciliation, when you know the conversion rate
that the bank used at the time of the refund, you can adjust the conversion rate on the negative miscellaneous receipt
to reect the information on the bank statement.
Receivables automatically creates the necessary journal entries to account for the exchange gain or loss. You can view
the exchange gain or loss accounting entries on the original credit card payment.
241
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
• Standard Remiances
• Factored Remiances
• Seings for Remiance Batches
Standard Remiances
A standard remiance refers to the common practice of remiing receipts. You remit automatic receipts to your bank so
that the bank can transfer funds from customer bank accounts to your bank account on the receipt maturity date. You
remit manual receipts so that the bank credits your bank account when the customer check clears.
The remiance process initiates the transfer of payment for transactions that are paid by credit card or Electronic Funds
Transfer (EFT) for both direct debit and Automated Clearing House (ACH) bank account transfer.
Factored Remiances
A factored remiance is a sale of accounts receivable to your bank in exchange for cash. You remit receipts to your
bank so that the bank can lend you money against the receipts either before the maturity date for automatic receipts or
before clearing for manual receipts.
To factor receipts, you must identify the remiance method of the remiance batch as Factored. In addition, you can
only factor receipts assigned a receipt class with a remiance method of Factoring or Standard and Factoring.
After clearing factored receipts, Receivables creates a short term debt for the borrowed amount to track your liability in
case of customer default.
You can track your risk of customer default when you factor a receipt with your bank. In this case, Receivables creates a
short term debt for the risk when the receipt is cleared. Run the Clear Receipts Automatically program to eliminate your
risk on or after the maturity date of your automatic receipts.
This table shows the accounting entries that Receivables creates when you factor receipts with a receipt class that
requires conrmation, remiance, and clearance:
242
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
You can deposit receipts into remiance bank accounts that are either in the currency of the receipt or your ledger
currency, provided the bank account allows multiple currencies. If you are remiing receipts in foreign currencies,
set the Conversion Rate Type prole option to a value other than User, because you can't specify a user-dened
conversion rate when remiing receipts.
To manage automatic remiance batches, set the Receipts per Commit Receivables system option to a large number
to avoid intermediate saves in the program. You must use numbers that are large enough to handle your largest
automatic remiance batches. To help determine the number to enter, review the log le for your largest automatic
remiance creation batch. Reduce this number only if you run out of rollback segments.
Related Topics
• Remiance Bank Accounts on Receipt Methods
• Change Instrument
• Clear Payment Information
• Retry
• Reverse Receipt
Change Instrument
You can change the payment instrument and corresponding expiration date on a transaction or a receipt.
Note: If the receipt method assigned to a transaction uses bank account transfer as the payment method,
then you can't change the expiration date.
To include the transaction in future runs of automatic receipts, you can reassign the transaction payment information
and an automatic receipt method.
Retry
You can retry receipt or remiance processing for transactions, receipts, and refunds. This action removes the error
code and makes the transaction, receipt, or refund available for inclusion in the next automatic receipts or remiance
batch.
243
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Reverse Receipt
You can use this action to reverse receipts or refunds. This action raises a business event, reverses the receipt, reopens
the original transaction, and removes payment.
Related Topics
• Options for Resolving Payment File Transmission Failures
• Options for Resolving Payment File Validation Errors
If you don't want to recognize the cash until it is deposited into your bank account, you can reconcile the bank
statement within your accounts receivable. This step is optional for both automatic and manual receipts.
Remied Receipts
Clearing remied receipts credits your cash account and debits your remiance or factoring account.
Remied receipts are cleared X days after their maturity date, where X is the number of clearing days dened for the
receipt method/bank account combination on each receipt.
Factored Receipts
Clearing factored receipts creates a short term debt to account for your risk in case of customer default. The debt is
cleared by the Clear Receipts Automatically process Y days after each receipt maturity date, where Y is the number of
risk elimination days dened for the receipt method/bank account combination assigned to the receipt.
Factored receipts are cleared immediately on the remiance date. To eliminate risk created by clearing factored
receipts, set the Eliminate Bank Risk parameter to Yes when you run the Clear Receipts Automatically process.
Report Output
This table describes the two important row headings in the Bank Risk Report.
244
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Total for Remiance The total amount in the ledger currency of all receipts in each remiance batch.
Review this report each time you clear receipts using the Clear Receipts Automatically program.
Report Parameters
Clear Remied Receipts
Clear Date
Specify the date to use as the clearance date for remied receipts. This is also the date that is used to make conversion
rate adjustments. The default is the system date.
Accounting Date
Enter the accounting date to use for the clearance record for each receipt.
Enter the conversion rate type to use to determine the conversion rate. Conversion rate adjustments are made for
receipts that are in a currency dierent from the bank account currency.
Report Output
The report sorts results by status and receipt number, and provides subtotals by status and bank name and a grand
total in the ledger currency.
This table describes important column headings in the Clear Receipts Automatically Execution Report.
245
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
This table describes important rows in the Clear Receipts Automatically Execution Report.
Total for Status The amount of all receipts cleared for the given bank and status in the ledger currency.
Number of Records Processed for The number of receipts processed for the given bank and status.
Status
Total for Bank The amount of all receipts cleared for the given bank in the ledger currency.
Number of Records Processed for The number of receipts processed for the given bank.
Bank
Grand Total for Status The total amount of all receipts cleared for all banks in the given status in the ledger currency.
Number of Records Processed for The total number of receipts processed for all banks in the given status.
Status
246
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Overview
The Receipts Awaiting Bank Clearance Report lets you review receipts waiting to be cleared by your remiance bank.
Key Insights
The report provides a separate section for each currency included in the output, and sorts information within each
currency section by remiance bank account and remiance batch date.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
When do I use this report? To review all receipts waiting to be cleared by your remiance bank.
247
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Currency
Order By
• Maturity Date
• Receipt Number
• Remiance Bank (the default, if no value selected)
Report Output
The report provides a separate section for each currency included in the output. The report does not convert receipt
currencies to the ledger currency nor provide a grand total in the ledger currency.
By default the report sorts information within each currency section by remiance bank account and remiance batch
date, and provides subtotals by remiance bank account and remiance batch date and a grand total for the currency.
• If you set the Order By parameter to Maturity Date, the report sorts receipts by maturity date and provides
subtotals by remiance bank account and maturity date.
• If you set the Order By parameter to Receipt Number, the report sorts receipts by receipt number but does not
provide any subtotals.
This table describes important column headings in the Receipts Awaiting Bank Clearance Report.
Remiance Bank Account Name The name of the remiance bank account for the applicable receipts.
Remiance Batch Date The date the remiance batch was created for the applicable receipts.
248
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
This table describes important row headings in the Receipts Awaiting Bank Clearance Report.
Total for Remiance Batch Date The total amount of all receipts for the given batch date.
Total for Remiance Bank Account The total amount of all receipts for the given remiance bank account.
Total for Maturity Date The total amount of all receipts for the given maturity date.
Total for Currency The total amount of all receipts in the receipt currency.
249
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Overview
The Receipts Awaiting Remiance Report lets you review receipts awaiting remiance to your bank.
Key Insights
The report runs on both automatic and manual receipts. Once a receipt is approved for remiance it will no longer
appear on the report.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Manager to analyze the overall remiance status.
250
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
FAQ Answer
When do I use this report? To review all receipts requiring remiance to your bank.
Once a receipt is approved for remiance it will no longer appear on the report.
Run this report in accordance with your regular customer payment business process.
• Maturity Date
• Receipt Number
• Remiance Bank (the default, if no value selected)
Status
Report Output
The report provides a separate section for each currency included in the output. The report does not convert receipt
currencies to the ledger currency nor provide a grand total in the ledger currency.
If the report includes all receipts available for remiance, there is a separate section for each remiance status within
each currency.
251
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
By default the report sorts the receipts within each currency section by remiance bank account, and provides subtotals
by receipt method, remiance method, remiance bank account and remiance status, and a grand total for the
currency.
• If you set the Order By parameter to Maturity Date, the report sorts receipts by maturity date and provides
subtotals by maturity date.
• If you set the Order By parameter to Receipt Number, the report sorts receipts by receipt number and provides
all of the default subtotals.
This table describes important column headings in the Receipts Awaiting Remiance Report.
Remiance Bank Account Name The name of the remiance bank account for the applicable receipts.
Customer Bank The name of the bank associated with the customer.
This table describes important row headings in the Receipts Awaiting Remiance Report.
Status The section title for a specic remiance status within a currency section.
Total for Receipt Method The total amount of all receipts with a given receipt method.
Total for Remiance Method The total amount of all receipts with a given remiance method.
Total for Remiance Account The total amount of all receipts for a given remiance bank account.
Total for Status The total amount of all receipts with a given remiance status for a receipt currency.
252
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
Total for Maturity Date The total amount of all receipts for a given maturity date.
Total for Currency The total amount of all receipts in the receipt currency.
If you enable the Ignore override option on the remiance batch, Receivables replaces the remiance bank information
on the receipt with the remiance batch bank information and includes the receipt in the remiance batch, without
reviewing either the receipt Allow override option seing or the remiance bank Override bank option seing.
If you don't enable the Ignore override option on the remiance batch, Receivables still replaces the remiance bank
information on the receipt with the remiance batch bank information and includes the receipt in the remiance batch
under these conditions:
Note: If the Allow override option on the receipt is not enabled, Receivables includes the receipt in
the remiance batch only if the receipt remiance bank is the same as the remiance batch bank.
253
Oracle Financials Cloud Chapter 2
Using Receivables Credit to Cash Process Customer Payments
In both cases, Receivables veries that both the receipt and the batch remiance banks have the same general ledger
accounts dened for remiances, and for unapplied, unidentied, and on-account receipts.
254
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Note: Credit card services are currently not available in Oracle Financials Cloud implementations.
Create or Edit Funds Capture Process Formats tab, Authorization section: Controls the formats and transmission
Proles Page Outbound Format choice list and Inbound congurations used to communicate with
Response Format choice list. the payment system.
Accounts tab: Authorization Transmission
Conguration choice list
Create Routing Rules Page All elds. • Routes funds capture transactions
to a payment system
• Determines the payment system
account and the funds capture
process prole to be used for
authorization processing.
Reorder Priority of Routing Rules Dialog All elds Reorders priority of routing rules.
Box
Set Rules Page All elds Species default payment systems that
are used if no routing rules are set up or if
none of the conditions in the routing rules
are met for the funds capture transaction.
255
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Validate
Open Connection with Payment System Payment
Instrument
Reserve
Receive Payment System Response
Funds
End
The authorization process for credit cards includes the steps described in the following table.
Step Description
Request authorization. The source product requests authorization. Oracle Fusion Receivables creates an automatic
receipt.
This process determines the payment system to which a transaction is sent, as well as the
funds capture process prole.
Route transaction to payment Routing rules are applied in the order of their priority. Payments performs selements or
system. refunds through the same payment system used for authorizations.
256
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Step Description
Reserve funds. After the issuing bank determines that the credit card is valid, it reserves funds.
Receive payment system response. Payments receives a response from the payment system and closes the connection. The
response contains a variety of information, depending on the success or failure of the
transaction.
For example, a credit card that receives a successful authorization stores the following data in
the table.
• Authorization code
• Amount
• Date
• Assigned funds capture process prole and payment system
Perform error-handling. Receivables displays any errors. You can resolve errors returned by Payments.
Store authorization reference. The source product stores the unique authorization reference.
257
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Create or Edit Funds Capture Creation Rules Selement Grouping Rules All check boxes
Process Proles
Create or Edit Funds Capture Creation Rules Selement Limit • Amount choice list
Process Proles • Conversion Rate Type
choice list
• Number of
Selements eld
258
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Part 2, as illustrated in the gure, includes the grouping of individual selements into batches and their submission to
the payment system. Part 2 is separate from Part 1 and begins when the Create Selement Batches process is manually
run or scheduled.
259
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Part 3, as illustrated in the gure, includes the receipt of the selement batch acknowledgment. Part 3 is separate from
Part 2 and begins when the Retrieve Selement Batch process is manually run or scheduled.
Receive
End Part 1 Settlement Validate Settements
Status
Start Part 2
Group Individual
Settlements into Batches
End Part 2
Retrieve
Start Part 3
Acknowledgments
End Part 3
The selement process for processor payment systems includes the steps described in the following table.
Step Description
Remit receipts. During receipt remiance, specically during the approval of a remiance batch, Receivables
submits corresponding selements requests as a funds capture process request to Payments.
260
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Step Description
The funds capture process request contains selements that need funds captured
electronically.
Read funds capture process prole For each selement, Payments reads the funds capture process prole and the payment
and payment system for each system information, as determined during the routing of the initial authorization transaction.
selement. Payments uses this information in subsequent processing.
Validate selements. 1. Payments validates all the selements sent as part of the funds capture process request
to ensure it has all the information required for payment processing.
2. Payments stores the selements in the database. The initial status of the selement
validation and storage is returned to Receivables.
Group individual selements into A selement batch is selement information from one or more funds capture process requests
batches. that's formaed and transmied to a payment system for selement.
Payments processes selements from all submied funds capture process requests and
groups them by payment systems and other grouping rules to create selement batches.
Optional grouping rules are set in the funds capture process prole.
Transmit selement batch to After the selement batch is formaed, it's transmied to the payment system for processing
payment system. and capture of funds as specied in the prole
Retrieve acknowledgments. 1. The payment system may create an acknowledgment that the batch was received or
processed.
2. Payments retrieves the acknowledgment le. This step and the subsequent step are
optional and depend on the level of service that's provided by your payment system.
Process status and update Payments reads the acknowledgment le and updates the statuses of the applicable
selements. selements. Receivables doesn't update receipt status based on this information, but restricts
follow-on transactions, such as refunds.
261
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
illustrate how selement grouping rule options are used to group selements into selement batches using a specic
funds capture process prole.
• Business unit
• First-party legal entity
• Selement date
Selement Amount External Payer Business Unit First-Party Legal Selement Date
that Owns the Entity that Owns
Transaction the Transaction
The Create Selement Batches program then groups the selements into the following selement batches:
Selement Batch 1
Selement Batch 1 contains Selements A and B because both selements have the same selement grouping
aributes as follows:
262
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Selement Batch 2
Selement Batch 2 contains Selement C because it has the following selement grouping aributes:
Selement Batch 3
Selement Batch 3 contains Selement D because it has the following selement grouping aributes:
If your company has multiple divisions, each division is represented by a separate payment system account. A payment
system account contains a relationship-specic value for each of the aributes required by the payment system. For
example, your payment system may require a Submier ID and Submier Password to be included in any message sent
to it. Each aribute is represented by a seing on the payment system account.
• Presenter's ID
• Submier's ID
263
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
If the values for the preceding payment system account seings are the same, selement transactions are grouped into
one selement batch. This occurs even when the following payment system account seings have dierent values:
• Division Number
• Merchant Name
Typically, separate selement batch les are created for each payment system account. Whether you generate
selement batches manually from the Oracle Enterprise Scheduler submission page or automatically, they are based on
a unique combination of the following:
• Internal payee
• Funds capture process prole
• Payment system account
264
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Note: The applicable process is called internally. Any required parameter values are known by Payments
without your intervention.
Name of Report and Process Report Description Options You Select for the Output
Automatic Process
265
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Generation
Before you can generate prenotications, an active debit authorization must exist between you and your customer.
During receipt method setup, Receivables provides an option for users to specify whether transactions are ISO 20022.
When an automatic receipt batch is created for ISO 20022 transactions, prenotications are automatically generated by
the Automatic Receipts Format Report.
Note: Before creating receipts, the Receivables user must know that they are for ISO 20022 transactions
and that he or she must subsequently download prenotications for delivery to customers. Receivables
doesn't notify Payments when it generates prenotications. The following table describes the steps that the
Receivables user can perform to submit the Automatic Receipts Format Report.
266
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Validation
Prenotications don't undergo any validations.
Delivery
After generation, prenotications are not automatically delivered to customers. Instead, they are manually downloaded
and then delivered to customers by E-Mail or through a country's postal system.
Prenotications are delivered according to the following guidelines for SEPA selement batches:
• A prenotication noties the debtor at least ve calendar days before collecting the payment, unless a dierent
time line has been agreed between you and the debtor.
• The lead time for submiing a SEPA CORE direct debit le (payment instrument governed by the rules of the
SEPA Core Direct Debit Scheme) to a bank is ve days for the rst use of a debit authorization and two days for
subsequent use.
• The lead time for submiing a SEPA B2B (SEPA Business to Business) direct debit le to a bank for business
debtors is one day for the rst use of a debit authorization and one day for subsequent use.
You and your customer may agree to a frequency of prenotication delivery. For example, with a recurrent SEPA direct
debit, you can agree to send a prenotication once a year. This can only be done, however, if the amount to be collected
stays the same. Otherwise, a new prenotication must be sent to your customer.
267
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
specify an overall status for the direct debit selement batch and individual statuses for some or all of the transactions.
For example, it's possible for a direct debit selement batch of ve transactions to have an overall status of ACCEPT,
while two individual transactions in the payment le have statuses of REJECT. In this case, the two transactions in the
acknowledgment le failed, but by inference the other three batch transactions that were not in the acknowledgment
le are inferred to have a status of ACCEPT.
Banks and payments systems use the payment status report to specify the following processing statuses:
The use of the payment status report is always governed by a bilateral agreement between your company and the bank.
A bilateral agreement species how your company wants to receive acknowledgments from the bank, whether:
A bilateral agreement can also specify whether your company wants to receive:
Payments processes the payment status report message according to the message structure specied in ISO 20022
payments message standards for the CustomerPaymentStatusReportV03 (pain.002.001.03).
The following aspects of payment status reports are discussed in this topic:
• Accepted status
• Rejected status
• Rejection and refund transactions
• ISO 20022 direct debt transaction ow
• Mapping of ISO 20022 reason codes to payment status and error codes
Accepted Status
Per ISO 20022 guidelines, group status represents the selement le status. Several group statuses are provided that
represent success. If you receive the payment status report message with the group statuses of ACCP, ACSP, or ACWC,
the batch status and the transaction status of all the transactions within the batch are updated as Accepted.
Payments supports the following success statuses at the transaction level of the payment status report:
268
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Rejected Status
The group status of RJCT applies to the batch. If you receive the payment status report message with the group status
of RJCT, the batch status and the transaction status of all the transactions within this batch are updated as Rejected.
Payments supports the following failure status at the transaction level of the payment status report: RJCT: Rejected
269
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
6 N/A N/A
You can view the results
of the Funds Capture
Acknowledgment process in
the Funds Capture Processes
section of the Funds Capture
work area, Overview page by
clicking View Output.
7 Receivables updates the status N/A If the ISO 20022 direct debit
of its receipts according to the transactions are accepted, the
270
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Mapping of ISO 20022 Reason Codes to Payments Status and Error Codes
When you receive an acknowledgment le from your bank or payment system, it can have accepted or rejected
transactions. The batch status, therefore, can be accepted, rejected, or partially accepted.
The rejection reasons that can appear in an acknowledgment le correspond to Payments status and error codes on the
following levels:
• Batch level mapping
• Transaction level mapping
ISO Reason Code ISO Reason Code SEPA Reason IBY Batch Status IBY Status
Name (IBY_BATCHES_ALL.STATUS)
(IBY_TRXN_SUMMARIES_ALL.STAT
ISO Reason Code ISO Reason Code Name SEPA Reason IBY Status
(IBY_TRXN_SUMMARIES_ALL.
STATUS)
271
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
ISO Reason Code ISO Reason Code Name SEPA Reason IBY Status
(IBY_TRXN_SUMMARIES_ALL.
STATUS)
BE01 InconsistentWithEndCustomer Debtor's name does not match 5 (Payment System Error)
with the account holder's
name.
MD02 MissingMandatoryInformationInMandate
Mandate data missing or 5 (Payment System Error)
incorrect
MS02 NotSpeciedReasonCustomerGenerated
Refusal by the Debtor 5 (Payment System Error)
MS03 NotSpeciedReasonAgentGenerated
Reason not specied 5 (Payment System Error)
272
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
ISO Reason Code ISO Reason Code Name SEPA Reason IBY Status
(IBY_TRXN_SUMMARIES_ALL.
STATUS)
RR01 MissingDebtorAccountOrIdentication
Regulatory reason 5 (Payment System Error)
SL01 DueToSpecicServiceOeredByDebtorAgent
Specic Service oered by the 5 (Payment System Error)
Debtor Bank
• Mixed Grouping: Each le contains several selement batches. Each selement batch contains several
transactions.
273
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
A group is created with the least common aributes. For example, if there are three transactions with the same
debtor but dierent mandates sequence types, such as rst, recurring, or one-o, then Payments creates three
separate groups. However, if two of the transactions have same mandate sequence type, then two groups are
created.
• Grouped: Each le contains only one selement batch. The selement batch contains several transactions.
• Single: Each le contains several selement batches. Each selement batch contains only one transaction.
Note: Payments only supports mixed grouping per the SEPA requirements.
The payment information level is mandatory and repetitive. Repetitive means that one or more blocks of payment
information can be included in a SEPA direct debit message format le. The payment information level contains
elements related to the credit side of the transaction, such as the following:
• Payment method
• Number of transactions
• Group identier
• Creditor legal entity
• Creditor business unit
• Creditor's bank account details
• Internal bank account
• Currency
• Charge bearer
• Creditor identication number
• Selement date
• Sequence type
• Service level
274
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
• Local instrument
• Category purpose
• Charge bearer
• Collection date
• Creditor details
Note: The preceding elements always appear in the SEPA direct debit message format.
Both SEPA and CGI (Common Global Implementation) are initiatives that promote wider acceptance of ISO20022 as the
common XML payments standard used between businesses and banks. They can dier, however, in element denition,
depending on whether or not a debit authorization is used.
The following table describes dierences between the SEPA and CGI direct debit messages as they relate to the
denition of certain message elements, which is determined by the existence or nonexistence of a debit authorization.
Element SEPA and CGI Direct Debit Messages CGI Direct Debit Messages without a
with a Debit Authorization Debit Authorization
Creditor Creditor (First Party Legal Entity) per the Creditor (First Party Legal Entity) related
debit authorization. to remiance bank account used on the
invoice.
Ultimate Creditor Creditor (First Party Legal Entity) per Creditor (First Party Legal Entity) per the
the invoice if dierent than debit invoice.
authorization.
When you select payment grouping on the Create Funds Capture Process Prole page, the transactions are grouped
within the selement batch based on the values of the selected parameters. The logical grouping elements, however,
are either all enabled or all disabled, depending on whether or not you select the Enable grouping option in the
Payment Grouping Rules section on the Create Funds Capture Process Prole page. The logical grouping elements are
the same for SEPA, as well as for CGI.
The direct debit transaction information level contains elements such as the following:
• Payment identier details
• Payment amount
• Debit authorization details
• Ultimate creditor
• Debtor
• Debtor's bank account
• Purpose code
275
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
• Remiance information
Note: Some of the preceding elements appear conditionally in the SEPA direct debit message format.
The batch booking option on the Create Funds Capture Process Prole page determines whether the batch
booking element is set in the SEPA direct debit message. If you select the batch booking option, it applies to all
transaction groups of the payment le.
Validation Description Single Euro Payments Areas Core Direct ISO20022 Direct Debit Common Global
Debit 5.0 (pain.008.001.02) Implementation 2.0 (pain.008.001.02)
Yes No
Debit authorization presence:
Yes Yes
Active debit authorization:
276
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Validation Description Single Euro Payments Areas Core Direct ISO20022 Direct Debit Common Global
Debit 5.0 (pain.008.001.02) Implementation 2.0 (pain.008.001.02)
Yes Yes
Veries that the following required elds
are present on a debit authorization:
Yes Yes
Veries the following data:
Yes No
Payments supports the following
additional SEPA validations:
277
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Validation Description Single Euro Payments Areas Core Direct ISO20022 Direct Debit Common Global
Debit 5.0 (pain.008.001.02) Implementation 2.0 (pain.008.001.02)
No Yes
Payments supports the following
additional CGI validations:
Yes Yes
Veries the following data that is required
for the ISO 20022 direct debit format:
Yes Yes
Match payment system account aributes:
278
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Tip: Allow international payments can be selected only when you provide the name of the
bank and the branch.
12. Enter the IBAN (International Bank Account Number) in the IBAN eld if you are seing up a customer bank
account in a European country.
279
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Note: Validation of the IBAN is based on the country for which the customer bank account is
set up.
13. From the Currency choice list, select the currency in which payments are received.
If you select a currency, then the customer bank account is used to pay invoices in that currency only. If you
don't select a currency, then the customer bank account is considered multicurrency and is used to pay invoices
in any currency.
2. From the Conversion Rate Agreement Type choice list, select the type of conversion rate agreement you have
with the customer.
3. In the Conversion Rate eld, enter the conversion rate for which one currency can be exchanged for another.
4. In the Conversion Rate Agreement Number eld, enter the number of the conversion rate agreement with the
customer that species the currency in which payments are made.
5. In the Check Digits eld, enter one or multiple digits.
6. In the Secondary Account Reference eld, you can optionally enter additional account information.
7. In the Agency Location Code eld, enter the eight-digit value that identies a Federal agency as the customer.
280
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
4. To add a row from which to select another joint bank account owner, click the green plus.
On the simplied bank account page, you can also update the bank and branch if you created the bank account with the
Oracle Cash Management prole option named Use Existing Banks and Branches set to Yes. When you update the bank
and branch, you must select the same prole option.
To initiate collection, SEPA countries require banks to use the ISO 20022 XML message standards, known as SEPA data
formats, which are legally binding between banks. Similarly, Oracle recommends that you use the SEPA formats for
initiating payments. Banks can, however, continue to accept other formats from their customers for the initiation of
SEPA payments.
In the Create or Edit Debit Authorization dialog box, you can perform the following tasks:
• Enter or edit debtor details
• Enter or edit creditor details
• Enter or edit authorization details
281
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
• View history
Navigation to the Create Debit Authorization dialog box: Receivables > Billing > Manage Customers link > Manage
Customers page > Search on Bank Account Number > Site link > Bank Account tab > Payment Instruments
section.
For SEPA direct debits, all transactions are in euro. If your accounts or those of your customer are in any other currency,
the funds for the SEPA direct debits must be converted to euro.
The creditor identication number remains the same over time to enable your customer and his bank to return to you
for refunds, complaints, or to conrm the existence of a SEPA debit authorization when you present a SEPA direct debit
collection notication.
Note: A one-o SEPA debit authorization cannot be used for any subsequent transactions.
You can also specify the intended frequency of collection against a debit authorization. Frequency can range from daily
to annually.
282
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Another optional aribute is the nal collection date, which is the intended date of the last collection against a debit
authorization.
SEPA debit authorizations are versioned as they are updated. The application assigns a 1 to the rst version of a debit
authorization. Version 1 increases by one due to a change in:
If any of the preceding values change, a reason for the change to the SEPA debit authorization is required in the Edit
Debit Authorization dialog box.
• You can specify both a nal collection date and a cancellation date.
• A canceled SEPA debit authorization cannot be reenabled.
• A SEPA debit authorization automatically expires when 36 months elapse after the last initiated direct debit.
View History
In the History section, you can see all the past versions of the SEPA debit authorization.
283
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping Mapping
Creation Date Time <CreDtTm> 1.2 File generation system Same as SEPA
date
Tag Structure:
<CreDtTm>20100406T23:
56: 55</CreDtTm>
284
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping Mapping
<Id>SEPA_
INT_IDNT</Id>
<Issr>SEPA_ INIT_
ISUR</Issr>
</Othr>
</OrgId>
</Id>
</InitgPty>
Postal Address <PstlAdr> 9.1.1 AOS element. Not used Not supported for CGI.
[AOS element that can
be supported for free in
future.]
Private Identication Not Applicable Not Applicable Not supported Not Used
Country of Residence <CtryOfRes> 9.1.33 AOS element. Not used Not supported for CGI.
[AOS element that can
be supported for free in
future.]
Forwarding Agent <FwdgAgt> 1.9 AOS element. Not used Not Used
285
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
286
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
287
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
<LclInstrm> <LclInstrm>
<Cd>CORE</Cd> <Cd>XXXX</Cd>
</LclInstrm> </LclInstrm>
288
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
Address Type Not Applicable 9.1.2 AOS element. Not Same as SEPA
supported.
Address Line Not Applicable 9.1.11 AOS element that can Primary address of the
be supported for free. legal entity selected on
the mandate.
Street Name Not Applicable 9.1.5 AOS element that can Same as SEPA
be supported for free.
289
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
Building Number Not Applicable 9.1.6 AOS element that can Same as SEPA
be supported for free.
Post Code Not Applicable 9.1.7 AOS element that can Primary address of the
be supported for free. legal entity selected on
the mandate.
Town Name Not Applicable 9.1.8 AOS element that can Primary address of the
be supported for free. legal entity selected on
the mandate.
Country Subdivision Not Applicable 9.1.9 AOS element. Not Primary address of the
supported. legal entity selected on
the mandate.
Identication Not Applicable 9.1.12 AOS element that can Same as SEPA
be supported for free.
Country of Residence <CtryOfRes> 9.1.33 AOS element. Not Primary address of the
supported. legal entity selected on
the mandate.
290
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
Creditor Agent <CdtrAgt> 2.21 BIC of the internal bank BIC of the internal bank
branch of the bank branch of the bank
account aached to the account aached to the
mandate mandate, as well as the
branch number.
Tag structure:
<CdtrAgt>
<FinInstnId>
<BIC>BOFABE3X</
BIC>
</FinInstnId>
</CdtrAgt>
Creditor Agent Account <CdtrAgtAcct> 2.11 AOS element. Not Same as SEPA
supported.
Postal Address <PstlAdr> 9.1.1 AOS element. Not Passed only when
supported. Ultimate Creditor
(UltCdtr) is populated.
Private Identication Not Applicable 9.1.21 Not supported at this Same as SEPA
level.
291
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
Charges Account Agent <ChrgsAcctAgt> 2.26 AOS element. Not Not Used
supported
292
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal )
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Direct Debit <DrctDbtTxInf> 2.28 Set of elements used Set of elements used
Transaction to provide information to provide information
Information on the individual on the individual
transactions included transactions included
in the message. in the message.
293
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
294
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
295
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
296
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
<IBAN>GB52CHAS60924235582306</
IBAN>
</Id>
</ OrgnlDbtrAcct>
<OrgnlDbtrAgt>
<FinInstnId>
<Othr>
<Id>SMNDA</Id>
</Othr>
</FinInstnId>
</ OrgnlDbtrAgt>
</ AmdmntInfDtls>
</MndtRltdInf>
<CdtrSchmeId>
<Id>
<PrvtId>
<Othr>
<Id>1234</Id>
<SchmeNm>
<Prtry>SEPA</ Prtry>
</SchmeNm>
</Othr>
</PrvtId>
</Id>
</CdtrSchmeId>
</DrctDbtTx>
297
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Date Of Signature <DtOfSgntr> 2.49 Date on which the Date on which the
debtor has signed the debtor has signed the
direct debit mandate. direct debit mandate.
298
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Original Creditor Agent <OrgnlCdtrAgt> 2.54 AOS element. Not Same as SEPA
supported
Original Creditor Agent <OrgnlCdtrAgtAcct> 2.55 AOS element. Not Same as SEPA
Account supported
Original Debtor Agent <OrgnlDbtrAgt> 2.58 Not captured on debit Same as SEPA
authorization
Original Debtor Agent <OrgnlDbtrAgtAcct> 2.59 AOS element. Not Not Used
Account supported
Original Final Collection <OrgnlFnlColltnDt> 2.60 AOS element. Not Not Used
Date supported
First Collection Date <FrstColltnDt> 2.63 AOS element. Not Date of the selement
supported for which the mandate
was rst used.
299
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Final Collection Date <FnlColltnDt> 2.64 AOS element. Not Mandate Final
supported Collection Date
Prenotication Date <PreNtfctnDt> 2.68 This element is not AOS element. Not
supported. supported
300
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Private Identication Not Applicable 9.1.21 AOS element. Not Not Supported.
supported
Debtor Agent <DbtrAgt> 2.70 BIC of the branch BIC of the internal bank
of Customer branch of the bank
Bank Account by account aached to the
FinancialInstitutionIdentication
mandate, as well as the
branch number.
Tag structure:
<DbtrAgt>
301
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
<FinInstnId>
<BIC>BOFABE3X</
BIC>
</FinInstnId>
</DbtrAgt>
Debtor Agent Account <DbtrAgtAcct> 2.71 AOS element. Not Not used.
supported
302
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
Address Type Not Applicable 9.1.2 AOS element. Not Not Supported.
supported
Street Name Not Applicable 9.1.5 AOS element. Not Not Supported.
supported
Building Numb Not Applicable 9.1.6 AOS element. Not Not Supported.
supported
Post Code Not Applicable 9.1.7 AOS element. Not Not Supported.
supported
Town Name Not Applicable 9.1.8 AOS element. Not Not Supported.
supported
Country Subdivision Not Applicable 9.1.9 AOS element. Not Not Supported.
supported
Debtor Account <DbtrAcct> 2.73 Customer Bank For CGI, we can pass
Account IBAN is the bank account
populated by IBAN number in other tag in
addition to IBAN.
Tag Structure:
<DbtrAcct>
<Id>
<IBAN>
303
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
IT60X0542811101000000123456
</IBAN>
</Id>
</DbtrAcct>
Instruction for Creditor <InstrForCdtrAgt> 2.75 AOS element. Not Not supported.
Agent supported.
Code <Cd> 2.77 SUPP is passed during Purpose Code from the
formaing. Payer. If null, from the
FCPP.
Tag Structure:
<Purp>
<Cd>SUPP</Cd>
</Purp>
304
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
305
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Message Element <XMLTag> ISO Element Number SEPA Implementation CGI Implementation
Mapping proposal Mapping proposal
But you can move a selement batch and its transactions from an intermediary status to a Success status under certain
conditions. When you submit the Retrieve Funds Capture Acknowledgments process, the selement batch and its
transactions update from an intermediary status to Success only if:
• You select a reference number from the Selement Batch Reference choice list.
• The funds capture processing type on the funds capture process prole is Bank Account
• These formats aren't specied in the Formats tab of the funds capture process prole:
306
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
the protocol named Secure File Transfer Retrieval Protocol for Static File Names. Then, on the Create Transmission
Conguration page in the Value eld for the Remote File Name parameter, you can enter an asterisk in the le name as
a wildcard character. By entering the asterisk, you can retrieve multiple acknowledgment les from your bank in a single
aempt.
For example, suppose you have two les:
• PAY_ACK_01012019.xml
• PAY_ACK_02012019.xml
To retrieve both les in one aempt, enter PAY_ACK_*.xml in the Value eld of the Remote File Name parameter on the
Create Transmission Conguration page.
To retrieve funds capture acknowledgment les from your bank, you have the option of using either static le names,
dynamic le names with asterisks, or both. After you opt in to the applicable feature, you can connect with banks that
support both static le names and dynamic le names.
Overview
The Funds Capture Accompanying Leer is a predened funds capture report that is manually delivered to your
payment system or bank. The report accompanies a selement batch le and summarizes its contents
307
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
The following gure illustrates an example of the Funds Capture Accompanying Leer.
Key Insights
The following table lists the dierence between the formal Funds Capture Accompanying Leer report name and the
process name.
308
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Funds Capture Accompanying Leer Create Selement Batch Accompanying .PDF le
Formats Leer
Navigate: Navigator > Setup and Maintenance > Search: Tasks pane: Manage Funds Capture Process
Proles > Go to Task > Select Processing Type > Create buon.
◦ Oering: Financials
◦ Functional Area: Customer Payments
◦ Task: Manage Funds Capture Process Proles
2. On the Manage Funds Capture Process Proles page, select a processing type from the Select Processing Type
choice list and click Create.
3. On the Create Funds Capture Process Prole page, Formats tab, Selement section, select options for the
Outbound Format, Inbound Response Format, and the Accompanying Leer Format.
4. Sign in as a manager.
5. From the Accounts Receivables work area, click the Funds Capture icon.
6. Click the Tasks icon.
7. Click the Selement Batch Accompanying Leer link.
8. The parameters page for the Funds Capture Accompanying Leer appears.
9. From the Selement Batch Reference choice list, select the applicable selement batch reference number and
click Submit. A conrmation message displays with a process ID.
Report Parameters
The following table describes the process parameter.
Name Description
Selement Batch Reference Application-assigned reference number for the selement batch.
309
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
FAQ Answer
When do I use this report? The Funds Capture Accompanying Leer is used when you want to summarize the contents of
a selement batch and manually send the summary and the selement batch to the payment
system or bank.
• Manually deliver the Funds Capture Accompanying Leer to your payment system or
bank, along with the selement batch.
Overview
The Funds Capture Payer Notication report is a predened funds capture report that can be faxed, emailed as a PDF
aachment, printed, or mailed to customers after a selement or selement batch is transmied to your payment
system or bank. The report informs customers of a funds capture transaction that will charge their credit card or bank
account.
310
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
This image illustrates an example of the Funds Capture Payer Notication report.
Key Insights
This table lists the the formal Funds Capture Payer Notication report name and the process name that's used to
manually generate the report.
◦ Oering: Financials
◦ Functional Area: Customer Payments
◦ Task: Manage Funds Capture Process Proles
311
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
2. On the Manage Funds Capture Process Proles, from the Select Processing Type choice list, select a processing
type.
3. Click Create.
4. On the Funds Capture Process Prole page, Formats tab, Notication to Payer section, from the Format choice
list, select the Receipt of Payment Notication format.
5. From the Delivery Method choice list, select Email.
6. Sign in as an Oracle Receivables user.
7. Click the Billing icon.
8. On the Billing Tasks pane, click the Create Customer link and create a customer, a customer address, and a
customer site.
9. On the Account Site page, select the Payment Details tab.
10. In the Receipt of Payment Notication Preferences section, from the Debit Advice Delivery Method choice
list, optionally select Email with .pdf as aachment. This option lets you aach the Funds Capture Payer
Notication report to an email as a PDF aachment. If you select the Email option, the Funds Capture Payer
Notication report is sent as HTML in the body of the email.
11. In the Debit Advice Email ID eld, enter a valid email.
12. In the Setup and Maintenance work area, select:
◦ Oering: Financials
◦ Functional Area: Customer Payments
◦ Task: Manage Internal Payees
13. On the Manage Internal Payees page, click the Create icon.
14. On the Create Internal Payee page, Notication to Payer section, enter a valid email in the From Email eld and
the subject that you want to see in the notication email in the Subject eld.
Report Parameters
This table describes the process parameters.
Name Description
312
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Name Description
From Selement Date Starting date within a date range of selement transactions.
From Payment System Order Number Order number generated by Payments, which identies the rst selement transaction to the
payment system.
To Payment System Order Number Order number generated by Payments, which identies the last selement transaction to the
payment system.
Allow Sending Replacement Copy The inclusion of selements in the Funds Capture Payer Notication report that were included
in a previous report if, for example, the customer requests a duplicate copy of the Funds
Capture Payer Notication report.
FAQ Answer
When do I use this report? The Funds Capture Payer Notication report is used when you want to inform the customer
of a funds capture transaction that will charge the customer's credit card or bank account. By
informing customers of expected debits to their bank accounts, they can maintain sucient
balances so that payments aren't rejected.
It is considered a best practice to inform your customers that funds capture transactions will
charge their credit card or bank account.
313
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Caution: On a live instance of Payments, it is strongly recommended that you disable the transaction testing
functionality and unassign it from the payment administrator.
314
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
Following the Payment Card Industry Data Security Standard (PCI DSS) security standards, the CVN isn't stored, even
temporarily, in the application.
Note: CVN capture during transaction authorization is currently not allowed. However, you may provide CVN
during credit card token creation.
Credit card payments made without required entry of a CVN, follow the usual process where you create a transaction
type of Invoice, submit the Create Automatic Receipts process, and an authorization is created during automatic receipt
creation.
315
Oracle Financials Cloud Chapter 3
Using Receivables Credit to Cash Manage Funds Capture
316
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
You schedule and run all Receivables reports from the Scheduled Processes work area. You can also access and open
all reports in the Reports and Analytics work area.
Print Invoices Template Layout for printing invoices. Includes information about the customer, due date, line amount,
tax amount, and outstanding balance.
Print Credit Memos Template Layout for printing credit memos. Includes information about the customer, application date,
line amount, and total amount applied.
Print Debit Memos Template Layout for printing debit memos. Includes information about the customer, due date, line
amount, and outstanding balance.
317
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Print Chargebacks Template Layout for printing chargebacks. Includes information about the customer, due date, line
amount, and outstanding balance.
Print Summary Balance Forward Bills Layout for printing balance forward bills in summary mode. Includes information on the
Template beginning balance, summary information of current customer billing activity, and ending
balance for the billing cycle.
Print Detailed Balance Forward Bills Layout for printing balance forward bills in detail mode. Includes information on the beginning
Template balance, details of current customer billing activity, and ending balance for the billing cycle.
Print Bills Receivable Template Layout for printing bills receivable. Includes information about the customer drawee, drawee
contact, creation date, transactions assigned to the bill, and total bill amount.
Accounting Reports
Use these reports to review and analyze Receivables accounting information.
Bad Debt Provision Report Provides information for reviewing bad debt exposure and provisioning based on percent
collectible assigned to the customer. Includes transaction number, balance due amount, and
bad debt provision amount in the ledger currency.
Invoices Posted to Suspense Report Provides a list of all transactions that have revenue amounts posted to suspense accounts as
a result of running the Import AutoInvoice process. Includes information on transaction class,
customer, transaction date, and transaction amount by business unit.
Potential Reconciling Items Report Provides a list of journal items that may potentially post to incorrect general ledger accounts.
Includes customer account number, payment number, transaction number, and credit and
debit amounts by reporting level, reporting context, accounting date, and balancing segment.
Billing Reports
Use these reports to review and analyze Receivables billing and related transaction information.
Billing History Report Provides a summarized history of transactions and activities against them by customer site for
a specied date range. Includes information on original transaction amount, current balance
due, sum of all payments applied to the transaction, total credit memo amounts against the
transaction, and total adjustment amounts to the transaction.
318
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Import AutoInvoice Execution Report Report for the process that imports transactions from other source systems into Receivables.
Includes information about both successful and rejected transactions by transaction type,
customer, transaction number, and transaction date.
Print Adjustments Report Prints information about adjustments associated with specied transactions and customers by
business unit, adjustment number, and transaction number.
Transaction Details Report Lists invoices, credit memos, debit memos, and chargebacks for review. Includes information
about transaction header, transaction lines, sales credits, revenue accounts, account sets, and
transaction exelds by business unit, transaction number, and transaction type.
Automatic Receipt Creation and Report for the process that creates automatic receipts and receipt remiances in a batch.
Remiance Execution Report Includes information about automatically generated receipts, remied receipts, and data
validation errors by batch.
Bank Risk Report Provides information about receipts that are currently at risk with the remiance bank.
Includes information about the remiance batch, receipt, and receipt amount by business unit,
remiance bank branch, and remiance bank account.
Clear Receipts Automatically Report for the process that clears receipts automatically. Includes information about the
Execution Report clearing of customer receipts by remiance bank account, receipt number, and customer.
Create Automatic Receipt Write-os Report for the process that writes o unapplied amounts on selected receipts. Includes
Execution Report information about the receipt write-os by currency, customer, receipt number, amount, and
date.
Create Customer Statements Report for the process that generates customer statements. Prints customer billing
Execution Report information in a format presentable to the customer. Includes information on invoices, debit
memos, chargebacks, payments, on-account credits, credit memos, adjustments, and past due
information.
Customer Account Status Report Provides a list of customer open items and the total balance due based on customer account
status for the specied ledger currency.
Customer Balances Revaluation Displays information related to the dierence between the original customer balance and
Report the revaluated balance for manually adjusting the general ledger. Includes the customer
balance and the open items that make up that balance by business unit, revaluation period,
and customer.
319
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Document Number Audit Report Provides a list of document numbers assigned to transactions, adjustments, and receipts to
help identify missing document numbers for a business unit, document sequence name, and
document number range. Includes information about the status, customer, currency, and
amount of the transactions, adjustments, and receipts.
Format Automatic Receipts Report Prints automatic receipts in a specied receipt batch so that they can be sent to customers for
conrmation. Includes receipt number, receipt date, currency, and the transactions applied to
each receipt.
Generate Late Charges Report Prints information on late charges for transactions that are overdue or have late payments by
batch name. Includes transaction number, due date, and overdue amount of transactions.
Process Receipts Through Lockbox Report for the process that creates receipts for payments made through lockbox. Includes
Execution Report information on lockbox receipts and data validation errors for each transmission from the
bank.
Receipts Days Late Analysis Report Provides the cost of late customer payments by calculating weighted average days late for
each customer. Includes information about the transaction number, transaction type, due date,
receipt number, receipt days late, and receipt weighted days late by business unit, customer,
transaction number, and collector.
Receipts Awaiting Bank Clearance Provides a list of receipts waiting to be cleared by the remiance bank. Includes information
Report about the remiance bank account name, remiance batch date, maturity date, receipt
number and receipt amount by business unit, maturity date, and currency.
Receipts Awaiting Remiance Report Provides a list of receipts waiting to be remied to the bank. Includes information about the
remiance bank account name, maturity date, receipt number, and receipt amount by business
unit, remiance bank account, maturity date, and currency.
Receivables Aging by General Ledger Provides information about outstanding receivables balances by general ledger account as
Account Report of a specic date. Includes information about customer, transaction number, due date, and
outstanding amount by balancing segment, transaction as-of date, aging buckets, currency,
and customer.
Receivables Open Items Revaluation Displays the amount needed to manually adjust general ledger account balances to reect the
Report dierence between the original and revalued customer open items. Includes information about
transaction number, due date, currency, open original amount, conversion rate, open ledger
currency amount, revaluation rate, and revaluation open amount by business unit, revaluation
period, conversion rate type and balancing segment.
Receivables Projected Gains and Compares the revalued amount of foreign currency transactions with the entered amount
Losses Report and prints the projected unrealized gain or loss. Includes information about the currency,
entered amount, ledger currency amount, revaluation rate, and the revaluation gain and loss
by business unit, ledger currency, customer, and transaction number.
Recognize Revenue Execution Report Report for the process that recognizes revenue and creates revenue distributions for
transactions that use invoicing and revenue scheduling rules. Includes information about
revenue accounting distributions and unprocessed or partially processed transactions for
customer billing.
320
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Reversal Status Report Provides information about the status of automatic receipt reversals processed for a
selement batch. Includes the receipt date, receipt number, receipt amount, reversal reason
code, and a description of automatic receipt reversals that were unsuccessful.
Automatic Bills Receivable Report for the process that creates a bills receivable remiance from bills receivable. Provides
Remiance Execution Report the details of bills receivable remied to the bank to initiate collection from customers.
Automatic Bills Receivable Report for the process that creates bills receivable from transactions. Lists the transactions
Transactions Batch Report assigned to each bill receivable.
Close Matured Bills Receivable Report for the process that creates and applies receipts for standard remied bills receivable,
Execution Report and applies receipts and eliminates risk on bills receivable factored with recourse. Lists the
changes to each bill receivable and shows all receipts that were cleared by the process run.
Print Bills Receivable Report Prints bills receivable either individually, belonging to a bills receivable batch, or belonging to a
bills receivable remiance batch.
Neing Selement Leer Prints a leer that provides details of Payables and Receivables transactions in a neing
selement.
Neing Reversal Leer Prints a leer that provides details of Payables and Receivables reversed transactions in a
neing selement.
Neing Selement Report Lists the Payables and Receivables transactions belonging to a specic neing selement in
PDF format.
Neing Selement Listing Lists the Payables and Receivables transactions belonging to a specic neing selement in
spreadsheet format.
321
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Prepare Receivables to General Extracts and prepares transaction and accounting information for reconciling Receivables to
Ledger Reconciliation the General Ledger. You must run this process before you can use the Receivables to General
Ledger Reconciliation Report.
Receivables to General Ledger Provides both summary and detailed reconciliation of receivables data to the general ledger.
Reconciliation Report The summary report displays receivables and accounting beginning and ending balances,
as well as summarized activity for the period and how this activity was accounted. The detail
reports display the real-time details that make up balances from the summary report, and
indicate potential causes for dierences between actual and reconciling amounts.
Related Topics
• Reports and Analytics Work Area and Panel Tab
Subject Areas
To create an analysis, you begin by selecting a subject area and then selecting columns of information to include in
the analysis. For example, to create an analysis of transaction information, you begin by selecting the Receivables -
Transactions Real Time subject area. Subject areas are based around a business object or fact. In this example, the
subject area is based on the column in the transactions tables.
322
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Folders
Each subject area has one or more fact folders and a number of dimension folders. Fact folders contain aributes that
can be measured, meaning that they are numeric values like transaction line amounts. Fact folders are usually last in
the list of folders and are usually named after the subject area. Dimension folders contain aribute and hierarchical
columns like customer information.
Some folders appear in more than one subject area, such as Time. These are referred to as common folders or common
dimensions.
Each folder within a subject area may have a dierent level of granularity. For example:
Aributes
Each dimension folder contains aributes (columns), such as customer category and customer codes.
323
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
These two gures illustrate the structure of subject areas, folders, and aributes.
324
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Related Topics
• How Data Is Structured for Analytics
325
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• RA_CUSTOMER_TRX
• RA_CUSTOMER_TRX_LINES
• RA_CUST_TRX_LINE_SALESREPS
• RA_CUST_TRX_LINE_GL_DIST
• AR_PAYMENT_SCHEDULES
TOTAL NA NA $6400
326
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Note: Because the sample invoice had freight at the header level, it is not linked to any line and therefore the
link_to_cust_trx_line_id column is null.
The RA_CUST_TRX_LINE_SALESREPS table reects the sales credits alloed to salespersons 1492, 1525, and 1624. The
revenue and non-revenue amounts associated with the rst line item of the invoice are split between salesperson 1492
and salesperson 1525. Salesperson 1624 gets the complete sales credit for the second line item of the invoice, while all
three share the credit for the header level freight.
CUST_TRX_LINE_SALESREP_ID
SALES_REP_ID CUSTOMER_TRX_LINE_ID
REVENUE_AMOUNT_SPLIT
NON_REVENUE_AMOUNT_SPLIT
PREV_CUST_TRX_LINE
_SALESREP_ID
327
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
CUST_TRX_LINE_SALESREP_ID
SALES_REP_ID CUSTOMER_TRX_LINE_ID
REVENUE_AMOUNT_SPLIT
NON_REVENUE_AMOUNT_SPLIT
PREV_CUST_TRX_LINE
_SALESREP_ID
CUST_TRX_LINE_GL_DIST_ID
CODE_COMBINATION_ID CUSTOMER_TRX_LINE_ID ACCOUNT_CLASS AMOUNT
Note: If you enter an invoice with rules, the account distributions are not built when the invoice is rst
created. Instead the RA_CUST_TRX_LINE_GL_DIST table stores an account set, which represents how the
actual distribution rows should be created and what percentage of the actual distribution should be allocated
to each account. Account sets can be identied by a Y in the account_set_ag column. The actual distribution
records are built when you run revenue recognition.
The AR_PAYMENT_SCHEDULES table reects the current status of Invoice I-101. The invoice has a status of OP (open)
and an amount_applied of NULL, because no payment has been applied against it. Once payment is received in full, the
status will change to CL (closed), the amount_applied will change to 6400, and the amount_due_remaining will be zero.
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE CUSTOMER_TRX_ID
CASH_RECEIPT_ID
TRX_NUMBER STATUS AMOUNT CLASS
_REMAINING _APPLIED
328
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE CUSTOMER_TRX_ID
CASH_RECEIPT_ID
TRX_NUMBER STATUS AMOUNT CLASS
_REMAINING _APPLIED
Note: Receivables handles debit memos the same as invoices in all tables, except that in the
AR_PAYMENT_SCHEDULES table it sets the class of the payment schedule to DM instead of INV.
Credit Memos
When you enter a credit memo against an invoice, Receivables creates records in the following tables:
• RA_CUSTOMER_TRX
• RA_CUSTOMER_TRX_LINES
• RA_CUST_TRX_LINE_SALESREPS
• RA_CUST_TRX_LINE_GL_DIST
• AR_PAYMENT_SCHEDULES
• AR_RECEIVABLE_APPLICATIONS
Note: The previous_customer_trx_id column references the original transaction you have credited.
CUSTOMER_TRX_LINE_ID
CUSTOMER_TRX_IDLINK_TO_CUST_TRX_LINE_ID
LINE_TYPE EXTENDED_AMOUNT
PREVIOUS_CUSTOMER_TRX_ID
PREVIOUS_CUSTOMER_TRX
329
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Note: Based on the sample credit memo, Receivables inserts two records into the
RA_CUSTOMER_TRX_LINES table. The total value of the credit memo is prorated between the invoice and tax
lines associated with line 1 of the original invoice. The previous_customer_trx_line_id column references the
customer_trx_line_id column of the original invoice you have credited.
CUST_TRX_LINE_SALESREP_ID
SALES_REP_ID CUSTOMER_TRX_LINE_ID
REVENUE_AMOUNT_SPLIT
NON_REVENUE_AMOUNT_SPLIT
PREV_CUST_TRX_LINE
_SALESREP_ID
Note: Assuming the credit memo is only applied to the rst line of the invoice, salesperson 1492 and
salesperson 1525 will split the loss of the sales credit. The prev_cust_trx_line_salesrep_id column references
the original sales credit from the original invoice.
CUST_TRX_LINE_GL_DIST_ID
CODE_COMBINATION_ID CUSTOMER_TRX_LINE_ID ACCOUNT_CLASS AMOUNT
Note: Because this is a credit memo, the revenue and tax accounts will be debited and the receivable account
will be credited.
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_CREDITED
330
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Note: The class column of the credit memo payment schedule is CM. The example credit memo has a status
of CL (closed) and the amount_applied column equals the amount of the credit memo, because the credit
memo has been applied to an invoice. The amount_due_original column equals the amount of the credit
memo, -1000. The amount_due_remaining is zero because the credit memo has been applied to an invoice.
After applying the credit memo, the AR_PAYMENT_SCHEDULES table stores Invoice I-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_CREDITED
Note: Receivables updates the payment schedule of the invoice to reect the application of the credit memo.
The amount_due_remaining column is reduced by -1000 and the amount_credited column is -1000, the
amount of the credit memo.
RECEIVABLE_APPLICATION_ID
AMOUNT_APPLIED
STATUS PAYMENT_SCHEDULE_ID
CUSTOMER_TRX_ID
CASH_RECEIPT_ID
APPLIED_PAYMENT_SCHEDULE_ID
APPLIED_CUSTOMER_TR
Receivables uses the AR_RECEIVABLE_APPLICATIONS table to store the mapping of the credit memo to the invoice
being credited. The payment_schedule_id and customer_trx_id columns contain the credit memo data, while the
applied_payment_schedule_id and applied_customer_trx_id reference the original invoice. If the credit memo applies
to an invoice with multiple payment schedules, a record is inserted into AR_RECEIVABLE_APPLICATIONS for each
payment schedule of the invoice. The code_combination_id column, which is not shown, stores the receivable account
of the invoice. However, when the transaction is posted to the general ledger it posts as two distributions. One entry is
posted to the receivable account of the credit memo, as it is stored in the RA_CUST_TRX_LINE_GL_DIST table, and the
other entry is posted to the receivable account of the invoice, as it is stored in the RA_CUST_TRX_LINE_GL_DIST table.
For a standard credit memo, the receivable account of the credit memo is debited, while the receivable account of the
invoice is credited. Normally, the receivable accounts will be the same, but this process permits the exibility of using a
unique receivable account to record your credit memos.
331
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
The RA_CUSTOMER_TRX table stores On-Account Credit transaction number OC-101 as follows:
Note: The previous_customer_trx_id column is NULL because the credit doesn't apply to a specic invoice.
The RA_CUSTOMER_TRX_LINES table stores On-Account Credit transaction number OC-101 as follows:
CUSTOMER_TRX_LINE_ID
CUSTOMER_TRX_IDLINK_TO_CUST_TRX_LINE_ID
LINE_TYPE EXTENDED_AMOUNT
PREVIOUS_CUSTOMER_TRX_ID
PREVIOUS_CUSTOMER_TRX
If there had been a sales credit for this invoice, records relating to the revenue credit would be inserted in the
RA_CUST_TRX_LINE_SALESREPS table, linked using the column customer_trx_line_id.
For on-account credits, Receivables inserts one record into the RA_CUSTOMER_TRX_LINES table. The total value of the
credit is stored in the EXTENDED_AMOUNT column. The previous_customer_trx_line_id and previous_customer_trx_id
columns are null because the credit doesn't apply to a specic invoice.
The RA_CUST_TRX_LINE_GL_DIST table stores On-Account Credit transaction number OC-101 as follows:
CUST_TRX_LINE_GL_DIST_ID
CODE_COMBINATION_ID CUSTOMER_TRX_LINE_ID ACCOUNT_CLASS AMOUNT
Chargebacks
You create chargebacks to decrease the balance of an invoice and to create another debit item for the same amount.
Receivables handles chargebacks the same as invoices, but also creates an adjustment to decrease the balance of the
invoice.
• RA_CUSTOMER_TRX
• RA_CUSTOMER_TRX_LINES
• RA_CUST_TRX_LINE_GL_DIST
• AR_ADJUSTMENTS
332
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• AR_PAYMENT_SCHEDULES
You receive a payment for $2000 on June 1, 2011, and decide to create chargeback CB-101 for the balance due of $4400.
Receivables creates one record in RA_CUSTOMER_TRX_LINES for the chargeback with a line_type of CB and the
EXTENDED_AMOUNT equal to the balance of the invoice.
CUST_TRX_LINE_GL_DIST_ID
CODE_COMBINATION_ID CUSTOMER_TRX_LINE_ID ACCOUNT_CLASS AMOUNT
Receivables inserts two records into the RA_CUST_TRX_LINE_GL_DIST table. The code_combination_id of the REC
record stores the receivable account distribution for the chargeback. The code_combination_id of the REV record stores
the revenue account distribution for the chargeback.
333
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
When the chargeback is created, Receivables inserts a record into the AR_ADJUSTMENTS table to record an adjustment
against the invoice. The amount column equals the inverse of the amount_due_remaining column on the invoice
payment schedule in the AR_PAYMENT_SCHEDULES table. The customer_trx_id and the payment_schedule_id
columns reference the original invoice.
For chargebacks, the type column is always INVOICE. The code_combination_id column stores the revenue account
of the chargeback. This transaction will oset the REV distribution from the RA_CUST_TRX_LINE_GL_DIST table. To
link this adjustment with the chargeback, the chargeback_customer_trx_id column, which is not shown, stores the
customer_trx_id of the chargeback.
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_ADJUSTED
The class column identies this payment schedule as a chargeback. The example chargeback has a status of OP (open)
and an amount_applied of NULL, because no payment has been applied against it. The amount_due_original and
amount_due_remaining columns equal the amount of the chargeback.
After creating the chargeback , the AR_PAYMENT_SCHEDULES table stores Invoice I-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_ADJUSTED
Receivables updates the invoice payment schedule in the AR_PAYMENT_SCHEDULES table by reducing
the amount_due_remaining column to zero, to reect the application of the chargeback to the invoice. The
amount_adjusted column equals the amount of the chargeback and the status column is changed to closed (CL).
Adjustments
You can create adjustments to increase or decrease invoice balances. You can make adjustments to invoices, lines, tax,
or freight. Receivables uses the following tables to store adjustment information:
• AR_ADJUSTMENTS
• AR_PAYMENT_SCHEDULES
334
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Receivables inserts a record into the AR_ADJUSTMENTS table to record adjustment details, such as the amount, the
type of adjustment, the customer_trx_id, and the payment_schedule_id of the invoice to adjust. The amount column
equals the amount of the adjustment. The code_combination_id column stores the general ledger distribution for the
adjustment transaction.
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_ADJUSTED
Receivables updates the payment schedule record of the invoice in AR_PAYMENT_SCHEDULES, by adjusting the
amount_due_remaining to zero, changing the status to CL, and changing the amount_adjusted to -2400.
Unapplied Receipts
When you create a receipt, Receivables creates records in the following tables:
• AR_CASH_RECEIPTS
• AR_CASH_RECEIPT_HISTORY
• AR_PAYMENT_SCHEDULES
• AR_RECEIVABLE_APPLICATIONS
335
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
payment_schedule_id
amount_due_original
amount_due_remaining
cash_receipt_idcustomer_ trx_number status amount_applied
class
trx_id
The example receipt has a status of OP (open) and an amount_applied of NULL because the receipt hasn't been
applied to a customer balance. The amount_due_original column equals the sum of the amount column in the
AR_CASH_RECEIPTS table for the given cash_receipts_id. The class is PMT because this is a receipt related to a
receivable activity. The amount_due_original and amount_due_remaining columns equal the inverse amount of the
receipt.
payment_schedule_id
amount_applied status payment_schedule_id
code_combination_id
cash_receipt_id applied_payment_schedule_id
applied_customer_trx_id
The applied_payment_schedule_id and applied_customer_trx_id columns are NULL because the receipt hasn't
been applied to a specic transaction. The amount_applied column equals the amount of the receipt. The
code_combination_id column stores the general ledger account associated with unapplied cash receipts.
Consider sample receipt R-101, which is now applied to customer invoice I-101 for 6400 USD:
• Receipt Number: R-101
336
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
After you apply the receipt, Receivables updates the status column from UNAPP to APP. If the receipt were only partially
applied, the status would remain UNAPP.
payment_schedule_id
amount_due_original
amount_due_remaining
cash_receipt_id
customer_ trx_number status amount_applied
class currency
trx_id
The payment schedule of invoice I-101 has a class of INV, while the payment schedule of receipt R-101 has a class of
PMT. The payment schedule record of the receipt is updated to reduce the amount_due_remaining column by the
amount applied. Since the entire amount is applied, the amount_due_remaining is zero. The status of the receipt is
changed to CL, and the amount_applied is -4000.
Note: If the cash receipt is not conrmed in the AR_CASH_RECEIPT_HISTORY table, the applications of that
receipt are not reected in the payment schedule of the transaction the receipt is applied against.
Receivables updates the payment schedule record of the invoice to reduce the amount_due_remaining by the amount
of the applied receipt. The status is still OP because the entire balance hasn't been paid. Receivables updates the
amount_applied to reect the amount applied to the invoice.
337
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Receivables inserts three records into the AR_RECEIVABLE_APPLICATIONS table. The rst record, with a status
of UNAPP, records the original unapplied receipt. The second record, with a status of UNAPP, osets the original
unapplied receipt. The third record, with a status of APP, stores the applied receipt information, including a reference to
the applied invoice, from the trx_number column.
The code_combination_id column stores the general ledger account for this receipt, based on the status of the receipt.
For the UNAPP record, the code_combination_id represents the general ledger account associated with unapplied
receipts. For the APP record, the code_combination_id is the receivable account associated with the invoice transaction
to which this receipt is applied.
When you apply the entire receipt, Receivables updates the status column from UNAPP to APP. If the receipt were only
partially applied, the status would remain UNAPP.
payment_schedule_id
amount_due_original
amount_due_remaining
cash_receipt_id
customer_ trx_number status amount_applied
class currency
trx_id
The payment schedule of the invoice has a class of INV, while the payment schedule of the receipt has a class of PMT.
The payment schedule record of the receipt is updated to reduce the amount_due_remaining column by the amount
338
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
applied. Since the entire amount is applied, the amount_due_remaining is zero. The status of the receipt is changed to
CL, and the amount_applied is -100.
receivable_application_id
status trx_number amount_applied
amount_applied_from
trx_to_rcpt_rate
acct_amt_applied_to
acct_amt_applied_from
code_combination_id
Receivables inserts three records into the AR_RECEIVABLE_APPLICATIONS table. The rst record, with a status
of UNAPP, records the original unapplied receipt. The second record, with a status of UNAPP, osets the original
unapplied receipt. The third record, with a status of APP, stores the applied receipt information, including a reference to
the applied invoice, from the trx_number column.
The code_combination_id column stores the general ledger account for this receipt, based on the status of the receipt.
For the UNAPP record, the code_combination_id represents the general ledger account associated with unapplied
receipts. For the APP record, the code_combination_id is the receivable account associated with the invoice transaction
to which this receipt is applied.
Reverse Receipts
When you reverse a receipt, Receivables creates records in the following tables:
• AR_CASH_RECEIPTS
• AR_CASH_RECEIPT_HISTORY
• AR_PAYMENT_SCHEDULES
• AR_RECEIVABLE_APPLICATIONS
If receipt R-101 were not an actual receipt, we could enter a reverse receipt transaction to cancel the receipt.
The AR_CASH_RECEIPTS table stores information for the reversed receipt as follows:
Receivables updates the status column of the original receipt from applied (APP) to reversed (REV).
The AR_CASH_RECEIPTS_HISTORY table stores information for the reversed receipt as follows:
339
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
A new record, which is not postable, is inserted into the AR_CASH_RECEIPT_HISTORY table to record the reversed
receipt. Additionally, the current_record_ag of the original cash receipt record is updated to null, while the
reverse_gl_date column of the original receipt record is populated.
The AR_PAYMENT_SCHEDULES table stores information for the reversed receipt as follows:
payment_s amount_due_original
amount_due_remaining
cash_receipt_idcustomer_trx_id
trx_number status amount_applied
class
chedule_id
The payment schedule of the invoice has a class of INV, while the payment schedule of the receipt has a class of PMT.
Because the receipt was reversed, the amount_due_remaining and amount_applied columns are zero and the status
column is closed (CL).
Receivables updates the payment schedule record of the invoice to increase the amount_due_remaining by the amount
of the reversed receipt. The status is still OP because the entire balance is not paid. The amount_applied column is zero
because no transactions have been applied to the invoice.
The AR_RECEIVABLE_APPLICATIONS table stores information for the reversed receipt as follows:
receivable_application_id
amount_applied status payment_schedule_id
code_combination_id
cash_receipt_id applied_payment_schedule_id
applied_customer_trx_id
Receivables inserts three records into the AR_RECEIVABLE_APPLICATIONS table. The rst record, with a status
of APP, osets the original application of the receipt, including a reference to the applied invoice, from the
applied_payment_schedule_id and applied_customer_trx_id columns.
The second and third records, with a status of UNAPP, oset the original unapplied transactions. The
code_combination_id for the APP record is the receivable account associated with the invoice to which this receipt was
originally applied. The code_combination_id for the two UNAPP records is the general ledger account associated with
unapplied receipts.
340
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Miscellaneous Receipts
When you create a miscellaneous receipt, Receivables creates records in the following tables:
• AR_CASH_RECEIPTS
• AR_CASH_RECEIPT_HISTORY
• AR_MISC_CASH_DISTRIBUTIONS
The AR_CASH_RECEIPTS table stores information for the miscellaneous receipt as follows:
Receivables uses a status of APP for miscellaneous receipts. The type column is MISC for receipts not related to a
receivables activity. The amount column stores the net amount of the receipt, while the receipt_number column stores
the receipt number.
The AR_CASH_RECEIPTS_HISTORY table stores information for the miscellaneous receipt as follows:
The only valid status values for a miscellaneous receipt are REMITTED, CLEARED, and REVERSED.
The AR_MISC_CASH_DISTRIBUTIONS table stores information for the miscellaneous receipt as follows:
The code_combination_id stores the general ledger account associated with miscellaneous receipts. Each receipt may
have multiple account distributions. The sum of the distributions for a given receipt will equal the amount of the receipt.
341
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
For example, your enterprise calculates late charges on the 15th and 30th of each month. Your customer has an
overdue invoice of $100 that falls due on November 16:
◦ On November 30, you run the Create Late Charges program. The program calculates late charges for this
overdue invoice.
◦ On December 10, your customer pays the invoice.
342
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
◦ On December 15, you run the Create Late Charges program again. The program assesses further charges
for the additional 10 days that the payment was overdue.
• Flat Rate: Use a at rate to calculate the late charge amount. Receivables ignores the number of days that a
payment is overdue. If you use balance forward billing and the average daily balance calculation method, then
this is the calculation formula used. The formula is:
• Simple: Calculate late charges on overdue transactions only. If you use interest tiers and charge schedules to
create late charges and penalties, then this is the calculation formula used. The formula is:
• Compound: Calculate late charges on the sum of overdue transactions and prior late charges. The formula is:
(Amount Overdue + Prior Late Charges) * (Interest Rate/100) * (Number of Days Late/Number of Days in
Period)
Tip: The charge schedule approach provides you with a convenient method to update interest rates or
amounts when your late charge policy changes. You can simply apply a new charge schedule to the applicable
interest tiers. If you don't use charge schedules, then when your late charge policy changes you must update
each of your applicable customer proles with the new rates.
• Interest Tiers: Use the Manage Interest Tiers page to dene a set of interest tiers based on ranges of late days.
Use these seings for each set of interest tiers:
343
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• Charge Schedules: Use the Manage Charge Schedules page to assign late charge rates to the periods of the sets
of interest tiers that you have dened. Use these seings for each charge schedule:
◦ Charge Method: Select the charge method to use for the interest tier periods:
• Amount: Apply a at amount against overdue transactions that fall within the specied period
ranges.
• Percentage: Apply a percentage of the overdue transactions that fall within the specied period
ranges.
◦ Tier Levels Rate: Assign the rate, either a at amount or percentage of the outstanding balance, to each
period in the interest tier.
• Prole Class: Specify these values on the related prole class, or customer or customer account prole:
◦ Use multiple interest rates option: If you set the Use multiple interest rates option, then if the eective
dates for two charge schedules occur within the same charge calculation period, both rates apply to late
charge calculations during that period.
◦ Currency Seings: Enter for each currency in which you intend to calculate late charges, the charge
schedules to use for late charges and, if applicable, penalty charges:
• Interest Charge Type eld and Penalty Charge Type eld: Enter the value Charge Schedule.
• Interest Charge Schedule eld and Penalty Charge Schedule eld: Enter the charge schedules
that you previously dened to use for late charges and penalty charges.
The Simple calculation formula is the amount overdue multiplied by the rate and days overdue in the period:
Amount Overdue * (Interest Rate/100) * (Number of Days Late/Number of Days in Period)
This table provides an example of a charge schedule with four interest tier periods, each with an assigned interest rate.
1-30 days 2%
31-45 days 3%
46-60 days 4%
Over 60 days 5%
344
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
In this example:
After an additional 15 days (60 days overdue), the late charges are calculated as follows:
$1,000 * (4/100) * (60/30) = $80
Seings That Aect Late Charge Calculation Using Average Daily Balance
These seings aect late charge calculation using average daily balance:
• Billing and Revenue Receivables System Options: Set these system options for late charges in the Late Charges
section of the Billing and Revenue tab of the Create System Options page:
◦ Assess late charges option: Set the Assess late charges option to indicate that your enterprise assesses
late charges on overdue transactions. This option is reviewed rst, before reviewing the various aspects
of your late charge policy dened in system options or customer proles.
◦ Average Daily Balance Calculation Basis eld: Select a calculation basis to include or exclude as part
of the balance calculation any debit items that were billed after the most recently generated balance
forward bill:
• Include Post-Billing Debit Items: The average daily balance formula includes debit items that were
created after the previous balance forward bill cuto date.
• Exclude Post-Billing Debit Items: The average daily balance includes only those debit items that
were already included on the last balance forward bill.
◦ Average Daily Balance Calculation Period eld: Select the period that Receivables uses to calculate the
average daily balance:
• Due-Date to Run Date: Receivables computes the sum of the applicable debits and credits for
each day that falls between the balance forward bill due date and the Create Balance Forward Bill
program submission date. To calculate the average daily balance, Receivables divides the sum by
the number of days.
• Run-Date to Run-Date: Receivables computes the sum of the applicable debits and credits for each
day that falls between the last submission date and current submission date of the Create Balance
Forward Bill program. To calculate the average daily balance, Receivables divides the sum by the
number of days.
• Customer Prole Class: Set these options for late charges in the Credit Limits and Late Charges tab on the
Create Receivables Customer Prole Class page, or on the applicable customer or customer site prole:
◦ Enable late charges option: Set the Enable late charges option to enable the assessment of late charges
for customers assigned this prole.
◦ Late Charge Calculation Method eld: Select the calculation method Average Daily Balance.
345
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
◦ Receipt Grace Days eld: Enter the number of receipt grace days after the transaction due date before
late charges are calculated.
Note: After the grace days expire, Receivables calculates the number of days overdue using
the original due date.
This table provides an example of an average daily balance calculation. In this example, there are ve days in the billing
period, and a student enrolls in a class and makes a partial payment two days later.
June 1 No activity $0
In this example:
• The beginning balance for this customer is $0 and there is no account activity on the rst, third, and fth day.
• When the student enrolls in a class on June 2, there is a single charge of $1,000.
• The student makes a partial payment of $250 against the enrollment fee on June 4.
• The last column represents the daily balance. The average daily balance is $700.
If the interest rate is 10%, then the total late charge for this billing period is $70. This is calculated as follows:
($0 + $1,000 + $1,000 + $750 + $750 = $3,500) / 5 days = $700
$700 * 10% interest rate = $70 total late charge
Related Topics
• Example of Seing Up Balance Forward Billing
346
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
You can record and present late charges as one of three documents:
• Adjustments
• Debit Memos
• Interest Invoices
You must complete the entire setup for late charges. In addition, you must complete specic steps for the document
that you intend to use.
Note: Because interest invoices and debit memos are considered to be regular transactions, tax may be
calculated on these transaction amounts.
Adjustments
If you record late charges as adjustments, then Receivables combines all interest charges relating to an overdue
transaction, and creates a single late charge adjustment against that transaction.
Note: You can't record late charges as adjustments for bills receivable transactions. You can only record late
charges for bills receivable as debit memos or interest invoices.
If you also assess penalty charges, then Receivables creates two adjustments.
If you select Credit Items in the Charge Reductions eld of the applicable customer prole, then credit items belonging
to the customer reduce the outstanding overdue amount during late charge calculations.
1. Select Adjustment in the Late Charge Type eld on the Credit Limits and Late Charges tab of the applicable
customer prole.
2. Dene a Late Charges receivables activity and enter an activity GL account.
3. If you assess penalties in addition to late charges, then dene a separate Late Charges receivables activity for
Penalties and enter an activity GL account. Receivables creates penalties as a separate adjustment against the
overdue transaction.
4. Assign these activities to Billing and Revenue system options:
◦ Select the receivables activity for late charges in the Interest Charge Activity eld in the Late Charges
section.
◦ Select the receivables activity for penalties in the Penalty Charge Activity eld in the Late Charges
section.
Debit Memos
If you record late charges as debit memos, then Receivables creates one debit memo per overdue transaction.
If you also assess penalty charges, then Receivables includes a separate line for penalty charges on the debit memo.
If you select Credit Items in the Charge Reductions eld of the applicable customer prole, then credit items belonging
to the customer reduce the outstanding overdue amount during late charge calculations.
347
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
You must complete these steps to record late charges as debit memos:
1. Select Debit Memo in the Late Charge Type eld on the Credit Limits and Late Charges tab of the applicable
customer prole.
2. Dene a transaction source for late charges with a type of Imported. Receivables creates a debit memo batch
using the Invoice API.
3. Dene a transaction type for late charges:
◦
Select the debit memo transaction type in the Debit Memo Charge Transaction Type eld in the Late
Charges section.
◦ Select the debit memo transaction source in the Late Charge Transaction Source eld in the Late
Charges section.
5. Select payment terms for the applicable customer proles to indicate the debit memo due date.
Interest Invoices
If you record late charges as interest invoices, then Receivables creates a single interest invoice per customer site and
currency. The interest invoice consolidates and itemizes charges for a period, and includes details about charges for
each overdue transaction.
If you also assess penalty charges, then Receivables includes a separate line for penalty charges on the invoice.
If you select Credit Items in the Charge Reductions eld of the applicable customer prole, then Receivables calculates
negative charges on existing credit items belonging to the customer, and includes these negative charges as lines on
the interest invoice.
You must complete these steps to record late charges as interest invoices:
1. Select Invoice in the Late Charge Type eld on the Credit Limits and Late Charges tab of the applicable
customer prole.
2. Dene a transaction source for late charges with a type of Imported. Receivables creates an interest invoice
batch using the Invoice API.
3. Dene a transaction type for late charges:
◦Select the interest invoice transaction type in the Interest Invoice Transaction Type eld in the Late
Charges section.
◦ Select the interest invoice transaction source in the Late Charge Transaction Source eld in the Late
Charges section.
5. If you use interest tiers and charge schedules to assess increasingly higher late charges the longer a payment
is overdue, you can set the Use multiple interest rates option on the related prole class, or on an individual
customer or customer account prole.
If you set this option, then if the eective dates for two charge schedules occur within a charge calculation
period, both rates apply to late charge calculations during that period.
348
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
6. Select payment terms for the applicable customer proles to indicate the interest invoice due date.
To create a lookup code for the replacement of the legal entity balancing segment value:
1. Navigate to the Manage Receivables Lookups page.
2. Search for the AR_FEATURES lookup type.
If the lookup type AR_FEATURES doesn't exist, create this lookup type in the Manage Standard Lookups page.
3. Select the AR_FEATURES lookup type and click the Plus (+) icon to create a new row for entering the lookup
code.
4. In the Lookup Code eld, enter AR_LATE_CHARGE_BSV_OPTION.
5. Check the Enabled box to activate the replacement of the legal entity balancing segment value.
6. In the Start Date eld, enter the date that this lookup code becomes active.
7. Complete the other lookup code elds according to your business requirements.
8. Save your work.
When the AR_LATE_CHARGE_BSV_OPTION lookup code is activated, a run of the Create Late Charges process replaces
the balancing segment value of the receivable and revenue accounts dened in the interest invoice transaction type
assigned to the Interest Invoice Transaction Type eld in the Late Charges section of Billing and Revenue Receivables
System Options for all legal entities of overdue transactions that don't have multiple balancing segment values.
If any legal entity has multiple balancing segment values assigned, then the Create Late Charges process doesn't
replace the balancing segment value of the receivable and revenue account code combinations but instead retains the
default values.
349
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
The Interest Invoice Transaction Type assigned to Receivables System Options for the business unit has the following
receivable and revenue accounts (Company-Account-Activity-Cost Center-Intercompany-Project-Site-SubAccount, with
the Company segment dened as the primary balancing segment):
The business unit has three legal entities: Vision Operations, Vision Services, Vision Foods.
This table describes overdue customer transactions as of the date the late charges are calculated (all transactions
belong to the same business unit):
This table describes the resulting interest invoices and balancing segment value assignments generated for each legal
entity after a run of the Create Late Charges process:
Late Charge Interest Invoice Legal Entity Overdue Interest Invoice Interest Invoice
Batch Number Transactions Receivable Revenue Account
Account
• Interest Invoice 2001 has the balancing segment value assignment 01 with legal entity Vision Operations.
• Interest Invoice 2002 has the balancing segment value replaced as 02 with legal entity Vision Services.
• Interest Invoice 2003 has the balancing segment value retained as 01 with legal entity Vision Foods.
350
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
These examples illustrate the dierence between calculating the minimum customer balance using the Overdue
Transactions Only charge calculation method and the Average Daily Balance charge calculation method. In these
examples, the minimum customer balance is $250.
These examples also illustrate how submiing the Create Late Charges program on dierent dates (May 20 or May 30)
can potentially change the activity that is selected for late charge calculation.
In these examples:
• The billing date is May 1 and the billing cycle is from the rst day of the month to the last day of month
inclusive.
• The due date is the 10th of the following month.
• The receipt grace period is three days.
351
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
If you submit the Create Late Charges program on May 20, then the customer balance includes 3 overdue invoices (April
10, April 12, and May 4) for a total of $500. The balance also includes 3 payments (May 6, May 13, and May18) for a total
of $275.
The total customer balance is $225, which is below the minimum balance of $250. Therefore, late charges are not
calculated for this customer.
To calculate late charges, Receivables starts with the ending balance of the last balance forward bill and includes only
invoices that were on the last bill. In this case, Receivables includes invoices that were created before May 1 (April 10 and
April 12) for a total of $400.
Receivables then subtracts all credits that were recorded before May 13 (the due date plus receipt grace days). Credits
include the receipts from May 6 and May 13 for a total of $75.
In this case, the total customer balance is $325, which is higher than the minimum balance of $250. Therefore, late
charges are calculated for this customer, using the applicable Average Daily Balance calculation method.
The total customer balance is $275, which is higher than the minimum balance of $250. On this day, late charges are
calculated for this customer.
To determine the customer balance, Receivables still starts with the ending balance of the last balance forward bill (May
1), and subtracts all credits (receipts and credit memos) up through the due date plus receipt grace days (May 13).
352
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Are there exceptions to the general policy? Yes, for the customer account site and customer transactions
Field Value
Late Charges
Activity Type
353
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Field Value
Name of the Late Charges receivables activity that you previously dened.
Interest Charge Activity
Field Value
Credit Items
Charge Reductions
Adjustment
Late Charge Type
Compound
Interest Calculation Formula
Monthly
Interest Calculation Period
2
Receipt Grace Days
30
Interest Days Period
No
Assess Late Charges Once
354
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Field Value
Percent
Minimum Invoice Balance Overdue
Type
15
Minimum Invoice Balance Overdue
Percent
Percent
Minimum Customer Balance
Overdue Type
15
Minimum Customer Balance
Overdue Percent
Fixed Rate
Interest Charge Type
9
Interest Charge Rate
1. Open the Statement, Dunning, and Late Charges Site Proles Used prole option.
2. Set the prole option to No.
By seing this prole option to No, the Create Late Charges program uses the late charge policy assigned to the
bill-to site.
3. Open the Create Transaction Type page and create a transaction type that excludes invoices from late charges.
4. Complete the elds, as shown in this table:
Field Value
Invoice
Transaction Class
Open
Transaction Status
355
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Field Value
Review this report after a run of the Generate Late Charges program, or run the program in Draft mode to review the
results before generating late charges.
Report Output
You can present late charges to the customer as an interest invoice, an adjustment, or a debit memo.
For interest invoice late charges, the report displays multiple rows for multiple overdue transactions or late payments,
as well as a total that includes all charges. The Generate Late Charges program creates one interest invoice per
customer site and currency.
For adjustment or debit memo late charges, the Generate Late Charges program creates only one adjustment or debit
memo per overdue transaction or late payment. The report displays one page per adjustment or debit memo.
This table describes important column headings in the Generate Late Charges Report.
Due Date The transaction due date. Late charges apply to the open balance on the transaction after the
due date.
Days Late The number of days that the outstanding balance is past due.
Interest Days The number of past-due days that interest applies to the outstanding balance.
356
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
This table describes important row headings in the Generate Late Charges Report.
Adjustment Number The number assigned to the adjustment, for late charges presented as an adjustment.
Charge Calculation Date The date the late charges were calculated for this report.
Total Interest Charge for Overdue The total late charge calculated for overdue invoices.
Invoices
Total Late Charge The total of all late charges calculated for the customer for the report period.
If you also assess penalty charges, then complete the related elds for penalty charges.
Process Statements
357
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Receipts that have cross-site or cross-customer applications are reported on statements after the On-Account and
Unapplied receipts. These entries display the amount applied to transactions of other sites in the Transaction Amount
column and have no eect on the balance of the statement.
Scenario
In this example two sites, SF (San Francisco) and CA (California), pay each other's invoices. Every receipt is recorded
against the invoice to which it is applied. It is also reported on the statement of the site that owns the receipt as a cross-
site entry, with the amount applied to the other site displayed as the transaction amount. If the receipt is not fully
applied, the portion not applied is entered as an unapplied receipt.
358
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Generate Bill
• Print a draft statement for a customer: If you select this option, you must enter a customer name or customer
account number.
• Print Statements: Print statements for specied customers or statement cycle
359
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• Reprint Statements: Reprint a previous statement for specied customers or statement cycle.
Bucket
Cycle
Statement Date
As-of Date
Transaction Type
Primary Salesperson
Standard Messages
The names of the standard messages to print on statements. Use the numbered elds to indicate the order in which you
want messages to appear.
Report Output
The report summarizes transactions and amounts due by customer bill-to site, with a nal total for the customer
account.
Bill-to
The customer name and address for each statement. The country of the customer address is included if it is
dierent from the home country specied in Receivables system options.
Note: If you do not have a statement address dened for a customer, the program prints a statement for each
bill-to address that has activity during the statement cycle for the statement submission.
Statement Date
The date the statement is generated.
360
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Account Number
The customer account number.
Column Headings
Transaction Number
The number of the transaction activity. For example, if the activity is a payment, the report prints the debit item
number to which this payment applies. The report also identies cross-site and cross-customer receipts.
Transaction Date
The date of the transaction activity.
Class
The name of each debit and credit activity:
• Invoice
• Adjustment
• Credit Memo
• Debit Memo
• Payment
• Late Charge
Note: Receivables does not print NSF or STOP payments that were reversed after your statement date.
Due Date
The date that payment is due on the open item.
Reference
Additional information about each transaction activity, including payment number, credit memo number,
purchase order number, and adjustment name.
Bill-to Site
The bill-to site for the transaction.
Total Amount
The original amount of the transaction.
Amount Due
The remaining amount due on the transaction. Credit items appear with negative amount due values.
Current
Customer open item information based on the aging bucket you dene as your rst bucket.
361
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Financial Charges
The total amount of late charges for the customer site.
Related Topics
• How to Use Statement Cycles
• How do on-account and unapplied receipts appear on statements
362
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Subledger Accounting categorizes accounting events as event types. Event types are grouped into event classes
that in turn are grouped into event entities. The overall grouping of these components is called an event model. The
Receivables accounting event model is predened for you, and includes each Receivables event class and its life cycle.
This accounting event model forms the basis for creating subledger accounting.
As the foundation of the event model, Receivables contains predened event entities. An event entity enables
Subledger Accounting to handle the accounting for similar business events in a consistent manner. The event entities
for Receivables are:
• Transactions
• Receipts
• Adjustments
• Bills Receivable
Each event entity is associated with one or more event classes. An event class represents a category of business events
for a particular activity or document. Event classes group similar event types and enable the sharing of accounting
denitions.
An event type represents a business operation that you can perform for an event class. An accounting event has both
an event class and an event type that aect how the Create Receivables Accounting program determines the subledger
accounting for it. Event types provide the lowest level of detail for storing accounting denitions.
363
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
364
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Review these activities related to seing up your Financials environment for Receivables to General Ledger
reconciliation:
If you don't implicitly map primary balancing segment values to business unit, you must reconcile based on ledger. In
this case, you will need access to all business units associated with the ledger to perform a thorough reconciliation.
Note: Implicit mapping means that no specic setup is used to assign the business unit to a primary
balancing segment. This is a business decision, and your setup in Receivables should be such that the default
accounting assigned to activities for that business unit should be the primary balancing segment value that
was decided.
If the nancial category of Accounts Receivable is not included in the chart of accounts setup, the Receivables to
General Ledger Reconciliation report won't select any data. When you run the extract program, if you try to select
general ledger natural account values that don't have this category assigned, the extract program displays an error
indicating that the nancial category was not assigned.
Once you assign the Accounts Receivable nancial category, you can leave the Account parameter blank when you
run the extract, in order to include all accounts that have the Accounts Receivable nancial category in the ledger. You
can alternatively enter specic natural account values to limit the report to reconciling only a subset of the receivables
accounts in the ledger, but these values must have the Accounts Receivable nancial category assigned.
If you set up accounts for unidentied, unapplied, and on-account receipts, and on-account credit memos, you must
also assign the Accounts Receivable nancial category to these accounts in order to include them in reconciliation. If
you want to exclude these accounts during reconciliation, then you must exclude them from the Account parameter,
and both the Include On-Account Items parameter and the Include Unapplied and Unidentied Receipts parameter.
365
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Caution: You must assign unique general ledger accounts to unidentied, unapplied, and on-account
receipts, and on-account credit memos, to exclude them from reconciliation. Don't assign them the same
receivables accounts as that used for transactions, because the accounting for transactions would also be
excluded, causing reconciling dierences.
Use the Reconciliation Data Purge Frequency prole option to indicate the number of days to keep reconciliation
extract data in the tables. Enter a value for the number of days needed to not lose prior extracts that you may need for
comparison purposes.
Every time you run the extract program, it refers to the value of the Reconciliation Data Purge Frequency prole
option. If there are any reconciliation data extract requests in the table older than the number of days specied in the
prole option, these requests are purged.
For example, if a reconciliation data extract is run on January 1, and the value of this prole option is set to 30 days, then
the data from January 1 is not purged if you run another extract on January 29. However, the data is purged if you run
another extract on February 1.
The Zero Amount Journal Lines Displayed prole option aects whether journal lines with zero amounts display in the
Not Transferred to GL Detail report. If this prole option is set to Yes, the Summary report may equal zero and the detail
report will list these zero amount journal lines. This doesn't prevent Period Close and doesn't cause reconciling issues as
the net eect on the report is zero.
User Security
This section includes considerations for segment security and data access set.
Segment security applies to Detail reports only. If you don't have segment security access, then summary and detail
report totals may not match.
Typically General Ledger users are secured by a data access set, and Receivables users by business unit security. This
means that for the Receivables to General Ledger Reconciliation report:
• General Ledger users can see general ledger data for the balancing segment values in their data access set, as
well as the Receivables and Subledger Accounting data for all business units linked to the ledger.
• Receivables users can see the Receivables and Subledger Accounting data for business units in their security
denition, as well as general ledger data for all balancing segment values in the ledger.
However, if security is congured such that the data role for the General Ledger or Receivables job roles also have FND
grants to specic business units for General Ledger users or specic data access sets for Receivables users, then the
reconciliation report will only include:
• For General Ledger users, the Receivables and Subledger Accounting data for those business units in the ledger
to which the user has access.
• For Receivables users, general ledger data for those balancing segment values included in the data access set
to which the user has access.
This doesn't present a problem for the Receivables to General Ledger Reconciliation report if there is an implicit
mapping between business units and balancing segment values. Users can simply lter the report for the balancing
segment values that are mapped to the business units to which they have access, and the report should work properly.
366
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
However, if there is not an intentional and implicit mapping between balancing segment values and business units, then
this can cause the Receivables to General Ledger Reconciliation report to display undesirable results:
• For General Ledger users, the report will include general ledger data for all balancing segment values in the
data access set, while Receivables and Subledger Accounting data are limited to the business units to which a
user is granted access.
• For Receivables users, the report either won't include any general ledger data, or it will include general ledger
data that is not properly mapped to the Receivables and Subledger Accounting data for the business unit.
You can resolve this issue by removing the FND grants from specic business units for the General Ledger job roles,
and from specic data access sets for the Receivables job roles.
Related Topics
• Chart of Accounts Components
Tip: To avoid unintended reconciling dierences, you must ensure that you include or exclude the related
accounting activity associated with the Receivables transaction activity included in a given extract. For
example, if you intend to reconcile by a specic business unit but don't select the associated primary
balancing segment values in the Account parameter, accounting data from other business units belonging to
the same ledger will display as dierences.
Enter a name that is descriptive of this extract. Consider using a name that indicates the accounting period, date, and
time, especially if you are planning to create multiple extracts.
Note: Enter a unique request name each time you run the extract. If you reuse a request name, then the
extract may contain no data.
Ledger
The ledgers available for selection are based on your security assignment. The default is the rst ledger in alphabetic
order.
Business Unit
367
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Note: The business unit must be mapped to a balancing segment. If not, you must reconcile by ledger.
If you have implicitly mapped your business unit to one or more primary balancing segment values, you
will also need to select these values when you run the extract.
Accounting Period
You can select either an Open or Closed accounting period. The default is the latest period in the Closed Pending status,
if it exists, for the selected ledger.
You can run the extract on an Open period to see point-in-time summary balances, in order to review possible
reconciling activities you may encounter during period close processing. If you select an Open period for reconciliation,
users can still enter activity against the period after the extract runs, creating potential discrepancies between the
summary and detail information on the report. Best practice is to close the accounting period to be reconciled before
you run the extract, and then select this Closed period in the Accounting Period parameter.
You can include or exclude Intercompany transactions, or you can reconcile by Intercompany activity only.
You can include or exclude on-account items. On-account items include on-account receipts and on-account credit
memos.
Note: You may want to exclude on-account items if they typically post to non-receivable accounts. If
you plan to exclude on-account items, you also need to exclude the related general ledger account in the
Account parameter. Therefore, don't post this activity to the same Receivables account as your invoices
to avoid reconciling dierences.
You can include or exclude unapplied receipts and unidentied receipts. Unapplied receipts are receipts that haven't yet
applied; unidentied receipts are receipts without customer information.
Note: You may want to exclude unapplied and unidentied receipts if they typically post to non-
receivable accounts. If you plan to exclude unapplied and unidentied receipts, you also need to exclude
the related general ledger account in the Account parameter. Therefore, don't post this activity to the
same Receivables account as your transactions to avoid reconciling dierences.
Account
You can select values from any of the segments of the accounting exeld. The natural account segment values must
have the nancial category of Accounts Receivable assigned in your general ledger setup in order for the extract and
report to work properly.
If you are excluding on-account items, or unapplied and unidentied receipts, from your reconciliation, you must
also exclude their associated general ledger accounts, if those accounts have the nancial category of Accounts
Receivable assigned. If they don't have the nancial category assigned, by default these accounts are not included in
your reconciliation.
368
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
If you are reconciling by business unit, select the range of balancing segment values implicitly mapped to your business
unit.
If you are reconciling Intercompany activity, select the range of Intercompany accounts. These accounts must have the
nancial category of Accounts Receivable assigned.
If you are reconciling everything, you don't need to select any values. The report automatically selects data for
Receivables accounts that have the nancial category of Accounts Receivable assigned.
Drill down on any amount in the Summary report Dierence column to display the Dierences Detail report for that
item. The Dierences Detail reports display the details that make up balances from the Summary report, and indicate
potential causes for dierences between actual and reconciling amounts.
Note: For a more ecient reconciliation, don't allow general ledger sources other than Receivables to post to
Receivables accounts.
If you restrict the number of general ledger accounts that you include in a run of the Prepare Receivables to General
Ledger Reconciliation program, this can aect the display of data in the detail reports and may be the cause of a
dierence between the accounted amount of a transaction and the reconciling amount.
For example, if Receivables transactions are recorded against balancing segment values 1, 2, 3 or natural accounts
A, B, C, and the account range you used excluded some of these values, then these transactions would show up as
dierences on the report.
If you are downloading a large amount of data from the report to a spreadsheet and you plan to perform a number of
data manipulations, use the CSV format. If you are downloading data for reference purposes only, use the Excel or PDF
format.
Review these additional guidelines for using the Receivables to General Ledger Reconciliation report:
369
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Note: It may happen that the Summary report will contain variance amounts. If the Summary report contains
variance amounts, contact your system administrator.
Any dierences that you nd require further investigation and possible correction. Common reasons for dierences
between transactional amounts and accounted amounts include:
• Transactions that are not accounted.
• Transactions with subledger accounts that fall outside the account range of the report.
• Transaction amounts don't agree with the subledger journal line amounts.
• Journals are posted to the subledger or general ledger that didn't come from Receivables.
• Subledger journals were not transferred or posted to general ledger.
After nding and correcting discrepancies, you must re-run the Prepare Receivables to General Ledger Reconciliation
program and review the Summary report.
Note: Some dierences may be valid. For example, if you included unapplied and unidentied receipts in your
extract, but you don't post these receipts to a receivables account or an account with the nancial category of
Accounts Receivable assigned, then these receipts appear as a dierence that is outside the account range of
the report. In this case, you can re-run the extract and exclude these items.
The drill-down page doesn't include non-Receivables journal lines dated in previous scal years, which means that
these journal lines won't match the Non-Receivables Begin Balance amount. The drill-down page is only intended to
provide current scal year journals that might have posted erroneously to the receivables account.
The journal source of these journals is typically not Receivables. However, you may see manual subledger journal
entries that were entered for the Receivables source directly into the subledger but not necessarily linked to a specic
Receivables transaction. Most of these entries represent adjustment journal entries.
Manual subledger journals created during the current reconciling period display in the Summary report in the Other
Accounting section, and become part of the Non-Receivables Begin Balance amount in subsequent periods. Manual
general ledger journals that may aect receivables accounts are created directly in the general ledger and don't display
in the Other Accounting section on the Summary report, but display instead in the Non-Receivables Activity amount.
370
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Ensure that appropriate security is given to users for all business units and accounting exeld segment values
that each user is responsible for reconciling.
• Intercompany Transactions: You can't limit the display of intercompany transactions on the Receivables
Aging by Account report. If the reconciliation extract either excludes intercompany transactions or displays
intercompany transactions only, then the Receivables to General Ledger Reconciliation report and the
Receivables Aging by Account report won't display compatible data.
• Unaccounted Amounts: The Receivables Aging by Account report doesn't display unaccounted activity.
Unaccounted amounts display as dierences in the Summary Reconciliation report. In this case, compare
the Accounting End Balance with the Receivables Aging by Account report. You will need to subtract out any
amount in Other Accounting, as this is not included in the Receivables Aging by Account report.
• Receipts at Risk: The Receivables Aging by Account Report has the option to display or ignore Receipts at Risk.
The Receivables to General Ledger Reconciliation report doesn't use this option, and always excludes receipts
at risk. For reconciliation purposes, be sure to exclude receipts at risk when running the Receivables Aging by
Account report.
• Open Credits: The Receivables Aging by Account report has the option to Age, Summarize, or Exclude open
credits. For reconciliation purposes, it is recommended that you Age or Summarize open credits.
Caution: Do not use Advanced Collections Aging reports for reconciliation because they don't include general
ledger account information. This applies to these three reports:
• Aging by Common Currency Report
• Collections Aging 4-Bucket Report
• Collections Aging by Collector 7-Bucket Report
If you want to include Intercompany activity with other Receivables activity, set the Include Intercompany parameter to
Yes and include the Intercompany account in the range of account values to extract. By default, if no account range is
selected, all accounts with the nancial category of Accounts Receivable are included in the extract.
If you want to exclude Intercompany activity from reconciliation, set the Include Intercompany parameter to No, and
also exclude the Intercompany range of accounts from the extract.
371
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
If you are reconciling only the Intercompany activity, set the Include Intercompany parameter to Intercompany Only,
and select the account range for your Intercompany Receivables accounts.
If you never include unapplied and unidentied receipts, or on-account items, in your reconciliation, then don't assign
the nancial category of Accounts Receivable to these accounts in your chart of accounts setup.
The totals for Bills Receivable and Bills Receivable Application net to zero, because both sides of the creation of
bills receivable and the application of transactions, or unapplication in the case of canceled bills, are recorded here.
Creation and Acceptance require the assignment of transactions to the bill receivable, so each of these bills display
the associated transaction applications. Cancellation reverses the bill receivable and its applications, so canceled bills
display both sides of the activity, application and unapplication.
Status changes to Remied, Unpaid, and Factored bills receivable have an accounting impact only because, as the bill
goes through its lifecycle, only the account it posts to changes. These events display in the Summary report in the Other
Accounting section. Like all other events related to reconciliation, the accounts used for these activities need to have the
nancial category of Accounts Receivable assigned to the natural account segment in the chart of accounts.
Other activities against bills receivable are included in existing sections of the Summary report and the related drill-
down reports. On-account credit memos against a bill receivable display in the Invoices section, along with all other
transaction activity. Receipts applied to bills receivable display with other receipts in the Applied Receipts section.
Related Topics
• Journal Capture Options
• How Account Balances Are Calculated
372
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• For new software installations, prior to running nal accounting, in order to conrm the correct derivation of
accounting.
• Whenever the accounting setup has been modied--such as the creation of new transaction types, receipt
methods or receivables activities--prior to running nal accounting.
The report suggests journal items that potentially posted to general ledger accounts with unexpected account types,
thus creating reconciliation issues in general ledger. An unexpected account type refers to general ledger account
types that are not normally associated with an item general ledger category. General ledger account types used by
Receivables include assets, liabilities, income, and expense.
For example, a receivable item might be expected to post to an asset account. If the item posts to a non-asset account,
then it will appear on the Potential Reconciling Items Report.
Typical items that the Potential Reconciling Items Report includes are:
• Adjustment journals with oset accounts that are asset accounts, rather than income or expense.
• Revenue journals for invoices and credit memos that post to account types other than income.
• Unearned revenue journals that post to an account type other than liability.
• Unbilled journals created for deferred billing that post to an account type other than asset.
• Late charge journals that post to an account type other than income.
• Cash, conrmation, or remiance journals that post to account types other than asset.
• Short term debt journals created by factoring receipts that post to account types other than liability.
• Nonrecoverable tax that posts to an account type other than expense.
When a potential reconciling item is an error, correct both the individual transaction and the incorrect setup to prevent
future occurrences of the same error.
373
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Projected Gains and Losses Report lets you review open foreign (non-ledger) currency invoices, debit memos, and
chargebacks revalued according to the revaluation rate that you specify.
Key Insights
The report compares the revalued amount of each debit item with the entered amount and prints the unrealized gain or
loss.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
374
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
Who uses this report? Financial Manager during period close processing.
When do I use this report? To review projected gain or loss for open foreign currency transactions revalued according to
the revaluation rate that you specify.
The report includes a nal summary section at the end by currency to review your unrealized gain and loss totals for
each currency. The net revaluation gain or loss totals, calculated as the dierence between the revaluation gain and
revaluation loss, average out to the same for the customer/transaction type totals and the currency totals.
Use this report according to your customer account and open balance reviews and revaluations.
Conversion Date
Date that corresponds to the conversion rate to use as the revaluation rate. The rate date and the rate type together
determine the revaluation rate used to revalue your debit items.
For example, if you are using the Spot rate for June 1, 2014, enter 01-Jun-14. If you are using Period Average as your
rate type, enter a date that is within the Receivables accounting period for the Period Average rate you dened.
If you enter a rate type and rate date that do not exist for a currency, the report does not calculate unrealized gains or
losses for that currency.
375
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Report Output
This table describes important column headings in the Projected Gains and Losses Report.
Ledger Currency Amount The transaction amount converted to the ledger currency.
Revaluation Rate Rate that the report uses to revalue the balance of the transaction.
Revaluation Gain Unrealized gain between the revalued amount and the entered amount.
Revaluation Loss Unrealized loss between the revalued amount and the entered amount.
This table describes important row headings in the Projected Gains and Losses Report.
Customer Account Number and Summary section for each customer account.
Customer Name
Total for Type [Transaction Type] The total unrealized gain and unrealized loss for each transaction type per customer account.
Total for Customer [Customer Name] The total unrealized gain and unrealized loss for each customer account.
Total for Report The total unrealized gain and unrealized loss for all customer accounts in the report.
This table describes the currency summary headings in the Projected Gains and Losses Report.
Foreign Invoice Amount The total transaction amount in each foreign currency.
376
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Ledger Currency Invoice Amount The total transaction amount in the ledger currency for each foreign currency.
Revaluation Rate Rate that the report uses to revalue the transaction amount for each foreign currency.
Revaluation Gain The total unrealized gain between the revalued amount and the entered amount for each
currency.
Revaluation Loss The total unrealized loss between the revalued amount and the entered amount for each
currency.
Total for Report The total unrealized gain and unrealized loss for all open items on this report.
Overview
The Receivables Aging by General Ledger Account Report helps you review information about outstanding receivables
balances.
Key Insights
You can use this report either during reconciliation or to age or summarize open receivables.
377
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Manager during period close processing.
When do I use this report? Review information about your customer outstanding receivables balances by general ledger
account as of a specic accounting date.
• If you are including credits in reconciliation, set the Show Open Credits parameter to Age to include credits in
the total customer balance.
• When reconciling by general ledger account, set the Report Summary parameter to Customer Summary to
display grand totals by accounting exeld.
Caution: Do not use Advanced Collections Aging reports for reconciliation, because they do not include
general ledger account information. This applies to these three reports:
• Aging by Common Currency Report
• Collections Aging 4 Bucket Report
• Collections Aging by Collector 7 Bucket Report
378
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Always select specic balancing segment values rather than running the report for all values.
Report Summary
• Customer Summary: Prints customer names with their total open balances.
• Invoice Summary: Prints information on all customer open receivables.
Report Format
Aging Bucket
Note: When using the report for reconciliation, set the Show Open Credits parameter to Do Not Show, if you
did not include these items in the Receivables to General Ledger Reconciliation extract and report.
Receipts at risk are standard receipts that have not been cleared or factored receipts that have not been risk eliminated:
• Age: Include receipts at risk in this report. The report displays the receipts at risk with other open receipts in the
appropriate bucket and includes them when determining the customer balance.
• Do Not Show: Receipts at risk are not included in this report.
• Summarize: Displays the sum of your receipts at risk in the Customer Credit Memos, Customer Payments, and
Customer Balance rows.
Note: When using the report for reconciliation, always set the Show Receipts at Risk parameter to Do Not
Show.
379
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Report Output
The report can include both detail and summary information about customer current and past due invoices, debit
memos, and chargebacks. If you set the Report Format parameter to Detailed, the report provides totals by customer
site. If you set the Report Format parameter to Brief, the report provides totals by customer account number.
Report Headings
Company
The balancing segment of the receivables account associated with the transaction included in this group.
Accounting Flexeld
The general ledger account concatenated segments and concatenated description.
Row Headings
Company Total
The total outstanding amount for the balancing segment value of the accounting exeld. This heading only
appears when the Report Summary parameter is set to Invoice Summary.
• If you set the Show Open Credits parameter to Do Not Show or Summarize, the report does not include credit
item amounts in your company total.
• If you set the Show Open Credits parameter to Age, the report includes credit item amounts in your company
total.
Customer Balance
The total balance for each customer when you set the Show Open Credits parameter to Summarize. This balance
includes all debit and credit items for each customer.
Total Debits
If you set the Show Open Credits parameter to Age, this total includes both debit items and credit items.
Customer Payments
If you set the Show Open Credits parameter to Summarize, this displays the total amount of payments for each
customer within this site. Payments include both unapplied and on-account cash. This total is included in the
Customer Balance row for each customer.
Customer Balance
The total balance for each customer.
• If you set the Show Open Credits parameter to Do Not Show or Age, the report does not include on-account
payments, unapplied payments, and on-account credits in your customer balances.
• If you set the Show Open Credits parameter to Summarize, these credit items are included in your customer
balances.
380
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Site Balance
If you set the Show Open Credits parameter to Summarize, this displays the total balance for each site. This
balance includes all debit and credit items for each customer.
If you set the Show Open Credits parameter to Summarize, this total does not include credits.
381
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Receivables Open Items Revaluation Report is used to revalue your open items, including invoices, credit memos,
and debit memos.
Key Insights
Revalue open items based on the revaluation rate that you specify, which is either an end-of-period rate or a daily rate.
The report is divided into sections for each unique combination of balancing segment and receivables account.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
382
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
Who uses this report? Financial Manager during period close processing.
When do I use this report? When you need to revalue your customer open transactions for determining the amount
needed to manually adjust your general ledger balance to reect the dierence between the
original and revalued balance.
• Open Original Amount: The value of your open items before revaluation, which you can reconcile with your
general ledger balances. The report also provides a complete list of all open items and explains the balance of
your receivables account.
• Revaluation Open Amount: The value for each revalued open item with the revaluation rate. This itemized total
is required in some countries.
• Open Revalued Amount: The higher of the two item values both before and after the revaluation. The report
adds up these values and calculates the dierence. This total is required in some countries, where the lower
market value of open items needs to be determined.
The report is divided into sections for each unique combination of balancing segment and receivable account. Within
each section, the report lists open items for each customer.
The Receivables Open Items Revaluation Report determines the amount needed to manually adjust your general ledger
balance to reect the dierence between the original and revalued balance. This revaluation dierence is calculated and
summarized for each accounting exeld. You should reverse this adjustment at the beginning of the next period to
synchronize Receivables and General Ledger balances.
You can run the Receivables Open Items Revaluation Report for a revaluation period, up to a particular due date, and for
a range of balance segment values. Check that you have entered rate information for each currency that you use. Use
the Include Up To Due Date parameter to split your assets into short-term, mid-term, or long-term receivables.
Report Parameters
Revaluation Period
The accounting period that you want to revalue. All open transactions with transaction dates up to the last date of this
period are selected.
383
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Enter a date if you want to dierentiate short-term, mid-term, and long-term receivables. Otherwise, leave this eld
blank. The date is the maximum due date included in this report.
Rate Type
If you select Daily as your rate type, select a conversion rate type.
Conversion Date
If you select Daily as your rate type, select the conversion date.
Transferred to GL Only
• Yes: Include only transactions transferred to general ledger. Only receipts transferred to general ledger aect
open balances.
• No: Include both posted transactions and transactions and receipts not yet posted to aect open balances.
Cleared Only
Balancing Segment
Dene the ltering conditions for the balancing segment values to include or exclude.
Report Output
This table describes the report headings in the Receivables Open Items Revaluation Report.
Balancing Segment Each value of the balancing segment for the selected balancing segment range.
Accounting Flexeld The accounting exeld for each of the accounts with the balancing segments within the
selected range.
This table describes the column headings in the Receivables Open Items Revaluation Report.
384
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Open Original Amount The transaction amount in the entered currency. The report prints an asterisk if the open
amount diers from the original amount. The open amount may dier if receipts were applied
or adjustments made to the transaction.
Conversion Rate The conversion rate used for foreign currency transactions. This value is 1 for ledger currency
transactions.
Open Ledger Currency Amount The ledger currency balance of the transaction, valued at the conversion rate used when the
transaction was approved.
Revaluation Rate The rate that the report uses to revalue the balance of the transaction.
Revaluation Open Amount The transaction balance, revalued using the revaluation rate.
Open Revalued Amount The dierence between the Revaluation Open Amount and the Open Ledger Currency
Amount. During reconciliation, debit the receivables account if the dierence is positive; credit
the receivables account if the dierence is negative. In other words, Open Revalued Amount =
Revaluation Open Amount - Open Ledger Currency Amount (with sign).
This table describes row headings in the Receivables Open Items Revaluation Report.
Customer Name The name of the customer with items charged to the accounting exeld of the receivables
account.
Customer Account Number The account number of the customer with items charged to the accounting exeld of the
receivables account.
385
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
This table describes the summary headings in the Receivables Open Items Revaluation Report.
Accounting Flexeld The accounting exeld that totals are calculated for.
Open Ledger Currency Amount The total for each accounting exeld, balancing segment, and the entire report.
Revalued Amount The total for each accounting exeld, balancing segment, and the entire report.
Dierence The total for the dierence between the Open Ledger Currency Amount and the Revaluation
Open Amount for each accounting exeld, balancing segment, and the entire report.
Open Revalued Amount The total for each accounting exeld, balancing segment, and the entire report.
Dierence The total for the dierence between the Open Ledger Currency Amount and the Open
Revalued Amount for each accounting exeld and the entire report.
386
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Receivables to General Ledger Reconciliation Report is the primary tool for the reconciliation of receivables data to
the general ledger.
Key Insights
The report provides both summarized and detailed reconciling data for review and analysis.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables to Ledger
Reconciliation
Who uses this report? Financial Manager during period close processing.
When do I use this report? When you are reconciling your receivables to your general ledger balances.
387
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
What can I do with this report? Review report after running the Prepare Receivables to General Ledger Reconciliation
scheduled process.
388
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• Bills receivable
• Bills receivable application
Note: On-account credit memo refund amounts and on-account credit memo gain or loss amounts are
included in the Invoices section of the Reconciliation report, because they aect the open balance of the
receivable amount of the credit memo. In all cases the intent is to close the credit memo, so both the original
credit memo and the activity against it are displayed.
The report also reconciles manual journal entries created in the Receivables subledger.
If your business unit is implicitly mapped to the primary balancing segment value in the chart of accounts, you can
run the report to reconcile by either business unit or ledger. If there is no implicit mapping, then you must reconcile by
ledger.
There is one important dierence between a Closed and Close Pending status. If the period status is set to Closed,
Receivables checks for incomplete invoices and orphan accounting lines. These validation checks are not performed
under a Close Pending status.
Note: You can't reopen a Closed or Close Pending Receivables accounting period once the general ledger
accounting period has been closed. This guarantees that the subledger is properly synchronized to the general
ledger.
The Receivables to General Ledger Reconciliation Accounting variance report captures information related to these two
causes of data corruption:
• Accounting entries in general ledger sourced from subledger accounting that are present in the general ledger
tables, but not available in the subledger accounting tables.
• Accounting entries transferred from the subledger to general ledger that are present in the subledger
accounting tables, but are not available in the general ledger tables.
389
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
What's the dierence between a closed and close pending accounting period?
To set an accounting period to the Closed status, you must rst clear any unposted items. Once an accounting period is
closed, journal entry, transaction entry, and posting are not allowed unless you reopen the accounting period.
The Close Pending status diers from the Closed status in two ways:
• This status doesn't validate for unposted items.
• You can still create journal entries for activity that existed in the accounting period prior to seing it to Close
Pending.
390
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Bad Debt Provision Report provides information about your bad debt exposure.
Key Insights
The report uses the percent collectible value that you specify in the Collectible eld of the Credit and Collections
section of the customer account prole to calculate the bad debt provision.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Accounting
Who uses this report? Financial Manager during period close processing.
When do I use this report? When you need customer overdue transaction collectibility information to create the provision
for bad debt accounting journals.
391
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
Report Output
The report by default sorts information by customer account status, but you can sort the information within each
account status by customer name or customer account number.
This table describes column headings in the output of the Bad Debt Provision Report.
Class and Transaction Type In the context of this report, any activity against an open item, including payments.
Ledger Currency Bad Debt Provision The bad debt provision based on the ledger currency balance due and the percent that is
uncollectible.
This table describes row headings in the output of the Bad Debt Provision Report.
Total for Customer [Name] The total balance due and provision for each customer in the ledger currency.
Total for Report The total balance due and provision for all customers in the report in the ledger currency.
392
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Customer Account Status Report displays detailed information about each of your customer accounts.
Key Insights
The report displays for each customer all open debit items, credit items, and total balance due in the ledger currency.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Specialist or Financial Manager when analyzing customer accounts.
393
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
When do I use this report? When you want to analyze the detail that makes up the customer account balances by specic
account statuses or collectors.
Arrange the information in the report by Collector, Customer Name or Customer Account Number.
Limit the report to customer accounts within a range of account statuses. The range you specify includes all statuses in
alphabetic order.
Report Output
This table describes important column headings in the Customer Account Status Report.
Transaction Number Either the transaction number or the receipt number for customer payments.
Transaction Date Either the transaction date for an invoice, debit memo, credit memo or on-account credit, or
the receipt date for customer payments.
Transaction Type The transaction type for each transaction in the report. If this is a payment, the report displays
Payment.
394
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Transaction Due Date The date payment is due for the transaction. If the transaction is an installment invoice, the
report displays a separate row for each due date.
Original Amount in Ledger Currency The original amount of the transaction in the ledger currency. The report displays credit items
as negative numbers.
Balance Due in Ledger Currency The remaining amount due for each transaction converted to the ledger currency. The report
displays credit balances as negative numbers.
This table describes important row headings in the Customer Account Status Report.
Total for Account Status The total balance due for each account status in the ledger currency.
Total for Collector (collector name) The total balance due for each customer site in the ledger currency.
and Customer Site (site number)
Total for Report The total balance due for the entire report in the ledger currency.
395
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Overview
The Customer Balance Revaluation Report identies customers with credit (negative) balances.
Key Insights
The report provides the balance of a customer and the open items that make up the balance, and lists customers by
positive and negative balance.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
Who uses this report? Financial Manager during period close processing.
When do I use this report? When you need to create accounting journals for revaluated customer accounts and identify
customers with negative balances.
396
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
FAQ Answer
• Independent from the accounting entries for your receivables account, this report gives you the balance of your
customer and the open items that make up the balance. It takes into account on-account receipts.
• The report lists the customers with a negative balance only, customers with a positive balance only, or
both positive and negative balances, depending on the seing of the Customer Balance parameter. This
information is needed for countries that require a separate entry on the balance sheet for customers with a
negative balance.
Use the results of this report to determine the amount you need to manually adjust your general ledger balance to
reect the dierence between the original balance and the revaluated balance. You would then reverse this entry at the
beginning of the following period to resynchronize your receivables with general ledger accounts.
Note: Make sure you have entered an End-of-Period (EOP) rate for each currency used. If any EOP is missing,
the report noties you that the results calculated may be incorrect.
Run this report in conjunction with both your customer account reviews and reconciliation activities.
If you want to dierentiate short-term, mid-term, and long-term receivables activities, enter a date in this parameter.
Otherwise, leave the eld blank.
Customer Balance
Report Output
This table describes important column headings in the Customer Balance Revaluation Report.
397
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Open Original Amount The balance of the transaction in the entered currency.
Conversion Rate The conversion rate for foreign currency transactions. This value is 1 for ledger currency
transactions.
Open Ledger Currency Amount The balance of the transaction in the ledger currency valuated at the conversion rate used
when the transaction was approved.
EOP Rate The End-of-Period rate, which the report uses to revaluate the balance of the transaction.
EOP Open Ledger Currency Amount The balance of the transaction in the ledger currency revaluated using the EOP rate.
Open Revaluated Amount Receivables uses the lower of the Open Ledger Currency Amount and the EOP Open Ledger
Currency Amount to determine the market value of the open item.
This table describes important row headings in the Customer Balance Revaluation Report.
Customer Name/Customer Account The customer name, customer account number, and customer site with open items.
Number
Total The total open ledger currency amount, EOP open ledger currency amount, and open
revaluated amount for the customer.
Balance for [Customer Name] The total open balance for the customer in the ledger currency.
Debit The sum of the positive open items for the customer.
Credit The sum of the negative open items for the customer.
398
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
Tip: The Debit and Credit totals help you determine the amount of the adjustments to your general ledger
balances.
399
Oracle Financials Cloud Chapter 4
Using Receivables Credit to Cash Manage Accounts Receivable Balances
• Chargeback
• Payment (receipt)
Activity against an individual transaction or receipt refers to the specic debits, credits, reversals, and adjustments that
constitute the history of one receivables item.
400
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
The Recognize Revenue process also creates the receivable, tax, freight, and AutoInvoice clearing account assignments
which correspond to the accounting date of each transaction included in the process submission.
Note: The Recognize Revenue process creates accounting distributions for all periods of status Open, Future,
or Not Open. If any period has a status of Closed or Close Pending, then the Recognize Revenue process
creates the distributions in the next Open, Future, or Not Open period.
If you later decide that the revenue distributions need to be reclassied, you can update the individual revenue
distribution on the transaction. Receivables automatically creates the necessary reverse accounting entries.
Each run of the Recognize Revenue process generates a Revenue Recognition Execution report. Use this report to
review the details of revenue recognition on your transactions, as well as any records that failed processing.
• Partially Processed Transactions: If some but not all of the transaction lines are successfully processed, then the
transaction appears as Partially Processed. For example, if processing succeeded for lines 1 and 2 of an invoice
that has 3 invoice lines, the report displays one record for line number 3 with the accompanying line details.
401
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
• Unprocessed Transactions: If all of the transaction lines weren't processed, then the transaction appears as
Unprocessed. For example, if processing failed for all 3 lines of an invoice, the report displays three record
entries, one for each line, with the accompanying line details.
The main reason for failure to process revenue on a transaction or transaction line is data corruption on the transaction.
Two examples of data corruption are:
Note: The Transactions with Invalid Accounts section only appears on the execution report when the
Recognize Revenue process is submied in Summary mode.
This section lists all successfully processed transaction lines that have invalid revenue accounts.
An invalid revenue account doesn't prevent the processing of transactions and transaction lines for revenue
recognition. If a transaction contained transaction lines that failed processing for revenue recognition, then the failed
transaction lines appear instead in the Unprocessed or Partially Processed Transactions section. In this case, the
same transaction number may appear on both sections of the report, if there were both transaction lines that failed
processing and transaction lines that were processed successfully but with invalid revenue accounts.
Related Topics
• How Revenue Scheduling Rules Are Used
If you use a deferred revenue scheduling rule with multiple accounting periods, Receivables creates the revenue
recognition schedule based on the rule, and the start date is determined by the accounting start date that you provide.
If the accounting start date occurs in a closed accounting period, Receivables posts that portion of revenue into the
subsequent open accounting period.
If you use a non-deferred revenue scheduling rule with multiple accounting periods, Receivables uses the schedule
created by the Recognize Revenue program. If an accounting period is closed, Receivables posts that portion of revenue
into the subsequent open accounting period.
The following examples illustrate revenue recognition with deferred and non-deferred revenue scheduling rules.
402
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
The February 2 row shows what the original revenue recognition schedule is if the revenue scheduling rule is not
deferred. However, because the rule is deferred, Receivables creates a single distribution line that posts to an unearned
revenue account when you run the Recognize Revenue program.
You can then earn the revenue on this invoice, but you enter March 2 as the accounting start date. Receivables honors
the original schedule, illustrated by the February 2 row, but ignores the original start date from the transaction and uses
the March 2 accounting date that you entered. This shifts the schedule by one month, as illustrated by the March 2 row.
The February 2 row shows the original revenue recognition schedule that Receivables creates when you rst run the
Recognize Revenue program. At this stage, February is open.
You then discover that the schedule was incorrect, so you unearn and then correctly re-earn the invoice revenue. When
you re-earn revenue on invoices with non-deferred revenue scheduling rules, Receivables uses the original schedule, as
illustrated by the February 2 row.
But because February is now closed, Receivables posts the February allocation to March, as illustrated by the March 2
row.
403
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
It may also happen that Receivables can't automatically record certain contingencies, such as the completion of a
particular service. In these cases you need to manually schedule revenue recognition.
Note: Once you manually adjust revenue, Receivables discontinues the automatic monitoring of
contingencies on the related transactions.
You can expire a time-based contingency if the terms of the contingency are met in advance of the specied time
period, such as a change in time-period for a funding clause or acceptance clause.
404
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
Optionally enter a value in the Sales Credit Percent Limit eld on Receivables system options to limit the percentage of
revenue plus non-revenue sales credit that a salesperson can have on any transaction line. If you don't enter a value for
this system option, then no sales credit limit validation is performed during revenue accounting.
405
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
Note: You can't set an invoice with active revenue contingencies to Incomplete.
Adjust Revenue
When you move revenue on an invoice line from an unearned to an earned revenue account, or vice versa, this action
removes the invoice line revenue contingencies. The invoice is no longer subject to automatic revenue recognition.
This does not apply to adjustments to sales credits, because you can only adjust sales credits on revenue that has
already been scheduled.
Adjust Invoices
You can manually adjust an invoice with revenue contingencies. However, if the GL Account Source for the specied
adjustment activity is Revenue on Invoice, then Receivables removes the contingency from the invoice after making
the adjustment. This is because AutoAccounting derives the anticipated revenue accounting distribution accounts and
amounts, thereby overriding the event-based revenue management process.
If you want Receivables to continue monitoring an invoice for automatic revenue recognition, then always use a credit
memo to adjust an invoice with contingencies.
Receivables removes the contingencies from the invoice for these types of changes:
• For distributions, you change an existing accounting distribution to a revenue or any other account.
• For sales credits, you rerun AutoAccounting when you modify sales credits.
Credit Invoices
If you issue a credit memo against an invoice that had revenue automatically deferred upon import, then the impact of
the credit memo on the invoice diers depending on the original reason for the revenue deferral. This applies only if
you set the Invoice Accounting Used for Credit Memos prole option to Yes.
For example, you apply a credit memo against an invoice that had revenue deferred due to one or more contingencies,
but some of the revenue was partially recognized. A portion of the invoice revenue, therefore, is still in an unearned
revenue account. Dierent procedures apply depending on whether the contingencies are payment-based or time-
based:
• Payment-based contingencies: If revenue on this invoice was deferred due to unmet payment-based
contingencies, then Receivables always debits the unearned revenue account for the full amount of the credit
memo, according to the initially assigned revenue scheduling rules.
Caution: This is a departure from standard functionality. When you credit an invoice that is not
under evaluation for event-based revenue management, Receivables prorates the amount of the
credit memo between the earned and unearned revenue invoice amounts.
If the amount of the credit memo exceeds the amount of the unearned revenue on the invoice, and the credit
memo transaction type allows overapplication, then Receivables records the excess amount as a debit to the
unearned revenue account. You can optionally clear the negative unearned revenue on this invoice.
• Time-based contingencies: If revenue on this invoice was deferred due to unexpired time-based contingencies,
then Receivables always prorates the credit memo amount between the earned and unearned revenue
406
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
amounts on the invoice. If a multi-period revenue scheduling rule exists on an invoice, then Receivables further
prorates the credit memo amount across future periods.
If you apply a credit memo against an invoice with revenue that was already manually adjusted, then Receivables
follows standard credit memo functionality. Receivables prorates the credit memo amount between the earned and
unearned revenue amounts on the invoice, even if the invoice was initially analyzed for collectibility and acceptance.
In this case, you must conrm that the earned and unearned revenue on the invoice is stated appropriately for each
period. If necessary, use the Manage Revenue Adjustments pages to make any further adjustments.
Reverse Receipts
If you apply a receipt to an invoice with revenue contingencies, and you later reverse the receipt, the impact of the
receipt reversal diers depending on the original reason for the revenue deferral.
Dierent procedures apply depending on whether the contingencies are payment-based or time-based:
If revenue on an invoice was deferred due to unexpired time-based contingencies only, then the reversal of a
receipt does not impact the amount and timing of revenue recognition. For example, if all lines of an invoice
are associated with a nonstandard refund policy (90 days), Receivables recognizes revenue only upon the
expiration of the 90-day period. Applying and later reversing a receipt against this invoice has no impact on the
timing and amount of revenue recognition.
If you transfer only 5%, the new salesperson receives 5% of the line total and the transferred amount is prorated among
the three salespersons.
407
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
Salesperson 1 20 5% .05 * 20 = 1
Note: To safely update sales credits on transactions that have had revenue adjustments, you should always
use the Manage Revenue Adjustments pages.
Related Topics
• How do I manage sales credits
• Payment-based contingencies: Receivables recognizes revenue on the invoice line or portion of the invoice line
when payment is received.
• Time-based contingencies: Receivables recognizes revenue only when the contingency expires.
If no unexpired contingencies remain on the invoice line, Receivables initiates revenue recognition according to the
initially assigned revenue scheduling rule. If other unexpired contingencies remain on the invoice line, Receivables
doesn't initiate revenue recognition for the invoice line.
408
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
After 60 days, the scal funding clause on Lines 2 and 3 expires. Receivables initiates revenue recognition in full for
Lines 2 and 3.
After another 30 days, the cancellation provision on Line 5 expires. Receivables initiates revenue recognition in full for
Line 5.
Receivables doesn't recognize revenue on this invoice line until the acceptance clause expires after 120 days. If, for
example, you obtain wrien acceptance from the customer after 80 days, you can record early acceptance to allow
revenue recognition.
Note: The accounting date when you enter early acceptance becomes the revenue recognition date for this
invoice line.
After 45 days, you apply a $500 receipt against the invoice. Because it is a partial payment, Receivables prorates this
payment across the two invoice lines, based on the weighted average formula:
• Receivables recognizes revenue for Line 1 in the amount of $65.21.
• Receivables can't recognize revenue for Line 2 because of the acceptance clause and cancellation provision.
Receivables instead assigns $434.79 for Line 2 as an amount that is pending revenue recognition.
After 60 days, the acceptance clause on Line 2 expires. However, Receivables can't recognize the $434.79 that is still
pending because of the cancellation provision.
409
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
After 150 days, the acceptance clause on Line 2 expires, and Receivables recognizes the entire $1,000 in revenue for
Line 2.
Related Topics
• Revenue Contingencies
Payment in Full
You import invoice 2002 for $600, and Receivables defers all revenue because the customer is not creditworthy. You
later apply a payment of $600 against this invoice.
Since payment in full was received and applied against the invoice, Receivables recognizes the revenue by debiting
$600 from the unearned revenue account and crediting $600 to an earned revenue account, according to the initially
assigned revenue scheduling rule.
Note: Revenue that is recognized based on receipt application can never exceed the original amount due on
the invoice line, less any applicable credit memos. If there is an overpayment, Receivables doesn't recognize
the overpayment as revenue, even if the transaction allows overapplication.
You then apply a receipt for $100 against this invoice. Because the customer is not creditworthy, Receivables can
recognize revenue only to the extent of the applied receipt. Because this is a partial receipt, Receivables must calculate
how much revenue to aribute to each invoice line.
When applying a partial receipt, Receivables uses a weighted average formula to calculate the revenue amounts to
recognize for each line. Receivables calculates the revenue for each line as follows:
• Line 1 = $50
($50/$350) * $100 = $14.28571
Receivables rounds this amount down to $14.28.
• Line 2 = $100
((($100+$50)/$350) * $100) - $14.28 = $28.5771
Receivables rounds this amount down to $28.57.
• Line 3 = $200
((($200+$100+$50)/$350) * $100) - ($14.28 + $28.57) = $57.15
Receivables rounds the last amount up to account for the rounding of the previous lines.
Any future receipts applied against this invoice are calculated for revenue for each line in the same way.
410
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
Receivables reviews the original invoice 3003, and determines that revenue was deferred because:
• Invoice 3003 was assigned extended payment terms.
• Line 3 is associated with a non-standard refund policy contingency.
• Line 5 is associated with a cancellation provision contingency.
Since the $400 receipt is a partial payment, Receivables prorates this payment across the invoice lines, based on the
weighted average formula. However, for simplicity, assume that Receivables applies $80 to each invoice line:
• Receivables recognizes revenue for Lines 1, 2, and 4 in the amount of $80 each.
• Receivables can't recognize revenue for Lines 3 and 5 due to the unexpired time-based contingencies.
Receivables therefore marks the $80 payments for Lines 3 and 5 as amounts that are pending revenue
recognition at a later date.
When the contingencies later expire, Receivables recognizes revenue for Lines 3 and 5 in the amount of $80 each. Any
future receipts applied against this invoice are analyzed in the same way.
Ineligible Transactions
You apply a payment for $200 against invoice 1001. After reviewing the original invoice 1001, Receivables determines
that this transaction was never eligible for automatic revenue recognition. This could be for one of several reasons:
• The invoice wasn't created manually or imported using AutoInvoice.
• A deferred revenue scheduling rule is assigned to the invoice.
• Event-based revenue management was never activated for the invoice. Either there is no default revenue
policy, or contingencies didn't exist on the invoice during import.
In this case, Receivables doesn't proceed with further analysis of this receipt. Applying a payment to invoice 1001 won't
trigger revenue recognition.
411
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
First Transaction
This table shows the initial accounting entry:
Second Transaction
You apply a $300 receipt against the invoice, 45 days after the invoice date.
• $80 to Line 1.
• $180 to Line 2.
• $40 to Line 3.
• Receivables can't recognize revenue for Line 1 or Line 3 due to the related contingencies. Receivables records
payments to Line 1 and Line 3 as amounts that are pending revenue recognition at a later date.
• Receivables can only recognize revenue for Line 2.
The total amount due on this invoice is now $450. The unearned revenue amount on this invoice is $570.
412
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
Third Transaction
You apply a credit memo for $200 against this invoice.
Because this invoice has a combination of payment-based and time-based contingencies, the balance of the credit
memo is not prorated between the unearned revenue and revenue accounts. Instead, Receivables credits the
receivables account and debits the unearned revenue account for the full amount of the credit memo.
The total amount due on this invoice is now $250. The unearned revenue amount on this invoice is $370.
Fourth Transaction
After 90 days pass, the refund policy expires. Receivables initiates revenue recognition for the amount of the receipt
that you previously applied to Line 1.
The total amount due on this invoice is still $250. However, the unearned revenue amount on this invoice is $290.
Fifth Transaction
You apply a credit memo for $150 against this invoice.
Because the invoice still has a combination of payment-based and time-based contingencies against it, Receivables
credits the receivables account and debits the unearned revenue account for the full amount of the credit memo.
413
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
The total amount due on this invoice is now $100. The unearned revenue amount on this invoice is $140.
Sixth Transaction
After 120 days pass, the cancellation policy expires. Receivables initiates revenue recognition for the amount of the
receipt that you previously applied to Line 3.
The total amount due on this invoice is still $100. The unearned revenue amount on this invoice is $100.
Seventh Transaction
You apply a $100 receipt against the invoice.
414
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
If a revenue scheduling rule with more than one period exists, Receivables uses the original start date and revenue
recognition schedule on the transaction.
After you post to general ledger, you must use the Manage Revenue Adjustments pages to update sales credits.
Note: For rule-based transactions, you can't use the Create and Edit Transaction pages to update sales credits
or modify salespersons after running revenue recognition, even if the transaction is incomplete. You must use
the Manage Revenue Adjustments pages.
415
Oracle Financials Cloud Chapter 5
Using Receivables Credit to Cash Manage Revenue for Receivables
416
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
You can apply full or partial transaction amounts to a bill. To apply a partial amount, update the Applied Amount eld
with the amount that you want. The unapplied portion of a transaction remains an open item.
If you designated an amount for the bill receivable, you must apply transactions to equal the designated amount. You
can't complete a bill receivable with a designated amount until the total transaction application amounts equal this
amount.
Note: Transactions applied to a bill receivable follow the natural application rule, even though the individual
transactions assigned to the bill may allow for overapplication.
You can only apply transactions that have the same currency as the bill receivable, and all transactions applied to the bill
must share the same conversion rate. The bill inherits the conversion rate from the transactions assigned to it when you
complete the bill. If you want to apply transactions with a dierent currency, you must remove all transactions currently
applied to the bill and change the currency of the bill.
Related Topics
• Prepare Transactions for Bills Receivable Batches
In addition to preparing eligible transactions, review these setups and guidelines before running the Create Bills
Receivable Batch program to create bills receivable from transactions:
• Bills Receivable Transaction Sources
• Bills Receivable Dates
417
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
If you are using a bills receivable creation receipt method that has the Inherit Transaction Number option enabled,
automatic numbering of bills receivable occurs in this way:
• If the program creates a bill receivable from one transaction only, the bill receivable number inherits the
transaction number, unless the transaction number is already used by another transaction with the same
transaction source as the bill receivable.
• If the transaction number of a bill receivable created from one transaction only is already used by another
transaction with the same transaction source as the bill receivable, or if the program creates a bill receivable
from more than one transaction, the program uses the automatic transaction numbering seings on the
transaction source.
Date Guideline
Accounting Date Enter an accounting date that belongs to an open or future period. Bills receivable that don't
require customer acceptance can inherit the accounting date of the batch.
For bills receivable that require customer acceptance, the accounting date is derived from the
acceptance accounting date that you enter when the customer accepts the bill.
Issue Date
The issue date is the date that the bill receivable is created. You must enter an issue date that
is:
Maturity Date The maturity date is the date when full payment is due on the bill receivable. The maturity
date can't be earlier than the issue date. If you don't enter a date in this parameter, Receivables
derives the maturity date from the bills receivable creation receipt method.
418
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Seing Guideline
• Belonging to the reference set of the business unit selected for the program run.
• Assigned to the bills receivable creation receipt method of the program run, if one is
selected.
If you want to use transactions belonging to more business units, then set up and assign
to transactions the necessary number of bills receivable creation receipt methods and bills
receivable transaction types to include all reference sets with all the applicable business units.
• If the rule is One per Customer or One per Customer Due Date, then at least one
customer must contain an active drawee site dened as Primary. These rules cannot
group transactions from dierent customer sites with no site dened as Primary.
• If the rule is One per Invoice, One per Payment Schedule, One per Site, or One per
Site Due Date, then a primary drawee site is not required, but the customer bill-to site
must also be a drawee site. These rules cannot group transactions if there is no bill-to
site dened as a drawee site.
Related Topics
• Prepare Transactions for Bills Receivable Batches
• Create a Bills Receivable Creation Receipt Method
• Bills receivable inherit transaction numbers option is enabled on the bills receivable creation receipt method
assigned to the transaction.
• Transaction number is not already used by another transaction with the same transaction source as the bill
receivable.
419
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
If the Bills receivable inherit transaction numbers option is not enabled, or if the bill contains more than one
transaction, then the batch process numbers bills receivable according to the transaction source assigned to the batch.
Ordinarily, a bills receivable transaction source has the Automatic transaction numbering option enabled. If you
are using document sequences and the Copy document number to transaction number option is enabled, then
Receivables uses the document sequence number assigned to the bill as the bill receivable number.
Related Topics
• Guidelines for Transaction Numbering
• Create a Bills Receivable Creation Receipt Method
If the bill receivable requires drawee acceptance, completing the bill changes its status to Pending Acceptance. While a
bill receivable has the status of Pending Acceptance, you can't perform any other activity on the transactions belonging
to the bill, such as applying receipts, credit memos, or adjustments. When you receive wrien acceptance from the
customer, you can accept the bill receivable.
If the bill receivable doesn't require drawee acceptance, completing the bill changes its status to Pending Remiance
and these actions are performed:
• Record the rst accounting for the bill.
• Reduce the amount due on the applied transactions.
• Assign the bill receivable to the outstanding balance of the customer drawee.
If you are using document sequencing, Receivables ignores the Document Number Generation Level Receivables
system option and generates the document number when you complete the bill receivable. If the Copy Document
Number to Transaction Number option on the bills receivable transaction source is enabled, then the document
number and bill receivable number are the same.
420
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
This accounting date becomes both the accounting date for the bill receivable and the acceptance accounting
date for the transactions applied to the bill. Receivables calculates the acceptance accounting date according to
the open accounting period rules for the applied transactions.
Related Topics
• What's the dierence between a signed and unsigned bill receivable
What's a drawee?
A drawee is a customer who accepts funding in the form of a bill receivable with the intention of repaying the party that
issues the bill when it matures.
421
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Can I continue to add and remove transactions to and from the bill receivable?
Yes, up until the bill is completed or, for bills that require acceptance, until the bill is accepted.
• The bill receivable is a signed bill with the status Pending Acceptance, or an unsigned or drawee-issued bill with
the status Pending Remiance.
• The bill has never been posted to general ledger.
• There are no payments against the bill.
You can also incomplete a bill receivable to update details of the bill and complete the bill again.
• Standard remiances: You remit bills receivable to your bank, and the bank manages the collection process. On
the bill receivable maturity date, the bank collects payment in full from your customers and transfers the funds
directly to your bank account, less any fees or other charges. With standard remiances, you bear the nancial
risk of customer default.
• Factored remiances: You remit bills receivable as collateral in return for cash advances or loans from your
bank. Receivables creates a receipt for the bill receivable upon remiance. If the bill receivable is factored with
recourse, you bear the nancial risk of customer default, and Receivables records a short term debt for the
default risk. If the bill receivable is factored without recourse, the bank assumes the risk of customer default,
and Receivables closes the bill upon creation of the remiance.
When you create a bills receivable remiance, the receipt class determines the remiance processes, and the bills
receivable remiance receipt method assigned to the receipt class determines the accounting for the bills receivable.
Receivables selects qualifying bills receivable for remiance and groups them according to the remiance bank that
is assigned to each bill. You can specify additional selection criteria to limit the bills receivable that are selected for
remiance.
422
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Based on the remiance bank information, Receivables selects the following bills receivable for inclusion in the batch:
• Bills receivable with the same remiance bank account as the remiance batch.
• Bills receivable with no remiance bank account.
• Bills receivable with a dierent bank account from that of the remiance batch, if the Ignore Override option is
not enabled.
Note: You can change the batch remiance bank information after the remiance batch is created. However,
you will receive a warning if the remiance bank of any bill receivable in the batch is dierent from the new
remiance bank of the batch, unless the Override bank option is enabled on that remiance bank account.
After you have entered information for the batch and your selection criteria, use the Save buon to generate the bills
receivable remiance batch. Receivables validates the status, currency, and remiance bank information of the bills
receivable included in the batch. Receivables then selects bills receivable in maturity date order, starting with the earliest
maturity date.
Once a bill receivable is selected for a remiance batch, you can't apply customer payments or other activities to the bill,
or select the bill for another remiance batch.
After creating the remiance batch, use the Mange Bills Receivable Remiance Batches page to review, update, and
approve the batch.
Related Topics
• Create a Bills Receivable Remiance Receipt Method
• Create a Remiance Bank Account for Bills Receivable
The receipt creation process diers for standard and factored remiances:
• Standard remiances: Run the Close Matured Bills Receivable program to create receipts and apply them to
bills receivable, either at the maturity date plus the number of collection days or at the remiance date plus
423
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
the number of collection days, whichever is later. Receivables updates the status of the bill receivable to Closed
when the receipt is applied to the bill receivable.
• Factored remiances: Receivables creates a receipt when a remiance is approved. For bills receivable that are
factored with recourse, the receipt is applied to short term debt and the status of the bill is updated to Remied.
For bills receivable factored without recourse, the receipt is applied to the bill receivable upon remiance and
the status of the bill is updated to Closed.
Related Topics
• Automatic Clearing of Receipts
• Remiance Methods and Clearance Methods
Process Tasks
You can run the Close Matured Bills Receivable process to accomplish a number of dierent tasks in relation to bills
receivable remiances.
For standard remied bills receivable, Receivables both creates the receipt and applies it to the bill receivable. The apply
date is the same as the receipt date. Receivables normally performs these operations on the bill maturity date. If the
bill was remied with insucient time for the bank to collect the funds from the drawee by the maturity date, then
Receivables performs these operations on the remiance date plus the number of remiance bank collection days.
424
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
You can clear receipts for standard remied bills receivable manually, or use the Clear Receipts Automatically process to
clear receipts that have a clearance method of Automatic Clearing.
For bills receivable factored with recourse, Receivables applies receipts created at the time of remiance to bills
receivable and eliminates the risk on each bill. The apply date is the bill receivable maturity date plus the number of risk
elimination days.
For standard remiances, Receivables uses the accounting date you enter unless the date is not in an open period, in
which case it will use the accounting date on the bill receivable. If the accounting date on the bill is also not in an open
period, then it uses the rst day of the next available open period.
For factored remiances, Receivables uses the accounting date you enter unless the date is not in an open period, in
which case it will use the accounting date entered for the remiance. If the accounting date entered for the remiance is
also not in an open period, then it uses the rst day of the next available open period.
When you reverse or unapply a receipt for a bill receivable, Receivables creates reversal journal entries for the receipt
application with either of these results:
• If the receipt is reversed before the maturity date, the status of the bill receivable is updated to Pending
Remiance.
• If the receipt is reversed after the maturity date, the status of the bill receivable is updated to Unpaid.
425
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Status Meaning
Pending Acceptance The bill was completed, but requires acceptance by the customer drawee.
Pending Remiance The bill was completed, and, if necessary, accepted, and is ready for remiance.
Remied The bill was remied to the bank for collection on the maturity date.
Factored The bill was remied to the bank for collection and an advance given for the bill amount.
Matured Pending Risk Elimination A bill factored with recourse has reached the maturity date but is still open to risk of default.
Unpaid Payment for the bill was not received on the maturity date.
Canceled The bill is canceled and the open debits returned to the original transactions.
Closed A standard bill was paid, or a factored bill had its risk eliminated.
426
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Receivables applies receipts created at the time of remiance to bills receivable and eliminates the risk on each bill. The
apply date is the bill receivable maturity date plus the number of risk elimination days.
You can use the Close Matured Bills Receivable program to apply receipts and eliminate risk on bills receivable factored
with recourse. The program performs these tasks:
You can also use the Eliminate Risk action to manually eliminate risk on a bill receivable. You can do this, for example,
if payment is received from the customer during the risk elimination period.
If a customer is at risk of not paying the bill receivable after risk has been eliminated, you can use the Reestablish
Risk action to reestablish risk on the bill. When you reestablish risk on a Closed bill receivable that was factored with
recourse, Receivables unapplies the receipt that was created when the bill was factored and applies the receipt to short
term debt. The status of the bill is updated to Matured Pending Risk Elimination.
• Pending Remiance, and the bill receivable has not been selected for remiance, placed on hold, or reserved by
another bill receivable pending acceptance.
• Standard Remied, and the bill receivable has matured.
• Matured Pending Risk Elimination.
• Closed, and the bill receivable has been matured as well as paid by one receipt.
• Protested.
When you mark a bill receivable as Unpaid, the status of the bill is updated to Unpaid and the open balance is recorded
as a debit to Unpaid Bills Receivable.
Receivables performs these additional actions depending upon the previous status of the bill:
• If the bill is Matured Pending Risk Elimination, Receivables reverses the receipt created when the bill was
factored with recourse.
• If the bill is Remied or Factored with Recourse and then Closed as Unpaid, Receivables reverses the receipt
created as a result of the remiance.
You can later remove a bill receivable from the Unpaid status by using the Restate action. When you restate a bill
receivable, Receivables reclassies the bill from Unpaid to Pending Remiance.
427
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
• If the bill receivable is recalled before the maturity date, the status of the bill receivable is updated to Pending
Remiance.
• If the bill receivable is recalled after the maturity date, the status of the bill receivable is updated to Unpaid.
If you are recalling a bill because payment was received, then after the recall you can apply the receipt directly to the bill
receivable.
Bills Receivable
When you complete a bill receivable, or accept a bill receivable if it requires acceptance, Receivables creates this journal
entry on the bill receivable:
If you cancel a bill receivable that is not Pending Acceptance, Receivables creates this journal entry on the bill receivable:
Receivable • Bills Receivable (if the bill has the status Pending Remiance)
• Unpaid Bills Receivable (if the bill has the status Unpaid)
428
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Remied Bills Receivable • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
• Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
On maturity (or maturity plus the number of collection days, if the bill is remied on or after maturity), Receivables
creates this journal entry on the receipt created:
Factored Bills Receivable • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
• Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
Receivables creates this journal entry on the receipt created when factoring with recourse:
When you eliminate the risk on a bill receivable factored with recourse, Receivables creates this journal entry on the
receipt created:
429
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
When you reestablish risk on a bill receivable factored with recourse, Receivables creates this journal entry on the
receipt created:
• Remiance (if the clearance • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
method used is By Automatic • Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
Clearing or By Matching)
• Cash (if the clearance method
used is Direct)
When you mark as unpaid a bill receivable with the status Standard Remied, Receivables creates this journal entry on
the bill receivable:
When you mark as unpaid a bill receivable with the status Closed that was previously standard remied:
430
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
• The accounting entries are reversed on the receipt that was applied to the bill receivable:
When you mark as unpaid a bill receivable with the status Matured Pending Risk Elimination or Closed that was
previously factored with recourse:
• Receivables creates this journal entry on the receipt created when the bill was factored with recourse:
• Receivables creates this journal entry on the negative miscellaneous receipt created when the bill receivable
factored with recourse is marked as unpaid:
431
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
When you mark as unpaid a bill receivable with the status Matured Pending Risk Elimination or Closed that was
previously factored without recourse:
◦ Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
• Receivables creates this journal entry on the receipt created when the bill was factored without recourse:
When you restate a bill receivable that was previously marked as unpaid, Receivables creates this journal entry on the
bill receivable:
Remiance before it was ◦ Factored Bills Receivable (if the bill was factored with recourse)
remied
◦ Unpaid Bills Receivable (if
the bill had the status Unpaid
before it was remied)
432
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
• Receivables creates this journal entry on the receipt created when the bill was factored:
◦ Bills Receivable (if the bill was ◦ Cash (if the clearance method used is Direct)
factored without recourse
and had the status Pending
Remiance before it was
remied)
◦ Unpaid Bills Receivable (if
the bill was factored without
recourse and had the status
Unpaid before it was remied)
• Cash (if the receipt was • Bills Receivable (if the bill has the status Pending Remiance)
cleared) • Unpaid Bills Receivable (if the bill has the status Unpaid or Protested)
• Remiance (if the receipt
wasn't cleared)
When you apply an on-account credit memo to a bill receivable, Receivables creates this journal entry on the credit
memo:
Receivable • Bills Receivable (if the bill has the status Pending Remiance)
• Unpaid Bills Receivable (if the bill has the status Unpaid or Protested)
Create intercompany accounting entries whenever a transaction, receipt, or credit memo is applied to a bill receivable
with a dierent company segment.
433
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Use the Mark as Canceled action to cancel a bill. You can cancel a bill that is Pending Acceptance, Pending Remiance,
or Unpaid:
• If the bill is Pending Acceptance, canceling the bill releases the applied transactions and has no accounting
impact.
• If the bill is Pending Remiance or Unpaid, Receivables unassigns the applied transactions and creates reverse
accounting entries.
434
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Overview
The Automatic Bills Receivable Transactions Batch Report lists the contents of a bills receivable batch.
Key Insights
The report lists the bills receivable created in a batch, or the bills receivable that will be created in a batch submied in
Draft.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables Balances
435
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
FAQ Answer
Who uses this report? Financial Specialist responsible for bills receivable.
When do I use this report? When you need to review a list of the bills receivable created in a batch, or the bills receivable
that will be created in a batch if the Create Bills Receivable Batch process is submied in Draft.
Batch Name
Report Version
• Detail: Listing of the bills receivable in a batch and information about the transactions assigned to each bill
receivable.
• Summary: Listing of the bills receivable in a batch.
Report Output
This table describes the report headings in the output of the Automatic Bills Receivable Transactions Batch Report.
436
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Drawee Site The site reported on belonging to the customer drawee account.
Payment Method The bills receivable creation receipt method used to generate bills receivable from transactions.
Grouping Rule The bills receivable creation receipt method rule used to group transactions into bills
receivable.
Maximum The maximum amount, specied in the bills receivable creation receipt method, that a bill
receivable can have.
Minimum The minimum amount, specied in the bills receivable creation receipt method, that a bill
receivable can have.
Lead Days The number of days before the transaction due date, specied in the bills receivable creation
receipt method, that a transaction was eligible to be applied to a bill receivable.
This table describes the column headings in the output of the Automatic Bills Receivable Transactions Batch Report.
Bills Receivable Transaction Type The bills receivable transaction type assigned to bills receivable created from transactions by
the bills receivable creation receipt method.
437
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Document Number The document sequence number assigned to the bill, if applicable.
Transaction Type The transaction type of the transaction applied to the bill.
Applied Amount The amount of the transaction that was applied to the bill.
Transaction Date The creation date of the transaction applied to the bill.
Transaction Due Date The due date of the transaction applied to the bill.
Balance Due: The open balance of the transaction applied to the bill.
Conversion Rate The conversion rate used for the entered currency of the transaction applied to the bill, if not
the ledger currency.
This table describes the row headings in the output of the Automatic Bills Receivable Transactions Batch Report.
Total Count of Invoices The total number of transactions applied to a single bill receivable.
Drawee The name of the customer drawee for the applicable transactions.
Total The total amount of the bill receivable amount in the entered currency.
Batch Total in Ledger Currency The total amount of all bills receivable in the ledger currency for the customer drawee.
Total Count of Bills Receivable The total number of bills receivable created in the batch.
Batch Total The total bills receivable amount in the ledger currency for all customer drawees in the batch.
Related Topics
• Prepare Transactions for Bills Receivable Batches
438
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Overview
The Bills Receivable Remiance Batch Management Report provides detailed information about a bills receivable
remiance batch.
Key Insights
Review both remiance batch information and information about each bill receivable in the batch.
FAQ Answer
How do I nd this report? Scheduled Processes - Create Bills Receivable Remiance Batch
Who uses this report? Financial Specialist responsible for bills receivable.
When do I use this report? To review a run of the Create Bills Receivable Remiance Batch process.
What can I do with this report? According to your bills receivable remiance schedule.
439
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
FAQ Answer
Review this report each time you generate a bills receivable remiance batch.
Approve
Indicate whether to approve the remiance batch when it is generated. Approving the remiance batch initiates the
accounting event for the bills receivable remiance.
Currency
The currency for the remiance batch. The program selects bills receivable eligible for remiance with this currency.
Remiance Method
With Recourse
440
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
The bills receivable remiance receipt class and receipt method to use to create the remiance batch.
The remiance bank and account for this remiance batch. The program selects both eligible bills receivable with this
remiance bank account, and eligible bills receivable with no remiance bank account assigned.
Bills receivable with the status Pending Remiance that match the other criteria for this remiance batch are eligible for
selection. If you select Yes, then bills receivable with the status Unpaid are also eligible for selection.
Only create a remiance batch if the total amount of eligible bills receivable equals or exceeds this amount.
Only create a remiance batch if the total amount of eligible bills receivable equals or is less than this amount.
Report Output
The report contains two sections:
• Bills Receivable Remiance Batch: Information about the remiance batch.
• Remied Bills Receivable: Information about each bill receivable in the remiance batch.
Batch Date
The remiance batch date.
Batch Status
• Completed Approval
• Completed Cancellation
• Completed Creation
• Completed Deletion
• Processed
• Started Approval
• Started Cancellation
• Started Creation
• Started Deletion
• Waiting Post Batch
441
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Remiance Method
Standard or Factoring.
Payment Method
The remiance receipt method used to create the remiance batch.
Accounting Date
The remiance accounting date.
Currency
The remiance currency.
Batch Amount
The total remiance amount in the remiance currency.
Drawee Bank
The customer drawee bank.
Maturity Date
The date payment is due on the bill receivable.
Amount
The bill receivable amount.
Row Headings
Totals for Customer [Customer Name]
The total bills receivable remiance amount for each customer.
442
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Use this report according to your bills receivable transaction processing requirements.
Batch Name
Remiance Batch
The bills receivable remiance batch from which to print bills receivable.
Report Output
This table describes important column headings in the Print Bills Receivable Program and Report.
Bills Receivable Applied Amount The amount of the transaction that was applied to bills receivable.
This table describes important row headings in the Print Bills Receivable Program and Report.
443
Oracle Financials Cloud Chapter 6
Using Receivables Credit to Cash Manage Bills Receivable
Total Original Transaction Amount The total of the original amounts of all transactions in the report.
Total Bills Receivable Amount Due The total open transaction amount that was applied to bills receivable.
444
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
Credit Management is part of the Credit-to-Cash solution for capturing orders, billing customers, processing payments
and adjustments, and managing all related accounting. The Credit Management solution includes the following
processes:
• Credit proles and policies
• Credit reviews
• Credit review management
• Credit management tools
Credit Reviews
A credit review begins when a credit-related event takes place.
All credit reviews begin with the creation of a credit case folder. The case folder is the central document that a credit
analyst uses to review and make decisions about a particular customer credit review.
445
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
The credit manager can perform the functions of the credit analyst, as well as oversee the case folders of all his or her
credit analysts, and approve or reject credit decisions.
446
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
Note: In cases where one customer account calls the credit checking service more than once with dierent
requests, and each of these requests results in a credit checking failure, then a separate credit case folder is
created for each credit checking failure, identied by the customer account and the source transaction that
initiated the credit authorization request. If such a credit request is approved, a credit authorization is created
for the customer account using the aributes of the source transaction.
• The active case folder template is selected for the combination of credit classication and review type. If the
customer or customer account credit prole doesn't have a credit classication dened, then the default case
folder template is used.
• The case folder template is used to display in the case folder the required and optional data point values to use
for the credit review.
• If the case folder template contains a scoring model, the case folder displays the data point values needed for
the credit score calculation, and the scoring model aempts to calculate the credit score.
• If the credit score calculation is successful, the score is displayed in the Credit Score eld. The available
hyperlink opens the Scoring Details page for review of the scoring calculation.
If the credit score calculation is not successful, due to missing data point values, you must enter or populate the
necessary values to calculate the score.
• The user who creates a new credit case folder is designated as the credit analyst for the case folder. The case
folder created by credit checking failure or periodic review is assigned the credit analyst for the applicable
customer or customer account, if dened in the credit prole.
The new credit case folder is assigned an initial status and is displayed rst in the Credit Reviews work area.
The party-level hierarchy is set up using the Manage Hierarchies setup task. To use a particular type of hierarchy in
Credit Management, you specify the hierarchy type using the Hierarchy Type for Credit Management prole option.
The default value for this prole option is None, meaning no customer hierarchy is used by Credit Management unless
you assign one. If you want to use a party-level hierarchy, set the Hierarchy Type for Credit Management prole option
value to the correct hierarchy type as dened in the Manage Hierarchies setup task.
If a party-level hierarchy is dened for a customer, then the credit checking process rst derives a credit limit from the
parent party in the hierarchy, and then considers the available credit for each child party in the hierarchy to nd the
actual credit limit.
447
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
For example, consider the following party-level hierarchy for Vision Corporation:
Vision Corporatoin
(Global Ulimate Party)
Credit Limit: 50 Mil
(Effective Credit Limit: 27 Mil)
Account 3
Credit Limit:
Not Specified
The party prole credit limit denes the total credit amount that all children have available. In this example, Vision
Corporation has a credit limit of $50 million. The actual credit limit for a given party is derived by considering both the
dened credit limits and the children that don't have a credit limit dened.
Vision USA has a credit limit of $20 million available to its three accounts. Account 1 has a specied credit limit of $5
million, so Account 2 and Account 3 together can use up to $15 million.
Vision Middle East has a credit limit of $3 million available to its two accounts. Account 7 and Account 8 together can
make use of this $3 million.
Vision Canada and Vision Mexico don't have credit limits dened, so eectively these parties can make use of the
undened $27 million in credit.
If, for example, Vision Canada Account 4 submits an order for $2.5 million and Vision Mexico Account 6 submits an
order for $3.5 million, then after these orders are authorized, the remaining credit available to Vision Canada and Vision
Mexico is $21 million.
448
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
For a scoring model, a scorable data point requires you to enter possible value ranges for the given item of data and to
assign a numeric score to each value range to reect the possible credit risk.
For example, the data point that identies the count of customer past due invoices may have ranges from 0-10 (low
credit risk), 10-50 (moderate credit risk), and 50-100 (high credit risk).
A non-scorable data point provides additional reference information for a credit review, independent of the score
calculation. This additional information can be a factor in making a credit decision.
For example, if a customer has a business location in a high-risk country, this can potentially reduce its credit rating.
Related Topics
• How You Maintain the Summary Tables for Data Points
449
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
Receivables populates the Data Points section with all system-derived data point values. You can't update these values.
A warning icon appears next to each required data point that doesn't have a value populated.
You can save a case folder without completing all of the required data point values, but you can't approve a case folder
until all required values are entered and, if a scoring model is used, the credit score is calculated.
Enter in the Value elds the remaining data that you need for your credit determination. You can either enter a value
directly or import third-party data for the specic customer or customer account.
The values for data points in the categories Aging, Billing and Payments, and Business Information and Credit that
relate to customers and customer accounts are system-derived. You can't enter values for these data points in a case
folder. If a value is missing for one or more of these data points, you must refresh the summary tables that maintain this
data, and then refresh the case folder, to populate the required elds.
You can enter and import missing values, or refresh system-derived values. You must ensure that you enter values
within the ranges dened for each data point in the scoring model.
If necessary, you can change the default scoring model during your credit review by selecting a dierent scoring model
in the Scoring Model eld. Changing the scoring model updates the credit score according to the data points of the new
scoring model.
When you have completed your updates to all data point values, use the Calculate buon to calculate the credit score
and remain on the page. Use the Save buons to calculate the credit score and return to the case folder. If necessary,
continue to update data points until the credit score is calculated.
Related Topics
• How You Import Third-Party Credit Data for Data Points
450
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
The following table lists the recommendation you can make for each type:
Type Recommendation
No change Maintain the current record for the customer or customer account. If the credit review is due to
a credit checking failure, the credit authorization request is denied.
Approve Source Transaction Credit For the Credit Checking Failure request type only. If you enter Yes, a credit authorization is
Request created for the customer account using the aributes passed through the credit checking
service, regardless of whether sucient credit is available.
Decline Source Transaction Credit For the Credit Checking Failure request type only. If you enter Yes, credit authorization is
Request declined for the customer or customer account.
Place customer on credit hold The customer or customer account is placed on credit hold and any credit authorization
request is denied.
Release customer from credit hold The customer or customer account is released from credit hold and can initiate new credit
authorization requests.
Set credit classication Change the credit classication for the customer or customer account.
Set credit limit Increase or decrease the credit limit for the customer or customer account.
Set order amount limit Increase or decrease the order amount limit for the customer or customer account.
Set credit review cycle Change the credit review cycle for the customer or customer account.
Set next review date Enter a specic date for the next credit review for the customer or customer account.
451
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
Type Recommendation
If you are updating the credit limit, you must respect the customer hierarchy, if one exists:
• If you increase the credit limit, ensure that you don't increase a child credit limit to cause the sum of the
children to exceed the parent credit limit.
• If you decrease the credit limit, ensure that you don't reduce the parent credit limit below the sum of the credit
limits of the children.
Note: You don't need to set up approval limits and hierarchies of approvers in advance in order to assign case
folders to other analysts for review and approval.
◦ Select the Approve case folder radio buon to approve the case folder.
◦ Select the Approve and specify the next approver radio buon to indicate your approval and to assign
the case folder to the next approver.
◦ Enter any comments in the Comment eld.
8. Save your work.
452
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
If you select the Approve case folder radio buon, the case folder status is set to Approved and the recommendations
assigned to the case folder initiated. The case folder status is updated to Closed after all recommendations are
successfully implemented.
If you select the Approve and specify the next approver radio buon and designate another approver, the case folder
status is set to Pending Approval and the case folder is assigned to this approver (credit analyst or credit manager).
The next approver can either approve the case folder, reject the case folder, or approve and assign the case folder to
another approver.
A run of the Periodic Credit Review process includes all customers with a Next Review Date value on or before the
current date and the applicable Credit Review Cycle value dened.
Note: The process only includes customer and customer accounts that have both Next Review Date and
Credit Review Cycle dened. If either value is missing, the customer is not included in the process run.
After the process run, the current date is populated in the Last Review Date eld, and the Next Review Date eld is
populated according to the Credit Review Cycle value. For example, after a credit review on January 1, 2017, quarterly
reviews are assigned a next review date of April 1, 2017; semiannual reviews, July 1, 2017; and annual reviews January 1,
2018. You can change the default Next Review Date and Last Review Date values at any time, according to your credit
policy and business requirements.
Process Parameter
Use the Order Output By parameter to order the report data by customer, customer account, or next review date.
The process only provides this parameter, and includes all eligible customers and customer accounts in the review. You
can't run the Periodic Credit Review process for a subset of customers or customer accounts eligible for credit review.
The process creates a new case folder for each applicable customer or customer account and assigns the case folder to
a credit analyst. The process also records the customers that already have active case folders.
The report provides separate sections for customers that had new case folders created and customers that already have
currently active case folders.
453
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
Credit Classication The credit classication for the customer or customer account.
Credit Review Cycle The credit review cycle for the customer or customer account.
Credit Analyst Assigned The name of the credit analyst assigned to the case folder.
If after conversion to the credit currency the sum total is equal to or greater than the dened credit limit, then the
customer has exceeded the credit limit and a credit review is initiated.
• The Transaction eld value is a combination of the type of the source transaction and the source transaction
number.
• The Customer and Customer Account elds display the customer and customer account requesting the credit
authorization.
• The Contact eld displays the customer account contact on the source transaction.
454
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
• The Requested Amount eld value displays in the requested authorization amount currency.
• The Available Credit eld value displays in the customer or customer account credit limit currency.
• The Preauthorization Request eld indicates whether a case folder is created from a preauthorization failure.
If the value in this eld is Yes, then the application that called the credit checking service requested that a case
folder be created if the preauthorization request failed.
Additional data points follow the same rules for weight, range, and score values as all other data points.
A weighted point earned is (point earned x the weight assigned to the data point). So if the point earned for Data Point
A is 5, and the weight given to Data Point A in the scoring model is 50, then the weighted point earned is 250 or 2.5,
expressed as a percentage.
The calculation of a credit score is the sum of the weighted points earned expressed as a percentage.
455
Oracle Financials Cloud Chapter 7
Using Receivables Credit to Cash Manage Credit Management
A Closed case folder generates a public Credit Case Folder Closure business event. This business event contains the
following information:
• Key aributes of the case folder, including case folder number, status, credit analyst, creation date, and last
update date.
• Key aribute values that the application calling the credit checking service passed using the latest credit
checking service call, including customer, customer account, requested authorization amount, and source
transaction information.
• If Approve Source Transaction Credit Request is one of the recommendations, the key aributes of the
new credit authorization record, including credit authorization number, authorization expiration date, and
authorization amount.
• If the case folder was approved, a list of all approved recommendations, including new values in the credit
prole for credit limit and credit classication.
You usually withdraw a case folder when you need to add or update information pertinent to the case folder approval
process. After entering your updates, you can submit the case folder again for approval.
You reject a case folder if you don't agree with the case folder recommendations.
Only a user with the appropriate permissions can reject a case folder, often a credit manager. A rejected case folder is
returned to the credit analyst for further review. After the appropriate review and investigation, the credit analyst can
submit the case folder again for approval.
456
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The model enables you to dene and keep track of all bank accounts in one place and explicitly grant account access to:
This eliminates the redundant duplicate bank account setup in dierent business units when these business units share
the same bank account.
Banks
Creating a bank is the rst step in the bank account creation. You can:
• The option to create from an existing party is implicitly implemented by the matching option.
• The option is available only after the existing party has been found with the same bank.
• If you select the matching option, the page repopulates the information from the matched party.
Branches
Once you have created your bank, the next step is creating a branch or branches associated to the bank. The matching
option is also available when creating branches. To create a new branch without using the matching option, manually
enter the required information. You can also dene other branch- related aributes in the same page.
If you don't use the matching option when an existing party is found, a branch with the same party name is created.
Accounts
The four areas associated with dening an account are:
• General information
• Control of the account
• Security and access to the account
• Business unit assignment
457
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Once the bank and branch are created, proceed to the bank account setup by doing the following:
• Select the bank branch you want to associate to your bank account.
• Assign the owner of the bank account.
Note: To create a bank account for Payables or Receivables, add the Business Unit Access rst for
the business units to use the bank account.
Related Topics
• Considerations When You Create Accounts
• Reconciliation Matching Rules
How You Upload Addresses for Existing Banks and Bank Branches
This example shows how to upload new addresses for existing banks or bank branches by using the Manage File Import
Activities page from Trading Community Model.
The following table summarizes key decisions for this scenario:
What setup data are you uploading? Addresses for existing bank and branches
Is the data an update or new setup Update to existing bank or branch data
data?
Uploading an Address
1. On the Setup and Maintenance work area, navigate to the Manage Banks or the Manage Bank Branches page.
2. Select Query By Example from the View menu to sort and select the banks or bank branches to which you
want to upload the addresses.
3. From the View menu, hover over Columns and select BankPartyNumber for Manage Banks or
BranchPartyNumber for Manage Bank Branches. If the BankPartyNumber or the BranchPartyNumber
column isn't visible, select Manage Columns from the menu and move the BankPartyNumber or the
BankPartyNumber to the Visible Columns list on the Manage Columns dialog box.
4. Click the Export to Excel buon to export the selected bank party number or branch party number to a CSV or
Excel le.
5. Add the bank party number or branch party number to your CSV or Excel le containing all the address
information to be uploaded, such as Address 1, city, state, and country.
458
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
A B C D E
7. On the Setup and Maintenance work area, navigate to the Manage File Import Activities page, and click Create.
8. On the Create Import Activity: Enter Import Options page, complete the following elds, and click Next.
Field Value
Object Account
Data Type
Accept the default value or leave the data type as Comma Separated if that's the separator
used in the CSV le
9. On the Create Import Activity: Map Fields page, complete the following elds, and click Next.
◦ For the BankPartyNumber or the BranchPartyNumber aribute, select OrganizationProle as the
target object, and select PartyNumber as the target aribute.
◦ For every Address aribute, select Address as the target object, and select the corresponding values
(Address1, City, State, Country) as the target aribute.
The following table depicts a sample aribute mapping to upload new addresses:
459
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
10. On the Create Schedule page, click Next to execute the address upload immediately. You can also dene a
specic schedule.
11. On the Create Import Activity: Review and Activate page, verify the import activities options. Click Activate to
upload.
12. Verify that the Scheduled Process status is Completed in the Manage File Import Activities page.
13. On the Setup and Maintenance work area, navigate to the Manage Banks or Manage Bank Branches pages.
Verify that the bank or bank branch addresses are correctly imported.
Related Topics
• Overview of Cash Management Rapid Implementation
• Considerations When You Create Accounts
Note: The import process supports bank les with the following le extensions: *.txt, *.dat, *.csv, *.xml, *.txt,
and *.ack.
The electronic bank statement process consists of the following three phases:
1. Retrieve phase: Retrieves the electronic bank statement le or stream from external sources and stores it
in the database. The external sources can be a le stored on a remote computer or a le stored on the local
computer.
460
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
2. Load phase: Processes the retrieved electronic bank statement and populates the bank statement interface
tables, also known as the staging area.
3. Import phase: Processes the loaded bank statement data from the staging area against functional validations
before populating the data into the bank statements tables. The parsing rules are executed during this phase.
If the process fails with import errors, correct the reported errors. Rerun just the import phase from the Processing
Warnings and Errors table of the Bank Statements and Reconciliation Overview page. However, if there are any errors
during the load phase, purge the error data and resubmit the program.
The following prerequisites for Oracle Fusion Cash Management and Oracle Fusion Payments are required to process
electronic bank statements.
Cash Management
Set up the following entities in Cash Management:
• Bank Account
• Balance Codes: The ISO 20022 balance codes for the opening and closing booked and available
balances are provided and additional codes can be dened using the Balance Code lookup
(CE_INTERNAL_BALANCE_CODES).
• Transaction Codes
• Parsing Rules: Parsing Rules setup is optional but relevant to Bank Statement Reconciliation.
Payments
Set up the following entities in Payments:
• Code Map Group: Uses code map groups for mapping the balance codes and transaction codes that are
reported on the external data le to the ones that are dened internally in the application. Each code map
group is assigned to a format. Two code map groups mapping the BAI and EDIFACT opening and closing
booked balance codes to the internal balance codes are provided. You can create transaction code mapping
(CE_TRX_CODE ) to determine the ow indicator for congurable BAI2 transaction codes .SWIFT940 doesn't
require a balance code mapping because it's position-based but you can create a code map group to map the
transaction codes to the internally-dened transaction codes. The delivered code map groups provide only
basic mappings. You can either modify or create code map groups according to your requirements.
• Format: Cash Management delivers a single format for each of the bank statement formats supported. You can
add additional formats.
You can load and import bank statements in Oracle Fusion Cash Management by any of the following methods:
• Automatic Bank Statement File Import
• Manual Bank Statement File Import through Oracle Web Center
461
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
2. Set up Transmission Conguration: Contains the connectivity details for the nancial institute or bank. This
connectivity information is provided by the bank. The following protocols are supported for connecting and
retrieving a le from bank server:
◦
Secure File Transfer Retrieval Protocol for Static File Names (SFTP_GET): The bank provides the SFTP
server details including SFTP server host/ip, port, credential details. Before using this protocol, you must
log a service request with Oracle Support and provide the SFTP connectivity details. The SFTP_GET
protocol currently supports only basic user name and password based authentication.
◦ Hp(s) GET Request: The bank provides the SSL enabled destination URL for connecting and retrieving
the statement les. This URL can have authentication enabled. The HTTPS_GET protocol supports hps
connection but doesn't support the exchange of any dynamic tokens.
3. Schedule Process Electronic Bank Statement Request: The process performs the following tasks:
Example
The following example describes how to manually load and import an electronic bank statement.
Note: For detailed information on the import and export process, see the hyperlink at the end of
this topic for: Files for Import and Export: Explained.
4. Run the Load and Import Bank Statement process. This process has the following parameters:
◦ Format: Select the bank statement le format. For example, BAI2 format.
◦
Data File: Select the .zip le from the WebCenter document repository. For example, bai2.zip from n$/
cashManagement$/import$ account.
◦ Intraday: Select this parameter if you're importing an intraday statement. Intraday statement type can
either be Cumulative or Incremental.
◦ Submit Autoreconciliation: Use this parameter to submit the Autoreconciliation process immediately
after the Load and Import Bank Statement process completes successfully. This option isn't available if
Intraday is selected.
5. Check for any processing errors from the Bank Statements and Reconciliation Overview page. If the le is
successfully imported, you can review it from the Manage Bank Statements page.
462
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Related Topics
• Overview of Parse Rule Sets
• How You Set Up Formats
• Overview of Files for Import and Export
• How You Map Congurable BAI2 Transaction Codes
Status Explanation
Load Error This status is assigned at the le level. A le fails with load errors for the following two reasons:
An error in fetching the data or an error parsing the data and populating the interface tables.
Such errors typically arise when the data isn't compliant with its standard.
Import Error This status is assigned at both statement level and le level. An import error at statement
level indicates that the data was populated in the interface and loaded successfully but some
functional validations have failed. Example: Duplicate bank statement or a transaction code not
set up. An import error at le level implies that there exists at least one statement in that le
that failed with an import error.
Import Warning This status is assigned at the statement level. Statements with Import Warning imply that
this statement has been imported without any errors, but the program encountered some
functional validation failures which are harmless enough not to stop the import.
463
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Status Explanation
Depending on the status of the le or the statement and the associated issue you can use the Retry icon to restart the
program from where it failed in its last run. The following table explains the dierent retry options available:
Load Error If the le failed during the fetch phase (no The program starts all over again from the
hyperlink on File ID), all the parameters fetch phase.
that were specied during program
submission are available in the dialog.
The parameters can then be updated and
program resubmied again.
Load Error If the le failed during the load phase The program starts from the load phase.
(hyperlink on the File ID). Since the The program aempts to load the
le is already fetched, the parameters already fetched data le using the format
associated with fetching the le aren't specied.
shown; rather only the Format parameter
is shown. In case a wrong value for
Format is specied in the earlier run, it
can be corrected here and the program
resubmied again.
Import Error Import error at le level; no elds are The program starts the import phase for
available on retry dialog. all the statements that led with import
errors under that le.
Import Error Import error at statement level. If a The program starts the import phase
statement fails with Duplicate Bank for that particular statement, using the
Account error then the dialog shows the updated bank account. The program
bank account eld. The correct bank starts the import phase for that particular
account can be selected and program statement.
resubmied again.
Import Error Import error at statement level, for all The program starts the import phase
other import errors, no elds are available for that particular statement, using the
on retry dialog. updated bank account. The program
starts the import phase for that particular
statement.
The following list of common issues and solutions can be used to troubleshoot the Bank Statement Processing
program:
Issue Solution
The program has been run and Check the Bank Statements and Reconciliation work area to verify if any processing errors
successfully completes but doesn't have been reported for your bank statement.
464
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Issue Solution
The program has reported a load If the le was fetched (a hyperlink appears on the File ID eld), you must purge the le to load
error for your le and you realize that the correct one. If the le wasn't fetched (no hyperlink on the File ID eld), you can restart the
the wrong le was processed and program using the Retry option.
want to correct the error.
The program has reported a load No. If you reprocess a data le that has been fetched in the application, then you have to
error for your le and the le was resubmit the program Once a le is fetched, subsequent retry on that le doesn't recall the
fetched. You have gured out the data le from its original source.
problem in the data le and want to
retry the program. Can you process
the edited le?
You have processed a data le You can process the same le without any problem. The program has the capability to detect
where some statements imported duplicate bank statements and it marks those statements as Import Error.
successfully, but some failed. The
failures were because of an error
from the bank. They have sent the
corrected le, but the le contains
the other statements data that was
successfully imported. What is the
impact if the le is processed again?
A transaction or balance code A in Verify if there is a code mapping dened for A that maps it to B.
the data le appears as B after the
import. Why?
A new code map group has been Make sure the new code map group is assigned to the Format in Oracle Fusion Payments.
dened but it doesn't seem to be
working.
The program reports an import error Such balances are imported by the program and they appear in the bank statements user
if a transaction code isn't dened, but interface. However, the balance description is empty because they a'ren't dened in the
doesn't report or give a warning if a application.
balance code is missing for balances.
What happens to the balance codes?
After import, some balance records Verify if the balance codes for the balance records are dened in the balance code lookup.
have an empty balance description.
The program indicates that a If an existing internal code serves the same purpose as the new code, you can create a code
transaction code isn't dened. Should map associating the new code with the existing code. If you use the existing transaction code,
a code map or a transaction code be then you must dene the transaction code.
dened?
Related Topics
• Overview of Parse Rule Sets
465
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
1. Navigate to the File-Based Data Import for Oracle Financials Cloud guide.
2. In the Table of Contents, click File-Based Data Imports.
3. Click Import Bank Statements.
4. In the File Links section, click the link to the Excel template.
Follow these guidelines when preparing your data in the worksheet:
• Enter the required information for each column. Refer to the tool tips on each column header for detailed
instructions.
• You can hide or skip the columns you do not use, but do not delete them.
466
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
467
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
For the Transaction Type eld, the valid values are from the lookup codes dened in lookup type CE_TRX_TYPE. You
can access the lookup types from the Manage Cash Management Lookups page. Enter the transaction type meaning in
the spreadsheet.
BKF Fee
CHK Check
INT Interest
LBX Lockbox
MSC Miscellaneous
For Transaction Code, enter valid codes dened in Manage Bank Statement Transaction Codes task. The following are
examples of transaction codes:
100 Check-Payroll
468
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Generate the CSV le. Click the Generate CSV File buon. A .zip le is created containing 6 CSV les.
This creates a .zip le containing six CSV
les.
Transfer the .zip le. Navigate to Tools > File Import and Transfers the .zip le to the WebCenter
Export. document repository. Select "n$/
cashManagement$/ import$" for the
Account.
Load and import the data. Run the program: Load Interface File for In the Process Details screen, for the
Import. Import Process, select Import Bank
Statements in Spreadsheet. For the
Data File, select the name of the .ZIP
le that was transferred into the (n$/
cashManagement$/ import$) repository
in the UCM. The data from the .ZIP
le will be loaded to the following
interface tables: CE_ STATEMENT_
HEADERS_INT CE_ STATEMENT_
LINES_INT CE_ STMT_ BALANCES_INT
CE_ STMT_ BAL_ AVALBTY_INT CE_
STMT_ LINES_ AVALBTY_INT CE_ STMT_
LINES_ CHARGES_INT After the load
is successfully completed, the Import
process imports the data from the
interface tables into the corresponding
bank statement tables. You are able to
review the imported statements from the
Manage Bank Statements page, the entry
type is spreadsheet, then proceed with
either manual or autoreconciliation.
Review import errors. Review ESS Job Log les, x the errors in If there are errors during import after a
the spreadsheet and restart the process successful load, the entire import fails
again. and no records will be imported into bank
statement tables from the interface tables.
You can review the import errors from
the ESS job log les. You must purge the
current load from the Bank Statement and
Reconciliation dashboard, x the errors in
the spreadsheet, and restart the process
again.
469
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
For example, you are a cash manager reviewing the unreconciled items on a bank statement. The conversion rate the
bank is using is dierent than what you expect. You need to conrm the conversion rate with the accounts payable
manager.
Related Topics
• What does social networking have to do with my job
470
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
For Foreign currency bank accounts, the accounting conversion rate type dened at the bank account setup is used to
default the conversion rate type and conversion rate that's used for accounting.
Note: You can enable the Opt in feature Assign User Exchange Rate for Cash External Transactions to
overwrite the conversion rate when you create the external transaction.
Instructions and CSV Generation Contains instruction information about preparing and loading data, the format of the template,
submiing the Import External Transactions process, and correcting import errors.
CE_ EXTERNAL_ TRANSACTIONS Enter information about the external transaction that you are adding, such as bank account,
amount, date, transaction type, reference, business unit, cash account, and oset account.
• Alternatively, extract data from external application into a temporary spreadsheet that contains the same
columns and structure as this template. Then cut and paste the data from the temporary spreadsheet into the
template.
471
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
If there are errors during import, the errors can be corrected and re-uploaded using the Correct Import Errors
spreadsheet.
1. From the Bank Statement and Reconciliation page, click on Correct Import Errors.
2. This opens the Manage External Transactions spreadsheet.
3. The worksheet will be pre-populated with rows that failed import. Review and correct the errors in the
spreadsheet. Once the errors are corrected, click the Upload and Import buon.
4. Click the Download buon to see if there are any rows returned. If the spreadsheet is empty, then all rows are
successfully imported.
Manage Reconciliation
Automatic Reconciliation
Automatic Reconciliation uses the reconciliation rule set assigned to the bank account to reconcile bank statement
lines and system transactions. Use autoreconciliation to process a large volume of bank statements or to automate the
reconciliation process.
Set up the following before performing automatic bank statement reconciliation:
Banks, Branches, and Accounts Dene banks, branches and accounts to keep track of all bank accounts in one place.
Parse Rule Sets Use to parse inbound addenda and other elds into more granular constituent elds. A parse
rule set is associated with a bank account and used as reference data for the parsing batch job
or scheduled process.
Transaction Codes Expand or modify existing delivered transaction codes or create transaction codes as required.
Transaction codes must match your bank's transaction code.
Transaction Type Mapping Based on the payment method, identify the transaction types for Payables and Receivables
and provide a description.
472
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Bank Statement Reconciliation Use Reconciliation matching rules to determine how to match bank statement lines to system
Matching Rules transactions.
Bank Statement Reconciliation Use tolerance rules to specify date, amount and percentage tolerances that prevent or warn
Tolerance Rules when reconciliation is a breach of a dened tolerance.
Bank Statement Automatic Consists of one or more matching rules and tolerance rules. They must be prioritized
Reconciliation Matching Rule Set or sequenced in the order in which they must be executed. Manage Bank Statement
Reconciliation Rule Sets page
Transaction Creation Rules Use to identify unreconciled or external bank statement lines, and create an account for a
transaction. For example, bank fees and interest.
Dene Subledger Accounting Rules Congure predened accounting rules for external entry transactions.
Note: The parameter Number of Days can be used for selecting the bank statements when you
don't want to enter the From and To Statement End Dates. You can use this parameter when
submiing and scheduling the process.
• Review the unreconciled and reconciled lines. You can either perform manual reconciliation or resubmit the
autoreconciliation process from the Bank Statements and Reconciliation work area.
• Review reconciliation exceptions from the Review Exception page.
• Use the Mark Reviewed feature to prevent the accidental reversal of the reconciliation of a reconciled bank
statement.
Related Topics
• Overview of Tolerance Rules
• Overview of Bank Statement Transaction Creation Rules
• Overview of Reconciliation Rules Sets
• Reconciliation Matching Rules
473
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
For each one to one automatic reconciliation rule, exceptions are looked for in the following order:
1. Ambiguous
2. Date
3. Amount
If an exception type is found for a given bank statement line the program stops looking for other types of exceptions
using the same rule.
The exceptions are presented to you in the context of the bank statement line so the appropriate matching system
transaction can be selected and reconciled.
If an application transaction is an exception to more than one bank statement line it can only be selected to reconcile
with one of the statement lines.
Related Topics
• Overview of Reconciliation Rules Sets
• Overview of Tolerance Rules
• Reconciliation Matching Rules
A check was generated for $100.00, but the bank recorded this payment as $10.00 by mistake. On your bank statement,
you see an entry of a $10.00 payment.
Using the reversal method, the bank reverses the whole error transaction amount so that the error entry and the
reversal entry net out to zero. Then, the bank makes another transaction entry for the correct transaction amount. In
474
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
this example, a reversal entry of a $10.00 receipt is created to oset the original error entry. An additional correction
entry is created as a $100.00 payment. With the reversal method, the error and reversal statement lines as well as the
added correction entry line should all be reconciled to the check transaction.
Using the adjustment method, the bank simply creates an additional transaction entry to make up for the dierence
between the original transaction amount and the error entry. In this example, the bank generates an additional
adjustment entry of a $90.00 payment. The adjusted amount of $90.00 is the dierence between the original error
amount of the $10.00 payment and the correct amount of the $100.00 payment. With the adjustment method, the error
line and adjustment line should be reconciled to the check transaction.
Related Topics
• Overview of Tolerance Rules
The Oracle Cash Management Cash Positioning and Forecasting provide solutions to accurately report cash balances
and position. This enables managers to make cash ows decisions such as investing and borrowing in a timely manner.
It also eectively reports cash forecast information from dierent sources to help manage the cash requirements of the
organization.
You have the exibility to create detailed cash position and forecast reports by using SMART View and nancial reports
to meet reporting requirements. Use the setups in Oracle Functional Setup Manager to specify the requirements.
475
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The following ESS programs are used to create your cash position:
• Cash Position Data Extraction: This program streamlines the extraction of data from all relevant sources. The
Extraction Duration dened in the Specify Cash Positioning and Forecasting Options is used to get historical
data. Submiing the program locks the following setup pages for Cash Positioning and Forecasting::
◦ Specify Cash Positioning and Forecasting Options
◦ Manage Cash Positioning and Forecasting Transaction Grouping
All future system transactions will be stored in the cube.
• Cash Position Data Transfer: This program automatically runs after a successful extraction takes place. It
maintains the Essbase cubes, keeping the data in sync with the transaction data from dierent applications.
The following results in successful extraction:
◦ It maintains the Essbase cubes, keeping the data in sync with the transaction data from dierent
applications.
◦ Converts amounts in all four currencies stored in the cubes:
a. Transaction
b. Ledger
c. Bank Account
d. Reporting
• Cash Position Data Deletion: Use this program to delete the cube prior to making changes to congure the
dimensions or reporting options. The following occurs:
◦ Deletes data from the interface tables.
◦ Deletes the Cash Positioning cubes.
◦ Unlocks the Specify Cash Positioning and Forecasting Options and the Manage Cash Positioning and
Forecasting Transaction Grouping setup pages for Cash Positioning and Forecast:
476
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
• For converting the bank account amount to the reporting amount, the application uses the default conversion
type dened at Currency Rates Manager.
System Transactions
• If the conversion rate isn't dened for a specic transaction date, the application searches going back, up to 1
year to nd the closest conversion rate.
• For converting the transaction amount to the bank account amount the applications uses the Bank Conversion
Rate Type (BANK_EXCHANGE_RATE_TYPE) from the bank account that corresponds to the transaction used.
• For converting the transaction amount to the ledger amount, the application uses the conversion rate dened
for the transaction.
• For converting the transaction amount to the reporting amount, the application uses the default conversion
type dened in the Currency Rates Manager.
Note: If the rate can't be found, the default conversion type dened in the Currency Rates Manager is used.
• Interface tables: Are created to allow the extraction of data from the various sources before transferring them
to the Essbase cube.
• ADF User Interface: The Bank Statement page enable view both intraday and prior-day bank statements.
• ESS Job: The program is created to support loading of data from dierent sources to the Essbase cube. Sources
such as the bank statement and transactions from AP payments, AR receipts, and Payroll payments. The
existing Bank statement loader and import program supports loading and importing prior and intraday bank
statements.
You dene the extraction duration of the transaction data in Essbase. You can also dene reporting options such as:
• the currency for cash balances.
• the balance code to use from the bank statement in cash balances.
477
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
You create transaction grouping (transaction cube dimensions). You can create congurable dimensions to the
transaction cube, in addition to the core dimensions delivered by Cash Management.
• The congurable dimensions are available in Smart View for you to build congurable reports.
• Dimensions available out of the box include Bank, Legal Entity, Currency, Currency Type, Transaction Type,
Source of the Transaction (Bank Statements, AP Invoices, Payroll, AP Payments, AR Invoices, AR Receipts,
External Transactions), Reconciliation Status of the transaction, Time, and Flow indicator for the bank
statement line.
• Design your congurable cube dimensions to meet the dierent reporting requirements for your organization.
Related Topics
• How You Set Up Cash Positioning and Forecasting
Cash Positioning
Watch video
Cash positioning is the planning tool to view your daily cash position. Project your cash needs and evaluate your
company liquidity position. The daily cash positions are based on actual cash ows from data sources such as bank
statements and external transactions.
You can generate a daily cash position based on the following dimensions:
• Currency Type: Reporting, Accounting, Transaction currency, and Ledger currency
• Currency
• Flow Indicator
• Reconciliation Status
• Bank Name and Bank Account Name
• Legal Entity
• Region and Legal Entity
• Application
• Source
• Type: Balance and Transaction
• Time
You can view or manipulate the data from the Essbase cube in Excel using SMART View. The cash positions generated
in SMART View enable you to analyze the data easily and quickly. You can expand on the inow and outow
summarized amounts and drill down to view the details of the source transaction.
Note: To run Cash Position reports successfully, install a Smart View plugin later than the 11.1.2.5.500 version
on the certied browsers Internet Explorer or Firefox.
478
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Balance Types
Banks can report dierent types of balances on the bank statements. You have the option to select which type of
balances you want to use in SMART View as the opening balance in the cash position. Examples of the Balance Types
are:
• Opening ledger balance
• Opening available balance
• Opening 1 day and 2- day oat
• Closing ledger balance
• Closing available balance
• Closing 1 day and 2- day oat
Related Topics
• How You Set Up Cash Positioning and Forecasting
You can download the spreadsheet template to prepare your cash position data. The template contains an instruction
sheet to help guide you through the process. To access the template, complete the following steps:
1. Navigate to the File-Based Data Import for Oracle Financials Cloud guide.
2. In the Table of Contents, click File-Based Data Imports.
3. Click Cash Management Cash Position Data Import.
4. In the File Links section, click the link to the Excel template.
Follow these guidelines when preparing your data in the worksheet
• Enter the required information for each column. Refer to the tool tips on each column header for detailed
instructions
• Do not change the order of the columns in the template.
• You can hide or skip the columns you do not use, but do not delete the
Instructions and CSV Generation Contains instruction information about preparing and loading data, the format of the template,
submiing the Cash Position Data Transfer process, and correcting import errors.
479
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Bank Statement Headers Enter information about the bank statement headers that you are adding, such as the source
statement header ID, the source system, bank account name, and the legal entity name.
Bank Statement Lines Enter information about the bank statement lines, such as the booking date, the transaction
type, and amounts.
System Transactions Enter information about the system transactions, such as AP payments, AR receipts, and
external transactions.
Note: If a valid value cannot be provided for dimensional columns such as the bank name, bank account
name, legal entity name, currency, and transaction type, provide the following default values namely:
NO_BANK_VALUE, NO_BANK_ACCOUNT_VALUE, NO_LEGAL_ENTITY_VALUE, NO_CURR_VALUE,
NO_TRANSACTION_TYPE_VALUE respectively.
If there are errors during bank statements import, the errors can be corrected and re-uploaded to the cube using the
Correct Bank Statement Import Errors spreadsheet:
1. From the Cash Balances Dashboard page, go to task pane, and click on Correct Bank Statement Import Errors.
This opens the Cash Position Bank Statements spreadsheet.
2. The worksheet is pre-populated with rows that failed import
3. Review and correct the errors in the spreadsheet.
4. Once the errors are corrected, click the Upload and Import buon.
5. Click the Download buon to see if there are any rows returned. If the spreadsheet is empty, then all rows have
successfully been imported.
If there are errors during system transactions import, the errors can be corrected and re-loaded to the cube using the
Correct Transaction Import Errors spreadsheet:
1. From the Cash Balances Dashboard page, go to the task pane, and click on Correct Transaction Import Errors.
This opens the Cash Position Transactions spreadsheet.
480
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Considerations
Consider the following when determining your investing or borrowing situations:
• Cash Forecasting: Is the estimation of the cash position based on the following sources: Payables (Payables
Invoices, Payables Payments), Receivables (Receivables Invoices, Receivables Receipts), Payroll (Payroll
payments), and External transactions.
• The Cash Forecast reports are now displaying Payables and Receivables invoices that are due and overdue,
including unpaid or partially paid invoices. It ensures the right level of liquidity is represented and you're
including all aspects of your cash outows.
• The overdue invoice amounts are displayed in the current date columns. By drilling down to the transaction,
you can nd the detail information such as invoice date and due date.
• Prior Day Bank Statement: Statement or statements sent by the bank indicating previous day banking activity,
cash transactions such as deposits or withdrawals, and account balances.
Related Topics
• How You Set Up Cash Positioning and Forecasting
481
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Payment Number Yes, the payment reference is generated The unique payment reference number.
by the application.
• Pending Approval
• Approved
• Rejected
• Validated
• Invalid
• Selement in Process
• Failed
• Completed
• Voided
The Payment Status can be either nonactionable or actionable. The following table lists the possible statuses:
482
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Formaed The payment has been formaed but transmission isn't needed.
Formaed and ready for transmission Passed validation and ready to be transmied.
Note: Cash Management calls the Resolve Document Validation Errors in Oracle Fusion Payment page to let
you resolve issues encountered during the payment process request.
Related Topics
• Options for Resolving Payment File Validation Errors
• Options for Resolving Payment File Transmission Failures
483
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Transfer Number Unique bank account transfer reference that's system generated.
Status
Status of the bank account transfer. Valid values are:
• Pending Approval
• Approved
• Rejected
• Validated
• Invalid
• Selement in Process
• Failed
• Completed
• Voided
Payment Status
The status is a combination of the Payment Process Request and payment le. The payment status can be either
nonactionable or actionable. The Action icon is only enabled if the payment status is actionable.
Formaed The payment has been formaed but transmission isn't needed.
484
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Formaed and ready for transmission Passed validation and ready to be transmied.
Cash Management calls the Resolve Document Validation Errors in Oracle Fusion Payment to let you resolve issues
encountered during the payment process request.
Related Topics
• Options for Resolving Payment File Transmission Failures
• Options for Resolving Payment File Validation Errors
• Overview of Approval Management
Why are system transactions available but the bank accounts are not displayed on the
Cash Balances work area or the Cash Position page?
To accurately predict a cash position, the application requires an ocial prior day closing balance. Create or import a
prior day bank statement with a reported closing balance to see the bank accounts in the Cash Balances work area or
the Cash Position page.
How can I change the reporting currency for the Cash Management infolets, Cash
Balances work area, and 5 Day Forecast after creating the cash position cube?
If you haven't yet submied the Cash Position Data Extraction process, you can change the reporting currency in the
Specify Cash Positioning and Forecasting Options page.
485
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
To change the reporting currency after creating the cash position cube:
1. Submit the Cash Position Data Deletion process.
2. Change the reporting currency on the Specify Cash Positioning and Forecasting Options page. This eld is
editable after you delete the data in the cash position cube.
3. Click Save.
4. Submit the Cash Position Data Extraction process to extract data to the cube. The Cash Position Data Transfer
process runs automatically when you submit the process.
Why does the Cash Position Data Extraction program show error messages for
missing conversion rates in the log le?
The cash position cube stores cash position amounts in four currencies:
• Transaction
• Ledger
• Bank account
• Reporting
If the currencies are dierent, the Cash Position Data Extraction program tries to convert transactions into a compatible
currency. If one of the currency rates is missing, the conversion fails and the transaction isn't transferred to the cube
resulting in an error message. To avoid conversion failures, add the missing currency conversion rates and rerun the
extraction program to transfer the transactions.
Any gain or loss calculation due to dierent currencies is handled by Subledger Accounting.
Related Topics
• How You Submit Accounting Process
• Intercompany Transactions Types
External transactions created for bank account transfers have journal entries created by the Create Accounting process.
Any gain or loss calculation due to dierent currencies is handled by Oracle Fusion Subledger Accounting.
Related Topics
• How You Submit Accounting Process
486
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
You can schedule and run reports from the Scheduled Processes work area in the Tools section of the Navigator.
Bank Statement Report Displays the bank statements that are • *Bank Account
used to analyze balances and transaction • *From Statement End Date
details. • *To Statement End Date
Cash in Transit Report Lists all transactions for a specic bank • *Bank Account
account, that have been remied to the • Transaction Source
bank but haven't been cleared. The report • As-of Date
excludes all voided transactions and all
reversed transactions with a reversal date
on or prior to the As of Date.
487
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Cash to General Ledger Reconciliation Displays bank statement transactions • *Bank Account
Report and general ledger accounting entries • *Accounting Period
that haven't been reconciled and can
cause discrepancies. The report is used to
reconcile bank balances to general ledger
cash balances.
To run predened reports, navigate to the Scheduled Processes work area and follow these steps:
Related Topics
• Reports and Analytics Work Area and Panel Tab
• How Data Is Structured for Analytics
• How You Create and Edit Reports
• Set Up the Reports and Analytics Panel Tab
• Overview of Analytics and Reports
488
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Overview
The Cash Management Bank Statement Report displays bank account balances and transaction information for specic
bank statements. The following gure is an example of the report:
Key Insights
The Cash Management Bank Statement Report is used for reviewing activity of a specic bank account.
Report Parameters
The following table describes required process parameters:
Name Description
Bank Account The specic bank account used to receive payments and disburse funds.
From Statement End Date Starting date range of the activities for the account.
To Statement End Date Ending date range of the activities for the account.
489
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
FAQ Answers
How do I nd this report? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.
When do I use this report? Use this report to review the bank statement of a specic bank account over a selected period.
What can I do with this report? You can use this report to review bank statements and their reconciliation status.
Overview
The Cash in Transit Report lists, for a specic bank account, all transactions that have been remied to the bank but
haven't been cleared. The Cash in Transit report excludes the following:
490
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Key Insights
The Cash in Transit Report lists the transactions that are created but haven't been cleared as of a specic date.
Report Parameters
The following table describes required process parameters:
Name Description
Bank Account The specic bank account used to receive payments and disburse funds.
491
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
FAQ Answers
How do I nd this report? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.
When do I use this report? Use this report to review the transactions of a specic bank account that have been remied
but haven't been cleared.
What can I do with this report? Identify transactions that haven't been cleared as of a specic date.
492
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Overview
The Cash to General Ledger Reconciliation Report compares the GL cash account balance against the bank account
balance. It displays the unreconciled GL cash account journal entries and unreconciled bank statement lines that help
identify the discrepancies between the balances. This is done based on the specied range of periods.
Key Insights
The Cash to General Ledger Reconciliation Report lists the subledger transactions that are accounted in GL but they are
not reconciled in Cash Management.
Consider assigning a unique GL cash account for each bank account and using it to record all cash transactions to
facilitate this book to bank reconciliation.
Report Parameters
The following table describes required process parameters:
493
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Name Description
Bank Account The specic bank account used to receive payments and disburse funds.
From Accounting Period The rst scal period a company uses to report nancial results, such as a calendar month or
scal period. A portion of time in which the accounting calendar may be divided. Accounting
periods make up an accounting calendar.
To Accounting Period The ending scal period a company uses to report nancial results, such as a calendar month
or scal period. A portion of time in which the accounting calendar may be divided. Accounting
periods make up an accounting calendar.
FAQ Answers
How do I nd these reports? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.
• Review and identify the discrepancies in the bank account balances in Cash
Management and the GL cash account balance.
What can I do with this report? Reconcile bank balances to the general ledger cash account balances.
Subject Areas
To create an analysis, you begin by selecting a subject area from which you select columns of information to include in
the analysis. For example, to create an analysis of bank statement balance information, you begin by selecting a Cash
Management - Bank Statement Balances Real Time subject area. Subject areas are based around a business object or
fact. In this example, the subject area is based on the column in the bank statement balance tables.
494
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Folders
Each subject area has one fact folder and a number of dimension folders. Fact folders contain measurable aributes,
which are numeric values like balance code and credit, debit indicator. Fact folders are usually at the end of the list of
folders, and are named after the subject area. Dimension folders contain aribute and hierarchical columns like entry
type and legal sequence number.
Some folders appear in more than one subject area, such as Time. These are referred to as common folders or common
dimensions.
Each folder within a subject area may have a dierent level of granularity. For example, Bank Statement Balance Detail
has various aributes, and Bank Statement Detail has subfolders and aributes in the subfolders.
Aributes
Each dimension folder contains aributes or columns. For example, the folder Bank Statement Balance Detail contains
the following aributes:
• Balance Code
• Balance Code Description
• Credit Debit Indicator
• Float Days
• Funds Date
Related Topics
• How Data Is Structured for Analytics
• Albania
• Algeria
• Andorra
• Argentina
495
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
• Australia
• Austria
• Azerbaijan
• Bahrain
• Belarus
• Belgium
• Bosnia and Herzegovina
• Brazil
• British Virgin Islands
• Bulgaria
• Canada
• Columbia
• Costa Rica
• Croatia
• Cyprus
• Czech Republic
• Denmark
• Dominican Republic
• Egypt
• El Salvador
• Estonia
• Faroe Islands
• Finland
• France
• French Guiana
• Georgia
• Germany
• Gibraltar
• Greece
• Greenland
• Guadeloupe
• Guatemala
When entering bank accounts, dierent countries can have certain rules governing the format and content of the
following related elds:
1. Bank Code
2. Branch Number
3. Account Number
496
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
4. Check Digit
5. IBAN
Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertaining
to the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the site
or user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, these
validations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement of
bank account number aren't aected by this prole.
Albania
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Algeria
Validation Rules
497
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Andorra
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Argentina
Validation Rules
498
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be a maximum of 22 characters.
• Spaces and hyphens are allowed.
• Optional
Check Digit
• Optional
IBAN
Australia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, the length should be either 2 or 3 numeric characters.
• Mandatory
Branch Number
• The combined length of the Branch Number and Bank Code should be 6 numeric
characters. Hence, the valid length values (3,4,6) depend upon the Bank Code (3,2,0).
• This eld is labeled as Bank State Branch.
• Mandatory
Account Number
• Length should be between 5 to 10 characters.
• If the account currency is Australian Dollar, account number should be numeric. For
foreign currencies, alphanumeric values are allowed
• Optional
Check Digit
499
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Austria
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Length should be of 5 numeric characters.
• Optional
Branch Number
• Length should be of 5 numeric characters.
• Mandatory
Account Number
• Length should be between 4 to 11 numeric characters.
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 20 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Azerbaijan
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
500
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Length can't be more than 28 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Bahrain
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Belarus
Validation Rules
501
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Belgium
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be of 12 numeric characters.
• It should be in the format 999-9999999-99.
• A check algorithm is applied on the Account Number.
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 16 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
502
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 20 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
503
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Brazil
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be a maximum of 3 numeric characters.
• If the length is less than 3, then it's converted to a 3 digit number by prexing it with as
many leading zeroes as is necessary.
• Mandatory
Branch Number
• Length should be a maximum of 5 numeric characters.
• Mandatory
Account Number
• Optional
Check Digit
• Optional.
Company Code
• This is entered in the Account Creation form.
• If entered, length should be a maximum of 15 numeric characters
504
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Bulgaria
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 22 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
505
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Canada
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• This eld is labeled as Routing Transit Number.
• Mandatory
Account Number
• Optional
Check Digit
Columbia
For Colombia, there are no validations for Bank Code, Branch Number, Account Number, or Check Digit elds as
illustrated in the following table:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Optional
Tax Payer ID
• Length should be a maximum of 15 numeric characters 14 digits for Tax Payer ID plus
the last digit for check digit.
• it's unique within the country.
• Cross Validations of Tax Payer ID in Customers, Suppliers, and Companies. If the Tax
Payer ID is used by a Customer, Supplier, or a Company, then the Customer name,
Supplier name, or the Company name should match with the Bank name.
506
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
The rst 15 digits are multiplied by the associated factor, as illustrated in the following table.
Digit Factor
1st 71
2nd 67
3rd 59
4th 53
5th 47
6th 43
7th 41
8th 37
9th 29
10th 23
11th 19
12th 17
13th 13
507
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
14th 7
15th 3
Costa Rica
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Croatia
Validation Rules
508
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 21 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Cyprus
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 28 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
509
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Czech Republic
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 24 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Denmark
Validation Rules
510
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 18 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Dominican Republic
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
511
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Egypt
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
El Salvador
.
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
512
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Estonia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 20 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Faroe Islands
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
513
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Finland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• If entered, it should be 6 numeric characters.
• Mandatory
Account Number
• Length should be between 8 to 14 numeric characters.
• A check algorithm is applied on the Account Number.
• Optional
Check Digit
• If entered, it should be 1 numeric digit.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 18 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
1 1
2 1
3 1
4 2
5 2
514
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
6 1
7 2
8 1
9 1
Method 1
Method 2
A computed sum is then calculated based on the value of the check. Dierent calculations are performed depending on
the rst two digits of the formed check value.
Digit Factor
8th 1
9th 3
515
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
10th 7
11th 1
12th 3
13th 7
Example using check number 88345600000089: Multiply the given digits with the given factor.
8th Digit 0 1 0
9th Digit 0 3 0
10th Digit 0 7 0
11th Digit 0 7 0
12th Digit 0 3 0
13th Digit 8 7 56
N/A N/A 56
Total
• The 14th digit of the check should equal the value of 10 minus the last digit of the computed sum. For the check
value is '88345600000089', the last digit of the computed sum is 6. So 10 - 6 = 4. So, the 14th digit of the check
should equal 4. The test fails here as the 14th digit's 9.
• Both the 14th digit of the check and the last digit of the computed sum are 0. Using the same example, the test
fails here as both values aren't 0.
If the rst two digits of the check aren't '88', then the computed sum is calculated for each of the rst 13 digits by adding
the even numbered digits to the following calculated sum for each odd numbered digit :
516
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
1st 1 2 0.2 0 2 2
3rd 3 6 0.6 0 6 6
5th 5 10 1 1 0 1
7th 0 16 1.6 1 6 0
9th 0 0 0 0 0 0
11th 0 0 0 0 0 0
13th 8 16 1.6 1 6 7
The computed sum is then converted using the following process, before being used to see if the Account Number is
valid:
517
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
1. 28 + 9 = 37
2. 37/10 = 3.7. Integer result therefore = 3
3. 3 * 10 = 30
4. 30 - 28 = 2
This number is then compared to the 14th digit of the Account Number. If it matches, then the test is passed, else it's
failed.
In our example, the test fails as the 14th digit of the account number is 9. If the 14th digit had been 2, then the test would
have been passed.
France
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be a maximum of 5 numeric characters.
• If the length is less than 5, then it's converted to a 5 digit number by prexing it with as
many leading zeroes as is necessary.
• Mandatory
Branch Number
• Length should be a maximum of 5 numeric characters.
• If the length is less than 5, then it's converted to a 5 digit number by prexing it with as
many leading zeroes as is necessary.
• Mandatory
Account Number
• Length should be a maximum of 11 numeric characters
• Special characters and spaces aren't allowed
• Optional
Check Digit
• If entered, length should be a maximum of 2 numeric characters.
• A check algorithm is applied on the check digit.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 27 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
518
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
A check digit's calculated (CD1) from the Account Number, Bank Code, and Branch Number in the following manner.
This is then used as the basis for the check digit validity test.
CDI
For the check algorithm, the digits of the Account Number entered as characters A to Z. are converted to numeric
values, the French government provides the following conversion table:
Value Conversion
A, J 1
B, K, S 2
C, L, T 3
D, M, U 4
E, N, V 5
F, O, W 6
G, P, X 7
H, Q, Y 8
I, R, Z 9
The leer A is converted by applying the table to 1, so the account number becomes 11234567890.
A value for CD1 is formed by joining together the bank elds in the following way:
• The Bank Code is concatenated with Branch Number concatenated to the converted Account Number. To
illustrate with the Bank Code as 12345, the Branch Number as 67890 and the converted Account Number as
11234567890. Then CD1 is created as 123456789011234567890.
• To this concatenated value, 00 is added as a sux and the resulting value is divided by 97. The remainder
obtained as result of this division is then subtracted from 97. The result of this subtraction is the calculated
check digit.
• In our example, suxing 00 gives 12345678901123456789000. Dividing by 97 and deriving the remainder. Mod
(12345678901123456789000, 97) = 86 Subtract from 97. 97 - 86 = 11
• If the user entered Check Digit's equal to this calculated value, then the validation is successful.
In the given example, as the user entered check digit'sn't 11, the check isn't valid.
519
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
French Guiana
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 34 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Georgia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
520
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Germany
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be 8 numeric characters.
• Optional
Branch Number
• If entered, then the length should be 8 numeric characters.
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
Account Number
• Length should be a maximum of 10 numeric characters.
• Optional
Check Digit
• If a value is entered for the check digit, then it must be a single digit and must match the
last digit of the Account Number.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 22 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Gibraltar
Validation Rules
521
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 23 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Greece
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be of 3 numeric characters.
• Optional
Branch Number
• If entered, then the length should be of 4 numeric characters.
• Mandatory
Account Number
• Length should be between 8 to 16 alphanumeric characters.
• Optional
Check Digit
• If a value is entered, then it must be one numeric character.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 27 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
522
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Greenland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Guadeloupe
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
523
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 34 characters. Leading and trailing spaces are ignored. There should
be no spaces in the middle. .
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Guatemala
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Hungary
• Iceland
• India
• Ireland
• Israel
524
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
• Iran
• Iraq
• Italy
• Ivory Coast
• Japan
• Jordan
• Kazakhstan
• Kosovo
• Kuwait
• Latvia
• Lebanon
• Liechtenstein
• Lithuania
• Luxembourg
• Malta
• Martinique
• Mauritania
• Mauritius
• Mayoe
• Mexico
• Moldova
• Monaco
• Montenegro
• Morocco
• Netherlands
• New Zealand
• Norway
When entering bank accounts, dierent countries can have certain rules governing the format and content of the
following related elds:
1. Bank Code
2. Branch Number
3. Account Number
4. Check Digit
5. IBAN
Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertaining
to the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the site
or user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, these
525
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
validations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement of
bank account number aren't aected by this prole.
Hungary
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 28 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Iceland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be of 4 numeric characters.
• If the length is less than 4, then it is converted to a 4 digit number by prexing it with as
many leading zeroes as is necessary.
• Optional
Branch Number
• If entered, then the length should be of 4 numeric characters.
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
Account Number
• Length should be a maximum of 18 numeric characters.
526
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• If the length is less than 18, then it is converted to an 18 digit number by prexing it with
as many leading zeroes as is necessary.
• A check algorithm is applied on the Account Number.
• Optional
Check Digit
• If a value is entered for the check digit, then it must be a single digit and must match the
seventeenth digit of the Account Number.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 26 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
1. Check algorithm is performed against the Account Number (from digit 9 to 16). Each of these digits is multiplied
with the factors as given in the following table:
Digit Factor
9th 3
10th 2
11th 7
12th 6
13th 5
14th 4
15th 3
16th 2
These products are added and the sum is divided by 11. The remainder obtained as a result of this division is subtracted
from 11 to obtain the calculated check digit. If remainder is 0, then calculated check digit is taken as 0.
527
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
This calculated check digit should match the entered check digit (seventeenth digit of the Account Number), else the
Account Number isn't valid.
India
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• This eld is labeled as the IFSC Code
• Mandatory
Account Number
• Optional
Check Digit
Ireland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be of 6 numeric characters.
• Optional
Branch Number
• If entered, then the length should be of 6 numeric characters.
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
Account Number
• Length should be 8 numeric characters.
• Optional
Check Digit
• Mandatory
IBAN
528
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 22 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Israel
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• If entered, the length should be a maximum 2 numeric characters
• Mandatory
Branch Number
• Length should be 3 numeric characters.
• Mandatory
Account Number
• Length should be a maximum of 13 numeric characters.
• Spaces aren't allowed.
• Optional
Check Digit
Iran
Validation Rules
529
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Iraq
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Italy
Validation Rules
530
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be a maximum of 5 numeric characters.
• Mandatory
Branch Number
• Length should be a maximum of 5 numeric characters.
• Mandatory
Account Number
• Length should be a maximum of 12 alphanumeric characters.
• If the length is less than 12, then it is converted to a 12 digit number by prexing it with
as many leading zeroes as is necessary.
• Optional
Check Digit
• If entered, length should be a single alphabetic character and a check algorithm is
applied on the Check Digit.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 27 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
The check digit is used to validate against the Bank Code, Branch Number, and Account Number. These are
concatenated to obtain a 22 character string.
Each character is assigned a value depending upon whether the character is in an odd position or an even position in
the string as given in the following table:
A/0 = 0 A/0 = 1
B/1 = 1 B/1 = 0
C/2 = 2 C/2 = 5
D/3 = 3 D/3 = 7
E/4 = 4 E/4 = 9
531
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
F/5 = 5 F/5 = 13
G/6 = 6 G/6 = 15
H/7 = 7 H/7 = 17
I/8 = 8 I/8 = 19
J/9 = 9 J/9 = 21
K = 10 K=2
L = 11 L=4
M = 12 M = 18
N = 13 N = 20
O = 14 O = 11
P = 15 P=3
Q = 16 Q=6
R = 17 R=8
S = 18 S = 12
T = 19 T = 14
U = 20 U = 16
V = 21 V = 10
W = 22 W = 22
X = 23 X = 25
532
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Y = 24 Y = 24
Z = 25 Z = 23
The rst character is an odd position. The values assigned are added up and the sum is divided 26.
The remainder obtained as a result of this division is converted into an alphabet as given in the following table:
Transformation Algorithm
0=A 9=J 18 = S
1=B 10 = K 19 = T
2=C 11 = L 20 = U
3=D 12 = M 21 = V
4=E 13 = N 22 = W
5=F 14 = O 23 = X
6=G 15 = P 24 = Y
7=H 16 = Q 25 = Z
8=I 17 = R N/A
This value should be the same as the user entered check digit or else the Check Digit validation fails.
Ivory Coast
Validation Rules
533
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Japan
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be 4 numeric characters
• Optional
Alternate Bank Name
• Mandatory
Branch Number
• Length should be 3 numeric characters.
• Optional
Alternate Branch Name
• Mandatory
Account Number
• Optional
Check Digit
534
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Jordan
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Kazakhstan
Validation Rules
535
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Kosovo
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Kuwait
Validation Rules
536
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be a maximum of 22 characters.
• Spaces and hyphens are allowed.
• Optional
Check Digit
Latvia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 21 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
537
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Lebanon
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Liechtenstein
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 21 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
538
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Lithuania
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 20 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Luxembourg
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be 3 numeric characters.
• Optional
Branch Number
• If entered, then the length should be 3 numeric characters.
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
Account Number
539
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Optional
Check Digit
• If entered, then the length should be 2 numeric characters
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 20 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Malta
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 31 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Martinique
Validation Rules
540
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 34 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Mauritania
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
541
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Mauritius
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 30 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Mayoe
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
542
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Length should be 34 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Mexico
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be between 10 to 11 numeric characters.
• Spaces and hyphens are allowed.
• Optional
Check Digit
• Optional
IBAN
◦ Should be numeric
Moldova
Validation Rules
543
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Monaco
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 27 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
544
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Montenegro
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 22 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Morocco
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
545
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Netherlands
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Two types of account numbers are validated:
• If the bank account number is numeric and consists of one of the following then bank
account will be considered as Post or Giro Account.
◦ prexed with P or G
There is no check digit validation for Post or Giro accounts.
• For other account numbers, the length should be between 9 and 10 numeric characters.
A check algorithm is applied on the Account Number.
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 18 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Digit Factor
1st 10
546
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
2nd 9
3rd 8
4th 7
5th 6
6th 5
7th 4
8th 3
9th 2
10th 1
If the result so obtained is perfectly divisible by 11 (that's, no remainder on division by 11), then the test is successful,
otherwise the account number entered isn't valid.
New Zealand
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be 2 numeric characters.
• Mandatory
Branch Number
• Length should be 4 numeric characters.
• This eld is labeled Bank State Branch.
• Mandatory
Account Number
• Length should be a maximum of 8 numeric characters.
547
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Optional
Check Digit
Norway
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be of 11 numeric characters.
• A check algorithm is applied on the Account Number, if the 5th and 6th digits of the
account number aren't 00.
For example, for Account Number, 1234001234, the check algorithm will not be applied but for
Account Number 02056439653, the check algorithm will be applied as outlined in the Check
Algorithm for Account Number, following this table.
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 15 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
548
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
1. The check digit is set as the last (that's, the 11th digit) of the Account Number. For example, if the account number is
02056439653, then the check digit is set to 3.
Digit Factor
1st 5
2nd 4
3rd 3
4th 2
5th 7
6th 6
7th 5
8th 4
9th 3
10th 2
The rst ten digits of the account number are multiplied by the associated factor. The computed sum is then calculated
by summing the totals.
Multiply each digit with the given factor. The following table illustrates the factors that determine validation:
1st 0 5 0
2nd 2 4 8
3rd 0 3 0
549
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
4th 5 2 10
5th 6 7 42
6th 4 6 24
7th 3 5 15
8th 9 4 36
9th 6 3 18
10th 5 2 10
4. The computed sum is then added to the check digit. In the example, 163 + 3 = 166.
7. If the remainder is '0', then the validation is successful, else the check fails.
8. In the given example, the check fails the Account Number as the remainder is 1. If the 11th digit of the Account
Number was 2 (that's, the check digit would be 2), then the remainder would be 165 - (11 * 15) = 0 and the check on the
Account Number would be successful.
• Pakistan
• Palestine
• Poland
• Portugal
550
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
• Qatar
• Reunion
• Romania
• Saint Barthelemy
• Saint Lucia
• San Marino
• Saint Martin
• Saint Pierre and Miquelon
• Saudi Arabia
• Serbia
• Serbia and Montenegro
• Senegal
• Seychelles
• Singapore
• Slovakia
• Slovenia
• Spain
• Sweden
• Switzerland
• The Former Yugoslav Republic of Macedonia
• Tunisia
• Turkey
• Ukraine
• United Arab Emirates
• United Kingdom
• United States
When entering bank accounts, dierent countries can have certain rules governing the format and content of the
following related elds:
1. Bank Code
2. Branch Number
3. Account Number
4. Check Digit
5. IBAN
Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertaining
to the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the site
or user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, these
551
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
validations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement of
bank account number aren't aected by this prole.
Pakistan
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Palestine
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
552
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Poland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, the length should be of 8 numeric characters.
• Optional
Branch Number
• If entered, the length should be of 8 numeric characters.
• If the Bank Code and Branch Number are entered, then both values must match
• Mandatory
Account Number
• Length should be a maximum of 16 alphanumeric characters.
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 28 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Portugal
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be of 4 numeric characters.
• Mandatory
Branch Number
• Length should be of 4 numeric characters.
• Mandatory
Account Number
• Length should be a maximum of 11 numeric characters.
• Optional
Check Digit
• Length should be of 2 numeric characters.
553
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 25 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Digit Factor
1st 73
2nd 17
3rd 89
4th 38
5th 62
6th 45
7th 53
8th 15
9th 50
10th 5
11th 49
554
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
12th 34
13th 81
14th 76
15th 27
16th 90
17th 9
18th 30
19th 3
The nineteen digits of the created check digit (CD1) are multiplied by the associated factor. The multiple sum is then
calculated by summing the totals.
1st 1 73 73
2nd 2 17 34
3rd 3 89 267
4th 4 38 152
5th 5 62 310
6th 6 45 270
7th 7 53 371
8th 8 15 120
555
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
9th 1 50 50
10th 2 5 10
11th 3 49 147
12th 4 34 136
13th 5 81 405
14th 6 76 456
15th 7 27 189
16th 8 90 720
17th 9 9 81
18th 0 30 0
19th 1 3 3
Qatar
Validation Rules
556
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Reunion
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
557
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Romania
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 24 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Saint Barthelemy
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
558
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Saint Lucia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
San Marino
Validation Rules
559
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length can't be more than 27 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
560
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Saudi Arabia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be a maximum of 4 characters
• Optional
Branch Number
• Mandatory
Account Number
• Length should be a maximum of 25 characters.
• Optional
Check Digit
561
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Senegal
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Serbia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory.
Account Number
• Optional
Check Digit
562
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 34 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Seychelles
Validation Rules
563
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
Singapore
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be 4 numeric characters.
• Mandatory
Branch Number
• Length should be 3 numeric characters.
• Mandatory
Account Number
• Optional
Check Digit
Slovakia
Validation Rules
564
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 24 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Slovenia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length can't be more than 19 characters. Spaces are removed from the left and right.
Spaces in the middle aren't removed.
• The rst 2 characters are leers.
565
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Spain
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Mandatory
Bank Code
• Length should be a maximum of 4 numeric characters.
• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing
it with as many leading zeroes as is necessary.
• Mandatory
Branch Number
• Length should be a maximum of 4 numeric characters.
• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing
it with as many leading zeroes as is necessary.
• Mandatory
Account Number
• Length should be 10 numeric characters.
• Optional
Check Digit
• If entered, length should be a maximum of 2 numeric characters.
• A check algorithm is applied on the Check Digit.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 24 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Two check digits are calculated, CD1 from the Bank Code and Branch Number and CD2 from Account Number in the
following manner; these are then used as the basis for the check digit validity test:
CD1
1. For the Bank Code, the Spanish government provides the following factor table:
Digit Factor
1st 4
566
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
2nd 8
3rd 5
4th 10
The four digits of the Bank Code are multiplied by the associated factor. The computed sum is then calculated by
summing the totals.
Digit Value Factor Result Digit Value Factor Result Digit Value Factor Result Digit Value Factor Result
1st 1 4 4
2nd 2 8 16
3rd 3 5 15
4th 4 10 40
N/A N/A 75
Total
2. For the Branch Number, the Spanish government provides the following factor table:
Digit Factor
1st 9
2nd 7
3rd 3
4th 6
567
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The four digits of the Branch Number are multiplied by the associated factor. The computed sum is then calculated by
summing the totals.
1st 5 9 45
2nd 6 7 42
3rd 7 3 21
4th 8 6 48
3. The computed sums from both the Bank Code and Branch Number calculations are then summed up. According to
the example, it's 75 + 156 = 231.
231 / 11 = 21
6.CD1 is then derived by subtracting the remainder from 11. If dierence is 11, then CD1 is 0 and if dierence is 10, then
CD1 is 1 11 - 0 = 11. So for this example, CD1 = 11 = 0.
CD2
1. For the Account Number, the Spanish government provides the following factor table:
Digit Factor
1st 1
2nd 2
3rd 4
4th 8
568
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Digit Factor
5th 5
6th 10
7th 9
8th 7
9th 3
10th 6
The ten digits of the bank number are multiplied by the associated factor. The computed sum is then calculated by
summing the totals.
1st 1 1 1
2nd 2 2 4
3rd 3 4 12
4th 4 8 32
5th 5 5 25
6th 6 10 60
7th 7 9 63
8th 8 7 56
9th 9 3 27
569
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
10th 0 6 0
280 / 11 = 25
4. CD2 is then derived by subtracting the remainder from 11. 11 - 5 = 6. So for this example CD2 = 6.
The value in the user entered check digit eld is compared to the calculated CD1 and CD2 using the following checks, if
both of the checks are true, then the validation is unsuccessful.
Check Description
1 CD1 is compared to the rst digit of the entered check digit eld.
2 CD2 is compared to the second digit of the entered check digit eld.
Example of the test using the previously calculated CD1 and CD2:
Where CD1 = 0 and CD2 = 6 and suppose the user entered Check Digit Value is '05'. As CD2 does not match, the check
digit's invalid.
Sweden
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be between 4 to 5 numeric characters.
• Optional
Branch Number
• If entered, then the length should be between 4 to 5 numeric characters.
570
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
Account Number
• Length should be a maximum of 16 numeric characters.
• Optional
Check Digit
• Length should be a single numeric character.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 24 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Switzerland
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be between 3 to 5 numeric characters.
• Optional
Branch Number
• If entered, then the length should be between 3 to 9 numeric characters.
• Mandatory
Account Number
• Length should be a maximum of 17 numeric characters.
• Optional
Check Digit
• Optional
Account Type
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 21 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
571
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
• Length should be 19 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Tunisia
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory.
Account Number
• Optional
Check Digit
572
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
Turkey
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory.
Account Number
• Optional
Check Digit
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed, IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 26 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
Ukraine
Validation Rules
573
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, the length should be a maximum of 4 characters.
• Optional
Branch Number
• Mandatory
Account Number
• Length should be a maximum of 21 characters.
• Optional
Check Digit
United Kingdom
Validation Rules
574
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional
Bank Code
• If entered, then the length should be 6 numeric characters.
• Mandatory
Branch Number
• it's unique within the country.
• Length should be a maximum of 6 numeric characters.
• If the length is less than 6, then it's converted to a 6 digit number by prexing it with as
many leading zeroes as is necessary.
• This eld is labeled as Sort Code.
• Mandatory
Account Number
• Length should be between 7 to 8 characters.
• If the length is 7 characters, it's converted to 8 characters, by adding a zero as the lead
or rst character.
• Optional
Check Digit
• Optional
Secondary Account Reference
• If entered, length should be a maximum of 18 characters.
• This eld is labeled as Building Society Roll Number.
• Mandatory
IBAN
• If the IBAN isn't entered, a warning message is displayed, IBAN hasn't been entered.
This bank account is dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN.
• Length should be 22 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
• The rst 2 characters are leers.
• The third and fourth characters are numbers.
United States
Validation Rules
The elds are checked for validity by adopting the following rules:
Field Rule
• Optional.
Bank Code
575
Oracle Financials Cloud Chapter 8
Using Receivables Credit to Cash Manage Cash Management and Banking
Field Rule
• For example, 001 and 000007 are invalid Routing Transit Numbers because on padding
to 9 digits, they become - 000000001, 000000007, and thus having 8 leading zeroes.
• A check algorithm is applied on the Routing Transit Number.
• Mandatory
Account Number
• Optional
Check Digit
Factor 3 7 1 3 7 1 3 7
• The digits of the Routing Transit Number are multiplied by the associated factor. The computed sum is then
calculated by summing the totals.
• Subtract the sum from the next highest multiple of 10. The result is the calculated Check Digit. This should be
the same as the 9th digit of the Branch Number or Routing Transit Number; otherwise the Branch Number or
Routing Transit Number is invalid.
For Example:
Routing 0 7 6 4 0 1 2 5 Total
Number
Multiply 3 7 1 3 7 1 3 7 N/A
by
Sum 0 49 6 12 0 1 6 35
= 109
576
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Prole Change the information related to customer prole such as: assigned collector, business level,
preferred contact method of communication, type of payment terms applied, frequency of
statement cycle and so on.
Contact Add or modify the name, phone number, address and email information of the customer.
What is Impacted
• If you change the collector assigned to the customer, the working of the selected delinquent customer is
impacted.
• If you change the business level of the customer, the way the delinquent customer data is displayed on your
collections dashboard is changed.
• If you change the preferred contact method, the dunning communication method is changed accordingly.
Activity
You can create an activity or a series of activities and add detailed information needed to follow up with a delinquent
customer.
Here's how you create an activity:
1. On the Activity tab of the Collections Dashboard, click the create icon.
2. Enter the required subject, due date and description of your follow-up activity.
3. Select the required customer and assign the activity to self or other collections agent.
4. Click save and close.
577
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
You also have an option to select the category of the activity like, dunning call, follow-up call, to-do, meeting and so on
to dene the type of activity you want to do. You can set the priority of the activity according to requirement and can
also upload any aachment for reference. After the activity is created, it appears in the activity tab.
Note
Notes are an excellent way to save some additional information about the customer. You can even paste email
messages into notes. You can create notes for any account or transaction.
Here's how you create a note:
1. Select the customer account or transaction and click the note icon.
2. Select the required type of note from the drop-down list.
3. In the text area, enter the content for the note. You can also format the text according to your need and if
required, add a link.
4. Click save and close.
After a note is created, you can always go back and edit the note to update any information.
Note: Credit card services are currently not available in Oracle Financials Cloud implementations.
578
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Field Action
Payment Amount The total amount is auto-displayed as the payment amount; however, you can change the
amount to make partial payment.
Credit Card Select the existing credit card and verify the number, name and expiration date of the card.
Security Code Security code is mentioned on the back of your credit card. Verify the with the existing
details.
Purchase Order Line Number If required, enter your purchase order line number.
6. After all the required details are entered, click submit to process the payment using existing credit card.
579
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Field Action
Payment Amount The total amount is auto-displayed as the payment amount; however, you can change the
amount to make partial payment.
Create Credit Card hyper link Click the create credit card hyper link to create the new credit card details.
Card Brand Enter the name of the credit card as mentioned on the card.
Expiration Date Enter the expiry date as mentioned on the credit card.
Name on Card Enter the name of the cardholder as mentioned on the credit card.
Financial Institution Enter the name of the issuing nancial institution of the credit card.
Company Card check box Select this check box if the credit card is a company issued card.
From Date By default, the current date of creation and activation of new credit card details is mentioned
as from date.
580
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Field Action
Create Billing Address hyper link Click to create billing address information for the credit card. Refer section "Create Billing
Address" for details.
Context Value Select this check box if a descriptive exeld has been congured.
6. After all the required details are entered, click save and close.
Note: After the new credit card details are saved, the credit card appears in the list of choices and you can
process the payment same as the using the existing credit card details.
Field Action
Country Select from the list of values if other than the default value.
Address Line 1 Enter the billing address for the credit card.
Postal Code Enter the seven-digit numeric code for the billing address.
581
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Field Action
Payment Amount The total amount is auto-displayed as the payment amount; however, you can change the
amount to make partial payment.
Bank Account More than one bank account can appear in the list. Select the correct account and verify all
the information with the customer.
Field Action
Payment Amount The total amount is auto-displayed as the payment amount; however, you can change the
amount to make partial payment.
582
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Field Action
Create Bank Account hyper link Click the create bank account hyper link.
Allow international payments check Select this check box to accept international payments.
box
From Date The date defaults based on the date of creating the bank account.
Currency Enter the currency used for payments from this bank account.
6. In the Additional Information section, optionally you can enter these detailed information of the bank account:.
◦ Account Name
◦ Alternate Account Name
◦ Conversion Rate Agreement Type
◦ Conversion Rate
◦ Conversion Rate Agreement Number
◦ Check Digits
◦ Secondary Account Reference
◦ Agency Location Code
583
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
◦ Account Type
◦ Description
7. In the Account Owner section, enter the account owner name and date from which the bank account details is
created.
8. Click save and close.
After the bank details are saved you can use this to pay for your customer's transaction same as using the existing bank
account payments.
You can create a dispute based on various sections of the customer's transaction.
Remember that you can only submit only one dispute at a time. For example, if you want to dispute tax and shipping on
the same transaction; the tax will be one dispute and shipping a dierent dispute.
Note: In the details section, click details, activity and lines tabs one by one to review the
details of transaction.
Note: The dispute amount and quantity can’t be greater than the current amount or
quantity. If you don't enter the dispute quantity and dispute amount, by default the entire
invoice quantity and current amount is disputed.
8. You also have an option to upload any aachments and enter customer comments.
9. After all the required details are entered, click submit.
A conrmation message with the dispute number is displayed to conrm the submission.
A designated user then reviews the submied dispute request. If the dispute is approved, the appropriate credit memo
is created automatically.
584
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
585
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
• Speed up the collection process by automatically sending precongured or custom dunning leers to one or
more customers via email, fax or print.
• Exclude specic customers from receiving dunning notices based on their proles.
• Assign follow-up dunning calls and notices to collection agents.
• Record and display dunning correspondence activity. View a history of each dunning event including leers
resent.
Dunning Contact Congure using default names in Dunning Contact when the customer is unidentied.
Dunning Address Add and manage the correspondence address of the customer to send dunning notice. It can
be an Email, fax or physical location.
Dunning Template Choose an appropriate Dunning Template to escalate the need to pay.
Dunning Notice Notify your customers about one or more overdue payments.
Business Intelligence Publisher Use this publisher to create and generate reports and dunning correspondence.
586
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
All the important information is visible in the form of infotiles. Here's how you can use these infotiles:
Here are some of the things you can do to manage delinquent customers using Delinquent Customers infotile:
◦ View the list of all the delinquent customers assigned to you or your group.
◦ Set up the customers data in the order of customer's collections level.
◦ Assign the default customer seings from Preferences page.
◦ View and edit the customer's information by selecting delinquent customer information hyperlinks based
on customer name, work status, and aging bucket.
◦ Navigate to the Transaction tab to create or view disputes, adjustments, promises, and process
payments.
• Manage Promises
Here are some of the things you can do to manage promises using Promises infotile:
◦ View the details of broken and open promises in the form of a table.
◦ Review the individual promises made by the customers with promise status, date and amount.
• Manage Strategies
Here are some of the things you can do to manage strategies using Strategy Tasks infotile:
• Manage Activities
Here are some of the things you can do to manage activities using Activities infotile:
587
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
information. A submied bankruptcy request is sent to the appropriate person for approval. The bankruptcy is either
approved or rejected.
Here are the things that happens to a bankrupted customer transactions:
• The status of the customer is changed to Bankrupt.
• All the Collection activities of the bankrupt customer are suspended.
• The Delinquent transactions of the customer no longer appear on your Collections Dashboard.
Points to consider
It is important to consider these points before creating the request for bankruptcy:
1. Ensure that Request Bankruptcy is enabled in preferences.
2. Bankruptcy is applied at customer, account and site levels.
You can withdraw a bankruptcy after a bankruptcy request has been submied. If bankruptcy isn’t approved, you can't
withdraw the bankruptcy. You need to contact the person approving the request to reject it.
588
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Metrics
Oracle Fusion Advanced Collections embeds technology to combine advanced metrics with dimension-based reporting
functionality. Once you run the Initialize and Load Metrics program, the metrics are created.
As transactions are added and receipts are applied, you must run the Incremental Metrics Load program. This routine
maintenance program updates all the data and dimensions.
Multidimensional analysis is possible with the Manager Dashboard and SMART View, an Excel-based ad hoc reporting
tool. You can instantly view statistics using dierent dimensions on the same data, and drill up, down, and through on
any hierarchy level.
589
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
The Key Performance Indicators can be aggregated across a number of dimensions and hierarchies such as:
• Business Unit
• Customer, Account, and Site
• Collector
• Prole Class
• Country, State, Province, City, or ZIP Code
• Salesperson
• Aging Bucket
Collectors
Work Statuses
There are four dierent work statuses available on your dashboard. Lets understand what each status means:
Open You can keep the work status as Open By default, the current date is displayed as
when the customer is available and you Work Status Date.
need to contact them for collections.
Note: These customers are either
newly delinquent, or a customer
with a work status of "follow-up" or
"ignore" whose time duration has
passed.
Follow-up You can keep the work status as Follow- By default, the current date is displayed as
up when you want to follow up with the the Work Status Date.
customer at a future date for payment.
Remember that the work status
automatically changes to Open, if the
590
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Ignore You can keep the work status as Ignore By default, the current date is displayed as
when you want to ignore the customer Work Status Date.
until a future date.
Remember that the work status
automatically changes to Open, if the
delinquency isn't resolved or if the follow
up date has passed.
Note: The work status date needs
to be equal to or greater than the
current date and can't exceed the
Maximum Number of Days value.
You can reschedule the Maximum
Number of Days value from the
seings preference.
591
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Related Topics
• Scoring Formulas
Manage Collectors
Using Collections Manger Dashboard Collectors tab you can do these tasks to manage your collectors:
• You can reassign all customers from one collector to another
• Reassign few selected customers to another collector, and
• Assign a backup collector to an existing one
Let's say that as a Collections Manager, you have analyzed the performance of Collector A and Collector B. You have
discovered that Collector A has a beer success rate of collecting payments from their delinquent customers than
Collector B. So you might want to do these:
• Reassign all of Collector B customers to Collector A
• Assign Collector B to a limited number of customers
• Assign Collector B to backup Collector A to cover for them when they're out sick or on vacation
You will see that Collector A now has all of the customers originally assigned to Collector B.
You will see that Collector A now has the two customers you reassigned from Collector B.
592
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
4. Select Collector B in the Backup Collector eld and enter the Start Date. Note: You also have an option to select
the end date of backup collector.
5. Select Yes to enable the backup collector.
6. Click the Save buon.
Once this backup collector signs into the application they have the ability to access any customer currently
assigned to the primary collector.
593
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Status Result
Broken The customer has failed to make payment by the Promised date.
State Result
Promise View the Promise details with the payment amount and the promised dates.
594
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
8. Click Submit.
Note: You can congure an automatic conrmation leer sent to you for every submied promise to pay
request.
• Whenever you run Promise Reconciliation program. You can assign the promise to pay request status as
Fullled or Broken based on the promise date.
Manage Strategy
Collections Task
A collections task is an activity performed under a strategy. A strategy consists of sequence of grouped tasks which help
you to complete a collection process. You can view all your tasks and task details in Strategy tab.
Advantages
Here are few advantages of Tasks:
• You can congure tasks that are unique to your business, group tasks into a strategy, and apply the strategy
based on each customer's collection risk score.
• You can assign the tasks directly to yourself or to others based on the group of customers delegated for
collection.
• You can congure these tasks manually or automatically.
595
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Task Status
When you run the Strategy Management program, the status for each task gets updated. Here's what each task status
means:
• To Be Created: Task isn't created yet.
• Open: Work in progress
• Skip: Task was skipped
• Time-out: The task wasn't assigned before wait time
• In Error: Problem occurred while sending out correspondence
• Closed: There's no need to perform this task as customer has already paid
• Canceled: Strategy switched, there is no need to perform the task
• Complete: Task is performed
596
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Collections Metrics
Collections Eectiveness Index Metrics
Using Collections' eectiveness metrics you can measure and view the performance of your collections activities
at various levels. It provides you industry standard formulas to measure and calculate these metrics' for collection
performance. The result of these calculations are displayed in percentage to measure the eectiveness of your
collection eorts over time. The closer is your percentage to 100 the more eective is your collection eort.
You can accurately measure the eectiveness of your collection process, amount collected and the amount yet to be
collected, and evaluate the individuals, subgroups, and overall groups.
• Metrics Common Currency: This is the default currency used for reporting. You can dene this in Collections
Preferences.
• Inception Date: This is the date from which your customer balance is calculated. You can't calculate any
balance before the inception date. You can set the Inception Date from the Collections Preferences. Remember
that when you start calculating metrics for the rst time, any unpaid open transaction before the Inception
Date, becomes the starting balance for the Inception Date.
For example: If a customer has open transactions in calendar year 2012 totaling 100,000 USD and the inception
date is set to January 1, 2013. Then the beginning balance for the customer on January 1, 2013 will be 100,000
USD.
• Activity Date: The activity date drives what bucket of time the document is grouped into your metrics. Each
document has a corresponding activity date, documents include:
◦ invoices
◦ receipt application
◦ credit memos
◦ adjustments
◦ unapplied receipts
The activity date is typically the accounting date of the document. You can calculate the balances and metrics
from the current time going backward to the inception date based on the activity dates of the corresponding
documents.
597
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
(Beginning Balance + Credit Sales minus Ending Balance) / N / (Beginning Balance + Credit Sales minus Current
Receivables) / N * 100.
Current Receivables= the current amount of receivables transactions which isn't in dispute or due from past.
Related Topics
• Guidelines for Seing Up Collections Preferences
Here we have 5 metrics related to Days Sales Outstanding. We will look at few formulas with sample calculations.
Scenario
As a Collections Manager you need to understand the Days Sales Outstanding metrics and use the analytics to make
decisions. Say the date of the calculation is October 1, 2011. This table displays the receivables data used for each of the
calculations.
598
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
DSO
In this example you can see, how to calculate the (aggregate) average time, in days, for which the receivables are
outstanding. This will help you to determine if a change in receivables is due to a change in sales, selling terms, or other
factors.
You can compare the days' sales outstanding with the company's credit terms to understand how eciently your
company manages its receivables.
If DSO = Ending Balance * N / Credit Sales, where N = Number of days in the period.
then as per the data shown in the table, the 3rd Quarter DSO = ($8,000 / $16,000) x 91 = 45.5 days DSO
True DSO
You can calculate DSO using an average balance over the period rather than Ending Balance snapshot.
Number of days from invoice date to reporting date x (invoice amount/net credit sales for the month in which the sale
occurred) = True DSO per invoice
The sum of True DSO for all open invoices = True DSO per total accounts receivable. True DSO = (Beginning Balance +
Ending Balance / 2) * N / Credit Sales. For example:
Sum of True DSO for all open invoices = True DSO per total accounts receivable
For example, the calculation based on the earlier data: ($3,000 / $16,000) x 91 = 17 days Best Possible DSO.
599
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Sales Weighted DSO = ((Current Age Category / Credit Sales of Current Period) + (1 to 30 Day Age Category / Credit
Sales of Prior Period) + (31 to 60 Day Age Category / Credit Sales of 2nd Prior Period) + (61 to 90 Day Age Category /
Credit Sales of 3rd Prior Period) + (91 to 120 Day Age Category / Credit Sales of 4th Prior Period) ) x 30
(($3,000 / $5,000) + ($3000 / $5,000) + ($2,000 / $6,000)) x 30 = (0.6 + 0.5 + 0.4) x 30 = 45 days Sales Weighted DSO.
These terms imply the credit health of your customer. In general, more favorable terms are oered to credit worthy
customers and less favorable to customers at risk.
Formula:
Formula:
Sum (Amount Due Remaining * Days Late) / Sum (Original Amount Due).
600
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Formula:
Promise Metrics
You can measure your customer's promises in nominal and currency terms. Here are the formulated metrics for
Promises:
601
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Scenario
Say you're discussing the outstanding transactions with your customer. Your customer said that they're willing to pay
for 10 of their transactions on an agreed upon date. So, you created 10 promises with total transaction amount of 1,000
USD due on the promised date. Your customer fails to make payment of 700 USD on the promised due date for 5 of the
transactions. Now, here's what the table will show as the metric result for the customer:
Promise Count 10
602
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Things to Remember
Here are some things to remember to create a case folder:
• Transactions need to be in same currency.
• Transactions need to belong to same case.
• Transactions must belong to same Bill-to Customer, however you may have transactions from dierent Sold-to
Customers.
• Transactions need to be from the class of Invoice, Debit Memo, or Chargeback. You can't create a case folder
for the class of credit memos, adjustments or receipts.
• Case Folder Status can only be Open or Closed.
• Promise to Pay: You can only make promise to pay the full amount of transaction. Here's how you can make
promise to pay for all the grouped transaction at a time:
a. Click Promise buon.
b. Enter the Promise Date.
c. Click Submit.
• Create Notes: Notes are associated to the case folder and not to the individual transaction. Here's how you can
create notes for the case folder:
a. In the Notes section, click create.
b. Enter the Promise Date.
603
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
• Create a Promise: Click the Promise buon. Enter one or more transactions numbers to create the promise or
promises. Enter the date of the promise.
• Update a Promise: Click the Promise buon, update the promise date.
• Pay Case: Click the Pay buon. Select the transaction or transactions to be paid. Select the payment method
and amount to be paid. You can make partial payments on the transactions.
Note: At this time Cloud customers can only make EFT (Electronic Fund Transfers) as the method
of payment. Credit card payments aren't available to Cloud customers.
Here are certain restrictions for creating and editing a case folder:
• transaction types added to a case folder.
• adding or removing one or more transactions to a case folder.
604
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
You can schedule a report from your Scheduled Process Work area and Reports and Analytics Work area.
On the Navigator, click on Tools and then click Scheduled Processes to Schedule a report.
• Schedule a report from Reports and Analytics Work Area:
On Navigator, click on Tools and then click on Reports and Analytics work area
or,
Click the Reports and Analytics link on Oracle Business Intelligence Catalog.
• Aging
• Dunning
• Promises
Aging Reports
Aging By Common Currency You can translate all your open • *Currency Conversion Type
transaction into a common currency • *Targeted Currency
based on the seven bucket aging method. • Business Unit
• From Customer Name
• To Customer Name
• As-of Account Date
• *Aging Bucket Method
• Show Open Credits
Collections Aging 4 Bucket Report You can view your customer's open • *Business Unit
transaction information based on the four • From Customer Account
bucket aging method. • To Customer Account
• From Customer Name
• To Customer Name
• *Order By
• *Report Summary
• *Aging Bucket Method
• *Report Format
• *Show Open Credits
• As-of General Ledger Date
• From Balance Due
• To Balance Due
• *Show Receipts At Risk
Collections Aging by Collector 7 Bucket You can view your customer's open • *Business Unit
Report transaction information by collector based • From Customer Account
on the seven bucket aging method. • To Customer Account
• From Customer Name
605
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
• To Customer Name
• *Order By
• *Report Summary
• *Aging Bucket Method
• *Report Format
• Show Open Credits
• As-of Accounting
• Date
• From Balance Due
• To Balance Due
• *Show Receipts At Risk
• From Collector Name
• To Collector Name
Dunning Report
Validate Customer Dunning Setup Report Displays customer dunning setup issues • *Business Unit
and provides solution. • *Business Level
• *Show Errors Only
• From Customer Name
• To Customer Name
• From Customer Account
• To Customer Account
Promises Report
606
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Related Topics
• Overview of Analytics and Reports
• Data Structure for Analytics
• How You Create and Edit Reports
Aging Reports
Using collections aging reports you can list your customer's open transactions information which can help you in
creating collection strategies and tasks.You can view all your customer's open transactions based on the aging buckets
you have dened.
Here are the types of aging report you can create:
Report Parameters
This table shows all the required parameters for creating Collections Aging 4 Bucket Report:
607
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Aging Bucket Method Either Staged or Aged, based on your company setup.
Report Parameters
This table shows all the required parameters for creating Collections Aging by Collector 7 Bucket Report:
Aging Bucket Method Either Staged or Aged, based on your company setup.
608
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Report Parameters
This table shows all the required parameters for creating Aging by Common Currency Report:
Name Description
Targeted Currency The currency you want displayed in the report. The default is USD.
609
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
FAQ Answers
Where can I nd these reports? On the Navigator menu click on the Scheduled Processes work area to schedule and run these
reports.
What can I do with these reports? Use these reports to formulate strategies with task or tasks to collect on outstanding
delinquent customers.
Related Topics
• Aging Methods
• Collections Strategies
• Processing Strategies
610
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Report Parameters
This table shows all the required parameters for creating Validate Customer Dunning Setup Report.
Name Description
611
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
FAQ Answers
Where can I nd this report? On the Navigator menu click on the Scheduled Processes work area to schedule and run these
reports.
When do I use this report? You can use this report when conguring your dunning setups for customers, accounts, or by
collector.
What can I do with this report? Use this report to validate and identify gaps in the dunning setup for customer, accounts, or by
collector.
Related Topics
• Collections Conrmation Notices
Report Parameters
This table shows all the required parameters for creating Collections Promise Reconciliation Report.
Name Description
612
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
Name Description
FAQ Answers
Where can I nd this report? On the Navigator menu click on the Scheduled Processes work area to schedule and run these
reports.
When do I use this report? You can use this report to review and keep track of customer promise to pay commitments.
What can I do with this report? You can track the payment progress of customers who have made promises to pay on their
accounts.
Related Topics
• Collections Conrmation Notices
613
Oracle Financials Cloud Chapter 9
Using Receivables Credit to Cash Manage Advanced Collections
614
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
You can enable your customers to do all these tasks themselves. This self-service approach reduces customer inquiries.
You can use Bill Management to handle both Business-to-Business and Business-to-Customer transactions.
And, once you register existing customers as external users, here are some tasks that they can do in the application:
• Review accounts
• Make online payments
• Print transactions
• Dispute transactions (if authorized)
615
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
Note: You can only register existing contacts of a customer account. Also, you must ensure
that the customer contact is saved with the role type as Contact to avoid duplication of
customer contacts.
Registering Wait for a few minutes. If the customer contact gets successfully registered, the status
changes to Registered. If not, it changes to Error.
Registered That's it! You have completed the registration process. The customer receives emails with
the user-name, password, and link to access Bill Management.
Just in case you want to remove the customer, repeat the previous steps and click Unregister User. The status for that
customer contact changes to Unregistered.
1. Create Customer.
2. Create a new contact to the customer with a valid email address.
3. Register User in HCM Via HCM Service.
4. Provide users with Bill Management privilege using the HCM Provisioning Service.
5. Register a user in Bill Management using the BM User Registration Service.
6. Find all user records for the particular customer (all of its accounts/account's site).
7. Get a specic user record for the particular customer account.
The customer contacts that are already associated with a customer account or account's site can only be registered
to Bill Management. To register a new external customer contact to Bill Management, you must rst create the
external customer contact as a contact for an account/account's site using either Collections or Receivables customer
management ows.
Related Topics
• Manage Bill Management Users
616
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
After you or the customer signs in, the steps for reviewing accounts, printing a transaction, and raising a dispute are the
same for both of you.
Total The total number of open transactions that are pending payment for all currencies.
Invoices
◦ The total number of printed invoices of open transactions.
Tip: If you lter for a customer account and currency, infotiles display the total amount of the open
transactions for that currency.
Note: If you can't see the Dispute infotile, then you probably don't have the required permission to
raise disputes. Contact your Applications Administrator or Security Manager.
617
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
Tip: Don't want to sign in to Bill Management every time you want to review your accounts? Just download
the transactions in an XLS le by clicking Export to Excel.
Print Transactions
You can't view the invoice and credit memo of a transaction unless you print the transaction from the Receivables
application.
You may want a printed copy of your transactions, let's say for maintaining records. To print a transaction again:
1. On the Account Overview page, do one of the following:
Dispute Transactions
If your customer has a problem with the balance or the outstanding amount of a transaction, they can raise a dispute.
You can also dispute the transaction on their behalf.
To raise disputes:
1. On the Account Overview page, select the transaction number to open the transaction.
2. Click Request Credit.
618
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
Note: If you can't see the Request Credit buon, you probably don't have the required
permission to raise disputes. Contact your Applications Administrator or Security Manager.
3. On the Manage Disputes page, select the applicable dispute section and dispute reason.
4. Click Submit.
1. On the Account Overview page, select the transaction. You can pay for multiple transactions simultaneously
provided they're of the same currency and same organization.
2. Click Pay.
3. Review the transaction details.
Note: You can also modify the amount you want to pay for a transaction in the Payment
column.
4. Select your bank account. To add a new bank account, select Add Bank Account from the list.
5. Click Continue. On successful completion, you get a payment conrmation message on the page.
Additionally, you can congure the next payment date and dene the number of future payments using the Manage Bill
Management System Options task from the Setup and Maintenance work area.
Why can't the customer see the Request Credit buon and the
Dispute infotile?
If the customer doesn't have the required permission to raise disputes, they won't be able to see the Request Credit
buon and the Dispute infotile. They can contact their Receivables or Collections Manager to request permission and
raise disputes.
619
Oracle Financials Cloud Chapter 10
Using Receivables Credit to Cash Manage Bill Management
620
Oracle Financials Cloud Glossary
Using Receivables Credit to Cash
Glossary
funds capture payment profile
A key setup entity that holds rules for funds capture processing.
Oracle BI Publisher
An Oracle application that performs the following formatting tasks for Oracle Fusion Payments: 1) formats extracted
data into a message, such as a settlement batch or payment file, that can be understood by the payment system, 2)
supports remittance advice formatting and delivery.
payment system
An external organization that provides financial settlement services. The payment system can be the bank at which the
deploying company has its bank accounts or it can be a third-party processor that connects companies and financial
networks.
routing rule
A rule that determines which payment system account and which funds capture process profile are used to process
funds capture transactions.
settlement
A funds capture transaction that moves money from the account of the cardholder or the bank account owner into the
account of the payee.
settlement batch
A group of transactions, typically settlements and credits, that are sent to the payment system together in a file.
Settlement batches are generally used with a processor-model payment system.
source product
The product that owns a transaction and submits the request for disbursement or funds capture to Oracle Fusion
Payments.
XML
Abbreviation for Extensible Markup Language.
621
Oracle Financials Cloud Glossary
Using Receivables Credit to Cash
622