Using Receivables Credit To Cash

Oracle Financials
Cloud
Using Receivables Credit to Cash
20A
Oracle Financials Cloud
20A
Part Number F24536-02
Copyright © 2011, 2020, Oracle and/or its aliates. 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 permied 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-specic supplemental regulations. As such, use, duplication, disclosure, modication, 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 aliates 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 aliates. 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 aliates 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 aliates 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.
Contents
Preface i
1 Manage Customer Billing 1

Create and Process Transactions ............................................................................................................................................... 1
Manage Recurring Billing .......................................................................................................................................................... 29
Manage AutoInvoice .................................................................................................................................................................. 38
Present Bill .................................................................................................................................................................................. 122
Process Billing Adjustments ................................................................................................................................................... 134
Manage Transaction Information .......................................................................................................................................... 166
2 Process Customer Payments 191

Apply Customer Payments ...................................................................................................................................................... 191
Manage Automatic Receipts ................................................................................................................................................... 213
Reverse Receipts ....................................................................................................................................................................... 223
Manage Lockbox ....................................................................................................................................................................... 229
Process Refunds ....................................................................................................................................................................... 236
Process Bank Deposits ............................................................................................................................................................. 241
3 Manage Funds Capture 255

How Authorizations for Credit Cards Are Processed ........................................................................................................ 255
How Selement Batches Are Processed ............................................................................................................................. 257
Examples of Selement Grouping Rules ............................................................................................................................. 261
How Selement Transaction Files Are Merged into One Selement Batch ................................................................ 263
Oracle Payments Funds Capture Predened Reports ...................................................................................................... 264
ISO 20022 Direct Debit Prenotications .............................................................................................................................. 265
ISO 20022 Payment Status Reports ..................................................................................................................................... 267
Logical Grouping in ISO 20022 SEPA and CGI Direct Debit Messages ......................................................................... 273
Validations for ISO 20022 SEPA and CGI Direct Debit Selement Messages .............................................................. 276
Set Up a Customer Bank Account ........................................................................................................................................ 278
How You Update Bank, Branch, and Bank Account Numbers on External Bank Accounts ...................................... 281
How You Create and Edit a SEPA Debit Authorization ..................................................................................................... 281
Payments Mapping of ISO 20022 Direct Debit Message Structure for SEPA and CGI ............................................... 283
Update of a Selement Batch from Stuck to Success ..................................................................................................... 306
Retrieval of Funds Capture Acknowledgment Files Using a Wildcard .......................................................................... 306
Reports for Manage Funds Capture .................................................................................................................................... 307
FAQs for Manage Funds Capture .......................................................................................................................................... 313
4 Manage Accounts Receivable Balances 317

Access Receivables Information ............................................................................................................................................. 317
Process Late Charges .............................................................................................................................................................. 342
Process Statements .................................................................................................................................................................. 357
Close Receivables Accounting Period .................................................................................................................................. 362
Reports for Customer Account Balances ............................................................................................................................ 390
FAQs for Review Customer Account Balances .................................................................................................................. 399
5 Manage Revenue for Receivables 401

Process Revenue for Receivables .......................................................................................................................................... 401
Process Revenue Adjustments for Receivables ................................................................................................................ 404
6 Manage Bills Receivable 417

Create and Process Bills Receivable ...................................................................................................................................... 417
Remit Bills Receivable .............................................................................................................................................................. 422
Update Bills Receivable ........................................................................................................................................................... 425
Reports for Manage Bills Receivable ................................................................................................................................... 434
7 Manage Credit Management 445

Overview of Credit Management .......................................................................................................................................... 445
Components of a Credit Case Folder .................................................................................................................................. 446
How the Credit Limit is Derived in a Party Hierarchy ...................................................................................................... 447
Overview of Data Points ......................................................................................................................................................... 448
Guidelines for Updating Data Points in a Credit Case Folder ........................................................................................ 450
Guidelines for Entering Recommendations for Customer Credit ................................................................................... 451
Credit Case Folder Approvals ................................................................................................................................................ 452
How You Run Periodic Credit Reviews ................................................................................................................................ 453
FAQs for Manage Credit Management ............................................................................................................................... 454
8 Manage Cash Management and Banking 457

Manage Banks, Bank Branches, and Bank Accounts ....................................................................................................... 457
Manage Bank Statements ...................................................................................................................................................... 460
Manage External Transactions ............................................................................................................................................. 470
Manage Reconciliation ............................................................................................................................................................ 472
Cash Positioning and Forecasting ........................................................................................................................................ 475
Reports for Manage Cash Management and Banking ..................................................................................................... 487
Bank Account Validation ........................................................................................................................................................ 495
9 Manage Advanced Collections 577

Manage Customer Data .......................................................................................................................................................... 577
Process Collections Payments ............................................................................................................................................... 578
Process Collections Disputes ................................................................................................................................................. 584
Manage Customer Correspondence .................................................................................................................................... 585
Manage Collections Work ....................................................................................................................................................... 586
Collection Manager Dashboard ............................................................................................................................................. 589
Manage Promise to Pay .......................................................................................................................................................... 593
Manage Strategy ...................................................................................................................................................................... 595
Collections Metrics ................................................................................................................................................................... 597
Manage Case Folder ................................................................................................................................................................ 602
Reports for Manage Advanced Collections ........................................................................................................................ 604
10 Manage Bill Management 615

Overview of Bill Management ................................................................................................................................................ 615
Register External Users ............................................................................................................................................................ 615
Select Your Customer Account .............................................................................................................................................. 616
Review Customer Accounts .................................................................................................................................................... 617
Print Transactions ..................................................................................................................................................................... 618
Dispute Transactions ................................................................................................................................................................ 618
Make Online Payments ............................................................................................................................................................ 619
FAQs for Bill Management ..................................................................................................................................................... 619
Oracle Financials Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Using Oracle Applications
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.
• Training: Take courses on Oracle Cloud from Oracle University.
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.
> Greater than symbol separates elements in a navigation path.
i
Oracle Financials Cloud Preface
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
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send an e-mail to:
[email protected].
ii
Oracle Financials Cloud Chapter 1
Using Receivables Credit to Cash Manage Customer Billing
1 Manage Customer Billing
Create and Process Transactions

Requirements for Completing a Receivables Transaction
Watch video
Before you can complete a Receivables transaction, you must ensure that you have entered all required information.
The information required to complete a transaction diers 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 specied. 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.
Dierent requirements apply depending on the kind of transaction:

• Standard Invoice
• Invoice with Rules
• Standard Credit Memo
Requirements for Completing a Standard Invoice

These requirements apply to a standard invoice (invoice without rules):
• The invoice must have at least one line.
• The accounting date of the invoice must be in an Open or Future period.
• The invoice sign must agree with the creation sign of the transaction type.
• The sum of the distributions for each line must equal the invoice line amount.
• If freight was entered for the invoice, you must specify a freight account.
• If the Require Salesperson Receivables system option is enabled, you must assign one or more salespersons to
each line.
• If salespersons are assigned to each line, the total revenue sales credit percentage must equal 100 percent.
• All the activity date ranges for the setup values, for example, payment terms, must be valid for the invoice date.
• If the invoice uses an automatic receipt method, you must enter customer bank, branch, and account
information.
Requirements for Completing an Invoice with Rules

These requirements apply to an invoice with rules:
• The invoice must satisfy the requirements for a standard invoice.
• Each line must have a revenue scheduling rule and a rule start date.
1
• Each line must have valid account sets.

• Tax that is calculated or entered must have valid account sets.
Requirements for Completing a Standard Credit Memo

These requirements apply to a standard credit memo:
• 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 predened
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.
If the invoice is a project-related invoice, then no distribution information is displayed.
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 reects the split
and you can either accept this percentage or enter another one.
Related Topics
• Example of Deriving Accounting Flexeld Segments in AutoAccounting
2
Guidelines for Entering Invoice Lines

Use invoice lines to enter the goods or services to bill the customer on an invoice. You can create invoice lines in three
ways: enter an inventory item; enter a memo line; or enter a free text line description.
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
exeld 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 dened for the memo line. You can accept this
price or enter the actual selling price. If the currency of the invoice is dierent from the ledger currency, the formula for
calculating the default unit price is (Standard Price / Currency Conversion Rate).
Tax Inclusive Amounts

The choices in the Amount Includes Tax eld indicate whether the amount for this line includes the tax amounts. The
default value is Use Tax Rate, in which case the display of inclusive amounts depends on the seing of the Inclusive
Tax option on the tax rate code for this line. You can change this seing if the Allow Override option for this tax rate
code is enabled. If you change this seing, the line amount is recalculated.
Updates to Tax Lines

You can change the tax rate code on the invoice if the Allow Override option for this tax rate code is enabled. You
can also manually create new tax lines, either to correct the tax rate or to reect other changes to the invoice, such as
including a tax exemption.
Related Topics
• AutoAccounting Account Types and Segment Values
• What happens if I make the transaction line inclusive of tax
• Considerations for Seing Up Tax Rates
• Example of Additional Tax Determining Factors on a Receivables Transaction Line
3
How Revenue Scheduling Rules Are Used

Use revenue scheduling rules to determine revenue recognition schedules for your invoice lines. Revenue scheduling
rules determine the accounting period or periods in which to record revenue distributions. You can assign a dierent
revenue scheduling rule to each invoice line.
Seings That Aect Revenue Scheduling Rules

If the transaction uses revenue scheduling rules, each invoice line must have revenue scheduling rule information,
including the rule name, rule type, revenue period, number of revenue periods, date to start recognizing revenue, and,
where applicable, an end date.
These rules apply to each of the four rule types:

• Daily Revenue Rate, All Periods or Daily Revenue Rate, Partial Periods: Enter a rule start date and a rule end
date.
• Variable Schedule: Enter the number of revenue periods over which to distribute revenue for this invoice line.
• Fixed Schedule: The transaction entry process populates the default duration for this rule.
How the Revenue Schedule Is Calculated

The rule type on the revenue scheduling rule calculates the revenue distributions on the transaction:
• The Daily Revenue Rate, All Periods rule type uses a daily revenue rate to accurately calculate revenue
distributions across all accounting periods, including both full and partial periods. A partial period is an
accounting period with either a start date that is not the rst day of the period or an end date that is not the last
day of the period.
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:
Revenue Amount = Daily Revenue Rate * Days in Period
• 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
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 dene 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 Specic Date for a xed schedule rule, you can set specic accounting dates
on which to recognize revenue. When you specify a date for one period, then all other periods also require a
specic 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 dene 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.
Using Revenue Scheduling Rule Types

You bill a contract for $900 that is to last 90 days. The contract starts on January 14 and ends on April 13. The
accounting period is Monthly. In this contract period, January and April are partial periods, and February and March are
full periods.
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
January 14 January 18 180 180 225 180

February 14 February 28 280 295 225 240

March 14 March 31 310 295 225 240

April 13 April 13 130 130 225 240

Observations on this example:
• 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 denition and divides the
revenue equally across the number of periods specied 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
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.
How Foreign Currency Transactions Are Processed

When you enter a receipt or transaction that is not in the ledger currency, use the available window to enter conversion
rate information. This information is used to convert the foreign currency receipt or transaction amounts to the ledger
currency.
Seings That Aect Foreign Currency Conversion

You can use personalization to display the Inverse Conversion Rate eld. The Inverse Conversion Rate eld
determines the calculation of the ledger currency amount.
Enter conversion rate information:
• 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 specic 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 dened 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 veries 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 dene your non-user
conversion rates in the Daily Rates window. If you entered a conversion type other than User, Receivables
veries that a rate exists for the conversion date that you entered.
How the Ledger Currency Amount Is Calculated

The ledger currency amount is calculated in this way:
• 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
Related Topics
• Guidelines for Creating Conversion Rate Types
• Examples of Using Conversion Rate Types in a Journal
Guidelines for Updating Installments on Transactions

Use the Review Installments window in the Review Transaction page to update the installments on a transaction.
You can perform these updates on installments:
• Update the due date of an installment.
• Update the unpaid portion of an installment.
• Add or delete installments.
Note: You can't update installments on transactions with balance forward billing payment terms.
Set Up for Installment Updates

To set up for installment updates, perform these two tasks:
• Set the AR: Update Due Date prole option to Yes in the Manage Receivables Prole Options page.
Seing this prole option to Yes exposes editable elds in the Due Date and Original Amount columns in the
Review Installments window.
• Enable the Allow change to printed transactions option for the applicable business units in the Transactions
section of the Billing and Revenue tab in the Create or Edit Receivables System Options page.
While not required, best practice is to enable this option if you want to allow updates to installments after
transactions are printed and delivered to customers for review.
Update the Due Date of Installments

Use the applicable Due Date elds to update the due date of one or more installments with an open balance.
When you update an installment 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

Use the applicable Original Amount elds to update any installment with an open balance. If an installment has either a
credit or adjustment against it, you can update the remaining balance after the credit or adjustment is applied.
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.
Add and Delete Installments

You can add or delete installments to reect all the changes that you need to make to the installments on a transaction.
7
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 buon.
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.
Structured Payment References on Transactions and Receipts

The structured payment reference, also known as a creditor reference, is an internationally recognized standard for
matching transactions to remiances.
The structured payment reference is an alphanumeric string, with each character or group of characters carrying
information related to the details of a specic transaction and payments against that transaction: supplier, customer,
transaction details, receipts, bank account information, and control characters.
As required by certain countries, the structured payment reference appears on all communications between suppliers
and customers related to the processing of payments against specic transactions. This includes the supplier invoices,
and all related remiances, bank transfers, and bank statements and reconciliation.
Structured Payment Reference Field

Use the Structured Payment Reference eld to enter your structured payment references for both transactions and
receipts. This is a free text eld with a maximum length of 256 characters.
The Structured Payment Reference eld appears on these pages:

• Create/Edit/Review/View Transaction (Invoice and Debit Memo)
• Create/Edit Standard Receipt
• Edit Receipt: Application Reference Window
Structured Payment References on Transactions

Enter a structured payment reference on your applicable invoices and debit memos in the Miscellaneous tabbed region
of the Create and Edit Transaction pages.
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
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.
Structured Payment References on Receipts

Enter a structured payment reference in the header section of the Create and Edit Receipt pages. You can only use
structured payment references with standard receipts.
If you intend to apply the receipt to a specic transaction, enter the transaction structured payment reference.
In the Edit Receipt page, you can:
• Update the structured payment reference on a receipt.
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.
For automatic receipts:
• 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 selement 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
OAGIS 10.1 XML Transactions

How You Add User-Dened Aributes to OAGIS 10.1 XML Receivables Transactions
Add and maintain user-dened aributes at the invoice header, invoice line, and invoice tax line level of OAGIS 10.1 XML
Receivables transactions.
OAGIS 10.1 XML provides many standard aributes for including information related to a transaction, such as purchase
orders, shipping information, inventory details, and accounting. You can include aributes not mapped in and with no
standard tag available in OAGIS 10.1 XML, by adding the aributes to the UserArea extension of OAGIS 10.1.
Prepare User-Dened Aributes

You use public APIs to insert and process user-dened aributes in XML transactions.
9
The public APIs include:

• arp_util.insert_ar_extension_aributes: Use the public API arp_util.insert_ar_extension_aributes to create and
load user-dened aributes into the AR_EXTENSION_ATTRIBUTES table.
• arp_util.update_ar_extension_aributes: Use the public API arp_util.update_ar_extension_aributes
to update the ATTRIBUTE_NAME and ATTRIBUTE_VALUE of user-dened aributes already in
AR_EXTENSION_ATTRIBUTES table.
• arp_util.update_ready_for_xml_ag: Use the public API arp_util.update_ready_for_xml_ag to set
RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY to Y in the Load Extension Aributes for XML
Transactions BIP report. The signature of this API is available in the delivered data model for the BIP report
process.
Use these APIs in the PL/SQL code you write in the anonymous code block of the delivered Load Extension Aributes
for XML Transactions BIP data model. The Load Extension Aributes for XML Transactions BIP report process runs as
part of the Generate and Transfer XML Transactions process.
The extension aributes for Receivables transactions are computed and loaded into the AR_EXTENSION_ATTRIBUTES
table during XML creation and delivery, once you congure the Load Extension Aributes for XML Transactions BIP
data model to compute and load extension aributes using the API arp_util.insert_ar_extension_aributes. 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 aributes into the AR_EXTENSION_ATTRIBUTES table appear
in the report output of the Load Extension Aributes for XML Transactions BIP process.
To add user-dened aributes 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 Aributes 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 aributes 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 aributes are inserted. The API to set this is
arp_util.update_ready_for_xml_ag.
8. Save your work.
When you have nished dening your extension aributes and completed creating the Receivables transactions to
deliver in XML format, run the Generate and Transfer XML Transactions process to deliver these transactions.
If RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY is not set to Y by the Load Extension Aributes for XML

Transactions process, the process marks the XML Delivery Status of the transactions as Delivery Failed. Review the
report output of the BIP process for errors encountered while inserting extension aributes for transactions that did not
have READY_FOR_XML_DELIVERY set to Y.
API Signatures
The signatures of the APIs are available in the delivered data model for the Load Extension Aributes for XML
Transactions BIP report process.
The signature of the API arp_util.insert_ar_extension_aributes to insert user-dened aributes into the
AR_EXTENSION_ATTRIBUTES table is as follows:
PROCEDURE insert_ar_extension_aributes(extension_ar_tbl IN ARP_UTIL.EXTENSION_ATTR_TBL_TYPE,
10
x_msg_count OUT NOCOPY NUMBER,
x_msg_data OUT NOCOPY VARCHAR2,
x_return_status OUT NOCOPY VARCHAR2);
In this case EXTENSION_ATTR_TBL_TYPE is a PL/SQL table of the EXTENSION_ATTRIBUTE_RECORD record type. The
denition 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);
The signature of the API arp_util.update_ar_extension_aributes to update ATTRIBUTE_NAME and ATTRIBUTE_VALUE

of the user-dened aributes already in the AR_EXTENSION_ATTRIBUTES table is as follows:
PROCEDURE update_ar_extension_aributes(extension_ar_tbl IN ARP_UTIL.EXT_ATTR_TBL_FR_UPDATE,
In this case EXT_ATTR_TBL_FR_UPDATE is a PL/SQL table of the EXT_ATTR_RECORD_FR_UPDATE record type. The
denition 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);
The signature of the API arp_util.update_ready_for_xml_ag to update READY_FOR_XML_DELIVERY_FLAG in the

RA_CUSTOMER_TRX_ALL table is as follows:
PROCEDURE update_ready_for_xml_ag(p_customer_trx_id IN NUMBER,
p_xml_ready_ag IN VARCHAR2,
OAGIS 10.1 XML Delivery Errors

After you run the Generate and Transfer XML Transactions process to deliver transactions in OAGIS 10.1 XML format,
review the status of your XML transaction deliveries. If necessary, take corrective actions on any transactions that were
not successfully delivered.
XML Transaction Delivery Errors

Use the Manage Transactions page to review transactions delivered in XML format. Use Collaboration Messaging to
review and correct any transactions with the XML delivery status Processing Error or Delivery Failed.
• Use the Manage Undelivered Collaboration Messages page to review the error details of transactions with the
XML delivery status Processing Error.
11
• 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.
Inbound CBOD Collaboration Message

The inbound CBOD collaboration message returns an acknowledgment code of Success, Error, or Other. This
acknowledgment code appears in the XML Delivery Status column of the Manage Transactions page.
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 Conrmation Codes page of the Manage B2B Trading Partners task in the
Collaboration Messaging work area.
Note: Collaboration Messaging provides the CollaborationMessageService, which service providers

and trading partners can use to send the CBOD acknowledgment. You can access the details of the
CollaborationMessageService using the available URL.
Review Errors in XML Transaction Delivery

To review errors in XML delivery:
1. Navigate to the Manage Transactions page.
2. Search for transactions with the Delivery Method eld set to XML.
3. Scroll across to expose the Ready for XML Delivery and XML Delivery Status columns.
4. If the XML Delivery Status column for an XML transaction displays Processing Error or Delivery Failed, use
Collaboration Messaging to investigate the cause of the failure.
5. Navigate to the Collaboration Messaging work area.
6. If the status is Processing Error, navigate to the Manage Undelivered Collaboration Messages page.
You can either reprocess these transactions from the Manage Undelivered Collaboration Messages page or set
them to Delivery Failed by canceling the transactions.
7. If the status is Delivery Failed, navigate to the Manage Failed Collaboration Messages page.
You can reprocess these transactions with another run of the Generate and Transfer XML Transactions
process, seing the Transactions Included parameter to Failed Transactions.
Correct Errors in XML Transaction Delivery

Review and correct outbound processing, document retrieval, and inbound processing errors using the Manage Failed
Collaboration Messages and Manage Undelivered Collaboration Messages tasks.
To review and correct errors in XML delivery:

1. Navigate to the Collaboration Messaging work area.
2. Open either the Manage Failed Collaboration Messages page or the Manage Undelivered Collaboration
Messages page.
12
3. Search for the XML transaction you want.

4. In the Messages section, review the Error Type and Error Subtype columns:
◦ Error Type displays the category of delivery error: Outbound Processing Error, Document Retrieval, or
Inbound Processing Error.
◦ Error Subtype displays the specic delivery error.
This table displays for each Error Type and Error Subtype the corrective action to use:
Error Type Error Subtype Corrective Action
Outbound Processing Error Collaboration Messaging Framework is 1. Navigate to Setup and

disabled Maintenance.
2. Open the Manage Collaboration
Messaging Conguration page.
3. Enable collaboration messaging for
the Order to Cash business process.
4. Rerun the Generate and Transfer
XML Transactions process with the
Transactions Included parameter
set to Failed Transactions.
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
Conguration page and search for
the customer account.
3. Set the Association
Status to Enabled for the
PROCESS_INVOICE_OUT
document.
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. Dene the PROCESS_INVOICE_OUT
document for this trading partner.
Outbound Processing Error External Partner Message not found 1. Navigate to the Collaboration
trading partner.
3. Dene the
PROCESS_INVOICE_COLLAB_MSG_OUT
message for this trading partner.
13

Outbound Processing Error Application Partner Document status is 1. Navigate to the Collaboration
Hold Messaging Framework work area.
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
3. Review the error description and x
the Web service URL, if that is the
reason for the error.
Outbound Processing Error Unexpected error 1. Navigate to the Collaboration

3. Review the error description and x
the reason for the error.
Outbound Processing Error External Partner Document status is not 1. Navigate to the Collaboration
Active Messaging Framework work area.
trading partner.
3. Set the PROCESS_INVOICE_OUT
document status to Active for this
trading partner.
Outbound Processing Error External Partner Message status is not 1. Navigate to the Collaboration
Active Messaging Framework work area.

14

Messaging Service Providers page
and search for the service provider.
3. Set the
message status to Active for this
service provider.
Outbound Processing Error Application Service Invocation Failure 1. Navigate to the Collaboration
Document Retrieval Application Partner Document not found 1. Navigate to the Collaboration
3. Associate the
PROCESS_INVOICE_OUT document
to the customer account.
Document Retrieval Application Query returned no records

Rerun the Generate and Transfer
Transactions Included parameter set to
Failed Transactions.
Inbound Processing Error Setup validation failure 1. Navigate to the Collaboration

Messaging Service Providers page
and search for the service provider.
3. Dene the
CONFIRM_BOD_COLLAB_MSG_IN
message and associate it to the
message for this service provider.
Inbound Processing Error Unidentied Message Type 1. Ensure that the type in the
BusinessObjectDocument tag of
the CBOD XML sent by the external
partner is ConrmBODType.
2. The existing document cannot be
reprocessed. The inbound CBOD
15
needs to be re-sent by the external

partner.
Related Topics
• Reprocess Undelivered Messages
Reports for Create and Process Transactions

Billing History Report
Use the Billing History Report to review a summarized history of activity against each of your customer invoices, debit
memos, chargebacks, and on-account credits.
The Billing History Report includes for each debit item the original transaction amount, the current balance due, the
sum of all payments applied to the debit item, the total credit memo amounts that aect the debit item, and the total
adjustment amounts for the debit item.
Submit this report according to your transaction or customer review requirements.
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.
Report Heading Description
Transaction Original Amount The original amount of the transaction.

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.

Activity Adjusted Amount The amount of each adjustment to the transaction.

This table describes the row heading in the Billing History Report.
Row Heading Description
Total for Currency The totals for all transaction activity in the entered currency.
16

Document Number Audit Report

Use the Document Number Audit Report to identify missing document numbers. The report identies missing numbers
in a given sequence. If you are using manual or partial automatic numbering, the report only validates that the numbers
are unique, not that they are sequential.
You enable document sequencing in the Sequencing section of the Specify Options page of your primary ledger. If
you enable both of the following options, then document sequencing is always used in all legal entities assigned to the
ledger:
• Set the Sequencing By option to Legal Entity.

• Enable the Enforce Document Sequencing option for Receivables.
However, even with these seings 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.
Run this report according to your document audit requirements.
Report Parameters
Report Type
Adjustment, Invoice, or Receipt.
Sequence Name
The name of the document sequence that you want to audit.
From/To Document Number
The document number range to include in the report.
Report Output
This table describes the important column headings in the Document Number Audit Report.
Column Heading Description
Document Number The missing document number.

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
• Deleted: The Audit table contains an entry for this document number but the
Transaction table does not.
Overview of the Invoices Posted to Suspense Report

This topic contains summary information about the Invoices Posted to Suspense Report.
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 exeld,
postable status, and currency.
Frequently Asked Questions

The following table lists frequently asked questions about the Invoices Posted to Suspense Report.
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
FAQ Answer
What type of report is this? Oracle Business Intelligence Publisher

Invoices Posted to Suspense Report

Use the Invoices Posted to Suspense Report to review a list of all transactions that have revenue amounts posted to
suspense accounts.
Receivables posts revenue amounts to a suspense account when you import transactions using AutoInvoice and both of
the following are true:
• The amount specied 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 exeld,
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.
Class The transaction class of the transaction.

Transaction Type The transaction type assigned to the transaction.

Transaction Number The number assigned to the transaction.

Customer Name The customer name on the transaction.

Customer Account Number The customer account number on the transaction.

Transaction Date The date the transaction was created.

Accounting Date The date the transaction posts to general ledger.

Entered Amount The transaction amount in the entered currency.

Accounted Amount The transaction amount in the ledger currency.

19
This table describes important row headings in the Invoices Posted to Suspense Report.
Company The company or balancing segment of the accounting exeld 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.

Report Summary The total accounted amount for all transactions.

20
Overview of the Transaction Details Report

This topic contains summary information about the Transaction Details Report.
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 exeld.

The following table lists frequently asked questions about the Transaction Details Report.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Billing

Who uses this report? Financial Specialist during transaction reviews.
21
FAQ Answer

When do I use this report? When you need to see all the details related to specic transactions.

What can I do with this report? Schedule as needed.


Transaction Details Report

Use the Transaction Details Report to review all of the information that was entered for each of your transactions.
The report provides detailed information on all invoices, credit memos, debit memos, and chargebacks belonging to a
business unit.
The report provides, for each transaction, complete header and line information, tax information, freight information,
sales credits, revenue accounting, account sets, and transaction exeld.
Run this report according to your customer transaction review requirements.
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.

Special Instructions Any special instructions about the transaction.

Comments User comments about the transaction.

Transaction Flexeld The transaction exeld for the transaction, if applicable.

This table describes the revenue accounts column headings in the Transaction Details Report.
22
Revenue Accounts Column Heading Description
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 Flexeld The revenue account for the line item distribution.

Comments User comments about 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.
Account Sets Column Heading description
Line Number The transaction line number to which this account set is applied.

Other Line The tax or freight line number.

Line Type The line type: Line, Tax, Freight, or Charges.

Account Class The account class for the accounting exeld.

Percentage The percentage of the transaction line amounts that is associated with this account.

Accounting Flexeld The accounting exeld for the tax account.

Comments User comments about the transaction line.

Revenue Scheduling Rule The revenue scheduling rule associated to the transaction line, if applicable.

23
Overview of the Transaction Register

This topic contains summary information about the Transaction Register.
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 specied period.

The following table lists frequently asked questions about the Transaction Register.
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
FAQ Answer
• During the receivables reconciliation process.

What type of report is this? Oracle Transactional Business Intelligence

Related Subject Areas

This report uses the Receivables - Transactions Real Time subject area.
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 specied period.
You can optionally review transactions that update customer balances but do not post to the general ledger by seing
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.
Selected Report Parameters

Accounting Date
The transaction accounting date range to include in the report.
Transaction Currency
Conne the report to one transaction currency.
Transaction Class
Conne the report to invoices, credit memos, chargebacks or debit memos.
Post to General Ledger Eligible
• 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
This table describes the report headings in the Transaction Register.
Transaction Entered Amount The amount of the transaction in the transaction currency.

Transaction Currency The currency of the transaction.

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.

Grand Total Total accounted amount for the report.

Related Topics
• Options for Posted and Non-Posted Activities using Transaction Types
• Guidelines for Using the Receivables to General Ledger Reconciliation Report
FAQs for Create and Process Transactions

When do I enter an invoicing rule?
Enter an invoicing rule for invoices that recognize receivables over more than one accounting period. There are two
invoicing rules:
• In Advance: Use this rule to recognize the receivable immediately.
• In Arrears: Use this rule to recognize the receivable at the end of the revenue recognition schedule, which is
dened by the revenue scheduling rule assigned to the invoice.
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.
What's the dierence between the various customers?

An invoice identies the customer or customers involved in the transaction. Often the various customer entries all refer
to the same enterprise, or to legal entities belonging to the same enterprise.
If you enter ship-to customer information, this populates the default bill-to information. If you enter bill-to information,
this does not populate default ship-to information.
From an invoicing point of view, you don't have to provide ship-to information. However, taxes are calculated based on
ship-to information.
26
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 identies 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 identied. For example, similar
goods are sold to dierent 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 dierent parties.
What legal entity is assigned to a transaction?

A legal entity is assigned to a transaction according to this hierarchy:
1. Legal entity of the transaction type assigned to the transaction.
2. Legal entity of the transaction source assigned to the transaction.
3. Default legal entity assigned to the business unit.
You can update the legal entity assigned to the transaction in the Miscellaneous section of the Create and Edit
Transaction pages with any other legal entity associated with the active ledger of the business unit.
How do I create and update installments?

Assign split payment terms to an invoice or debit memo to let customers make payments in multiple installments. The
billing process automatically creates the payment schedules based on the transaction date and the details of the split
payment terms. For example, split payment terms can specify that 40 percent of an invoice is due 30 days after the
invoice date, and the remainder is due in 60 days.
You can review installments for an invoice or debit memo transaction from the Review Transaction page or the Manage
Transactions page. You can perform these actions on installments:
• Update the due date of an installment.
How do I manage sales credits?

The sales credit allocation is calculated based on the salespersons assigned to the transaction. Use the Sales Credits
section on the Review Transaction page to review and update sales credit allocations to both the transaction and
transaction lines.
If the AR: Update of Existing Sales Credits Allowed prole option is set to No, the existing sales credits are read only.
You can still adjust sales credit allocations by adding new lines with the changes that you want to apply.
How do I manage freight charges?

You can assign freight charges to a transaction or to each transaction line. When you assign freight charges to a
transaction, the freight amount is included in the total amount of the transaction.
By default, tax is not calculated on freight charges. However, you can calculate sales tax on freight by using a memo line
to dene freight services and entering this memo line as a transaction line item.
How do I manage default tax exemption handling for invoice lines?

If you update the default tax exemption handling value at the transaction level, this value becomes the default value for
any new transaction lines created. You can change this default value on the new lines created at the line level.
27
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.
Why can't I incomplete the transaction?

Because the primary ledger is set to enable document sequencing at the legal entity level and to enforce document
sequencing in chronological order by accounting date.
Once the transaction is completed and a document number assigned, you can't incomplete the transaction because it
would create a gap in the chronological sequence.
Why can't I update freight information for the entire invoice?

You update freight charges that apply to the entire invoice at the invoice level only. If freight is entered on one or more
individual invoice lines, you can only update these freight amounts at the line level. Updates to freight at the invoice
level don't update freight amounts at the line level.
Why can't I update an installment on the transaction?

Because the transaction belongs to a bill plan and the installment has either a dispute or an adjustment against it.
Can I enter a document number on a void transaction?

No, document sequencing uses the accounting date as the document sequence date. Void transactions don't have an
accounting date.
In addition, you can't void an existing transaction assigned a document number if the Receivables system option Allow
transaction deletion is not enabled. This is to maintain the integrity of gapless sequencing.
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 conrm that the customer was overcharged for a line item on the invoice. You need management
approval to make an adjustment to the invoice.
From the Review Transaction: Invoice page:
1. Click Social to open Oracle Social Network. Click the Share buon, 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 aention.
Your manager asks you to conrm 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
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
Manage Recurring Billing

Overview of Recurring Billing
Use Recurring Billing to manage the creation of invoices on a cyclical basis for a xed period of time, as reected in
the terms of a contract with your customer. Examples include the use of rental equipment at a xed monthly rate, or
consulting services provided on an ongoing basis for the life of a project.
Use the Create Recurring Bill Plan page to dene a bill plan according to the negotiated terms of the contract with your
customer. Important components of the bill plan include contract and billing dates, billing frequency, payment terms,
receipt method and payment instrument details, and the items or memo lines to be billed.
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 reect 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.
How You Implement Recurring Billing

Set up for recurring billing to create and manage recurring billing bill plans. You use recurring bill plans to generate a
set of transactions with the same header and line information over a period of time agreed upon between you and the
customer.
To set up for recurring bill plans, complete these tasks:
• Set Receivables Prole Options for Recurring Bill Plans
• Set Receivables System Options for Recurring Bill Plans
• Set Up Transaction Sources for Recurring Bill Plans
29
• Set Up Transaction Types for Recurring Bill Plans
Set Receivables Prole Options for Recurring Bill Plans

Set one or both of these prole options for recurring bill plans:
• Default Business Unit prole option: If applicable, dene a business unit to populate by default in the Business
Unit eld on the Create Recurring Bill Plan page.
• Conversion Rate Type prole option: If applicable, dene a conversion rate type to populate by default in the
Conversion Rate Type eld on the Create Recurring Bill Plan page.
Enter a value for this prole option if you intend to create a bill plan in a currency other than the ledger
currency of the business unit assigned to the bill plan.
Set Receivables System Options for Recurring Bill Plans

To set Receivables system options for recurring bill plans:
1. Navigate to the Create System Options or Edit System Options page.
2. Select the applicable business unit.
3. Click the Billing and Revenue tab, if it is not already displayed.
4. In the Transactions section, enable the Enable recurring billing option to activate features in Receivables for
recurring bill plans. This includes:
◦ Recurring Bill Plan pages
◦ Recurring Bill Plan aributes in the Manage Transactions page and the Edit and View Transaction pages
◦ Generate Recurring Billing Data process
5. In the Transactions section, enable the Allow change to printed transactions option if you want to be able to
update installments on transactions generated by a bill plan after the transaction was printed and delivered.
6. Complete or update the rest of Receivables system options according to your requirements, and save.
Set Up Transaction Sources for Recurring Bill Plans

Receivables provides the predened transaction source ORA_RecurringBilling. This transaction source appears by
default on the Create Recurring Bill Plan page. You can set up additional transaction sources for use with recurring bill
plans according to your needs.
To set up a transaction source for recurring bill plans:

1. Navigate to the Manage Transaction Sources page.
2. Click the Add icon.
3. In the Transaction Source Set eld, select the Common Set.
4. In the Name eld, enter a name for this transaction source for recurring bill plans.
5. In the Description eld, enter a description for this transaction source.
6. In the Type eld, select Imported.
7. Enter the dates that this transaction source is active.
Note: You can only use transaction sources that are active on or before the rst transaction date
specied on the bill plan, and are active during the entire life of the bill plan.
8. Enable the Automatic transaction numbering option and enter a number in the Last Number eld.
9. In the Standard Transaction Type eld, select Invoice or another transaction type that you have dened for
use with recurring bill plans.
10. In the Invalid Line eld, select Reject Invoice.
11. In the Accounting Date in a Closed Period eld, select Adjust.
30
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 seings according to your requirements, and save.
Set Up Transaction Types for Recurring Bill Plans

Set up Invoice transaction types for use with invoice transactions created by a recurring bill plan.
Receivables provides the predened 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.
To set up an Invoice transaction type for recurring bill plans:

1. Navigate to the Manage Transaction Types page.
2. Click the Add icon.
3. In the Transaction Type Set eld, select the Common Set.
4. In the Name eld, enter a name for this transaction type for recurring bill plans.
5. In the Description eld, enter a description for this transaction type.
6. In the Transaction Class eld, select Invoice.
7. In the Transaction Status eld, select Open, Closed or Pending.
You can't create a Void transaction type for use with recurring bill plans.
8. Enter the dates that this transaction type is active.
Note: You can only use transaction types that are active on or before the rst transaction date
specied on the bill plan, and are active during the entire life of the bill plan.
9. In the Creation Sign eld, select Positive Sign.
10. In the Generate Bill eld, select Yes.
11. Ensure that the Open Receivable and Post to GL options are enabled.
12. In the Reference Accounts section, enter a Revenue account.
13. Complete the remaining seings according to your requirements, and save.
How You Use the Dates on a Recurring Bill Plan

Use the dates on the recurring bill plan to manage the billing activities and milestones for all transactions created by the
plan.
If you need to update any dates related to the bill plan, you must ensure that all updates are consistent with the contract
terms and all necessary billing periods and transactions.
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 reected 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
First Transaction Date

Enter in the First Transaction Date eld the date of the rst transaction created by the bill plan. The default is the
system date, that is, the same date as the contract start date. You can enter a rst transaction date that is either on or
after the contract start date within the rst billing period.
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.
Second Transaction Date

Use the Second Transaction Date eld to create a transaction date for the second and all subsequent transactions
created by the bill plan. You enter a second transaction date if the rst transaction created was for a partial period only,
and you don't want to use the rst transaction date as the creation date for all remaining transactions in the plan.
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.
Second Billing Period Start Date

Use the Second Billing Period Start Date eld to create a dierent billing period start date for the remaining billing
periods in the bill plan.
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.
How Recurring Bill Plans Generate Invoices

Create a recurring bill plan to generate a set of invoices for a customer over a specied period of time.
The denition of a bill plan reects the negotiated terms of a contract with the customer for goods delivered or services
rendered. A bill plan includes details such as billing frequency, contract start and end dates, payment terms, and the
items or memo lines to include on each invoice. After you create a recurring bill plan, you use AutoInvoice to generate
invoices for a given billing period according to the bill plan denition.
Seings That Aect Recurring Bill Plans

These seings are important for creating bill plans and generating invoices automatically:
• Receipt Method: Create at least one receipt method for each customer for whom you intend to create a bill plan.
The receipt method must be active as of the rst transaction date of the bill plan.
32
• Create Recurring Bill Plan page: Important seings for creating a bill plan include:
◦ Transaction Source eld: Use the predened transaction source ORA_RecurringBilling or enter an
Imported transaction source dened for use with bill plans.
◦ Transaction Type eld: Use the predened transaction type Invoice or enter an Invoice transaction type
dened 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 dierent 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.
How Invoices Are Generated for a Bill Plan

Complete these steps to generate invoices for a bill plan:
1. Create a bill plan that reects 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. Identies 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
3. Run the Import AutoInvoice program. The program:
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.
Guidelines for Updating Recurring Bill Plans

You may need to update one or more details of a recurring bill plan to reect changes to the terms of the contract with
your customer.
Use the Edit Recurring Bill plan page to update a bill plan. Until you generate transactions for a bill plan, you can update
any aribute except the business unit assignment and the bill plan name. Updates to a bill plan that has not generated
transactions are not tracked in the recurring bill plan history.
Once you generate transactions for a bill plan, the aributes 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 exelds.
Note: Updates to a recurring bill plan aect future-generated transactions only. You can't use the bill plan to
modify transactions already generated by the bill plan.
Review these guidelines for updating a recurring bill plan:
• Inactivate a Recurring Bill Plan

• Change Assignments to a Recurring Bill Plan
• Update Invoice Lines
• Rules for Changing the Price of Invoice Line Items
Inactivate a Recurring Bill Plan

After the life of a bill plan is complete and the last transactions generated, you should inactivate the bill plan by
deselecting the Active option. A bill plan should be inactivated after the contract end date.
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:
• You can't make any updates to the bill plan.

• Running the Generate Recurring Billing Data program doesn't generate transactions for the bill plan.
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
Change Assignments to a Recurring Bill Plan

The bill plan contains certain aributes that may change during the life of a bill plan. These aributes are:
• Transaction source
• Transaction type
• Currency
• Salesperson
Changes include inactivating the aribute, updating the start and end dates, or updating details of the aribute 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 aributes. Ensure that the new aribute
is active for the duration of the bill plan, and is otherwise compatible with the bill plan.
Update Invoice Lines

Update the invoice lines of a recurring bill plan to reect changes to the invoicing terms of the contract agreed upon
with your customer. Updates to invoice lines aect future transactions only, that is, transactions generated after you
update the bill plan. The invoice lines of transactions already generated do not change.
You can perform these updates to invoice lines:

• Add one or more bill plan lines: Click the plus (+) icon to add an invoice line. You can enter an inventory
item, memo line, or description to create the line item. Enter the quantity and, for descriptions, the unit
price to calculate the line amount. Complete the remaining information for the new line according to your
requirements.
• Delete existing bill plan lines: Select a line and click the delete (x) icon to delete a line.
• Update the quantity of an item: Use the Quantity eld to update the quantity to be billed for an existing invoice
line.
• Make a price change to a line item: Use the New Price and Eective From elds to enter the new price for the
line item and the date the new price becomes eective.
Rules for Changing the Price of Invoice Line Items

You can change the price of a line item to reect changes to the terms of the contract with your customer.
If necessary, you can expose the New Price and Eective From elds on an invoice line by selecting them from the
View menu: View > Columns > Line Information > New Price and Eective From.
These rules apply to changing the price of a line item:

• You can either increase or decrease the price of a line item.
• The date a new price becomes eective is a future date only. You can't enter an eective date for a price
change that is earlier than or equal to the system date.
You can enter a future eective date for either the current billing period or a future billing period.
• You can only change the price of a line item once during the current billing period, that is, before the next
transaction is generated. After the next transaction is generated, the new price becomes the current unit price.
If necessary, you can change the price again before the next billing period.
• The total transaction amount is not prorated in the billing period that the new price becomes eective.
35
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 eective 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.
How You Create Invoices for a Recurring Bill Plan

Recurring Billing uses AutoInvoice to generate invoice lines and create invoices for recurring bill plans.
You rst run the Generate Recurring Billing Data process to generate invoice lines. You then run the Import AutoInvoice
process to create invoices from invoice lines. If necessary, you can use the AutoInvoice workbook to correct errors and
reload your data.
Generate Recurring Billing Data Process

Run the Generate Recurring Billing Data process to generate invoice lines for active bill plans. By default, the process
generates invoice lines for all eligible bill plans belonging to all business units. You can use the process parameters to
select a subset of bill plans by business unit, bill plan name, billing frequency, and customer.
The Generate Recurring Billing Data process looks for active bill plans using the parameters you selected and identies
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.
On February 5, the process performs the following operations:
• 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).
Import AutoInvoice Process

Run the Import AutoInvoice process to group bill plan invoice lines into recurring invoices. The import process groups
invoice lines into recurring invoices using the mandatory parameters Bill Plan Name and Bill Plan Period of the
AutoInvoice grouping rule, as well as any optional parameters that you specify.
36
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 reected 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.
Review Transactions Generated by a Recurring Bill Plan

Use the Review Transaction page to review individual transactions generated by a recurring bill plan.
You can access transactions generated by a bill plan in either of these ways:
• From the Manage Recurring Bill Plans page:
a. Search for bill plans.

b. Select a bill plan with a Status Tracker value of Complete, and click the Review Transactions buon.
c. The Manage Transactions page opens.
d. Click a transaction number to open the Review Transaction page.
• From the Manage Transactions page:
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.
To identify a bill plan transaction:
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 identies the bill plan that generated the transaction.
The Bill Plan Period eld identies the billing period for the transaction.
If the terms of the contract with your customer change, you can update the bill plan itself to reect 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
FAQs for Manage Recurring Billing

Can I change the contract dates on a bill plan?
Yes, but changing one date does not update the others automatically. The contract start and end dates should reect
the actual terms of the contract. In addition, the contract start date is also the rst billing period start date.
By default, the contract start date and rst transaction date are the system date, and the contract end date is one year
later. If you update the contract start date, then you must update the rst transaction date accordingly.
What happens if the bill plan is not in the ledger currency?

If the recurring bill plan uses a currency other than the ledger currency, enter the conversion rate type and, if applicable,
the conversion rate.
The conversion rate date used is the date transactions are generated for a given billing period.
Can I defer revenue on invoices generated by a bill plan?

No, the revenue on invoices generated by a recurring bill plan is recognized on the invoice transaction date. You can't
assign invoicing rules or revenue scheduling rules to bill plans.
What happens if I inactivate a bill plan?

All of the dates on the bill plan are still respected. During the inactive period, the Generate Recurring Billing Data
program doesn't create transactions for this bill plan. If you activate the bill plan again, the program creates transactions
for all applicable billing periods dened in the bill plan, including the periods during which the bill plan was inactive.
After the contract end date and the conclusion of all invoicing, you can inactivate the bill plan.
What's the dierence 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:
• First transaction date, followed by rst transaction date + billing frequency.

• First transaction date, followed by second transaction date, followed by second transaction date + billing
frequency.
The billing period is the period of time covered by a single invoice for goods shipped or services rendered.
The billing periods are dened in either of these ways, depending on whether you use the second billing period start
date:
• Contract start date, followed by contract start date + billing frequency.

• Contract start date, followed by second billing period start date, followed by second billing period start date +
billing frequency.
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
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
There are two other AutoInvoice interface tables:

• AR_INTERFACE_CONTS_ALL is populated if there are any revenue contingencies associated with the
transaction line.
• RA_INTERFACE_ERRORS_ALL stores information about interface data that failed validation.
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
AutoInvoice Validations on Imported Data

AutoInvoice validates data imported using the AutoInvoice le-based data import spreadsheet for compatibility
with Receivables. The validation process ensures that the columns in the AutoInvoice Interface tables reference the
appropriate values and columns in Receivables.
Review these aspects of the AutoInvoice validation process:

• Standard Validations
• Transaction Source Seings
• Credit Memos Against Paid Invoices
Standard Validations
AutoInvoice performs these standard validations on all data:
• Setup Values Dened: Ensures that the values pertaining to your setup are already dened 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
• Currency Precision: Ensures that the amount and the accounted amount have the correct precision for a given
currency, as dened 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.
Transaction Source Seings

You can only use transaction sources of type Imported with the Import AutoInvoice process. The seings in the
AutoInvoice Options and Import Information sections of the Imported transaction source determine how AutoInvoice
validates imported transaction lines.
Credit Memos Against Paid Invoices

AutoInvoice validates credit memos by reviewing the seing of the Receipt Handling for Credits option on the
transaction source.
If the Receipt Handling for Credits option is enabled, then AutoInvoice automatically reviews each credit memo and
associated invoice to determine its eligibility for receipt handling.
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
How AutoInvoice Processes Data During Import

Use the Import AutoInvoice process to import and validate transaction data from Project, Distributed Order
Orchestration, and non-Oracle nancial systems to create invoices, debit memos, credit memos, and on-account credits
in Receivables.
You can download an AutoInvoice spreadsheet template to use to prepare your data. The template contains an
instruction sheet to help guide you through the process of entering your information.
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 AutoInvoice 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 them.
40
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.
This gure describes the AutoInvoice import process:
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
Seings That Aect AutoInvoice Import Processing

These seings aect AutoInvoice import processing:
• Receivables interface tables: The interface tables temporarily store the transaction data from your source
system. You can enter values in specic columns of these tables to pass to AutoInvoice during the import
process.
41
• 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, dene 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.
If the value of RA_INTERFACE_LINES_ALL.CONVERSION_TYPE is User, then you must provide a conversion

rate in RA_INTERFACE_LINES_ALL.CONVERSION_RATE.
• Transaction source: Select an Imported transaction source for a run of the Import AutoInvoice process. These
seings on the Imported transaction source inuence the import process:
◦ 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 seings in this section to modify details of the import process.
◦ Import Information section: Use the seings in this section to indicate how AutoInvoice validates
imported data.
• AutoInvoice grouping rule: Dene an AutoInvoice grouping rule to identify the transaction aributes 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: Dene an AutoInvoice line ordering rule to organize the transaction lines
belonging to a transaction created by the grouping rule in a specic 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.
How Imported Data Is Processed

The AutoInvoice import process contains three phases: validation, grouping, and transfer.
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 seings 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 aention to the mandatory and optional aributes 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
How Freight Lines and Late Charges Are Processed

AutoInvoice ensures that there is at most one freight line for an imported invoice, or at most one freight line per
transaction line, but not both. If you import multiple header freight lines for one invoice, AutoInvoice validates that all
of the freight lines apply to the same freight account and consolidates them into one line. This consolidated freight line
is the only freight line for this invoice that is passed to the Receivables tables. If all of the freight lines don't apply to the
same freight account, then AutoInvoice rejects the invoice.
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 Aributes
• How AutoInvoice Validates Imported Transactions
• How AutoInvoice Processes Credited Amounts
AutoInvoice Execution Report

Use the AutoInvoice Execution Report to review a run of the Import AutoInvoice process.
The AutoInvoice Execution Report lists the total number of transactions imported for each AutoInvoice run, with
detailed information for all transaction lines that failed import. The report includes summary information for the
invoices, debit memos, and credit memos that were processed in each currency. The report also shows the total amount
for each transaction class for all transactions processed.
43
You can also review and correct AutoInvoice errors by downloading the AutoInvoice Lines spreadsheet from the Billing
work area.
How You Correct AutoInvoice Errors

During AutoInvoice import, records that pass validation are transferred to the Receivables tables. Records that fail
validation remain in the AutoInvoice interface tables. Before AutoInvoice can validate these records and create
transactions, you must correct invalid data and run AutoInvoice again.
Each time you run AutoInvoice, the process generates a list of records that failed validation. You can display these
AutoInvoice errors as an Excel workbook in either of two ways:
• Click the Manage AutoInvoice Lines link to open a workbook with all error records.
• Click a Number of Errors link in the AutoInvoice Errors section to open a workbook for these specic error
records.
AutoInvoice Errors Workbook

Every workbook has three tabbed worksheets. You can use the tools available in the workbook to manage the review
and update of information.
The workbook is populated with information from the AutoInvoice tables:

• RA_INTERFACE_LINES_ALL: Transaction header and line information.
• RA_INTERFACE_SALESCREDITS_ALL: Sales credit information for transactions.
• RA_INTERFACE_DISTRIBUTIONS_ALL: Distributions linked to the appropriate transaction lines in the
ra_interface_lines table from the transaction exeld.
• RA_INTERFACE_CONTS_ALL: Revenue contingencies that impact revenue recognition for imported
transactions.
• RA_INTERFACE_ERRORS_ALL: All interface lines that failed validation and were not imported into Receivables
tables.
The three tabbed worksheets arrange AutoInvoice information in this way:

• AutoInvoice lines and line distributions.
• Tax and freight distributions.
• Sales credits and revenue contingencies.
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 buon at any time. When you save, this updates
the corresponding records in the AutoInvoice interface tables.
44
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 buon to display the parameters
for AutoInvoice submission. Once the process is successfully submied, AutoInvoice provides a concurrent request ID.
Related Topics
• AutoInvoice Data Preparation
AutoInvoice Import and Credit Memos

You can use AutoInvoice to import and validate transaction data from a legacy system to create credit memos in
Receivables.
You can import:
• On-Account Credit Memos
• Credit Memos against Transactions
• Credit Memos Against Invoices With Rules
• Credit Memos Against Invoices Without Rules
• Credit Memos Against Tax and Freight Lines
Note: You can't apply a credit memo to a chargeback using AutoInvoice.
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.
On-Account Credit Memos

An on-account credit memo is a credit memo that is not linked to an 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
Credit Memos against Transactions

You can link a credit memo to an invoice in one of two ways:
1. Populate the REFERENCE_LINE_ID column on the RA_INTERFACE_LINES_ALL table with the
CUSTOMER_TRX_LINE_ID of the invoice.
2. On the RA_INTERFACE_LINES_ALL table, populate the REFERENCE_LINE_ATTRIBUTE1-15 columns with the
INTERFACE_LINE_ATTRIBUTE1-15 columns of the invoice. The INTERFACE_LINE_ATTRIBUTE1-15 columns are
stored in the RA_CUSTOMER_TRX_LINES_ALL table.
You must also populate the REFERENCE_LINE_CONTEXT column with the INTERFACE_LINE_CONTEXT column
of the invoice. The INTERFACE_LINE_CONTEXT column is stored in the RA_CUSTOMER_TRX_LINES_ALL table.
45
When you import credit memos against transactions, AutoInvoice validates that the seing of the Open Receivable
option on the transaction type assigned to the credit memo being imported matches the seing 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.
Credit Memos Against Invoices With Rules

When you import credit memos against invoices with rules, AutoInvoice uses the method you entered in
RA_INTERFACE_LINES_ALL.CREDIT_METHOD_FOR_ACCT_RULE to determine how to reverse the accounting entries
created for the original invoice.
You can enter LIFO, PRORATE, or UNIT:
• 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 specic quantities, starting with the period specied 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.
Credit Memos Against Invoices Without Rules

When you import credit memos against invoices without rules, AutoInvoice rst looks for an accounting date in the
interface table to use as the accounting date of the credit memo. If there is no accounting date in the interface table,
AutoInvoice uses the value of the Default Date parameter of the Import AutoInvoice program. The credit memo lines
must always have the same accounting date as the credit memo.
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.
Credit Memos Against Tax and Freight Lines

When you import credit memos, AutoInvoice ensures that you don't overapply tax and freight lines.
AutoInvoice Import and Transaction Distributions

You can assign distributions to transactions during AutoInvoice import.
You can assign distributions in either of two ways:
• Using the AutoInvoice Interface Tables

• Using AutoAccounting
The values that you can pass to AutoInvoice for the accounting exeld are either accounting segment values
or account code combination IDs. Use the Accounting Flexeld 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
Assign Distributions Using the AutoInvoice Interface Tables

If you pass accounting exeld segment values, you must assign values to the SEGMENT1-30 columns of the
RA_INTERFACE_DISTRIBUTIONS_ALL table. You can only assign values to enabled segments. For example, if you
enable six accounting exeld segments, then assign values to SEGMENT1-6 only.
If you pass accounting exeld 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.
Assign Distributions Using AutoAccounting

If you want AutoAccounting to determine your transaction distributions, don't enter values in the
RA_INTERFACE_DISTRIBUTIONS_ALL table. Use the AutoAccounting pages to dene your revenue, receivables, tax,
freight, clearing, unbilled receivable, and unearned revenue accounts.
After you dene 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.
AutoInvoice and Transaction Flexelds

Transaction exelds are descriptive exelds that AutoInvoice uses to identify transactions and transaction lines.
There are four types of transaction exelds:
• Line Transaction Flexeld

• Reference Transaction Flexeld
• Link-To Transaction Flexeld
• Invoice Transaction Flexeld
If you use AutoInvoice, you must dene the Line Transaction Flexeld. Because the Line Transaction Flexeld is unique
for each transaction line, you use the Line Transaction Flexeld to reference and link to other lines. AutoInvoice always
uses the Line Transaction Flexeld structure for both Link-to and Reference information during the import process. You
must explicitly dene the Link-to, Reference, and Invoice Transaction Flexeld structures only if this information is to be
displayed on a page that you have designed.
You can display Invoice Transaction Flexeld 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 Flexeld segment that you want to display. For example, if you want to
47
reference the order number for imported invoices when using an invoice list of values, you must assign the transaction
exeld 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 exeld and exeld segments as required:
1. Navigate to the Edit Descriptive Flexeld page for the exeld 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 exeld according to your requirements and save.
Line Transaction Flexeld

Use columns INTERFACE_LINE_ATTRIBUTE1-15 and INTERFACE_LINE_CONTEXT to dene the Line Transaction
Flexeld. Line Transaction Flexelds are unique for each record in the interface table and therefore can be used as
record identiers.
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 dene a new
context for the Line Transaction Flexeld to distinguish these transactions from transactions that originated in Oracle
Cloud applications.
Reference Transaction Flexeld

Reference Transaction Flexelds have the same structure as the Line Transaction Flexelds. Reference Transaction
Flexelds are used to apply a credit memo to an invoice.
For example, to refer a credit memo to a specic invoice, use the REFERENCE_LINE_ATTRIBUTE1-15 and
REFERENCE_LINE_CONTEXT columns of the credit memo to enter the Line Transaction Flexeld of the invoice.
Link-To Transaction Flexeld

Link-To Transaction Flexelds also have the same structure as the Line Transaction Flexeld. Use Link-To Transaction
Flexelds to link transaction lines together in the interface table.
For example, you might want to import tax and freight charges that are associated with specic transaction lines. If
you want to associate a specic tax line with a specic transaction line, use the LINK_TO_LINE_ATTRIBUTE1-15 and
LINK_TO_LINE_CONTEXT columns of the tax line to enter the Line Transaction Flexeld of the invoice.
Invoice Transaction Flexeld

To create an Invoice Transaction Flexeld, create a new exeld with a similar structure as the Line Transaction
Flexeld, but only include header level segments.
For example, if the Line Transaction Flexeld structure has four segments, and the last two segments contain line
level information, dene your Invoice Transaction Flexeld using the rst two segments only. You should also include
segments included in the Invoice Transaction Flexeld in the AutoInvoice grouping rules.
Related Topics
• Considerations for Managing Extensible Flexelds
48
Example of Transaction Flexeld Indexes

Create indexes on your AutoInvoice Transaction Flexeld columns if you want to query transaction exeld information
in your invoice headers and lines. If you don't use indexes, the validation portions of the Import AutoInvoice program
can exhibit slow performance.
Dene Indexes
Dene non-unique, concatenated indexes on the tables and columns that you use for your Transaction Flexeld header
and line information. The tables and columns are described in this table:
Table Columns
RA_ CUSTOMER_ TRX_LINES_ALL interface_ line_ aribute1-15

RA_ CUSTOMER_ TRX_ALL interface_ header_ aribute1-15

RA_ INTERFACE_ LINES_ALL interface_ line_ aribute1-15

RA_ INTERFACE_ DISTRIBUTIONS_ interface_ line_ aribute1-15

ALL

RA_ INTERFACE_ SALESCREDITS_ interface_ line_ aribute1-15

ALL

To determine which indexes you might need to create, query your Line Transaction Flexeld and note each context
of this exeld and, for each context, the segments that are enabled using interface line aribute columns from the
RA_INTERFACE_LINES_ALL table.
You can then create non-unique, concatenated indexes for the same interface line aribute columns in the
RA_CUSTOMER_TRX_LINES_ALL and RA_INTERFACE_LINES_ALL tables, and for the same interface header aribute
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 aribute
columns in the RA_INTERFACE_SALESCREDITS_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL tables.
Transaction Flexeld Details

You have set up a Transaction Flexeld context that uses INTERFACE_LINE_ATTRIBUTE1-3. In addition, you are
populating sales credits in the RA_INTERFACE_SALESCREDITS_ALL table.
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
• 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 dened, then you only need to create one index for each of the four tables. However, if you
have multiple contexts dened, 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.
This table shows a Line Transaction Flexeld with three contexts:
Flexeld Context Aribute Columns assigned to Enabled Segments
Context1 Interface_ line_ aribute1







Context1 has two aribute columns; Context2 has three aribute columns; and Context3 has two aribute columns.
Context1 and Context2 share two aribute columns.
Sharing Indexes
Dene 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 laer case, Context2 would use the same index as Context1, because Context1 and Context2 have the same rst two
aribute columns.
50
In other words, if you are using the same, or similar, aribute columns for two or more contexts, then you can optionally
create a single index instead of creating an index for each context.
Use the following syntax for your Create Index Statement:

$ sqlplus AR username/AR password
SQL> CREATE [UNIQUE] INDEX index ON
{Table (column1, column2, ...)
|CLUSTER cluster}
|INITRANS n] [MAXTRANS n]
[TABLESPACE tablespace]
[STORAGE storage]
[PCTFREE n]
[NOSORT];
Accounting Date Derivation during AutoInvoice Import

During a run of the Import AutoInvoice program, AutoInvoice derives the accounting date to assign to transactions
using the following criteria:
• Does an accounting date exist for this transaction in the interface table?
• Does the transaction use rules?
• What is the seing of the Derive date option on the transaction source?
• What is the seing of the Accounting Date in a Closed Period option on the transaction source?
AutoInvoice derives the accounting date dierently depending on these criteria:

• Invoices without Rules
• Invoices with Rules
• Credit Memos
Note: If a transaction date is not passed for an invoice or debit memo, AutoInvoice uses the derived
accounting date as the transaction date.
Invoices without Rules

If an invoice doesn't use rules, AutoInvoice uses the following process to derive the accounting date:
1. AutoInvoice uses the accounting date in the interface table, if one exists and it is in an open or future enterable
period.
2. If no accounting date is provided in the interface table, and 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 as the
accounting date.
set Yes:
a. AutoInvoice uses the ship date in the interface table.
b. If the ship date does not exist, AutoInvoice uses the sales order date.
c. If the sales order date does not exist, AutoInvoice uses the value of the Default Date parameter.
4. If the derived accounting date for a transaction line exists but is in a Closed or Not Open period, and the
Accounting Date in a Closed Period option on the transaction source is set to Adjust, then AutoInvoice
automatically adjusts the accounting date to the rst accounting date in the next open or future enterable
period.
51
Invoices with Rules

If the invoice uses the In Advance invoicing rule:
• 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.
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.
Accounting Date Validation

AutoInvoice rejects lines using the following logic for accounting dates either passed by the user or derived by
AutoInvoice:
• Accounting period for the accounting date is not dened.

• Accounting date is in a Closed, Closed Pending, or Not Opened period, and the Accounting Date in a Closed
Period option on the transaction source is set to Reject. If the invoice uses the In Arrears invoicing rule, then
AutoInvoice only rejects lines that have an accounting date in a Closed period.
• Either the credit memo accounting date is earlier than the related invoice accounting date, or the credit memo
transaction date is earlier than the related invoice transaction date, or both.
52
Revenue Scheduling Rule Start Date Validation

AutoInvoice rejects lines for revenue scheduling rule start dates either passed by the user or derived by AutoInvoice
under these circumstances.
• If the invoice uses the In Advance invoicing rule, AutoInvoice rejects lines if either of these is true:
◦ Rule start date is in a Closed or Not Opened period and the Accounting Date in a Closed Period option
on the transaction source is set to Reject.
◦ Accounting period for the rule start date is not dened.
• If the invoice uses the In Arrears invoicing rule, AutoInvoice rejects lines if either of these is true:
◦ Rule start date results in an accounting date in a Closed period and the Accounting Date in a Closed
Period option on the transaction source is set to Reject.
◦ Accounting period for the accounting date is not dened.
Besides validating dates, AutoInvoice also rejects lines if:

• Revenue scheduling rule has overlapping periods.
• One or more accounting periods do not exist for the duration of the revenue scheduling rule.
Process CPQ Cloud Orders Using AutoInvoice

Oracle CPQ Cloud integrates with the Receivables Invoice Service to create and process Receivables transactions from
CPQ Cloud orders using AutoInvoice.
The quote-to-cash process includes these related operations in Receivables:

• Perform a credit check on the customer order.
• Create and transfer order lines to the AutoInvoice interface tables.
• Generate transactions using AutoInvoice.
• Generate credit memos using AutoInvoice for returns and canceled orders.
Customer Credit Check

If applicable, verify that the customer account has sucient credit to cover the order. If the credit authorization is
granted, then you can create and transfer order lines.
Create and Transfer Order Lines

Once the necessary credit authorization is received and the order is nalized, you can submit the order to Receivables
for invoicing using the Receivables Invoice Service.
You can submit these orders:

• Order lines with payment terms.
• Order lines for goods, services or subscriptions.
• One-time or recurring order lines.
A recurring order line includes the billing frequency (for example, monthly or quarterly), the amount to bill
for each billing period, and either the transaction start and end dates or the number of transaction periods.
53
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.
AutoInvoice and CPQ Cloud process order lines in this way:

1. AutoInvoice selects all eligible transaction lines and groups them into transactions according to the assigned
grouping rule.
2. After successful creation of transactions, AutoInvoice noties the CPQ Cloud callback service.
3. CPQ Cloud updates the status and invoice information of the applicable order lines.
4. Transaction lines that fail validation remain in the AutoInvoice interface tables. Use the AutoInvoice workbook
to correct errors and resubmit AutoInvoice.
Create and Generate Credit Memos

If necessary, you can cancel an existing order. Canceling an order generates a call to the Receivables Invoice Service
with a credit memo request. This creates credit memo lines in the AutoInvoice interface tables for the corresponding
invoice lines.
When canceling a recurring invoice:

1. Issue a credit memo line with identiers for the order and order line to identify the applicable invoices in
Receivables.
2. The Receivables Invoice Service updates the recurring bill plan information to indicate the order is canceled.
3. Run the Import AutoInvoice program to create and apply credit memos to the invoices already created in
Receivables.
4. The Receivables Invoice Service deletes future-dated invoice lines from the interface tables according to the
eective cancellation date.
Related Topics
How You Import Credit Card Transactions with Tokens

Use AutoInvoice to import credit card transactions with tokens. The credit card tokenization process makes use of a
third-party service provider to store the credit card information belonging to a transaction and replace it with a token.
You enable credit card tokenization in Oracle Payments. Credit card tokenization provides the essential information to
process a credit card transaction and can optionally contain authorization of the transaction. If the token doesn't include
authorization, then the authorization takes place in Payments after you generate the automatic receipts and create the
remiance.
Note: Credit card services are currently not available in Oracle Cloud implementations.
Tokenization Columns in the AutoInvoice Import Template

The AutoInvoice Import template contains columns, hidden by default, for credit card tokenization.
The following table provides the name and description of each of these columns:
54
Column Name Description
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.

Credit Card Expiration Date The credit card expiration date.

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 identies the credit card issuer, as dened 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 identier received from the tokenization service provider
Identier 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 Identier or the Credit
Card Voice Authorization Code column. If you provide values in both columns, the Credit Card Authorization
Request Identier takes precedence.
Import Credit Card Transactions with Tokens

To import credit card transactions with tokens:
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
AutoInvoice Interface Table RA_INTERFACE_LINES_ALL

This table stores the transaction header and line information of transactions imported using the AutoInvoice le-based
data import spreadsheet.
55
AutoInvoice uses Transaction Flexelds to uniquely identify each transaction that you import into Receivables.
AutoInvoice always uses the Line Transaction Flexeld 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 specic 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 dened 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 seing 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.
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
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 seing 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 specic 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 specic line, you must enter a value
in this column.
If LINE_TYPE = CHARGES, do not 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
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 seing 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 seing 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 verication code provided by the Payments Server.
Validation
None.
58
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 Flexeld aribute information for this transaction.
Descriptive Flexeld aributes allow you to store additional columns, the contents of which you dene. 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 Flexeld columns.
ATTRIBUTE_CATEGORY
Enter the Invoice Line Information Flexeld category information for this transaction.
Descriptive Flexeld categories allow you to store dierent categories of aributes. This column is optional.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.ATTRIBUTE_CATEGORY
59
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 specic 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
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
If LINE_TYPE = TAX or you are passing freight for a specic 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.
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
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, this column is optional. Depending on the seing 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 specic 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.
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.
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
CUST_TRX_TYPE_ID
Enter the transaction type ID for this transaction.
This column is optional. Depending on the seing 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 seing 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
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.
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 classication code for the transaction line.
65
The document scal classication 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.
For credit memos, do not enter a value in this column. AutoInvoice uses the FOB point from the transaction you are
crediting.
66
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.
If LINE_TYPE = TAX or FREIGHT, 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 Flexeld aribute information for the Transaction Information Flexeld. Descriptive Flexeld aributes
let you store additional columns, the contents of which you dene.
If LINE_TYPE = LINE, CHARGES, or you are passing header freight, these columns are optional.
If LINE_TYPE = TAX or FREIGHT, do not enter values in these columns.
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 Flexeld columns.
67
HEADER_ATTRIBUTE_CATEGORY
For the Transaction Information Flexeld, enter Descriptive Flexeld aribute category information which is shared
between this transaction and other transactions. Descriptive Flexeld categories allow you to store dierent categories
of aributes.
If LINE_TYPE = TAX or you are passing freight for a specic line, do not enter values in these columns.
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.ATTRIBUTE_CATEGORY
HEADER_GDF_ATTRIBUTE1-30
Reserved for country-specic functionality.
Validation
Performed by Global Financials.
Destination
RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE1-30
HEADER_GDF_ATTR_CATEGORY
Validation
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
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 Flexeld for this transaction. The Line Transaction Flexeld is a combination of aribute
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
aributes.
Receivables copies the Line Transaction Flexeld to the Invoice Transaction Flexeld. When you import transactions
with multiple lines using AutoInvoice, the aributes of the rst line from the ordered lines appear in the Invoice
Transaction Flexeld.
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 Flexeld is the same as the Line Transaction Flexeld.
Validation
Must not already exist together with INTERFACE_LINE_CONTEXT in RA_INTERFACE_LINES_ALL and
RA_CUSTOMER_TRX_LINES_ALL. All enabled aributes for a given INTERFACE_LINE_CONTEXT must have values.
Dierent aribute 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
your imported invoices, do not include newline or carriage return characters (chr(10) or chr(13)) in these Descriptive
Flexeld columns.
INTERFACE_LINE_CONTEXT
This is a required column in AutoInvoice. Enter the context of the Line Transaction Flexeld 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
Validation
None.
Destination
INTERFACE_LINE_ID
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
INTERNAL_NOTES
Enter internal notes for this transaction.
If LINE_TYPE = TAX or you are passing freight for a specic 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 seing 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 specied Segment on
the transaction source, AutoInvoice enters a corresponding ID in this column.
If LINE_TYPE = TAX or FREIGHT, do not enter a value 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 seing of the Invoicing
Rule option (Value, ID, None) in the Import Information section of the transaction source. If you specied Value on the
transaction source, AutoInvoice enters a corresponding ID in this column.
71
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 seing 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 specic 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.
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
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
Validation
Destination
RA_CUSTOMER_TRX_LINES_ALL.GLOBAL_ATTRIBUTE1-20
LINE_GDF_ATTR_CATEGORY
Validation
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 identies situations where the intended use of the product is a factor either in tax
determination or the tax recovery rate.
Validation
None.
73
Destination
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 Flexeld aribute 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 specic line, you must enter a value. Use link-to-line aributes to
associate this tax or freight line to another transaction line in RA_INTERFACE_LINES_ALL. All tax lines and freight for
specic lines must be associated with a line that has a LINE_TYPE of LINE. Enter the same combination of aribute
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
Destination
None.
LINK_TO_LINE_CONTEXT
Enter the context name of the Transaction Flexeld 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 seing
of the Memo Line Rule option (Value or ID) in the Import Information section of the transaction source, you can enter
75
a value either in this column or in the MEMO_LINE_NAME column. If you specied Value 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 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.
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.
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.
AutoInvoice populates the column RA_CUSTOMER_TRX_LINES_ALL.MOVEMENT_ID with

RA_INTERFACE_LINES_ALL.MOVEMENT_ID and updates MTL_MOVEMENT_STATISTICS with transaction information
(for example, customer_trx_id, batch_id, customer_trx_line_id).
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.MOVEMENT_ID
76
MTL_SYSTEM_ITEMS_SEG1-20
Assign a System Item Flexeld value for each segment you enable in Receivables. For example, if you enable six System
Item Flexeld 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 seing 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.
If LINE_TYPE = TAX or FREIGHT, do not enter values in these columns.
For credit memos, do not enter values in these columns. AutoInvoice uses the values from the transaction you are
crediting.
For debit memos, do not enter values in these columns.
Validation
Valid combination of System Item Flexeld 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 prole option.
Destination
None.
ORIGINAL_GL_DATE
Stores the value of the GL_DATE column before AutoInvoice modies the accounting date. This column is used by
AutoInvoice and should not be populated by the user.
Validation
None.
Destination
None.
77
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 specied, 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.
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 specied Value on the
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
If no default remit-to address is specied, 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.
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.
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.
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 specied Value on the
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.
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.
79
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.
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 specied Value on the
For credit memos, you must enter the bill-to customer ID or the bill-to customer reference of a related customer of the
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
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.
For credit memos, you must enter the bill-to customer reference or the bill-to customer ID of a related customer of the
Validation
Must exist in HZ_CUST_ACCOUNTS.ORIG_SYSTEM_REFERENCE.
Destination
None.
80
ORIG_SYSTEM_SHIP_ADDRESS_ID
Enter the ship-to customer address ID for this transaction.
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 specied Value on the
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
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.
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.
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
HZ_CUST_SITE_USES.SITE_USE_CODE = SHIP_TO.
Destination
None.
81
ORIG_SYSTEM_SHIP_CONTACT_ID
Enter the ship-to contact ID for this transaction.
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 specied Value on the
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.
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.
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
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 specied Value on the
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to customer from the transaction you
are crediting.
Validation
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
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.
For credit memos, do not enter a value in this column. AutoInvoice uses the ship-to customer from the transaction you
are crediting.
Validation
Destination
None.
ORIG_SYSTEM_SOLD_CUSTOMER_ID
Enter the sold-to customer ID for this transaction.
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 specied Value on the
For credit memos, do not enter a value. AutoInvoice uses the sold-to customer from the transaction you are crediting.
83
Validation
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
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.
For credit memos, do not enter a value. AutoInvoice uses the sold-to customer from the transaction you are crediting.
Validation
Destination
None.
OVERRIDE_AUTO_ACCOUNTING_FLAG
This column controls whether the code combination ID of the Accounting Flexeld for this accounting distribution,
populated by the feeder system, should override AutoAccounting.
Populate this column for invoices and credit memos.
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
Validation
Must exist in AR_RECEIVABLE_APPLICATIONS_ALL.PAYMENT_SET_ID.
Destination
RA_CUSTOMER_TRX_LINES_ALL.PAYMENT_SET_ID
PAYING_CUSTOMER_ID
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PAYING_CUSTOMER_ID
PAYING_SITE_USE_ID
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
For credit memos, AutoInvoice enters a value in this column using RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID.
85
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 seing of the Salesperson option
(Number or ID) in the Import Information section of the transaction source. If you specied Number on the transaction
source, AutoInvoice enters a corresponding ID 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 seing of the Salesperson option (Number or ID) in
the Import Information section of the transaction source.
Validation
Must exist in RA_SALESREPS.SALESREP_NUMBER.
Destination
None.
PRINTING_OPTION
Enter the printing option for this transaction.
86
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.
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
PRODUCT_FISC_CLASSIFICATION
Enter the product scal classication code of the inventory item on the transaction line.
The product scal classication is used to classify inventory items that have a tax requirement for tax determination or
tax reporting purposes.
Validation
None.
Destination
PRODUCT_TYPE
Enter the product type code of the inventory item. Valid values are GOODS and SERVICES.
Validation
None.
87
Destination
PURCHASE_ORDER
Enter the purchase order number for this transaction.
For credit memos, do not enter a value in this column. AutoInvoice uses the purchase order number from the
Validation
None.
Destination
RA_CUSTOMER_TRX_ALL.PURCHASE_ORDER
PURCHASE_ORDER_DATE
Enter the date of the purchase order for this transaction.
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.
For credit memos, do not enter a value in this column. AutoInvoice uses the purchase order revision from the
88
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.
For debit memos, if LINE_TYPE = CHARGES, set quantity to 1.
For credit memos, if LINE_TYPE = CHARGES, set quantity to 1 or -1.
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 specic line, this column is optional.
If LINE_TYPE = TAX or you are passing freight for a specic 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
Destination
RA_CUSTOMER_TRX_LINES_ALL.QUANTITY_ORDERED
REASON_CODE
Enter the reason code for this transaction.
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 specied Value on the transaction source,
For credit memos and on-account credits, this column is optional.
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.
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.
For credit memos and on-account credits, this column is optional.
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.
of the Payment Method Rule option (Value or ID) in the Import Information section of the transaction source, you can
90
enter a value either in this column or in the RECEIPT_METHOD_NAME column. If you specied Value on the transaction
source, AutoInvoice enters a corresponding ID in this column.
AutoInvoice selects a receipt method using the following hierarchy:

1. Primary receipt method of the parent primary bill-to site.
2. Primary receipt method of the parent customer.
3. Primary receipt method of the bill-to site.
4. Primary receipt method of the bill-to customer.
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.
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.
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 Flexeld 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 Flexeld 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 Flexeld of the
freight line you are crediting in these columns or the RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID of the
91
transaction freight line you are crediting in RA_INTERFACE_LINES_ALL.REFERENCE_LINE_ID. Otherwise, do not enter
values in these columns.
For on-account credits, 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 Flexeld 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 Flexeld 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 Flexeld 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 Flexeld in the REFERENCE_LINE_ATTRIBUTE1-15 columns. Otherwise, do not enter a value in this column.
For on-account credits, 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
RELATED_BATCH_SOURCE_NAME
Enter the name of the transaction source of the document to which this transaction is related.
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.
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.
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.
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.
93
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.
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
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.
For credit memos, 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
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.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.RULE_END_DATE
SALES_ORDER
Enter the sales order number for this transaction.
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.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order date from the transaction you
are crediting.
Enter the date of the revenue order for this transaction.
For credit memos, do not enter a value in this column. AutoInvoice uses the revenue order date from the transaction
you are crediting.
95
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_DATE
SALES_ORDER_LINE
Enter the sales order line number for this transaction.
For credit memos, do not enter a value in this column. AutoInvoice uses the sales order line number from the
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_LINE
SALES_ORDER_REVISION
Enter the sales order revision for this transaction.
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.
96
For credit memos, do not enter a value in this column. AutoInvoice uses the source of the sales order from the
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.SALES_ORDER_SOURCE
SALES_TAX_ID
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.
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
Destination
RA_CUSTOMER_TRX_ALL.SHIP_DATE_ACTUAL
SHIP_VIA
Enter the ship_via code for this transaction.
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 aributes 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.
If LINE_TYPE = CHARGES or FREIGHT, do not enter a value in this column.
If LINE_TYPE = LINE, this column is optional.
If LINE_TYPE = TAX, this column is required.
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
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 prole 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 seing
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 certicates 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.
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 seing of the Memo Reason option (Value or ID) in the Import Information section of the transaction
99
source, you must enter a value either in this column or in the TAX_EXEMPT_REASON_CODE_MEANING column. If you
specied Value on the transaction source, AutoInvoice enters a corresponding ID 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 seing 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.
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 = LINE, CHARGES, or FREIGHT, do not enter a value in this column.
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 specic 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
TAX_RATE
Enter the tax rate for this tax line.
If LINE_TYPE = LINE, CHARGES, or FREIGHT, do not enter a value in this column.
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.
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 specied Value on the transaction source, AutoInvoice
enters a corresponding ID 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.
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.
101
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
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
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.
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.
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
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.
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.
Validation
None.
Destination
RA_CUSTOMER_TRX_LINES_ALL.UNIT_SELLING_PRICE
UNIT_STANDARD_PRICE
Enter the standard price per unit for this transaction.
104
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-dened scal classication code for the transaction line.
Use the user-dened scal classication code to classify any tax requirement that you cannot dene using existing scal
classication 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
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 identies 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.
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
AutoInvoice Interface Table RA_INTERFACE_SALESCREDITS_ALL

This table stores sales credit information for transactions. This table must be populated if AutoAccounting derives
segment values based on Salesperson. If AutoAccounting does not depend on Salesperson, then the seings of
106
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 seing 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 Flexeld aribute information for this sales or revenue credit assignment. Descriptive Flexeld
aributes allow you to store additional columns, the contents of which you dene. These columns are optional.
Validation
None.
Destination
RA_CUST_TRX_LINES_SALESREPS_ALL.ATTRIBUTE1-15
ATTRIBUTE_CATEGORY
Enter the Descriptive Flexeld category information for this sales credit assignment. Descriptive Flexeld categories
allow you to store dierent categories of aributes. This column is optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.ATTRIBUTE_CATEGORY
Enter the same Transaction Flexeld 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 aribute you enabled.
107
Enter the context name of the Transaction Flexeld 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
RA_INTERFACE_SALESCREDITS_ALL.INTERFACE_LINE_ATTRIBUTE1-15.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.CUSTOMER_TRX_LINE_ID
INTERFACE_SALESCREDIT_ID
sequence RA_CUST_TRX_LINE_SALESREPS_S.
Validation
None.
Destination
RA_CUST_TRX_LINE_SALESREPS_ALL.CUST_TRX_LINE_SALESREP_ID
INTERFACE_STATUS
Validation
None.
108
Destination
None.
LAST_UPDATE_LOGIN
the RA_INTERFACE_SALESCREDITS_ALL table for processing.
Validation
None.
Destination
None.
REQUEST_ID
Validation
None.
Destination
None.
SALES_CREDIT_AMOUNT_SPLIT
Enter the sales credit amount for this salesperson. This column is optional. Depending on the seing 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 specied 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 seing of the Sales
Credit option (Amount or Percent) in the Import Information section of the transaction source, you must enter either a
109
percentage in this column or an amount in the SALES_CREDIT_PERCENT_SPLIT column. If you specied 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
seing 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 specied Value in the
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
seing 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
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 seing 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 specied Number in the transaction source,
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 seing 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.
AutoInvoice Interface Table RA_INTERFACE_DISTRIBUTIONS_ALL

This table stores accounting distributions for transactions created by AutoInvoice.
AutoInvoice doesn't require you to enter accounting distributions for your transactions. If you don't use
AutoAccounting, then you must manually enter accounting distributions for your transactions.
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
• If you enter a percentage, AutoInvoice requires that the distribution percentages add up to 100 for each
account class that you pass.
Distributions in RA_INTERFACE_DISTRIBUTIONS_ALL are linked to the appropriate transaction lines in

RA_INTERFACE_LINES_ALL from the transaction exeld. Though the distribution for the REC account class is at the
invoice level, it may be linked to any transaction line of the invoice in RA_INTERFACE_LINES_ALL. AutoInvoice will then
correctly transfer all distributions to RA_CUST_TRX_LINE_GL_DIST_ALL.
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.
Do not enter a value in this column if either of these is true:

• This accounting distribution is for a transaction that uses a revenue scheduling rule.
• This accounting distribution is a receivables (REC) account. If this distribution is for a receivables account, you
must enter 100 in RA_INTERFACE_DISTRIBUTIONS_ALL.PERCENT.
112
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 Flexeld aribute information for this accounting distribution. Descriptive Flexeld aributes allow
you to store additional columns, the contents of which you dene. These columns are optional.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.ATTRIBUTE1-15
ATTRIBUTE_CATEGORY
Enter the Descriptive Flexeld category information for this accounting distribution. Descriptive Flexeld categories
allow you to store dierent categories of aributes. 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 Flexeld for this accounting distribution.
This column is optional. Depending on the value you selected for the Accounting Flexeld 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
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
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
Enter the same Line Transaction Flexeld for the transaction with which you want to associate this accounting
distribution. You must enter a value for each aribute you enabled for the Line Transaction Flexeld.
Validation
None.
Destination
None.
This is a required column in AutoInvoice. Enter the context of the Line Transaction Flexeld entered in the
INTERFACE_LINE_ATTRIBUTE1-15 column.
114
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
INTERFACE_LINE_ATTRIBUTE1-15 and INTERFACE_LINE_CONTEXT.
Validation
None.
Destination
RA_CUST_TRX_LINE_GL_DIST_ALL.CUSTOMER_TRX_LINE_ID
INTERFACE_STATUS
Validation
None.
Destination
None.
INTERIM_TAX_CCID
This column identies 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 Flexeld value for each segment you enable in Receivables. This exeld represents the Interim
(deferred) tax account. For example, if you enable six Accounting Flexeld 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
Depending on the value you selected for the Accounting Flexeld 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 Flexeld segment values must exist in GL_CODE_COMBINATIONS.
Destination
None.
LAST_UPDATE_LOGIN
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 specied 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
Validation
None.
116
Destination
None.
SEGMENT1-30
Enter an Accounting Flexeld value for each segment you enable in Receivables. For example, if you enable six
Accounting Flexeld 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 Flexeld 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 Flexeld segment values must exist in GL_CODE_COMBINATIONS.
Destination
None.
AutoInvoice Interface Table AR_INTERFACE_CONTS_ALL

This table stores information about contingencies that impact revenue recognition on imported transactions.
CONTINGENCY_ID
Identies the revenue contingency, according to this table:
Contingency Name Contingency ID
Explicit Acceptance 2

Customer Creditworthiness 3

Doubtful Collectibility 4

Extended Payment Terms 5

Cancellation 7

Fiscal Funding Clause 8

Refund 9
117
Contingency Name Contingency ID

Forfeitures 10

Leasing Doubtful Collectibility 12

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
Validation
None.
Destination
AR_LINE_CONTS_ALL.EXPIRATION_EVENT_DATE
INTERFACE_CONTINGENCY_ID
Contingency identier.
Validation
None.
Destination
None.
PARENT_LINE_ID
Identies 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.
AutoInvoice Interface Table RA_INTERFACE_ERRORS_ALL

This table stores information about interface lines that failed validation and were not imported into the Receivables
tables. AutoInvoice identies all errors for each transaction line, thus reducing multiple validation and correction cycles.
When you resubmit AutoInvoice, the program deletes the errors for each line selected for processing. When all of the
records have been successfully processed, AutoInvoice purges any remaining data in this table.
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
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
Destination
None.
MESSAGE_TEXT
The message text is stored in this column.
Validation
None.
Destination
None.
FAQs for Manage AutoInvoice

Why did AutoInvoice reject the invoice?
In most cases this is due to an invalid tax rate code.
If an invoice contains invalid lines, AutoInvoice creates an invoice from valid lines and rejects only the invalid lines.
However, if an invoice contains an invoice line with an invalid tax rate code, the entire invoice is rejected.
Why did AutoInvoice process fewer lines than were selected?

This happens when both a credit memo for an invoice and the invoice itself are part of the same submission.
If the credit memo is selected rst, then the credit memo goes unprocessed, without failure, because the invoice wasn't
yet processed. The unprocessed credit memo remains in the interface table and will be processed the next time you
submit the Import AutoInvoice program.
When does AutoInvoice purge processed data?

If the Purge interface tables Receivables system option is enabled, then the Purge AutoInvoice Interface Data program
runs automatically after AutoInvoice has validated and transferred data to Receivables.
If the Purge interface tables Receivables system option is not enabled, then you must submit the Purge AutoInvoice
Interface Data program manually to purge temporary data.
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.
How does AutoInvoice process recurring invoices?

During AutoInvoice processing, the program selects recurring invoice lines that have a transaction date on or before
the system date. Recurring invoice lines with a transaction date later than the system date remain in the interface tables
until the appropriate date arrives.
121
How can I authorize a credit card transaction with token?

You don't need to explicitly authorize a tokenized credit card transaction. If the tokenized credit card transaction was
imported without authorization, then the authorization takes place in Payments after you generate the automatic
receipts and create the remiance.
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 predened 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 predened 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 aachments:
• If the feature is enabled, a copy of the printed transaction is added to the transaction header as an aachment.
Use the Review Transaction page to view this printed copy.
• If the feature is enabled, aachments 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
Identies the order in which the selected transactions are printed:

• Transaction Number
122
• Customer
• Postal Code
Batch Name
Print transactions belonging to the specied transaction batch.
Transaction Class
Print transactions belonging to the specied transaction class only: Invoice, Credit Memo, Debit Memo, Chargeback.
Transaction Type
Print transactions belonging to the specied 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 classication 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 specied
print lead days on the payment terms, in which case the print date is the number of lead days before the transaction
due date.
Open Invoices Only
Specify whether to only print transactions with open debit items. The default is Yes.
Output File Type
Specify the output to use for the print run:

• HTML
• PDF
• Zipped PDFs: Includes an index le of the print run, to identify the rst and last page of each printed
transaction.
• Excel
[Transaction Class] Template Name
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.
Itemized Tax by Line
Specify whether to print itemized tax information for each transaction line.
123
Selected Template Headings

This table describes important template headings for printed transactions.
Heading Description
Bill-to The bill-to customer and address for this transaction.

Ship-to The ship-to customer and address for this transaction.

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.

Payments The total of all payments made against the transaction.

Credits The total of all credits applied to the transaction.

Financial Charges The total of all late and penalty charges applied to the transaction.

Due Date The date that payment is due.

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.

Salesperson The primary salesperson for this transaction.

Related Topics
• Print Bills Receivable Program and Report
124
How You Store Printed Transactions as Aachments

Store a copy of a printed or emailed transaction on the transaction itself as a permanent record of the original printed
document.
Create a Lookup Code

To use this feature, you must rst enable the storing of printed transactions by creating an
AR_STORE_PRINTED_TRANSACTIONS lookup code under the AR_FEATURES lookup type.
To create the lookup code:

1. Navigate to the Setup and Maintenance work area.
2. Search for the Manage Receivables Lookups setup task.
3. In the Manage Receivables Lookups page, search for the AR_FEATURES lookup type.
If the AR_FEATURES lookup type does not exist, create this lookup type using the Manage Standard Lookups
setup task.
4. In the Lookup Type: AR_FEATURES section, click the Plus (+) icon.
5. In the Lookup Code eld, enter AR_STORE_PRINTED_TRANSACTIONS.
6. In the Meaning eld, enter Store a printed copy of the transaction as an aachment.
7. In the Start Date eld, enter the date that this lookup code becomes active.
8. Ensure that you check the Enabled box.
9. Save your work.
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 aachment 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 aempts 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 aachments.
Use the Review Transaction page to open and review the printed document from the Aachments eld or Aachments
window. The Printed Transaction Copy aachment category is associated with each transaction stored as an
aachment.
Whenever you reprint a transaction, an additional reprinted transaction copy is stored as an aachment. Use the
Aachments window to review the date of each printed aachment.
Related Topics
• Overview of Lookups
• Example of a Standard Lookup
How To Print Transaction Aachments

You can use the Print Receivables Transactions process to print aachments to Receivables transactions along with the
transactions. You can print aachments belonging to your invoices, debit memos, credit memos, and chargebacks.
Note: You can only print aachments in PDF format that are aached to the transaction header.
125
Seings That Aect Printing Aachments with Transactions

Complete these seings to print aachments with transactions:
• Preferred Delivery Method: Set the Preferred Delivery Method eld to Paper or Email in the prole of each
customer account or site that you want to print aachments with customer transactions. The seing at the
account level aects all sites belonging to the customer account.
• Aachment Categories: In the Manage Aachment Categories page, create aachment categories for each
type of document that you want to aach to and print along with transactions. For example, you can create
aachment categories such as Item Descriptions, Explanation of Charges, Company Contacts, or Additional
Information.
Use these seings in the Manage Aachment Categories page for each aachment category you create:
◦ Category Name: For example, EXP_CHARGES
◦ User Name: For example, Explanation of Charges
◦ Module: Transactions (Module Key = FinArTransactionsMain)
◦ Description: For example, Document that explains the charges on transactions.
◦ Entity Name: RA_CUSTOMER_TRX_ALL
◦ Display Name: Transaction Header
• Lookup Type: In the Manage Standard Lookups page, create the lookup type to print aachment categories
called AR_PRINT_ATTACHMENT_CATEGORIES.
Use these seings in the Manage Standard Lookups page for the lookup type:
◦ Lookup Type: AR_PRINT_ATTACHMENT_CATEGORIES
◦ Meaning: Categories of Aachments to be Printed
◦ Description: Species the categories of aachments to be printed by the Print Receivables Transactions
process.
◦ Module: Transactions (Module Key = FinArTransactionsMain)
◦ Lookup Conguration Level: User
• Lookup Codes: Create lookup codes under the AR_PRINT_ATTACHMENT_CATEGORIES lookup type for each
aachment category that you created.
Use these seings for the lookup codes:
◦ Lookup Code: Aachment category name
Note: The aachment category name and lookup code must match exactly.
◦ Enabled: Yes
◦ Start Date: Date this lookup code is active.
◦ Meaning: User-dened explanation of the lookup code/aachment category.
◦ Description: Optional description of the lookup code/aachment category.
• Generate Bill: Set the Generate Bill option to Yes for all transactions that you want to print with their PDF
aachments.
126
How Aachments Are Printed

When you run the Print Receivables Transaction process, the process prints aachments to transactions that satisfy
these criteria:
• The aachment is in PDF format.
• The aachment is aached to the transaction header.
• The preferred delivery method seing on the related customer proles is Paper or Email.
• The aachment category is dened as an active lookup code of the AR_PRINT_ATTACHMENT_CATEGORIES
lookup type.
You print four invoices with the following aachments:

• Invoice 1000:
◦ Header level: Aachment A, PDF le, Category is Additional Information to Customer (category name
ADDITIONAL_INFO)
◦ Line level: Aachment B, PDF le, Category is Explanation of Charges (category name EXP_CHARGES)
• Invoice 1001:
◦ Header level: Aachment C, PDF le, Category is Explanation of Charges (category name EXP_CHARGES)
◦ Line level: Aachment D, PDF le, Category is Customer Transactions
• Invoice 1002:
◦ Header level: Aachment E, PDF le, Category is Internal Notes
◦ Line level: Aachment F, PDF le, Category is Additional Information to Customer (category name
ADDITIONAL_INFO)
• Invoice 1003:
◦ Header level: Aachment G, .txt le, Category is Additional Information to Customer (category name
ADDITIONAL_INFO)
A run of the Print Receivables Transactions process will print the four invoices with the following aachments:
• Invoice 1000 with Aachment A
• Invoice 1001 with Aachment C
• Invoice 1002 with no aachment
• Invoice 1003 with no aachment
Related Topics
• Aachments
• Overview of Lookups
Balance Forward Billing

Overview of Balance Forward Billing
Use balance forward billing to consolidate the open transactions belonging to a customer account or customer site into
a single bill that you send on a regular basis, instead of sending a separate invoice for each individual transaction.
127
Considerations for balance forward billing include:

• Balance Forward Bill Details
• Balance Forward Billing Cycles
• Bill Consolidation at Account or Site Level
• Balance Forward Bill Number
Balance Forward Bill Details

A balance forward bill contains:
• Beginning balance or the balance carried over from the last billing period.
• Itemized list of current charges and activities (such as invoices, credit memos, debit memos, adjustments) in
either summary or detail format.
• Payment received during the last billing period.
• Current total outstanding balance.
Note: You can't update transactions that are included on a balance forward bill, regardless of the seing 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.
Balance Forward Billing Cycles

Assign balance forward billing cycles to generate balance forward bills on a weekly, monthly, bimonthly, quarterly,
yearly, or even daily basis. You can either create these billing cycles in Receivables or maintain them in external feeder
systems.
Bill Consolidation at Account or Site Level

You can generate bills consolidated at either the customer account or site level:
• Account-level balance forward billing lets you generate one bill for each business unit of the customer account,
addressed to the primary bill-to site of the account.
• Site-level balance forward billing lets you generate a balance forward bill for each bill-to site of a customer
account that has multiple bill-to sites.
You can exclude a site from a balance forward bill by disabling balance forward billing on the customer prole
of the site.
Balance Forward Bill Number

When you print a draft or nal balance forward bill, the program generates a unique balance forward bill number and
assigns this number to each transaction on the bill. You can use the balance forward bill number to:
• Query transactions that are included in a balance forward bill.
• Accept a nal balance forward bill.
• Optionally reprint a draft or nal balance forward bill.
• Apply payment against the transactions in a balance forward bill.
Related Topics
• What's a balance forward billing cycle
128
How Transactions for Balance Forward Billing Are Selected

Use the Create Balance Forward Bill program to generate balance forward bills. The steps in this topic illustrate how the
Create Balance Forward Bill program selects transactions for inclusion on a balance forward bill.
Seings That Aect the Inclusion of Transactions on Balance Forward Bills

You must select a billing cycle and a currency for a balance forward bill.
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 aached 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 dierent 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.
How Transactions Are Selected

The Create Balance Forward Bill program selects transactions for inclusion on a balance forward bill using this
sequence:
1. Determine the payment terms:
a. Use the balance forward billing payment terms selected, if applicable.

b. If no payment terms were selected, use all balance forward billing payment terms that match the selected
billing cycle.
2. Determine the customers:
a. Use the customer or customers selected, if applicable.

b. If no customers were selected, select all applicable customers. This includes:
• Customers that have balance forward billing enabled.

• Customers that have the selected payment terms at the account or site level.
• Customers with a scheduled billing date that is earlier than or equal to the submission date.
The program checks payment terms belonging to the account prole for customers enabled for account-
level balance forward billing, and belonging to the site prole (or account prole if no payment terms are
specied 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.
3. Select transactions of the specied customers:
◦ Include all transactions that have the selected payment terms.

◦ Include all transactions that were not included on a previous balance forward bill.
◦ Exclude all transactions that have the Print Option set to Do Not Print.
129
◦ Exclude all transactions with a bill type of Imported.

4. Validate transactions:
◦ Verify the balance forward payment terms on the transaction.

◦ Verify that the transaction billing date is equal to or earlier than the balance forward bill billing date.
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.
Example of Creating a Balance Forward Bill

This example demonstrates how to create, update, and deliver a balance forward bill.
This example shows how to create a balance forward bill and then print the bill with a monthly billing cycle in draft
mode. After reviewing the draft bill, you remove incorrect transactions and update the customer seings to allow new
transactions to be selected, if applicable for the billing cycle.
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 conrm 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.
Create a Draft Balance Forward Bill

1. Run the Create Balance Forward Bill process.
2. Complete the process parameters as shown in this table:
Parameter Value
Print draft balance forward bills

Print Option
Monthly
Billing Cycle
Yes
Print Output
USD
Currency
3. Review the draft balance forward bill.
130
4. If the bill is correct, you can do either of the following:

◦ Run the Create Balance Forward Bill process again using the Print Option of Print nal balance forward
bills.
◦ Run the Conrm Balance Forward Bill process using the Conrm Option of Accept draft balance
forward bills.
You can print conrmed balance forward bills at a later time using the Print Balance Forward Bill process.
Update the Balance Forward Bill

A draft balance forward bill may contain transactions that don't belong on the bill, or it may not contain transactions
that you expect to see on the bill. Along with the parameters you select for a run of the Create Balance Forward Bill
process, the seings of the prole assigned to each customer determine which transactions are selected for inclusion
on the bill.
These customer prole seings aect 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 prole 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 prole.
1. Review the draft balance forward bill, and review the parameter values that you entered to conrm that they are
correct.
2. If the bill is not correct, run the Conrm Balance Forward Bill process to reject the draft bill.
3. Complete the process parameters as shown in this table:
Parameter Value
Reject draft balance forward bills

Conrm Option
The number of the draft balance forward bill

Bill Number
4. For each applicable customer account or customer site, conrm the prole seings for balance forward billing.
5. If the Override Terms option on the customer prole 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
Related Topics
• Balance Forward Billing on Customer Accounts and Sites
How You Use Imported Billing Numbers with AutoInvoice

An imported billing number groups invoices imported using AutoInvoice into a consolidated bill using your own format.
You supply the value for the billing number and then create your own consolidated bill format for these invoices.
Unlike balance forward billing, the imported billing number lets you consolidate invoices that have dierent values for
key aributes into one bill. These key aributes are payment terms, receipt methods, payment details, purchase order
numbers, and invoicing rules.
How To Prepare AutoInvoice to Use the Imported Billing Number

To prepare AutoInvoice for using the imported billing number, ensure that you complete these activities:
1. Create an Import prole class with these balance forward bill seings:
◦ Balance forward billing is enabled.
◦ Bill Level is Site.
◦ Bill Type is Import.
Assign this prole class to all applicable customers.
2. Populate the CONS_BILLING_NUMBER column in the RA_INTERFACE_LINES table.
When you run AutoInvoice, this groups all invoices under the same bill that have the same customer bill-to
address.
Validation of the Imported Billing Number

When you enter an imported billing number, AutoInvoice validates all of the invoices imported using this billing number
under a single bill.
During validation AutoInvoice checks each invoice to ensure that:

• Imported billing number is unique for the given business unit.
• All invoices have the same customer bill-to address.
If any single invoice from the group fails validation, then all of the invoices belonging to the bill are rejected.
Related Topics
• Why did AutoInvoice create transactions with duplicate transaction numbers
• Why did AutoInvoice reject transactions
FAQs for Present Bill

How do I manage templates for printing transactions?
Use Business Intelligence (BI) Publisher to manage the predened print templates for printing Receivables transactions
and balance forward bills.
There are seven print templates, one for each transaction class and two for balance forward bills:
• Invoice
• Credit Memo
132
• 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 reect your current organization logo.
• Add or remove aributes to and from the template according to your requirements.
• Set your template as the default template in BI Publisher.
There are two predened data models:

• Oracle Receivables - Header view and Line view
• Oracle Receivables Balance Forward - Header view, Summary Billing Lines view and Detail Billing Lines view
The data models provide the source data that is displayed on printed transactions. You can't modify the data models.
How can I change a customer's billing cycle?

Change the payment terms assigned to the customer prole to another balance forward billing payment terms. Future
transactions inherit the new payment terms.
How do I print transactions?

Use the Print Receivables Transactions process to schedule print runs of transactions and balance forward bills
according to the needs of your enterprise. When you schedule a print run, this both marks each transaction, or each
transaction in a balance forward bill, as printed and generates the printed document according to the template assigned
to the transaction.
It is not recommended to print transactions and balance forward bills directly from BI Publisher, because BI Publisher
does not mark transactions as printed. If a printed transaction is not marked as printed, then users can still make
changes to the transaction.
You can use the View Print buon 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.
How can I order names and numbers on searches and selections?

Search and selection ranges and parameters in Receivables use alphanumeric character ordering to determine the order
in which to consider names and numbers. The alphanumeric character ordering is: 1 - 9, followed by A - Z, followed by a
- z.
When you enter an alphanumeric range, such as in report parameters, Receivables does not compare each number as
a whole when determining the range of data to display, but instead compares the rst digit in each entered parameter
value, and then the next digit, and so on.
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
Process Billing Adjustments

How Adjustments to Transactions Are Calculated
Create adjustments to increase or decrease the balance due on an invoice, debit memo, or chargeback. For example,
after receipt application an invoice has an open balance of two dollars. You can create an adjustment for the remaining
amount and close the debit item.
Seings That Aect Adjustments

These seings aect the creation and update of adjustments:
• Adjustment types: The adjustment type determines what part of the invoice is adjusted: Invoice (entire invoice
amount); Line; Charges (late charges and penalties); Tax; Freight.
• Receivables activity: The Receivables activity determines the transaction distribution account to use for the
expense or revenue generated by the adjustment.
• Natural Application and Overapplication rules: The seings for these rules on the transaction type determine
whether an adjustment must make the balance due zero, or whether an overapplication is allowed. If the
transaction type doesn't allow overapplication, you can't enter an amount that would reverse the sign of the
balance of the debit item.
• Approval limits: If the adjustment amount is within your approval limits for the currency of the item, the
adjustment is approved and the customer balance updated. If the adjustment amount is outside your approval
limits for the currency of the item, the adjustment is set to the status Pending Approval until someone with the
appropriate approval limits either approves or rejects the adjustment.
• Invoices with Unconrmed Receipts prole option: You can adjust invoices selected for automatic receipt
application if this prole option is set to Adjust or Adjust and Credit.
• Override Adjustment Activity Account Allowed prole option: If this prole option is set to Yes, you can
update the default transaction distribution account determined by the Receivables activity.
• Adjustment Reason Required prole option: If this prole option is set to Yes, you must enter a reason for the
adjustment.
How Adjustments are Calculated

The calculation for each adjustment type is as follows:
• Invoice: Apply the adjusted amount to the entire invoice, or to the installment you are updating if the
transaction has multiple installments.
You must enter an amount large enough to close the item you are adjusting. If the Allow Overapplication
option on the transaction type is set to Yes, you can enter an amount greater than the balance due.
• Line: Apply the adjusted amount to the invoice lines. The adjusted amount is prorated across all lines. If the
adjustment includes tax, the amount is prorated across lines and tax.
• Charges: Apply the adjusted amount to the charges amount on the invoice. If the adjustment includes tax, the
amount is prorated across charges and tax.
• Tax: Apply the adjusted amount to the tax amount.
• Freight: Apply the adjusted amount to the freight amount.
134
Related Topics
• Natural Application and Overapplication
• Receivables Activity Types
Automatic Adjustments to Receivables Transactions

Use the Create Automatic Billing Adjustments process to automatically adjust the remaining balances of all open
invoices, debit memos, credit memos, and chargebacks.
When you run Create Automatic Billing Adjustments, the process:
• 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 specic 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.
How You Approve Adjustments to Receivables Transactions

Adjustments to transactions that are pending approval require review and further action by a user with the necessary
approval limits.
You can perform these actions on pending 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
Note: You can't approve a pending adjustment in either of these cases:

• Transaction associated with the adjustment is selected for automatic receipt creation and the Invoices with
Unconrmed Receipts prole option is set to Credit or None.
• Adjustment was already posted to the general ledger.
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
submied 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.
There are three revenue reversal rules:
• 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.
Split Term Methods on Credit Memos

If you are crediting a transaction that has multiple installments, you must select a split term method.
The split term method determines how to credit a transaction with multiple installments and species how the
installments are credited.
There are three split term methods:
• FIFO (First in First Out): This method reduces the remaining balance starting from the rst installment.
136
• 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).
How You Update Sales Credits on Credit Memo Lines

Review and update the default sales credits assigned to each credit memo line.
You can review and update the default salespersons and the default sales credits assigned to each salesperson. If
AutoAccounting depends on salesperson, you may need to rederive AutoAccounting during your updates.
Update the Default Sales Credits

If you are reviewing a credit memo against a specic invoice, Receivables derives the default sales credits from the sales
credit lines of the original invoice. If you are reviewing an on-account credit memo, all sales credits are assigned to the
primary salesperson.
You can perform these updates to default sales credits:

• Update the revenue or non-revenue allocations to existing salespersons by percentage or amount.
• Split the sales credit with one or more new salespersons. First update the sales credit percentage or amount
for the primary salesperson, then add a row for each new salesperson and enter the salesperson name and
percentage allocation.
• Change the primary salesperson.
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.
Choose Whether to Rederive AutoAccounting for Salespersons

If AutoAccounting depends on salesperson and you change the primary salesperson, Receivables asks if you want to
rerun AutoAccounting for this credit memo line.
If you click Yes:

• Receivables reruns AutoAccounting and updates the revenue accounts for this credit memo line.
• If you have already posted the credit memo account assignments, the original accounting entries and sales
credit record are not updated. Instead Receivables creates new accounting entries and sales credit records to
oset the original sales credit entries and to note the new ones.
• If AutoAccounting is dened for tax, unbilled, unearned, and AutoInvoice clearing accounts to use sales credits,
Receivables updates the classes associated with this credit memo line that are currently based on salesperson.
If you click No, Receivables does not run AutoAccounting, but does save your updates to sales credit information.
Related Topics
• Sales Credits and AutoAccounting
Manual Credit Request Workow Notications

The manual credit request workow notication process sends an email or online notication to each designated
approver.
137
The approver uses the notication window to review the credit request details, review and update credit request
information, and sign o on the review by clicking the Complete buon and sending the review to the next approver.
The approver uses the Review Credit Memo Request page, available from the notication window, to review transaction
and dispute information, update details of the credit request, and enter comments related to the review.
The notication 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 buon 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 predened template is used by default to present the workow notication. You can use Oracle
BI Publisher to copy and modify this template according to your business requirements and set the modied
template as the new default.
Review of Dispute and Collections Information on Receivables Transactions

Review and update information related to transactions under dispute, and review Collections installment and case folder
notes on transactions.
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.
To enter and manage a dispute:

1. In the Billing work area, open the Manage Transactions page.
2. Search for and select the transaction you want.
3. In the Review Transaction page, select Dispute Transaction from the Actions menu.
4. In the Manage Disputes page, select the section of the transaction to dispute and enter the dispute reason.
5. Optionally enable the Reverse applications and credit open balance option to initiate the Credit Memo Rebill
process. Use this option to credit the entire amount of the original invoice for rebill purposes.
The Credit Memo Rebill process reverses any receipts and adjustments against the original invoice and creates
a credit memo for the entire invoice amount.
138
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 buon 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.
Review Receivables and Collections Notes and Comments

When you submit a dispute, the dispute process creates a note that contains the Credit Memo Request Number
(Dispute Number), Dispute Amount, Credit Memo Reason, and your Internal Comments, and aaches this note to the
transaction under dispute.
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 specic transaction installments.
To review Collections notes on transactions:

2. Search for and select the transaction you want.
3. In the Review Transaction page, select Review Installments from the Actions menu.
4. In the Review Installments window, click the Notes icon on the installment you want.
5. In the Installment tabbed region of the Notes window, review any installment notes in the Note Text column.
6. Click the Case Folder tab.
7. In the Case Folder tabbed region of the Notes window, review any case folder notes in the Note Text column.
To review comments related to transactions under dispute:

2. Search for and select the original invoice transaction under dispute.
3. In the General Information section of the Review Transaction: Invoice page, click the Notes icon.
4. In the Notes window, click the Transaction tab and review the dispute comments for the original invoice in the
Note Text column.
5. Close the original invoice transaction.
6. In the Manage Transactions page, search for and select the credit memo created by the dispute for the original
transaction.
7. In the Review Transaction: Credit Memo page, click the Show More link.
8. Click the Miscellaneous tab.
9. Review the customer comments in the Comments eld.
Unapply Receipts During Credit Memo Request Approval

If the credit memo approval process approves a dispute amount greater than the open balance on the invoice, you can
set up the applied credit memo to automatically reverse existing receipt applications.
Use this procedure, for example, when an invoice was partially paid but the customer later disputes a portion of the
original invoice amount greater than the current open balance.
139
The credit memo approval process performs these steps:

1. Unapply one or more full or partial receipt amounts from the invoice to accommodate the approved credit
memo amount.
2. Create and apply the credit memo to close the invoice.
3. Reapply the receipts and place any remaining receipt amount on-account for the customer.
This process doesn't reverse other activity against an invoice, including adjustments and credit memos. If reversing
all available receipts and applying the approved credit memo still leaves a negative invoice balance, then the approval
process ends in error.
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 seings:
◦ Type: Manual
◦ Receipt Handling for Credits: On account
Note: You can also assign these seings to the predened transaction source Credit Memo.
2. In the transaction source assigned to the invoice, select the credit memo transaction source you created, or the
predened 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.
How Credit Memo Distributions Are Calculated

When you credit a transaction and create a credit memo, this assigns a revenue and tax account to each credit memo
line and generates the default distribution amount for each account assignment. Use the Distributions window to review
and update the account assignments for credit memo and tax lines.
If the transaction you are crediting has associated freight charges, you can also update credit memo freight
distributions, unless the credit memo transaction type has Allow Freight set to No or you have specied a standard
memo line of type Tax.
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 osets the original posted account assignment.
• The second assignment records the new amount or account that you have updated.
Seings and Documents That Aect Credit Memo Distributions

These seings and documents aect the calculation and display of credit memo distributions:
• AutoAccounting: Account assignments dier depending on whether AutoAccounting depends on salesperson
to determine the segment values.
140
• Invoice Accounting Used for Credit Memos prole option: If this prole 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 seing of the Invoice
Accounting Used for Credit Memos prole option.
• Credit memo revenue reversal rule: This rule aects account assignments on standard credit memos with
revenue scheduling rules.
How Credit Memo Distributions Are Calculated

AutoAccounting assigns a revenue and tax account to each credit memo line. The calculation of the default distribution
amount allocated to each account assignment varies depending upon the related documents and seings.
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 seing of the Invoice
Accounting Used for Credit Memos prole option:
• If the Invoice Accounting Used for Credit Memos prole 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 prole 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 prole option is set to Yes, and the transaction uses a
revenue scheduling rule, the default amount is calculated according to the seing 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
◦ Period 4 = $30
◦ Period 5 = $20
This table shows the accounting entries for invoice 102 over the ve accounting periods:
Account Debit Credit Accounting Date Period Status
Accounts Receivable 100.00 None 1/1/XX Open

Unearned Revenue 20.00 None 1/1/XX Open

Unearned Revenue None 100.00 1/1/XX Open

Revenue None 20.00 1/1/XX Open

Unearned Revenue 20.00 None 2/1/XX Not Open

Revenue None 20.00 2/1/XX Not Open







The examples describe four separate scenarios:
• Scenario 1: A full credit memo entered against the invoice.

• Scenario 2: A partial credit memo entered against the invoice, with the revenue reversal rule set to Prorate.
• Scenario 3: A partial credit memo entered against the invoice, with the revenue reversal rule set to LIFO.
• Scenario 4: A partial credit memo entered against the invoice on 6/1/XX, with the revenue reversal rule set to
UNIT.
142
Full Credit Memo

A full credit memo is entered on 2/15/XX against invoice 102 with these details:
• Credit memo date = 2/15/XX

• Credit memo amount = $100
This table shows the reverse accounting entries after the credit memo is applied:

Revenue 20.00 None 2/15/XX Open


Accounts Receivable None 100.00 2/15/XX Open



Revenue 10.00 None 3/1/XX Not Open

Unearned Revenue None 10.00 3/1/XX Not Open





Partial Credit Memo with Revenue Reversal Rule Prorate

A partial credit memo for $65 is entered on 2/15/XX against invoice 102. The details are:
• Revenue reversal rule = Prorate

143
This table shows the partial reverse accounting entries after the credit memo is applied, with the computations used to
derive the partial amounts:

(65/100) * ($100)

Revenue (65/100) * 13.00 None 2/15/XX Open

($20)


($20)





($10)


Revenue (65/100) * 19.50 None 4/1/XX Not Open

($30)


Revenue (65/100) * 13.00 None 5/1/XX Not Open

($20)


Partial Credit Memo with Revenue Reversal Rule LIFO

• Revenue reversal rule = LIFO

• Credit memo amount is fully applied by Period 2
144
This table shows the partial and full reverse accounting entries after the credit memo is applied:










Partial Credit Memo with Revenue Reversal Rule UNIT

A partial credit memo for $65 is entered on 6/1/XX for 8 units against invoice 102, assuming that this invoice consists of
10 units with a value of $10 each for a total of $100. The details are:
• Revenue reversal rule = UNIT
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:
Period Calculation Net Unit Price
Period 5 ($20-$0)/10 units $2
145

Period 4 ($30-$0)/10 units $3

Period 3 ($10-$0)/10 units $1

Period 2 ($20-$0)/10 units $2

Period 1 ($20-$0)/10 units $2

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 Amount to Credit Amount Credited (actual)
Period 5 $2 * 8 units $16




Period 1 $2 * 8 units $1 (balance of credit memo)

This table shows the partial reverse accounting entries after the credit memo is applied:




146








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.
• 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:
Unbilled Receivable 20.00 None 1/1/XX Open
147

Revenue None 20.00 1/1/XX Open

Unbilled Receivable 20.00 None 2/1/XX Not Open






Accounts Receivable 100.00 None 5/1/XX Not Open


Unbilled Receivable None 100.00 5/1/XX Not Open


The examples describe four separate scenarios:
• Scenario 1: A full credit memo entered against the invoice.

Prorate.
LIFO.
UNIT.
Full Credit Memo

A full credit memo is entered on 6/1/XX against invoice 103 with these details:

This table shows the reverse accounting entries after the credit memo is applied:
148
No Entries None None 1/1/XX Closed



Revenue (reverse 20.00 None 4/1/XX Open

Period 1 entry)


Period 2 entry)


Period 3 entry)


Period 4 entry)

Unbilled Receivable None 20.00 4/1/XX Open





Period 5 entry)



(reverse original
receivable)


Partial Credit Memo with Revenue Reversal Rule Prorate

• Revenue reversal rule = Prorate
149

This table shows the partial reverse accounting entries after the credit memo is applied, with the computations used to
derive the partial amounts:




($20)


($20)


($10)


($30)






($20)




150
Partial Credit Memo with Revenue Reversal Rule LIFO

• Revenue reversal rule = LIFO

This table shows the partial and full reverse accounting entries after the credit memo is applied:













151
Partial Credit Memo with Revenue Reversal Rule UNIT

A partial credit memo for $40 is entered on 6/1/XX for 8 units against invoice 103, assuming that this invoice consists of
10 units with a value of $10 each for a total of $100. The details are:
• Revenue reversal rule = UNIT

• Last Period to Credit = last period of the invoice
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:
Period 5 ($20-$0)/10 units $2

Period 4 ($30-$0)/10 units $3

Period 3 ($10-$0)/10 units $1

Period 2 ($20-$0)/10 units $2

Period 1 ($20-$0)/10 units $2

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 Amount to Credit Amount Credited (actual)


This table shows the partial reverse accounting entries after the credit memo is applied:
152









Examples of Accounting for Credit Memos with Installments

These examples illustrate the accounting for a partial credit memo against an invoice with installments.

• Payment Terms = 3 Installments, as illustrated in this table:
Due Date Amount
2/1/XX $50

3/1/XX $25

4/1/XX $25

This table shows the payment schedules for these installments:
153
Due Date Original Amount Due Remaining Amount Due Total Amount Credited
2/1/XX $50 $50 $0

3/1/XX $25 $25 $0

4/1/XX $25 $25 $0

The examples describe three separate scenarios:
• 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.
• Scenario 3:
◦ A partial credit memo entered against the invoice with the split term method set to FIFO.
Partial Credit Memo with Split Term Method of Prorate

There are three transactions against invoice 104:
• 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:
• Split term method = Prorate

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
Due Date Calculation Amount Credited
2/1/XX $45/100 * $50 $22.50

3/1/XX $45/100 * $25 $11.25

4/1/XX $45/100 * $25 $11.25

This credit memo aects the payment schedules of invoice 104, as shown in this table:
2/1/XX $50 $27.50 $22.50

3/1/XX $25 $13.75 $11.25

4/1/XX $25 $13.75 $11.25

Transaction 2: On 1/15/XX a payment is received for $20. This payment aects the payment schedules of invoice 104, as
shown in this table:
Due Date Original Amount Due Remaining Amount Total Amount Payment Applied
Due Credited
2/1/XX $50 $7.50 $22.50 $20

3/1/XX $25 $13.75 $11.25 $0

4/1/XX $25 $13.75 $11.25 $0

Transaction 3: On 1/16/XX another credit memo for $20 is entered against invoice 104. The details are:

Due Credited
2/1/XX $50 $3.22 $26.78 $20
155
Due Credited

3/1/XX $25 $5.89 $19.11 $0

4/1/XX $25 $5.89 $19.11 $0

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.
Partial Credit Memo with Split Term Method of LIFO

• A partial credit memo for $45 with the split term method set to LIFO.
Transaction 1: On 1/1/XX a credit memo for $45 is entered against invoice 104. The details are:
• Split term method = LIFO
2/1/XX $50 $50 $0

3/1/XX $25 $5 $20

4/1/XX $25 $0 $25

Due Credited
2/1/XX $50 $30 $0 $20

156
Due Credited
3/1/XX $25 $5 $20 $0

4/1/XX $25 $0 $25 $0

Due Credited
2/1/XX $50 $15 $15 $20

3/1/XX $25 $0 $25 $0

4/1/XX $25 $0 $25 $0

Partial Credit Memo with Split Term Method of FIFO

• A partial credit memo for $45 with the split term method set to FIFO.
Transaction 1: On 1/1/XX a credit memo is entered against invoice 104. The details are:
• Split term method = FIFO
2/1/XX $50 $5 $45

3/1/XX $25 $25 $0

157
4/1/XX $25 $25 $0

Due Credited
2/1/XX $50 $0 $45 $5

3/1/XX $25 $10 $0 $15

4/1/XX $25 $25 $0 $0

Total $100 $35 $45 $20

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.

Due Credited
2/1/XX $50 $0 $45 $5

3/1/XX $25 $0 $10 $15

4/1/XX $25 $15 $10 $0

158
Reports for Process Billing Adjustments

Overview of the Adjustment Register
This topic contains summary information about the Adjustment Register.
Overview
The Adjustment Register provides information about approved adjustments that aect transaction balances.
Key Insights
Review both manual and automatic adjustments by customer, adjustment status, adjustment type, or adjustment
reason.

The following table lists frequently asked questions about the Adjustment Register.
FAQ Answer

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
FAQ Answer
What can I do with this report? Schedule to run as needed.



This report uses the Receivables - Adjustments Real Time subject area.
Adjustment Register
Use the Adjustment Register to review both manual and automatic approved adjustments that aect 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 specied 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.

Transaction Number The transaction number of the adjusted transaction.

Transaction Type The transaction type of the adjusted transaction.

Adjustment Number The adjustment number assigned to the transaction.

Adjustment Accounting Date The accounting date of the adjustment.

Adjustment Entered Amount The amount of the adjustment.

Entered Currency The entered currency of the adjustment.

Adjustment Accounted Amount The accounted amount of the adjustment in the ledger currency.
160

Adjustment Reason The reason for the adjustment.

Overview of the AutoAdjustment Preview Report

This topic contains summary information about the AutoAdjustment Preview Report.
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

The following table lists frequently asked questions about the AutoAdjustment Preview Report.
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.

What can I do with this report?

Set the AutoAdjustments Option parameter of the Create Automatic Billing Adjustments
program to Generate Report Only.

AutoAdjustment Preview Report

Use the AutoAdjustment Preview Report to review your potential transaction adjustments. The report is generated
after a run of the Create Automatic Billing Adjustments program with the AutoAdjustments Option parameter set to
Generate Report Only.
Note: This report is for automatic adjustments only. Use the Adjustment Register to review both manual and
automatic approved adjustments.
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 satised 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.
Customer Name The name of the customer on the transaction.

Number The account number of the customer on the transaction.

Transaction Number The original transaction number.

Transaction Type The transaction type for the transaction.
162

Due Date The due date for the transaction.

Adjustment Number The number assigned to the adjustment to the transaction.

Adjusted Amount The amount of the adjustment.

Balance Due The remaining balance due on the transaction after the adjustment.

Status The current status of 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.

Print Adjustments Program and Report

Use the Print Adjustments program to print adjustments to your transactions. The report provides a listing of
adjustments for review. The report lists each adjustment separately, with summary information about the adjustment
and the transaction that was adjusted.
This is a listing only. The report does not provide any amount or count totals.
Review this report to verify your transaction adjustment process.
Report Parameters
Order By
Arrange the information in the report by Adjustment Number, Customer, Postal Code or Transaction Number.
From/To Adjustment Number
Range of adjustment numbers to include in the report.
163
From/To Transaction Number
Range of transactions with adjustments by transaction number to include in the report.
Tax Registration Number
Conne the report to one customer tax registration number.
FAQs for Process Billing Adjustments

How can I credit a transaction that was already paid?
By unapplying the receipt that was previously applied to the transaction and creating a credit memo for the unapplied
amount. Use the Manage Receipt page to select and unapply the receipt application. You can then either place the
amount of the receipt on account for later reallocation to a dierent transaction, or send the customer a refund.
How can I credit only part of the balance due on a transaction?

Use the Transaction Amounts section of the Credit Transaction page to enter a partial credit amount or percentage
on line, tax, or freight. The amount or percentage entered is prorated across all respective lines of the credit memo.
Percentages are based on the original balance of the transaction being credited. Receivables updates the balance due
for each line that you credit and creates all of the accounting reversal entries. Receivables also reverses this percentage
of the sales revenue and non-revenue credits assigned to salespersons.
You can also credit individual transaction, tax, or freight lines. After you credit individual lines and return to the Credit
Transaction page, the table displays the results of all your line-level updates. If you again update line, tax, or freight in
the Transaction Amounts section, you must let Receivables rederive the line-level calculations.
How can I credit tax amounts?

If you enable the Automatically derive tax from lines option, then the amount or percentage credited to the
transaction line is credited to the tax line as well. This derived tax amount is a draft calculation only. If you want to
change the derived tax, you must enter any updates at the line level. After you save or complete, the tax engine
calculates the actual tax amount to be credited and updates the nal tax credit amount. You cannot edit the derived
value after you save or complete.
If you want to credit tax only, do not enable the Automatically derive tax from lines option. Leave the Line amount
blank or zero, and enter the tax percentage or amount to credit on the Tax line.
When do I credit and rebill a transaction?

Sometimes the simplest way to manage a transaction change is to credit and rebill. You credit the entire balance of
an invoice, duplicate the original invoice, and update the duplicate with the correct information, then resubmit to the
customer.
Common scenarios for credit and rebill include:
• A customer indicates that an invoice does not reect the correct price of a product or service. The customer
requests a new invoice with the correct information.
• A customer wants to correct accounting directly in the subledger, instead of making a manual journal entry in
general ledger. With credit and rebill, the credit memo reverses the accounting of the original invoice, and the
updated duplicate invoice creates new accounting for posting to general ledger.
• The customer wants to change the bill-to information on a posted transaction.
164
When do I create a debit memo?

Create a debit memo to reect a charge for an item that is not a standard invoice item. Debit memos often reect
updates or adjustments to existing transactions.
You create debit memos to:
• Enter a price correction to a line item or the tax calculation on an original invoice.
• Include a required charge missing from an original invoice, such as freight.
• Create a debit memo reversal to record the amount of the net of a closed debit and credit transaction after
reversing a receipt.
• Record late charges against a customer or customer site account.
If you record late charges as debit memos, the application creates one debit memo per overdue transaction.
Any penalties and late payment charges assessed appear as line items on the debit memo.
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 dierent numbering sequence for debit memos, you must set up and use a dierent transaction
source.
When do I enter a credit memo manually?

Once a disputed transaction or transaction amount receives all of the required approvals, the Credit Memo Creation
process creates the credit memo. If the process fails to create the credit memo, then you must enter the credit memo
manually. Reasons why the process might fail include missing setup steps, or the disputed transaction does not have
enough balance due remaining.
Use the information on the credit memo request to create the credit memo. After you create the credit memo, enter the
credit memo number into the notication and submit.
Can I unapply a standard credit memo?

Yes, you can unapply a standard credit memo and turn it into an on-account credit memo. When you unapply the
standard credit memo, enter an accounting date in an open or future-enterable period. Unapplying a standard credit
memo removes its debit items and reverses the accounting for the credit memo in the accounting period you specify.
If the Use Invoice Accounting For Credit Memos prole option is set to No, then you must enter a receivable account
when you unapply the credit memo. If the Use Invoice Accounting For Credit Memos prole option is set to Yes, then
no other action is required.
What is the credit memo request approval process?

The Credit Memo Request Approval process is managed by the Approval Management Extensions (AMX) to the human
workow services of Oracle SOA Suite. The approval process makes use of approval groups that contain either static or
dynamically generated lists of approvers.
An approval group consists of a name and a predened set of users congured to act on a task in a certain paern.
Approval groups are congured and managed with the Oracle BPM Worklist.
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 dened correctly.
• Conrm the members of the approval group.
165
• Conrm that, for credit memo requests, the appropriate rules are dened in the worklist.
Manage Transaction Information

Review of Transactions and Transaction Activities
Use the Manage Transactions page to view detailed or summary information about your invoices, credit memos, debit
memos, and chargebacks.
Along with standard search and display functions, you can perform these activities on selected transactions:
• Review Installments
• View Balance Details
• View Transaction Activities
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 prole 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.
View Balance Details

View complete information for a specic transaction, including the original transaction amount, the total amount of
payments against the transaction, any credits, refunds, adjustments, or charges applied to the transaction, and any
discounts taken.
The Balance Details window indicates the receipt, credit, or discount that was applied to the transaction, and the type
of adjustments that were created. For example, a single transaction might have two adjustments against it, one of type
Charges and another of type Freight. Similarly, the transaction might have one credit memo applied against it at the line
level and another at the tax level.
The Balance Details window displays the total amount of each action aecting a transaction in the Total column and
displays how the line, tax, freight, and charge balances were aected in the Balance row.
View Transaction Activities

View all activities that have taken place against a specic invoice, credit memo, or debit memo. You can drill down to
view the details of each activity.
There are three activity classes that identify activity against transactions:
• Payment: Any payment made against the transaction balance.
• Credit Memo: Any credit memo applied to the transaction.
• Adjustment: Any adjustment made to the transaction balance.
166
All amounts are in the currency of the particular activity.
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.
RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES tables

Important columns in the RA_CUSTOMER_TRX table include:
• CUSTOMER_TRX_ID column
• TRX_NUMBER column
• BILL_TO_CUSTOMER_ID column
• TRX_DATE column
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 seing. 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.
Important columns in the RA_CUSTOMER_TRX_LINES table include:

• CUSTOMER_TRX_LINE_ID column
• LINK_TO_CUST_TRX_LINE_ID column
167
• 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 identies 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.
RA_CUST_TRX_LINE_SALESREPS and RA_CUST_TRX_LINE_GL_DIST tables

Important columns in the RA_CUST_TRX_LINE_SALESREPS table include:
• CUST_TRX_LINE_SALESREP_ID column
• SALES_REP_ID column
• REVENUE_AMOUNT_SPLIT column
• NON_REVENUE_AMOUNT_SPLIT column
• PREV_CUST_TRX_LINE_SALESREP_ID 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 identies 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 specic 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.
Important columns in the RA_CUST_TRX_LINE_GL_DIST table include:

• CUST_TRX_LINE_GL_DIST_ID column
• CODE_COMBINATION_ID column
• ACCOUNT_CLASS column
• AMOUNT column
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 identies 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
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
• 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 identies 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:
TRANSACTION CLASS FOREIGN KEY TABLE
Invoices INV customer_ trx_id RA_ CUSTOMER_TRX

Debit Memos DM customer_ trx_id RA_ CUSTOMER_TRX

Credit Memos CM customer_ trx_id RA_ CUSTOMER_TRX

Chargebacks CB customer_ trx_id RA_ CUSTOMER_TRX

Receipts PMT cash_ receipts_id AR_ CASH_RECEIPTS

The status column identies 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
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 reected by the sum of the amount_due_remaining column for all conrmed payment schedules for a given
customer.
AR_ADJUSTMENTS table
Important columns in the AR_ADJUSTMENTS table include:
• ADJUSTMENT_ID column
• AMOUNT column
• TYPE 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_CREDIT_MEMO_AMOUNTS
Important columns in the AR_RECEIVABLE_APPLICATIONS table include:

• RECEIVABLE_APPLICATION_ID column
• AMOUNT_APPLIED column
• STATUS column
170
• 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.
Important columns in the AR_CREDIT_MEMO_AMOUNTS table include:

• CREDIT_MEMO_AMOUNT_ID column
• GL_DATE column
• AMOUNT column
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.
Important columns in the AR_CASH_RECEIPTS table include:

• AMOUNT column
• STATUS column
• RECEIPT_NUMBER column
• TYPE column
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 unidentied, and no customer balance was updated.
• UNAPP: The receipt customer was identied, but the receipt has neither been fully applied to a specic invoice
nor placed on account.
• APP: The entire amount of the receipt was either placed on account or applied to specic customer invoices.
• REV: The receipt was reversed.
• NSF: The receipt was reversed due to insucient funds.
• STOP: The receipt was reversed by a stop payment.
The type column identies 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
Important columns in the AR_CASH_RECEIPT_HISTORY table include:

• CASH_RECEIPT_HISTORY_ID column
• AMOUNT column
• STATUS column
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 conrmed by
the customer.
• REMITTED: This status is valid for both manual and automatic receipts, and indicates that the receipt was
remied.
• 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 seing the current_record_ag to NULL and by seing 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.
Important columns in the AR_MISC_CASH_DISTRIBUTIONS table include:

• MISC_CASH_DISTRIBUTION_ID column
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
Receivables Accrual Accounting Entries

Receivables creates default accounts for revenue, receivable, freight, tax, unearned revenue, unbilled receivable,
late charges, and AutoInvoice clearing (suspense) accounts using the information specied in the AutoAccounting
structure and the subledger accounting rules. You then submit the Create Receivables Accounting program to create
the accounting entries in Subledger Accounting.
172
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
• Remiances
• 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

None Tax (if you charge tax)

None Freight (if you charge freight)

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:
In the rst period of the rule:
Debit Credit
Unbilled Receivables None

None Revenue

In the second period of the rule:
Debit Credit
173
Debit Credit

None Revenue

In the third and nal period of the rule:
Debit Credit

None Revenue

Receivables None

None Unbilled Receivables



If you enter an invoice with an In Advance invoicing rule, Receivables creates the following journal entries:
In the rst period of the rule:
Debit Credit
Receivables None

None Unearned Revenue



Unearned Revenue None

None Revenue

174
In all periods of the rule for the portion that is recognized:
Debit Credit
Unearned Revenue None

None Revenue

Credit Memos and On-Account Credits

This section describes the default accounting entries for credit memos.
When you credit an invoice, debit memo, or chargeback, Receivables creates the following journal entry:
Debit Credit
Revenue None

Tax (if you credit tax) None

Freight (if you credit freight) None

None Receivables (Credit Memo)

Receivables (Credit Memo) None

None Receivables (Invoice)

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 prole option is set to Yes, Receivables credits the accounts of
the original transaction. If this prole 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
specied 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 oseing entry and the new entry.
If you unapply the standard credit memo, Receivables reverses the accounting entries and creates the following journal
entry:
175
Debit Credit
Receivables (Invoice) None

None Receivables (Credit Memo)

The standard credit memo is converted to an on-account credit memo.
If the Invoice Accounting Used for Credit Memos prole 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
Revenue (if you credit line amounts) None

Tax (if you credit tax) None

Freight (if you credit freight) None

None Receivables (On-Account Credit)

Receivables uses the freight, receivable, revenue, and tax accounts that you specied 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
Receivables (On-Account Credit) None


Receipts
This section describes the default accounting entries for receipts.
When you enter a receipt, Receivables creates the following journal entries:
176
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

Unapplied Cash None

None Unapplied Cash

None Receivables

Note: These examples assume that the receipt has a Remiance Method of No Remiance and a Clearance
Method of Directly.
When you enter an unidentied receipt, Receivables creates the following journal entry:
Debit Credit
Cash None

None Unidentied

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
Debit Credit

When your receipt includes a discount, Receivables creates the following journal entry:
Debit Credit
Cash None

None Receivables

Earned/ Unearned Discount None

None Receivables

Receivables uses the default cash, unapplied, unidentied, on-account, unearned, and earned accounts that you
specied under remiance 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

None Unapplied Cash

To close the receivable on the credit memo and increase the unapplied cash balance, Receivables creates the following
journal entry:
Debit Credit
Receivables None

None Unapplied Cash

When you enter a receipt and combine it with a negative adjustment, Receivables creates the following journal entries:
178
Debit Credit
Cash None


Write-O None


You set up a Write-O account when dening your receivables activity.
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
Unapplied Cash None

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
Debit Credit

Receivables (Chargeback) None

None Chargeback (Activity)

Chargeback (Activity) None


You set up a Chargeback account when dening your receivables activity.
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
Unapplied Cash (Receipt 1) None

None Neing (Receipt 1)

Neing (Receipt 2) None

None Unapplied Cash (Receipt 2)

Note: Both receipts must be in the same currency.
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 Neing account when dening 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 (neing).
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 neing application, using the adjusted conversion rate.
• Recalculate the exchange gain or loss on whichever receipt gained the additional funds.
Remiances
This section describes the default accounting entries for remiances.
180
When you create a receipt that requires remiance to your bank, Receivables debits the Conrmation account instead
of Cash. An example of a receipt requiring remiance is a check before it is cashed. Receivables creates the following
journal entry when you enter such a receipt:
Debit Credit
Conrmation None

None Receivables

You can then remit the receipt to your remiance bank using one of the two remiance methods: Standard or
Factoring. If you remit your receipt using the standard method of remiance, Receivables creates the following journal
entry:
Debit Credit
Remiance None

None Conrmation

When you clear the receipt, Receivables creates the following journal entry:
Debit Credit
Cash None

Bank Charges None

None Remiance

If you remit your receipt using the factoring remiance method, Receivables creates the following journal entry:
Debit Credit
Factor None

None Conrmation

181
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

Bank Charges None

None Short-Term Debt

On the maturity date, Receivables reverses the short-term liability and creates the following journal entry:
Debit Credit
Short-Term Debt None

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
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

None Revenue (if you enter line amounts)



Receivables None

None Late Charges

Credit Card Refunds

This section describes the default accounting entries for credit card refunds.
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

None Receivables Activity (Clearing Account)

183
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
Receivables Activity (Clearing None

Account)

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

None Receivables Activity (Clearing Account)

Receivables creates this journal entry for the original payment receipt:
Debit Credit
Receivables Activity (Clearing None

Account)

None Unapplied

Related Topics
• Examples of Accounting Entries for Bills Receivable Activities
• AutoAccounting Account Types and Segment Values
Examples of Accounting Entries for Invoicing Rules

These examples illustrate how the In Advance and In Arrears invoicing rules recognize receivables.
In Advance Accounting Entries

This example shows how you can use the In Advance invoicing rule to recognize your receivable immediately.
184
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
Account Debit Credit
Receivables $3,000 None

Unearned Revenue None $3,000

Unearned Revenue $1,000 None

Revenue None $1,000

February

Revenue None $1,000

March

Revenue None $1,000

In Arrears Accounting Entries

This example shows how you can use the In Arrears invoicing rule to record your receivable at the end of the revenue
recognition schedule.
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
Unbilled Receivables $1,000 None

Revenue None $1,000

February

Revenue None $1,000

March

Revenue None $1,000

Receivables $3,000 None

Unbilled Receivables None $3,000

Intercompany Receivables Transactions

An intercompany transaction is a transaction between two entities with common ownership. The accounting for
intercompany transactions is recorded separate from standard transactions in Receivables.
Receivables determines a transaction to be an intercompany transaction based on the rst party (legal entity) and third
party (bill-to customer) relationship dened in the intercompany accounting setup. When a transaction is marked as
intercompany, the intercompany receivables account is used for accounting instead of the standard receivables account
derived from AutoAccounting. This applies to transactions both created manually and imported using AutoInvoice.
Rules Governing Intercompany Transactions

Intercompany accounting is recorded for invoices, credit memos, on-account credit memos, debit memos, and
chargebacks. The intercompany account derivation occurs after the transaction is created but before the intercompany
transaction is complete.
186
These rules govern the use of intercompany transactions in Receivables:

• Adjustments: You can make manual and automatic adjustments against intercompany transactions, but these
adjustments are not marked as intercompany and do not derive an intercompany account.
• Distributions: You cannot update the account distributions once an intercompany transaction is created.
• Receipts: You can apply full or partial receipts to intercompany transactions with no restrictions.
• On-account credit memos: You should only apply intercompany on-account credit memos to intercompany
transactions. The related application pages display only intercompany transactions.
• Receivables period close: Close a Receivables accounting period after closing the related intercompany period.
If you close a Receivables accounting period rst, this generates a warning to close the related intercompany
period.
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
• Intercompany Balancing Rules
Legal Entity Time Zones in Receivables

The applicable dates on Receivables transactions and receipts are converted to the time zone date of the legal entity
that owns them, according to the Legal Entity Time Zone functionality.
For example, a legal entity on the west coast of the United States uses a shared service center on the east coast to
process transactions. An invoice entered by the shared service center at 2:30 AM on December 1 (shared service center
time zone) is entered with a transaction date and accounting date of 11:30 PM on November 30 (legal entity time zone).
Rules for Time Zone Derivation

Dierent time zone derivation rules apply to transactions and receipts.
The following rules apply to time zone derivation on a transaction:

• Time zone conversion applies to the transaction date, adjustment date, and accounting date on transactions
• Time zone is derived from the legal entity associated to the business unit of the transaction. This includes both
user-entered business units and business units provided by default.
• If there is no legal entity associated with the business unit used on the transaction, then the system date is
used. There is no time conversion of this date.
• These rules apply to invoices, credit memos, on-account credit memos, debit memos, chargebacks, and
adjustments.
• There is no time zone conversion within AutoInvoice. If another application passes a source date to
AutoInvoice, this source date may be subject to time zone conversion according to the rules of that application.
The following rules apply to time zone derivation on a receipt:

• Time zone conversion applies to the receipt date, batch date, conrmation date, deposit date, application date,
reversal date, accounting date, and unapply accounting date on all receipts, receipt batches, receipt write-os,
and chargebacks where the default date is the system date.
• Time zone conversion applies to the refund date and accounting date on all refunds where the default date is
the system date.
187
• 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 remiance batch date and accounting date on all remiance 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 remiance 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, remiance batches, receipt reversals, refunds, on-account applications, credit memo write-os, and
updates to conversion rates.
Manually Updating the Date or Legal Entity

After transaction or receipt dates are converted to the applicable time zone, no further time zone conversion takes
place. If you manually update either the date or the legal entity on a transaction or receipt, this action doesn't
recalculate time zone dates based on your changes. The changes that you make become the new date or legal entity.
Related Topics
• What legal entity is assigned to a receipt
Oracle Receivables Integration with Oracle Project

Integration services between Receivables and Project let you manage aspects of Project invoices both before and after
transfer to Receivables using AutoInvoice.
Integration services between Oracle Receivables and Oracle Project include:
• Tax Amounts on Project Invoices
• Contract Invoices
• Invoice Printing
• Net Invoices
Tax Amounts on Project Invoices

You can review estimated tax amounts on draft Project invoices before transfer to Receivables. You can review
estimated tax amounts for the entire invoice or for selected invoice lines. You can also print invoices in Project with
estimated tax amounts.
Project invoices use the same tax conguration, as dened 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
conguration between invoice creation in Project and invoice transfer to Receivables, the nal tax calculation may dier
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
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
190
Using Receivables Credit to Cash Process Customer Payments
2 Process Customer Payments
Apply Customer Payments

Guidelines for Applying Receipts and On-Account Credit Memos
Watch video
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 Prole Option
• Receipt Application on Cross-Customer Transactions
• Foreign Currency Receipts
• Balance Forward Bills
Credit Memo Search

You can only search for and display complete credit memos.
Transaction Balance for Applications Always Used Prole Option

The Transaction Balance for Applications Always Used prole option determines the default amount applied value
to use for receipt applications. If you set this prole option to Yes, then the default amount applied is the remaining
transaction amount.
If you set this prole option to No, or if a null value exists, then the defaulting rule is:
• If the unapplied receipt amount is greater than or equal to the transaction, then the default amount applied is
the remaining transaction amount.
• If the unapplied receipt amount is less than the remaining transaction amount, then the default amount applied
is the unapplied receipt amount.
Receipt Application on Cross-Customer Transactions

You can apply a receipt to the open debit items of unrelated customers if the Allow Payment of Unrelated
Transactions system option is set to Yes.
If a customer paying relationship assignment exists, then customers can pay for transactions of related customers in
the same hierarchy according to the paying relationship. The paying relationships are:
• Pay Any: Any customer within the relationship can pay for the accounts of any other customer within the
relationship.
191
• 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).
Foreign Currency Receipts

If you apply receipts in the same foreign currency as the transactions, enter foreign currency conversion rate
information using predened conversion rates, or enter your own rate. If, when you post a foreign currency receipt
application to general ledger, the rate changes, Receivables records a realized gain or loss amount.

You can apply on-account credit memos to transactions and refunds only. Receivables doesn't calculate discounts for
on-account credit memo applications.
You can't use cross currency applications with on-account credit memos. The currency of the on-account credit memo
and the currency of the transaction must be the same.
Balance Forward Bills

You can use the balance forward billing number as the document reference for the Match Receipt By rule. Receivables
applies receipts to transactions identied by the balance forward billing number.
Related Topics
• Customer Hierarchies and Paying Relationships
• Receipt Application using the Match Receipts By Rule
How Recommendations for Receipt Application Are Calculated

During payment processing, Receivables matches the remiance reference information on your receipts to open
transactions, and presents recommendations for which transactions to use for a given receipt application. This
recommendation process operates for manual receipts, lockbox receipts, and receipts uploaded using a spreadsheet.
In general, Receivables generates recommendations rather than applying receipts automatically when there is a
data entry error, such as an incorrect invoice number, or when no transaction meets the minimum requirements for
automatic receipt application, as dened by your implementation.
Seings That Aect Recommendations for Receipt Application

These seings aect recommendations for receipt application:
• Match Receipts By rule: The Match Receipts By rule identies 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
You can set Match Receipt By document references at the customer site, customer account, lockbox, and
Receivables system option level. Receivables searches these seings 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 dierent from the default seing (or if there was no default seing), 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 denes 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.
How Recommendations for Receipt Application Are Calculated

Receivables matches the remiance reference on the receipt to transactions, based on the active Match Receipt By rule.
Receivables searches for a Match Receipt By rule to use for comparison in the order customer site, customer account,
lockbox (for lockbox processing), and Receivables system options.
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 seings 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 buon 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
Receipts Applied without a Reference

Receivables will apply a receipt to a transaction or generate transaction recommendations without a remiance
reference under these conditions:
• Customer information on the receipt matches that of the transaction.
• Receipt amount is equal to or greater than the transaction amount.
• For lockbox processing, the AutoCash rule is unable to apply the receipt.
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
Neing to manage the oset 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.
Write-os and Receipts

A write-o is a receipt activity that cancels an open debit item and assigns it to a write-o account. You can write o
both overpayment and underpayment amounts.
You write o an overpayment when, after applying a receipt to debit items, a small unapplied amount remains. You
write o an underpayment when a receipt underpays an invoice by a small amount and the write-o is preferable to
billing the customer for the dierence.
Considerations for write-os include:

• Write-o Setup
• Recommendations for Write-os
• Automatic Write-os
• Foreign Currency Write-os
194
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.
These setups are related to receipt write-os:

• Receivables activity: Set up accounts under the Receivables activity Receipt Write-o to credit receipt write-o
amounts.
• Application exception rule set: Dene an application exception rule set and assign the rule to Receivables
System Options: Cash Processing tab. The application exception rule set denes how to manage overpayments
and underpayments.
• Receivables system options: Dene the write-o limit range per receipt. You cannot write o receipt balances
that are less than or greater than this range.
• Approval limits: Dene user approval limits per currency for write-os.
Recommendations for Write-os

During automatic payment processing, Receivables identies underpayments and overpayments after receipts
are applied to transactions. Depending on the details of your setup, Receivables can write o certain payments
automatically and present other payments to you for review.
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-os
Use the Create Automatic Receipt Write-os program to automatically write o receipts. You can only use this program
to write o overpayment amounts.
The Create Automatic Receipt Write-os 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-os program to:
• Schedule periodic write-os as receipt adjustments for small remaining balances.
• Limit write-os by a percentage of the original receipt amount and by the policy of your enterprise.
• Create write-os for specic currencies and customers.
You can also print and review write-os 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.
Foreign Currency Write-os

When you write o a foreign currency receipt, Receivables uses the conversion rate information from the original
receipt for the write-o record.
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
Related Topics
• What are the exception rule activities
• Application Exception Rule Conditions and Actions
• Approval Limits Document Types
How Cross-Currency Receipts Are Processed

Use cross-currency receipt applications to process payments that customers make in a currency that is dierent from
the currency of the open debit item. You can apply cross-currency receipts to invoices, debit memos, and chargebacks.
When you apply a cross-currency receipt, Receivables calculates both the open balance on the transaction (if any) and
the foreign exchange gain or loss for the application.
You can apply receipts to transactions using any currency dened in General Ledger.
Seings That Aect Cross-Currency Receipts

These seings aect cross-currency receipt applications:
• Realized Gains and Realized Losses Accounts: Dene a realized gains account and a realized losses account
at the Receivables system option level to account for the conversion rate gain or loss in the ledger currency
resulting from a cross-currency receipt application.
• Cross Currency Rate Type: Enter the default conversion rate type at the Receivables system option level to
use when the receipt and transaction currency are dierent and the two currencies don't have a xed-rate
relationship. If the receipt and transaction have a xed-rate relationship, then Receivables uses the conversion
rate dened between these currencies.
Receivables uses this rate type to calculate the allocated receipt amount when you enter the amount applied,
and vice versa. If this Receivables system option is not dened, then you must manually enter both values.
Lockbox also uses this rate type to apply cross-currency receipts if the program can't calculate the rate to use.
• Cross Currency Rounding Account: Dene a cross-currency rounding account at the Receivables system
options level to record any rounding error amounts created during a cross-currency receipt application for
currencies that have a xed-rate relationship.
• Suspense Account: Dene a suspense account in general ledger for journal entries created by cross-currency
receipt applications. For each cross-currency receipt application, general ledger creates one entry in the
suspense account so that each journal entry will balance in the entered currency.
How Cross-Currency Receipts Are Calculated

When applying cross-currency receipts, your customer needs to provide the following remiance information:
• Which transactions to apply the receipt to.
• If the receipt is a partial payment, how much of each transaction is to be seled.
• If applicable, conversion rate information, which is either:
◦ Conversion rate to use to convert to the ledger currency.

◦ If you are manually entering allocated receipt amounts, how much of the receipt to allocate to a
transaction.
196
In the Create Receipt or Manage Receipt page:
• 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.
Receivables performs these calculations:
• 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
This formula can be also expressed as:
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
dierent currency. When you post these multi-currency journal entries, General Ledger:
• Separates the entries by currency before balancing them.

• Creates an entry in the suspense account to balance each journal entry.
197
Examples of Cross-Currency Receipt Applications

The following examples illustrate the calculations and journal entries when you apply cross-currency receipts.
In the rst example, you apply a receipt in one currency to an invoice in a dierent currency. Both the invoice currency
and the receipt currency are dierent from your ledger currency.
In the second example, you apply a receipt in one currency to three separate invoices, each in a dierent currency.
Apply a Receipt to One Invoice

On JAN-01 you create Invoice 101 for 100 Canadian dollars (CAD). The corporate conversion rate on JAN-01 is 1 USD =
1.5 CAD. Receivables uses this rate to calculate the amount of the invoice in your ledger currency as 66.67 USD (100 / 1.5
= 66.67).
Receivables creates corresponding journal entries for this amount in both the invoice currency and your ledger
currency, as illustrated in this table:
Accounts Receivable 100 CAD [66.67 USD] None

Sales None 100 CAD [66.67 USD]

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:
Invoice Balance Balance Amount Amount Cross- Allocated Allocated Exchange

Number Due Base Due Applied Applied Currency Receipt Receipt Gain/Loss
Base Rate Amount Amount
Base
101 66.67 100.00 NA NA NA NA NA NA

Following your customer remiance 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

Base
101 6.67 10.00 90.00 60.00 NA NA NA NA

The calculations used to arrive at these amounts are:
• Balance Due = 100 - 90 = 10 (CAD)

• Balance Due Base = 10 / 1.5 = 6.67 (USD)
• Amount Applied Base = 90 / 1.5 = 60 (USD)
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.
This is represented as follows:

Base
101 6.67 10.00 90.00 60.00 0.7111111 64.00 56.64 <3.36>

The calculations used to arrive at these amounts are:
• Cross-Currency Rate = 64 (EUR) / 90 (CAD) = 0.7111111

• Allocated Receipt Amount = 64 (EUR) / 1.13 = 56.64 (USD)
• Exchange Gain/Loss = 56.64 (USD) - 60 (USD) = <3.36> (USD)
Receivables creates the accounting entries as illustrated in this table:
Cash 64 EUR [56.64 USD] None

Foreign Exchange Loss 3.36 USD None

Accounts Receivable None 90 CAD [60 USD]

199
Apply a Receipt to Three Invoices

Your customer remits Receipt 1234 for 300 EUR and wants this receipt applied to three outstanding invoices:
• Invoice 101 for 100 Canadian dollars (CAD)
• Invoice 102 for 100 US dollars (USD)
• Invoice 103 for 8000 Japanese yen (JPY)
Your customer provides remiance information, including rate information, as described in this table:
Invoice Number Date Invoice Balance Paid Amount Rate to EUR EUR Remied
101 1-JAN 100 CAD 90 CAD .725298 65.28

102 2-JAN 100 USD 100 USD 1.15989 115.99

103 4-JAN 8000 JPY 8000 JPY .0086927 69.54

Activity totals:
• Total Remied Amount: 250.78 EUR
• On Account: 49.22
• Total Remiance: 300.00 EUR
After you enter and apply the receipt according to the customer remiance information, this is represented as follows:

Base
101 6.67 10.00 90.00 60.00 .725298 65.28 57.14 <2.86>

102 0.00 0.00 100.00 100.00 1.15989 115.99 99.12 <0.88>

103 0.00 0.00 500.00 96.15 .0086927 69.54 94.61 1.54

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
Credit Card Chargebacks

A customer may request a refund for all or part of a previously remied credit card receipt directly with the credit card
issuer.
Note: Credit card services are currently not available in Oracle Financials Cloud implementations.
Under this procedure, the credit card issuer credits the customer account for the disputed amount, deducts the amount
from your merchant bank account, and noties 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.
To record a credit card chargeback:

1. Ensure that you have dened a receivables activity of type Credit Card Chargeback.
2. In the Manage Receipts page, open the credit card receipt with the chargeback request.
3. Unapply the credit card receipt:
◦ If you are unapplying the full amount, use the Unapply Application buon to unapply the credit card
receipt application from the transaction.
◦ If you are only unapplying a partial amount, enter the new amount to apply to the transaction in the
related Applied Amount eld.
4. Create the credit card chargeback. Select Create Credit Card Chargeback from the Actions menu to open the
Create Credit Card Chargeback window:
a. Enter the Credit Card Chargeback activity in the Receivables Activity eld.
b. Enter the amount of the chargeback request in the Amount eld.
c. Enter the date to use for this transaction in the Application Date eld.
d. Optionally enter details of this transaction in the Reason eld.
The credit card chargeback application and corresponding negative miscellaneous receipt record the event and correct
the accounting. Because there are no funds to transfer, you don't have to remit the negative miscellaneous receipt.
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
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
• 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 remiance.
This table indicates the reference type and corresponding reference number that you can use to identify the
miscellaneous receipt:
Reference Type Reference Number
Payment Check numbers recorded in Payables wrien from the same bank account as the remiance
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.

Remiance Remiance 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
Reports for Apply Customer Payments

Overview of the Applied Receipts Register
This topic contains summary information about the Applied Receipts Register.
Overview
The Applied Receipts Register provides information about all receipt applications that aect your customer balances.
Key Insights
Review receipt applications by customer and receipt batch. The report displays all receipt applications within the
specied date range regardless of check date.

The following table lists frequently asked questions about the Applied Receipts Register.
FAQ Answer


When do I use this report? When you need a listing of your customer applied receipts or to assist the receivables
reconciliation process.

What can I do with this report? Schedule to run as needed.


203

This report uses the Receivables - Standard Receipt Application Details Real Time subject area.
Applied Receipts Register

Use the Applied Receipts Register to review all receipt applications that aect your customer balances.
The report includes both customer receipts and discount information. You can use this report to review receipt
applications for a specic customer, receipt batch, or applied transaction number. You cannot use this report to review
miscellaneous receipts.
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.

You can select receipt applications by customer and receipt batch. Specify a receipt application accounting date range
to review specic information for the period. The report displays all receipt applications within the date range regardless
of check date.
Application Accounting Date
The application accounting date range.
Receipt Batch Number
Select receipts by batch to review specic batches, such as lockbox batches.
Application Exception Reason
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.
Applied Transaction Number
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
specied 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
Application Accounting Date The accounting date of the receipt application or application reversal.

Entered Applied Amount The receipt amount applied in the entered currency.

Earned Discount The earned discount amount in the ledger currency.

Unearned Discount The unearned discount amount in the ledger 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 Dening Automatic Receipt Methods
205
Overview of the Receipts Days Late Analysis Report

This topic contains summary information about the Receipts Days Late Analysis Report.
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.

The following table lists frequently asked questions about the Receipts Days Late Analysis 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 when analyzing late payments.

206
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.



Receipts Days Late Analysis Report

Use the Receipts Days Late Analysis Report to review the timeliness of your customer payments. The report provides
details of receipt applications against customer transactions for the period you specify.
The report includes, for each customer payment, both transaction details and receipt application details. Receipt
information includes the number of days late, if any, that payment was received based on the due date, and the
calculated cost to you of a late payment.
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.
Weighted Average Days Late

The weighted average days late for receipts within the date range by customer and currency. Use the weighted
average days late to see the average amount that past due debit items cost you.
Weighted Average Days Late = Sum of Weighted Days Late / Total Amount Paid
207
Overview of the Unapplied Receipts Register

This topic contains summary information about the Unapplied Receipts Register.
Overview
The Unapplied Receipts Register lets you review detailed information about customer unidentied, 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 unidentied receipts in the ledger currency, and a grand total for the report.

The following table lists frequently asked questions about the Unapplied Receipts Register.
FAQ Answer


When do I use this report? • When you need a listing of your customer unapplied receipts.
• To assist the receivables reconciliation process.



This report uses the Receivables - Standard Receipt Application Details Real Time subject area.
208
Unapplied Receipts Register

Use the Unapplied Receipts Register to review detailed information about customer unidentied, on-account and
unapplied payments by business unit and accounting period. Information about customer on-account and unapplied
payments more accurately indicates how much a customer actually owes you.
The Unapplied Receipts Register excludes receipts applied to activities that do not aect the customer balance, such as
receipt write-os, short-term debt, and credit card refunds. For example, when you create a credit card refund, it is the
credit memo associated with the refund that aects the customer balance (this is reported in the Transaction Register).
The report also excludes miscellaneous receipts.
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.

Accounting Date
The accounting date range to include in the report.
Receipt Currency
Conne the report to one receipt currency.
Receipt Batch Number
Conne the report to a specic receipt batch, such as a lockbox batch.
Application Status
Conne the report to Unapplied, On-account or Unidentied receipts.
Report Output
The report groups receipts by receipt batch and customer, and provides separate totals by business unit for on-account,
unapplied, and unidentied 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 Currency The currency of the receipt.

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 unidentied receipts.

Grand Total Total for the report.

209
Related Topics
Write-o Unapplied Receipt Balances Report

Use the Write-o Unapplied Receipt Balances Report to review a run of the Create Automatic Receipt Write-os
program. You can also generate the report without creating actual write-o entries to review the results of a proposed
program run.
Both the manual and automatic write-o processes initiate the Create Automatic Receipt Write-os program to process
the writing o of unapplied receipt amounts. The program validates both the data that you enter and your write-o
approval limit, selects the records to write o, then creates the accounting entries and updates the receipt balances.
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.

Receipt Currency
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.
Unapplied Amount Percentage
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 specic unapplied receipt that you want to write o. If you specied 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-os
• 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-os program to write o receipts according to
your selection criteria, and generate the Write-o Unapplied Receipt Balances Report.
210
Write-o Receivables Activity
The receivables activity that determines the general ledger account to use to credit the write-os.
This parameter is required if you set the Create Write-os 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.
FAQs for Apply Customer Payments

Why can't I apply a receipt amount to a closed debit item?
The transaction type of the debit item to which you are applying the receipt is used to validate the application amount. If
the transaction type allows overapplication, then you can apply a receipt to a closed debit item.
If the transaction type allows natural application only, then you can't enter an amount that would reverse the sign of the
debit item. In this case, you can only enter an amount that brings the balance due closer to zero.
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 buon to open the Search and Select window. Use the Bill-to Site eld to lter customer transactions by
bill-to site.
Why did changing the receipt application reverse an adjustment?

Because transaction adjustments created after receipt application no longer apply when you change the receipt.
For example, you apply a $99 receipt to a $100 invoice, then you adjust the remaining $1 to close the transaction. If you
later change the receipt application, either by unapplying the receipt, reversing the receipt, or changing the applied
amount on the receipt, this reverses the adjustment on the transaction.
If necessary, you can retain the original adjustment record by creating a new adjustment in the transaction or in receipt
details.
Can I credit receipts against the transactions of other business units?

No, Receivables only considers on-account and unapplied receipts as credit against open balances for business units
that are set up to process both transactions and receipts.
How are transaction line amounts reduced?

The application rule set assigned to the transaction type of the debit item determines how to reduce the open line, tax,
freight, and late charge amounts for both receipt and on-account credit memo applications. If there is no application
rule set assigned to the transaction type, the application process uses the application rule set assigned to Receivables
system options.
211
An application rule set uses these application rules:
• 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.
How do I use transaction and customer recommendations?

Use transaction recommendations with lockbox receipts and manual receipts. Receivables recommends one or more
transactions for receipt application, with what it considers the closest match displayed rst. You can select any of the
recommended transactions that you want to apply to the receipt up to the receipt amount.
Use customer recommendations with lockbox receipts that contain invalid customer information. Receivables provides
a list of customers for you to select one for the receipt.
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.
What are exception trends?

Exception trends monitor manual receipt applications. In many cases, Receivables matches receipts to transactions
automatically and successfully applies the receipts.
When customer payments are not fully applied to open debit items, you must review the unapplied amounts and apply
receipts manually to complete the payment process. You can add an exception reason that explains why a manual
receipt application was necessary, for example, an invalid invoice number was used. You use the Exception Reason
lookup type to dene lookup codes for your exception reasons.
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.
How can I reapply a receipt applied in error?

First unapply the original receipt applications, and then apply the receipt to the new transactions that you want. You can
reapply both automatic and manually entered receipts before or after posting to general ledger.
Unapplying a receipt reopens each transaction or transaction line that was previously closed by the receipt. Receivables
enters a reversal accounting date for each transaction or transaction line reopened. The reversal accounting date,
which is the date to post this reapplication to general ledger, is the same as either the accounting date of the original
application or, if the original application accounting date is in a closed period, the system date. If the system date is not
in an open period, the default is the last date of the most recent open period.
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.
When do I create a chargeback?

Use chargebacks to create a new debit item for your customers when closing an existing debit item. You can also create
a chargeback against a credit memo or on-account credit with a positive balance.
212
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.
What's the dierence between a chargeback and a credit card chargeback?

A chargeback closes an existing debit item and creates a new debit item for a customer. A chargeback is an open
receivable applied to a customer balance.
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.
Manage Automatic Receipts

How Automatic Receipts Are Processed
Use the automatic receipt process to create a batch of receipts from selected customer transactions for payment by
credit card or bank account transfer.
You use automatic receipts for customers with whom you have predened 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 conrm 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.
Seings That Aect Automatic Receipts

These Receivables seings pertain to the process of automatic receipts:
• Receipt Class: Use these seings for the receipt class of the receipt method assigned to each transaction:
◦ Creation method of Automatic.

◦ Set the Require conrmation option if the automatic receipts must be conrmed by the customer.
• Receipt Method: Use these seings 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
◦ 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 remiance 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 conrmation. This allows for the additional time required to send
the receipts to your customer and for the customer to conrm them.
• Factored receipts. Factored receipts are often remied long before their maturity date.
◦ Customer Payment Method: Enter the payment method that the customer uses to remit payment to you.
• Document sequences: If you are using document sequences:
◦ 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.
◦ Dene 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.
• Transactions to include in the automatic receipt batch:
◦ Receipt Method: All transactions must have the same receipt method as the automatic receipt batch.
◦ Customer payment information: All transactions must have dened both a paying customer and
payment instrument information.
• Customer account or site to include in the automatic receipt batch:
◦ Payment Details: Dene 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 prole 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 prole to determine
whether to include open items in dispute during transaction selection.
◦ Minimum Receipt Amount eld: Use this eld on the customer or site prole to dene 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 prole option: If you are using automatic receipts to pay foreign currency transactions,
then set this prole option to a value other than User to convert to the ledger currency.
• Remiance Bank Account:
◦ Dene a remiance bank account for the batch receipt method in the batch currency.
214
◦ Minimum Receipt Amount eld: Enter an amount below which the program won't generate automatic
receipts.
Caution: The automatic receipt process compares the remiance bank account and customer
prole 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.
How Automatic Receipts Are Processed

Complete all of these steps to prepare and process automatic receipts:
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 prole 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 dierence 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 remiance bank account or customer prole) 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. Conrm the batch. If necessary, send the automatic receipt batch to your customer for conrmation.
6. Remit receipts. Remit the receipts to your bank:
◦ If you are processing credit card payments, then the remiance process requests transfer of funds from
the credit card issuer to your bank.
◦ If you are processing bank account transfers, then the remiance process requests transfer of funds
from the customer bank account to your bank.
Related Topics
• What's the dierence between the various customers
• Requirements for Completing a Receivables Transaction
• Remiance Bank Accounts on Receipt Methods
215
Guidelines for Automatic Receipt Processing

You use the automatic receipt process for customers that have agreed to payment collection on a regular basis.
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
• Remiance Bank Information
• Document Sequences
• Bill-to Sites and Automatic Receipts
• Payment of Related Transactions
• Automatic Receipts System Options
Discounts and Automatic Receipts

You wouldn't normally use discounts with automatic receipts, because the concept of early payment doesn't apply. You
and the customer decide the receipt maturity date in advance, and the automatic receipt process transfers funds from
the customer bank account or credit card on that date only.
You can calculate earned discounts on payments for automatic receipts that don't require conrmation, if you set up
payment terms with the transaction due date equal to the discount date. For example, if the payment terms specify that
a transaction is due 30 days after the transaction date, create a percentage discount for 30 days after the transaction
date. This identies the 30-day period as a discount period.
You can't use discounts with automatic receipts that require conrmation by the customer. Alternatively, you can dene
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.
Start and End Date Ranges

Many of the setup objects used in automatic receipt processing have start and end date ranges, such as receipt
methods, remiance bank accounts, and customer bank accounts. Date ranges determine which objects display in lists
of values.
You must ensure that the setup objects used in automatic receipts do not contain inconsistent or overlapping date
ranges.
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.
Remiance Bank Information

The automatic receipt process assigns one of your remiance bank accounts to each receipt created by the payment of
a customer open debit item.
Remiance bank account information includes the general ledger accounts used during receipt application.
The automatic receipt process usually assigns to the receipt the primary remiance bank account associated with
the receipt method and currency of the transaction. The one exception to this is if a non-primary remiance bank
216
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 remiance bank account instead.
This matching of your remiance 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 remiance bank information for an automatic receipt under these conditions:
• Receipt status is Conrmed.
• Unapplied and On-Account general ledger accounts of the remiance 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 prole 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.
To set up document sequencing for automatic receipts:

• Ensure that a document category is created for each receipt method assigned to transactions selected for
automatic receipt application.
• Assign each applicable document category a document sequence with automatic numbering.
Bill-to Sites and Automatic Receipts

Use the Require billing location for receipts Receivables system option to determine whether Receivables creates an
automatic receipt for a customer without a primary bill-to site:
This table indicates the eect of seing or not seing the Require billing location for receipts Receivables system
option for automatic receipts:
Option Primary Bill-to Site? Create Automatic Receipt?
No No Yes, without a bill-to site

Yes No No

• If the system option is set to No and the customer doesn't have a primary bill-to site dened, 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 dened, Receivables
doesn't create the automatic receipt.
Payment of Related Transactions

If you use customer selection criteria for an automatic receipt batch, the process searches for transactions with a
matching paying customer, rather than the bill-to customer. The paying customer is the customer associated with the
customer bank account assigned to the transaction. This customer may dier from the bill-to customer if, for example,
you want a primary customer to pay for related transactions.
217
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.
• Dene 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.
Automatic Receipts System Options

You use the Automatic Receipts section of the Cash Processing tab of Receivables system options to set up automatic
receipts for your business unit.
Use the Receipt Conrmation Threshold Amount eld to set a value agreed upon with your customers to
automatically conrm automatic receipts. An automatic receipt batch with a total amount below the value you enter
doesn't require conrmation.
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 remiance batches.
To help determine the values to use, refer to the end of the log le of your largest automatic receipt batch and
remiance 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 dierence between an account relationship and a paying relationship
• Guidelines for Managing Document Sequences
• Ledger and Legal Entity Document Sequencing in Receivables
How You Approve Automatic Receipts

Approve a batch of automatic receipts to verify that the batch contains all of the receipts that you want. You can
approve an automatic receipt batch that has a status of Creation Completed or Started Approval.
You can update the automatic receipt batch before you approve it, as long as there are no concurrent processes for
creating or approving this batch that are either running or pending.
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 conrmation according to
the Number of Receipts Rule on the receipt method and closes the transactions they are paying.
Note: Receipts that require conrmation close transactions only when they are conrmed by the customer.
218
When you remit an approved automatic receipt batch, your remiance bank uses the batch maturity date to determine
when to transfer the funds from your customer bank account to your remiance bank account. Receivables uses the
Receipt Maturity Date Rule on the receipt method to determine the maturity date on the approved receipts.
How You Conrm Automatic Receipts

Conrm automatic receipt batches to indicate that your customer has reviewed each receipt and agrees that the
payment information is correct.
Depending on the agreement you have with your customer, certain types of automatic receipts require conrmation
from your customer before they can be considered payments and remied to the bank. Once your customer approves
these receipts, you can make any necessary changes, then conrm the receipts.
When a customer conrms the automatic receipt batch, they may provide a conrmation number for each receipt. Enter
this number in the available reference or comment eld. This number is passed to your remiance 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
conrmation, you must conrm the receipt or receipt batch once it has been approved by your customer. Receipts
that require conrmation automatically close the invoices for which they were created when you conrm them. After
conrming the automatic receipt batch, you can create a remiance batch to initiate the transfer of funds for each
receipt.
You can make these updates to an automatic receipt batch before you conrm it:
• Transactions selected to apply to the receipt.
• Conversion rate information.
• Receipt maturity date.
• Your remiance bank.
• Customer bank account information.
You can only change the approved amounts for your receipt applications if the receipt isn't conrmed. Once conrmed,
Receivables automatically applies the receipt and updates the balance of the transactions to which it is applied.
ISO Rejection Code Mapping to Reversal Categories

To automatically reverse receipts in a selement batch, you must map the ISO rejection codes to a reversal category.
This mapping is used to derive the reason for reversing a receipt.
Use the Manage Reversal Reason to Category Mappings setup task to map the ISO rejection codes with the
corresponding reversal categories.
Congure ISO Rejection Codes as Reversal Reasons

Before you begin, ensure that the ISO codes appear in the Reversal Reason list on the Manage Reversal Reason to
Category Mappings page. Dene the ISO codes as lookups of the CKAJST_REASON lookup type.
To congure ISO rejection codes as reversal reasons:

1. Navigate to Setup and Maintenance.
2. Search for the Manage Receivables Lookups task.
219
3. Click the Go to Task icon.
The Manage Receivables Lookups page appears.

4. Enter CKAJST_REASON in the Lookup Type box and click the Search buon.
5. Click the Add Row icon that appears on the Financials Generic Lookup Type: CKAJST_REASON table.
6. Enter the ISO rejection code in the Lookup Code box.
7. Enter the meaning and description for the rejection code in the Meaning and Description boxes.
8. Click the Enable box so that the rejection code appears as the reversal reason on the Manage Reversal Reason
to Category Mappings page.
9. Repeat steps 5 through 8 to congure other ISO rejection codes.
10. Click the Save and Close buon when you complete conguring all the ISO rejection codes.
Map Rejection Codes to Reversal Categories

To map the ISO rejection codes to reversal categories:
1. Navigate to Setup and Maintenance.

2. Search for the Manage Receivables Reversal Reason to Category Mappings task.
3. Click the Go to Task icon.
The Manage Reversal Reason to Category Mappings page appears.

4. Click the Add Row icon.
5. Select the ISO rejection code from the Reversal Reason list.
6. Select the category from the Reversal Category list.
7. Click the Enabled box to enable the mapping between the reversal reason and reversal category.
8. Enter the Payment Standard, identier of the established standard that is associated with the reversal reason.
9. Repeat steps 4 to 8 to map other ISO rejection codes.
10. Click the Save and Close buon when you complete mapping all the ISO rejection codes.
How Automatic Receipts Are Reversed

Use the Automatic Receipts Reversal process to identify the rejected selements in a selement batch and reverse the
corresponding receipts. The process only reverses automatic receipts, not manual receipts.
Seings That Aect Reversal of Automatic Receipts

Before you can reverse automatic receipts in a selement batch, you must map the ISO rejection codes to a reversal
category. This mapping is used to derive the reversal category for reversing the receipt.
Use the Manage Reversal Reason to Category Mappings setup task to map the ISO rejection codes with corresponding
reversal categories.
How Receipts are Reversed

When a bank can't process an automatic remiance of a record, the record is sent back for reversal. The returned record
consists of two bank les:
• 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
The following steps outline the reversal process:

1. The Retrieve Funds Capture Acknowledgments process in Payments processes the pain message and sends
information on the rejected receipts to Receivables.
2. The Automatic Receipts Reversal process receives the information on the rejected receipts and looks for the
mapping between the rejection code and reversal category.
3. If a mapping exists for the rejection code, the corresponding receipt is reversed. If a mapping doesn't exist, the
status of the corresponding receipt is set to Conrmed.
4. To reverse receipts that are set to Conrmed, you must dene the mapping and run the Automatic Receipts
Reversal process to reverse the corresponding receipts.
Note: Reconciled receipts aren't reversed by the Automatic Receipts Reversal process. You must
manually unreconcile the receipts before reversing them.
5. After the Automatic Receipts Reversal process completes, the Reversal Status Report is generated. Use the
report to review the automatic receipt reversals processed in a selement batch. The report displays details of
the:
◦ Receipts that are reversed along with the reversal reason
◦ Receipts that aren't reversed and the reason they weren't reversed
6. The report is automatically run after the Automatic Receipts Reversal process. However, you can also run the
report manually.
Related Topics
• How Selement 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.
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 remiance.
Create a Credit Card Automatic Receipt Method

Create an automatic receipt method for processing tokenized credit card transactions and enter this receipt method in
the AutoInvoice Import template. The receipt method is assigned to tokenized credit card transactions during import.
Important seings include:

• Receipt Class: Use the Creation Method Automatic. This exposes the Automatic Processing tab when you
create the receipt method.
• Receipt Method: Number of Receipts Rule: If you are importing tokenized credit card transactions with
authorization, you can only use the Number of Receipts Rule One per Invoice to group transactions. If you are
importing tokenized credit card transactions without authorization, then you can use any rule.
221
• 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.
Review Imported Transactions

Use the Review Transaction page to open and review your imported tokenized credit card transactions.
Review these actions:
• 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.
Create Automatic Receipts and Remiance

Use the automatic receipt process and the Create Automatic Receipt Batch page to create receipts for your imported
tokenized credit card transactions. Use the Create Receipt Remiance Batch page to remit receipts to the bank.
Considerations for automatic receipts and remiance include:
• 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 remiance batch.
FAQs for Manage Automatic Receipts

Can I manually enter an automatic receipt?
Yes, if the customer remits a manual document for a transaction that was supposed to be paid by automatic receipt, you
can manually enter this as a standard receipt. You must select a receipt method assigned to a receipt class that has a
creation method of Automatic.
Receivables treats this receipt like any other automatic receipt. When you remit the receipt to the bank, the funds are
transferred from the customer bank account to your bank account.
Why can't I nd a transaction in the automatic receipt batch?

Because the transaction doesn't have the appropriate seings. An automatic receipt batch can only include complete
transactions that contain customer payment details and have a receipt method belonging to a receipt class with an
Automatic creation method. This applies to both imported and manually entered transactions.
If necessary, update the transactions that you want to include in the automatic receipt batch with customer payment
information and the appropriate receipt method.
222
Can I unconrm a receipt?

No, you can't unconrm an automatic receipt after you conrm it. If you conrm a receipt in error, you need to reverse
and then recreate the receipt.
Once you conrm an automatic receipt, the transactions closed by this receipt can no longer be selected for automatic
receipt creation. However, transactions with a remaining balance due can be included in a subsequent automatic receipt
batch.
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
insucient funds.
Considerations for reversing receipts include:
• Receipts Eligible for Reversal
• Receipt Reversal Process
• Reversal Categories and Reasons
Receipts Eligible for Reversal

You can reverse these types of receipts:
• Invoice-related receipts.
• Miscellaneous receipts.
• Credit card refund (negative miscellaneous) receipts.
• Receipts that are part of a batch.
• Receipts that were applied to open receipts, provided that neither receipt is drawn negative by the reversal.
Receipt Reversal Process

When you reverse a receipt, Receivables automatically creates reversal journal entries in the general ledger and reopens
all of the debit and credit items that were closed by the receipt.
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.
Reversal Categories and Reasons

The reversal categories are used to identify the reversal for further processing. For example, use the Credit Card Refund
Reversal category for reversing a credit card refund miscellaneous receipt. Use the Reverse Payment category for
receipts with incorrect data entry.
The reversal reasons are user-dened reference information that describe why a particular category of reversal took
place.
223
Debit Memo Reversals

Use debit memo reversals when you need to reverse a receipt, but you want to maintain the link between the billing
activity and the payment. When you create a debit memo reversal, Receivables reverses the receipt, but doesn't update
any of the receipt activity associated with the original receipt.
Debit Memo Reversal Process

A debit memo reversal is dierent from a standard reversal because, instead of reopening the debit and credit items
that were closed with the original receipt, Receivables creates one new receivable in the amount of the net of the closed
debit and credit transactions. As a result, the reversed receipt shows the transaction as still applied.
You must create a debit memo reversal under each of these circumstances:
• 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 remied 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.
Debit Memo Transaction Type for Debit Memo Reversals

To create a debit memo reversal, you enter a debit memo transaction type. The debit memo transaction type provides
the default receivable account distribution for the new debit item.
If the receipt that you are reversing uses a receipt method with the Debit Memos Inherit Receipt Number option
enabled, you can control whether the debit memo has the same transaction number as the original receipt. If the
Debit Memos Inherit Receipt Number option is not enabled, Receivables uses the predened Debit Memo Reversal
transaction source to determine the numbering for the debit memo reversal.
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 predened memo line.
Receivables creates this line on the debit memo:
Debit memo for reversal of payment {PAYMENT_NUMBER}
where {PAYMENT_NUMBER} represents the original receipt number.
Accounting Entries for Debit Memo Reversals

When you create a debit memo reversal, Receivables creates the accounting entries on the new debit memo transaction
rather than on the original receipt. This ensures that you don't make duplicate entries, and eliminates the need for a
clearing account.
With regular debit memos, AutoAccounting creates both the receivable and revenue account distributions. With debit
memo reversals, the debit memo transaction type provides the receivable account distribution, and the cash account on
the receipt is used as the revenue account distribution.
224
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 remied, then the cash account is the same as the remied 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
Reports for Reverse Receipts

Overview of the Reversed Receipts Report
This topic contains summary information about the Reversed Receipts Report.
Overview
The Reversed Receipts Report lets you review receipt reversals by reversal date and remiance bank.
225
Key Insights
The report displays results and total receipts by bank, customer or reversal reason. You can optionally review specic
receipts according to the parameters that you specify.

The following table lists frequently asked questions about the Reversed Receipts Report.
FAQ Answer

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 remiance bank, and categorize by stop
payments, insucient funds, and receipts entered in error.




This report uses these subject areas:
• Receivables - Standard Receipt Application Details Real Time

• Receivables - Miscellaneous Receipts Real Time
Reversed Receipts Report

Use the Reversed Receipts Report to review receipt reversals by reversal date and remiance bank. You reverse receipts
when your customer stops payment or when a payment comes from an account with non-sucient funds.
Display results and total receipts by bank, customer or reversal reason. Optionally review specic receipts by type, bank
account, customer account number, reversal category or entered currency.
Use this report in conjunction with your customer payment processing processes.

From/To Reversal Date
The range of receipt reversal dates to include in the report.
Reversal Category
Review receipt reversals for this reversal category only.
Reversal Reason
226
If you selected a reversal category, review receipt reversals for this reversal reason within a reversal category only.
Receipt Type
Standard or Factoring.
Debit Memo Reversal Number
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.
Paying Customer The name of the paying customer.

Paying Customer Account The account number of the paying customer.

Customer Site The identier of the customer site.

Remiance Bank The name of the remiance bank.

Remiance Bank Account The number of the remiance bank account.

Receipt Number The number of the receipt that was reversed.

Receipt Date The date that the receipt was created.

Reversal Date The date that the receipt was reversed.

Receipt Type Standard or Factoring.

Reversal Category The category of reasons why a receipt was reversed.

Reversal Reason The specic 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

Receipt Currency The entered currency of the receipt.

Receipt Accounted Amount The amount of the receipt in the ledger currency.

This table describes the row headings in the Reversed Receipts Report.
[Remiance Bank Name] Total Total of all reversed receipts for a remiance 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.

FAQs for Reverse Receipts

What's the dierence between reversing a receipt, unapplying a receipt, and deleting
a receipt?
You reverse a receipt when no payment was received from the customer for the receipt amount. Reversing the receipt
creates reversal journal entries in the general ledger and reopens all of the debit and credit items that were closed by
the original receipt.
You unapply a paid receipt either to return payment to the customer or to reapply a receipt applied in error to the
correct transaction. If you unapply a receipt to return payment to the customer, either with a refund or an on-account
credit, you must create a credit memo against the original transaction that was closed by the receipt application.
You can delete manual receipts that were created but not yet applied to transactions. You can delete automatic receipts
belonging to an automatic receipt batch that hasn't yet been approved. When you delete a receipt from a batch, the
transactions closed by the receipt become available for automatic receipt selection.
Why can't I reverse a receipt?

There are certain conditions that prevent you from reversing a receipt or initiating a debit memo reversal.
You can't reverse a receipt if any of the following are true:
• The receipt is already reconciled in Oracle Fusion Cash Management.
• A chargeback was created against the receipt, and a receipt, adjustment, or credit memo was created against
the chargeback.
228
• 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 remied.
• 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:
• The receipt is already reconciled in Oracle Fusion Cash Management.

• The receipt is a miscellaneous receipt.
• The receipt is unidentied (no customer name or account number).
Manage Lockbox
Lockbox Standard Receipt Import Process
Use the lockbox standard receipt import both to create receipts in Receivables from data supplied by your remiance
bank and to apply the receipts to customer transactions.
The lockbox process has three steps:
• 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, unidentied, or on-account
amounts.
229
This gure illustrates the lockbox process:
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:
• No duplicate entries exist.

• Customer and receipt information is valid.
• Amounts to apply do not exceed the receipt amount.
230
• Columns in the AR_PAYMENTS_INTERFACE_ALL table reference the correct values and columns in
Receivables.
If the receipt and transaction currencies are dierent, Receivables also requires specic 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
Lockbox and Cross Currency Receipts

You can use lockbox to import and apply receipts when the currencies of the receipt and the transaction are dierent.
Conversion Rate Information

Lockbox uses these eld types in the bank transmission le to apply cross currency receipts between currencies that
don't have a xed rate relationship:
• Transaction Amount Applied (amount_applied): The amount of the receipt to apply in the transaction currency.
• Receipt Amount Applied (amount_applied_from): The amount of the receipt to apply in the receipt currency.
• Conversion Rate (trans_to_receipt_rate): The conversion rate between the two currencies.
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
amount_applied_from / trans_to_receipt_rate = amount_applied
The formula lockbox uses to apply a cross currency receipt is:

Transaction Amount Applied * Conversion Rate = Receipt Amount Applied
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
If both the conversion rate and either the Transaction Amount Applied or the Receipt Amount Applied are missing,
lockbox uses the seing 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 dierent combinations of
information provided in the bank transmission le:
Information Provided in Transmission Action Result

File
• 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.

Calculate the missing value or values. Apply the receipt.

Fixed rate relationship:
• One or two of Conversion Rate,

Transaction Amount Applied,
Receipt Amount Applied
Calculate the missing value. Apply the receipt.

Floating rate relationship:
• Conversion Rate
• Transaction Amount Applied or
Derive the xed conversion rate and Apply the receipt.

Fixed rate relationship: calculate the missing value.

• If the rate is dened, use it to derive

Floating rate relationship: Refer to the Cross Currency Rate Type the missing value and apply the
system option. receipt.
• If the rate is not dened, reject the
receipt.
Rounding Remiance Amounts

The method your customer uses to sum payment amounts in the bank transmission le can aect whether lockbox fully
applies a cross currency receipt.
Discrepancies in Rounding Amounts

Your customer has three invoices, each for 1000 EUR. The customer adds the invoice amounts and then converts the
total to USD. The conversion rate used is: 1 EUR = .860956 USD.
The result of adding the invoice amounts and converting the total is:
232
Transaction * Rate = Amount (in receipt currency)
3000.00 EUR * .860956 = 2,582.87 USD (rounded)
Although this method is mathematically correct, lockbox uses a dierent procedure to calculate remiance 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)
1,000.00 EUR * .860956 = 860.96 USD (rounded)
1,000.00 EUR * .860956 = 860.96 USD (rounded)
1,000.00 EUR * .860956 = 860.96 USD (rounded)
The total is 2,582.88 USD.
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 remiance amounts are calculated using the same method as lockbox.
Process Receipts Through Lockbox Execution Report

Use the Process Receipts Through Lockbox Execution Report to review the results of a lockbox transmission.
Use this report in conjunction with your lockbox receipt processing.
Selected Program Parameters

New Transmission
• Yes: To import a new bank le.
• No: To resubmit an existing lockbox transmission.
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
resubmiing.
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
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 specied 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 dened the accounting date in the lockbox as Constant Date, enter an accounting date.
• If you dened 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.
Complete Batches Only

• Yes: Only transfer the receipts in a lockbox batch if all records pass the validation step.
• No: Transfer any receipts within a batch that pass validation, even if others are rejected.
Allow Payment of Unrelated Invoices

• Yes: Apply receipts to the debit items of unrelated customers.
• No: Apply receipts only to the debit items of customer accounts with whom you have an account relationship.
Post Receipt with Invalid Transaction Reference as Unapplied

• Yes: Allow the import of a receipt that is applied to more than one transaction, even if one or more of the
transactions are invalid. The unapplied portion of the receipt is transferred as an unapplied amount.
You can later manually apply any unapplied amounts to transactions.
• No: Only allow the import of a receipt that is applied to more than one transaction when all of the transactions
are valid.
Submit Post Receipts

• Yes: Apply receipts in the lockbox transmission and update the customer balance.
• No: Process receipts without applying them to transactions. Select this option if you want to review and edit
receipts before applying them to customer open debit items.
Number of Instances to Process AutoApply
234
Enter the number of AutoMatch workers submied 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:
• Transmission Record Count

• Records Transferred to Date
• Records Transferred this Run
• Transmission Amount
• Amount Transferred to Date
• Amount Transferred This Run
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
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
FAQs for Manage Lockbox

Can one customer pay for another customer's transactions using lockbox?
Yes, if you have set up a relationship between these customers, or if the Allow payment of unrelated transactions
system option is enabled for this lockbox submission. The paying customer should be identied by a customer or MICR
number on the receipt record. Otherwise, if you are using AutoMatch when applying a receipt from Customer A to a
transaction from Customer B, the receipt is designated as paid by Customer B. Additionally, all transactions listed to be
paid by one receipt must belong to the same customer, otherwise lockbox imports the receipts as Unapplied.
If the Allow payment of unrelated transactions system option is not enabled, you must set up a relationship between
the customers before you can make applications in this way.
Why are there duplicate transactions in a lockbox?

Transactions numbers are only required to be unique within a transaction source. A customer can have duplicate
transaction numbers as long as they belong to dierent transaction sources. However, lockbox can't automatically apply
a payment to these transactions.
If a customer has more than one transaction with the same number within a lockbox transmission, then lockbox can't
determine to which transaction to apply the payment. The receipt is left in one of these statuses:
• Unapplied: If the customer account number or MICR number is provided.

• Unidentied: If the customer account number or MICR number is not provided, and there are not successful
matching recommendations.
You must apply receipts to these transactions manually.
Can lockbox overapply a receipt?

Yes, if you set the Overapplication in Lockbox Allowed prole option to Yes. If the transaction type of the debit item
allows overapplication, then lockbox applies the receipt and, if the payment exceeds the balance due, changes the sign
of the debit item.
If the transaction type does not allow overapplication, then lockbox leaves the remaining amount unapplied.
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
Considerations for manual refunds include:
• Rules for Issuing Refunds

• Non-Credit Card Refunds
• Credit Card Refunds
• Refunds for Overpayments
Rules for Issuing Refunds

Before you can issue a refund you must unapply the receipt amount. You can either unapply the amount of the refund
from one or more application lines on the receipt, or you can apply an on-account credit memo in the amount of the
refund to the original receipt.
These rules apply to issuing refunds:
• 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 remied or cleared.
• You can't issue a credit card refund unless the customer payment was made by credit card.
Non-Credit Card Refunds

You can issue refunds for receipts or on-account credit memos.
To issue a non-credit card refund:
1. Unapply the amount to refund from the receipt or credit memo.

2. Issue the manual refund, and enter the values required by Payables. This refunds the amount to the original
receipt customer.
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.
Credit Card Refunds

You can issue credit card refunds for receipts only. Credit card refunds update credit card transactions that didn't
complete, for example, the customer returned the product that was originally charged to the credit card number; or a
charge was mistakenly applied to an incorrect credit card number.
To issue a credit card refund:
1. Unapply the credit card amount to refund from the receipt.

2. Issue a manual credit card refund to create a negative miscellaneous receipt for the amount.
3. Run the Create Automatic Remiances program to remit the negative miscellaneous receipt and initiate the
refund.
Receivables submits a refund request directly to Payments to create the disbursement. Payments applies the refund to
the same credit card used on the original transaction.
237
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.
Refunds for Overpayments

During lockbox processing, Receivables identies overpayments after receipts are applied to transactions. Depending
on the details of your setup, Receivables can suggest for your review overpayment amounts as refunds to your
customers.
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
How Manual Credit Card Refunds Are Processed

You can refund all or part of a previously remied credit card receipt to your customer credit card accounts.
You issue a credit card refund against the unapplied receipt amount to generate a negative miscellaneous receipt. You
then run the Create Automatic Remiances program to process this negative receipt to transfer the funds from your
account back to the credit card of your customer.
Seings That Aect Manual Credit Card Refunds

These seings aect manual credit card refunds:
• Complete the funds capture setups in Oracle Payments:
◦ Dene formats
◦ Dene payment systems
◦ Dene system security options
◦ Integrate external payment systems
◦ Dene credit card brands
◦ Dene funds capture payment methods
◦ Dene funds capture process proles
◦ Dene internal payees
• Credit Card Refund Receivables Activity: Dene a Credit Card Refund Receivables activity. This activity identies
the general ledger clearing account to use to clear credit card refunds.
• Credit Card Refund Reversal Reason Lookups: Dene 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
• Credit Card Transaction Remiance Method: On the original credit card transactions, use a receipt class
with a remiance method of Standard. When you refund these payments, the credit card refund (negative
miscellaneous receipt) inherits the remiance method from the original receipt.
How Manual Credit Card Refunds Are Processed

The Create Automatic Remiances program passes the negative miscellaneous receipt information to Payments. The
Create Automatic Remiances program uses Payments to transfer funds back and forth between the credit card issuer
and your bank.
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, dene
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 remied.
If the negative miscellaneous receipt was not approved and remied, 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 remied, 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.
Reverse Receipts with Credit Card Refunds

You can reverse a receipt with a credit card refund application either before or after the negative miscellaneous receipt
was remied.
If the negative miscellaneous receipt was not approved and remied, 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 remied, 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 seled, 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
• Remiance Methods and Clearance Methods
239
• Funds Capture Process Proles
How AutoInvoice Processes Credited Amounts

Use automated receipt handling to manage imported credit memos using AutoInvoice against paid transactions. You
can set up Receivables to either refund the credited amount or place the credited amount on account.
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.
Seings That Aect Automated Receipt Handling for Credits

These seings aect automated receipt handling for credits:
• Transaction Source: Dene an imported transaction source and enable the Receipt Handling for Credits
option to indicate your enterprise policy. Assign this transaction source to the applicable imported credit
memos.
• Minimum Refund Amount Receivables system option: If you plan to process refunds, specify in the Minimum
Refund Amount eld in Receivables system options the minimum amount necessary for AutoInvoice to create
a refund.
• Receivables Activity: If you plan to process refunds, dene a Credit Card Refund receivables activity for credit
card refunds and a Refund receivables activity for non-credit card refunds. The receivables activity identies
the general ledger clearing account to use to clear the refund amounts.
• Credit Card Transaction Remiance Method: On the original credit card transactions, use a receipt class with a
remiance method of Standard.
• Transaction Type: The transaction type assigned to the debit items must be set to Natural application only. If
the transaction type of a debit item is set to Allow overapplication, then you must process the credit manually.
How Automated Receipt Handling Processes Credits

During AutoInvoice import, the process ow for automated receipt handling for credits is as follows:
1. AutoInvoice veries that the transaction source assigned to the credit memo has automated receipt handling
enabled.
2. AutoInvoice evaluates each credit memo and its associated transaction to determine eligibility for automatic
receipt handling. To be eligible:
◦ The transaction type of the paid transaction must be set to allow natural application only.
◦ The transaction must not be in doubt.
3. If eligible, then AutoInvoice unapplies the paid transaction from the receipt to be credited.
4. AutoInvoice creates the credit memo in the amount of the requested credit, and applies the credit to the
transaction.
5. If your policy is to automatically refund your customers, then AutoInvoice evaluates the receipt for refund
eligibility. To be eligible, the receipt must not be in doubt.
6. If eligible for refund, AutoInvoice creates the refund for all credit request amounts that are greater than or
equal to the value entered in the Minimum Refund Amount eld in Receivables system options.
AutoInvoice places on account any credit amount that is less than the specied minimum.
7. AutoInvoice applies the appropriate receivable activity to the receipt, as determined by the transaction source.
240
Transactions and Receipts in Doubt

AutoInvoice rejects a credit memo from automated receipt handling if one of the following conditions exists on the
transaction to be credited:
• The transaction type of the transaction is set to allow overapplication.

• An on-account credit memo was previously applied against the transaction.
• A regular or chargeback adjustment already exists against the transaction.
• The credit memo is imported against a transaction with a negative creation sign.
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:
• The receipt to be refunded hasn't been remied.

• Receipts with dierent payment types (ACH, cash, credit card) were used to pay the same transaction to be
credited.
• Installments exist on the transaction and are not fully paid.
• The receipt has an on-account credit memo against it.
Related Topics
• AutoInvoice Data Preparation
FAQs for Process Refunds

What happens if I apply a credit card refund to a receipt in a dierent currency?
If you apply a credit card refund to a receipt that is not in the ledger currency, then you must account for the exchange
gain or loss between the time of the original transaction and the time of the refund.
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 reect 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.
Process Bank Deposits
241
Considerations for Remiing Receipts

Remit receipts to your bank to initiate the transfer of payments from your customer bank accounts. You remit receipts
after your own internal approval, or approval and customer conrmation, if conrmation is required.
Considerations for managing remiances include:
• Standard Remiances
• Factored Remiances
• Seings for Remiance Batches
Standard Remiances
A standard remiance refers to the common practice of remiing 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 remiance 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 Remiances
A factored remiance 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 remiance method of the remiance batch as Factored. In addition, you can
only factor receipts assigned a receipt class with a remiance 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 conrmation, remiance, and clearance:
Action Accounting Entries
Conrm Receipts DR Conrmation CR Accounts Receivable

Factor Remiances DR Factoring CR Conrmation

Clear Receipts DR Cash DR Bank Charges CR Short Term Debt

Eliminate Risk DR Short Term Debt CR Factoring

242
Remiance Batch Seings

You can create one remiance batch per remiance bank account or clearing institution.
You can deposit receipts into remiance 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 remiing receipts in foreign currencies,
set the Conversion Rate Type prole option to a value other than User, because you can't specify a user-dened
conversion rate when remiing receipts.
To manage automatic remiance 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 remiance batches. To help determine the number to enter, review the log le for your largest automatic
remiance creation batch. Reduce this number only if you run out of rollback segments.
Related Topics
• Remiance Bank Accounts on Receipt Methods
Corrective Actions to Funds Transfer Errors

You can resolve funds transfer errors resulting from exceptions returned by Oracle Payments using the available
corrective actions.
The available corrective actions are:
• 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.
Clear Payment Information

You can remove the payment information from a transaction. This action raises a business event and clears the receipt
method from the transaction so that it is not eligible for selection during the next run of automatic receipts.
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 remiance 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 remiance
batch.
243
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
Automatic Clearing of Receipts

Use the Clear Receipts Automatically process to automatically clear remied receipts, and clear or eliminate risk on
factored receipts.
The Clear Receipts Automatically process manages the clearing process for both remied and factored receipts. The
receipts that you intend to clear with the Clear Receipts Automatically process must belong to a receipt class with a
clearance method of Automatic.
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.
Remied Receipts
Clearing remied receipts credits your cash account and debits your remiance or factoring account.
Remied receipts are cleared X days after their maturity date, where X is the number of clearing days dened 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 dened for the receipt method/bank account combination assigned to the receipt.
Factored receipts are cleared immediately on the remiance 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.
Reports for Process Bank Deposits

Bank Risk Report
Use the Bank Risk Report to see the receipts that are currently at risk with your remiance bank. A receipt is deemed to
be at risk if you have factored it with a bank or a clearing house, but are still liable for the amount on the receipt until its
maturity date (for example, receipts that have been factored but not risk eliminated).
When you run the Bank Risk Report, you must enter the remiance bank branch and bank account for which you want
to print remiances.
Report Output
This table describes the two important row headings in the Bank Risk Report.
244
Total for Remiance The total amount in the ledger currency of all receipts in each remiance batch.

Total Report The total amount of all remiances.

Clear Receipts Automatically Execution Report

Use the Clear Receipts Automatically Execution Report to review a run of the Clear Receipts Automatically program.
The Clear Receipts Automatically program clears remied receipts and either clears or eliminates risk on factored
receipts. Receipts eligible for clearance by this program must have a receipt class with a clearance method of Automatic
Clearing.
Review this report each time you clear receipts using the Clear Receipts Automatically program.
Report Parameters
Clear Remied Receipts
Indicate whether to clear remied receipts.
Clear Discounted Receipts
Indicate whether to clear factored receipts.
Eliminate Bank Risk:
Indicate whether to eliminate risk on cleared and factored receipts.
Clear Date
Specify the date to use as the clearance date for remied 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.
Conversion Rate Type
Enter the conversion rate type to use to determine the conversion rate. Conversion rate adjustments are made for
receipts that are in a currency dierent 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
Status The status of the receipt.

Receipt Number The number of the receipt.

Maturity Date The maturity date of the receipt.

Payment Method The receipt method for the receipt.

Currency The currency of the receipt.

Amount The amount of the receipt in the entered currency.

Ledger Amount The amount of the receipt in the ledger currency.

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
Overview of the Receipts Awaiting Bank Clearance Report

This topic contains summary information about the Receipts Awaiting Bank Clearance Report.
Overview
The Receipts Awaiting Bank Clearance Report lets you review receipts waiting to be cleared by your remiance bank.
Key Insights
The report provides a separate section for each currency included in the output, and sorts information within each
currency section by remiance bank account and remiance batch date.

The following table lists frequently asked questions about the Receipts Awaiting Bank Clearance Report.
FAQ Answer

Who uses this report? Financial Manager to analyze risk.

When do I use this report? To review all receipts waiting to be cleared by your remiance bank.



247
Receipts Awaiting Bank Clearance Report

Use the Receipts Awaiting Bank Clearance Report to review receipts waiting to be cleared by your remiance bank.
The report includes both automatic and manual receipts that have been remied but not cleared, or that have been
conrmed and require bank clearance but do not require remiance.
Run this report in accordance with your regular customer payment business process.

Bank Account Name
Report for this bank account only, if specied.
Currency
Report for this currency only, if specied.
Order By
• Maturity Date
• Receipt Number
• Remiance 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 remiance bank account and remiance batch
date, and provides subtotals by remiance bank account and remiance 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 remiance 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.
Remiance Bank Account Name The name of the remiance bank account for the applicable receipts.

Remiance Batch Date The date the remiance batch was created for the applicable receipts.

Maturity Date: The maturity date of the receipt.

Remiance Method The remiance method for the applicable receipts.

Receipt Method The receipt method for the applicable receipts.
248


Amount The amount of the receipt.

This table describes important row headings in the Receipts Awaiting Bank Clearance Report.
Currency The section title for a particular receipt currency.

Total for Remiance Batch Date The total amount of all receipts for the given batch date.

Total for Remiance Bank Account The total amount of all receipts for the given remiance 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
Overview of the Receipts Awaiting Remiance Report

This topic contains summary information about the Receipts Awaiting Remiance Report.
Overview
The Receipts Awaiting Remiance Report lets you review receipts awaiting remiance to your bank.
Key Insights
The report runs on both automatic and manual receipts. Once a receipt is approved for remiance it will no longer
appear on the report.

The following table lists frequently asked questions about the Receipts Awaiting Remiance Report.
FAQ Answer

Who uses this report? Financial Manager to analyze the overall remiance status.
250
FAQ Answer

When do I use this report? To review all receipts requiring remiance to your bank.



Receipts Awaiting Remiance Report

Use the Receipts Awaiting Remiance Report to review receipts awaiting remiance to your bank. You can either review
all receipts or receipts that are in a certain stage of the remiance process. By default the report includes receipts that
have started but not yet completed the creation or approval process.
The report runs on both automatic and manual receipts that require remiance. Automatic receipts can only appear on
the report if they do not require conrmation or if they require conrmation and are conrmed.
Once a receipt is approved for remiance it will no longer appear on the report.
Run this report in accordance with your regular customer payment business process.

Order By
• Maturity Date
• Receipt Number
• Remiance Bank (the default, if no value selected)
Status
Select the status of the transactions to include in the report:
• Available for Remiance: Include all receipts available for remiance.

• Creation Completed: Include receipts that have been selected for remiance but have not been approved.
• Deletion Completed: Include receipts that have been deleted.
• Started Creation: Include receipts that have started, but not completed, the remiance creation process.
• Started Approval: Include receipts that have started, but not completed, the remiance approval process.
• Started Deletion: Include receipts that have started, but not completed, the deletion process.
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 remiance, there is a separate section for each remiance status within
each currency.
251
By default the report sorts the receipts within each currency section by remiance bank account, and provides subtotals
by receipt method, remiance method, remiance bank account and remiance 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 Remiance Report.
Remiance Bank Account Name The name of the remiance bank account for the applicable receipts.

Customer Bank The name of the bank associated with the customer.

Maturity Date The maturity date of the receipt.

Remiance Method The remiance method for the applicable receipts.

Receipt Method The receipt method for the applicable receipts.


Amount The amount of the receipt.

This table describes important row headings in the Receipts Awaiting Remiance Report.
Currency The section title for a particular receipt currency.

Status The section title for a specic remiance status within a currency section.

Total for Receipt Method The total amount of all receipts with a given receipt method.

Total for Remiance Method The total amount of all receipts with a given remiance method.

Total for Remiance Account The total amount of all receipts for a given remiance bank account.

Total for Status The total amount of all receipts with a given remiance status for a receipt currency.
252

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.

FAQs for Process Bank Deposits

Why can't I add receipts to a remiance batch?
For one of these reasons:
• Automatic receipts weren't fully applied. Because automatic receipts are created against specic transactions,
you can't remit receipts until they are fully applied.
• Incorrect receipt class. You can only include receipts in a remiance batch with receipt methods that have a
receipt class that requires remiance. A receipt class requires remiance if the remiance method is Standard,
Factoring, or Standard and Factoring.
Why can't I change the remiance bank on the receipt?

Because the primary ledger is set to enable document sequencing at the legal entity level.
The receipt was assigned the legal entity of the remiance bank account belonging to the receipt method, and a
document number was generated for the receipt for that legal entity. Changing the remiance bank would change the
legal entity assignment and invalidate the document number.
Why can't I override a receipt's remiance bank account?

Three seings control the override of a receipt remiance bank account with the remiance batch bank account.
These seings are:
• Ignore override option on the remiance batch.

• Allow override option on the receipt.
• Override bank option on the receipt remiance bank.
If you enable the Ignore override option on the remiance batch, Receivables replaces the remiance bank information
on the receipt with the remiance batch bank information and includes the receipt in the remiance batch, without
reviewing either the receipt Allow override option seing or the remiance bank Override bank option seing.
If you don't enable the Ignore override option on the remiance batch, Receivables still replaces the remiance bank
information on the receipt with the remiance batch bank information and includes the receipt in the remiance batch
under these conditions:
• Allow override option on the receipt is enabled.
Note: If the Allow override option on the receipt is not enabled, Receivables includes the receipt in
the remiance batch only if the receipt remiance bank is the same as the remiance batch bank.
253
• Override bank option on the receipt remiance bank is enabled.
In both cases, Receivables veries that both the receipt and the batch remiance banks have the same general ledger
accounts dened for remiances, and for unapplied, unidentied, and on-account receipts.
254
Using Receivables Credit to Cash Manage Funds Capture
3 Manage Funds Capture
How Authorizations for Credit Cards Are Processed

Oracle Fusion Payments processes authorization requests that are received from source products. An authorization is a
real-time process that:
• Validates credit card information

• Reserves funds through the payment processor and issuing bank
Seings That Aect Authorizations for Credit Cards

The following table describes the options that aect authorization processing:
Page or Dialog Box User Interface Element Action
Create or Edit Funds Capture Process Formats tab, Authorization section: Controls the formats and transmission
Proles Page Outbound Format choice list and Inbound congurations used to communicate with
Response Format choice list. the payment system.

Accounts tab: Authorization Transmission
Conguration 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 prole 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 Species 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
How Authorizations for Credit Cards are Processed

The following diagram illustrates the steps performed in the authorization process.
Source Product Oracle Fusion Payments Payment

System and
Request Issuing Bank
Route Transaction to Payment System
Start Authorization
Perform Extract and Format Operation
Validate
Open Connection with Payment System Payment
Instrument
Reserve
Receive Payment System Response
Funds
Perfom Error- Send Results Update

Handling Notification Authorization Status
Store Authoriztion Reference
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 prole.

Route transaction to payment Routing rules are applied in the order of their priority. Payments performs selements or
system. refunds through the same payment system used for authorizations.

256
Step Description
Perform extract and format

operation. This process:

• Extracts data from Payments tables
• Uses Oracle Business Intelligence Publisher (Oracle BI Publisher) to format the extracted
data into a message that is understood by the payment system.
Open connection with payment

system. Payments:

• Opens a connection with the payment system using transmission information specied
in the funds capture process prole
• Sends the formaed authorization request
Validate payment instrument.

The payment system or the issuing bank:
• Validates the credit card

• May perform a fraud checking service
• Ensures that the credit card is active
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.

Update authorization status.

Authorization information received from the payment system is stored in the Transaction
Authorization Entity table owned by Payments. This table creates a unique reference identier
for 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 prole and payment system
The preceding information is used during the selement process.
Send results notication.

Payments:
• Noties Receivables of the success or failure of the transaction authorization.

• Sends the unique reference identier for the authorization to the source product.
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
How Selement Batches Are Processed

Oracle Fusion Receivables starts the selement process, and Oracle Fusion Payments seles the transactions.
Selements received by Payments from Receivables are stored and later built into selement batches for transmission
to your processor or payment system. During the selement process, captured funds are processed and deposited into
the rst party payee's bank account. First party payees are organizations within your company that receive payments
from customers who pay with credit cards or bank account transfers.
Note: If you use a gateway payment system, individual selements, rather than selement batches, are
submied directly to your payment system.
Seings That Aect Selement Batches

The following table lists the options that aect selement batch processing.
Pages Tab Section User Interface Element
Create or Edit Funds Capture Formats Selement • Outbound Format

Process Proles choice list
• Inbound Response
Format choice list
Create or Edit Funds Capture Formats Selement Response • Outbound Format

Process Proles Processing choice list
• Acknowledgment
Parser choice list
Create or Edit Funds Capture Creation Rules Selement Grouping Rules All check boxes
Process Proles

Create or Edit Funds Capture Creation Rules Selement Limit • Amount choice list
Process Proles • Conversion Rate Type
choice list
• Number of
Selements eld
Create or Edit Funds Capture Accounts Selement Transmission • Conguration choice

Process Proles list
• Acknowledgment
Transmission
Conguration choice
list
258
How Selement Batches are Processed

Part 1 of the selement process ow, as illustrated in the gure, includes the creation of a selement transaction during
the Receivables remiance process. This assumes that authorization was already performed.
Part 2, as illustrated in the gure, includes the grouping of individual selements into batches and their submission to
the payment system. Part 2 is separate from Part 1 and begins when the Create Selement Batches process is manually
run or scheduled.
259
Part 3, as illustrated in the gure, includes the receipt of the selement batch acknowledgment. Part 3 is separate from
Part 2 and begins when the Retrieve Selement Batch process is manually run or scheduled.
Oracle Fusion Receivables Oracle Fusion Payments

Receive Funds Capture Process
Start Part 1 Remit Receipts
Requests
Read Funds Capture Process

Profile and Payment System
Receive
End Part 1 Settlement Validate Settements
Status
Start Part 2
Group Individual
Settlements into Batches
Extract and Format Settlement

Batch Data
Transmit Settlement Batch to

Payment System
End Part 2
Retrieve
Start Part 3
Acknowledgments
Process Status and Update Settlements
End Part 3
The selement process for processor payment systems includes the steps described in the following table.
Step Description
Remit receipts. During receipt remiance, specically during the approval of a remiance batch, Receivables
submits corresponding selements requests as a funds capture process request to Payments.

260
Step Description
Receive funds capture process

requests. Funds capture process requests received by Payments include:

• Information identifying the request
• One or more selements or credits
The funds capture process request contains selements that need funds captured
electronically.
Read funds capture process prole For each selement, Payments reads the funds capture process prole and the payment
and payment system for each system information, as determined during the routing of the initial authorization transaction.
selement. Payments uses this information in subsequent processing.

Validate selements. 1. Payments validates all the selements sent as part of the funds capture process request
to ensure it has all the information required for payment processing.
2. Payments stores the selements in the database. The initial status of the selement
validation and storage is returned to Receivables.
Group individual selements into A selement batch is selement information from one or more funds capture process requests
batches. that's formaed and transmied to a payment system for selement.

Payments processes selements from all submied funds capture process requests and
groups them by payment systems and other grouping rules to create selement batches.
Optional grouping rules are set in the funds capture process prole.

Extract and format selement batch

data.
1. Payments extracts selement batch data into an XML message.
2. It integrates with Oracle Business Intelligence Publisher (Oracle BI Publisher) to format
the XML message into a payment system format, as specied in the prole.
Transmit selement batch to After the selement batch is formaed, it's transmied to the payment system for processing
payment system. and capture of funds as specied in the prole

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
selements. selements. Receivables doesn't update receipt status based on this information, but restricts
follow-on transactions, such as refunds.

Examples of Selement Grouping Rules

Selement grouping is congured by selecting one or more check boxes in the Selement Grouping Rules section on
the Create Funds Capture Process Prole page. Selection of selement grouping aributes species that selements
with the same aribute are included in a unique selement batch when that prole is used. The following scenarios
261
illustrate how selement grouping rule options are used to group selements into selement batches using a specic
funds capture process prole.
Funds Capture Process Prole 1

In this example, Funds Capture Process Prole 1 has the following selement grouping options selected:
• Business unit
• First-party legal entity
• Selement date
Create Selement Batches

During funds capture transaction processing, the Create Selement Batches program selects the selements listed in
the following table.
Selement Amount External Payer Business Unit First-Party Legal Selement Date
that Owns the Entity that Owns
Transaction the Transaction
A 1000 USD Customer 1 California North America February 1, 2012

B 250 USD Customer 2 California North America February 1, 2012

C 500 USD Customer 3 Oregon North America February 1, 2012

D 750 USD Customer 4 California North America March 1, 2012

The Create Selement Batches program then groups the selements into the following selement batches:
Selement Batch 1
Selement Batch 1 contains Selements A and B because both selements have the same selement grouping
aributes as follows:
• Business unit = California

• First-Party legal entity = North America
• Selement date = February 1, 2012
262
Selement Batch 2
Selement Batch 2 contains Selement C because it has the following selement grouping aributes:
• Business Unit = Oregon

• Selement date = February 1, 2012
Selement Batch 3
Selement Batch 3 contains Selement D because it has the following selement grouping aributes:
• Business Unit = California

• Selement date = March 1, 2012
How Selement Transaction Files Are Merged into One

Selement Batch
A selement is a funds capture transaction that moves funds from the cardholder account or the bank account owner
into the internal payee's account. Internal payees are your company's business units that receive payments from
payers, such as customers, by credit card payments or direct debits to bank accounts. A selement batch is a group
of selements and credits that are sent to the payment system together in a le. Selement batches are generally
used with processor payment systems, which interact with banks and card institutions, such as Visa and MasterCard to
process nancial transactions.
If your company has multiple divisions, each division is represented by a separate payment system account. A payment
system account contains a relationship-specic value for each of the aributes required by the payment system. For
example, your payment system may require a Submier ID and Submier Password to be included in any message sent
to it. Each aribute is represented by a seing on the payment system account.
Seings That Aect Selement Transaction Files

The values for the following payment system account seings on the Edit Payment System Accounts page aect the
merger of selement les into one batch:
• Presenter's ID
• Submier's ID
263
If the values for the preceding payment system account seings are the same, selement transactions are grouped into
one selement batch. This occurs even when the following payment system account seings have dierent values:
• Division Number
• Merchant Name
How Selement Transaction Files Are Merged into One Selement

Batch
Processor payment systems accepts a daily limit of selement batch les from deploying companies. Large companies
may generate a large number of daily selement batch les that exceed the payment system's limit. To counteract
this constraint, Oracle Fusion Payments enables you to merge selement transactions of dierent payment system
accounts into a single selement batch le.
Typically, separate selement batch les are created for each payment system account. Whether you generate
selement 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 prole
• Payment system account
Oracle Payments Funds Capture Predened Reports

Oracle Payments provides the following funds capture predened reports:
• Funds Capture Accompanying Leer Formats
• Funds Capture Authorization and Selement Formats
• Funds Capture Payer Notication Formats
All of the preceding reports are:
• Processes that result in a formaed le

• Formaed using a specic template
• Manually generated, if opted, using the Scheduled Processes page
• Automatically generated, if opted, using setup pages
Running Funds Capture Reports Manually

To manually run Payments reports, perform the following steps from the Scheduled Processes page using the
Navigator menu.
1. Click the Schedule New Process buon.

2. Search on the Process Name.
3. Enter the applicable parameters.
264
4. Enter the applicable process options and schedule.

5. Click the Submit buon.
Running Funds Capture Reports Automatically

The following table lists funds capture reports with their corresponding processes that automatically run after you select
specic options on the applicable page.
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
Report: Funds Capture Formats authorizations, Automatically runs. Selement batches.

Authorization and Selement selements, and selement
Formats batches, groups selements
into batches, and submits
Process: Create Selement them to payment systems.
Batches

Report: Funds Capture Payer Creates payment notications Document.

Notication Formats that can be faxed, E-Mailed, Location: Create Funds
or printed and mailed to Capture Process Prole
Process: Send Receipt of external payers after the page, Formats tab, Payer
Payment Notications selement or selement batch Notication section.
is transmied to inform them
of a funds capture transaction Option to select:
that will charge their credit Automatically submit at
card or bank account. selement check box.

Report: Funds Capture Creates an accompanying Document.

Accompanying Leer Formats leer for a direct debit Location: Create Funds
selement batch le that your Capture Process Prole page,
Process: Selement Batch company either prints and Formats tab, Selement
Accompanying Leer mails to the bank, or manually section.
transmits to the bank, along
with the selement batch le. Option to select:
Accompanying Leer
Format check box.
ISO 20022 Direct Debit Prenotications

An ISO 20022 direct debit prenotication is a wrien or electronic leer using the required ISO 20022 message
standard for SEPA countries. A prenotication must be sent to your customer ve days in advance of collection. The
prenotication informs customers of each upcoming direct debit from their accounts. You must notify your customer of
the amount and date of a planned ISO 20022 direct debit collection before you send instructions to your bank with the
relevant ISO 20022 debit authorization aached.
The prenotication provides advance warning to your customers and ensures that funds are available for collection. The
prenotication also allows your customer to reject a collection, if necessary, before selement.
265
This topic discusses the following aspects of prenotications:

• ISO 20022 format
• Generation
• Validation
• Delivery
ISO 20022 Format

Per ISO 20022 payment standards, the ISO 20022 direct debit prenotication leer must include the following
information:
• Debit authorization reference identier
• Debtor's bank account number
• Debtor's bank
• Direct debit currency must be euro only
• Direct debit amount
• Direct debit date
Generation
Before you can generate prenotications, 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, prenotications 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 prenotications for delivery to customers. Receivables
doesn't notify Payments when it generates prenotications. The following table describes the steps that the
Receivables user can perform to submit the Automatic Receipts Format Report.
Scenario Step Description Result
Generate prenotications while creating Automatic receipt batch is created,

automatic receipts. 1. Navigate to the Create Automatic approved, and formaed to generate
Receipt Batch page or to the Create prenotication leers.
Automatic Receipt Batch process in Oracle
Enterprise Scheduler.
2. Enter all required aributes.
3. Select the Create, Approve, and

Format options and submit the process.
Generate prenotications while approving Automatic receipt batch is approved and

automatic receipts. 1. Navigate to the Receivables Balances formaed to generate prenotication
work area. leers.

2. Open an automatic receipt batch that is
pending approval.
266
Scenario Step Description Result
3. Select the Approve and Format action.
Generate prenotications while conrming Automatic receipt batch is formaed to

automatic receipts. 1. Navigate to the Receivables Balances generate prenotication leers.
work area.
2. Open an automatic receipt batch that is

pending conrmation.
3. Select the Format action.
Validation
Prenotications don't undergo any validations.
Delivery
After generation, prenotications 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.
Prenotications are delivered according to the following guidelines for SEPA selement batches:
• A prenotication noties the debtor at least ve calendar days before collecting the payment, unless a dierent
time line has been agreed between you and the debtor.
• The lead time for submiing 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 submiing 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.
Note: Receivables doesn't notify Payments when it delivers prenotications.
You and your customer may agree to a frequency of prenotication delivery. For example, with a recurrent SEPA direct
debit, you can agree to send a prenotication once a year. This can only be done, however, if the amount to be collected
stays the same. Otherwise, a new prenotication must be sent to your customer.
ISO 20022 Payment Status Reports

An ISO 20022 payment status report, also known as an ISO 20022 direct debit acknowledgment, is an electronic
message format that is based on the ISO 20022 message format called CustomerPaymentStatusReport
(pain.002.001.03). The payment status report is sent by your bank or payment system to Oracle Fusion Payments.
This inbound acknowledgment noties you of the processing status of the ISO 20022 direct debit selement batch
transaction that you sent to your bank or payment system. Each selement transaction is accepted or rejected.
The payment status report conveys the processing status, either directly or by inference, of every ISO 20022 direct
debit selement received by your bank or payment system. The payment status message format allows banks to
267
specify an overall status for the direct debit selement batch and individual statuses for some or all of the transactions.
For example, it's possible for a direct debit selement 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:
• Positive: Received, Accepted, or Accepted with Change

• Pending
• Negative: Rejected
• Positive and negative: Partially Accepted
The use of the payment status report is always governed by a bilateral agreement between your company and the bank.
A bilateral agreement species how your company wants to receive acknowledgments from the bank, whether:
• Your company wants only one acknowledgment at any milestone.

• Your company wants to receive acknowledgments at each milestone within the clearing process, such as the
bank receiving the payment le, passing technical validations, passing business validations, and accepting or
rejecting transactions.
A bilateral agreement can also specify whether your company wants to receive:
• An acknowledgment for accepted transactions only

• An acknowledgment for rejected transactions only
• An acknowledgment that has details of both accepted and rejected transactions
Payments processes the payment status report message according to the message structure specied 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 selement 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:
• ACCP: Accepted with technical validation

• ACSP: Accepted by the clearing system
• ACWC: Accepted with a change
268
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
Rejection and Refund Transactions

ISO 20022 direct debit collections that are diverted from normal execution before interbank selement are known
as rejection transactions. Rejection transactions and their associated rejection reasons appear in the payment status
report. Payments supports the following rejection and refund transactions:
• Invalid format of the ISO 20022 direct debit collection message
• Incorrect IBAN check digit
• Closed account
• Deceased customer
• Nonacceptance of direct debits by customer account
• Claim by your customer for reimbursement of a direct debit to its account
ISO 20022 Direct Debit Transaction Flow

The following table describes the point where the payment status report appears in the ow of ISO 2022 direct debit
transactions between Oracle Receivables, Payments, and Oracle General Ledger.
Step Receivables Payments General Ledger
1 Receivables creates a batch N/A N/A

of ISO 20022 direct debit
receipts.

2 Using the Auto-Remiance N/A N/A

Batch process, Receivables
submits the ISO 20022 direct
debit receipts to Payments for
processing.

3 N/A Payments creates a selement N/A

batch using an ISO 20022
SEPA or CGI selement format
and transmits the ISO 20022
direct debit collection message
to your bank or payment
system.

4 N/A Your bank or payment system N/A

acknowledges receipt of
the ISO 20022 direct debit
selement batch by sending
you a payment status report,
269
which is formaed as an XML

message and follows the
Customer Payment Status
Report (pain. 002.001.03)
format.

5 N/A To retrieve acknowledgments N/A

from your bank or payment
system, you can schedule
and run, typically once a day,
the Retrieve Funds Capture
acknowledgment process,
which is a link in the Tasks
pane of the Funds Capture
work area, Overview page.

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.
If View Output indicates

Successful, the ISO20022
direct debit selement or
selement batch transaction
was accepted by your bank
or payment system and the
payment processing status is
reected in the Status column
in the Search Results section
on the Manage Selements or
Manage Selement Batches
page.
If View Output indicates

Rejected, the ISO20022 direct
debit selement or selement
batch transaction was rejected
by your bank or payment
system and the payment
processing status is reected
in the Status column in the
Search Results section on
the Manage Selements or
Manage Selement Batches
page.
Payments noties Receivables

of the accepted or rejected
ISO 20022 direct debit
transactions.
7 Receivables updates the status N/A If the ISO 20022 direct debit
of its receipts according to the transactions are accepted, the
270
payment status information it funds are accounted for in

receives from Payments. Oracle Fusion General Ledger.

If the ISO 20022 direct debit
transactions are rejected,
the receipt amounts are
unapplied and register as
funds outstanding.

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
Batch Level Mapping

The following table lists the ISO 20022 batch level rejection code that can appear in an acknowledgment le that is
received from your bank or payment system, along with the corresponding Payments status code.
ISO Reason Code ISO Reason Code SEPA Reason IBY Batch Status IBY Status
Name (IBY_BATCHES_ALL.STATUS)
(IBY_TRXN_SUMMARIES_ALL.STAT
FF01 InvalidFileFormat Operation/ Transaction 1 (Transmission Error) 101 (Batch

code incorrect, invalid Transmission Error)
le format

Usage: To be used to
indicate an invalid le
format

Transaction Level Mapping

The following table lists the ISO 20022 transaction level rejection codes that can appear in an acknowledgment le that
is received from your bank or payment system, along with the corresponding Payments status codes.
ISO Reason Code ISO Reason Code Name SEPA Reason IBY Status
(IBY_TRXN_SUMMARIES_ALL.
STATUS)
AC01 IncorrectAccountNumber Account identier incorrect 5 (Payment System Error)

(invalid IBAN)
271
STATUS)
AC04 ClosedAccountNumber Account closed 19 (Invalid Bank Account)

AC06 BlockedAccount Account blocked 5 (Payment System Error)

Account blocked for Direct
Debit by the Debtor

AG01 TransactionForbidden Direct debit forbidden on this 5 (Payment System Error)

account for regulatory reasons

AG02 InvalidBankOperationCode Operation/ Transaction code 5 (Payment System Error)

incorrect, invalid le format

Usage: To be used to indicate
an incorrect operation/
transaction code

AM04 InsucientFunds Insucient funds 17 (Insucient Funds)

AM05 Duplication Duplicate collection Ignore. The original

transactions should be
acknowledged correctly.

BE01 InconsistentWithEndCustomer Debtor's name does not match 5 (Payment System Error)
with the account holder's
name.

FF01 InvalidFileFormat Operation/ Transaction code 5 (Payment System Error)

incorrect, invalid le format

Usage: To be used to indicate
an invalid le format

MD01 NoMandate No Mandate 5 (Payment System Error)

MD02 MissingMandatoryInformationInMandate
Mandate data missing or 5 (Payment System Error)
incorrect

MD07 EndCustomerDeceased Debtor deceased 5 (Payment System Error)

MS02 NotSpeciedReasonCustomerGenerated
Refusal by the Debtor 5 (Payment System Error)

MS03 NotSpeciedReasonAgentGenerated
Reason not specied 5 (Payment System Error)
272
STATUS)

RC01 BankIdentierIncorrect Bank identier incorrect 5 (Payment System Error)

(invalid BIC)

RR01 MissingDebtorAccountOrIdentication
Regulatory reason 5 (Payment System Error)

RR02 MissingDebtorNameOrAddress Regulatory reason 5 (Payment System Error)

RR03 MissingCreditorNameOrAddress Regulatory reason 5 (Payment System Error)

RR04 RegulatoryReason Regulatory reason 5 (Payment System Error)

SL01 DueToSpecicServiceOeredByDebtorAgent
Specic Service oered by the 5 (Payment System Error)
Debtor Bank

Note: The reason codes are stored in IBY_TRXN_SUMMARIES_ALL.BEPCODE table.
Logical Grouping in ISO 20022 SEPA and CGI Direct Debit

Messages
SEPA (Single Euro Payment Area) is a system that provides a standardized process for credit transfers, an improved
debit system, and a cheaper way for individuals and rms to make transactions within European member countries
or regions. The SEPA direct debit message format, which is based on ISO 20022 message guidelines, supports logical
grouping of transactions within a selement batch. A logical grouping refers to the number of selement batches and
transactions that are allowed in a transmission le. A selement batch is a group of transactions, typically credit card
selements or credits, which are grouped, formaed, and transmied to a payment system together in a le. Selement
batches are generally processed by a processor-model payment system.
For the SEPA direct debit message format, Oracle Fusion Payments supports the following three-level XML message
structure:
• Level 1: Group header

• Level 2: Payment information
• Level 3: Direct debit transaction information
The following logical groupings are allowed in each transmission le:
• Mixed Grouping: Each le contains several selement batches. Each selement batch contains several
transactions.
273
A group is created with the least common aributes. For example, if there are three transactions with the same
debtor but dierent 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 selement batch. The selement batch contains several transactions.
• Single: Each le contains several selement batches. Each selement batch contains only one transaction.
Note: Payments only supports mixed grouping per the SEPA requirements.
Level 1 - Group Header

The group header level of the SEPA direct debit message format contains selement batch information that maps to a
row in the IBY_BATCHES_ALL table. The group header is mandatory and repetitive. Repetitive means that one or more
blocks of group header information can be included in a SEPA direct debit message format le.
The group header contains elements such as the following:

• Message identication
• Creation date and time
• Number of transactions
• Control sum
• Initiating party
Level 2 - Payment Information

Payment information is the middle level of the SEPA direct debit message format. It contains aributes common to a
group of transactions. Transactions are grouped at the payment information level only if selected in the funds capture
process prole. Otherwise, the payment information level doesn't exist in the SEPA direct debit message.
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 identier
• Creditor legal entity
• Creditor business unit
• Creditor's bank account details
• Internal bank account
• Currency
• Charge bearer
• Creditor identication number
• Selement date
• Sequence type
• Service level
274
• 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 dier, however, in element denition,
depending on whether or not a debit authorization is used.
The following table describes dierences between the SEPA and CGI direct debit messages as they relate to the
denition 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 remiance bank account used on the
invoice.

Ultimate Creditor Creditor (First Party Legal Entity) per Creditor (First Party Legal Entity) per the
the invoice if dierent than debit invoice.
authorization.

When you select payment grouping on the Create Funds Capture Process Prole page, the transactions are grouped
within the selement 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 Prole page. The logical grouping elements are
the same for SEPA, as well as for CGI.
Level 3 - Direct Debit Transaction Information

Direct debit transaction information is the level of the SEPA direct debit message format that contains an individual
transaction for each selement batch. Each individual transaction maps to a row in the IBY_TRXN_SUMMARIES_ALL
table. The direct debit transaction information level is mandatory and repetitive. Repetitive means that one or more
blocks of direct debit transaction information can be included in a SEPA direct debit message format le.
The direct debit transaction information level contains elements such as the following:
• Payment identier details
• Payment amount
• Debit authorization details
• Ultimate creditor
• Debtor
• Debtor's bank account
• Purpose code
275
• Remiance 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 Prole 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.
Validations for ISO 20022 SEPA and CGI Direct Debit

Selement Messages
Oracle Fusion Payments provides two BI Publisher templates and two corresponding selement formats for the Single
Euro Payments Area (SEPA) and Common Global Implementation (CGI) versions of ISO 20022 direct debit selement
messages. Payments aaches validations to the ISO 20022 selement formats for SEPA and CGI to verify that required
data is present in the selement message formats.
The following table describes the validations that are aached to the ISO 20022 SEPA and CGI selement formats by
Payments.
20022 SEPA and CGI Selement Formats Supported by Payments
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:
• Debit authorization must be present

on the transaction.
Note: For SEPA transactions,

the debit authorization is
required, but for CGI it's not
required.

Yes Yes
Active debit authorization:
• Veries that the direct debit

authorization is active and that
the transaction date is greater
than the debit authorization
signing date and less than the debit
authorization cancellation date.
• Ensures that a one-o debit
authorization is never used more
than once.
276
Yes Yes
Veries that the following required elds
are present on a debit authorization:
• Authorization Reference Identier

• Authorization Signing Date
• Creditor Legal Entity
• Creditor Identier
Yes Yes
Veries the following data:
• Internal bank branch country exists.

• Customer's bank branch country
exists.
Yes No
Payments supports the following
additional SEPA validations:
• Veries that the Customer Bank

Account IBAN is not null.
• Veries that the Customer Bank
Branch BIC is not null.
• Veries that the Internal Bank
Account IBAN is not null.
• Veries that the Internal Bank
Branch BIC is not null.
• Veries that internal bank branch
country exists.
• Veries that customer's bank
branch country exists.
• Veries that the selement
currency is euro.
• Veries that the customer bank
account is in the SEPA zone.
• Veries that the Creditor Identier
structure is as follows:
◦ Position 1-2 lled with the

ISO country code.
check digit according to ISO
7064 Mod 97-10.
Creditor Business Code. If
not used, then lled with
ZZZ.
◦ Position 8 onward is lled
with the country-specic part
of the identier as a national
identier of the Creditor,
as dened by the National
Community.
277
No Yes
Payments supports the following
additional CGI validations:
• Veries that either the Customer

Bank Branch BIC or the Customer
Bank Branch Number is not null.
• Veries that either the Internal Bank
Branch BIC or the Internal Bank
Branch Number is not null.
Yes Yes
Veries the following data that is required
for the ISO 20022 direct debit format:
• Local Instrument is not null.

• Service Level is not null.
Yes Yes
Match payment system account aributes:
• If the transaction has no payee

legal entity name, then validate the
payment system account seing
ISO20022_IP_NAME.
• If the transaction has no
payee legal entity registration
number, then validate either
ISO20022_IP_BICORBEI or
ISO20022_IP_OTHERID payment
system account seings.
Set Up a Customer Bank Account

If you want to receive payments from your customers by EFT from their bank accounts, you can set up customer bank
accounts.
To set up a customer bank account, perform the following steps:
• Find your existing customer.

• Create a customer bank account.
• Provide additional customer bank account information.
• Optionally, add joint bank account owners.
• Optionally, specify intermediary accounts
278
Finding Your Existing Customer

Navigator > Receivables > Billing link > Overview page > Tasks pane > Customers section > Manage Customers
link > Manage Customers page.
1. In the Search section, enter your customer's name in the Organization Name eld or your customer's account
number in the Account Number eld and click Search. Your customer's details appear in the Search Results
section.
2. In the Search Results section, select the row that shows your customer's organization name.
Creating a Customer Bank Account

Determine whether you want to create a customer bank account at the customer level or at the customer site level.
To create a customer bank account, perform the following steps:

1. To create a customer bank account at the:
◦ Customer level, go to step 2.
◦ Customer site level, go to step 3.
2. Click the customer Account Number link in the Account Number column in the Customer Name: Accounts
section.
The Edit Account: Customer Name page appears. Go to Step 4 and continue.
3. Click the applicable Site Number link in the Site Number column in the Customer Name: Sites section.
The Edit Site: Customer Name page appears.
4. Select the Payment Details tab.
5. Select the Bank Accounts subtab.
6. Click Create.
The Create Bank Account page appears.
7. From the Country choice list, select the country in which the customer bank account resides. Validation of the
bank account is based on the country for which you create the bank account.
If the country of the customer bank account and the country of the bank account's branch through which the
payment is made is the same, then the payment is considered a domestic payment.
If the country of the customer bank account and the country of the bank account's branch through which the
payment is made is not the same, then the payment is considered an international payment.
8. In the Account Number eld, enter the bank account number.
9. From the Bank Name choice list, select the bank at which the customer bank account resides.
10. From the Branch choice list, select the branch where the bank account resides.
You can create a customer bank account for receiving domestic payments by check without specifying a bank
or branch. To receive electronic international payments, however, you must specify both a bank and a branch.
11. To receive international payments from a customer bank account, select Allow international payments.
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 seing up a customer bank
account in a European country.
279
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.
Providing Additional Customer Bank Account Information

To enter additional information regarding the customer bank account you are creating, perform the following steps on
the Create Bank Account page in the Additional Information section.
1. In the Account Sux eld, enter the value that appears at the end of the bank account number, if applicable.
Note: An account sux is required in some countries.
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 species the currency in which payments are made.
5. In the Check Digits eld, enter one or multiple digits.
Note: Only a few countries require check 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 identies a Federal agency as the customer.
Optionally, Adding Joint Bank Account Owners

To optionally add other customers to the customer bank account as joint bank account owners, perform the following
steps on the Create Bank Account page in the Account Owners section.
1. In the Account Owner eld, select a joint bank account owner from the list.
2. In the From Date eld, select a starting date for the joint bank account owner.
If the customer wants to share the bank account with another party, then there are multiple owners of the bank
account. For multiple bank account ownership, you must specify one owner as the primary owner. The primary
owner is the customer for whom you are creating the bank account.
A joint bank account scenario, for example, might be where two business units of the same company are
conducting business in a foreign country and they want to use a common bank account for receiving and
making payments.
3. To specify the primary bank account owner among multiple owners, click the green check mark and then click
the Primary eld in the applicable account owner row.
The check mark appears in the row you selected.
280
4. To add a row from which to select another joint bank account owner, click the green plus.
Optionally, Specifying Intermediary Accounts

You can specify intermediary bank accounts for this customer on the Create Bank Account page in the Intermediary
Accounts section. Intermediary bank accounts are used if there are restrictions on the transfer of funds between two
countries. You can specify an intermediary bank account to assist in the transfer of funds between the originator's bank
and the beneciary's bank.
How You Update Bank, Branch, and Bank Account

Numbers on External Bank Accounts
You can now edit the bank account number of external bank accounts in these modules:
• Suppliers
• Customers
• Expenses
• Payroll
• Bill Management
• Higher Education
• Human Capital Management
On the simplied bank account page, you can also update the bank and branch if you created the bank account with the
Oracle Cash Management prole option named Use Existing Banks and Branches set to Yes. When you update the bank
and branch, you must select the same prole option.
How You Create and Edit a SEPA Debit Authorization

A SEPA debit authorization is a paper or electronic document that authorizes you, as a SEPA-based creditor, or payee,
to collect payments throughout the SEPA region by debiting your SEPA-based customer's, payer's or debtor's, bank
account. As the creditor, you or your bank, as agreed to by you and your customer, initiate the collection of funds from
your customer's account. In turn, your customer instructs its bank to transfer funds directly to your bank.
Note: Both you and your customer must hold bank accounts within the SEPA region.
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
• 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.
Enter or Edit Debtor Details

SEPA debit authorizations require both you and your customer to specify the following identiers for your bank
accounts and bank:
• IBAN (International Bank Account Number): An alphanumeric sequence that conforms to the ISO 20022
standard for uniquely identifying an international bank account number. It contains the routing information
required to transfer a payment from one bank to another.
• BIC (Bank Identier Code): A universal method of identifying nancial institutions to facilitate the automated
processing of telecommunication messages in banking and related nancial environments.
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.
Enter or Edit Creditor Details

You must provide your unique creditor identication number in the XML message for SEPA direct debits and when you
create or edit a debit authorization.
The creditor identication number:

• Is issued by your bank
• Identies you as the creditor on the paper SEPA debit authorization
• Remains constant
• Proves that you can initiate a SEPA direct debit
• Varies in length between countries
• Contains a maximum of 35 characters
The creditor identication number remains the same over time to enable your customer and his bank to return to you
for refunds, complaints, or to conrm the existence of a SEPA debit authorization when you present a SEPA direct debit
collection notication.
Enter or Edit Debit Authorization Details

When you create a SEPA debit authorization, you can select a transaction type of Recurring or One-o.
• Recurring direct debits: Your customer authorizes regular direct debits that you initiate.
• One-o direct debits: Your customer authorizes collection of only one direct debit.
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
Another optional aribute 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:
• A debtor bank account

• A creditor legal entity
• A creditor identication number
• An authorization reference identier
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.
SEPA debit authorizations are date-specic. The following rules apply:
• 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.
Payments Mapping of ISO 20022 Direct Debit Message

Structure for SEPA and CGI
ISO 20022 is the platform proposed by the International Organization for Standardization (ISO) to develop all nancial
messages. This topic provides Payments data mapping information for SEPA and CGI implementations of the ISO
20022 direct debit message.
The ISO 20022 direct debit message structure contains the following blocks of message elements:
• Group header message elements

• Payment information message elements
• Direct debit transaction information message elements
Group Header Message Elements

The following table lists the group header message elements and Payments data mapping information for SEPA and
CGI implementations of the ISO direct debit message.
283
Message Element <XML Tag> ISO Element Number SEPA Implementation CGI Implementation
Mapping Mapping
Group Header <GrpHdr> 1.0 Set of characteristics Same as SEPA

shared by all individual
transactions included
in the message.

Message Identication <MsgId> 1.1 Selement Batch Same as SEPA

Number

Tag Structure:

MsgId>543</ MsgId>

Creation Date Time <CreDtTm> 1.2 File generation system Same as SEPA
date

Tag Structure:

<CreDtTm>20100406T23:
56: 55</CreDtTm>

Authorization <Authstn> 1.3 AOS element. Not Not supported

supported

Number Of <NbOfTxs> 1.6 Sum of number of Same as SEPA

Transactions transactions in le

Tag Structure:

<NbOfTxs>1</
NbOfTxs>

Control Sum <CtrlSum> 1.7 Total of the payment Same as SEPA

amounts

Tag Structure:

<CtrlSum>15027. 4</
CtrlSum>

Initiating Party <InitgPty> 1.8 Tag Structure: Same as SEPA

<InitgPty>

<Nm>SEPA_
INIT_NM</Nm>

<Id>

<OrgId>

<Othr>

284
Mapping Mapping
<Id>SEPA_
INT_IDNT</Id>

<Issr>SEPA_ INIT_
ISUR</Issr>

</Othr>

</OrgId>

</Id>

</InitgPty>

Name <Nm> 9.1.0 Mapped with the Same as SEPA

values dened in Legal
Entity.

Mapping:

Name INITIATING_
PARTY_NAME

Postal Address <PstlAdr> 9.1.1 AOS element. Not used Not supported for CGI.
[AOS element that can
be supported for free in
future.]

Identication <Id> 9.1.12 Not Applicable Same as SEPA

Organization Not Applicable 9.1.13 Not supported Payment System

Identication Identier seing
"ISO20022
Organization
Identication. "

Private Identication 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
Payment Information Message Elements

The following table lists payment information message elements and Payments data mapping information for SEPA
and CGI implementations of the ISO direct debit message.
Mapping proposal Mapping proposal )
Payment Information <PmtInf> 2.0 The Payment Same as SEPA

Information block
is mandatory and
repetitive. It is the
logical grouping
element. It contains,
among others,
elements related
to the Credit side
of the transaction,
such as Creditor or
PaymentTypeInformation
and
DirectDebitTransactionInformation
which contains, among
others, elements
related to the Debit
side of the transaction,
such as Debtor or
RemianceInformation.

Payment Information <PmtInfId> 2.1 System generated Same as SEPA

Identication Selement Group ID.
This is a system wide
unique key.

Tag structure:

<PmtInfId>543_ 1</
PmtInfId>

Payment Method <PmtMtd> 2.2 DD Same as SEPA

Tag structure:

<PmtMtd>DD</
PmtMtd>

Batch Booking <BtchBookg> 2.3 Value from FCPP Same as SEPA

Tag structure:

<BtchBookg>true</
BtchBookg>

286
Number of <NbOfTxs> 2.4 Number of transactions Same as SEPA

Transactions in the payment
information block

Tag structure:

<NbOfTxs>1</
NbOfTxs>

Control Sum <CtrlSum> 2.5 Sum of all the Same as SEPA

transactions in the
payment information
block

Tag structure:

<CtrlSum>1156. 34</
CtrlSum>

Payment Type <PmtTpInf> 2.6 Not Applicable Same as SEPA

Information

Instruction Priority <InstrPrty> 2.7 AOS element. Not Not supported

supported

Service Level <SvcLvl> 2.8 Not Applicable Same as SEPA

Code <Cd> 2.9 SEPA CGI

Tag Structure: Tag Structure:

<SvcLvl> <SvcLvl>

<Cd>SEPA</Cd> <Cd>XXXX</Cd>

</SvcLvl> </SvcLvl>

Proprietary <Prtry> 2.10 AOS element. Not Not supported

supported

Local Instrument <LclInstrm> 2.11 Not Applicable Same as SEPA

Code <Cd> 2.12 Can be set up at the Can be set up at the

payer level (primary payer level (primary
source) or FCPP source) or FCPP
(secondary source). (secondary source).
The only values are Values are as per the
CORE and B2B external codes list.

Tag structure: Tag Structure:

287
<LclInstrm> <LclInstrm>

<Cd>CORE</Cd> <Cd>XXXX</Cd>

</LclInstrm> </LclInstrm>

Proprietary <Prtry> 2.13 AOS element. Not Not supported.

supported.

Sequence Type <SeqTp> 2.14 Depending on the Depending on the

type of mandate the type of mandate the
following values are following values are
supported: supported:

If recurrent mandate If recurrent mandate
FRST/ RCUR/FNAL FRST/ RCUR/FNAL

If one o mandate If one o mandate
OOFF OOFF


<SeqTp>OOFF</ <SeqTp>OOFF</
SeqTp> SeqTp>

Category Purpose <CtgyPurp> 2.15 SUPP Leave Blank

Tag structure: At least one bank
(JPMC) does not
<CtgyPurp> populate Category
Purpose.
<Cd>SUPP</Cd>
Tag structure:
</CtgyPurp>
<CtgyPurp>

<Cd></Cd>

</CtgyPurp>

The choice of SUPP
is based on AR
Transaction Class.
Transaction Class
contains only Invoice,
Credit Memo, Debit
Memo, and the last
two don't t any ISO
purpose codes.

Alternately, this
could come from AR
Transaction Type.
However, there is
no easy way to map
those to ISO Purpose
codes without AR
enhancement.
288
Requested Collection <ReqColltnDt> 2.18 Selement Date Selement Date

Date
Tag structure: Tag structure:
<ReqdColltnDt>20100406</
<ReqdColltnDt>20100406</ReqdColltnDt>
ReqdColltnDt>

Creditor <Cdtr> 2.19 Name: Legal Entity Same as SEPA

Name on the Debit
Authorization

Postal Address: First
two lines of address of
Legal Entity

Identication: Not
supported

Country: Country of
Legal Entity

Tag structure:

<Cdtr>

<Nm>Vision
Operations</ Nm>

<PstlAdr>

<Ctry>US</ Ctry>

<AdrLine>475 Park
Avenue</ AdrLine>

</PstlAdr>

</Cdtr>

Name <Nm> 9.1.0 Not Applicable Same as SEPA

Postal Address <PstlAdr> 9.1.1 Not Applicable Same as SEPA

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
Building Number Not Applicable 9.1.6 AOS element that can Same as SEPA

Post Code Not Applicable 9.1.7 AOS element that can Primary address of the
the mandate.

Town Name Not Applicable 9.1.8 AOS element that can Primary address of the
the mandate.

Country Subdivision Not Applicable 9.1.9 AOS element. Not Primary address of the
supported. legal entity selected on
the mandate.

Country Not Applicable 9.1.10 Not Applicable Same as SEPA

Identication Not Applicable 9.1.12 AOS element that can Same as SEPA

Country of Residence <CtryOfRes> 9.1.33 AOS element. Not Primary address of the
supported. legal entity selected on
the mandate.

Creditor Account <CdtrAcct> 2.20 IBAN of the Internal Same as SEPA

Bank Account of the
creditor will be mapped
to this eld

Tag structure:

<CdtrAcct>

<Id>

<IBAN>IT60X0542811101000000123456</
IBAN>

</Id>

<Ccy>EUR</Ccy>

</CdtrAcct>


Type <Tp> 1.1.8 AOS element that can Same as SEPA

290
Currency <Ccy> 1.1.11 Not Applicable Same as SEPA

Name <Nm> 1.1.12 AOS element that can Same as SEPA


Creditor Agent <CdtrAgt> 2.21 BIC of the internal bank BIC of the internal bank
branch of the bank branch of the bank
account aached to the account aached 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.

Ultimate Creditor <UltmtCdtr> 2.23 Not supported at Same as SEPA

this level. Mapping
provided in Direct debit
transaction information
block.

Name <Nm> 9.1.0 Not supported at this Same as SEPA

level.

Postal Address <PstlAdr> 9.1.1 AOS element. Not Passed only when
supported. Ultimate Creditor
(UltCdtr) is populated.

Identication <Id> 9.1.12 Not supported at this Same as SEPA

level.

Organization Not Applicable 9.1.13 Not supported at this Same as SEPA

Identication level.

Private Identication Not Applicable 9.1.21 Not supported at this Same as SEPA
level.
291
Country of Residence <CtryOfRes> 9.1.33 AOS element. Not Not supported.

supported.

Charge Bearer <ChrBr> 2.24 SLEV Payer Bank Charge

Bearer
Tag structure:

<ChrgBr>SLEV</
ChrgBr>

Charges Account <ChrgsAcct> 2.25 AOS element. Not Not Used

supported

Charges Account Agent <ChrgsAcctAgt> 2.26 AOS element. Not Not Used
supported

Creditor Scheme <CdtrSchmeId> 2.27 Identication Creditor Same as SEPA

Identication Identier on the
Debit Authorization
populated by
Identication.

This data can be
present at payment
information or direct
debit transaction
information level.

Tag structure:

<CdtrSchmeId>

<Id>

<PrvtId>

<Othr>

<Id>1234</Id>

<SchmeNm>

<Prtry>SEPA</ Prtry>

</SchmeNm>

</Othr>

</PrvtId>

</Id>

</CdtrSchmeId>

292
Name <Nm> 9.1.0 AOS element. Not Same as SEPA

supported

Postal Address <PstlAdr> 9.1.1 AOS element. Not Same as SEPA

supported

Identication <Id> 9.1.12 Not supported in favor Same as SEPA

of Private Identier

Private Identication <PrvtId> 9.1.21 Tax identier of Same as SEPA

the creditor legal
entity selected on the
mandate.

Tag structure:

<PrvtId>

<Othr>

<Id>XXXX</Id>

</Othr>

</PrvtId>

Other <Othr> 9.1.27 Not supported in favor Same as SEPA


Direct Debit Transaction Information Message Elements

The following table lists the direct debit transaction information message elements and Payments data mapping
information for SEPA and CGI implementations of the ISO direct debit message.
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.

Payment Identication <PmtId> 2.29 The instruction The instruction

and the end to end and the end to end
identication are identication are
293
part of payment part of payment

identication identication


<PmtId> <PmtId>

<InstrId>AR110086</ <InstrId>AR110086</
InstrId> InstrId>

<EndToEndId>AR110086</ <EndToEndId>AR110086</
EndToEndId> EndToEndId>

</PmtId> </PmtId>

See Mapping See Mapping

Instruction <InstrId> 2.30 PSON number on the Same as SEPA

Identication receipt

End To End <EndToEndId> 2.31 PSON number on the Same as SEPA

Identication receipt

Payment Type <PmtTpInf> 2.32 Not Applicable Same as SEPA

Information

Instruction Priority <InstrPrty> 2.33 AOS element. Not Not supported

supported

Service Level <SvcLvl> 2.34 Not Applicable Same as SEPA

Code <Cd> 2.35 SEPA CGI


<SvcLvl> <SvcLvl>

<Cd>SEPA</Cd> <Cd>XXXX</Cd>

</SvcLvl> </SvcLvl>

Proprietary <Prtry> 2.36 AOS element. Not Not supported

supported

Local Instrument <LclInstrm> 2.37 Not Applicable Same as SEPA

Code <Cd> 2.38 Can be set up at the Can be set up at the

payer level (primary payer level (primary
source) or FCPP source) or FCPP
(secondary source). (secondary source).
294
The only values are Values are as per the

CORE and B2B external codes list.

Tag structure: Tag Structure:

<LclInstrm> <LclInstrm>

<Cd>CORE</Cd> <Cd>XXXX</Cd>

</LclInstrm> </LclInstrm>


supported.

Sequence Type <SeqTp> 2.40 Depending on the Depending on the

type of mandate the type of mandate the
following values are following values are
supported: supported:

If recurrent mandate If recurrent mandate
FRST/ RCUR/FNAL FRST/ RCUR/FNAL

If one o mandate If one o mandate
OOFF OOFF


<SeqTp>OOFF</ <SeqTp>OOFF</
SeqTp> SeqTp>

Category Purpose <CtgyPurp> 2.41 SUPP Leave Blank

Tag structure: At least one bank
(JPMC) does not
<CtgyPurp> populate Category
Purpose.
<Cd>SUPP</Cd>
Tag structure:
</CtgyPurp>
<CtgyPurp>

<Cd></Cd>

</CtgyPurp>

Instructed Amount <InstdAmt> 2.44 Transaction amount Transaction amount

and currency and currency

Tag structure: Tag structure:

<InstdAmt Ccy= <InstdAmt Ccy=
"EUR">15027. 4</ "EUR">15027. 4</
InstdAmt> InstdAmt>

295
Charge Bearer <ChrgBr> 2.45 SLEV Payer Bank Charge

Bearer
Tag structure:

<ChrgBr>SLEV</
ChrgBr>

Direct Debit <DrctDbtTx> 2.46 Tag structure: Same as SEPA

Transaction
<DrctDbtTx>

<MndtRltdInf>

<MndtId>AR SEPA
95.1</MndtId>

<DtOfSgntr>20100406</
DtOfSgntr>

<AmdmntInd>true</
AmdmntInd>

<AmdmntInfDtls>

<OrgnlMndtId>M1. 1.
1</ OrgnlMndtId>

<OrgnlCdtrSchmeId>

<Nm>Vision
Operations</ Nm>

<Id>

<PrvtId>

<Othr>

<Id>DE98ZZZ09999999999</
Id>

<SchmeNm>


</SchmeNm>

</Othr>

</PrvtId>

</Id>

</ OrgnlCdtrSchmeId>

<OrgnlDbtrAcct>

<Id>

296
<IBAN>GB52CHAS60924235582306</
IBAN>

</Id>

</ OrgnlDbtrAcct>

<OrgnlDbtrAgt>

<FinInstnId>

<Othr>

<Id>SMNDA</Id>

</Othr>

</FinInstnId>

</ OrgnlDbtrAgt>

</ AmdmntInfDtls>

</MndtRltdInf>

<CdtrSchmeId>

<Id>

<PrvtId>

<Othr>

<Id>1234</Id>

<SchmeNm>


</SchmeNm>

</Othr>

</PrvtId>

</Id>

</CdtrSchmeId>

</DrctDbtTx>

Mandate Related <MndtRltInf> 2.47 Only added if a debit

Information authorization exists.

Mandate Identication <MndtId> 2.48 Unique Mandate Unique Mandate

Reference Id Reference Id

297
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.

Amendment Indicator <AmdmntInd> 2.50 True/False True/False

Amendment <AmdmntInfDtls> 2.51 Not Applicable Same as SEPA

Information Details

Original Mandate <OrgnlMndtId> 2.52 Original Mandate Same as SEPA

Identication Reference Number in
the mandate.

Original Creditor <OrgnlCdtrSchmeId> 2.53 Not Applicable Same as SEPA

Scheme Identication

Name <Nm> 9.1.0 Not supported in favor Same as SEPA


Postal Address <PstlAdr> 9.1.1 AOS element. Not Not supported.

supported.

Identication <Id> 9.1.12 Not supported in Same as SEPA

favor of Organization
Identier

Organization Not Applicable 9.1.13 Payment System Same as SEPA

Identication Account parameters
> value for ISO20022
Creditor Scheme
Identication.

Note that this provides
the current creditor
scheme as the
payment system
account has no way to
track historical data.
Per BofA and JPMC,
this value should not
change.

Private Identication <PrvtId> 9.1.21 Not supported in Same as SEPA

Identier

Other <Othr> 9.1.27 Not supported in favor Same as SEPA

298
Country of Residence <CtryOfRes> 9.1.33 AOS element. Not Same as SEPA

supported

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 <OrgnlDbtr> 2.56 AOS element. Not Same as SEPA

supported

Original Debtor <OrgnlDbtrAcct> 2.57 Customer Bank Customer Bank

Account Account IBAN on Account IBAN on
the Original Debit the Original Debit
Authorization is passed Authorization is passed
in the IBAN in the IBAN

Bank Account Currency

Bank Account Name.

If IBAN is not provided,
populate the regular
bank account number
in the "Othr" tag.

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

Original Frequency <OrgnlFrqcy> 2..61 AOS element. Not Not Used

supported

Electronic Signature <ElctrncSgntr> 2.62 Not Supported. Not Supported in V2

First Collection Date <FrstColltnDt> 2.63 AOS element. Not Date of the selement
supported for which the mandate
was rst used.

299
Final Collection Date <FnlColltnDt> 2.64 AOS element. Not Mandate Final
supported Collection Date

Frequency <Frqcy> 2.65 AOS element. Not Mandate Frequency

supported

Creditor Scheme <CdtrSchmeId> 2.66 See Identication. See Identication.

Identication

Name <Nm> 9.1.0 AOS element. Not Not Supported.

supported

Postal Address <PstlAdr> 9.1.1 AOS element. Not Not Used

supported

Identication <Id> 9.1.12 Not supported, in Same as SEPA

Identication

Organization Not Applicable 9.1.13 Payment System Same as SEPA

Identication Account parameters
> value for ISO20022
Creditor Scheme
Identication.

Private Identication <PrvtId> 9.1.21 Not supported, in Not Supported.

Identication

Other <Othr> 9.1.27 Not supported, in favor Same as SEPA

of Private Identication

Country of Residence <CtryOfRes> 9.1.33 AOS element. Not Not Supported.

supported

Prenotication <PreNtfctnId> 2.67 This element is not AOS element. Not

Identication supported. supported

Prenotication Date <PreNtfctnDt> 2.68 This element is not AOS element. Not
supported. supported

Ultimate Creditor <UltmtCdtr> 2.69 Name Invoice Legal Mapping: Ultimate

Entity Name Creditor BICOrBEI/
Ultimate Creditor Other
Identication Populate ID from PSA seings.
Else Populate the LE
300
Legal entity registration number of

registration Invoice LE.
number by other in
OrganizationIdentication

Tag description:

<UltmtCdtr>

<Nm>Vision
Operations</ Nm>

<Id>

<OrgId>

<Othr>

<Id>SYS11100</ Id>

</Othr>

</OrgId>

</Id>

</UltmtCdtr>


Postal Address <PstlAdr> 9.1.1 Conditional AOS element that can



Organization Not Applicable 9.1.13 AOS element. Not Not Supported.

Identication supported

Private Identication Not Applicable 9.1.21 AOS element. Not Not Supported.
supported

Country of Residence <CtryOfRes> 9.1.33 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 aached to the
FinancialInstitutionIdentication
mandate, as well as the
branch number.
Tag structure:

<DbtrAgt>

301
<FinInstnId>

<BIC>BOFABE3X</
BIC>

</FinInstnId>

</DbtrAgt>

Debtor Agent Account <DbtrAgtAcct> 2.71 AOS element. Not Not used.
supported

Debtor <Dbtr> 2.72 Name Customer Name Same as for SEPA.

Address Customer Name Customer Name
Address
Address Customer
Identication Populate Address

BIC of the bank Identication Populate
branch of customer
bank account in BIC of the bank
OrganizationIdentication branch of customer
bank account in
Tag structure: OrganizationIdentication

<Dbtr> Tag structure:

<Nm>AR SEPA <Dbtr>
Customer</Nm>
<Nm>AR SEPA
<PstlAdr> Customer</Nm>

<Ctry>US</ Ctry> <PstlAdr>

<AdrLine>Hyderabad</ <Ctry>US</ Ctry>
AdrLine>
<AdrLine>Hyderabad</
</PstlAdr> AdrLine>

<Id> </PstlAdr>

<OrgId> <Id>

<BIC>BOFABE3X</ <OrgId>
BIC>
<BIC>BOFABE3X</
</OrgId> BIC>

</Id> </OrgId>

</Dbtr> </Id>

</Dbtr>


302
Postal Address <PstlAdr> 9.1.1 Not Applicable Same as SEPA

Address Type Not Applicable 9.1.2 AOS element. Not Not Supported.
supported

Country Not Applicable 9.1.10 Not Applicable Same as SEPA

Address Line Not Applicable 9.1.11 Not Applicable Same as SEPA

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


Organization Not Applicable 9.1.13 Not used in favor of Same as SEPA

Identication Private Identication

Private Identication Not Applicable 9.1.21 Not Applicable Same as SEPA

Country of Residence <CtryOfRes> 9.1.33 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

IT60X0542811101000000123456

</IBAN>

</Id>

</DbtrAcct>

Ultimate Debtor <UltmtDbtr> 2.74 Not supported Bill-to Same as SEPA

Customer is the same
as the Customer/ Payer
used as Debtor.

Instruction for Creditor <InstrForCdtrAgt> 2.75 AOS element. Not Not supported.
Agent supported.

Purpose <Purp> 2.76 Not Applicable Same as SEPA

Code <Cd> 2.77 SUPP is passed during Purpose Code from the
formaing. Payer. If null, from the
FCPP.
Tag Structure:

<Purp>

<Cd>SUPP</Cd>

</Purp>


supported.

Regulatory Reporting <RgltryRptg> 2.79 AOS element. Not Not supported.

supported.

Tax <Tax> 2.80 AOS element. Not Not supported.

supported.

Related Remiance <RltdRmtInf> 2.81 AOS element. Not Not supported.

Information supported.

Remiance Information <RmtInf> 2.88 Not Applicable Same as SEPA

Unstructured <Ustrd> 2.89 Not used in favor of Same as SEPA

Structured element

304
Structured <Strd> 2.90 We populate the In the case of grouped

invoice number in the invoices, populate one
reference. STRD element per
invoice.
<RmtInf>

<Strd>

<CdtrRefInf>

<Tp>

<CdOrPrtry>

<Cd>SCOR</Cd>

</CdOrPrtry>

</Tp>

<Ref>23184</ Ref>

</CdtrRefInf>

</Strd>

</RmtInf>

Referred Document <RfrdDocInf> 2.91 AOS element. Not Not supported.


Referred Document <RfrdDocAmt> 2.99 AOS element. Not Not supported.

Amount supported.

Creditor Reference <CdtrRefInf> 2.110 Not Applicable Same as SEPA

Information

Creditor Reference <CdtrRefTp> 2.111 Not Applicable Same as SEPA

Type

Code <Cd> 2.113 CINV representing Same as SEPA

Commercial Invoice


supported.

Issuer <Issr> 2.115 Not Applicable Same as SEPA

Creditor Reference <CdtrRef> 2.116 AR Transaction In the case of grouped

Number(s) comma invoices, populate one
delimited if multiple
305
invoices are included STRD element per

on one receipt invoice.

Supplier <Invcr> 2.117 AOS element. Not Not supported.

supported.

Invoiced <Invcee> 2.118 AOS element. Not Not supported.

supported.

Additional Remiance <AddtlRmtInf> 2.119 AOS element. Not Not supported.


Update of a Selement Batch from Stuck to Success

When you set up a funds capture process prole, you can specify whether you want to receive funds capture
acknowledgments from your bank. To set up funds capture acknowledgments, you specify an Inbound Response
Format in the Selement Response Processing section on the Formats tab of the funds capture process prole.
However, if your bank doesn't support funds capture acknowledgments, and you mistakenly specify an Inbound
Response Format in the Selement Response Processing section anyway, then a successful selement batch is set to
an intermediary status that waits for an acknowledgment that won't arrive. You can't move such transactions from an
intermediary status to a Success or Reject status in Oracle Payments.
But you can move a selement 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 selement batch and its
transactions update from an intermediary status to Success only if:
• You select a reference number from the Selement Batch Reference choice list.
• The funds capture processing type on the funds capture process prole is Bank Account
• These formats aren't specied in the Formats tab of the funds capture process prole:
◦ Selement section: Inbound Response Format

◦ Selement Response Processing section: Outbound Format and Inbound Response Format
• A funds capture acknowledgment isn't aached to the transmission conguration.
Retrieval of Funds Capture Acknowledgment Files Using

a Wildcard
You can retrieve multiple funds capture acknowledgment les from your bank instead of a single le by using a wildcard
in the le name. First, you must opt in to the applicable feature. Second, create a transmission conguration using
306
the protocol named Secure File Transfer Retrieval Protocol for Static File Names. Then, on the Create Transmission
Conguration 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
aempt.
For example, suppose you have two les:
• PAY_ACK_01012019.xml
• PAY_ACK_02012019.xml
To retrieve both les in one aempt, enter PAY_ACK_*.xml in the Value eld of the Remote File Name parameter on the
Create Transmission Conguration 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.
1. In the Oerings work area, select the Financials oering.

2. Click Opt In Features.
3. On the Opt In: Financials page, click the Features icon, or pencil, for Payments.
4. On the Edit Features: Payments page, select the Enable check box for the feature named Retrieve Funds
Capture Acknowledgment Files Using a Wildcard Search.
5. Click Done.
Reports for Manage Funds Capture

Funds Capture Accompanying Leers
This topic includes details about the Funds Capture Accompanying Leer.
Overview
The Funds Capture Accompanying Leer is a predened funds capture report that is manually delivered to your
payment system or bank. The report accompanies a selement batch le and summarizes its contents
307
The following gure illustrates an example of the Funds Capture Accompanying Leer.
Key Insights
The following table lists the dierence between the formal Funds Capture Accompanying Leer report name and the
process name.
308
Report Name Process Name Output
Funds Capture Accompanying Leer Create Selement Batch Accompanying .PDF le
Formats Leer

Generation of the Funds Capture Accompanying Leer

To generate the Funds Capture Accompanying Leer from within Oracle Fusion Payments, complete these steps:
1. In the Setup and Maintenance work area, go to the following:
Navigate: Navigator > Setup and Maintenance > Search: Tasks pane: Manage Funds Capture Process
Proles > Go to Task > Select Processing Type > Create buon.
◦ Oering: Financials
◦ Functional Area: Customer Payments
◦ Task: Manage Funds Capture Process Proles
2. On the Manage Funds Capture Process Proles page, select a processing type from the Select Processing Type
choice list and click Create.
3. On the Create Funds Capture Process Prole page, Formats tab, Selement section, select options for the
Outbound Format, Inbound Response Format, and the Accompanying Leer 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 Selement Batch Accompanying Leer link.
8. The parameters page for the Funds Capture Accompanying Leer appears.
9. From the Selement Batch Reference choice list, select the applicable selement batch reference number and
click Submit. A conrmation message displays with a process ID.
Tip: Write down or remember the process ID.
10. Navigate:Navigator > Tools > Scheduled Processes link.

11. In the Process ID eld on the Scheduled Processes page, enter the process ID and click Search. The result
displays in the Search Results section.
12. Select the resulting row in the Search Results section to display additional details on the page.
13. In the Log and Output section, click the 1 more link to display the Aachments dialog box. You can now see
the <process ID> .PDF output le.
Report Parameters
The following table describes the process parameter.
Name Description
Selement Batch Reference Application-assigned reference number for the selement batch.

309

The following table lists frequently asked questions and provides the answers about the Funds Capture Accompanying
Leer.
FAQ Answer
How do I nd this report?

You can nd the Funds Capture Accompanying Leer in the Log and Output section. Click the
1 more link to display the Aachments dialog box. You can now see the .PDF output le.
Who uses this report? • Financial Manager

• Financial Specialist
When do I use this report? The Funds Capture Accompanying Leer is used when you want to summarize the contents of
a selement batch and manually send the summary and the selement batch to the payment
system or bank.


You can:
• Manually deliver the Funds Capture Accompanying Leer to your payment system or
bank, along with the selement batch.

Funds Capture Payer Notication Reports

This topic includes details about the Funds Capture Payer Notication report.
Overview
The Funds Capture Payer Notication report is a predened funds capture report that can be faxed, emailed as a PDF
aachment, printed, or mailed to customers after a selement or selement batch is transmied 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
This image illustrates an example of the Funds Capture Payer Notication report.
Key Insights
This table lists the the formal Funds Capture Payer Notication report name and the process name that's used to
manually generate the report.
Report Name Process Name Output
Funds Capture Payer Notication Formats Send Receipt of Payment Notications

PDF le if the delivery option is Printed,
emailed as a PDF aachment if the
delivery option is Email with .pdf as
aachment, faxed if the delivery option is
Fax, or as HTML in the body of the email if
the delivery option is Email.
Email Delivery of the Funds Capture Payer Notication Report

To enable customers to receive the Funds Capture Payer Notication report by email, complete these steps:
1. In the Setup and Maintenance work area, select:
◦ Task: Manage Funds Capture Process Proles
311
2. On the Manage Funds Capture Process Proles, from the Select Processing Type choice list, select a processing
type.
3. Click Create.
4. On the Funds Capture Process Prole page, Formats tab, Notication to Payer section, from the Format choice
list, select the Receipt of Payment Notication 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 Notication Preferences section, from the Debit Advice Delivery Method choice
list, optionally select Email with .pdf as aachment. This option lets you aach the Funds Capture Payer
Notication report to an email as a PDF aachment. If you select the Email option, the Funds Capture Payer
Notication 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:
◦ Task: Manage Internal Payees
13. On the Manage Internal Payees page, click the Create icon.
14. On the Create Internal Payee page, Notication to Payer section, enter a valid email in the From Email eld and
the subject that you want to see in the notication email in the Subject eld.
Generation of the Funds Capture Payer Notication Report

To generate the Funds Capture Payer Notication report from within Oracle Payments, complete these steps:
1. From the Accounts Receivable work area, click the Funds Capture icon.
2. Click the Tasks icon.
3. Click the Send Receipt of Payment Notications link. The parameters page for the Send Receipt of Payment
Notications appears.
4. Select applicable parameters and click Submit. A conrmation message displays with a process ID.
Tip: Write down or remember the process ID.
5. Navigate: Navigator > Tools > Scheduled Processes link.

6. In the Process ID eld on the Scheduled Processes page, enter the process ID and click Search. The result
displays in the Search Results section.
7. Select the resulting row in the Search Results section to display additional details on the page.
8. In the Log and Output section, click the 1 more link to display the Aachments dialog box. You can now see the
<process ID> PDF output le.
Report Parameters
This table describes the process parameters.
Name Description
Selement Batch Reference Payments-assigned reference number of the selement batch.
312
Name Description

From Selement Date Starting date within a date range of selement transactions.

To Selement Date Ending date within a date range of selement transactions.

From Payment System Order Number Order number generated by Payments, which identies the rst selement transaction to the
payment system.

To Payment System Order Number Order number generated by Payments, which identies the last selement transaction to the
payment system.

Allow Sending Replacement Copy The inclusion of selements in the Funds Capture Payer Notication report that were included
in a previous report if, for example, the customer requests a duplicate copy of the Funds
Capture Payer Notication report.


The following table lists frequently asked questions and provides answers about the Funds Capture Payer Notication
report.
FAQ Answer
How do I nd this report?

You can nd the Funds Capture Payer Notication report in the Output section. Click the 1
more link to display the Aachments dialog box. You can now see the PDF output le.

When do I use this report? The Funds Capture Payer Notication 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 sucient
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.


You can:
1. Generate and schedule the Funds Capture Payer Notication report.

2. Send the Funds Capture Payer Notication report to customers by email, US mail, or fax.

313
FAQs for Manage Funds Capture

What happens if I don't disable the transaction testing function
before going live?
You can experience inconsistent data between applications. You may also unintentionally create holds or charges on
credit cards for amounts not owed by the card holder.
Using the transaction testing functionality, you can initiate transactions without source product interaction to test the
setup of Oracle Fusion Payments and the payment system connectivity. Transactions initiated from Payments, rather
than the source product, are not recorded in any source product. This functionality is a valuable testing and diagnostic
tool, but it can create inconsistent data between applications if used incorrectly in a live environment.
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.
What's the dierence between credit card payments made with a

CVN or without a CVN?
Credit card payments made with a 3 or 4-digit Card Verication Number (CVN) code that is on the front or back of the
card improves transaction security and prevents fraud. When the cardholder isn't present in person, merchants often
ask for the code so they can secure transactions occurring online, by mail, fax, or over the phone. The code results in
an electronic authorization request to verify the authenticity of the card. The merchant receives a reply message as to
whether or not the card and the code match. Merchants who send the CVN with their credit card authorizations may
also accrue lower transaction costs than those who don't.
Note: CVN capture during transaction authorization is currently not allowed. However, you may provide CVN
during credit card token creation.
Credit card payments made online, by mail, fax, or over the phone without a CVN requested by the merchant, present
a greater risk to the merchant because the card isn't veried as authentic by the reply message to the electronic
authorization request. Additionally, in some territories and countries, credit card authorization is rejected without the
CVN code.
What's the dierence between application behavior for credit card

payments made with a CVN or without a CVN?
Credit card payments made with required entry of a 3 or 4-digit Card Verication Number (CVN) necessitates the
performance of two prerequisite setups. In the Setup and Maintenance work area, use the following: Oering:
Financials, Functional Area: Customer Payments, Task: Manage Funds Capture Payment Methods. On the Manage
Funds Capture Payment Methods page, select a payment method and click the Edit icon. In the Edit Funds Capture
Payment Method dialog box, select the Require security code entry check box. On the Manage System Security
Options page, enable tokenization in the Credit Card Data subsection. After this, when you save a transaction type of
Invoice with a CVN required, the application creates an immediate authorization and receipt number for the invoice.
314
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.
When do customers use the simplied payment UI?

Oracle Payments Cloud provides a simplied, shared transaction extension component for payments by credit card
or bank account. This simplied UI is used by products that integrate with Payments, such as Oracle Fusion Bill
Management and Oracle Student Cloud. These products are used by self-service users, such as customers or students
who require a modern UI to pay for products or services by credit card or bank account. As part of order booking or
invoice payment processes, users enter their credit card or bank account data, which is stored by the application in
a secured manner. A bank account is stored encrypted, whereas a credit card is rst tokenized and then the token is
stored instead of the credit card number.
When can I derive a bank account number from IBAN?

When you create and save an external bank account in the majority of the European, Middle Eastern, and Caribbean
countries where the IBAN (International Bank Account Number) is used according to SWIFT (Society for Worldwide
Interbank Financial Telecommunication) guidelines, the bank account number automatically derives from the IBAN and
populates the Account Number eld.
315
316
Using Receivables Credit to Cash Manage Accounts Receivable Balances
4 Manage Accounts Receivable Balances
Access Receivables Information

Oracle Receivables Predened Reports
Receivables provides predened reports to help you analyze and manage your accounts receivable information.
The Receivables predened reports cover the following areas:
• Bill Presentment Templates
• Accounting Reports
• Billing Reports
• Receivables Balances Reports
• Bills Receivable Reports
• Neing Selement Reports
• Reconciliation Process and Report
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.
To run a report from Scheduled Processes:

2. Search for the process name that you want.
3. Enter values for the parameters that you need.
4. Enter the desired process options and schedule.
5. Click Submit.
The following tables group the Receivables reports by type and provide a description of each report.
Bill Presentment Templates

The predened print templates are used to print Receivables transactions. You can also create your own versions of
these print templates.
Display Name Description
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
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 specied 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
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 specied 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 exelds by business unit, transaction number, and transaction type.

Receivables Balances Reports

Use these reports to review and analyze payment information and customer balances.
Automatic Receipt Creation and Report for the process that creates automatic receipts and receipt remiances in a batch.
Remiance Execution Report Includes information about automatically generated receipts, remied receipts, and data
validation errors by batch.

Bank Risk Report Provides information about receipts that are currently at risk with the remiance bank.
Includes information about the remiance batch, receipt, and receipt amount by business unit,
remiance bank branch, and remiance bank account.

Clear Receipts Automatically Report for the process that clears receipts automatically. Includes information about the
Execution Report clearing of customer receipts by remiance bank account, receipt number, and customer.

Create Automatic Receipt Write-os Report for the process that writes o unapplied amounts on selected receipts. Includes
Execution Report information about the receipt write-os 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 specied ledger currency.

Customer Balances Revaluation Displays information related to the dierence 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
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 specied receipt batch so that they can be sent to customers for
conrmation. 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 remiance bank. Includes information
Report about the remiance bank account name, remiance batch date, maturity date, receipt
number and receipt amount by business unit, maturity date, and currency.

Receipts Awaiting Remiance Report Provides a list of receipts waiting to be remied to the bank. Includes information about the
remiance bank account name, maturity date, receipt number, and receipt amount by business
unit, remiance 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 specic 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 reect the
Report dierence 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
Reversal Status Report Provides information about the status of automatic receipt reversals processed for a
selement batch. Includes the receipt date, receipt number, receipt amount, reversal reason
code, and a description of automatic receipt reversals that were unsuccessful.

Bills Receivable Reports

Use these reports to review and analyze bills receivable activity.
Automatic Bills Receivable Report for the process that creates a bills receivable remiance from bills receivable. Provides
Remiance Execution Report the details of bills receivable remied 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 remied 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 remiance batch.

Neing Selement Reports

Use these reports to review and analyze Payables and Receivables neing selements.
Neing Selement Leer Prints a leer that provides details of Payables and Receivables transactions in a neing
selement.

Neing Reversal Leer Prints a leer that provides details of Payables and Receivables reversed transactions in a
neing selement.

Neing Selement Report Lists the Payables and Receivables transactions belonging to a specic neing selement in
PDF format.

Neing Selement Listing Lists the Payables and Receivables transactions belonging to a specic neing selement in
spreadsheet format.

321
Reconciliation Process and Report

Use this process and report to help you reconcile receivables data to the general ledger.
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 dierences between actual and reconciling amounts.

Related Topics
• Reports and Analytics Work Area and Panel Tab
Receivables Subject Areas, Folders, and Aributes

Use the subject areas, folders, and aributes to create real-time analyses of Receivables.
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.
Receivables has fourteen specic subject areas:

• Receivables - Adjustments Real Time
• Receivables - Credit Memo Applications Real Time
• Receivables - Credit Memo Requests Real Time
• Receivables - Miscellaneous Receipts Real Time
• Receivables - Payment Schedules Real Time
• Receivables - Receipt Conversion Rate Adjustments Real Time
• Receivables - Receipts Details Real Time
• Receivables - Revenue Adjustments Real Time
• Receivables - Standard Receipts Application Details Real Time
• Receivables - Transactions Real Time
• Receivables - Bills Receivable Real Time
• Receivables - Customer Real Time
• Receivables - Customer Tax Prole Real Time
322
• Receivables - Customer Account Site Tax Prole Real Time
Folders
Each subject area has one or more fact folders and a number of dimension folders. Fact folders contain aributes 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 aribute 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 dierent level of granularity. For example:
• Bill-to Customer has customer aributes.

• Transaction Line Details has subfolders and aributes within the subfolders for the various line amounts.
Aributes
Each dimension folder contains aributes (columns), such as customer category and customer codes.
323
These two gures illustrate the structure of subject areas, folders, and aributes.
324
These two gures illustrate the following components:

• Subject area: Receivables - Transactions Real Time
• Dimension - Presentation Folder: Bill-to Customer > Bill-to Customer Classication
• Dimension - Aributes: Bill-to Customer Class Category and Bill-to Customer Class Code
• Fact - Presentation Folder: Line Amounts
• Fact - Measures: Deferred Line values, Line Amount, Transaction Line values
Related Topics
• How Data Is Structured for Analytics
325
How Transaction Activities are Stored

This topic describes how Receivables stores transaction activities.
These transaction activities are:
• Invoices and Debit Memos

• Credit Memos
• Chargebacks
• Adjustments
Invoices and Debit Memos

When you create an invoice or debit memo either manually or using AutoInvoice, Receivables creates records in the
following tables:
• RA_CUSTOMER_TRX
Consider this sample invoice:
• Invoice Number: I-101

• Bill-to Customer: ABC Inc
• Invoice Date: 22-May-11
• Invoice Lines: 5
Item Amount Tax Total Amount
10 chairs @ $200 $2,000 $160 $2,160

10 tables @ $300 $3,000 $240 $3,240

Freight $1000 NA $1000

TOTAL NA NA $6400

The RA_CUSTOMER_TRX table stores information from Invoice I-101 as follows:
326
CUSTOMER_TRX_ID TRX_NUMBER BILL_TO_CUSTOMER_ID TRX_DATE
101467 I-101 ABC Inc 22-May-11

The RA_CUSTOMER_TRX_LINES table stores information from Invoice I-101 as follows:
CUSTOMER_TRX_LINE_ID CUSTOMER_TRX_ID LINK_TO_CUST_TRX_LINE LINE_TYPE EXTENDED_AMOUNT

_ID
100 101467 NA LINE 2000

101 101467 100 TAX 160

102 101467 NA LINE 3000

103 101467 102 TAX 240

104 101467 NA FREIGHT 1000

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 reects the sales credits alloed 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.
The RA_CUST_TRX_LINE_SALESREPS table stores information from Invoice I-101 as follows:
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
140195 1492 100 1000 0 NULL

140196 1525 100 1000 0 NULL

140197 1492 101 0 80 NULL

140198 1525 101 0 80 NULL

140199 1624 102 3000 0 NULL

327
PREV_CUST_TRX_LINE
_SALESREP_ID
140200 1624 103 0 240 NULL

140201 1492 104 0 200 NULL

140202 1525 104 0 200 NULL

140203 1624 104 0 600 NULL

The RA_CUST_TRX_LINE_GL_DIST table stores information from Invoice I-101 as follows:
CUST_TRX_LINE_GL_DIST_ID
CODE_COMBINATION_ID CUSTOMER_TRX_LINE_ID ACCOUNT_CLASS AMOUNT
10866 01-1200-1000-3000 NA REC 64000

10867 01-8100-1000-3000 100 REV 2000

10868 01-4100-1000-3000 101 TAX 160

10869 01-8200-1000-3000 102 REV 3000

10870 01-4200-1000-3000 103 TAX 240

10871 01-4400-1000-3000 104 FREIGHT 1000

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 identied 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 reects 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.
The AR_PAYMENT_SCHEDULES table stores information from Invoice I-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE CUSTOMER_TRX_ID
CASH_RECEIPT_ID
TRX_NUMBER STATUS AMOUNT CLASS
_REMAINING _APPLIED
30191 6400 6400 101467 NULL I-101 OP NULL INV
328
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
Consider a sample credit memo against line number 1 of Invoice I-101:
• Credit Memo Number: CM-101

• Credit Memo Date: 01-Jun-11
• Credit Memo Amount: -1000
The RA_CUSTOMER_TRX table stores Credit Memo CM-101 as follows:
CUSTOMER_TRX_ID TRX_NUMBER BILL_TO_CUSTOMER_ID TRX_DATE PREVIOUS_CUSTOMER

_TRX_ID
123456 CM-101 ABC Inc 01-Jun-11 101467

Note: The previous_customer_trx_id column references the original transaction you have credited.
The RA_CUSTOMER_TRX_LINES table stores Credit Memo CM-101 as follows:
CUSTOMER_TRX_LINE_ID
CUSTOMER_TRX_IDLINK_TO_CUST_TRX_LINE_ID
LINE_TYPE EXTENDED_AMOUNT
PREVIOUS_CUSTOMER_TRX
150 123456 NA LINE -926 101467 110100

151 123456 150 TAX -74 101467 NA

329
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.
The RA_CUST_TRX_LINE_SALESREPS table stores Credit Memo CM-101 as follows:
PREV_CUST_TRX_LINE
_SALESREP_ID
150205 1492 100 -463 0 140195

150206 1525 100 -463 0 140196

150207 1492 101 0 -37 140197

150208 1525 101 0 -37 140198

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.
The RA_CUST_TRX_LINE_GL_DIST table stores Credit Memo CM-101 as follows:
150160 01-1200-1000-3000 NA REC -1000

150161 01-8100-1000-3000 150 REV -926

150162 01-4100-1000-3000 151 TAX -74

Note: Because this is a credit memo, the revenue and tax accounts will be debited and the receivable account
will be credited.
The AR_PAYMENT_SCHEDULES table stores Credit Memo CM-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
AMOUNT_DUE_REMAINING
CUSTOMER_TRX_ID
TRX_NUMBER STATUS AMOUNT_APPLIED
CLASS AMOUNT_CREDITED
400100 -1000 0 123456 CM-101 CL -1000 CM NULL

330
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
CUSTOMER_TRX_ID
CLASS AMOUNT_CREDITED
30191 6400 5400 101467 I-101 OP NULL INV -1000

Note: Receivables updates the payment schedule of the invoice to reect 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.
The AR_RECEIVABLE_APPLICATIONS table stores Credit Memo CM-101 as follows:
RECEIVABLE_APPLICATION_ID
AMOUNT_APPLIED
STATUS PAYMENT_SCHEDULE_ID
CUSTOMER_TRX_ID
CASH_RECEIPT_ID
APPLIED_PAYMENT_SCHEDULE_ID
APPLIED_CUSTOMER_TR
400 1000 APP 400100 123456 NULL 30191 101467

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.

When you enter an on-account credit without a specic invoice reference, Receivables creates records in the following
tables:
• RA_CUSTOMER_TRX
Consider a sample on-account credit applied to customer ABC Inc:

• Transaction Number: OC-101
• Transaction Date: 05-Jun-11
331
• Credit Amount: -1000
The RA_CUSTOMER_TRX table stores On-Account Credit transaction number OC-101 as follows:
CUSTOMER_TRX_ID TRX_NUMBER ABC Inc TRX_DATE PREVIOUS_CUSTOMER_TRX_ID

BILL_TO_CUSTOMER_ID
660108 OC-101 NA 05-Jun-11 NULL

Note: The previous_customer_trx_id column is NULL because the credit doesn't apply to a specic 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
PREVIOUS_CUSTOMER_TRX
170 660108 NA LINE -1000 NA NA

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 specic invoice.
The RA_CUST_TRX_LINE_GL_DIST table stores On-Account Credit transaction number OC-101 as follows:
210220 01-1200-1000-3000 NA REC -1000

210221 01-8100-1000-3000 170 REV -1000

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.
Receivables uses the following tables to store chargeback information:
• RA_CUSTOMER_TRX
• AR_ADJUSTMENTS
332
Consider again sample invoice I-101:
• Invoice Number: I-101

• Invoice Date: 22-May-11
• Invoice Total: $6400
You receive a payment for $2000 on June 1, 2011, and decide to create chargeback CB-101 for the balance due of $4400.
The RA_CUSTOMER_TRX table stores CB-101 as follows:
CUSTOMER_TRX_ID TRX_NUMBER BILL_TO_CUSTOMER_ID TRX_DATE
765432 CB-101 ABC Inc 01-Jun-11

The RA_CUSTOMER_TRX_LINES table stores CB-101 as follows:
CUSTOMER_TRX_LINE_ID CUSTOMER_TRX_ID LINK_TO_CUST_TRX_LINE_ID

711 765432 NA CB 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.
Note: There is no impact to the RA_CUST_TRX_LINE_SALESREPS table.
The RA_CUST_TRX_LINE_GL_DIST table stores CB-101 as follows:
660116 01-1200-1000-3000 NULL REC 4400

660117 01-8100-1000-3000 711 REV 4400

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.
The AR_ADJUSTMENTS table stores CB-101 as follows:
333
ADJUSTMENT_ID AMOUNT CUSTOMER_TRX_ID TYPE PAYMENT_SCHEDULE_ID

CODE_COMBINATION_ID
57931 -4400 101467 INVOICE 30191 01-8100-1000-3000

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 oset 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.
The AR_PAYMENT_SCHEDULES table stores CB-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
CUSTOMER_TRX_ID
CLASS AMOUNT_ADJUSTED
565785 4400 4400 765432 CB-101 OP NULL CB NULL

The class column identies 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
CUSTOMER_TRX_ID
30191 6400 0 101467 I-101 CL 2000 INV -4400

Receivables updates the invoice payment schedule in the AR_PAYMENT_SCHEDULES table by reducing
the amount_due_remaining column to zero, to reect 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
Consider an adjustment to invoice I-101 to write o the remaining balance of $2400.
The AR_ADJUSTMENTS table stores the adjustment to I-101 as follows:
334
ADJUSTMENT_ID AMOUNT CUSTOMER_TRX_ID TYPE PAYMENT_SCHEDULE_ID

CODE_COMBINATION_ID
987654 -2400 899143 INVOICE 646566 01-5100-3000-1000

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.
The AR_PAYMENT_SCHEDULES table stores the adjustment to I-101 as follows:
PAYMENT_SCHEDULE_ID
AMOUNT_DUE_ORIGINAL
CUSTOMER_TRX_ID
646566 6400 0 899143 I-101 CL 4000 INV -2400

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.
How Payment Activities are Stored

This topic describes how Receivables stores payment activities.
These payment activities are:

• Unapplied Receipts
• Applied Receipts
• Reverse Receipts
• Miscellaneous Receipts
Unapplied Receipts
When you create a receipt, Receivables creates records in the following tables:
Consider this sample receipt:

• Receipt Number: R-101
• Received From: ABC Inc
• Receipt Date: 05-Jul-11
• Receipt Amount: 4000
The AR_CASH_RECEIPTS table stores information from Receipt R-101 as follows:
335
credit_receipt_id amount status receipt_number type
338700 4000 UNAPP R-101 CASH

The AR_CASH_RECEIPT_HISTORY table stores information from Receipt R-101 as follows:
cash_receipt_history_id amount status
457890 4000 CLEARED

The AR_PAYMENT_SCHEDULES table stores information from Receipt R-101 as follows:
payment_schedule_id
amount_due_original
amount_due_remaining
cash_receipt_idcustomer_ trx_number status amount_applied
class
trx_id
510555 -4000 -4000 338700 NULL R-101 OP 0 PMT

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.
The AR_RECEIVABLE_APPLICATIONS table stores information from Receipt R-101 as follows:
payment_schedule_id
amount_applied status payment_schedule_id
code_combination_id
cash_receipt_id applied_payment_schedule_id
applied_customer_trx_id
408289 4000 UNAPP 400100 01-1100-1000 338700 NULL NULL

The applied_payment_schedule_id and applied_customer_trx_id columns are NULL because the receipt hasn't
been applied to a specic 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.
Applied Receipts: Same Currency

When you apply a receipt, Receivables creates records in the following tables:
• AR_CASH_RECEIPTS: Stores one record for each receipt.
• AR_PAYMENT_SCHEDULES: Stores customer balance information at the transaction level.
• AR_RECEIVABLE_APPLICATIONS: Stores accounting entries for cash and credit memo applications.
Consider sample receipt R-101, which is now applied to customer invoice I-101 for 6400 USD:
336
• Received From: ABC Inc

credit_receipt_id receipt_number amount status type currency rate
1521 R-101 4000 UNAPP CASH USD NULL

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
cash_receipt_id
customer_ trx_number status amount_applied
class currency
trx_id
2211 6400 2400 NULL 1422 I-101 OP 4000 INV USD

2225 -4000 0 1521 NA R-101 CL -4000 PMT USD

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 conrmed in the AR_CASH_RECEIPT_HISTORY table, the applications of that
receipt are not reected 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 reect the amount applied to the invoice.
receivable_application_id status trx_number amount_applied code_combination_id
3132 UNAPP NULL 4000 01-1100-1000

3134 UNAPP NULL - 4000 01-1200-1100

3135 APP I-101 4000 01-1200-1100

337
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, osets 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.
Applied Receipts: Cross Currency

Consider the sample receipt R-102, which, according to the customer remiance advice, is to fully pay invoice I-102,
using a cross currency rate of 1 CAD = 0.729355 EUR.
Receipt Number: R-102:

• Received From: ABC Inc.
• Transaction Date: 5-JUL-11
• Receipt Amount: 100 EUR
• Conversion Rate: 1 EUR = .860956 USD
Invoice Number: I-102:

• Transaction Date: 05-JUN-11
• Invoice Amount: 52.50
• Conversion Rate: 1 CAD = .666667 USD
credit_receipt_id receipt_number amount status type currency rate
1521 R-102 100 APP CASH EUR .865956

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
cash_receipt_id
customer_ trx_number status amount_applied
class currency
trx_id
2212 52.5 0 NA 1423 I-102 CL 52.5 INV CAD

2224 -100 0 1520 NA R-102 CL -100 PMT EUR

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
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
3142 UNAPP NULL 100 NA NA NA 33.33 01-1100-1000

3134 UNAPP NULL -100 -100 NA -33.33 -33.33 01-1200-1100

3135 APP I-102 52.5 100 1.9048 35 33.33 01-1200-1000

of UNAPP, records the original unapplied receipt. The second record, with a status of UNAPP, osets 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:
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:
338700 4000 REV R-101 CASH

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
545352 4000 REVERSED

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
cash_receipt_idcustomer_trx_id
trx_number status amount_applied
class
chedule_id
510555 -4000 0 338700 NULL R-101 CL 0 PMT

30191 6400 6400 NULL 101467 I-101 OP 0 INV

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
408292 -4000 APP 400100 01-1200-1100 338700 30191 101467

408293 4000 UNAPP 400100 01-1100-1000 338700 NULL NULL

408294 -4000 UNAPP 400100 01-1100-1000 338700 NULL NULL

of APP, osets 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, oset 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
Miscellaneous Receipts
When you create a miscellaneous receipt, Receivables creates records in the following tables:
Consider this sample miscellaneous receipt:

• Received From: Stock Broker
The AR_CASH_RECEIPTS table stores information for the miscellaneous receipt as follows:
345678 500 APP R-102 MISC

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:
467890 500 CLEARED

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:
misc_cash_distribution_id cash_receipt_id code_combination_id amount
101789 345678 01-1190-1000-3000 250

101790 345678 01-1195-1000-3000 250

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
Processes for Synchronizing Receivables Transaction Data

Some transactions and transaction updates may not display at any given time on the Review Customer Account Details
page. This can be due, for example, to new customer data or to transactions becoming past due.
To ensure the display of accurate information in the Activities section of the Review Customer Account Details page,
and to ensure that you can search for new customers and display associated summary information in the Overview
section of the Review Customer Account Details page, use the Scheduled Processes work area to schedule regular runs
of the related synchronization processes.
These processes are:

• Refresh Receivables Transactional Events for Summary Tables: This process synchronizes all receivables data.
Run this process during implementation, and thereafter when entering transactions for new customers.
• Process Receivables Transactional Events for Summary Tables: This process synchronizes updated receivables
data. Run this process nightly or as needed according to the frequency and volume of transactions.
• Refresh Receivables Past Due Transactions for Summary Tables: This process synchronizes receivables
past due transaction data. Run this process nightly or as needed according to the frequency and volume of
transactions.
Process Late Charges

Late Charge Interest Calculation Methods
When you set up a late charge prole for your customers, you must decide the method to use to calculate late charges.
You select the calculation method in the Late Charge Calculation Method eld in the Credit Limits and Late Charges
tab of the Customer Prole Class pages, or on the applicable customer or customer site prole.
The interest calculation methods are:

• Average Daily Balance: Calculate late charges based on the average daily balance of overdue invoices. This
method is for balance forward bills only.
• Late Payments Only: Calculate late charges based on the number of days between the payment due date and
the actual payment date. This method uses the paid amount as the overdue invoice amount when calculating
the late charge.
• Overdue Transactions Only: Calculate late charges for transactions based on the number of days a payment is
late when you submit the Create Late Charges program.
• Overdue Transactions and Late Payments: Calculate late charges on both overdue transactions and late
payments. This option levies the largest late charge amount on a customer.
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
◦ 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.
Late Charge Interest Calculation Formulas

When you set up a late charge prole for your customers, you must decide the formula to use to calculate late charges.
You select the calculation formula in the Interest Calculation Formula eld in the Charge Calculation Setup section in
the Credit Limits and Late Charges tab of the Customer Prole Class pages, or on the applicable customer or customer
site prole.
The interest calculation formulas are:
• 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:
Amount Overdue * (Interest Rate/100)
• 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:
Amount Overdue * (Interest Rate/100) * (Number of Days Late/Number of Days in Period)
• 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)
How Late Charges Are Calculated Using Interest Tiers

Use interest tiers and charge schedules to assess increasingly higher late charges the longer a payment is overdue. You
can dene interest tiers and charge schedules for late charges and, if applicable, for additional penalty charges.
The interest tier provides period ranges for number of days overdue, and the charge schedule indicates the at amount
or percentage to charge in each overdue 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 proles with the new rates.
Seings That Aect Late Charge Calculation Using Interest Tiers

These seings aect late charge calculation using interest tiers:
• Interest Tiers: Use the Manage Interest Tiers page to dene a set of interest tiers based on ranges of late days.
Use these seings for each set of interest tiers:
◦ Aging Type: Select the value Interest Tier.

◦ Sequence Number: Use a numbering scheme to reect the order in which to consider each period.
343
◦ Detail Type: Select the value Past Due.

◦ From Days/To Days: Enter the date range for each period.
• 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 dened. Use these seings 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 specied period
ranges.
• Percentage: Apply a percentage of the overdue transactions that fall within the specied 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.
• Prole Class: Specify these values on the related prole class, or customer or customer account prole:
◦ Use multiple interest rates option: If you set the Use multiple interest rates option, then if the eective
dates for two charge schedules occur within the same charge calculation period, both rates apply to late
charge calculations during that period.
Note: This applies to interest invoices only.
◦ Currency Seings: 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 dened to use for late charges and penalty charges.
How Late Charges Using Interest Tiers Are Calculated

The active interest tier and charge schedule values are used to calculate late charges using the Simple calculation
formula.
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.
Days Overdue Tiers Interest Rate
1-30 days 2%

31-45 days 3%

46-60 days 4%

Over 60 days 5%

344
In this example:
• An invoice for $1,000 is 45 days overdue.

• There are 30 days in the billing period.
The late charges are calculated as follows:

$1,000 * (3/100) * (45/30) = $45
After an additional 15 days (60 days overdue), the late charges are calculated as follows:
$1,000 * (4/100) * (60/30) = $80
How Late Charges Are Calculated Using Average Daily Balance

If you use balance forward billing, use the Average Daily Balance charge calculation method to calculate late charges.
Seings That Aect Late Charge Calculation Using Average Daily Balance
These seings aect 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 dened in system options or customer proles.
◦ 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 Prole Class: Set these options for late charges in the Credit Limits and Late Charges tab on the
Create Receivables Customer Prole Class page, or on the applicable customer or customer site prole:
◦ Enable late charges option: Set the Enable late charges option to enable the assessment of late charges
for customers assigned this prole.
◦ Late Charge Calculation Method eld: Select the calculation method Average Daily Balance.
345
◦ 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.
How Late Charges Using Average Daily Balance Are Calculated

The Average Daily Balance charge calculation method is based on the average daily balance of overdue invoices for
balance forward bills. The formula is:
(Daily Balance/Number of Days in Billing Cycle) * (Interest Rate/100)
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.
Date Activity Student Balance
June 1 No activity $0

June 2 Enroll in class $1,000

June 3 No activity $1,000

June 4 $250 payment $750

June 5 No activity $750

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 Seing Up Balance Forward Billing
346
Guidelines for Presenting Late Charges

During your late charges setup, you must decide how to record and present late charges to your customers.
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 specic 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 prole, then credit items belonging
to the customer reduce the outstanding overdue amount during late charge calculations.
You must complete these steps to record late charges as adjustments:
1. Select Adjustment in the Late Charge Type eld on the Credit Limits and Late Charges tab of the applicable
customer prole.
2. Dene a Late Charges receivables activity and enter an activity GL account.
3. If you assess penalties in addition to late charges, then dene 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 prole, then credit items belonging
to the customer reduce the outstanding overdue amount during late charge calculations.
347
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 prole.
2. Dene a transaction source for late charges with a type of Imported. Receivables creates a debit memo batch
using the Invoice API.
3. Dene a transaction type for late charges:
◦ Select a class of Debit Memo.

◦
Specify the receivable and revenue accounts for this transaction type. Receivables uses these accounts
instead of AutoAccounting when generating late charges.
4. Assign the transaction source and transaction type to Billing and Revenue system options:
◦
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 proles 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 prole, 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 prole.
2. Dene a transaction source for late charges with a type of Imported. Receivables creates an interest invoice
batch using the Invoice API.
3. Dene a transaction type for late charges:
◦ Select a class of Invoice.

◦
Specify the receivable and revenue accounts for this transaction type. Receivables uses these accounts
instead of AutoAccounting when generating late charges.
4. Assign the transaction source and transaction type to Billing and Revenue system options:
◦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 prole class, or on an individual
customer or customer account prole.
If you set this option, then if the eective dates for two charge schedules occur within a charge calculation
period, both rates apply to late charge calculations during that period.
348
6. Select payment terms for the applicable customer proles to indicate the interest invoice due date.
Guidelines for Processing Interest Invoice Late Charges by Legal

Entity
You can generate separate late charges as interest invoices for each legal entity associated with an overdue transaction.
These separate late charges interest invoices apply to each legal entity associated with the active ledger of the business
unit of overdue transactions.
When you set up interest invoice late charges by legal entity, a run of the Create Late Charges process performs these
operations:
• Generates a separate late charge interest invoice for each legal entity associated with the active ledger of the
business unit of the overdue transaction.
• Replaces the balancing segment value of the receivable and revenue account code combinations of the late
charge interest invoice, as dened in Receivables system options, with the balancing segment value assigned to
the legal entity of the overdue transactions.
Set Up for Interest Invoice Late Charges by Legal Entity

To set up for interest invoice late charges by legal entity, you must:
• Complete the setups for recording late charges as interest invoices.
• Create a lookup code to enable the replacement of the legal entity balancing segment value.
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 dened 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.
Example of Generating Interest Invoice Late Charges by Legal Entity

The following example illustrates how a run of the Create Late Charges process generates interest invoices by legal
entity and manages balancing segment values.
349
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 dened as the primary balancing segment):
• Receivable Account: 01-1410000-3-1010-00-000-C-0

• Revenue Account: 01-210000-3-1010-00-000-C-0
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):
Transaction Number Transaction Date Due Date Legal Entity BSV
I-101 4/9/2018 5/9/2018 Vision Operations 01

I-102 3/19/2018 4/3/2018 Vision Services 02

I-103 4/22/2018 5/21/2018 Vision Services 02

I-104 3/5/2018 4/19/2018 Vision Foods 03, 04

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
2030 05-31-2018 2001 Vision Operations I-101 01-1410000-3-1010-00-000-

01-210000-3-1010-00-000-
C-0 C-0

2030 05-31-2018 2002 Vision Services I-102, I-103 02-1410000-3-1010-00-000-

02-210000-3-1010-00-000-
C-0 C-0

2030 05-31-2018 2003 Vision Foods I-104 01-1410000-3-1010-00-000-

01-210000-3-1010-00-000-
C-0 C-0

• 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
Examples of Using a Minimum Customer Balance with Late

Charges
In situations where it is not cost eective to calculate and collect late charges for small amounts, you can set a minimum
customer balance for late charges.
You set a minimum customer balance per currency on the Credit Limits and Late Charges tab of the Create Receivables
Customer Prole Class page, or on the applicable customer or customer site prole. Receivables only assesses late
charges when the minimum balance of the applicable customers is exceeded.
These examples illustrate the dierence 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 submiing the Create Late Charges program on dierent dates (May 20 or May 30)
can potentially change the activity that is selected for late charge calculation.
This table includes a timeline of debits and credits to a customer account:
Date Charge Type Amount
April 10 Debit $200

April 12 Debit $200

May 4 Debit $100

May 6 Credit $50

May 13 Credit $25

May 18 Credit $200

May 24 Credit $50

May 27 Debit $100

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
Create Late Charges on May 20: Overdue Transactions Only

The Overdue Transactions Only calculation method compares the minimum customer balance to the sum of all
customer debit and credit activities as of the date when you run the Create Late Charges program.
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.
Create Late Charges on May 20: Average Daily Balance

The Average Daily Balance calculation method starts with the ending balance of the last balance forward bill, and
subtracts all credits (receipts and credit memos) up through the due date plus receipt grace days to determine if the
customer balance is eligible for late charges.
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.
Create Late Charges on May 30: Overdue Transactions Only

If you submit the Create Late Charges program on May 30, then the customer balance includes 4 overdue invoices
(April 10, April 12, May 4, and May 27) for a total of $600. The balance also includes 4 payments (May 6, May 13, May 18,
and May 24) for a total of $325.
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.
Create Late Charges on May 30: Average Daily Balance

In this example, submiing the Create Late Charges program on May 30, as opposed to May 20, doesn't change the
customer balance calculation.
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).
Example of Seing Up a Late Charge Policy

This example demonstrates how to set up a late charge policy for the customer Business World. The example includes
the setup of late charge documents, the Business World customer prole, and your user-dened seings.
This table summarizes key decisions for this scenario.
352
Decisions to Consider In This Example
Which document will record late charges? Adjustments

What period basis is used for late charge calculations? Monthly

Which currencies? US dollar and British pound sterling

Are there exceptions to the general policy? Yes, for the customer account site and customer transactions

Summary of the Tasks

The calculation of late charges is determined by your late charge policy. The late charge policy comprises the late
charge document, Receivables system option seings, and customer prole seings.
1. Dene a Late Charges receivables activity..

2. Set Receivables system options for late charges.
3. Set up the Business World customer prole for late charges.
4. Update the customer site and customer transactions for late charges.
Dene a Late Charges Receivables Activity

To record late charges as adjustments, dene a Receivables activity for late charges:
1. Open the Create Receivables Activity page.

2. Complete the elds, as shown in this table:
Field Value
Name that identies this Receivables activity as a late charge adjustment.

Name
Late Charges
Activity Type
General ledger account for late charges.

Activity GL Account
Set Receivables System Options for Late Charges

Set Receivables system options for late charges:
1. Open the Create or Edit Receivables System Options page.

2. Complete the elds in the Late Charges section of the Billing and Revenue tab, as shown in this table:
353
Field Value
Enable this option.

Assess late charges
Name of the Late Charges receivables activity that you previously dened.
Interest Charge Activity
Set Up the Customer Prole

Set up the customer prole for Business World for late charges:
1. Open the Create Receivables Customer Prole Class page.

2. Complete the general required elds for the prole class.
3. Click the Credit Limits and Late Charges tab.
4. Complete the elds in the Late Charges section, as shown in this table:
Field Value
Enable this option.

Enable late charges
Overdue Invoices and Late Payments

Late Charge Calculation Method
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
5. In the Currency Seings section, click the Add icon.

354
Field Value
USD (US Dollar)

Currency
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
7. Repeat steps 5 and 6 for British pound sterling (GBP).

8. Assign this prole class to the Business World bill-to site.
Update the Customer Site and Transactions

Update the Business World customer site and transactions for late charges:
1. Open the Statement, Dunning, and Late Charges Site Proles Used prole option.
2. Set the prole option to No.
By seing this prole 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.
Field Value
Late charges exemption

Name
Invoice
Transaction Class
Open
Transaction Status
355
Field Value
Enable this option.

Exclude from late charges
calculation
5. Assign this transaction type to the applicable invoice transactions.
Generate Late Charges Report

Use the Generate Late Charges Report to review a run of the Generate Late Charges program. You can also print the
report for an individual late charge batch.
The Generate Late Charges Report outlines the specic late charges that were calculated, whether you ran the process
in Draft or Final mode. The report includes sections for each type of charge, such as overdue transactions, late
payments, and penalties.
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.

Original Amount The original transaction amount.

Overdue Amount The balance of the transaction that is still outstanding.

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.

Interest Rate The rate used to calculate the late charges.
356

Interest Charge The amount of interest charged on the outstanding balance.

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.

Currency The currency for the late charge calculation.

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.

FAQs for Process Late Charges

Why didn't late charges appear on transactions?
You must ensure that you assign an interest charge to each currency that you do business in for the applicable
customer proles. If you don't assign an interest charge to a currency, then Receivables doesn't calculate late charges
for past due items in that currency.
To ensure that late charges appear on transactions, enter values in the Interest Charge Type eld, and either the
Interest Charge Rate, Interest Charge Amount, or Interest Charge Schedule eld for each currency in the Late
Charges section of the customer prole.
If you also assess penalty charges, then complete the related elds for penalty charges.
Process Statements
357
Example of Cross-Site and Cross-Customer Receipts on

Statements
Customer statements accurately record and report on receipts that were applied across customers and customer sites.
The statement process displays each cross-customer or cross-site receipt on the statement of the customer or
customer site associated with the transaction to which the receipt was applied, as well as on the statement of the
customer or customer site that owns the receipt. The Reference column on the statement includes the amount of
each receipt, and the corresponding Transaction column displays the amount of each receipt applied to a specic
transaction.
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 eect 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.
This table illustrates the statement that the SF site receives:
Invoice Transaction Reference Site Transaction Amount

Amount
Invoice 1 Invoice NA SF 200.00 NA

Invoice 1 Payment check p1 200.00 CA -150.00 50.00


Invoice 5 Payment check p5 700.00 SF -600.00 NA

Invoice 5 Payment check p6 600.00 CA -600.00 0.00

Unapplied Payment check p2 500.00 SF -100.00 NA

Unapplied Payment check p5 700.00 SF -100.00 -200.00

Cross Receipt Payment check p2 500.00 SF 400.00 NA


358

Amount

This table illustrates the statement that the CA site receives:

Amount
Invoice 2 Invoice NA CA 500.00 NA

Invoice 2 Payment check p2 500.00 SF -400.00 100.00


Invoice 3 Payment check p3 500.00 CA -500.00 NA

Invoice 3 Payment check p4 100.00 SF -100.00 0.00

Unapplied Payment check p1 200.00 CA -50.00 -50.00

Cross Receipt Payment check p1 200.00 CA 150.00 NA

Cross Receipt Payment check p6 600.00 CA 600.00 0.00

Create Customer Statements Execution Report

Use the Create Customer Statements Execution Report to review a run of the Create Customer Statements program.
Review this report after you submit customer statements. You can also use this report to review draft statements before
sending them to your customers.

Transaction Business Unit
The selected business unit to print customer statements for.
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 specied customers or statement cycle
359
• Reprint Statements: Reprint a previous statement for specied customers or statement cycle.
Bucket
The name of the aging bucket to use for statements.
Cycle
The statement cycle for the statement submission.
Statement Date
The date on which to print statements.
As-of Date
The date from which to include data on statements.
Transaction Type
Print statements for this transaction type only.
Primary Salesperson
Print statements for this salesperson only.
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.
Selected Report Headings

Remit-to Address
The address for your customers to use to send payment for their open debit items.
Bill-to
The customer name and address for each statement. The country of the customer address is included if it is
dierent from the home country specied in Receivables system options.
Note: If you do not have a statement address dened 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
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 identies 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 dene as your rst bucket.
1-30 Days Past Due

Customer open item information based on the aging bucket you dene as your second bucket.
361
31-60 Days Past Due

Customer open item information based on the aging bucket you dene as your third bucket.
61-90 Days Past Due

Customer open item information based on the aging bucket you dene as your fourth bucket.
Over 90 Days Past Due

Customer open item information based on the aging bucket you dene as your fth bucket.
Financial Charges
The total amount of late charges for the customer site.
Total Amount Due

The total amount due for the customer site in the entered currency. If the customer has open items in multiple
currencies, the report contains a separate page for each currency.
Related Topics
• How to Use Statement Cycles
• How do on-account and unapplied receipts appear on statements
FAQs for Process Statements

What's the dierence between printing a statement and a draft statement?
When you print a statement, you must provide both an As of Date and a Statement Date. If you set the Print Option
parameter to Print Draft Statement, the process uses the As of Date parameter value.
If you set the Print Option parameter to Print Statement, the program uses the Statement Date parameter value.
What's the dierence between a statement and a balance forward bill?

A statement is an information document that provides a customer with a complete record of transaction, receipt, and
adjustment activity over a specied time period.
A balance forward bill is a single bill presented for payment that consolidates the open debit items of a customer over a
specied time period.
How many statements will a customer receive?

If you dened a statement site for the customer, Receivables generates a single, consolidated statement of all customer
activity for the specied period and sends the statement to this site.
If you have not dened a statement site for a customer, Receivables generates statements for each customer bill-to site
for the specied period that has these prole seings:
• Send statement option is enabled.

• Statement Cycle is provided.
• Minimum outstanding balance in the given currency is greater than the Minimum Statement Amount value.
362
Close Receivables Accounting Period

Receivables Accounting Event Model
An accounting event is a business event in Receivables that has an accounting impact. For example, creating or
applying a receipt is an accounting event.
Not all business events have an accounting impact, but you can decide which events you want to monitor as accounting
events. You can modify the accounting setup to create accounting for some events and not for others.
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 predened 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 predened 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
denitions.
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 aect how the Create Receivables Accounting program determines the subledger
accounting for it. Event types provide the lowest level of detail for storing accounting denitions.
Transactions Event Entity

This table describes the predened event classes and event types for the Transactions event entity.
Event Class Event Types
Chargeback Chargeback Created

Credit Memo Credit Memo Created

Credit Memo Updated

Debit Memo Debit Memo Created

Debit Memo Updated

363
Invoice Invoice Created

Invoice Updated

Receipts Event Entity

This table describes the predened event classes and event types for the Receipts event entity.
Miscellaneous Receipt Miscellaneous Receipt Created

Miscellaneous Receipt Reverse

Miscellaneous Receipt Updated

Receipt Receipt Created

Receipt Reverse

Receipt Updated

Adjustments Event Entity

This table describes the predened event classes and event types for the Adjustments event entity.
Adjustment Adjustment Created

Bills Receivable Event Entity

This table describes the predened event classes and event types for the Bills Receivable event entity.
Bills Receivable Bills Receivable Created

Bills Receivable Updated

364
Guidelines for Receivables to General Ledger Reconciliation

Periodically you need to reconcile the transactions in your accounts receivable system, both before and after you post to
the general ledger. The Receivables to General Ledger Reconciliation extract and report help to simplify this process and
reduce the amount of manual reconciling activity required.
The automated activities in the reconciliation process function according to the way you set up your Financials
environment. A review of some of these setups can help improve the overall reconciliation process.
Review these activities related to seing up your Financials environment for Receivables to General Ledger
reconciliation:
• Business Unit vs. Ledger Reconciliation

• Accounts Receivable Financial Category
• Prole Option Seings
• User Security
Business Unit vs. Ledger Reconciliation

If you implicitly map primary balancing segment values to your business unit, you can reconcile based on business unit.
This allows employees from dierent business units to balance their respective organization activity.
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 specic 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.
Accounts Receivable Financial Category

You must assign the nancial category of Accounts Receivable to all of your receivables natural account values. This is a
required setup step for Receivables to General Ledger reconciliation. You perform this task under the Manage Chart of
Accounts Value Sets activity.
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 specic 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 unidentied, 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 Unidentied Receipts parameter.
365
Caution: You must assign unique general ledger accounts to unidentied, 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 dierences.
Prole Option Seings

Review the seing of these prole options:
• Reconciliation Data Purge Frequency
• Zero Amount Journal Lines Displayed
Use the Reconciliation Data Purge Frequency prole 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 prole
option. If there are any reconciliation data extract requests in the table older than the number of days specied in the
prole option, these requests are purged.
For example, if a reconciliation data extract is run on January 1, and the value of this prole 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 prole option aects whether journal lines with zero amounts display in the
Not Transferred to GL Detail report. If this prole 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 eect 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
denition, as well as general ledger data for all balancing segment values in the ledger.
However, if security is congured such that the data role for the General Ledger or Receivables job roles also have FND
grants to specic business units for General Ledger users or specic 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
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 specic business units for the General Ledger job roles,
and from specic data access sets for the Receivables job roles.
Related Topics
• Chart of Accounts Components
Extract Reconciliation Data from Receivables to General Ledger

Run the Prepare Receivables to General Ledger Reconciliation program to select data for the Summary section of the
Receivables to General Ledger Reconciliation Report. The extract must run successfully in order to see the most current
Summary report, and before you can run the Receivables to General Ledger Reconciliation Report.
Use the following parameters of the Prepare Receivables to General Ledger Reconciliation program to control the
Receivables transaction activity that you intend to include in the extract:
• Business Unit
• Include Intercompany Transactions
• Include On-Account Items
• Include Unapplied and Unidentied Receipts
Tip: To avoid unintended reconciling dierences, 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 specic 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 dierences.
Prepare Receivables to General Ledger Reconciliation Parameters

Request Name
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
Use this parameter if you need to reconcile by a specic organization.
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.
Include Intercompany Transactions
You can include or exclude Intercompany transactions, or you can reconcile by Intercompany activity only.
Include On-Account Items
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 dierences.
Include Unapplied and Unidentied Receipts
You can include or exclude unapplied receipts and unidentied receipts. Unapplied receipts are receipts that haven't yet
applied; unidentied receipts are receipts without customer information.
Note: You may want to exclude unapplied and unidentied receipts if they typically post to non-
receivable accounts. If you plan to exclude unapplied and unidentied 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 dierences.
Account
You can select values from any of the segments of the accounting exeld. 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 unidentied 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
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.
Guidelines for Using the Receivables to General Ledger

Reconciliation Report
Use the Receivables to General Ledger Reconciliation report to facilitate the reconciliation of receivables data to the
general ledger.
The interactive reporting capability of the Receivables to General Ledger Reconciliation report provides both
summarized and detailed reconciling data for review. The Summary report lets you see receivables and accounting
beginning and ending balances, as well as summarized activity for the period and how this activity was accounted.
Drill down on any amount in the Summary report Dierence column to display the Dierences Detail report for that
item. The Dierences Detail reports display the details that make up balances from the Summary report, and indicate
potential causes for dierences between actual and reconciling amounts.
Note: For a more ecient 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 aect the display of data in the detail reports and may be the cause of a
dierence 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
dierences 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:
• Dierences between Transactional and Accounted Amounts

• Dierences between Summary and Detail Amounts
• Dierences between the Reconciliation Report and the Aging Report
• Recommendations for Reconciling by Business Unit and by Intercompany Activity
• Recommendations for Reconciling Unapplied and Unidentied Receipts and On-Account Items
• Recommendations for Reconciling Bills Receivable
369
Dierences between Transactional and Accounted Amounts

Ideally the Summary report should display no dierences between receivables transactional amounts and accounted
amounts. In addition, the beginning and ending receivables balances should agree with the Receivables Aging by
Account report.
Note: It may happen that the Summary report will contain variance amounts. If the Summary report contains
variance amounts, contact your system administrator.
Any dierences that you nd require further investigation and possible correction. Common reasons for dierences
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 dierences may be valid. For example, if you included unapplied and unidentied 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 dierence that is outside the account range of
the report. In this case, you can re-run the extract and exclude these items.
Dierences between Summary and Detail Amounts

The Non-Receivables Begin Balance amount is any portion of a general ledger account beginning balance that didn't
originate from Receivables transactions. You can drill down on this amount to see a list of general ledger journal lines
that have an accounting date that falls within the current scal year but prior to the period of the reconciliation report;
and that have an account combination that falls within the account range of the report.
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 specic
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 aect 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.
Summary amounts may not reect totals on detail pages because:

• Data was modied after the data extract was run for a given accounting period. If transactions or accounting
were created or modied between the time the extract was executed and the moment you drill down from a
summary amount to its detail amounts, the summary amount won't reect the detail page totals.
To limit discrepancies between the summary and detail reports, set the Receivables accounting period status to
Close Pending or Closed.
• Security rules in your setup may restrict you from seeing data from certain business units or segment values.
370
Ensure that appropriate security is given to users for all business units and accounting exeld segment values
that each user is responsible for reconciling.
Dierences between the Reconciliation Report and the Aging Report

You may nd dierences between the data displayed in the Receivables to General Ledger Reconciliation report and the
Receivables Aging by Account report. This list provides the principle reasons why this occurs and recommendations for
working with these dierences:
• 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 dierences 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
Recommendations for Reconciling by Business Unit and by Intercompany Activity

To reconcile by business unit, you need to have an implicit mapping of the business unit to one or more primary
balancing segment values. When you run the Prepare Receivables to General Ledger Reconciliation program, you
must specify both the business unit to reconcile and the balancing segment value or range of values assigned to that
business unit. The Business Unit parameter selects the receivables activity and the balancing segment value selects the
accounting data.
You have three options for reconciling Intercompany activity:
• Include Intercompany activity with other Receivables activity.

• Exclude Intercompany activity from reconciliation.
• Include only Intercompany activity.
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
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.
Recommendations for Reconciling Unapplied and Unidentied Receipts and On-

Account Items
If you want to exclude unapplied and unidentied receipts, and on-account items, from reconciliation, set the Include
Unapplied and Unidentied Receipts parameter and the Include On-Account Items parameter to No, and exclude
the respective ranges of accounts from the extract. To avoid reconciling dierences, unapplied and unidentied
receipts, and on-account items, should not post to the same general ledger accounts as that used for transactions. If
they do, then the accounting for transactions would also be excluded.
If you never include unapplied and unidentied 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.
Recommendations for Reconciling Bills Receivable

Two rows on the Summary report display bills receivable activity for the accounting period:
• Bills Receivable: Bills receivable created (unsigned or drawee-issued), accepted (signed), and canceled during
the accounting period.
• Bills Receivable Applications: All customer transactions applied to bills receivable created, accepted, and
canceled during the accounting period.
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 Remied, 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
Reports for Close Receivables Accounting Period

Potential Reconciling Items Report
During the internal reconciliation process, you use the Receivables to General Ledger Reconciliation Report to conrm
that transactional data and accounting data match. However, even if the data matches, the journals could still post to
incorrect general ledger accounts, due to issues with your Receivables setup.
Use the Potential Reconciling Items Report to help you identify and correct these setup issues.
372
You typically run the Potential Reconciling Items Report:
• For new software installations, prior to running nal accounting, in order to conrm the correct derivation of
accounting.
• Whenever the accounting setup has been modied--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 oset 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, conrmation, or remiance 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.
Possible causes for discrepancy include:
• Incorrect accounting setup.

• Incorrect manual updating of general ledger account distributions.
• Setup created for activities that is inconsistent with the intended use of Receivables.
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
Overview of the Projected Gains and Losses Report

This topic contains summary information about the Projected Gains and Losses Report.
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.

The following table lists frequently asked questions about the Projected Gains and Losses Report.
FAQ Answer

374
FAQ Answer

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.



Projected Gains and Losses Report

Use the Projected Gains and Losses Report to review open foreign (non-ledger) currency invoices, debit memos, and
chargebacks revalued according to the revaluation rate that you specify. The report compares the revalued amount of
each debit item with the entered amount and prints the unrealized gain or loss.
The report summarizes by customer and prints, for each transaction type, the total debit item foreign currency amount
by currency and the unrealized gain or loss, with subtotals for each transaction type and customer.
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 dierence 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 Type
Conversion rate type to use as the revaluation rate.
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 dened.
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.
From/To Accounting Date
Debit item accounting date range.
From/To Customer Name or Account Number
Customer range. The report summarizes transactions by customer account.
375
Report Output
This table describes important column headings in the Projected Gains and Losses Report.
Invoice Type The transaction type assigned to the transaction.

Currency The transaction entered currency.

Entered Amount The transaction amount in the entered currency.

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.
Currency Summary Heading Description
Currency The identier of each foreign currency.

Foreign Invoice Amount The total transaction amount in each foreign currency.
376
Currency Summary Heading Description

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 of the Receivables Aging by General Ledger Account Report

This topic contains summary information about the Receivables Aging by General Ledger Account 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

The following table lists frequently asked questions about the Receivables Aging by General Ledger Account Report.
FAQ Answer


When do I use this report? Review information about your customer outstanding receivables balances by general ledger
account as of a specic accounting date.

What can I do with this report? Schedule periodically.


Receivables Aging by General Ledger Account Report

Use the Receivables Aging by General Ledger Account Report to review information about outstanding receivables
balances by general ledger account as of a specic accounting date and customer or customer site. You can use this
report both for aging and for reconciliation to the general ledger.
The following notes refer to using the Receivables Aging by General Ledger Account Report for reconciliation:
• Select report parameter values consistent with the parameters of the Receivables to General Ledger
Reconciliation extract and report for inclusion or exclusion of on-account credits, unidentied payments, and
on-account and unapplied cash.
• Select the same balancing segment value as for the Receivables to General Ledger Reconciliation extract and
report.
Note: You can run the reconciliation report for other segments of the accounting exeld, but
this can cause dierent results between the two reports because only the Balancing Segment
parameter is used by the aging report.
• 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 exeld.
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
Use the Receivables Aging by General Ledger Account Report:

• During reconciliation, to compare with the balances of the Receivables to General Ledger Reconciliation Report.
378
• To age or summarize open receivables.

Balancing Segment
Always select specic balancing segment values rather than running the report for all values.
Transaction As-of Date
Accounting date from which to include receivable open items.
Report Summary
• Customer Summary: Prints customer names with their total open balances.
• Invoice Summary: Prints information on all customer open receivables.
Report Format
The report format aects customer information, not transaction information:

• Brief: Prints customer name and customer account number with item information.
• Detailed: Prints customer city and state with contact name and telephone number.
Aging Bucket
Prints information from the bucket set you specify.
Show Open Credits
Select whether and how to include credit items in the report:

• Age: Receivables ages your credit items and includes the credit amounts in the appropriate aging bucket
columns.
• Do Not Show: The report does not include credit items in your customer balances. In this case, the report does
not display any of your unapplied, on-account or unidentied payments, or on-account credit memos.
• Summarize: Displays the sum of your credit items in the Customer Credit Memos, Customer Payments, and
Customer Balance rows.
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.
Show Receipts at Risk
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
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 Flexeld
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 exeld. 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.
Customer Credit Memos

The total amount of credit memos for each customer if you set the Show Open Credits parameter to Summarize.
This total is included in the Customer Balance row 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
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.
Site Credit Memos

If you set the Show Open Credits parameter to Summarize, this displays the total amount of credit memos for
each customer site. This total is included in the Site Balance row for each customer.
Total Customer Balance

The total customer balance for all customers in the report.
Total for All Customers

The totals for all customers in the report.
Total Payments and Credit Memos

The total of credit items for all customers in the report.
Total for Accounting Flexeld

The total for each unique account code combination of the accounting exeld.
Total for Report

This total only appears when the Report Summary parameter is set to Invoice Summary.
If you set the Show Open Credits parameter to Summarize, this total does not include credits.
381
Overview of the Receivables Open Items Revaluation Report

This topic contains summary information about the Receivables Open Items Revaluation Report.
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.

The following table lists frequently asked questions about the Receivables Open Items Revaluation Report.
FAQ Answer

382
FAQ Answer

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 reect the dierence between the
original and revalued balance.



Receivables Open Items Revaluation Report

Use the Receivables Open Items Revaluation Report to revalue your open items, including invoices, credit memos, and
debit memos. The report takes into account changes in the value of your receivables due to changes in foreign currency
rates. You revalue open items based on the revaluation rate that you specify, which is either an end-of-period rate or a
daily rate.
The Receivables Open Items Revaluation Report provides you with three amounts:
• 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 dierence. 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 reect the dierence between the original and revalued balance. This revaluation dierence is calculated and
summarized for each accounting exeld. 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.
Include up to Due Date
383
Enter a date if you want to dierentiate 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
Select the rate type to use to revalue open transactions:
• Period. Rate at the end of the revaluation period.

• Daily. If you select Daily, then enter values for the Conversion Rate Type and Conversion Date parameters.
Conversion 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 aect
open balances.
• No: Include both posted transactions and transactions and receipts not yet posted to aect open balances.
Cleared Only
• Yes: Only cleared receipts aect open balances.

• No: Both cleared receipts and receipts not yet cleared aect open balances.
Balancing Segment
Dene 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.
Revaluation Date The date of the revaluation.

Balancing Segment Each value of the balancing segment for the selected balancing segment range.

Accounting Flexeld The accounting exeld 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
Transaction Number The number of the transaction.

Transaction Type: The transaction type assigned to the transaction.

Transaction Date The date the transaction was created.

Due Date The date payment is due on the transaction.

Currency The transaction entered currency.

Open Original Amount The transaction amount in the entered currency. The report prints an asterisk if the open
amount diers from the original amount. The open amount may dier 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 dierence between the Revaluation Open Amount and the Open Ledger Currency
Amount. During reconciliation, debit the receivables account if the dierence is positive; credit
the receivables account if the dierence 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 exeld of the receivables
account.

Customer Account Number The account number of the customer with items charged to the accounting exeld of the
receivables account.

Total The transaction totals.

385
Total for [Customer] The customer totals.

Total for Accounting Flexeld The accounting exeld totals.

This table describes the summary headings in the Receivables Open Items Revaluation Report.
Summary Heading Description
Accounting Flexeld The accounting exeld that totals are calculated for.

Open Ledger Currency Amount The total for each accounting exeld, balancing segment, and the entire report.

Revalued Amount The total for each accounting exeld, balancing segment, and the entire report.

Dierence The total for the dierence between the Open Ledger Currency Amount and the Revaluation
Open Amount for each accounting exeld, balancing segment, and the entire report.

Open Revalued Amount The total for each accounting exeld, balancing segment, and the entire report.

Dierence The total for the dierence between the Open Ledger Currency Amount and the Open
Revalued Amount for each accounting exeld and the entire report.

Total The total for the report.

386
Overview of the Receivables to General Ledger Reconciliation Report

This topic contains summary information about the Receivables to General Ledger Reconciliation Report.
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.

The following table lists frequently asked questions about the Receivables to General Ledger Reconciliation Report.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Receivables to Ledger
Reconciliation


When do I use this report? When you are reconciling your receivables to your general ledger balances.
387
FAQ Answer

What can I do with this report? Review report after running the Prepare Receivables to General Ledger Reconciliation
scheduled process.



This report uses these subject areas:
• Receivables - Adjustments Real Time
• Receivables - Bill Receivable Real Time
• Receivables - Credit Memo Applications Real Time
• Receivables - Receipt Details Real Time
• Receivables - Standard Receipt Application Details Real Time
• Receivables - Transactions Real Time
• Subledger Accounting - Journals Real Time
• Subledger Accounting - Receivables Summary Reconciliation Real Time
• General Ledger - Journals Real Time
• General Ledger - Transactional Balances Real Time
FAQs for Close Receivables Accounting Period

How are accounts reconciled to general ledger?
The Receivables to General Ledger Reconciliation report only reconciles accounts receivable for accrual basis
accounting, and only reconciles accounting in the primary ledgers.
The Receivables to General Ledger Reconciliation report reconciles the transaction types that impact the accounts
receivable in general ledger. These include:
• Invoice
• Debit memo
• Credit memo
• On-account credit memo
• Chargeback
• Adjustment
• Applied receipt
• On-account receipt
• Unapplied receipt
• Unidentied receipt
388
• 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 aect 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.
Note: This mapping is not dened anywhere in Receivables or General Ledger.
What happens to accounting periods during reconciliation?

When you drill down in the Receivables to General Ledger Reconciliation report, you see real-time details that make up
balances from the summary report. In order to guarantee that the summary balance for each type of activity agrees
with the drill-down detail, you must ensure that you limit access to an accounting period when you run the Prepare
Receivables to General Ledger Reconciliation program. Otherwise additional activity might be added to that period after
the extract has run.
Set the accounting period status to Closed or Close Pending. You typically set the accounting period to Close Pending
during the review process, and then reopen the period if adjusting entries need to be added. You must ensure that the
subsequent accounting period is open, in order that business operations continue during the reconciliation process.
There is one important dierence 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.
Either status will prevent additional entries in the closed period.
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.
What's a variance amount?

A variance amount is a line in the Receivables to General Ledger Reconciliation report that displays the total amount of
variance between transactional and accounted amounts.
Variance amounts are due to some type of data corruption. There are two types of variance amounts: receivables
variance and accounting variance. A receivables variance is the result of data corruption in the Receivables tables. An
accounting variance is the result of data corruption either in subledger accounting or the general ledger. Variance
amounts don't display in any other section of the summary or detail reports.
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
Why can't I close an accounting period?

One or more exceptions are preventing you from closing the accounting period.
Set the period status to Close Pending and run the Subledger Period Close Exceptions report. This report provides
detailed information about your accounts, including any exceptions that may prevent you from closing an accounting
period. After you clear the exceptions, you can close the accounting period.
What's the dierence 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 diers 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 seing it to Close
Pending.
Reports for Customer Account Balances
390
Overview of the Bad Debt Provision Report

This topic contains summary information about the Bad Debt Provision Report.
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 prole to calculate the bad debt provision.

The following table lists frequently asked questions about the Bad Debt Provision Report.
FAQ Answer
How do I nd this report? Reports and Analytics pane - Shared Folders - Financials - Receivables - Accounting


When do I use this report? When you need customer overdue transaction collectibility information to create the provision
for bad debt accounting journals.
391
FAQ Answer
What can I do with this report? Schedule periodically.


Bad Debt Provision Report

Use the Bad Debt Provision Report to review your bad debt exposure. The report prints for each customer all open debit
items, unapplied receipts, and on-account credits, and the provision for bad debt based on the percent collectible.
The Bad Debt Provision Report uses the percent collectible value that you specify in the Collectible eld of the Credit
and Collections section of the customer account prole to calculate the bad debt provision. The report does not include
customers with proles that do not have a value assigned to this eld.
Submit this report according to your customer account review requirements.
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
Overview of the Customer Account Status Report

This topic contains summary information about the Customer Account Status Report.
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.

The following table lists frequently asked questions about the Customer Account Status Report.
FAQ Answer

Who uses this report? Financial Specialist or Financial Manager when analyzing customer accounts.
393
FAQ Answer

When do I use this report? When you want to analyze the detail that makes up the customer account balances by specic
account statuses or collectors.



Customer Account Status Report

Use the Customer Account Status Report to review your customer accounts. The report displays for each customer all
open debit items, credit items, and total balance due in the ledger currency.
Run this report according to your customer account review process.

Order By
Arrange the information in the report by Collector, Customer Name or Customer Account Number.
From/To Account Status
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.

Class Indicates a debit item, credit item, bill receivable or payment.

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
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
Overview of the Customer Balance Revaluation Report

This topic contains summary information about the Customer Balance Revaluation Report.
Overview
The Customer Balance Revaluation Report identies 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.

The following table lists frequently asked questions about the Customer Balance Revaluation Report.
FAQ Answer


When do I use this report? When you need to create accounting journals for revaluated customer accounts and identify
customers with negative balances.


396
FAQ Answer

Customer Balance Revaluation Report

Use the Customer Balance Revaluation Report to identify customers with credit (negative) balances. The enterprises in
certain countries are required to enter a manual journal entry to adjust the general ledger balance for these customers.
The report provides you with two results:
• 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 seing 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
reect the dierence 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 noties you that the results calculated may be incorrect.
Run this report in conjunction with both your customer account reviews and reconciliation activities.

Revaluation Period
The period that you want to revaluate.
Include up to Due Date
If you want to dierentiate short-term, mid-term, and long-term receivables activities, enter a date in this parameter.
Otherwise, leave the eld blank.
Customer Balance
• Show positive Balance: List only customers with a positive balance.

• Show negative Balance: List only customers with a negative balance.
• Show positive and negative Balance: List the balance for all customers. This is the default.
Report Output
This table describes important column headings in the Customer Balance Revaluation Report.
397
Transaction Number The number of the transaction.

Transaction Type The name of the transaction type.

Transaction Date The date of the transaction.

Due Date The due date of the transaction.

Currency The transaction currency.

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

Tip: The Debit and Credit totals help you determine the amount of the adjustments to your general ledger
balances.
FAQs for Review Customer Account Balances

When is a receipt at risk?
You can apply a receipt to an open debit item before cash is actually received from the bank. Receipts with a Standard
remiance method are considered at risk if they have been conrmed, but not yet cleared. Receipts with a Factored
remiance method are considered at risk if they haven't yet been risk-eliminated.
By default receipts at risk appear as part of the customer open balance. Enable the Exclude receipts at risk option to
remove these receipt amounts from the open balance calculation.
What is the total open receivables amount?

The total open receivables amount is the amount per currency of the amount in the Total Transaction Due Amount
column less the amount in the Receipts Pending Application Amount column. This amount provides the current
receivables position of a customer account.
What is the last transaction and last receipt?

The Review Customer Account Details page displays information about the most recent transaction and the most recent
receipt belonging to the selected customer account. If there were multiple transactions or receipts on the same date, the
page displays the transaction and receipt with the largest amount.
This display is by date and, if applicable, by amount only. The transaction and receipt displayed don't necessarily
reference the same business unit or share the same entered currency.
What's the dierence between account activity and transaction

activity?
Activity against a customer account refers to the transactions and payments that go into the details of the account.
Customer account activities include:

• Invoice
• Credit Memo
• Debit Memo
399
• Chargeback
• Payment (receipt)
Activity against an individual transaction or receipt refers to the specic debits, credits, reversals, and adjustments that
constitute the history of one receivables item.
400
Using Receivables Credit to Cash Manage Revenue for Receivables
5 Manage Revenue for Receivables
Process Revenue for Receivables

How You Recognize Revenue on Transactions
Run the Recognize Revenue process to generate the revenue distribution records for invoices and credit memos that
use invoicing and revenue scheduling rules. Revenue scheduling rules determine the number of periods and the
percentage of total revenue to record in each accounting period. Invoicing rules determine when to recognize the
receivable for invoices that span more than one accounting period.
The Recognize Revenue process selects all transactions that have invoicing and revenue scheduling rules and that
haven't yet been processed since the last submission of the process. This includes new transactions, unprocessed
transactions, and partially processed transactions. The Recognize Revenue process creates the revenue distribution
records for all accounting periods specied by the revenue scheduling rule on each transaction line.
Creation of Revenue Distributions

The Recognize Revenue process creates distribution records for invoices and credit memos both created manually
and imported using AutoInvoice. The Recognize Revenue process uses the accounting distributions dened by
AutoAccounting to determine the accounts for the revenue distribution records. If a transaction contains a deferred
revenue scheduling rule, then the Recognize Revenue process instead creates the distribution records for the specied
unearned revenue account. Deferred revenue is later recognized according to the contingencies associated with the
particular transaction.
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 reclassied, 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.
Review of Unprocessed or Partially Processed Transactions

The Revenue Recognition Execution report contains a section called Unprocessed or Partially Processed Transactions,
for transactions that failed processing for revenue recognition.
A transaction can fail revenue recognition processing either partially or completely:
• 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
• 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:
• Incorrect accounting period on the transaction.

• Missing data needed to process revenue recognition on the transaction.
Review of Transactions with Invalid Accounts

The Revenue Recognition Execution report contains a section called Transactions with Invalid Accounts, for transactions
that were successfully processed for revenue recognition but contained invalid revenue accounts.
Note: The Transactions with Invalid Accounts section only appears on the execution report when the
Recognize Revenue process is submied 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
Examples of Deferred and Non-Deferred Revenue Scheduling

Rules
Revenue scheduling rules determine the number of accounting periods and percentage of total revenue to record in
each accounting period for a transaction. When you use deferred revenue scheduling rules, the Recognize Revenue
program creates a single distribution per line that posts to an unearned revenue account. You later earn the revenue
either when a contingency expires or by manually scheduling the revenue.
You can use deferred revenue scheduling rules only for invoices that are assigned the In Advance invoicing rule. If
you use a deferred revenue scheduling rule with a single accounting period, Receivables recognizes the revenue in the
period that you specify.
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
Revenue Recognition with a Deferred Revenue Scheduling Rule

This table illustrates revenue recognition on a $300 invoice with a 3-month deferred revenue scheduling rule and an
original start date of February 2. In this example, all accounting periods are open.
Accounting Date February March April May
February 2 $100 $100 $100 $0

March 2 $0 $100 $100 $100

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.
Revenue Recognition with a Non-Deferred Revenue Scheduling Rule

This table illustrates revenue recognition on a $300 invoice with a 3-month non-deferred revenue scheduling rule. In
this example, February is at rst open, but is later closed before you can nish adjusting the invoice revenue.
Accounting Date February March April May
February 2 $100 $100 $100 $0

March 2 $0 $200 $100 $0

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
FAQs for Process Revenue for Receivables

How does my revenue policy aect revenue recognition?
If you set up a revenue policy, Receivables assigns revenue contingencies to any transaction or transaction line that
violates the policy, and defers revenue on these transactions or transaction lines.
There are three policy areas that can cause the assignment of revenue contingencies:
• Creditworthy customer: If a customer is considered not creditworthy, Receivables assigns a payment-based

revenue contingency to the transaction and only recognizes revenue to the extent of payments received.
• Refund policy: If the transaction is associated with a contract that oers a refund period that exceeds the
refund policy, Receivables assigns a time-based revenue contingency to the transaction and only recognizes
revenue after the refund policy period expires.
• Payment terms: If the transaction has payment terms that exceed the payment terms policy, Receivables
assigns a payment-based revenue contingency to the transaction and only recognizes revenue to the extent of
payments received.
Why do transactions require manual scheduling?

If a transaction has a deferred revenue scheduling rule, then all revenue is assigned to the unearned revenue account.
You recognize revenue manually for these transactions at the appropriate time, according to the revenue policy of your
enterprise.
For transactions assigned time-based revenue contingencies, you can recognize revenue manually if the contingency is
met in advance of the specied time period, for example, a customer provides early acceptance of the terms of a post-
billing customer acceptance clause.
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.
When do I expire a revenue contingency?

You can expire a revenue contingency at any time, according to the circumstances surrounding the contingency and the
related transaction.
For example, you may need to expire one contingency on a transaction line and assign a new contingency to the same
transaction line. In other cases, a contingency may be assigned in error to a transaction.
You can expire a time-based contingency if the terms of the contingency are met in advance of the specied time
period, such as a change in time-period for a funding clause or acceptance clause.
Process Revenue Adjustments for Receivables
404
Implementation Seings for Revenue Recognition

You must ensure that you enable certain seings in order to recognize revenue properly on your transactions.
These seings inuence revenue recognition on your transactions:
• Enable Salesperson System Options
• Dene Lookups for Revenue Recognition
• AutoAccounting based on Standard Line
Enable Salesperson System Options

You must enable the Require salesperson Receivables system option for revenue accounting. Revenue accounting
requires that you assign sales credits to all transactions that can be adjusted for either revenue or sales credits. If you
don't normally track sales credits, and you want to use revenue accounting for revenue adjustments only, use the
default salesperson value of No Sales Credit.
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.
Dene Lookups for Revenue Recognition

Dene these lookups for revenue recognition, according to your requirements:
• Use the Revenue Adjustment Reason lookup type to dene reasons specic to your enterprise for making
revenue adjustments.
• You can assign payment-based revenue contingencies to the transaction lines of transactions that use the
In Arrears invoicing rule. This lets you recognize revenue after you receive payment, instead of recognizing
revenue according to the revenue recognition schedule. Use the AR_FEATURES lookup type to dene the
AR_CONT_INV_INARREARS_RULE lookup to enable this feature.
AutoAccounting based on Standard Line

If AutoAccounting is set to derive accounting segments based on standard line, the transaction line must be either an
inventory item or a standard memo line. Otherwise, AutoAccounting can't derive a valid account code combination for
revenue recognition.
Modications to Invoices with Deferred Revenue

You can modify invoice lines that have deferred revenue or revenue contingencies.
You can make these modications:
• Adjust revenue
• Adjust invoices
• Modify distributions and sales credits
• Credit invoices
• Reverse receipts
Each activity has a dierent eect on active revenue contingencies.
405
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 specied
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.
Modify Distributions and Sales Credits

You can manually change the accounting distributions and sales credits on 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 diers depending on the original reason for the revenue deferral. This applies only if
you set the Invoice Accounting Used for Credit Memos prole 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. Dierent 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
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 conrm 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 diers depending on the original reason for the revenue deferral.
Dierent procedures apply depending on whether the contingencies are payment-based or time-based:
• Payment-based contingencies: If you apply a receipt to an invoice with a payment-based contingency,

Receivables initiates revenue recognition for the applied amount. If you later reverse the receipt, Receivables
automatically unearns the previously earned revenue.
• Time-based contingencies: If you apply a receipt against an invoice line with an unexpired time-based
contingency, Receivables leaves the receipt amount as unearned revenue, but marks the amount as pending
revenue recognition when the contingency expires. If you later reverse the receipt, then Receivables reects the
receipt reversal by simply removing the pending status from the receipt amount.
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.
How You Transfer Sales Credits

If you transfer sales credits for all salespersons to a new salesperson using the Entire Revenue Amount option, this
action transfers 100% of sales credits from all salespersons on the specied lines to the new salesperson.
If you transfer sales credits for all salespersons to a new salesperson using the Schedule Percentage of Total Amount
of Selected Lines option, this action transfers only the specied percentage, prorated across the original salespersons
based on their current sales credits.
Example of Transferring Sales Credits

Three salespersons are assigned to a transaction line with a revenue split of 20:30:50. If you transfer all adjustable
revenue to a new salesperson, the new salesperson receives 100% (20 + 30 + 50).
If you transfer only 5%, the new salesperson receives 5% of the line total and the transferred amount is prorated among
the three salespersons.
This table illustrates the transfer of sales credits:
407
Salesperson Revenue Split Transfer Percentage Prorated Transfer

Percentage
Salesperson 1 20 5% .05 * 20 = 1

Salesperson 2 30 5% .05 * 30 = 1.5

Salesperson 3 50 5% .05 * 50 = 2.5

Sales Credits and AutoAccounting

In order to transfer sales credits, you must set up AutoAccounting to derive at least one segment of the revenue
account from salesperson. If no revenue account segment is derived from salesperson, the transfer of revenue sales
credits does not have an accounting impact. If there are no sales credits on the transaction, then you cannot add non-
revenue sales credits.
If you update sales credits on the Edit Transaction page, do not rerun AutoAccounting if all of these factors apply:
• AutoAccounting is based on salesperson.

• Update of Existing Sales Credits Allowed prole option is set to Yes.
• You previously adjusted revenue on the transaction using the Manage Revenue Adjustments pages.
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
How Multiple Contingencies Are Processed

If multiple contingencies exist on multiple invoice lines, then revenue recognition can occur at dierent times for
dierent lines on the invoice. If multiple contingencies exist on a single invoice line, then revenue recognition for that
line occurs only after the latest contingency expires.
Seings That Aect Invoices with Multiple Contingencies

A single invoice or invoice line can contain both payment-based contingencies and time-based contingencies:
• 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
How Multiple Contingencies Are Calculated

Multiple contingencies are calculated dierently for each of these circumstances:
• Two time-based contingencies on the same invoice.
• Two time-based contingencies on the same invoice line.
• Payment-based and time-based contingencies on the same invoice.
Two time-based contingencies on the same invoice

You enter a customer invoice with 6 lines. Lines 2 and 3 are associated with a scal funding clause (60 days) and
Line 5 is associated with a cancellation provision (90 days). Revenue for Lines 1, 4, and 6 are fully recognized, either
immediately or according to the existing revenue scheduling rules.
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.
Two time-based contingencies on the same invoice line

You enter or import an invoice for a creditworthy customer, and one of the invoice lines is associated with both a
nonstandard refund policy (50 days) and an acceptance clause (120 days).
Receivables doesn't recognize revenue on this invoice line until the acceptance clause expires after 120 days. If, for
example, you obtain wrien 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.
Payment-based and time-based contingencies on the same invoice

You import a customer invoice with 2 lines. Line 1 is $150 and Line 2 is $1,000. Line 2 is associated with an acceptance
clause (60 days) and a cancellation provision (150 days). In addition, the customer has been granted extended payment
terms on this invoice. Due to the existing contingencies, Receivables can't recognize revenue for either line on this
invoice.
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.
After 75 days, you apply a $650 receipt against the invoice:

• Receivables recognizes the remaining $84.79 in revenue for Line 1.
• Receivables still can't recognize revenue for Line 2 because of the acceptance clause and cancellation provision.
Receivables assigns another $565.21 for Line 2 as an amount that is pending revenue recognition. The total
amount for Line 2 that is pending revenue recognition is now $1,000.
409
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
Examples of Revenue Recognition after Receipt Application

These examples illustrate the impact of receipt applications on transactions with deferred revenue or 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.
Partial Receipt Application

You import a $350 invoice with three invoice lines. Receivables defers all revenue because the customer wasn't
creditworthy.
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 aribute 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
Partial Receipt Application with Multiple Contingencies

You apply a payment for $400 against invoice 3003. This invoice has 5 lines: Line 1 is $200, Line 2 is $450, Line 3 is
$100, Line 4 is $700, and Line 5 is $550.
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.
Examples of Accounting for Credit Memos Against Invoices with

Revenue Contingencies
These examples illustrate the accounting for partial credit memos against an invoice with revenue contingencies.
The details of the invoice setup are:
• An invoice is imported for $750.
• The invoice has 3 lines:
◦ Line 1 is $200
◦ Line 2 is $450
◦ Line 3 is $100
• The invoice has 2 revenue contingencies:
◦ Line 1 is associated with a nonstandard 90-day refund policy.
411
◦ Line 3 is associated with a 120-day cancellation provision.
• Invoice Accounting Used for Credit Memos prole option = Yes.

• Customer has extended payment terms.
First Transaction
This table shows the initial accounting entry:
Accounts Receivable 750.00 None

Unearned Revenue None 750.00

Second Transaction
You apply a $300 receipt against the invoice, 45 days after the invoice date.
Based on the weighted average formula, Receivables applies:
• $80 to Line 1.
• $180 to Line 2.
• $40 to Line 3.
The result of these applications is as follows:
• 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.
This table describes the accounting entry:
Cash 300.00 None

Accounts Receivable None 300.00

Unearned Revenue 180.00 None

Earned Revenue None 180.00

The total amount due on this invoice is now $450. The unearned revenue amount on this invoice is $570.
412
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.


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

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.
Based on the weighted average formula, Receivables applies:

• $27 to Line 1.
• $60 to Line 2.
• $13 to Line 3.
At this point, all time-based contingencies have expired.
Cash 100.00 None




414
The invoice is now fully paid and no unearned revenue remains.
FAQs for Process Revenue Adjustments for Receivables

What's the dierence between scheduled revenue and unscheduled revenue?
Revenue is scheduled when Receivables creates, for a transaction line, the revenue distribution records for all
accounting periods as specied by the revenue scheduling rule assigned to each line. Scheduled revenue doesn't mean
that the revenue amounts are already earned. It means only that Receivables has created the distribution records for
these amounts.
Revenue that is unscheduled is deferred to an unearned revenue account. Revenue remains unscheduled either until
you manually schedule the revenue or an event triggers the automatic recognition of previously deferred revenue, for
example, the customer makes a payment.
What happens if I change the accounting date?

If you change the accounting date, this becomes the new start date for revenue recognition, in place of the revenue
start date on the transaction line.
You can change the accounting date provided either of these factors is true:
• There is no revenue scheduling rule on the transaction line.

• If there is a revenue scheduling rule, it is for a single period only.
If a revenue scheduling rule with more than one period exists, Receivables uses the original start date and revenue
recognition schedule on the transaction.
What's the dierence between revenue and nonrevenue sales credits?

Revenue sales credits refer to the percentage of revenue generated from the sale recorded on a transaction or
transaction line that is alloed to each salesperson.
Non-revenue sales credits refer to additional revenue above the transaction or transaction line amount alloed to a
salesperson that is unrelated to the sale itself, for example, a sales bonus.
Can I update sales credits on the transaction?

Yes, you can update sales credits on the transaction or transaction line before posting to the general ledger.
The primary salesperson is assigned when you rst enter the transaction. You only need to enter or update sales credit
information on the transaction in these cases:
• Assign sales credits to more than one salesperson.

• Distribute credit across transaction lines.
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
416
Using Receivables Credit to Cash Manage Bills Receivable
6 Manage Bills Receivable
Create and Process Bills Receivable

Guidelines for Applying Transactions to Bills Receivable
You can apply any class of transaction to a bill receivable. You can also apply a bill receivable that has the status Unpaid
to a new bill receivable.
By default, you can only apply transactions that belong to the drawee and its related customers. If the Receivables
system option Allow payment of unrelated transactions is enabled, then you can apply transactions of unrelated
customers to the bill.
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 dierent 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
Guidelines for Batching Transactions for Bills Receivable

Use the Create Bills Receivable Batch program to create a batch of bills receivable from customer transactions. Use the
program parameters to specify the desired options for the batch and to limit the selection of transactions to batch for
bills receivable.
Transactions eligible for inclusion in a bills receivable batch require these seings:
• Paying customer dened as drawee.
• Bills receivable creation receipt method.
• All transactions must have the same currency and conversion rate.
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
• Bills Receivable Creation Receipt Methods
Bills Receivable Transaction Sources

Transaction sources for bills receivable require these seings:
• Source type of Manual.
• Automatic batch numbering option enabled.
• Value entered in the Last Number eld.
• Transaction source is both valid and active on the issue date of the bills receivable created by the program.
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 seings on the
transaction source.
Bills Receivable Dates

Review the guidelines related to entering and using these bills receivable dates: accounting date, issue date, and
maturity date.
This table describes the guidelines to follow for entering dates in bills receivable batches.
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:
• On or after the system date.

• Valid for the date of the bills receivable creation receipt method assigned to
transactions.
• Valid for the bills receivable transaction type.
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
Bills Receivable Creation Receipt Methods

The bills receivable creation receipt method assigns important values to bills receivable, and determines how
transactions are grouped into bills receivable.
This table describes the guidelines to follow for working with bills receivable creation receipt methods in bills receivable
batches.
Seing Guideline
Bills Receivable Transaction Types

Because transaction types are set-enabled, the Transaction Type parameter of the Create Bills
Receivable Batch program only makes available for selection the bills receivable transaction
types:
• 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.
Number of Bills Receivable Rule

The value of the Number of Bills Receivable Rule eld determines how to group transactions
into bills receivable:
• If the rule is One per Customer or One per Customer Due Date, then at least one
customer must contain an active drawee site dened as Primary. These rules cannot
group transactions from dierent customer sites with no site dened 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 dened as a drawee site.
Related Topics
• Create a Bills Receivable Creation Receipt Method
How Bills Receivable Are Numbered in a Batch

The numbering of bills receivable in a batch depends on the seings of the bills receivable creation receipt method and
the bills receivable transaction source.
If only one transaction is assigned to the bill receivable created by the batch, then the batch process uses the
transaction number as the bill receivable number provided both of these conditions apply:
• 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
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
Requirements for Completing a Bill Receivable

Use the Complete buon to complete bills receivable transactions.
To complete a bill receivable, you must:
• Enter all required information for the bill.
• Apply transactions to the bill. Transactions must have the same currency as the bill, and all transactions must
have the same conversion rate.
• Apply transactions to equal the designated amount of the bill, if applicable.
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 wrien 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 Remiance
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.
Record Drawee Acceptance of a Bill Receivable

When you complete a bill receivable that requires drawee acceptance, the bill is assigned the status Pending Acceptance
with no accounting date specied. A bill receivable requires drawee acceptance if the Signed option is enabled.
After the customer drawee accepts the bill receivable, use the Accept action to record the acceptance. In the Accept
window:
• Enter in the Date eld the date that the customer drawee accepted the bill receivable. This date must be after
the bill receivable issue date.
The date that you enter becomes the date that the transactions are applied to the bill.
420
• If necessary, in the Accounting Date eld, update the accounting date.
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.
After you accept the bill:
• Receivables records the rst accounting for the bill.

• The applications reduce the amounts due on the related transactions.
• The bill receivable appears in the outstanding balance of the customer drawee.
• The bill is updated with the status Pending Remiance.
Related Topics
• What's the dierence between a signed and unsigned bill receivable
FAQs for Create and Process Bills Receivable

What's a bill receivable?
A bill receivable is a separate transaction in Receivables. A bill receivable is a document that a customer formally agrees
to pay at some future date (the maturity date).
The bill receivable document eectively replaces, for the related amount, the open debit items that are applied to the
bill. Bills receivable are often remied for collection and used to secure short term funding.
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.
When do I number a bill receivable?

If the bills receivable transaction source doesn't specify automatic transaction numbering or copying of the document
sequence number to the bill number, or if you are not using document sequencing, then you must enter a number for
the bill receivable. Otherwise, the bill receivable is numbered when you save.
If you are using manual document sequencing, then you must enter a unique document number.
What happens if I assign an amount to the bill receivable?

This becomes the maximum amount for the bill. The total amount of the transactions applied to the bill must equal the
designated maximum amount in order to complete the bill.
If you don't enter a maximum amount, the amount of the bill is calculated as the sum of the applied transaction
amounts when you complete the bill.
Why doesn't the bill receivable have an accounting date?

Because the bill is a signed bill that requires drawee acceptance. Once the bill receivable is accepted, Receivables assigns
an acceptance accounting date to the bill.
421
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.
Why can't I create bills receivable from transactions?

Because you have to assign transactions both a bills receivable creation receipt method and a paying customer dened
as a drawee. Only transactions with these assignments are eligible for bills receivable batches.
Can I incomplete and delete a bill receivable?

Yes, but you can only incomplete a bill receivable under certain conditions.
All of these conditions must be true:
• The bill receivable is a signed bill with the status Pending Acceptance, or an unsigned or drawee-issued bill with
the status Pending Remiance.
• The bill has never been posted to general ledger.
• There are no payments against the bill.
After you incomplete the bill you can delete it.
You can also incomplete a bill receivable to update details of the bill and complete the bill again.
Remit Bills Receivable

Overview of Bills Receivable Remiances
Remit bills receivable to your remiance bank or other nancial institution to initiate the collection process from your
customers. Before remiing to a bank, you must create, review, and approve the bills receivable in a remiance batch.
You can create these types of bills receivable remiances:
• Standard remiances: 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 remiances, you bear the nancial
risk of customer default.
• Factored remiances: 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 remiance. 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 remiance.
When you create a bills receivable remiance, the receipt class determines the remiance processes, and the bills
receivable remiance receipt method assigned to the receipt class determines the accounting for the bills receivable.
Receivables selects qualifying bills receivable for remiance and groups them according to the remiance bank that
is assigned to each bill. You can specify additional selection criteria to limit the bills receivable that are selected for
remiance.
422
Create a Bills Receivable Remiance Batch

Create a bills receivable remiance batch from eligible bills receivable transactions. During batch creation, Receivables
uses the currency and remiance bank information to select bills receivable. You can specify additional selection criteria
to limit the bills that are selected for remiance using the Select and Add: Bills Receivable window.
All bills receivable with the status Pending Remiance are eligible for selection. You can also include bills receivable with
the status Unpaid if the Include Unpaid Status option is enabled.
Based on the remiance bank information, Receivables selects the following bills receivable for inclusion in the batch:
• Bills receivable with the same remiance bank account as the remiance batch.
• Bills receivable with no remiance bank account.
• Bills receivable with a dierent bank account from that of the remiance batch, if the Ignore Override option is
not enabled.
Note: You can change the batch remiance bank information after the remiance batch is created. However,
you will receive a warning if the remiance bank of any bill receivable in the batch is dierent from the new
remiance bank of the batch, unless the Override bank option is enabled on that remiance bank account.
After you have entered information for the batch and your selection criteria, use the Save buon to generate the bills
receivable remiance batch. Receivables validates the status, currency, and remiance 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 remiance batch, you can't apply customer payments or other activities to the bill,
or select the bill for another remiance batch.
After creating the remiance batch, use the Mange Bills Receivable Remiance Batches page to review, update, and
approve the batch.
Related Topics
• Create a Bills Receivable Remiance Receipt Method
• Create a Remiance Bank Account for Bills Receivable
Create and Clear Receipts for Bills Receivable Remiances

During the course of the bills receivable remiance process, Receivables both creates and clears receipts for bills
receivable.
Create Receipts for Bills Receivable Remiances

Receivables creates a receipt for each bill receivable that is remied to the bank. The bills receivable remiance receipt
method for the remiance batch determines when a receipt is created. You create a receipt to record the accounting
event of the expected funds transfer.
The receipt creation process diers for standard and factored remiances:
• Standard remiances: 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 remiance date plus
423
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 remiances: Receivables creates a receipt when a remiance 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 Remied.
For bills receivable factored without recourse, the receipt is applied to the bill receivable upon remiance and
the status of the bill is updated to Closed.
Clear Receipts for Bills Receivable Remiances

The clearing method of the bills receivable receipt class belonging to the bills receivable remiance receipt method
determines when Receivables clears receipts and recognizes cash in the remiance process. You dene the clearing
method, number of clearing days and risk elimination days when you set up the bills receivable remiance receipt class
and method.
Select one of these clearing methods:

• Directly: Receivables clears the receipt upon creation, and recognizes cash on the receipt date.
• Automatic Clearing: Run the Clear Receipts Automatically program to clear receipts on the receipt dates plus
the number of clearing days. For standard remiances, the receipt date is either the maturity date plus the
number of collection days or the remiance date plus the number of collection days, whichever is later. For
factored remiances, the receipt date is simply the remiance date.
• By Matching: Use Cash Management to clear the receipt and reconcile cash to your bank statements.
Related Topics
• Automatic Clearing of Receipts
• Remiance Methods and Clearance Methods
Close Matured Bills Receivable Process

Use the Close Matured Bills Receivable process and report to create and apply receipts for standard remied bills
receivable, and to apply receipts and eliminate risk on bills receivable factored with recourse. The corresponding report
lists the adjustments to each bill receivable and shows all receipts that were cleared by the program run.
Process Tasks
You can run the Close Matured Bills Receivable process to accomplish a number of dierent tasks in relation to bills
receivable remiances.
These tasks are:

• Create the receipt on the maturity date for standard remiances.
• Create the receipt when the remiance is approved for factored remiances.
• Unapply the receipt from short term debt and apply it to the bill receivable at the maturity date plus risk
elimination days for remiances factored with recourse.
• Update the bill receivable status to Matured Pending Risk Elimination at the maturity date plus risk elimination
days, and update the bill status to Closed for eliminating risk on bills receivable factored with recourse.
For standard remied 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 remied with insucient time for the bank to collect the funds from the drawee by the maturity date, then
Receivables performs these operations on the remiance date plus the number of remiance bank collection days.
424
You can clear receipts for standard remied 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 remiance 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.
Accounting Date Parameter

Enter the accounting date to use for the transactions generated by the process and report. You can enter any date in an
open accounting period.
For standard remiances, 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 remiances, 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 remiance. If the accounting date entered for the remiance is
also not in an open period, then it uses the rst day of the next available open period.
FAQs for Remit Bills Receivable

When can I approve a bills receivable remiance batch?
Once you have reviewed the bills receivable remiance batch and are satised with its content. Approving the
remiance batch initiates the accounting event for the specic type of bills receivable remiance. Depending on the
remiance method, the status of the bills receivable is updated from Pending Remiance to either Standard Remied or
Factored Remied.
What happens if the drawee makes a payment prior to remiance approval?

You can deselect the bill receivable from the remiance batch and apply the receipt directly to the bill receivable.
Can I reverse or unapply bills receivable receipts?

Yes, if the receipts were applied to the bills receivable and not to short term debt. You can reverse or unapply receipts
that were created for payments received from customer drawees or receipts that were created from the remiance
process.
For bills receivable factored with recourse, receipts are applied to short term debt before the bill maturity date plus risk
elimination days. For receipts applied to short term debt, use the Recall action to recall the bill receivable and reverse
these receipt applications.
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
Remiance.
• If the receipt is reversed after the maturity date, the status of the bill receivable is updated to Unpaid.
425
Update Bills Receivable

Bills Receivable Statuses
During the life cycle of a completed bill receivable, the status of the bill changes over time. Some of these changes are
necessary and normal, while others depend on specic events particular to a given bill.
This table lists each bills receivable status and its meaning.
Status Meaning
Pending Acceptance The bill was completed, but requires acceptance by the customer drawee.

Pending Remiance The bill was completed, and, if necessary, accepted, and is ready for remiance.

Remied The bill was remied to the bank for collection on the maturity date.

Factored The bill was remied 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.

Protested The customer drawee protests a bill in the status Unpaid.

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.

Bills Receivable Risk

Create factored bills receivable remiances to remit bills receivable as collateral in return for cash advances or loans
from your bank.
For bills receivable factored with recourse, you bear the nancial risk of customer default. When you create a bill
receivable factored with recourse, Receivables records a short term debt for the default risk. The bills receivable
remiance receipt method assigns the number of risk elimination days to the bill. The risk elimination days are
the number of days after the bill receivable maturity date that you can clear short term debt on your factored bills
receivable.
426
Receivables applies receipts created at the time of remiance 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:
• Unapplies the receipt from short term debt.

• Applies the receipt to the factored bill receivable at the maturity date plus risk elimination days. The apply date
is the bill receivable maturity date plus the number of risk elimination days.
• Eliminates the risk on the factored bill receivable.
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.
Unpaid Bills Receivable

On the bill receivable maturity date, the drawee is expected to pay the bill. If payment is not received, you should mark
the bill as Unpaid.
You can mark a bill receivable as Unpaid under the following statuses and with the related conditions:
• Pending Remiance, and the bill receivable has not been selected for remiance, placed on hold, or reserved by
another bill receivable pending acceptance.
• Standard Remied, 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 Remied or Factored with Recourse and then Closed as Unpaid, Receivables reverses the receipt
created as a result of the remiance.
You can later remove a bill receivable from the Unpaid status by using the Restate action. When you restate a bill
receivable, Receivables reclassies the bill from Unpaid to Pending Remiance.
427
Recall a Bill Receivable from Remiance

If necessary, you can recall a remied or factored bill receivable from the remiance batch. You may need to recall a bill
from remiance if, for example, there was an error in the remiance process or you received payment for the bill from
the customer.
Select the bill receivable that you want and use the Recall action to enter the necessary information. The recall date and
accounting date that you enter must be on or after the remiance date.
When you submit the recall:
• If the bill receivable is recalled before the maturity date, the status of the bill receivable is updated to Pending
Remiance.
• 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.
Examples of Accounting Entries for Bills Receivable Activities

These examples illustrate the journal entries that Receivables creates for each bills receivable activity.
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:
Debit Account Credit Account
Bills Receivable Receivables

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 Remiance)
• Unpaid Bills Receivable (if the bill has the status Unpaid)
428
Remied Bills Receivable

When you remit a bill receivable with a standard remiance method, Receivables creates this journal entry on the bill
receivable:
Remied Bills Receivable • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
• Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
On maturity (or maturity plus the number of collection days, if the bill is remied on or after maturity), Receivables
creates this journal entry on the receipt created:
• Remiance (if the clearance Remied Bills Receivable

method used is By Automatic
Clearing or By Matching)
• Cash (if the clearance method
used is Direct)
Factored Bills Receivable with Recourse

When you factor a bill receivable with recourse, Receivables creates this journal entry on the bill receivable:
Factored Bills Receivable • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
• Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
Receivables creates this journal entry on the receipt created when factoring with recourse:
• Remiance (if the clearance Short Term Debt

method used is By Automatic
used is Direct)
When you eliminate the risk on a bill receivable factored with recourse, Receivables creates this journal entry on the
receipt created:
429
Short Term Debt Factored Bills Receivable

When you reestablish risk on a bill receivable factored with recourse, Receivables creates this journal entry on the
receipt created:
Factored Bills Receivable Short Term Debt

Factored Bills Receivable without Recourse

When you factor a bill receivable without recourse, Receivables creates this journal entry on the receipt created:
• Remiance (if the clearance • Bills Receivable (if the bill had the status Pending Remiance before it was remied)
method used is By Automatic • Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
used is Direct)

When you mark as unpaid a bill receivable with the status Pending Remiance, Receivables creates this journal entry on
the bill receivable:
Unpaid Bills Receivable Bills Receivable

When you mark as unpaid a bill receivable with the status Standard Remied, Receivables creates this journal entry on
the bill receivable:
Unpaid Bills Receivable Remied Bills Receivable

When you mark as unpaid a bill receivable with the status Closed that was previously standard remied:
• Receivables creates this journal entry on the bill receivable:
430
Unpaid Bills Receivable Remied Bills Receivable

• The accounting entries are reversed on the receipt that was applied to the bill receivable:

◦ Cash (if the receipt was cleared)
◦ Remiance (if the receipt wasn't cleared)
When you mark as unpaid a bill receivable with the status Matured Pending Risk Elimination or Closed that was
previously factored with recourse:
Unpaid Bills Receivable Factored Bills Receivable

• Receivables creates this journal entry on the receipt created when the bill was factored with recourse:
◦ Short Term Debt (if the bill

was Matured Pending Risk
Bills Receivable Funds Recovery

Elimination)
◦ Factored Bills Receivable (if
the bill was Closed)
• Receivables creates this journal entry on the negative miscellaneous receipt created when the bill receivable
factored with recourse is marked as unpaid:
Bills Receivable Funds Recovery

◦ Cash (if the original receipt was cleared)
◦ Remiance (if the original receipt wasn't cleared)
431
When you mark as unpaid a bill receivable with the status Matured Pending Risk Elimination or Closed that was
previously factored without recourse:

◦ Bills Receivable (if the bill had the status Pending Remiance before it was remied)
◦ Unpaid Bills Receivable (if the bill had the status Unpaid before it was remied)
• Receivables creates this journal entry on the receipt created when the bill was factored without recourse:
◦ Bills Receivable (if the bill

had the status Pending
◦ Cash (if the receipt was cleared)
Remiance before it was ◦ Remiance (if the receipt wasn't cleared)

remied)
◦ Unpaid Bills Receivable (if
the bill had the status Unpaid
before it was remied)
When you restate a bill receivable that was previously marked as unpaid, Receivables creates this journal entry on the
bill receivable:
Bills Receivable Unpaid Bills Receivable

Recalled Bills Receivable

When you recall a bill receivable that was previously standard remied or factored:
◦ Bills Receivable (if the bill

had the status Pending
◦ Remied Bills Receivable (if the bill was standard remied)
Remiance before it was ◦ Factored Bills Receivable (if the bill was factored with recourse)
remied
the bill had the status Unpaid
before it was remied)
432
• Receivables creates this journal entry on the receipt created when the bill was factored:
◦ Short Term Debt (if the bill

was factored with recourse)
◦ Remiance (if the clearance method used is By Automatic Clearing or By Matching)
◦ Bills Receivable (if the bill was ◦ Cash (if the clearance method used is Direct)
factored without recourse
and had the status Pending
Remiance before it was
remied)
the bill was factored without
recourse and had the status
Unpaid before it was remied)
Transaction and Receipt Applications

When you apply a receipt to a bill receivable, Receivables creates this journal entry on the receipt:
• Cash (if the receipt was • Bills Receivable (if the bill has the status Pending Remiance)
cleared) • Unpaid Bills Receivable (if the bill has the status Unpaid or Protested)
• Remiance (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 Remiance)
• 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 dierent company segment.
FAQs for Update Bills Receivable

When do I cancel a bill receivable?
When you want to return the debt to the transactions that were originally applied to the bill. You typically cancel a bill
receivable if it was created in error or if you prefer to apply payments to transactions that were applied to the bill.
433
Use the Mark as Canceled action to cancel a bill. You can cancel a bill that is Pending Acceptance, Pending Remiance,
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 Remiance or Unpaid, Receivables unassigns the applied transactions and creates reverse
accounting entries.
What's the dierence between holding and protesting a bill receivable?

Place a bill receivable on hold when you want to exclude the bill from remiance while you investigate information
about the bill or about the transactions applied to the bill. You can only place bills on hold with the status Pending
Remiance or Unpaid. You can later release the bill receivable from hold and make it available again for remiance.
Mark a bill receivable as under protest if the drawee protests a bill receivable with the status Unpaid, for example,
because of a disagreement as to the maturity date or of payments submied. There is no accounting impact on a
bill under protest. Once the protest is resolved, you can either mark the bill as Unpaid again or, if applicable, apply a
customer receipt to the protested bill.
Reports for Manage Bills Receivable
434
Overview of the Automatic Bills Receivable Transactions Batch

Report
This topic contains summary information about the Automatic Bills Receivable Transactions Batch Report.
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 submied in
Draft.

The following table lists frequently asked questions about the Automatic Bills Receivable Transactions Batch Report.
FAQ Answer

435
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 submied in Draft.


Set the Batch Mode parameter of the Create Bills Receivable Batch process to Draft.

Automatic Bills Receivable Transactions Batch Report

Use the Automatic Bills Receivable Transactions Batch Report to review the contents of a bills receivable batch. A bills
receivable batch contains bills receivable created from customer drawee transactions.
You can run the report in Detail mode or Summary mode. The report lists the bills receivable created in a batch, or the
bills receivable that will be created in a batch submied in Draft. The report is also generated in Detail mode when you
run the Create Bills Receivable Batch program.

Business Unit
The selected business unit for the report.
Batch Name
The name of the bills receivable batch.
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.
Drawee Name The name of the customer drawee.

Drawee Number The account number of the customer drawee.
436

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, specied in the bills receivable creation receipt method, that a bill
receivable can have.

Minimum The minimum amount, specied in the bills receivable creation receipt method, that a bill
receivable can have.

Lead Days The number of days before the transaction due date, specied in the bills receivable creation
receipt method, that a transaction was eligible to be applied to a bill receivable.

Currency The ledger currency.

This table describes the column headings in the output of the Automatic Bills Receivable Transactions Batch Report.
Bills Receivable Number The bill receivable number.

Amount The amount assigned to the bill.

Maturity Date The date payment is due on the bill receivable.

Drawee Bank Name The name of the customer drawee bank.

Contact Name The contact person at the customer drawee bank.

Special Instructions Any special instructions for processing the bill.

Bills Receivable Transaction Type The bills receivable transaction type assigned to bills receivable created from transactions by
the bills receivable creation receipt method.

Issue Date The date the bill receivable is created.

437
Accounting Date The bill receivable accounting date.

Document Number The document sequence number assigned to the bill, if applicable.

Transaction Number The number of the transaction applied to the bill.

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
438
Overview of the Bills Receivable Remiance Batch Management

Report
This topic contains summary information about the Bills Receivable Remiance Batch Management Report.
Overview
The Bills Receivable Remiance Batch Management Report provides detailed information about a bills receivable
remiance batch.
Key Insights
Review both remiance batch information and information about each bill receivable in the batch.

The following table lists frequently asked questions about the Bills Receivable Remiance Batch Management Report.
FAQ Answer
How do I nd this report? Scheduled Processes - Create Bills Receivable Remiance 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 Remiance Batch process.

What can I do with this report? According to your bills receivable remiance schedule.

439
FAQ Answer

Bills Receivable Remiance Batch Management Report

Use the Bills Receivable Remiance Batch Management Report to review a run of the Create Bills Receivable Remiance
Batch program. You can run the program either as a scheduled process or from the Create or Edit Bills Receivable
Remiance Batch pages.
You can also use the Manage Bills Receivable Remiance Batches page to search for and review remiance batches.
Review this report each time you generate a bills receivable remiance batch.

Business Unit
The selected business unit for the report.
Remiance Batch Date
The creation date of the remiance batch.
Remiance Batch Accounting Date
The accounting date of the remiance batch.
Approve
Indicate whether to approve the remiance batch when it is generated. Approving the remiance batch initiates the
accounting event for the bills receivable remiance.
Currency
The currency for the remiance batch. The program selects bills receivable eligible for remiance with this currency.
Remiance Method
• Standard: Remit bills receivable to the remiance bank.

• Factoring: Remit bills receivable as collateral in return for cash advances or loans from the remiance bank.
When the remiance batch is approved, create the receipt for the bill receivable.
With Recourse
If you set the Remiance Method parameter to Factoring:
• Yes: You bear the nancial risk of customer default.

• No: The bill receivable is closed and the remiance bank assumes the risk of customer default.
440
Receipt Class and Method
The bills receivable remiance receipt class and receipt method to use to create the remiance batch.
Remiance Bank Branch and Bank Account
The remiance bank and account for this remiance batch. The program selects both eligible bills receivable with this
remiance bank account, and eligible bills receivable with no remiance bank account assigned.
Include Unpaid Status
Bills receivable with the status Pending Remiance that match the other criteria for this remiance batch are eligible for
selection. If you select Yes, then bills receivable with the status Unpaid are also eligible for selection.
Minimum Remiance Total
Only create a remiance batch if the total amount of eligible bills receivable equals or exceeds this amount.
Maximum Remiance Total
Only create a remiance 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 Remiance Batch: Information about the remiance batch.
• Remied Bills Receivable: Information about each bill receivable in the remiance batch.
Bills Receivable Remiance Batch

Batch Name
The name or number of the remiance batch.
Batch Date
The remiance 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
Remiance Bank Account Name

The remiance bank account name.
Remiance Method
Standard or Factoring.
Factored With Recourse

• Yes: Bills receivable factored with recourse.
• No: Bills receivable other than factored with recourse.
Payment Method
The remiance receipt method used to create the remiance batch.
Accounting Date
The remiance accounting date.
Currency
The remiance currency.
Batch Amount
The total remiance amount in the remiance currency.

Drawee Name
The customer drawee name.
Drawee Account Number

The customer drawee account number.
Drawee Bank
The customer drawee bank.
Bills Receivable Number

The number of the bill receivable.
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 remiance amount for each customer.
442
Number of Bills Receivable Remied for Customer [Customer Name]

The total number of bills receivable remied for each customer.
Totals for Currency

The total bills receivable remiance batch amount in the remiance currency.
Number of Bills Receivable Remied

The total number of bills receivable remied in the remiance batch.
Print Bills Receivable Program and Report

Use the Print Bills Receivable program to print a batch of bills receivable. You can print bills belonging to a bills
receivable batch or a bills receivable remiance batch.
The Print Bills Receivable Report prints details of each bill receivable included in the program run.
Use this report according to your bills receivable transaction processing requirements.

Bill Receivable Template Name
The print template to use to print bills receivable.
Batch Name
The bills receivable batch from which to print bills receivable.
Remiance Batch
The bills receivable remiance batch from which to print bills receivable.
Report Output
This table describes important column headings in the Print Bills Receivable Program and Report.
Drawee Account Number The account number of the customer drawee.

Original Transaction Amount The original amount of the transaction.

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
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
Using Receivables Credit to Cash Manage Credit Management
7 Manage Credit Management
Overview of Credit Management

Credit Management provides a comprehensive system for developing and implementing policies and procedures to
help you manage credit-related data and make intelligent credit decisions about your customers.
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 proles and policies
• Credit reviews
• Credit review management
• Credit management tools
Credit Proles and Policies

Create a credit prole for each of your customers and customer accounts. The credit prole contains key information
for establishing the creditworthiness of each of your customers, including credit classications, credit limits, and credit
review cycles.
You can set up a credit-only prole at the customer, or party, level for enterprises with an extended hierarchy of
businesses. You can also create specic proles for individual customer accounts.
Credit Reviews
A credit review begins when a credit-related event takes place.
There are three events that initiate credit reviews:

• A customer fails a credit authorization request.
• A customer is included in a scheduled run of the Periodic Credit Review process.
• A credit analyst initiates a credit review for a new customer or for an occasional review of an existing customer.
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.
Credit Review Management

Use the Credit Reviews work area to review and manage credit case folders. Credit analysts can search case folders, view
high-level information about their case folders, and take actions such as create a new case folder, reassign a case folder
to another analyst, and close case folders.
445
The credit analyst uses the case folder to:

• Review a customer credit score.
• Where necessary, update the data point values that aect a credit score.
• Provide recommendations for customer credit.
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.
Credit Management Tools

Credit Management provides tools for developing an analysis of customer creditworthiness and making informed credit
decisions.
The Credit Management tools include:

• Scoring models: Design scoring models to calculate a credit score based on credit data specic to a customer or
customer account.
• Data points: Enter and maintain detailed information about customer nancial and accounting history to
develop a picture of customer creditworthiness.
• Case folder templates: Create case folder templates for dierent types of credit reviews, and automatically
assign a specic template to a case folder during the initial credit review and case folder creation process.
Components of a Credit Case Folder

A credit case folder is a record that contains the set of data used to conduct a credit review of a customer or customer
account, or of a customer account with an individual credit request source transaction.
A credit case folder contains the following data and tools:
• Customer or customer account information, including the case folder currency and the current credit limit.
• Credit classication and review type for this case folder.
• If the Review Type is Credit Checking Failure, information about the failure, including the requested amount,
the customer's available credit, and information about the source transaction that initiated the credit
authorization request.
• Credit case folder template assigned to the case folder, used to dene the type of scoring and data points
available.
• Data points needed for the credit analysis.
• If applicable, a scoring model to calculate the credit score.
• Actions and Recommendations for the credit review.
The review types are:

• Ad Hoc Review: initiated by manually creating a credit case folder.
• Credit Checking Failure: initiated by a credit checking failure.
• Periodic Review: initiated by a periodic review of the credit of a customer or customer account.
446
Note: In cases where one customer account calls the credit checking service more than once with dierent
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, identied 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 aributes of the source transaction.
The credit case folder creation process involves these steps:
• The active case folder template is selected for the combination of credit classication and review type. If the
customer or customer account credit prole doesn't have a credit classication dened, 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 aempts 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 dened in the credit prole.
The new credit case folder is assigned an initial status and is displayed rst in the Credit Reviews work area.
How the Credit Limit is Derived in a Party Hierarchy

When a credit check is initiated, the credit checking process ordinarily looks for a credit limit value in the customer
account prole and, if no value is found, in the customer prole. Once a credit limit value is found, credit checking
proceeds to verify the customer's credit for the given credit authorization request.
You can also dene a party-level hierarchy for a customer. If you use a party-level hierarchy, then the credit checking
process uses the credit denitions in the party hierarchy to determine the customer credit limit.
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 prole option.
The default value for this prole 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 prole option
value to the correct hierarchy type as dened in the Manage Hierarchies setup task.
If a party-level hierarchy is dened 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
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)
Vision Canada Vision Mexico

Vision USA Vision Middle East
(Party) (Party)
(Party) (Party)
Credit Limit: Credit Limit:
Credit Limit: 20 Mil Credit Limit: 3 Mil
Not Specified Not Specified
(Effective Credit (Effective Credit
(Effective Credit (Effective Credit
Limit: 15 Mil) Limit: 3 Mil)
Limit: Null) Limit: Null)
Account 4 Account 6 Account 7

Account 1
Credit Limit: Credit Limit: Credit Limit:
Credit Limit: 5 Mil
Not Specified Not Specified Not Specified
Account 2 Account 5 Account 8

Credit Limit: Credit Limit: Credit Limit:
Not Specified Not Specified Not Specified
Account 3
Credit Limit:
Not Specified
The party prole credit limit denes 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
dened credit limits and the children that don't have a credit limit dened.
Vision USA has a credit limit of $20 million available to its three accounts. Account 1 has a specied 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 dened, so eectively these parties can make use of the
undened $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
Overview of Data Points

A data point is a single piece of credit information that pertains to a customer. Examples of data points include the
number or amount of past due invoices; bank account average balance; percentage of invoices paid promptly; and the
customer's credit ratings with external agencies.
The data points assigned to a case folder form the basis for making determinations about a customer's
creditworthiness. A collection of specic data points is also used by a scoring model to calculate the customer's credit
score.
Data Point Categories

Credit Management provides a set of predened data points in several categories.
These categories are:

• Aging: Data related to customer open balances.
• Bank References: Information about customer bank accounts.
• Billing and Payments: Customer transaction and payment history.
• Business Information and Credit: Data related to customer credit history, both within your own enterprise and
with external credit agencies and monitoring services.
• Collateral: Information about customer collateral, as it relates to establishing or requesting credit.
• Financial Data: Data related to the health of a customer business, such as prots, losses, and cash ow.
• Guarantors: Information about third parties willing to guarantee customer credit.
• References: Information about third parties that provide references for the customer.
• Trade References: Information from third parties in the same trade that provide statements of creditworthiness
for the customer.
• Venture Funding: Information about investment funding for the customer.
• Additional: Additional data points available for user-dened categories and values.
Scorable and Non-Scorable Data Points

Use scorable data points to provide numeric nancial data about a customer and to create a scoring model. Use non-
scorable data points for additional reference information.
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 reect the possible credit risk.
For example, the data point that identies 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
• How You Import Third-Party Credit Data for Data Points
Guidelines for Updating Data Points in a Credit Case

Folder
The credit case folder displays in the Data Points section the data points available by default for the credit review. These
default data points are supplied by the credit case folder template.
Data points are grouped by data point category in alphabetic order. Within a category, the required data points are
listed rst, followed by the optional data points.
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 Data Point Values

During a credit review, you can add optional data points to the case folder and remove default data points that were
set as optional in the case folder template. If you are using a scoring model, then any values you enter in optional data
points that are scorable are included in the credit score calculation.
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 specic 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.
Update a Scoring Model

If you are using a scoring model and the credit score was not calculated, use the Scoring Details page to complete the
data point values. In the Credit Score eld, click the Pending calculation hyperlink to navigate to the Scoring Details
page. The Scoring Details page displays the default scoring model assigned to the credit case folder template.
You can enter and import missing values, or refresh system-derived values. You must ensure that you enter values
within the ranges dened for each data point in the scoring model.
If necessary, you can change the default scoring model during your credit review by selecting a dierent 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 buon to calculate the credit score
and remain on the page. Use the Save buons 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
• How You Maintain the Summary Tables for Data Points
Guidelines for Entering Recommendations for Customer

Credit
After reviewing all of the available credit information and calculating the credit score, complete the credit review process
by recommending how to proceed with the credit status of this customer or customer account.
Use the Recommendations section to enter this information. Use the Plus (+) icon to open one or more rows for
entering your recommendations:
• The Type column indicates the actions available to you.
• The Current Value column displays current prole seings for the customer or customer account.
• The New Value column lets you enter and update specic recommendations.
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 aributes passed through the credit checking
service, regardless of whether sucient 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 classication Change the credit classication 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 specic date for the next credit review for the customer or customer account.
451
Type Recommendation

These updates apply to the recommendation types:

• No change: You can't enter any other type.
• Source transaction credit request types: These two types are mutually exclusive.
• Credit hold types: These two types are mutually exclusive.
• Credit prole types: The customer or customer account credit prole is updated with the new values you enter
here.
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.
Credit Case Folder Approvals

After completing your credit review and entering recommendations for a given credit case folder, you can approve the
case folder.
Depending on your business practices, a credit analyst with the authority to approve a case folder can either provide
nal approval, or approve and assign the case folder to another designated approver. Until a credit case folder has the
status Approved or Closed, you and other designated approvers can continue to work on the case folder.
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.
To approve a credit case folder:

1. Navigate to the Credit Reviews work area.
2. Open the credit case folder.
3. In the Data Points section, complete the editing of data points and the entry of data point values according to
the setup of the credit case folder template.
4. If you are using a scoring model, use the Scoring Details page as necessary to complete data point values and
calculate the credit score.
5. In the Recommendations section, complete the rows needed to indicate how to proceed with the credit status
of the customer account for this credit review.
6. From the Actions menu, select Approve.
7. In the Approve window:
◦ Select the Approve case folder radio buon to approve the case folder.
◦ Select the Approve and specify the next approver radio buon 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
If you select the Approve case folder radio buon, 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 buon 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.
How You Run Periodic Credit Reviews

Use the Periodic Credit Review process to perform a credit review of applicable customers and customer accounts.
You create the periodic credit review denition for your customers and customer accounts in the credit prole. The
important values in the credit prole are:
• Credit Review Cycle eld: Denes how often customers with this prole are subject to a periodic credit review:
Quarterly, Semiannually, Annually. In general, customers with a higher degree of credit risk would be subject to
more frequent reviews.
• Next Review Date eld: Contains the date of the next credit review for customers with this prole. This date is
calculated automatically if the Last Review Date and Credit Review Cycle elds contain values.
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 dened.
Note: The process only includes customer and customer accounts that have both Next Review Date and
Credit Review Cycle dened. 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.
Periodic Credit Review Report

Use the Periodic Credit Review Report to review a run of the Periodic Credit Review process.
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.
This table describes the column headings in the report output:
453
Customer The name of the customer.

Customer Account The name of the customer account.

Credit Classication The credit classication for the customer or customer account.

Credit Review Cycle The credit review cycle for the customer or customer account.

Next Review Date The date of the next credit review.

Case Folder Created The credit case folder number.

Credit Analyst Assigned The name of the credit analyst assigned to the case folder.

FAQs for Manage Credit Management

When does a customer exceed the credit limit?
After the credit limit is derived for the applicable customer or customer account, the credit limit amount is compared to
the sum total of all activity belonging to the customer parent entity and any child entities, if applicable.
The available credit for the customer or customer account is calculated as:
Total Defined Credit Limit - Open Credit Authorizations - Open Receivables Balance = Available Credit
If after conversion to the credit currency the sum total is equal to or greater than the dened credit limit, then the
customer has exceeded the credit limit and a credit review is initiated.
How can I review a credit checking failure?

In the Review Type eld, click the value Credit Checking Failure to display the Credit Checking Request Information
window.
The Credit Checking Request Information window provides details of the failed credit check:
• 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
• 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.
How can I use additional data points?

Use the Additional data point category to dene your own data points for use in the calculation of a credit score.
The Additional data point category provides fteen data points with these data entry types: Data Point 1 - Data Point
6: alphanumeric data points; Data Point 7 - Data Point 12: numeric data points; Data Point 13 - Data Point 15: date data
points.
Additional data points follow the same rules for weight, range, and score values as all other data points.
What happens when the summary tables are updated?

After you conrm a run of the Process Receivables Transactions for Customer Account Summaries process to
successfully update and refresh the AR_TRX_BALANCES_SUMMARY and AR_TRX_SUMMARY tables, you can refresh
your case folders.
Open any applicable case folder and select Refresh Data from the Actions menu. If the case folder uses a scoring
model, then the credit score and available credit are recalculated.
What are points earned and weighted points earned?

A point earned is the score assigned to a data point value, determined by the scores assigned to the data point ranges
in the scoring model.
For example, if Data Point A is set up with a score of 5 for the range of values 1 > 50, and a score of 10 for the range of
values 50 > 100, then if the value of Data Point A in the case folder is 32, the point earned is 5.
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.
What happens when I close a credit case folder?

After you complete all recommendations in a case folder, the case folder status is automatically updated from Approved
to Closed. You can also close a case folder using the Close action.
455
A Closed case folder generates a public Credit Case Folder Closure business event. This business event contains the
following information:
• Key aributes of the case folder, including case folder number, status, credit analyst, creation date, and last
update date.
• Key aribute 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 aributes 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
prole for credit limit and credit classication.
What's the dierence between closing, withdrawing and rejecting

a case folder?
You close a case folder if you determine, according to your business practices, that the credit review is no longer
needed.
For example, the customer may no longer need the pending orders or is no longer in business. You can't reopen closed
case folders. If necessary, you must manually create a new case folder.
You can withdraw a case folder that is pending approval with designated approvers.
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
Using Receivables Credit to Cash Manage Cash Management and Banking
8 Manage Cash Management and Banking
Manage Banks, Bank Branches, and Bank Accounts

How Bank, Branch, and Account Components Work Together
Banks, branches, and accounts t together on the premise of the Bank Account model.
The model enables you to dene and keep track of all bank accounts in one place and explicitly grant account access to:
• multiple business units

• functions
• users
This eliminates the redundant duplicate bank account setup in dierent 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:
• Search for existing banks to view and update

• Create a new bank from an existing party
Consider the following:
• 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 dene other branch- related aributes 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 dening an account are:
• General information
• Control of the account
• Security and access to the account
• Business unit assignment
457
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.
Consider the following:

• The Oracle Fusion Account Payables or Receivables accounts are identied by the business unit.
• The Oracle Fusion Payroll accounts are identied by the legal entity.
• The program, Inactivates Banks and Bank Branches enables you to inactivate all banks and bank branches that
have no active internal and external bank accounts.
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:
Decisions to Consider In This Example
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 buon 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
6. Save the spreadsheet as a CSV le.

The following table represents a sample spreadsheet:
A B C D E
BankPartyNumber or Address 1 City State Country

BranchPartyNumber

50170 1 Main St. San Francisco CA US

50172 2 Main St. San Francisco CA US

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
Name Enter a unique name

Object Account

File Type Text File

Upload From Select the appropriate option

Data Type
Accept the default value or leave the data type as Comma Separated if that's the separator
used in the CSV le
Header row included Checked

9. On the Create Import Activity: Map Fields page, complete the following elds, and click Next.
◦ For the BankPartyNumber or the BranchPartyNumber aribute, select OrganizationProle as the
target object, and select PartyNumber as the target aribute.
◦ For every Address aribute, select Address as the target object, and select the corresponding values
(Address1, City, State, Country) as the target aribute.
The following table depicts a sample aribute mapping to upload new addresses:
Column Header Example Value Object Aribute
BankPartyNumber or 50170 OrganizationProle PartyNumber

BranchPartyNumber

Address1 1 Main St. Address Address1
459
Column Header Example Value Object Aribute

City San Francisco Address City

State CA Address State

Country US Address Country

10. On the Create Schedule page, click Next to execute the address upload immediately. You can also dene a
specic 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
Manage Bank Statements

How You Process Electronic Bank Statements
The electronic bank statement process transfers bank statements and imports them into Oracle Fusion Cash
Management.
The following statement le formats are supported:
• BAI2
• SWIFT MT940
• EDIFACT FINSTA
• ISO20022 CAMT052 V1 - camt.052.001.01
• ISO20022 CAMT053 V1 - camt.053.001.01
• ISO20022 CAMT053 V2 - camt.053.001.02
• ISO20022 CAMT053 V3 - camt.053.001.03
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
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 dened 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 dened 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 congurable 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-dened 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
Automatic Bank Statement File Import

Use the payment transmission conguration feature to automate the bank statement le import process. The process
uses the payments transmission feature to connect to bank and download the bank statement le for subsequent
processing and loading into the application.
Perform the following steps to set up automatic bank statement le import:
1. Set up Payment System: Represents the nancial institute or bank in Oracle Fusion Payments. For customers
who access Oracle Fusion Applications through Oracle Public Cloud and other implementations, navigate to the
Manage Payments System page from Setup and Maintenance to create a payment system.
461
2. Set up Transmission Conguration: 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.
◦ Hp(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 hps
connection but doesn't support the exchange of any dynamic tokens.
3. Schedule Process Electronic Bank Statement Request: The process performs the following tasks:
◦ Connects to the bank and retrieves the banks statement le

◦ Processes and loads the bank statement le into the application
Manual Bank Statement File Import through Oracle Web Center

Use the document repository of Oracle Web Center Content Management to manually load and import bank statement
les. The Web Center document repository is also available for customers who access Oracle Fusion Applications
through other implementations. The account, n/cashManagement/import, is created on the Web Center for the
users of Oracle Fusion Cash Management.
Use the document repository of Oracle Web Center Content Management to manually load and import bank statement
les. The Web Center document repository is also available for customers who access Oracle Fusion Applications
through other implementations. The account, n/cashManagement/import, is created on the Web Center for the users
of Oracle Fusion Cash Management.
Example
The following example describes how to manually load and import an electronic bank statement.
1. Obtain a bank statement le: bai2.txt, from the bank.

2. Compress the le into a .zip le called bai2.zip
3. Using the File Import and Export functionality, transfer the .zip le to the Web Center document repository and
place it in the account: n/cashManagement/import.
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
Bank Statement Validation

Prior Day Bank Statements:
1. The Statement ID should be unique in a bank account within a calendar year.
2. Multiple statements are allowed within the date range.
Intraday Bank Statements:
1. The Statement ID should be unique in a bank account within a calendar year.
2. Only one statement is allowed per day.
Intraday Bank Statements: Cumulative
• The application deletes the existing intraday bank statement and imports the cumulative statement.
Intraday Bank Statements: Incremental

• The application checks if there is a manual intraday statement within the same date range. If yes, the
incremental statement isn't imported and the process is completed with a status of :Import Error.
• The application checks if there is an imported intraday statement within the same date range. If found, the
statement lines from the incremental intraday bank statement is appended to the existing intraday bank
statement. If not found, a new intraday statement is created.
Related Topics
• Overview of Parse Rule Sets
• How You Set Up Formats
• Overview of Files for Import and Export
• How You Map Congurable BAI2 Transaction Codes
Overview of Bank Statement Processing and Troubleshooting

The results of the Bank Statement Processing program are displayed in the Bank Statements and Reconciliation work
area if a problem is encountered.
The Processing Errors and Warnings region displays the following statuses:
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
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 dierent retry options available:
Status Fields on the Retry Dialog Action on Program Resubmission
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 specied during program
submission are available in the dialog.
The parameters can then be updated and
program resubmied 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 aempts to load the
le is already fetched, the parameters already fetched data le using the format
associated with fetching the le aren't specied.
shown; rather only the Format parameter
is shown. In case a wrong value for
Format is specied in the earlier run, it
can be corrected here and the program
resubmied 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.
resubmied 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
Issue Solution
appear on the Manage Bank

Statements page.

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 dened 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.
dened 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 dened, but interface. However, the balance description is empty because they a'ren't dened 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 dened 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 dened. 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 dene the transaction code.
dened?

Related Topics
• Overview of Parse Rule Sets
465
• How You Set Up Formats

• How You Set Up a Payment System
• Transmission Congurations
How Bank Statements Import Data is Processed

Use the Create Bank Statements in Spreadsheet template to create and import bank statements for any non-standard
format into Oracle Fusion Cash Management.
3. Click Import Bank Statements.
instructions.
466
Seings That Aect the Import Cash Management Bank Statements

instructions.
• Do not change the order of the columns in the template. Changing the order of the columns will cause the load
process to fail.
• You can hide or skip the columns you do not use, but do not delete them. Deleting columns will cause the load
process to fail.
• Each interface table represents a separate Excel sheet.
• The rst row in each sheet contains column headers that represent the interface table columns. The columns
are in the order that the control le expects them to be in the data le.
• Each column header contains (should this be tool tip) bubble text about the expected data type and, in some
cases, instruction text.
• You must enter data that conforms to what the control le can accept and process for the associated database
column.
• The format for date elds must be entered as MM/DD/YYYY.
• Amount columns must not contain a thousand separators and must use a period (.) as the decimal separator.
• Columns that must be whole numbers have data validation to allow only whole numbers.
• Enter positive amounts and use the Debit orCredit indicator column to distinguish debit and credit amounts.
• Columns have been formaed, where applicable, to match the expected data type to eliminate data entry
errors.
• For columns that require internal ID values, refer to the bubble text for additional guidance about nding these
values.
• For the Balance Code eld, the valid values are from the lookup codes dened in lookup type
CE_INTERNAL_BALANCE_CODES You can access the lookup types from the Manage Cash Management
Lookups page. Enter the Balance Code in the spreadsheet.
The following are the Balance Codes delivered by Cash Management:
Balance Code Meaning
CLAV Closing available

CLBD Closing booked

OPAV Opening available

OPBD Opening booked

467
For the Transaction Type eld, the valid values are from the lookup codes dened 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.
Transaction Type Transaction Type Meaning
ACH Automated clearing house

BKA Bank adjustment

BKF Fee

CHK Check

EFT Electronic funds transfer

INT Interest

LBX Lockbox

MSC Miscellaneous

ZBA Zero balance

For Transaction Code, enter valid codes dened in Manage Bank Statement Transaction Codes task. The following are
examples of transaction codes:
Transaction Code Description
100 Check-Payroll

115 Lockbox Deposit

475 Check paid

698 Miscellaneous Fee

How Import Cash Management Bank Statements is Processed

Once the bank statement information has been prepared, complete these steps in order:
468
Task Action Results
Generate the CSV le. Click the Generate CSV File buon. 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.

FAQs for Manage Bank Statements

How can I use social networking to address any reconciliation discrepancies?
Use the Social link on the Edit Bank Statement page to invite others to a conversation to address the discrepancies.
469
For example, you are a cash manager reviewing the unreconciled items on a bank statement. The conversion rate the
bank is using is dierent than what you expect. You need to conrm the conversion rate with the accounts payable
manager.
From the Edit Bank Statement page:

1. Click Social to open Oracle Social Network. Click the Share buon, or click Join if collaboration has already
been initiated.
2. Create a new related conversation.
3. Invite the accounts payable manager to join the conversation.
The accounts payable manager conrms that the conversion rate used by the bank is dierent than what it
should be.
Based on this information, you can manually reconcile the statement line with the payment. The conversation
serves as a record for the transaction.
Depending on your job role and permissions, you can access social networking features for the following Oracle Fusion
Cash Management activities:
• Bank statement
• External cash transaction
Related Topics
• What does social networking have to do with my job
Manage External Transactions

Overview of External Cash Transactions
External cash transactions are transactions related to cash activity that haven't been recorded in the applications. The
sources of external transactions are:
• Manual Entry
• Import
• Balancing Transactions: Transactions created during reconciliation to record amount dierences between the
statement line and application transaction can occur due to bank fees, conversion rates, or other charges.
Note
For the 1-1 reconciliation matching type of payments and receipts, the reconciliation dierences amount can be
automatically split into the exchange gain or loss and bank charges accounts dened at business unit access
level for the bank account..
For all the other reconciliation matching type scenarios (1-M, M-1, M-M), and transaction sources, such as
payroll, external transactions or journals, the reconciliation dierences account dened at bank account setup
is used.
• Bank Statement: The bank statement transaction creation program creates transactions based on rule
you dene from unreconciled statement lines. This includes items such as bank charges, interest, or other
miscellaneous items.
470
• Bank Account Transfer

• Ad Hoc Payment
• Reversal Reconciliation
For Foreign currency bank accounts, the accounting conversion rate type dened 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.
How External Transactions Import Data is Processed

Use the Cash Management External Transactions import process to create transactions from external applications and
for high volume entries.

3. Click the Cash Management External Transactions Import.
instructions.
Seings That Aect Cash Management External Transactions

The External Transactions Import Template contains then instructions tab and one tab that represent the table where
the data is loaded:
Spreadsheet Tab Description
Instructions and CSV Generation Contains instruction information about preparing and loading data, the format of the template,
submiing 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 oset account.

Recommended best practices for preparing data:

• Manually enter the external transactions directly into this template.
• 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
How Cash Management External Transactions is Processed

Once the external data has been prepared, proceed with the following steps:
1. Click the Generate CSV File buon to generate a ZIP le containing the CSV le.
2. Transfer the generated ZIP le to WebCenter document repository (UCM). Select n$/cashManagement$/
import$ account.
3. Submit the ESS job Load Interface File for Import process.
4. In the Process Details screen, for the Import Process, select Import External Transactions and for Data File,
select the name of the ZIP le that was transferred to the n$/cashManagement$/import$ repository in the
UCM.
5. The data from the ZIP le will be loaded to the interface table CE_EXTERNAL_TRANSACTIONS.
After the ESS Job Load Interface File for Import is completed successfully, the Import External Transactions ESS job will
be automatically invoked.
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 buon.
4. Click the Download buon 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:
Setup Prerequisites Description
Banks, Branches, and Accounts Dene 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
Setup Prerequisites Description
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 dened 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.

Dene Subledger Accounting Rules Congure predened accounting rules for external entry transactions.

To start the autoreconciliation process you must:

• Create a matching rule set and assign it to the bank account you want to use for autoreconciliation.
• Submit the Autoreconciliation process in the Bank Statements and Reconciliation page.
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
submiing 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
Overview of Reconciliation Exceptions

A reconciliation exception occurs when the autoreconciliation program can't nd an application transaction to match
with a particular bank statement line.
473
Exceptions are classied as the following:

• Ambiguous: This exception occurs when either there is more than one application transactions that could
match to the line or the transaction could match to more than one statement line.
• Date: This exception occurs when a system transaction meets all the matching criteria except the date of the
transaction is out of the tolerance range.
• Amount: This exception occurs when a system transaction meets all of the matching criteria except the
amount of the transaction is outside the tolerance range
Automatic Reconciliation Exceptions
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
How You Manually Reconcile a Bank Statement

Manual bank statement reconciliation involves selecting bank statement lines and system transactions to be reconciled
together. During reconciliation if a system transaction hasn't been cleared the reconciliation process clears the
transaction rst, and then reconciles it. Oracle Fusion Cash Management supports manual reconciliation for all
matching scenarios; one to one, one to many, many to one, and many to many. You are allowed to reconcile across
bank statements from the same bank account.
Banks sometimes make mistakes by depositing or withdrawing incorrect amounts to bank accounts. These bank errors
show up on bank statements, along with the corrections and adjustments to those errors. Banks resolve errors using
two methods: reversal and adjustment.
Reconciling Corrections and Adjustments to Bank Errors

Correcting bank errors using the reversal and adjustment method are described in the following example:
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
this example, a reversal entry of a $10.00 receipt is created to oset 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 dierence
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 dierence 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
Cash Positioning and Forecasting

Preparing a Cash Position
Watch: This video tutorial shows you how to prepare and review a cash position. The content of this video is also covered
in text topics.
How You Create a Cash Forecast Using Smart View

Watch: This video tutorial shows you how to create and view a cash forecast for bank accounts. The content of this video is
also covered in text topics.
Overview of Cash Positioning and Forecasting

Watch video
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 eectively reports cash forecast information from dierent 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.
Sources and Scheduled Processes

You have visibility to a variety of sources available in the Essbase, such as invoices, receipts, and payment. Scheduled
processes are designed to streamline the extraction and import of cash ow data from multiple applications such as:
• Oracle Accounts Payable (AP)
475
• Oracle Accounts Receivables (AR)

• Oracle Payroll
• Oracle Cash Management External Cash Transactions
• Cash Management Bank Statements
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 dened in the Specify Cash Positioning and Forecasting Options is used to get historical
data. Submiing 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 dierent applications.
The following results in successful extraction:
◦ It maintains the Essbase cubes, keeping the data in sync with the transaction data from dierent
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 congure 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:
Troubleshooting Conversion Rates

Warning Status:
1. Review the failed transactions reported in the ValidationErrors.txt log le.
2. Enter or correct the conversion rates for the failed transactions.
3. Resubmit the Cash Position Extraction Job process.
4. Review the status for the Cash Position Data Extraction and the Cash Position Data Transfer processes.
5. Review log les for any further warnings or errors.
Bank Statements
• If conversion rate isn't dened for a specic bank statement date or booking date, the application searches
going back up to 1 year to nd the closest conversion rate to use.
• For converting the bank account amount to the ledger amount, the application uses the Accounting Conversion
Rate Type (GL_CUR_EXCHANGE_RATE_TYPE) dened in the bank account setup for the corresponding bank
account.
476
• For converting the bank account amount to the reporting amount, the application uses the default conversion
type dened at Currency Rates Manager.
System Transactions
• If the conversion rate isn't dened for a specic 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 dened
for the transaction.
• For converting the transaction amount to the reporting amount, the application uses the default conversion
type dened in the Currency Rates Manager.
Note: If the rate can't be found, the default conversion type dened in the Currency Rates Manager is used.
Cash Positioning and Forecasting Solution Components

The following is used to create your cash position and forecast:
• Essbase cube: This component stores the actual transaction data sources such as AP payments, AR receipts,
and Payroll payments. This multidimensional database application stores the actual application data; bank
statements and transactions. The following dimensions are delivered by Cash Management: Bank, Legal
Entity, Currency, Currency Type, Transaction Type, Source of the Transaction (Bank Statements, AP Invoices,
AP Overdue Invoices, AP Payments, AR Invoices, AR Overdue Invoices, AR Receipts, Payroll, and External
Transactions), Reconciliation Status of the transaction, Time, and Flow indicator for the bank statement line.
• SMART View and Excel: Is used to view the generated cash positioning and forecasting reports. You can drill
down to view the transaction details by selecting the data cell from SMART View. The drill through is available
from specied individual data cells. Cash Management delivers predened drill through reports, but you have
the ability to create your own.
Note: To run Cash Position reports successfully, install a Smart View plugin later than the
11.1.2.5.500 version on the certied browsers Internet Explorer or Firefox.
• 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 dierent 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.
Setups in Functional Setup Manager

Specify Cash Positioning and Forecasting Options
You dene the extraction duration of the transaction data in Essbase. You can also dene reporting options such as:
• the currency for cash balances.
• the balance code to use from the bank statement in cash balances.
Manage Cash Positioning and Forecasting Transaction Grouping Setup
477
You create transaction grouping (transaction cube dimensions). You can create congurable dimensions to the
transaction cube, in addition to the core dimensions delivered by Cash Management.
• The congurable dimensions are available in Smart View for you to build congurable 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 congurable cube dimensions to meet the dierent 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
ESSBASE and SMART View

The Essbase cube is used for generating the cash position such as the following:
• Bank statements
• Transaction data from external transactions
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 inow and outow
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 certied browsers Internet Explorer or Firefox.
478
Balance Types
Banks can report dierent 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 Cash Position Import Data is Processed

Use the Cash Management Cash Position Data Import process to upload the cash positioning data from external
systems into the Essbase Cash Position Cube.
The data imported into Cash Management are:

• Bank Statement Headers
• Bank Statement Lines
• System Transactions
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:
3. Click Cash Management Cash Position Data Import.
Follow these guidelines when preparing your data in the worksheet
instructions
• You can hide or skip the columns you do not use, but do not delete the
Seings That Aect the Cash Position Data Import Process

The following table displays the name of the tabs and descriptions for the Cash Position Data Import template:
Instructions and CSV Generation Contains instruction information about preparing and loading data, the format of the template,
submiing the Cash Position Data Transfer process, and correcting import errors.
479
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.
How Cash Position Data Import Is Processed

After you nish preparing the data in the spreadsheet:
1. Click the Generate CSV File buon, on Instructions and CSV Generation tab, to generate a ZIP le containing 3
CSV les.
2. Transfer the generated ZIP le to WebCenter document repository (UCM). Select n$/cashManagement$/
import$ account.
3. Submit the ESS job Load Interface File for Import process.
4. In the Process Details screen, for the Import Process, select Cash Position Data Transfer and for Data File,
select the name of the ZIP le that was transferred to the n$/cashManagement$/import$ repository in
the UCM. The data from the ZIP le will be loaded to the interface tables CE_CP_STMT_HEADERS_INT,
CE_CP_STMT_LINES_INT and CE_CP_SYS_TRX_INT.
5. The data from the ZIP le will be loaded to the interface tables CE_CP_STMT_HEADERS_INT,
CE_CP_STMT_LINES_INT and CE_CP_SYS_TRX_INT.
After the ESS Job Load Interface File for Import is completed successfully, the Cash Position Data Transfer ESS job will
be automatically invoked. This process imports the data from the interface tables into the Cash Position Transaction
Cube.
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 buon.
5. Click the Download buon 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
2. The worksheet is -populated with rows that failed import.

3. Review and correct the errors in the spreadsheet.
4. Once the errors have been corrected, click the Upload and Import buon.
5. Click the Download buon to see if there are any rows returned. If the spreadsheet is empty, then all rows have
been successfully imported.
Considerations for Cash Forecasting

Prior to cash forecasting, cash positioning is usually performed on a daily basis by every cash management or treasury
department. The goal of the cash position is to estimate with an acceptable degree of condence the projected closing
bank account balances. In doing so, cash forecasting decisions such as investing and borrowing, can be made in a
timely manner.
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 outows.
• 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
Overview of the Cash Management Dashboard

Oracle Fusion Cash Management provides a dashboard for you to easily review and drill down to activity in the
application. The following is an overview of the ve available infolets on the dashboard:
1. Cash Balance: Displays the overall cash balance of the company across all its bank accounts.
2. Unreconciled: Compares the total month-to-date unreconciled statement line amount against the system
transaction amount.
3. At Risk: Presents the overall decit amount for the bank accounts with balances less than their target balances,
and the number of bank accounts less than the target. You can click the Expanded View to view the balance
and decit for each bank account.
4. 5 Day Forecast: Displays a bar graph representing the forecast of the overall cash balances for the next 5 days.
5. Missing Statements: Indicates the number of bank accounts with missing bank statements.
481
How Ad Hoc Payments Are Made

The Manage Ad Hoc Payments page is used to transfer ad hoc funds from an internal bank account to an external
payee bank account. Ad hoc payments may require an approval process prior to processing the payment. Processing
the payment goes through formaing validation prior to transmission.
The following table lists the elements for making an ad hoc payment and the possible statues that may result with
actions to take to correct issues.
Field Name Required Description
Payment Number Yes, the payment reference is generated The unique payment reference number.
by the application.

Payment Number Yes The bank account initiating the payment.

Payee Yes Name of the payee.

Payee Account Yes The payee bank account receiving the

payment.

Payment Date Yes Date of payment, application date

defaults.

Amount Yes Amount to pay.

Currency Yes Payment currency.

Status Yes, if Approvals are enabled.

Status of the payment. Valid values are:
• Pending Approval
• Approved
• Rejected
• Validated
• Invalid
• Selement in Process
• Failed
• Completed
• Voided
The Payment Status can be either nonactionable or actionable. The following table lists the possible statuses:
482
Nonactionable Status Description
Formaed The payment has been formaed but transmission isn't needed.

Transmied The payment has been formaed and transmied.

Terminated The payment has been terminated by the user.

Actionable Status Description
Pending action to address document Correction or missing data needed.

validation errors.

Pending action to address payment Correction or missing data needed.

validation errors

Failed validation and pending action Correction or missing data needed.

Formaed and ready for transmission Passed validation and ready to be transmied.

Failed formaing and pending action Correction or missing data needed.

Transmission failed Correction or missing data needed.

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
How You Transfer Funds Between Bank Accounts

Use the Manage Bank Account Transfers page to manage fund transfers between two internal bank accounts. The
following list provides the elements for:
• Payment status
• Bank account information
• Payment status details
Manage Bank Account Transfers Table:
483
Transfer Number Unique bank account transfer reference that's system generated.

From Account The bank account that initiates the transfer.

To Account The bank account receiving the transfer.

Transfer Date Date of transfer.

Amount Amount to transfer.

Currency Currency of the amount transferred.

Status
Status of the bank account transfer. Valid values are:
• Pending Approval
• Approved
• Rejected
• Validated
• Invalid
• Selement 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.
The following tables list the possible statuses:
Nonactionable Status Description
Formaed The payment has been formaed but transmission isn't needed.

Transmied The payment has been formaed and transmied.

Terminated The payment has been terminated by the user.

484
Actionable Status Description
Pending action to address document Correction or missing data needed.

validation errors

Pending action to address payment Correction or missing data needed.

validation errors

Failed validation and pending action Correction or missing data needed.

Formaed and ready for transmission Passed validation and ready to be transmied.

Failed formaing and pending action Correction or missing data needed.

Transmission failed Correction or missing data needed.

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
• Overview of Approval Management
FAQs for Cash Positioning and Forecasting

Why can't I see the bank accounts for some transactions in the Cash Balances work
area?
Cash balances, cash position and cash forecast reports retrieve data from the cash position cube. You must create the
cash position cube by running the Cash Position Data Extraction program from the Scheduled Processes work area.
You can see the bank accounts that aect your cash position after you run the program.
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 ocial 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 submied the Cash Position Data Extraction process, you can change the reporting currency in the
Specify Cash Positioning and Forecasting Options page.
485
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 dierent, 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.
When does the accounting for ad hoc payments take place?

Accounting for ad hoc payments occurs when the Create Accounting process is submied from Cash Management to
Oracle Fusion Subledger Accounting.
External transactions created for ad hoc payments have journal entries created by the process. Only one external
transaction is created for the From Bank Account.
Any gain or loss calculation due to dierent currencies is handled by Subledger Accounting.
Related Topics
• How You Submit Accounting Process
• Intercompany Transactions Types
When does the accounting for bank transfers take place?

Accounting for bank transfers occurs when the Create Accounting process is submied from Cash Management to
Oracle Fusion Subledger Accounting.
The bank account transfer creates two external transactions.
1. An outow (payables) external transaction is created for the From Bank Account.
2. An inow (receivables) external transaction is created for the To Bank Account.
Bank account transfers can occur between an intercompany and intracompany.
External transactions created for bank account transfers have journal entries created by the Create Accounting process.
Any gain or loss calculation due to dierent currencies is handled by Oracle Fusion Subledger Accounting.
Related Topics
• How You Submit Accounting Process
486
• Intercompany Transactions Types
Reports for Manage Cash Management and Banking

Oracle Fusion Cash Management Predened Reports
Oracle Fusion Cash Management provides predened reports that are used in the following areas:
• Bank Statements
• Cash Transit
• Reconciling to the General Ledger
Scheduled Processes Work Area
You can schedule and run reports from the Scheduled Processes work area in the Tools section of the Navigator.
Reports and Analytics Work Area
In some cases, reports are also:

• Accessed from the Reports and Analytics work area in the Tools section of the Navigator or from other work
areas.
• Opened using links that launch the Oracle Business Intelligence Catalog.
The following tables list the predened reports by type:
Bank Statement Reports:
Report Name Description Parameters (*Required)
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

Bank Statement Analysis Report Displays bank statements used to analyze NA

balances and transaction details.

Cash Transit Report
Cash in Transit Report Lists all transactions for a specic bank • *Bank Account
account, that have been remied 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
Cash to General Ledger Report
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 predened reports, navigate to the Scheduled Processes work area and follow these steps:

2. Search the Process Name.
3. Enter the parameters.
5. Click Submit.
Related Topics
• Reports and Analytics Work Area and Panel Tab
• How You Create and Edit Reports
• Set Up the Reports and Analytics Panel Tab
• Overview of Analytics and Reports
488
Cash Management Bank Statement Report

This topic includes details about the Cash Management Bank Statement Report.
Overview
The Cash Management Bank Statement Report displays bank account balances and transaction information for specic
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 specic bank account.
Report Parameters
The following table describes required process parameters:
Name Description
Bank Account The specic 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

The following table lists frequently asked questions about the Cash Management Bank Statement Report.
FAQ Answers
How do I nd this report? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.

Who uses this report? • Cash Manager

• Financial Manager
When do I use this report? Use this report to review the bank statement of a specic 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.


Cash in Transit Report

This topic includes details about the Cash in Transit Report.
Overview
The Cash in Transit Report lists, for a specic bank account, all transactions that have been remied to the bank but
haven't been cleared. The Cash in Transit report excludes the following:
• All voided transactions

• All reversed transactions with a reversal date on or prior to the As of Date
490
The following gure is an example of the cash in transit report:
Key Insights
The Cash in Transit Report lists the transactions that are created but haven't been cleared as of a specic date.
Report Parameters
Name Description

Transaction Source The origin of the transaction, such as payables or receivables.

As of Date The date when the transaction status is checked.

491

The following table lists frequently asked questions about the Cash in Transit Report.
FAQ Answers
How do I nd this report? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.

Who uses this report? • Cash Manager

When do I use this report? Use this report to review the transactions of a specic bank account that have been remied
but haven't been cleared.

What can I do with this report? Identify transactions that haven't been cleared as of a specic date.

What type of report is this? Oracle Business Intelligence

492
Cash to General Ledger Reconciliation Report

This topic provides information about the Cash to General Ledger Reconciliation Report.
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 specied 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
493
Name Description

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.


The following table lists frequently asked questions about the Cash to General Ledger Reconciliation Report.
FAQ Answers
How do I nd these reports? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.

Who uses these reports? • Cash Manager

When do I use these reports?

Use this report to:
• 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.

What type of reports are these? Oracle Business Intelligence Publisher

Cash Management Subject Areas, Folders, and Aributes

To create real-time analyses for Cash Management, you must be familiar with subject areas, folders, and aributes.
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
The following are the four cash management-specic subject areas:
1. Cash Management - Bank Statement Balances Real Time

2. Cash Management - Bank Statement Line Charges Real Time
3. Cash Management - Bank Statements Real Time
4. Cash Management - External Cash Transactions Real Time
Folders
Each subject area has one fact folder and a number of dimension folders. Fact folders contain measurable aributes,
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 aribute 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 dierent level of granularity. For example, Bank Statement Balance Detail
has various aributes, and Bank Statement Detail has subfolders and aributes in the subfolders.
Aributes
Each dimension folder contains aributes or columns. For example, the folder Bank Statement Balance Detail contains
the following aributes:
• Balance Code
• Balance Code Description
• Credit Debit Indicator
• Float Days
• Funds Date
Related Topics
Bank Account Validation

Bank Account Validation by Country: Albania to Guatemala
This outlines the country specic bank account validation rules performed in Oracle Fusion Cash Management.
The following countries have country specic validations:
• Albania
• Algeria
• Andorra
• Argentina
495
• 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, dierent 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
4. Check Digit
5. IBAN
Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertaining
to the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the site
or user level. The prole is predened with a default value of No at the site level. If the prole 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 aected by this prole.
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
• Optional, if entered, the following rules apply.

IBAN
• The modulus-97 rule is used to calculate the validity of the IBAN.
• 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 leers.
• The third and fourth characters are numbers.
Algeria
Validation Rules
497
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Andorra
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
• Length should be 24 characters. Spaces are removed from the left and right. Spaces in
the middle aren't removed.
Argentina
Validation Rules
498
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
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

IBAN
499
Austria
Validation Rules
Field Rule
• Optional
Bank Code
• Length should be of 5 numeric characters.
• Optional
Branch Number
• 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 dened in a country that requires IBAN for payment
processing.
• The modulus-97 rule is used to calculate the validity of the IBAN
Azerbaijan
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
500
Field Rule
Bahrain
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Belarus
Validation Rules
501
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Belgium
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• It should be in the format 999-9999999-99.
• A check algorithm is applied on the Account Number.
• Optional
Check Digit
• Mandatory
IBAN
processing.
502
Field Rule
Check Algorithm for Account Number

1. The entered check digit CD1, is the last two digits of the Account Number
2. The calculated check digit CD2, is derived by concatenating the rst two sections of the Account Number and
calculating the remainder on dividing this by 97. If the remainder is equal to 0, then the calculated check digit's
taken to be 97.
3. If the entered check digit (CD1) and calculated check digit (CD2) are equal, then the Account Number is valid,
else the check has failed.
4. Additionally, if the entered check digit (that's, the last section) is '00', then the Account Number is invalid
because the calculated check digit can never be 00 as per the 3rd point.
Example using account number 123-4567890-78
◦ The entered check digit (CD1) is '78'. The concatenation of the rst two sections gives '1234567890'
◦ Divide the result by '97'. 1234567890 / 97 = 12727504
◦ Derive the remainder. 1234567890 - (12727504 * 97) = 2 Therefore CD2 = 2
◦ Here CD1 <> CD2, therefore the Account Number isn't valid.
In this case, a valid Account Number would be '123456789-02'.
Bosnia and Herzegovina

Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
503
Brazil
Validation 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 prexing it with as
many leading zeroes as is necessary.
• Mandatory
Branch Number
• 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
• This eld is labeled as Company Code.

Secondary Account Reference

IBAN
British Virgin Islands

Validation Rules
504
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
• Length can’t be more than 24 characters. Spaces are removed from the left and right.
Bulgaria
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
505
Canada
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• This eld is labeled as Routing Transit Number.
• Mandatory
Account Number
• Optional
Check Digit

IBAN
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
Field Rule
• A check digit's applied on the Tax Payer ID.

IBAN
Check Algorithm for Tax Payer ID
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
Digit Factor
14th 7

15th 3

1. These 15 products are added and the sum is divided by 11.

2. If the remainder is 1 or 0, then the Check Digit should be 1 or 0 respectively.
3. If the remainder isn't 1 or 0, then the remainder is subtracted by 11 and that should be the Check Digit.
Costa Rica
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Croatia
Validation Rules
508
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Cyprus
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
509
Field Rule
Czech Republic
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Denmark
Validation Rules
510
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Length should be a maximum of 10 numeric characters

Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Dominican Republic
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
511
Egypt
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
El Salvador
.
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
512
Estonia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Faroe Islands
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
513
Field Rule
Finland
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• If entered, it should be 6 numeric characters.
• Mandatory
Account Number
• Optional
Check Digit
• If entered, it should be 1 numeric digit.
• Mandatory
IBAN
processing.
If 1st digit of Account Number is: Check Value Method
1 1

2 1

3 1

4 2

5 2

514
If 1st digit of Account Number is: Check Value Method
6 1

7 2

8 1

9 1

Method 1
The check is formed in the following two parts:

• The rst part of the check is formed from the rst 6 digits of the Account Number. To illustrate, if the account
number is 123456789, then the rst part of check would be created as 123456.
• The second part of check is formed as an eight digit value, comprising the 8th to 15th digits of the Account
Number. If the length is less than 8, then it's converted to an 8 digit number by prexing it with as many
leading zeroes as is necessary. Using the same example, the second part of check would be created as
00000089. check is then formed by concatenating the two parts. So, in our example the check is formed as
12345600000089.
Method 2
The check is formed in the following three parts:

• The rst part of the check is formed from the rst 6 digits of the Account Number. To illustrate, if the account
number is 123456789, then the rst part of check would be created as 123456.
• The second part of check is formed as the 8th digit of the Account Number. Using the same example, the
second part of check would be created as 8.
• The third part of check is formed as a seven digit value, comprising the 9th to 15th digits of the Account
Number. If the length is less than 7, then it's converted to a 7 digit number by prexing it with as many leading
zeroes as is necessary. Using the same example, the second part of check would be created as 0000009.
The check is then formed by concatenating the three parts. So, in our example the check is formed as
12345680000009.
A computed sum is then calculated based on the value of the check. Dierent calculations are performed depending on
the rst two digits of the formed check value.
If the rst two digits of the check are '88', then:

• The Finnish government provides the following factor table. The 8th to 13th digits of the check number are
multiplied by the associated factor. The computed sum is then calculated by summing the totals.
Digit Factor
8th 1

9th 3
515
Digit Factor

10th 7

11th 1

12th 3

13th 7

Example using check number 88345600000089: Multiply the given digits with the given factor.
Digit Value Factor Result
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
So the computed sum for this example is 56.
The test fails unless either of the following applies:
• 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 :
• Multiply the digit by 2.
516
• Divide the result by 10.

• From the result add the integer to the remainder.
Example using account number 123456800000089:
Digit Value Multiply (a) Divide (b) Integer Remainder Result
1st 1 2 0.2 0 2 2

2nd 2 N/A N/A N/A N/A 2

3rd 3 6 0.6 0 6 6

4th 4 N/A N/A N/A N/A 4

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

N/A N/A N/A N/A N/A 28

Total
The computed sum is then converted using the following process, before being used to see if the Account Number is
valid:
1. Computed sum is added to 9.

2. The result is divided by 10.
3. The integer result is multiplied by 10.
4. The result is subtracted by the original computed sum.
517
So the computed sum '282 is converted to '2' as:
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
Field Rule
• Mandatory
Bank Code
• Mandatory
Branch Number
• 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.
• This eld is labeled as Deposit Type.

Account Type
• Mandatory
IBAN
processing.
Check Algorithm for Check Digit
518
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

Example using account number A1234567890:
The leer 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 sux 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, suxing 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
French Guiana
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Georgia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
520
Field Rule
Germany
Validation Rules
Field Rule
• Optional
Bank Code
• If entered, then the length should be 8 numeric characters.
• Optional
Branch Number
• If the Bank Code and Branch Number are entered, then both values must match.
• Mandatory
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
last digit of the Account Number.
• Mandatory
IBAN
processing.
Gibraltar
Validation Rules
521
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Greece
Validation Rules
Field Rule
• Optional
Bank Code
• If entered, then the length should be of 3 numeric characters.
• Optional
Branch Number
• 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
processing.
522
Field Rule

Greenland
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Guadeloupe
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
523
Field Rule
processing.
• Length should be 34 characters. Leading and trailing spaces are ignored. There should
be no spaces in the middle. .
Guatemala
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Bank Account Validation by Country: Hungary to Norway

This outlines the country-specic bank account validation rules performed in Oracle Fusion Cash Management.
The following countries have country-specic validations:
• Hungary
• Iceland
• India
• Ireland
• Israel
524
• Iran
• Iraq
• Italy
• Ivory Coast
• Japan
• Jordan
• Kazakhstan
• Kosovo
• Kuwait
• Latvia
• Lebanon
• Liechtenstein
• Lithuania
• Luxembourg
• Malta
• Martinique
• Mauritania
• Mauritius
• Mayoe
• Mexico
• Moldova
• Monaco
• Montenegro
• Morocco
• Netherlands
• New Zealand
• Norway
1. Bank Code
2. Branch Number
3. Account Number
4. Check Digit
5. IBAN
525
Hungary
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Iceland
Validation Rules
Field Rule
• Optional
Bank Code
• If the length is less than 4, then it is converted to a 4 digit number by prexing it with as
• Optional
Branch Number
• Mandatory
Account Number
526
Field Rule
• If the length is less than 18, then it is converted to an 18 digit number by prexing it with
as many leading zeroes as is necessary.
• 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
processing.
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
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
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• This eld is labeled as the IFSC Code
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Ireland
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Length should be 8 numeric characters.
• Optional
Check Digit
• Mandatory
IBAN
528
Field Rule
processing.
Israel
Validation Rules
Field Rule
• Mandatory
Bank Code
• If entered, the length should be a maximum 2 numeric characters
• Mandatory
Branch Number
• Mandatory
Account Number
• Spaces aren't allowed.
• Optional
Check Digit

IBAN
Iran
Validation Rules
529
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Iraq
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Italy
Validation Rules
530
Field Rule
• Mandatory
Bank Code
• Mandatory
Branch Number
• 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 prexing 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
processing.
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:
Even Position Values Odd Position Values
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

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

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
Calculation Calculation Calculation
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
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Japan
Validation Rules
Field Rule
• Mandatory
Bank Code
• Length should be 4 numeric characters
• Optional
Alternate Bank Name
• Mandatory
Branch Number
• Optional
Alternate Branch Name
• Mandatory
Account Number
Account Type • Mandatory

• This eld is labeled as Deposit Type.
• Optional
Check Digit

IBAN
534
Field Rule
Jordan
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Kazakhstan
Validation Rules
535
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Kosovo
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Kuwait
Validation Rules
536
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Latvia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
537
Lebanon
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Liechtenstein
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
538
Field Rule
Lithuania
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Luxembourg
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
539
Field Rule
• Optional
Check Digit
• If entered, then the length should be 2 numeric characters
• Mandatory
IBAN
processing.
Malta
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Martinique
Validation Rules
540
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Mauritania
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
541
Mauritius
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Mayoe
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
542
Field Rule
Mexico
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Optional
IBAN
Secondary Account Reference • Optional

• If entered:

◦ Should be of 18 digits
◦ Should be numeric
Moldova
Validation Rules
543
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Monaco
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
544
Montenegro
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Morocco
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
545
Field Rule
Netherlands
Validation 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.
◦ length is 7 digits or less, or
◦ prexed with 000, or
◦ prexed 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
processing.
Check Algorithm for Non-Post or Giro Account Number

1. If the length is less than 10, then it is converted to a 10 digit number by prexing it with as many leading zeroes
as is necessary.
2. The Netherlands government provides the following factor table for each of the 10 digits:
Digit Factor
1st 10
546
Digit Factor

2nd 9

3rd 8

4th 7

5th 6

6th 5

7th 4

8th 3

9th 2

10th 1

These are multiplied and the sum of the products is calculated 4.
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
Field Rule
• Mandatory
Bank Code
• Mandatory
Branch Number
• This eld is labeled Bank State Branch.
• Mandatory
Account Number
547
Field Rule
• Account Sux should be between 2 to 4 numeric characters.
• Optional
Check Digit
• This eld is labeled Reference.

Description

IBAN
Norway
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• 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
processing.
548
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.
2. The Norwegian government provides the following factor table:
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.
3. Example using account number 02056439653:
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
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

N/A N/A 163

Total
4. The computed sum is then added to the check digit. In the example, 163 + 3 = 166.
5. Divide the result by 11. 166 / 11 = 15 6.
6. Derive the remainder. 166 - (11 * 15) = 1.
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.
Bank Account Validation by Country: Pakistan to the United States

This outlines the country specic bank account validation rules performed in Oracle Fusion Cash Management.
The following countries have country specic validations:
• Pakistan
• Palestine
• Poland
• Portugal
550
• 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
1. Bank Code
2. Branch Number
3. Account Number
4. Check Digit
5. IBAN
551
Pakistan
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Spaces in the middle aren't removed..
Palestine
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
552
Poland
Validation 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
processing.
Portugal
Validation Rules
Field Rule
• Mandatory
Bank Code
• Mandatory
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
553
Field Rule
• If entered, a check algorithm is applied on the Check Digit.
• Mandatory
IBAN
processing.

• A check digit's formed (CD1) from the Bank Code, Branch Number, and Account Number by concatenating the
three numbers.
• For example, using Bank Code 1234, Branch Number 5678, and Account Number 12345678901. Then CD1 is set
as 1234567812345678901.
• The Portuguese government provides the following factor table:
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
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.
Example using the value for CD1:
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

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

N/A N/A 3794

Total
• Divide the result by 97. 3794 / 97 = 39

• Derive the remainder. 3794 - (39 * 97) = 11
• CD1 is then derived by subtracting the remainder from 97. 97 - 11 = 86. So for this example CD1 = 86
• If the calculated value for CD1 isn't the same as the user entered check digit, then the check digit fails the
validation. In the given example, unless the user entered check digit's 86, the validation will fail.
Qatar
Validation Rules
556
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Reunion
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
557
Romania
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Saint Barthelemy
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
558
Field Rule
Saint Lucia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
San Marino
Validation Rules
559
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
This bank account is dened in a country that requires IBAN for payment processing.
Saint Martin (French Section)

Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
560
Saint Pierre and Miquelon

Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Saudi Arabia
Validation Rules
Field Rule
• Optional
Bank Code
• If entered, then the length should be a maximum of 4 characters
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Optional, if entered the following rules apply.

IBAN
561
Field Rule
Senegal
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Serbia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory.
Account Number
• Optional
Check Digit

IBAN
562
Field Rule

Serbia and Montenegro

Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Seychelles
Validation Rules
563
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
Singapore
Validation Rules
Field Rule
• Mandatory
Bank Code
• Mandatory
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Optional, if entered, the rules following apply.

IBAN
Slovakia
Validation Rules
564
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Slovenia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
565
Field Rule
Spain
Validation Rules
Field Rule
• Mandatory
Bank Code
• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing
it with as many leading zeroes as is necessary.
• Mandatory
Branch Number
• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing
it with as many leading zeroes as is necessary.
• Mandatory
Account Number
• 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
processing.
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
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.
Example using Bank Code '1234':
Multiply each digit with the given factor.
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
The four digits of the Branch Number are multiplied by the associated factor. The computed sum is then calculated by
summing the totals.
Example using Branch Number '5678':
1st 5 9 45

2nd 6 7 42

3rd 7 3 21

4th 8 6 48

N/A N/A 156

Total
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.
4. Divide the result by 11.
231 / 11 = 21
5. Derive the remainder
231 - (11 * 21) = 0.
6.CD1 is then derived by subtracting the remainder from 11. If dierence is 11, then CD1 is 0 and if dierence 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
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.
Example using account number '1234567890':
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

10th 0 6 0

N/A N/A 280

Total
2. Divide the result by 11
280 / 11 = 25
3. Derive the remainder.
280 - (11 * 25) = 5
4. CD2 is then derived by subtracting the remainder from 11. 11 - 5 = 6. So for this example CD2 = 6.
Check Digit Validity Test
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
Field Rule
• Optional
Bank Code
• If entered, then the length should be between 4 to 5 numeric characters.
• Optional
Branch Number
570
Field Rule
• Mandatory
Account Number
• Optional
Check Digit
• Length should be a single numeric character.
• Mandatory
IBAN
processing.
Switzerland
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Optional
Account Type
• Mandatory
IBAN
processing.
571
The Former Yugoslav Republic of Macedonia

Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit
• Mandatory
IBAN
processing.
Tunisia
Validation Rules
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory.
Account Number
• Optional
Check Digit

IBAN
572
Field Rule
Turkey
Validation 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.
processing.
Ukraine
Validation Rules
573
Field Rule
• Optional
Bank Code
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
United Arab Emirates

Validation Rules
Field Rule
• Optional
Bank Code
• If entered, the length should be a maximum of 4 characters.
• Optional
Branch Number
• Mandatory
Account Number
• Optional
Check Digit

IBAN
United Kingdom
Validation Rules
574
Field Rule
• Optional
Bank Code
• Mandatory
Branch Number
• it's unique within the country.
• 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.
processing.
United States
Validation Rules
Field Rule
• Optional.
Bank Code
• This eld is labeled as Routing Transit Number.

Branch Number
• Note that on padding the number to 9 digits, the rst 8 digits can't be all zeroes.
575
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

IBAN
Check Algorithm for Routing Transit Number

1. The ninth digit of the Number eld is used to represent the Check Digit.
2. A calculated Check Digit's computed from the remaining 8 digits using Modulus 10 algorithm.
3. Multiply each digit in the Routing Transit Number by a weighting factor. The weighting factors for each digit
areas given in the following table:
Digit 1st 2nd 3rd 4th 5th 6th 7th 8th
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
So the Check Digit = 1 (110 minus 109).
In this example, the Routing Transit Number 076401251 passes validation.
576
Using Receivables Credit to Cash Manage Advanced Collections
9 Manage Advanced Collections
Manage Customer Data

It is important for you to keep your customer data up to date, so that you can perform your collections activities
eciently, and stay updated with all the current and historical data of your customer.
Change Customer Information

Let's discuss from where you can change the customer information and what gets impacted if you do so.
To change a customer information, on Collections Dashboard go to Delinquent Customer tab and select the required
customer.
What You Can Change
Here's all the information you can change:
Tab Information to Change
Prole Change the information related to customer prole 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
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 dene the type of activity you want to do. You can set the priority of the activity according to requirement and can
also upload any aachment 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.
After a note is created, you can always go back and edit the note to update any information.
Process Collections Payments

Overview of Processing Payments
As a collector, you can use Advanced Collections to easily record and process customer payments. You can process
these payments with credit cards or bank electronic funds transfers.
Here's what you can do to process payments:
• Process payments in a foreign currency.

• Pay both delinquent and current open receivables.
• Make partial payments.
• Validate payments in the real time.
• Make secure credit payments by conguring the level of security in Oracle Fusion Payment setups.
• Add bank account and credit card details.
Things to Keep in Mind
• Make payments for one transaction at a time.

• Use only one payment type at a time.
• Don't pay more than the amount due for a transaction.
• Don't enter negative numbers or zero for the payment amount.
578
Make Credit Card Payments

You can use the credit card to make payment for a transaction. You can either use an existing credit card information or
create a new credit card details to make the payment.
Pay Using Existing Credit Card

Here are the steps to make payment using existing credit card details:
1. Search for the customer account to retrieve the outstanding transactions.
2. Select the transaction to pay.
3. The total amount defaults into the payment amount eld, but if the customer wants to make partial payment,
you can change enter the partial amount for the payment.
4. Select the payment method as credit card payment.
5. In the payment details section, enter or select these details:
Field Action
Payment Amount The total amount is auto-displayed as the payment amount; however, you can change the
amount to make partial payment.

Payment Method Select payment method as credit card.

Site Select the appropriate bill-to site.

Credit Card Select the existing credit card and verify the number, name and expiration date of the card.

Statement Billing Address Verify the billing address information.

Security Code Security code is mentioned on the back of your credit card. Verify the with the existing
details.

Purchase Order Number If required, enter your purchase order number.

Purchase Order Line Number If required, enter your purchase order line number.

Voice Authorization Date If required, enter the voice authorization date.

Voice Authorization Code If required, enter the voice authorization code.

Additional Information Enter any other required information as additional information.

6. After all the required details are entered, click submit to process the payment using existing credit card.
579
Pay Using New Credit Card

Here are the steps to make payment using a new credit card:
1. Search on the customer account to retrieve the outstanding transactions.

4. Select the payment method as credit card payment.
Field Action

Payment Method Select payment method as credit card.

Create Credit Card hyper link Click the create credit card hyper link to create the new credit card details.

Number Enter the new credit card number.

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.

Purpose If required, enter the purpose of the new credit card.

Description If required, enter the description.

From Date By default, the current date of creation and activation of new credit card details is mentioned
as from date.

To Date If required, you can enter a specic end date.

Statement Billing Address Select an address if available.

580
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 exeld has been congured.

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.
Create Billing Address

Click the create billing address hyperlink and enter the following details to create billing address details for the newly
added credit card.
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.

Address Line 2 Enter a second billing address if applicable.

Address Line 3 Enter a third billing address if applicable.

Site Name Enter a site name if applicable.

City Enter the city of the billing address.

State Enter the state of the billing address.

Postal Code Enter the seven-digit numeric code for the billing address.

Sales Tax Geocode Enter a tax code if applicable.

Mail Stop Enter a mail stop if applicable.

581
Make Electronic Fund Transfer Payments

You can use electronic fund transfer method to make payment for a transaction. You can either use an existing bank
information or create a new bank details to make the payment.
Pay Using Existing Bank Account Details

Here are the steps to make payment using existing bank account details:
you can change and enter the partial amount for the payment.
4. Select the payment method as Electronic Fund Transfer payment.
Field Action

Payment Method Select payment method as electronic funds transfer.


Bank Account More than one bank account can appear in the list. Select the correct account and verify all
the information with the customer.

Additional Information Enter any other required information as additional information.

6. After all the required details are entered, click submit.
Pay Using New Bank Account Details

Here are the steps to make payment using a new bank account details:
1. Search on the customer account to retrieve the outstanding transactions.
4. Select the payment method as Electronic Funds Transfer.
Field Action
582
Field Action
Payment Method Select payment method as electronic funds transfer.


Create Bank Account hyper link Click the create bank account hyper link.

Country Enter the country where the bank is located.

Account Number Enter the account number.

Bank Name Enter the name of the bank.

Branch Enter the name of the bank branch.

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.

To Date Enter a date if this bank account has an expiration date.

IBAN Enter the International Bank Account Number if applicable.

BIC Enter the Bank Identier Code.

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
◦ Account Type
◦ Description
7. In the Account Owner section, enter the account owner name and date from which the bank account details is
created.
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.
Process Collections Disputes

Create a Dispute
Watch video
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 dierent dispute.
Here are the steps to create a dispute in Collections:
1. Click the collections icon from the landing page.

2. Search for the required customer account. Click the customer icon.
3. Click the transaction tab to display the delinquent or past due transactions of this customer.
4. Select the transaction to be disputed.
Note: In the details section, click details, activity and lines tabs one by one to review the
details of transaction.
5. Click the Dispute buon.

6. In the manage disputes selected transaction section, select the dispute section and dispute reason from the
drop-down list.
7. In the dispute detail section, enter the dispute quantity and amount.
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 aachments and enter customer comments.
9. After all the required details are entered, click submit.
A conrmation message with the dispute number is displayed to conrm the submission.
A designated user then reviews the submied dispute request. If the dispute is approved, the appropriate credit memo
is created automatically.
584
Create an Adjustment Request

The approval of an adjustment is based on the approval limit given to the submier. Usually an amount range is set
up for the user by currency, for example a new user may have adjustment amounts that range from -$10 to -$50 in
US dollars. If the adjustment is within the submier's limit, it's automatically approved. If the adjustment exceeds the
limit, the adjustment goes through an approval process and is approved or rejected by someone with the appropriate
approval limit. Here are the steps to create an adjustment request:.
In this example, note the approval limits of an adjustment: The approval of an adjustment is based on the approval
limit given to the submier. Usually an amount range is set up for the user by currency, for example a new user may
have adjustment amounts that range from -$10 to -$50 in US dollars. If the adjustment is within the submiers limit, it's
automatically approved. If the adjustment exceeds the limit, the adjustment goes through an approval process and is
approved or rejected by someone with the appropriate approval limit.
1. Click the Collections icon from the landing page.
2. Search for the customer account. Click Customer icon.
3. Click the Transaction tab to display the delinquent or past due transaction for this customer account.
4. Select the transaction to be adjusted. Note that to review the details of transaction you can go to the Details
section and review the Details, Activity and Lines tabs one by one.
5. Click Adjust buon.
6. In the Adjustments section, click create icon.
7. Select the Receivables Activity, Adjustment Type, Adjustment Reason and enter the Adjustment Amount.
8. Select the Adjustment Date, Accounting Date and Installment Number.
9. Once all required details are entered, click Submit buon. A conrmation message is displayed.
FAQs for Process Collections Disputes

How does the dispute apply to my customer's outstanding balance?
To apply the dispute in your customer's outstanding balance the dispute must be approved in Oracle Fusion
Receivables. Once it's approved, a credit memo is created. You can apply this credit memo to your customer's
transaction that was disputed before updating their outstanding balance.
What's the dierence between freight and shipping?

Freight is the industry standard term for the compensation paid for any goods, cargo, or lading transported for pay by
water, land, or air. Freight distribution lines pertain to shipping plus other charges levied for moving goods and services.
Shipping is the base transportation cost charged to the customer for transporting goods.
Manage Customer Correspondence

Overview of Dunning
Using Advanced Collections Dunning process, you can inform your delinquent customers about their overdue
payments.
585
Here's how you can manage dunning process:
• Speed up the collection process by automatically sending precongured or custom dunning leers to one or
more customers via email, fax or print.
• Exclude specic customers from receiving dunning notices based on their proles.
• Assign follow-up dunning calls and notices to collection agents.
• Record and display dunning correspondence activity. View a history of each dunning event including leers
resent.
Here are the required details to send dunning correspondence:
Dunning Information Description
Dunning Contact Congure using default names in Dunning Contact when the customer is unidentied.

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.

Dunning Method Set up a method of correspondence. Such as print, fax or email.

Business Intelligence Publisher Use this publisher to create and generate reports and dunning correspondence.

FAQs for Manage Customer Correspondence

Why did my Dunning Process end in Error?
If your Dunning process has ended in error, verify these things
1. Check your Business Intelligence Publisher (BIP) server is set up properly.
2. Check your customer's information is accurate and up to date in the Prole tab.
3. Run and check the Validate Dunning Setup Report for the report details.
Manage Collections Work
586
Overview of Advanced Collections Work Area

Here are few tasks you can do using your Advanced Collections work area:
• View open tasks and delinquent customers details.

• Search for a customer to review the relevant information.
• Open promises, strategy tasks, and activities from the detailed table.
All the important information is visible in the form of infotiles. Here's how you can use these infotiles:
• Manage Delinquent Customers
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 seings 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:
◦ Review the number of open tasks, which can be manual or assigned.

◦ View the list of individual items with their due dates.
• Manage Activities
Here are some of the things you can do to manage activities using Activities infotile:
◦ View all assigned activities which needs your immediate aention.

◦ Create a new activity or view and edit the existing ones.
◦ The data in the Activity table is independent of the data in the Delinquent Customers table.
Request for Bankruptcy

You can initialize the request for bankruptcy on behalf of the customer. Based on the user dened descriptive
exeld, you can record the detailed information such as claims, aorneys involved, ling location, and any other legal
587
information. A submied 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.
Create Request for Bankruptcy

Here are the steps to create request for bankruptcy for a customer:
1. On the landing page, go to Collections menu and click the Collections submenu.
2. Search for the customer account. Click Customer.
3. Click the Prole tab.
4. In Bankruptcy sub tab, click Request buon.
5. Select the Reason for bankruptcy.
6. Optionally if required, enter Comments and upload Aachment.
7. Click Save and Close.
Note:
You can withdraw a bankruptcy after a bankruptcy request has been submied. If bankruptcy isn’t approved, you can't
withdraw the bankruptcy. You need to contact the person approving the request to reject it.
Bankruptcy Request Status

This table shows the actions a collector can take:
Request Type Request Status Bankruptcy Status
Bankruptcy Request Request Pending Request Pending

Bankruptcy Request Request Approved Request Approved

Bankruptcy Request Request Rejected Request Rejected

Bankruptcy Withdraw Withdraw Pending

Request Approved
Note: The withdraw request

can only be enabled when
the bankruptcy status is
Approved, at this step the
588
Request Type Request Status Bankruptcy Status
bankruptcy status isn’t

changed.

Bankruptcy Withdraw Withdraw Approved Withdraw Approved

Bankruptcy Withdraw Withdraw Rejected

Note: The withdraw request
can only be enabled when
the bankruptcy status is
Approved, at this step the
bankruptcy status isn’t
changed.

FAQs for Manage Collections Work

Why did my collections dashboard fail to display delinquent customers?
Here are the things you must check, if you don't see your delinquent customers on your collections dashboard
1. Verify that you’re hired as an employee and set up as a collector.
2. Go to the Prole tab, and conrm that you’re assigned as a collector for that customer.
3. Update the dashboard by submiing the process Update Collections Summary Data.
Collection Manager Dashboard

Using the Collections Manager Dashboard: Explained
The Collections Manager Dashboard enables insight into advanced metrics, known as Key Performance Indicators.
This provides you the ability to understand the nancial health of your customers and eectiveness of your collections
organization. Using this information you can strategically allocate collections resources more eectively.
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 dierent dimensions on the same data, and drill up, down, and through on
any hierarchy level.
589
The Key Performance Indicators can be aggregated across a number of dimensions and hierarchies such as:
• Business Unit
• Customer, Account, and Site
• Collector
• Prole Class
• Country, State, Province, City, or ZIP Code
• Salesperson
• Aging Bucket
Collectors
Use the Manage Resources page for the following:

• Assign collectors to new or dierent customers
• Reassign collectors to all or selected customers
• Assign backup collectors to cover for absent collectors
Delinquent Customers Work Status

Using Collections Dashboard your collectors or collectors group can view their delinquent customers work and update
their work items status. As you work on delinquencies, you can quickly reset the work status with dates for eective
tracking and reporting, and also manage tasks such as follow-up calls on dunning leers or resolve rejected disputes.
You can select the customer based on the various collections criteria and use the Update Work Status option to update
the customer work item status.
Work Statuses
There are four dierent work statuses available on your dashboard. Lets understand what each status means:
Work Status Description Work Status Date
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
Work Status Description Work Status Date
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 not exceed the
Maximum Number of Days value.
You can reschedule the Maximum
Number of Days value from the
seings preference

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
seings preference.

Hold You can keep the work status as Hold

when you don't want to change the work By default, the current date is displayed as
status of the customer. Work Status Date and you can't change it
until the customer is released from Hold
To change the work status you need to work status.
either release the customer from hold
status or remove the customer from the To release the Hold status:
collections dashboard. .
• After the Hold work status date has
passed, run the Update Collections
Dashboard Summary process.
To remove the customer from the

Collections Dashboard:
1. Ensure the customer has made

full payment for all the delinquent
items..
2. From Collections Scoring, run
the Delinquency Identication
concurrent process.
3. Set the Delinquency Method to
Delete and then run the Update
Collections Dashboard Summary
process.
591
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 beer 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
Now let's see how to do these tasks.
Reassign All Customers from One Collector to Another

As per the example here are the steps to reassign all of Collector B customers to Collector A.
1. On your Collections homepage, click Manage Resources.
2. From the Collectors table, select Collector B and click Reassign Collector buon.
3. This brings up the Reassign Collector window. Search for Collector A and click OK buon.
4. Click the Save buon.
You will see that Collector A now has all of the customers originally assigned to Collector B.
Reassign Selected Customers to Another Collector

As per the example here are the steps to reassign Collector B to a limited number of customers:
1. In Manage Resources, from the Collectors table, select Collector B.
2. From the list of Customers in Customers table, multi select two or more customers.
3. Click Reassign Customer.
4. The Reassign Customer window appears. Search for Collector A and click the OK buon.
You will see that Collector A now has the two customers you reassigned from Collector B.
Assign a Backup Collector

As per the example here are the steps to backup assign Collector B as a backup for Collector A :
1. In Manage Resources, from the Collectors table, select Collector A.
2. Go to the Backup Collectors section.
3. Click the New icon.
592
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.
Once this backup collector signs into the application they have the ability to access any customer currently
assigned to the primary collector.
Manage Promise to Pay

Promise to Pay
You can use Promise to pay if a delinquent customer is unable to make the payment immediately or plans to send the
payment later. Promise to pay can help you track if the customer has made the payment by the commied date or not.
You can use status of promise to pay to track the payment, and resolve the delinquent account if the customer has
already made the payment.
Here's what you can do Promise to Pay:
• record a payment commitment and schedule a promise to pay date
• apply promise to pay for multiple delinquent transactions at the same time
• review the outstanding customer account transactions
You can see these three tables in Promise to Pay section:

• Selected Transactions: You can view all the transactions for Promise to Pay here.
• Transaction Details: You can view the Status, State, Amount promised, and Promise date details of all the
Promise to Pay transactions here.
• Mass Promise: You can nd all the transactions for which the customer has commied to make full payment
here.
Manage Promise to Pay

You can do multiple tasks to manage the promise to pay, like these:
• Track the Payment: You can automatically track all the expected payments with its due date.
• Update promise state and status: You can schedule the promise in IEX: the Promise Reconciliation concurrent
program, to update the promise information daily. Remember that you need to schedule this program after
cash has been applied to open transactions. The system veries all the reconciled payments against open
promises and displays the updated promise state and status in your Work Area.
• Mass Transactions: You can make mass Promise to Pay transactions for multiple delinquent customers at a
time. You need to enter only the full payment amount for mass transactions.
• Cancel a Promise: There are times when the customer has made a promise in error. Not a problem, you can
always cancel the promise prior to the Promise due date. Promise to Pay Status
Promise to Pay Status

During the process of Promise to Pay, the transaction can have ve dierent statuses. Lets understand what's the result
of each status:
593
Status Result
Broken The customer has failed to make payment by the Promised date.

Canceled The Promise is invalid, as was entered in error.

Closed The payment is already made on or before the Promise date.

Collectible The Promise has reached the commied payment date.

Fullled The Promise amount is paid on commied date.

Promise to Pay State

The state of Promise to Pay tells you about the overall standing of the promise by the delinquent customer. Lets
understand what these states signies:
State Result
Promise View the Promise details with the payment amount and the promised dates.

Broken The payment isn't made on the commied date.

Create Promise to Pay

These examples illustrate how to create promise to pay.
Let's create a promise to pay for a single transaction for a partial amount of the balance and another mass promise to
pay for all transaction that are 60 days past due.
Create Promise to Pay Request for Single Transaction

You can create Promise to Pay request for either full amount or partial amount. Remember that you can enter partial
amounts for only single transaction at a time. Here are the steps to create Promise to Pay request for single transaction:
2. From the Transaction tab, select the single transaction that is 30 days past due.
3. Click the Promise buon.
4. Click Add row icon.
5. Enter the Promise Date. Note: You can only enter a future date. You can limit this date from the preferences
setup.
6. In Promise Amount eld, enter a partial or full amount of the transaction.
7. Optionally, select the preferred Payment Method. Note: Only credit cards and automatic fund transfers can be
accepted for immediate payment.
594
8. Click Submit.
Promise to Pay Details for Multiple Transactions

You can create Promise to Pay request for only full amount. Remember that you can't enter partial amounts for mass
promise to pay transactions. Here are the steps to create Promise to Pay request for multiple transactions at a time:
2. From the Transaction tab, select multiple transactions that are 60 days past due.
3. Click the Promise buon.
4. Click Add row icon.
5. Enter the upon Promise Date. Note: You can only enter a future date. You can limit this date from the
preferences setup.
6. By default, the full Promise Amount is displayed.
7. Optionally, select the preferred Payment Method. Note: Only credit cards and automatic fund transfers can be
accepted for immediate payment.
8. Click Submit.
FAQs for Manage Promise to Pay

When does the customer account get updated with the promise to pay information?
Here's when a customer account gets updated with the promise to pay information:
• Whenever the promise to pay request is submied it's immediately recorded and updated.
Note: You can congure an automatic conrmation leer sent to you for every submied promise to pay
request.
• Whenever you run Promise Reconciliation program. You can assign the promise to pay request status as
Fullled 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 congure 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 congure these tasks manually or automatically.
595
How You Create a Task

Here's how you can create a task:
1. Set a before or after time to start the next task.
Lets say, you want to allow ve days to a customer after sending a polite reminder and before scheduling a
follow up phone call task. To create the follow up phone call task, set the task to execute as: How long will the
strategy wait until it executes this task and set the wait for period as 5 days.
2. Add wait time after the task is completed.
Specify if the task is optional. If you don't complete the optional task, it is closed automatically at the end of the
wait time. This way the strategy gets free to start the next task.
3. If a task isn't completed on time, you can escalate it to your manager.
Remember that you can only escalate the manual tasks.
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
FAQs for Manage Strategy

What's a Collections method set?
A Collections method set is used to identify the default values to insure that no errors occur when you process the
strategies. Here's the list of default values:
• Collections Method
• Default Collector
• Default Strategy
• Strategy Grace Period Days
• Processing data at the Common Set or by Business Unit
How can I assign a strategy to a customer?

Strategies are assigned automatically when the Strategy Management program is executed. However, you also have
option to manually change the customer's strategy. To change a customer's strategy manually, go to the Prole tab
and click on the Strategy sub tab. Apart form changing the strategy, you can also add, remove, and reassign the tasks
associated to the strategy.
596
How do scoring engines and strategies work together?

Scoring formulas contain data points which are used to score your customers for their capability of making payment.
Based on the customers score generated by the scoring formula, you can associate a strategy to it.
Suppose you have a scoring formula congured to check for overdue transactions. All the transactions which are above
60 days overdue receive a score of 40. So now for any transaction that has scored 40, you can assign a strategy, like as
rst task you may direct the collector to contact the customer by phone.
Collections Metrics
Collections Eectiveness Index Metrics
Using Collections' eectiveness 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 eectiveness of your
collection eorts over time. The closer is your percentage to 100 the more eective is your collection eort.
You can accurately measure the eectiveness of your collection process, amount collected and the amount yet to be
collected, and evaluate the individuals, subgroups, and overall groups.
Now, let's understand the Metric parameters:
• Metrics Common Currency: This is the default currency used for reporting. You can dene 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.
Now lets look at few formulas for metric Calculations:
597
Calculate Collection Eectiveness Index

Using Collection Eectiveness Index (CEI) you can accurately measure the collection eectiveness, amounts to be
collected, and the amount actually collected. You can use this metric to evaluate individuals, subgroups, and overall
groups.
(Beginning Balance + Credit Sales minus Ending Balance) / N / (Beginning Balance + Credit Sales minus Current
Receivables) / N * 100.
Where N = number of days in the period.
Current Receivables= the current amount of receivables transactions which isn't in dispute or due from past.
Calculate Percent Current and Percent Over 90 Days Delinquent

Percent Current = Current Receivables / Ending balance * 100.
Percent Over 90 Days Delinquent = Receivables greater than 90 days Overdue / Ending balance * 100.
Calculate Over 90 Days Delinquent

The over 90 days delinquent is the total amount that's past 90 days due.
Calculate Beginning Balance and Ending Balance

Beginning Balance = Total outstanding open receivables at the beginning of the period.
Ending Balance = Total outstanding open receivables at the end of the period.
Calculate Credit Sales

Revenues generated by an entity that it allowed to the customers on credit, less all sales returns and sales allowances.
Related Topics
• Guidelines for Seing Up Collections Preferences
Days Sales Outstanding

Using the formulated metrics of Advanced Collections you can calculate the Days Sales Outstanding (DSO).
Let's understand Days Sales Outstanding using an example.
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.
Date of Invoice Aging Bucket Dollars in Bucket Credit Sales in Period
9/28/11 Current 3,000 USD 5,000 USD

598
Date of Invoice Aging Bucket Dollars in Bucket Credit Sales in Period
8/28/11 1-30 days past due 3,000 USD 6,000 USD

7/28/11 31-60 days past due 2,000 USD 5,000 USD

Total Open Receivables NA 8,000 USD 16,000 USD

Calculating Various Days Sales Outstanding (DSO)

Let's look at some examples with formulas to calculate each of the Days Sales Outstanding (DSO) metrics:
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 eciently 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:
September Invoice = ($3,000 / $5,000) x 2 = 1.2 days
August Invoice = ($3,000 / $6,000) x 33 = 16.5 days
July Invoice = ($2,000 / $5,000) x 64 = 25.6 days
Sum of True DSO for all open invoices = True DSO per total accounts receivable
1.2 + 16.5 + 25.6 = 43.3 True DSO
Best Possible DSO

In this example you can see, how to calculate the best possible level of receivables. You can use Best Possible DSO only
at the current receivables to calculate the best length of time you can turn over those receivables.
Best Possible DSO = Current Receivables * N / Credit Sales
For example, the calculation based on the earlier data: ($3,000 / $16,000) x 91 = 17 days Best Possible DSO.
599
Sales Weighted DSO

In this example you can see, how to calculate the (aggregate) average time, in days, for which the receivables are
outstanding weighted by the age of the receivables.
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.
Average Days Delinquent

In this example you can see, how to calculate the average time from the invoice due date to the paid date, or the
average days invoices are past due in days.
Average Days Delinquent = Standard DSO - Best Possible DSO.
45.5 DSO - 17 BPDSO = 28.5 average days delinquent
How You Calculate Weighted Average Metrics

Here's how you can calculate various weighted average metrics:
Weighted Average Terms

You can calculates the Weighted Average Terms of the customer, which is the average number of days allowed
for a customer before payment is due. This is weighted according to the item amount. This calculation is based on
your customer's due date of the installment and the terms oered. You can only include the closed and fully paid
transactions of your customers.
You can impose limits on the number of days allowed to a customer to make the payment with multiple payment terms.
Based on which you can either request for immediate payment or oer terms such as:
• NET 30
• 30 / 60 / 90
These terms imply the credit health of your customer. In general, more favorable terms are oered to credit worthy
customers and less favorable to customers at risk.
Formula:
Sum (Original Amount Due *Terms) / Sum (Original Amount Due).
Weighted Average Days Late

You can calculate the average days late weighted for a closed invoice amount with at least one late payment. Days late
are the number of days between the due date and the accounting date of the item activity that closed the item.
For example: The Weighted Average Days Late calculation informs you that your customer pays on average, 5 days
late. However, that number is more meaningful when you know that the customer had an average of 25 days to make
payments.
Formula:
Sum (Amount Due Remaining * Days Late) / Sum (Original Amount Due).
600
Weighted Average Days Paid

Weighted Average Days Paid is the number of days a customer takes to make payments. The average is weighted by
the payment amount, on the assumption that a larger payment is more signicant than a smaller payment.
For example: The weighted average terms are 25, plus the Weighted Average Days Late is 5. This means that your
customer pays an average of 30 days from the invoice date. The 25 days that were allowed plus the 5 extra days taken.
Formula:
(Sum (Date Paid - Invoice Date) x Amount Paid) / Total Payments.
The following table provides an example:
Invoice or Receipt Amount Due or General Days Late Calculation

Number Ledger Date
Invoice 1 1000 USD 7/01/2012 NA NA

Receipt 1 1000 USD 7/25/2012 24 24 x 1000 = 24,000

weighted

Invoice 2 20 USD 8/31/2012 NA NA

Receipt 2 15 USD 1/01/2011 123 123 x 15 (partial

payment) = 1,845
weighted

• 24,000 + 1,845 = 25,845 total weighted days.
• 21,000 + 15 = 1,015 USD total receipts.
• Weighted Average Days Late: 25,845 / 1,015 = 25.
Promise Metrics
You can measure your customer's promises in nominal and currency terms. Here are the formulated metrics for
Promises:
• Broken Promise Amount

• Broken Promise Count
• Broken Promise Percent
• Broken Promise Amount Percent
• Promise Amount
• Promise Count
Let's understand these metrics with an example:
601
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 Metric Resulting Value
Promise Count 10

Promise Amount 1000 USD

Broken Promise Count 5

Broken Promise Percent 50%

Broken Promise Amount 700 USD

Broken Promise Amount Percent 70%

FAQs for Collections Metrics

What's a metric?
You can use metrics to 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. You can use these
metrics to score and assess your customers for their delinquent transactions.
Here are some of the things you can do using these metrics:
• understand the health of your outstanding receivables

• increase the eciency of your collections organization
• expose potential problem areas where you can apply more collections resources
• change collections strategies based on the results
Manage Case Folder
602
Manage Case Folder

You can group related transactions using case folder. These transactions can typically have a common aribute, such
as: a bill-to customer, which is used by a collector to take action during the collections cycle.
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 dierent 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.
Create a Case Folder

Here are the steps to create a case folder:
1. Click the specic Customer.
2. Go to the Transaction tab.
3. Review and select the list of transactions you want to group in the case folder.
4. From Actions menu click Create Case Folder buon. The Case folder status is displayed as Open and a case
number is assigned automatically.
5. You can optionally select the Case Type and enter Comments.
6. Once all required details are entered, click Save.
Actions taken on Case Folder

Once the case folder is created, you can take these actions on the folder:
• Make Payment: Here's how you can make payment for all the grouped transaction in the case folder at a time:
a. Click Pay buon.
b. Enter the full or partial Payment Amount.
c. Select the Payment Method and Site.
d. Click Submit.
• 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 buon.
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
c. Select the note Type and enter the note text.

d. Click Save and Close.
Edit a Case Folder

You can make the these edits to a case folder:
• Add Transactions: Select one or more transactions from the transaction list to add to the case folder.
• Remove Transactions: Select the case folder containing the transactions and remove one or more
transactions.
Note: Transactions in the case folder having a collectible or open promise are canceled for the
entire group when adding or removing one or more transactions. The recommendation is to enter a
new promise for the case folder.
• Create a Promise: Click the Promise buon. Enter one or more transactions numbers to create the promise or
promises. Enter the date of the promise.
• Update a Promise: Click the Promise buon, update the promise date.
• Pay Case: Click the Pay buon. 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.
FAQs for Manage Case Folder

What's a case folder?
You can create case folders to logically group related transactions. Using case folders you can perform collection
activities on the entire group at a time. You can apply payment, create promises, and provide additional information
about the case folder. This increases your collections eciency by saving time and eort on customers that have a large
number of similar invoices.
Restrictions for creating and editing a case folder
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.
Reports for Manage Advanced Collections

Oracle Fusion Advanced Collections Predened Reports
You can generate some predened reports that can be used in various stages throughout the collections process.
How to schedule a report?
604
You can schedule a report from your Scheduled Process Work area and Reports and Analytics Work area.
• Schedule a report from Scheduled process 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.
You can create various predened reports based these areas:
• Aging
• Dunning
• Promises
Aging Reports
Here are the three types of predened 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

• *Order By
• *Report Summary
• *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

605
• *Order By
• *Report Summary
• *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
Here is the predened dunning report:
Validate Customer Dunning Setup Report Displays customer dunning setup issues • *Business Unit
and provides solution. • *Business Level
• *Show Errors Only
• From Customer Account
• To Customer Account
Promises Report
Here is the predened promise report:
Promise Reconciliation Report Displays promise information by collector • Business Unit

and is based on payments received and • *From Date
the promise status. • *To Date

• *Currency
• State
• Status
• *Report Format
• Collector Name
How to run a predened report?
Here are the steps to run a predened reports:
1. Navigate to the Scheduled Processes work area.
606

3. Search the Process Name.
4. Enter the required parameters of the process.
6. Click Submit.
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 dened.
Here are the types of aging report you can create:
Aging 4 Bucket Report

In this report, you can view your customer's open transaction information based on the four bucket aging method.
This image shows a sample of Collections Aging 4 Bucket Report.
Report Parameters
This table shows all the required parameters for creating Collections Aging 4 Bucket Report:
607
Parameter Name Description
Aging Bucket Method Either Staged or Aged, based on your company setup.

Order By Select by Customer or Transaction Type.

Report Summary Yes to display in summary, No to display in detail.

Show Open Credits Yes or No to display open credits.

Show Receipts At Risk Yes or No to display receipts at risk.

Aging by Collector 7 Bucket Report

In this report, you can view your customer's open transaction information by collector using the seven bucket aging
method.
This image shows a sample of Collections Aging by Collector 7 Bucket Report.
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.

As-of Accounting Date Period start date for the report.

Order By Select by Customer or Transaction Type.

608
Report Format Select the format such as HTML, PDF, or Excel.

Report Summary Yes to display in summary, No to display in detail.

Aging by Common Currency Report

In this report, you can view all open transaction information converted to one common currency for all Business Units
or a specic Business Unit.
This image shows a sample of Aging by Common Currency Report
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.

Aging Bucket Method Either Staged or Aged based on setup.


This table lists some frequently asked questions about the aging reports.
609
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.

Who uses these reports? • Financial Manager

When do I use these reports?

You can use these reports to:
• Review aging typically on a daily or weekly basis.

• Understand the aging and risk exposure of outstanding receivables.
What can I do with these reports? Use these reports to formulate strategies with task or tasks to collect on outstanding
delinquent customers.

What type of reports are these? Oracle Business Intelligence Publisher

Related Topics
• Aging Methods
• Collections Strategies
• Processing Strategies
Validate Customer Dunning Setup Report

In the Validate Customer Dunning Setup Report you can view all the dunning setup issues of your customers. You
can use this report to verify and identify gaps of dunning congurations. For example the report can display missing
customer e-mail, fax, or contact name. This report only shows those customers who have open transactions.
610
This image shows a sample of Validate Customer Dunning Setup Report
Report Parameters
This table shows all the required parameters for creating Validate Customer Dunning Setup Report.
Name Description
Business Unit Select the appropriate business unit.

From Collector Name Starting range of collectors.

To Collector Name Ending range of collectors.

From Customer Account Starting range of customer accounts.

To Customer Account Ending range of customer accounts.

From Customer Name Starting range of customer names.

To Customer Name Ending range of customer names.


This table lists some frequently asked questions about the Validate Customer Dunning Setup Report.
611
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 conguring 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 Conrmation Notices
Promise Reconciliation Report

In Collections Promise Reconciliation Report you can view all the promise details of each collector based on business
unit and date range. You can use this report to reconcile promises to pay with broken promises.
This image shows a sample of Collections Promise Reconciliation Report:
Report Parameters
This table shows all the required parameters for creating Collections Promise Reconciliation Report.
Name Description
Business Unit Select the appropriate business unit.

Collector Name Specify by collector if appropriate.

612
Name Description
Currency Select the appropriate currency.

Date From Starting date range.

Date To Ending date range

Report Format Select format such as HTML, PDF, or Excel.


This table lists some frequently asked questions about the Collections Promise Reconciliation Report.
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 Conrmation Notices
613
614
Using Receivables Credit to Cash Manage Bill Management
10 Manage Bill Management
Overview of Bill Management

Do you frequently do these tasks for your customers?
• Remind the customer to pay bills
• Print and mail their bills
• Identify their outstanding transactions
• Answer questions about their accounts
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.
Here's what you can do in the application.

• Register and unregister customers
• Review your customer accounts
• View and print transactions
• Dispute 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)
Register External Users

Using external user registration, the Collections or Receivables department personnel can register external customer
contact(s) and empower them to manage, pay, print and dispute their own transactions. You can register an external
user using either Oracle Applications UI or REST API.
Register External Users Using Oracle Application UI

To register customer contacts as external users using application UI:
1. Sign in to Oracle Applications.
2. In the Setup and Maintenance work area, select these options:
Oering: Financials
Functional area: Bill Management
Task: Manage Bill Management Registration
615
3. Click Register Users.

4. Search and select the customer contact.
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.
5. Click Register. Review the customer status. If the status is:
Status What you need to do
Registering Wait for a few minutes. If the customer contact gets successfully registered, the status
changes to Registered. If not, it changes to Error.

Error Register your customer contact again.

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.
Register External Users Using REST API

Using user registration, the Collections or Receivables department personnel can register external customer contact(s)
and empower them to manage, pay, print and dispute their own transactions. Use the billManagementUsers resource to
manage the user registrations. You must register a user to Bill Management, search for user records (all accounts) of a
particular customer, and search for customer records of a particular user.
Here are the steps to manage user registration using REST API:
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 specic 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
Select Your Customer Account

You can only access your customer's accounts if the Customer Account Billing Inquiry role or a similar role is assigned
to you.
To access your customer's accounts:
1. Sign in to Oracle Applications.

2. From the application dashboard, select Bill Management.
3. In the Select Account dialog box, enter the details of the customer account.
4. Click Search.
5. Select the customer and click OK.
Note: Your customers can just sign in to Bill Management using the link, user ID, and password given to
them at the time of registration.
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.
Review Customer Accounts

After you sign in to Oracle Applications and do the prerequisite steps, the Account Overview page opens. You can see
these items:
• Infotiles that provide a quick summary of transactions made by the customer.
Infotile What you see
Total The total number of open transactions that are pending payment for all currencies.

Invoices

◦ The total number of printed invoices of open transactions.
◦ A pie chart of invoices based on the aging bucket.
Credit Memos The total number of open receivables credit transactions.

In Dispute The total number of disputed transactions pending approval.

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.
• A list of open transactions for your accounts.
617
To view details of a transaction:

a. On the Account Overview page, click the transaction number.
b. Click View Activities.
To see a detailed transaction history for an account:
a. On the Account Overview page, click Transaction History.
b. You can also see transactions done during a specic period and when each transaction was fully or
partially closed, along with their receipt numbers.
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:
◦ Select the transaction number to open the transaction.

◦ Select the check box against the transaction.
2. Click Print.
To print invoices only:
1. On the Account Overview page, select the Invoice infotile.
2. Select the invoice number to view a copy of the invoice before printing. You can also select the check box
against the invoice.
3. Click Print.
To print credit memos only:
1. On the Account Overview page, select the Credit Memos infotile.
2. Select the credit memo number to view a copy of the credit memo before printing. You can also select the
check box against the credit memo.
3. Click Print.
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
Note: If you can't see the Request Credit buon, 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.
Make Online Payments

Only registered customers can make online payments.
To make payments:
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 conrmation message on the page.
Additionally, you can congure the next payment date and dene the number of future payments using the Manage Bill
Management System Options task from the Setup and Maintenance work area.
FAQs for Bill Management

Why can't my customer access Bill Management?
Here's why:
Your customer may not have the security permissions to access Bill Management or their customer accounts. They
should check with their supplier's Receivables or Collections Manager to get themselves registered to access Bill
Management.
Why can't the customer see the Request Credit buon 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
buon and the Dispute infotile. They can contact their Receivables or Collections Manager to request permission and
raise disputes.
619
Can I register my customer as a single user for multiple customer

accounts?
Yes, you can. If you do so, the customer can manage transactions for all those customer accounts.
How can the customer register for Bill Management?

Your customer can't register directly to Bill Management. You must register the customer as an external user.
What happens if multiple users are registered for an account?

All registered users can manage transactions for that account.
620
Oracle Financials Cloud Glossary
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
622

Using Receivables Credit To Cash

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Using Receivables Credit To Cash

Uploaded by

Copyright:

Available Formats

Oracle Financials

Using Receivables Credit to Cash

1 Manage Customer Billing 1

2 Process Customer Payments 191

3 Manage Funds Capture 255

4 Manage Accounts Receivable Balances 317

5 Manage Revenue for Receivables 401

6 Manage Bills Receivable 417

7 Manage Credit Management 445

8 Manage Cash Management and Banking 457

9 Manage Advanced Collections 577

10 Manage Bill Management 615

Using Oracle Applications

• Training: Take courses on Oracle Cloud from Oracle University.

> Greater than symbol separates elements in a navigation path.

Access to Oracle Support

Comments and Suggestions

1 Manage Customer Billing

Create and Process Transactions

Dierent requirements apply depending on the kind of transaction:

Requirements for Completing a Standard Invoice

Requirements for Completing an Invoice with Rules

• Each line must have valid account sets.

Requirements for Completing a Standard Credit Memo

If the invoice is a project-related invoice, then no distribution information is displayed.

Guidelines for Entering Invoice Lines

Tax Inclusive Amounts

Updates to Tax Lines

How Revenue Scheduling Rules Are Used

Seings That Aect Revenue Scheduling Rules

These rules apply to each of the four rule types:

How the Revenue Schedule Is Calculated

Revenue Amount = Daily Revenue Rate * Days in Period

Using Revenue Scheduling Rule Types

January 14 January 18 180 180 225 180

February 14 February 28 280 295 225 240

March 14 March 31 310 295 225 240

April 13 April 13 130 130 225 240

Observations on this example:

How Foreign Currency Transactions Are Processed

Seings That Aect Foreign Currency Conversion

Enter conversion rate information:

How the Ledger Currency Amount Is Calculated

Guidelines for Updating Installments on Transactions

Set Up for Installment Updates

Update the Due Date of Installments

Update the Unpaid Portion of an Installment

Add and Delete Installments

Structured Payment References on Transactions and Receipts

Structured Payment Reference Field

The Structured Payment Reference eld appears on these pages:

Structured Payment References on Transactions

Structured Payment References on Receipts

In the Edit Receipt page, you can:

• Update the structured payment reference on a receipt.

For automatic receipts:

OAGIS 10.1 XML Transactions

Prepare User-Dened Aributes

The public APIs include:

If RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY is not set to Y by the Load Extension Aributes for XML

PROCEDURE insert_ar_extension_aributes(extension_ar_tbl IN ARP_UTIL.EXTENSION_ATTR_TBL_TYPE,

x_msg_count OUT NOCOPY NUMBER,

x_msg_data OUT NOCOPY VARCHAR2,