Receivables Student Guide-11i

11i Oracle Receivables
Fundamentals
Volume 1 - Student Guide
D16812GC30
Edition 3.0
January, 2005
D40244
Copyright Oracle Corporation, 2005. All rights reserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing
restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this
documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights
and the following legend is applicable:
Restricted Rights Legend
Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed
to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the
Education Products group of Oracle Corporation. Any other copying is a violation of copyright law and may result in civil and/or
criminal penalties.
If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with
Restricted Rights, as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the documentation, please report
them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores, CA 94065.
Oracle Corporation does not warrant that this document is error-free.
Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Author
Douglas Myers, Tyra Crockett, Pratima Mahtani, Manjula Shankar
Technical Contributors and Reviewers
Vanessa Graziano, Rebecca Zarchikoff, David Reitan, Susan Flierl, Natalia Rachelson, Stacey
Gomes, David Barnacle, Steve Best, Amit Batra, Nami Hosomatsu, Bernadette Kennedy,
Chayne Kosloske, David Chin, Eric O'Brien, Friederun Baudach-Jaeger, Kathy Wohnoutka,
Lynn Warneka, John Brazier, David Millin, Paul Scott.
This book was published using:
oracletutor
Table of Contents
Order to Cash Lifecycle Overview .................................................................................................................1-1
Order to Cash Lifecycle Overview ................................................................................................................1-2
Objectives ......................................................................................................................................................1-3
Order to Cash Lifecycle.................................................................................................................................1-4
Order Lifecycle..............................................................................................................................................1-5
Overview of Application Integration.............................................................................................................1-6
Order Management Process...........................................................................................................................1-7
Viewing and Managing Orders......................................................................................................................1-8
Scheduling Process ........................................................................................................................................1-9
Pricing Process ..............................................................................................................................................1-10
Shipping Process ...........................................................................................................................................1-11
AutoInvoice Process ......................................................................................................................................1-12
Receivables Process.......................................................................................................................................1-13
Cash Management Process ............................................................................................................................1-14
Summary........................................................................................................................................................1-15
Overview of Oracle Receivables Process .......................................................................................................2-1
Overview of Oracle Receivables Process ......................................................................................................2-2
Objectives ......................................................................................................................................................2-3
Order to Cash Lifecycle.................................................................................................................................2-4
Overview of Receivables in the Order to Cash Process.................................................................................2-5
Overview of the Receivables Process............................................................................................................2-6
Overview of Receivables Integration ............................................................................................................2-7
Receivables Integration Process ....................................................................................................................2-8
Overview of the Transaction Process ............................................................................................................2-9
Overview of Other Invoice Operations..........................................................................................................2-10
Overview of Adjustments ..............................................................................................................................2-11
Overview of Credit Memos ...........................................................................................................................2-12
Overview of the AutoInvoice Process ...........................................................................................................2-13
Overview of Receipts and Remittances .........................................................................................................2-14
Overview of Collections ................................................................................................................................2-15
Overview of Tax............................................................................................................................................2-16
Oracle iReceivables .......................................................................................................................................2-17
Oracle iReceivables Product Integration .......................................................................................................2-18
Overview of Oracle iReceivables Features....................................................................................................2-20
Summary........................................................................................................................................................2-23
Manage Parties and Customer Accounts.......................................................................................................3-1
Manage Parties and Customer Accounts .......................................................................................................3-2
Objectives ......................................................................................................................................................3-3
Agenda...........................................................................................................................................................3-4
Customer Overview.......................................................................................................................................3-5
Party Model Overview...................................................................................................................................3-6
Party Model ...................................................................................................................................................3-8
Party Model and Relationships......................................................................................................................3-9
Party Model Components ..............................................................................................................................3-11
Managing Parties ...........................................................................................................................................3-12
Party Sites......................................................................................................................................................3-13
Customer Accounts........................................................................................................................................3-14
Integrating Party Information ........................................................................................................................3-15
Data Quality Management Overview ............................................................................................................3-16
Agenda...........................................................................................................................................................3-17
Profile Classes ...............................................................................................................................................3-18
Copyright 2005, Oracle. All rights reserved.
11i Oracle Receivables Fundamentals Table of Contents
Profile Class Characteristics ..........................................................................................................................3-20

Practice - Create a Customer Profile Class ................................................................................................3-21
Solution - Create a Customer Profile Class ...............................................................................................3-22
Managing Customer Account Profiles...........................................................................................................3-23
Updating Profile Classes ...............................................................................................................................3-24
Reviewing Profile Class Changes..................................................................................................................3-25
Agenda...........................................................................................................................................................3-26
Data Quality Management Overview ............................................................................................................3-27
Data Quality Management (DQM) ................................................................................................................3-28
How Does DQM Work? ................................................................................................................................3-29
Fuzzy Search .................................................................................................................................................3-30
Query Word Replacement .............................................................................................................................3-31
Entry Methods ...............................................................................................................................................3-32
Business Issues ..............................................................................................................................................3-33
Business Purposes..........................................................................................................................................3-34
Multiple Sites and Business Purposes: Centralized Example ........................................................................3-35
Multiple Sites and Business Purposes: Decentralized Example ....................................................................3-36
Interface Data Entry.......................................................................................................................................3-37
Using Standard and Quick Entry ...................................................................................................................3-39
Practice - Create a Customer using the Standard Data Entry Form ...........................................................3-41
Solution - Create a Customer using the Standard Data Entry Form ..........................................................3-44
Differences Between Standard and Quick Entry ..........................................................................................3-47
Practice - Create a Customer using the Quick Data Entry Form ...............................................................3-48
Solution - Create a Customer using the Quick Data Entry Form...............................................................3-49
Dun & Bradstreet (D&B) Integration ............................................................................................................3-50
D&B Data Formats........................................................................................................................................3-51
D&B Online...................................................................................................................................................3-52
D&B Batch Loading......................................................................................................................................3-53
Agenda...........................................................................................................................................................3-54
Customer Account Relationships ..................................................................................................................3-55
Practice - Create a Customer Account Relationship ..................................................................................3-56
Solution - Create a Customer Account Relationship .................................................................................3-57
Agenda...........................................................................................................................................................3-58
Oracle Trading Community Architecture ......................................................................................................3-59
TCA Parties ...................................................................................................................................................3-60
TCA Administration ......................................................................................................................................3-61
Using Party Paying Relationships .................................................................................................................3-62
Using Customer Account Relationships ........................................................................................................3-63
Party Paying and Customer Account Relationships ......................................................................................3-64
Creating Party Paying Relationships .............................................................................................................3-65
Pay Within Paying Relationships ..................................................................................................................3-66
Party Paying Relationships Process Flow......................................................................................................3-67
Pay Below Paying Relationships ...................................................................................................................3-68
Relationship Types and Relationship Groups................................................................................................3-69
Agenda...........................................................................................................................................................3-70
Merge Parties or Customer Accounts ............................................................................................................3-71
Party Merge ...................................................................................................................................................3-73
Agenda...........................................................................................................................................................3-74
Reviewing Information..................................................................................................................................3-75
Common Search Scenarios ............................................................................................................................3-76
Reports...........................................................................................................................................................3-77
Agenda...........................................................................................................................................................3-78
Required Customer Profile Setup Steps.........................................................................................................3-79
Collectors.......................................................................................................................................................3-80
Payment Terms ..............................................................................................................................................3-81
Optional Customer Profile Setup Steps .........................................................................................................3-82
Required Setup Steps for Customers .............................................................................................................3-84
ii
Profile Options...............................................................................................................................................3-85
Optional Setup Steps for Customers..............................................................................................................3-87
Flexible Address Formatting .........................................................................................................................3-89
Summary........................................................................................................................................................3-91
Process Invoices Using AutoInvoice...............................................................................................................4-1
Process Invoices Using AutoInvoice .............................................................................................................4-2
Objectives ......................................................................................................................................................4-3
Agenda...........................................................................................................................................................4-4
AutoInvoice Process ......................................................................................................................................4-5
AutoInvoice Integration.................................................................................................................................4-6
What Occurs During AutoInvoice .................................................................................................................4-7
AutoInvoice Interface Tables ........................................................................................................................4-8
Agenda...........................................................................................................................................................4-10
Managing AutoInvoice System Options........................................................................................................4-11
Transaction Batch Sources ............................................................................................................................4-12
Defining Transaction Batch Sources .............................................................................................................4-13
Grouping Rules..............................................................................................................................................4-14
Grouping Transaction Attributes ...................................................................................................................4-15
Grouping Rule Hierarchy ..............................................................................................................................4-16
Line Ordering Rules ......................................................................................................................................4-17
Transaction Flexfields ...................................................................................................................................4-18
Defining Transaction Flexfields ....................................................................................................................4-19
Determining Tax Liability .............................................................................................................................4-20
AutoInvoice Validation .................................................................................................................................4-21
Submitting AutoInvoice ................................................................................................................................4-22
Implementation Considerations .....................................................................................................................4-23
Agenda...........................................................................................................................................................4-24
Correct Errors Overview ...............................................................................................................................4-25
AutoInvoice Exception Handling Windows ..................................................................................................4-26
Summary........................................................................................................................................................4-28
Process Invoices ...............................................................................................................................................5-1
Process Invoices ............................................................................................................................................5-2
Objectives ......................................................................................................................................................5-3
Agenda...........................................................................................................................................................5-4
Oracle Receivables Overview........................................................................................................................5-5
Transactions Overview ..................................................................................................................................5-7
Transactions Workbench Windows ...............................................................................................................5-8
Agenda...........................................................................................................................................................5-9
Invoice Entry Methods ..................................................................................................................................5-10
Creating a Standard Invoice Manually ..........................................................................................................5-11
Invoice Components ......................................................................................................................................5-12
Transactions Window Tabs ...........................................................................................................................5-14
Required Transaction Information.................................................................................................................5-16
Entering Invoice Dates ..................................................................................................................................5-17
Transaction Defaults......................................................................................................................................5-18
Standard Invoice Line Types .........................................................................................................................5-20
Entering Freight Invoices or Lines ................................................................................................................5-21
Entering Sales Credits ...................................................................................................................................5-22
Completing Transactions ...............................................................................................................................5-24
Practice - Create an Invoice .......................................................................................................................5-25
Solution - Create an Invoice ......................................................................................................................5-26
Creating Invoice Batches...............................................................................................................................5-27
View Currency Details ..................................................................................................................................5-28
Agenda...........................................................................................................................................................5-30
Creating Copies of Invoices...........................................................................................................................5-31
Using Recurring Rules...................................................................................................................................5-32
iii
Practice - Copy an Invoice.........................................................................................................................5-34

Solution - Copy an Invoice ........................................................................................................................5-35
Creating Invoices with Rules.........................................................................................................................5-36
Accounting Rules ..........................................................................................................................................5-37
Assigning Accounting Rules to Invoice Lines...............................................................................................5-38
Using Invoices With Rules ............................................................................................................................5-39
Example of Billing in Advance .....................................................................................................................5-40
Example of Billing in Arrears........................................................................................................................5-41
Deferred Accounting Rules ...........................................................................................................................5-42
Revenue Recognition Program ......................................................................................................................5-43
How Oracle Receivables Uses Statements ....................................................................................................5-44
Making Adjustments Using Revenue Accounting.........................................................................................5-45
Setup Details Report......................................................................................................................................5-46
AR: Use Statement Site and Dunning Site Profiles .......................................................................................5-47
Agenda...........................................................................................................................................................5-48
Invoice Transaction Flow ..............................................................................................................................5-49
Invoice Correction Methods ..........................................................................................................................5-50
Overview of Corrections................................................................................................................................5-51
Overview of Corrections (Continued) ...........................................................................................................5-52
Updating Invoices..........................................................................................................................................5-53
Creating Debit Memos...................................................................................................................................5-54
Creating Adjustments ....................................................................................................................................5-55
Applying Different Types of Credits .............................................................................................................5-56
Credit Memo Options ....................................................................................................................................5-57
Practice - Create a Credit Memo................................................................................................................5-59
Solution - Create a Credit Memo ...............................................................................................................5-60
On-Account Credit Options...........................................................................................................................5-61
Reversing Sales Credits .................................................................................................................................5-62
Creating Refunds ...........................................................................................................................................5-63
Voiding Transactions.....................................................................................................................................5-65
Agenda...........................................................................................................................................................5-66
Transaction Types..........................................................................................................................................5-67
Define Transaction Types..............................................................................................................................5-68
Deposit Transaction Type..............................................................................................................................5-69
Agenda...........................................................................................................................................................5-70
Reports...........................................................................................................................................................5-71
Printing Transactions.....................................................................................................................................5-72
Process for Printing Transactions ..................................................................................................................5-73
Practice - Print a Transaction.....................................................................................................................5-74
Solution - Print a Transaction ....................................................................................................................5-75
Using Consolidated Billing............................................................................................................................5-76
Practice - Print Consolidated Billing .........................................................................................................5-77
Solution - Print Consolidated Billing.........................................................................................................5-78
Practice - Correct Errors ............................................................................................................................5-79
Solution - Correct Errors ...........................................................................................................................5-80
Agenda...........................................................................................................................................................5-84
Event-Based Revenue Management ..............................................................................................................5-85
Automated Process ........................................................................................................................................5-86
Evaluating Invoices for EventBased Revenue Management .......................................................................5-87
Collectibility Requirements for Revenue Recognition ..................................................................................5-88
How Collectibility Requirements Relate to Invoices.....................................................................................5-89
Applying Receipts and EventBased Revenue Management ........................................................................5-90
Agenda...........................................................................................................................................................5-91
XML Receivables Documents.......................................................................................................................5-92
XML Invoices Process Flow .........................................................................................................................5-93
Sending XML Invoice Documents ................................................................................................................5-95
Confirming the Import Status of XML Invoice Documents ..........................................................................5-96
iv
XML Invoice Documents ..............................................................................................................................5-97

Reviewing and Retransmitting XML Invoice Documents............................................................................5-98
Agenda...........................................................................................................................................................5-99
Promised Commitment Amounts ..................................................................................................................5-100
Summary........................................................................................................................................................5-101
Bill Presentment Architecture ........................................................................................................................6-1
Bill Presentment Architecture........................................................................................................................6-2
Objectives ......................................................................................................................................................6-3
Bill Presentment Architecture Overview.......................................................................................................6-4
BPA Framework ............................................................................................................................................6-5
BPA Process Flow .........................................................................................................................................6-6
Creating Templates........................................................................................................................................6-7
Defining Assignment Rules...........................................................................................................................6-9
Data Retrieval................................................................................................................................................6-10
Registering Data Sources...............................................................................................................................6-11
Enabling Data Sources...................................................................................................................................6-12
Viewing Data Sources ...................................................................................................................................6-13
Creating Database Views...............................................................................................................................6-14
Registering Data Source Views .....................................................................................................................6-15
Viewing Data Source Views..........................................................................................................................6-16
Template Management ..................................................................................................................................6-17
Modifying Templates ....................................................................................................................................6-18
Creating a New Template ..............................................................................................................................6-19
Uploading External Templates ......................................................................................................................6-20
Assigning Templates .....................................................................................................................................6-21
Defining Template Rules...............................................................................................................................6-22
Creating a New Assignment Rule..................................................................................................................6-24
Selecting Attribute Matching Criteria............................................................................................................6-25
Selecting Conditions for Rules ......................................................................................................................6-26
Assigning a Template to a Rule.....................................................................................................................6-27
Reordering Rules ...........................................................................................................................................6-28
Print Management..........................................................................................................................................6-29
Submitting Print Requests .............................................................................................................................6-30
Creating and Updating Page Setups...............................................................................................................6-31
Summary........................................................................................................................................................6-32
Credit Management.........................................................................................................................................7-1
Credit Management .......................................................................................................................................7-2
Objectives ......................................................................................................................................................7-3
Agenda...........................................................................................................................................................7-4
Set Up Oracle Credit Management................................................................................................................7-5
Define Credit Analysts ..................................................................................................................................7-6
Assign Credit Analyst to Accounts................................................................................................................7-7
Define Lookups .............................................................................................................................................7-8
Define System Options..................................................................................................................................7-9
Define Scoring Models..................................................................................................................................7-10
Assign Automation Rules ..............................................................................................................................7-11
Credit Checklist .............................................................................................................................................7-12
Credit Usage Rule Sets ..................................................................................................................................7-13
Define Credit Hierarchies ..............................................................................................................................7-14
Define Customer Profile Classes ...................................................................................................................7-15
Customer Profile Classes: Credit Profile Tab...............................................................................................7-16
Use Customers-Standard ...............................................................................................................................7-17
Agenda...........................................................................................................................................................7-18
Process Credit Reviews .................................................................................................................................7-19
Initiate a Credit Review.................................................................................................................................7-20
Collecting Credit Data ...................................................................................................................................7-21
Analyzing Credit Data ...................................................................................................................................7-22

Making a Recommendation...........................................................................................................................7-23
Implementing the Recommendation..............................................................................................................7-24
Agenda...........................................................................................................................................................7-25
Credit Management Application Workflow ..................................................................................................7-26
Oracle Approvals Management (AME).........................................................................................................7-27
Agenda...........................................................................................................................................................7-28
Review Credit Management Performance .....................................................................................................7-29
Agenda...........................................................................................................................................................7-30
Define Credit Hierarchies ..............................................................................................................................7-31
Identify a Credit Hierarchy............................................................................................................................7-32
Summary........................................................................................................................................................7-33
Implement Customer Invoicing......................................................................................................................8-1
Implement Customer Invoicing .....................................................................................................................8-2
Objectives ......................................................................................................................................................8-3
Agenda...........................................................................................................................................................8-4
Required Setup Steps for Transactions..........................................................................................................8-5
Receivables Transaction Types .....................................................................................................................8-6
Using Natural Application.............................................................................................................................8-8
AutoAccounting ............................................................................................................................................8-9
Payment Terms ..............................................................................................................................................8-10
Transaction Sources.......................................................................................................................................8-11
Remit-to Addresses........................................................................................................................................8-12
System Options Relating to Transactions......................................................................................................8-13
Miscellaneous System Options......................................................................................................................8-15
Profile Options...............................................................................................................................................8-17
Implementation Considerations for Transactions ..........................................................................................8-19
Implementation Considerations for Remit-To Addresses..............................................................................8-20
Optional Setup Steps for Transactions...........................................................................................................8-21
Accounting Rules ..........................................................................................................................................8-23
Salespeople ....................................................................................................................................................8-24
Standard Memo Lines....................................................................................................................................8-25
Setting Up Document Sequencing.................................................................................................................8-26
Setting Up Gapless Transaction Numbering..................................................................................................8-27
Setting Up Statements ...................................................................................................................................8-29
Consolidated Billing Invoices........................................................................................................................8-30
Setting Up Consolidated Billing....................................................................................................................8-31
Transaction Printing Views Overview...........................................................................................................8-32
Transaction Printing Views ...........................................................................................................................8-33
Agenda...........................................................................................................................................................8-34
Define Transaction Types in Order ...............................................................................................................8-35
Implementation Considerations for Document Sequencing Enhancements ..................................................8-36
Function Security...........................................................................................................................................8-37
Summary........................................................................................................................................................8-38
Receipts.............................................................................................................................................................9-1
Receipts .........................................................................................................................................................9-2
Objectives ......................................................................................................................................................9-3
Agenda...........................................................................................................................................................9-4
Oracle Receivables Overview........................................................................................................................9-6
Overview of Receipts ....................................................................................................................................9-7
Receipt Creation ............................................................................................................................................9-8
Cash Receipt Statuses....................................................................................................................................9-9
Manual Receipt Entry Process.......................................................................................................................9-10
Manual Receipt Types ...................................................................................................................................9-11
Manual Receipts Versus QuickCash Receipts...............................................................................................9-12
Practice - Enter a Manual Receipt .............................................................................................................9-13
vi
Solution - Enter a Manual Receipt.............................................................................................................9-14

Creating Batches............................................................................................................................................9-15
Validating Receipts in Batches ......................................................................................................................9-16
Batch Statuses................................................................................................................................................9-17
Agenda...........................................................................................................................................................9-18
Applying Batch Receipts ...............................................................................................................................9-19
Applying Receipts to an Invoice....................................................................................................................9-20
Applications Window ....................................................................................................................................9-21
Practice - Apply a Receipt .........................................................................................................................9-22
Solution - Apply a Receipt ........................................................................................................................9-23
Criteria for Mass Applying Receipts .............................................................................................................9-24
Practice - Use Mass Apply ........................................................................................................................9-25
Solution - Use Mass Apply........................................................................................................................9-26
Multiple Prepayment Types...........................................................................................................................9-27
Applying Cross Currency Receipts................................................................................................................9-28
Entering Discounts ........................................................................................................................................9-29
Agenda...........................................................................................................................................................9-30
Chargebacks and Adjustments.......................................................................................................................9-31
Chargebacks and Adjustments against Transactions .....................................................................................9-32
Chargebacks against Receipts........................................................................................................................9-33
Creating a Chargeback...................................................................................................................................9-34
Working with Claims.....................................................................................................................................9-35
Creating Claims .............................................................................................................................................9-36
Automatic Claim Creation Through Lockbox and Quickcash.......................................................................9-37
Resolving Claims...........................................................................................................................................9-38
Automated Settlement Methods Effectively Settle Deductions.....................................................................9-39
Resolving Claims not Associated to an Invoice ............................................................................................9-41
Resolving a Split Claim .................................................................................................................................9-42
Agenda...........................................................................................................................................................9-44
Balance Segments..........................................................................................................................................9-45
Deriving Balancing Segment Values.............................................................................................................9-46
Disabling the Balancing Segment Substitution Process for Activities ..........................................................9-47
AR: Disable Receivable Activity Balancing Segment Substitution ..............................................................9-48
Agenda...........................................................................................................................................................9-49
Lockboxes......................................................................................................................................................9-50
Using AutoLockbox ......................................................................................................................................9-51
Lockbox Integration ......................................................................................................................................9-52
Historical Data Conversion............................................................................................................................9-53
AutoLockbox Process....................................................................................................................................9-54
Importing Data from your Bank File .............................................................................................................9-56
AutoLockbox Validation ...............................................................................................................................9-57
AutoLockbox and Customer Identification ...................................................................................................9-59
AutoLockbox Transmissions .........................................................................................................................9-60
Applying Receipts using AutoLockbox.........................................................................................................9-61
Creating Claims Using AutoLockbox............................................................................................................9-63
Importing and Applying Cross Currency Receipts ........................................................................................9-65
Lockbox Execution Report ............................................................................................................................9-66
Receipt to Receipt Applications ....................................................................................................................9-67
Automated Receipt Handling for Credits ......................................................................................................9-69
Automatic Receipts........................................................................................................................................9-70
Bank Remittance Process ..............................................................................................................................9-71
Creating Automatic Receipts.........................................................................................................................9-72
Automatic Receipts and Remittance Process Overview ................................................................................9-73
Credit Cards...................................................................................................................................................9-74
Processing Credit Card Refunds....................................................................................................................9-76
Processing Credit Card Transactions.............................................................................................................9-77
Creating Credit Card Transactions ................................................................................................................9-78
vii
Credit Card Refunds ......................................................................................................................................9-79

Summary........................................................................................................................................................9-80
Implement Receipts .........................................................................................................................................10-1
Implement Receipts .......................................................................................................................................10-2
Objectives ......................................................................................................................................................10-3
Agenda...........................................................................................................................................................10-4
Overview of Receipt Setup............................................................................................................................10-5
Types of Receivables Activities ....................................................................................................................10-6
Receivables Activity Setup............................................................................................................................10-8
Receivables Activities Example ....................................................................................................................10-10
Receipt Class, Payment Method, and Bank Account Relationship .............................................................10-11
Defining Banks ..............................................................................................................................................10-12
Defining Bank Accounts ...............................................................................................................................10-13
Practice - Define Banks .............................................................................................................................10-14
Solution - Define Banks.............................................................................................................................10-15
Defining Receipt Classes...............................................................................................................................10-17
Associating a Bank Account With a Payment Method..................................................................................10-19
Defining Receipt Sources ..............................................................................................................................10-20
Defining AutoCash Rules ..............................................................................................................................10-21
Defining Application Rule Sets .....................................................................................................................10-23
Setting Up Cross-Currency Receipts .............................................................................................................10-24
System Options For Accounting....................................................................................................................10-25
Miscellaneous System Options Relating to Receipts....................................................................................10-26
Profile Options...............................................................................................................................................10-28
Agenda...........................................................................................................................................................10-30
Implementation Considerations for Receipts.................................................................................................10-31
Other Implementation Considerations for Receipts.......................................................................................10-32
Set Up Lockbox Integration...........................................................................................................................10-33
Function Security...........................................................................................................................................10-35
Summary........................................................................................................................................................10-36
Tax Accounting Process ..................................................................................................................................11-1
Tax Accounting Process ................................................................................................................................11-2
Objectives ......................................................................................................................................................11-3
Agenda...........................................................................................................................................................11-4
Order Management Global Taxes Overview .................................................................................................11-5
Receivables Global Tax Overview ................................................................................................................11-6
Other Products ...............................................................................................................................................11-7
Global Tax Overview ....................................................................................................................................11-8
Tax Overview ................................................................................................................................................11-10
Value Added Tax Overview ..........................................................................................................................11-11
US Sales Tax Overview.................................................................................................................................11-12
US Sales Tax Example ..................................................................................................................................11-13
Tax Partner Process Overview.......................................................................................................................11-14
Other Taxes in Oracle Applications...............................................................................................................11-16
Agenda...........................................................................................................................................................11-18
Tax Setup Steps .............................................................................................................................................11-19
Tax Setup Steps Continued............................................................................................................................11-20
Defining Tax Codes and Rates ......................................................................................................................11-21
Setting Up Inclusive and Exclusive Tax........................................................................................................11-23
Practice - Define a Tax Code.....................................................................................................................11-24
Solution - Define a Tax Code ....................................................................................................................11-25
Tax Groups Overview ...................................................................................................................................11-26
Setting Up Tax Groups (Optional).................................................................................................................11-27
Compound Tax Example ...............................................................................................................................11-28
Inclusive Tax with Compounding Example ..................................................................................................11-29
Defining Condition Sets ................................................................................................................................11-30
viii
Practice - Create a Tax Group....................................................................................................................11-31

Solution - Create a Tax Group...................................................................................................................11-32
Select a Tax Control Method.........................................................................................................................11-34
Setting Up Account Method (Optional).........................................................................................................11-36
Assigning Tax Codes to Items .......................................................................................................................11-37
Defining Tax Preferences, Defaults, and Rules .............................................................................................11-38
Defining Tax Exemptions..............................................................................................................................11-40
Defining Transaction Types ..........................................................................................................................11-41
Defining AutoAccounting for Tax.................................................................................................................11-42
Enabling Calculation of Tax on Freight ........................................................................................................11-43
Defining Tax Profile Options ........................................................................................................................11-44
For Order Management Profile Options ........................................................................................................11-45
Agenda...........................................................................................................................................................11-46
Tax Accounting Overview.............................................................................................................................11-47
Setting Up Tax Accounting for Deferred Tax ...............................................................................................11-48
Practice - Deferred Tax Codes...................................................................................................................11-49
Solution - Deferred Tax Codes ..................................................................................................................11-50
Defining Receivables Activities ....................................................................................................................11-52
Changing Tax Transactions ...........................................................................................................................11-53
Adjusting Tax on Invoices.............................................................................................................................11-54
Tax Credit Memo...........................................................................................................................................11-56
Agenda...........................................................................................................................................................11-57
Tax Reporting Ledger Overview ...................................................................................................................11-58
Tax Extract Overview....................................................................................................................................11-59
Sources of Data..............................................................................................................................................11-61
Tax Ledger Reporting Options ......................................................................................................................11-62
Matrix Reporting ...........................................................................................................................................11-63
RXi Report Steps ...........................................................................................................................................11-64
Modifying Attribute Sets ...............................................................................................................................11-65
Defining Summary Details ............................................................................................................................11-67
Publish RXi Reports ......................................................................................................................................11-68
Managing Access to RXi Reports and Attribute Sets ....................................................................................11-69
Summary........................................................................................................................................................11-70
Period Closing..................................................................................................................................................12-1
Period Closing Process ..................................................................................................................................12-2
Objectives ......................................................................................................................................................12-3
Period Closing Process ..................................................................................................................................12-4
Overview of Ordering to Period Closing.......................................................................................................12-5
Standard Reports ...........................................................................................................................................12-6
Reconciling Inventory Transactions ..............................................................................................................12-7
Reconciling Receivables Transactions, Receipts, and Customer Balances ...................................................12-8
Running Revenue Recognition ......................................................................................................................12-10
Transferring to the General Ledger ...............................................................................................................12-11
Running the Journal Import Program ............................................................................................................12-13
Mapping Receivables Transactions to General Ledger Categories ...............................................................12-14
Summary........................................................................................................................................................12-15
Appendix A Bank Reconciliation ...................................................................................................................13-1
Appendix A Bank Reconciliation ..................................................................................................................13-2
Course Objectives..........................................................................................................................................13-3
Agenda...........................................................................................................................................................13-5
Reconciliation Overview ...............................................................................................................................13-7
Reconciliation Integration .............................................................................................................................13-8
Oracle Receivables and Payables ..................................................................................................................13-9
Functions with Receivables ...........................................................................................................................13-10
Oracle General Ledger and Payroll ...............................................................................................................13-11
Reconciliation of Oracle Payroll EFT Payments ..........................................................................................13-12
ix
AutoReconciliation Overview .......................................................................................................................13-13

Load Bank Statements ...................................................................................................................................13-14
Agenda...........................................................................................................................................................13-15
Setting Up Oracle Cash Management and Related Products .........................................................................13-16
Practice - Set up a Bank Account ..............................................................................................................13-17
Setting Up Oracle Cash Management System Parameters ............................................................................13-21
Practice - Set up Classes and Payment Methods........................................................................................13-22
Setting Up Bank Transaction Codes..............................................................................................................13-25
Practice - Set up Bank Transaction Codes.................................................................................................13-26
Agenda...........................................................................................................................................................13-28
Bank Statement Open Interface .....................................................................................................................13-29
Importing Bank Statements ...........................................................................................................................13-32
Bank Statement Validation ............................................................................................................................13-33
Bank Statement Interface Errors....................................................................................................................13-34
Setup for Bank Statement Open Interface .....................................................................................................13-35
Agenda...........................................................................................................................................................13-36
Entering Bank Statements Manually .............................................................................................................13-37
Entering Bank Statement Information Manually...........................................................................................13-38
Agenda...........................................................................................................................................................13-39
Archiving and Purging...................................................................................................................................13-40
Archiving and Purging Automatically...........................................................................................................13-41
Bank Purging Program ..................................................................................................................................13-42
Agenda...........................................................................................................................................................13-43
Reconciling Bank Statements Automatically ................................................................................................13-44
Agenda...........................................................................................................................................................13-45
Reconciling Bank Statements Manually........................................................................................................13-46
Creating Miscellaneous Transactions ............................................................................................................13-47
Recording a Bank Transmission Error...........................................................................................................13-48
Recording Transactions from External Systems...........................................................................................13-49
Reconciliation Open Interface .......................................................................................................................13-50
Agenda...........................................................................................................................................................13-51
Manually Clearing and Unclearing................................................................................................................13-52
Practice - Enter, Format, and Approve Receipts........................................................................................13-53
Solution Enter, Format, and Approve Receipts ......................................................................................13-54
Clearing and Reconciling Transactions in Oracle Payables .........................................................................13-56
Clearing and Reconciling Transactions in Oracle Receivables ....................................................................13-57
Transferring Entries to Your General Ledger...............................................................................................13-58
Agenda...........................................................................................................................................................13-59
How to Record Exceptions ............................................................................................................................13-60
Handling NSF or Rejected Receipts Manually.............................................................................................13-62
Recording a Stopped Payment.......................................................................................................................13-63
Recording a Direct Debit from a Supplier .....................................................................................................13-64
Practice - Enter, Approve, and Pay Invoices .............................................................................................13-65
Entering Reversals.........................................................................................................................................13-68
Reconciling Corrections and Adjustments to Bank Errors ............................................................................13-69
Practice - Reconcile Bank Statements .......................................................................................................13-70
AutoReconciliation Matching........................................................................................................................13-73
Reversal Method............................................................................................................................................13-74
Adjustment Method .......................................................................................................................................13-75
Manual Reconciliation Matching ..................................................................................................................13-76
Agenda...........................................................................................................................................................13-77
Value Date Support .......................................................................................................................................13-78
Value Date Support in Oracle Payables and Oracle Receivables ..................................................................13-79
Value Date Derivation in Applications..........................................................................................................13-80
Selection Hierarchy for Value Date Support .................................................................................................13-81
Business Benefits of Value Date Support......................................................................................................13-82
Agenda...........................................................................................................................................................13-83
Oracle Cash Management Reports ................................................................................................................13-84

Archive/Purge Bank Statements Report ........................................................................................................13-85
AutoReconciliation Execution Report ...........................................................................................................13-86
Bank Statement Detail Report .......................................................................................................................13-87
Bank Statement Summary Report .................................................................................................................13-88
Bank Statements by Document Number Report...........................................................................................13-89
GL Reconciliation Report..............................................................................................................................13-90
Cash in Transit Report...................................................................................................................................13-91
Cleared Transactions Report..........................................................................................................................13-92
Transactions Available for Reconciliation Report........................................................................................13-93
Batches Available for Reconciliation Report ................................................................................................13-94
Bank Transaction Codes Listing....................................................................................................................13-95
Summary........................................................................................................................................................13-96
11i Receivables Fundamentals Supplemental Student Practices.................................................................14-1
11i Receivables Fundamentals Supplemental Student Practices ...................................................................14-2
Objectives ......................................................................................................................................................14-3
Setup..............................................................................................................................................................14-4
Practice - Create a New Employee (Required) ..........................................................................................14-5
Practice - Create a New User (Required)...................................................................................................14-7
Manage Parties and Customer Accounts .......................................................................................................14-10
Practice - Create a Profile Class (Required) ..............................................................................................14-11
Practice - Enter a Standard Customer (Required)......................................................................................14-14
Practice - Enter a Quick Customer (Required) ..........................................................................................14-18
Practice - Create a Customer Relationship (Required) ..............................................................................14-19
Practice - Submit Customer Related Reports (Optional) ...........................................................................14-21
Process Invoices ............................................................................................................................................14-24
Guided Demonstration - Open Receivables Periods (Required)................................................................14-25
Guided Demonstration - Review a Transaction Source (Required)...........................................................14-26
Guided Demonstration - Review a Transaction Type (Required)..............................................................14-27
Guided Demonstration - Review AutoAccounting Setup (Required)........................................................14-28
Practice - Enter a Manual Invoice (Required) ...........................................................................................14-29
Practice - Enter an Invoice with Standard Memo Lines (Required) ..........................................................14-31
Practice -Copy Invoices (Required)...........................................................................................................14-33
Practice - Enter an Invoice with a Bill in Arrears Invoicing Rule (Required) ...........................................14-36
Guided Demonstration - Run Revenue Recognition (Required) ...............................................................14-38
Correct Transactions......................................................................................................................................14-41
Practice - Enter a Debit Memo for Missed Freight (Required)..................................................................14-42
Practice - Update an Invoice (Required)....................................................................................................14-44
Practice - Create a Write-Off Adjustment (Required) ...............................................................................14-45
Practice - Issue a Credit Memo Against a Specific Invoice (Required).....................................................14-48
Practice - Create an On-Account Credit (Required) ..................................................................................14-50
Practice - Apply an On-Account Credit to an Invoice (Required).............................................................14-52
Process Commitments ...................................................................................................................................14-54
Guided Demonstration - Update the Deposit Transaction Type (Required)..............................................14-55
Practice - Enter a Deposit (Required) ........................................................................................................14-56
Practice - Apply Invoices Against the Deposit (Required)........................................................................14-57
Print Invoices, Statements and Reports .........................................................................................................14-60
Practice - Print Selected Invoices (Optional).............................................................................................14-61
Practice - Print Statements (Optional) .......................................................................................................14-62
Practice - Print Invoice Related Reports (Optional) ..................................................................................14-63
Process Invoices Using AutoInvoice .............................................................................................................14-66
Demo - Create a Sales Order and Generate an Invoice (Required) ...........................................................14-67
Manual Receipts ............................................................................................................................................14-72
Practice - Enter a Manual Receipt Batch (Required).................................................................................14-73
Practice - Enter a QuickCash Receipt Batch and Post Quick Cash (Required) .........................................14-75
Practice - Enter a Miscellaneous Receipt (Required) ................................................................................14-77
xi
Practice - Reverse a Receipt (Required) ....................................................................................................14-78

Practice - Apply an Unidentified Receipt (Required) ................................................................................14-79
Practice - Reverse and Re-Apply a Receipt (Required).............................................................................14-80
Practice - Print Receipt Related Reports (Optional) ..................................................................................14-82
xii
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
Thorough knowledge of the overall Oracle Receivables Process
Ability to navigate Oracle Applications
Prerequisites
11i E-Business Suite Essentials for Implementers
How This Course Is Organized

11i Oracle Receivables Fundamentals is an instructor-led course featuring lecture and hands-on
exercises. Online demonstrations and written practice sessions reinforce the concepts and skills
introduced.
xiii
Related Publications
Oracle Publications
Title
Part Number
Oracle Receivables Users Guide
A-15467
Additional Publications
System release bulletins
Installation and users guides
Read-me files
International Oracle Users Group (IOUG) articles
Oracle Magazine
xiv
Typographic Conventions
Typographic Conventions in Text
Convention
Bold italic
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Arrow
Brackets
Commas
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Plus signs
Key combinations
Italic
Quotation
marks
Uppercase
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.
For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
This subject is covered in Unit II, Lesson 3, Working with
Objects.
Use the SELECT command to view information stored in the

LAST_NAME
column of the EMP table.
Select File > Save.
Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]
xv
Typographic Conventions in Code

Convention
Caps and
lowercase
Lowercase
Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
DROP USER scott

IDENTIFIED BY tiger;
OG_ACTIVATE_LAYER
(OG_GET_LAYER (prod_pie_layer))
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
Syntax variables
CREATE ROLE role
SQL commands and SELECT userid

FROM emp;
functions
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
(M) From the menu, select Query then Find.
3.
(B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab
xvi
Typographical Conventions in Oracle Application Help System Paths

This course uses a navigation path convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example
(Help) General Ledger > Journals > Enter Journals
represents the following sequence of actions:
1.
In the navigation frame of the help system window, expand the General Ledger entry.
2.
Under the General Ledger entry, expand Journals.
3.
Under Journals, select Enter Journals.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.
xvii
xviii
Order to Cash Lifecycle

Overview
Chapter 1
Copyright Oracle, 2005. All rights reserved.
Order to Cash Lifecycle Overview
Chapter 1 - Page 1
Chapter 1 - Page 2
Objectives
Chapter 1 - Page 3

The ordering process leads to the shipping of goods which continues with invoicing the
customer and concludes with the receipt of cash and reconciling of the bank statement. All
orders do not follow this path, there may be some deviations in order processing.
In Order Management the order is entered with information including: customer, ship-to, billto, payment terms, order type, price list, unit price, and warehouse. Then the order is booked
and it goes through the workflow process. Credit Checking is also done. If it is a shipping item
and the quantities are available, it goes through shipping execution.
In Shipping Execution the order is pick released which generates the move order. Once the
item is brought from the sub-Inventory into the staging area it is ready to be placed on a
shipping vehicle. Now you can run the ship confirm process.
AutoInvoice is a concurrent program that imports invoices, credit memos, and onaccount
credits from other systems to Oracle Receivables. In Receivables you can print the invoice and
send it to the customer. You can proceed with collection efforts until you receive payment and
post your receipt.
In Cash Management the system pulls information from posted receipts and matches them to
the bank statement for reconciliation.
Chapter 1 - Page 4
Order Lifecycle
Order Lifecycle
Ordering: Entering the order, pricing the order, booking the order, reviewing credit if the order
exceeds the credit limit, scheduling (which can include checking ATP, placing demand, and
reserving on-hand Inventory), running pick release, and shipping the order.
Collecting: Running AutoInvoice, generating invoices, collection efforts, and receipt of
payments.
Accounting: Receipt information which is available to be used by Cash Management to
reconcile the bank statement and transferring accounting information to the General Ledger.
Chapter 1 - Page 5
Overview of Application Integration
Overview of Application Integration

Order Management receives customer information from the Customer Master which can
supply default information into the sales order.
Orders may come in directly from the CRM Suite of applications.
Order Management uses credit limits set by Credit Management to determine if the order
should be released or placed on credit hold for review.
Once the order has been booked, information can flow to the Shipping application if it is a
shippable item.
Inventory supplies item information for the sales order and receives reservation and demand
information.
Pricing supplies information for the list price and any modifiers to apply against the list price.
Order management then sends information to Receivables through AutoInvoice.
Now it can be printed and sent to the customer for payment.
Finally the accounting information is sent to the General Ledger. The receipt information can
also be accessed by Cash Management in order to reconcile the bank statements.
Chapter 1 - Page 6
Order Management Process
Order Management Process

Orders can be created from a number of different sources. You can create new orders by
entering the information or by copying existing orders. You can also bring orders in from EDI,
CRM, and other interfaces.
Chapter 1 - Page 7
Viewing and Managing Orders
Managing Orders and Lines

Once orders are in the system you can view them from different sources. Then you can manage
the orders and order lines by applying holds, removing holds, entering individual or mass
changes, creating copies, or making cancellations.
Chapter 1 - Page 8
Scheduling Process
Chapter 1 - Page 9
Pricing Process
Pricing Process
The pricing engine supplies the initial unit price from a price list or customer agreement. It will
also apply any modifiers for which the order qualifies. Modifiers can either raise or lower the
initial unit price. They can be set to be applied manually or automatically. They can also be set
to only be applied after certain events like saving, booking, or shipping.
Chapter 1 - Page 10
Shipping Process
Shipping Process
When the item is ready, it is pick released.
This creates the move order which can automatically detail where to get the item.
The items are brought from Inventory to the staging area.
The pick confirmation process in the system can automatically occur when you run pick
release.
Once the items are loaded on the truck from the staging area you can run the ship confirm
process.
When you run the ship confirm process the system can decrement Inventory and update
the sales order.
The information can then be transferred through AutoInvoice to Receivables for
invoicing the customer.
Chapter 1 - Page 11
AutoInvoice Process
AutoInvoice Process
Transaction data can be sourced from a number of locations for example: Order Management,
Contracts or legacy systems.
When the data is brought into the Interface Tables, errors are pushed to the Interface
Exceptions Table to be corrected.
Correct data gets pushed into Receivables by AutoInvoice program can be related to debit
memos, memos, and as invoices.
AutoInvoice Exceptions: Errors are sent to the Interface Exceptions Table where they can be
corrected. Once the lines are corrected, AutoInvoice can be rerun and invoices created from the
corrected lines.
Chapter 1 - Page 12
Receivables Process
Chapter 1 - Page 13
Cash Management Process
Cash Management Process

The final step of the process is to post entries to the General Ledger. The entries travel from
Cash Management to Receivables and then to the General Ledger.
Chapter 1 - Page 14
Summary
Chapter 1 - Page 15
Chapter 1 - Page 16
Overview of Oracle
Receivables Process
Chapter 2
Overview of Oracle Receivables Process
Chapter 2 - Page 1
Chapter 2 - Page 2
Objectives
Chapter 2 - Page 3
Chapter 2 - Page 4
Overview of Receivables in the Order to Cash Process
Overview of Receivables in the Order to Cash Process

Receivables can generate transactions from imported data brought through the AutoInvoice
program from Oracle Order Management, Oracle Service, Oracle Projects, Leasing, and legacy
systems. Transactions may also be created manually in the Receivables application. After
being completed the transaction information is ready to be transferred to the General Ledger.
Receipts that have been entered and remitted are available to be used by Cash Management to
reconcile bank statements. Receipts are available to be transferred to the General Ledger after
they are entered and saved.
Chapter 2 - Page 5
Overview of the Receivables Process
Overview of the Receivables Process

Note: Transfer to GL can happen at any time for any complete transaction, you do not have to
wait until you get a receipt or print and send invoices.
The transactions are created either by importing them or by manually creating them. The
transactions can then be reviewed and corrected before being completed. Once completed, they
are ready to be printed and sent to the customer for payment. However, there is a system option
Allow Changes to Printed Transactions, which will allow the correction of printed transactions
as well. Then the transactions go through the collection process. Once collected, the receipts
are enter and applied. The transactions can be transferred to the General Ledger once they are
completed. Finally, the receipts can be transferred once they are completely entered.
Chapter 2 - Page 6
Overview of Receivables Integration
Chapter 2 - Page 7
Receivables Integration Process
Overview of Receivables Integration

Inventory item information is available to Receivables for any manually created transactions,
although no inventory is decremented from any transactions created or modified in
Receivables. Transactions can be created by importing data from Order Management (which
may include orders from the CRM Suite of products), other applications and legacy systems.
Receivables sends accounting information to the General Ledger. Receipts are available for
bank reconciliation in Cash Management.
Once collected, the receipts are entered and applied. The transactions can be transferred to the
general ledger once they are completed. The receipts can be transferred once they are entered
and saved.
Chapter 2 - Page 8
Overview of the Transaction Process
Overview of the Transaction Process

Transactions can be copied in Receivables. A standard transaction would follow the path of
being reviewed, corrected, completed, printed, and sent to the customer. A receipt would be
entered against the transaction. The accounting information would be transferred to the General
Ledger after the transaction was completed.
Chapter 2 - Page 9
Overview of Other Invoice Operations
Overview of Other Invoice Operations

You can use an invoice to make copies. This process can be applied for invoices which will be
the same over a period of time.
Invoices can be created with or without rules. Invoices with rules can be imported or manually
created. The accounting rule indicates when revenue recognition should take place. The
invoicing rule indicates whether to bill in advance (the first period) or to bill in arrears (the last
period).
You can let your customers make invoice payments in multiple installments by using a split
payment term. When you assign a split payment term to an invoice, Receivables automatically
creates the payment schedules based on the invoice date and the payment terms that you
define. For example, your split payment term might specify that 40 percent of the invoice is
due in 30 days after the invoice date with the remainder due in 60 days.
Chapter 2 - Page 10
Overview of Adjustments
Overview of Adjustments
Adjustments are entered into the system and proceed through a validation process before being
approved. Adjustments can increase or decrease the remaining balance. Each user can have a
different approval limit. If the adjustment is within the approval limit it is automatically
approved. If it exceeds the approval limit it is placed in a pending status until approved by a
user with the appropriate approval limit.
Manual adjustments are created against one transaction. You select the transaction you want to
be adjusted.
Automatic adjustments can be made against a group of transactions. You set criteria options to
limit which transactions are selected by the system to be adjusted.
Chapter 2 - Page 11
Overview of Credit Memos
Overview of Credit Memos

You use the Credit Transactions window to enter, update, and review credit memos against
specific invoices, debit memos, or commitments.
You create credit memos to reduce the balance due for a transaction. When you credit a
transaction, Receivables creates the appropriate accounting entries and reverses any sales credit
assigned to your salespeople.
Receivables lets you credit an entire invoice or specific invoice lines.
You can also credit freight for an entire invoice or only for specific invoice lines. You can
delete an incomplete credit memo if the system option Allow Invoice Deletion is set to Yes.
A transaction must be complete before you can create a credit memo against it.
Note: The Line fields show amounts without tax, even if the transaction you are crediting is
tax inclusive. These include the Amount, Original, and Balance Due fields.
Chapter 2 - Page 12
Overview of the AutoInvoice Process
Overview of the AutoInvoice Process

Invoice data can be sourced from a number of locations for example: Order Management,
Contracts, and legacy systems.
When the data is brought into the interface tables, error messages are displayed in the interface
exceptions table.
Correct data gets pushed into Receivables as invoices.
AutoInvoice Exceptions: Errors are sent to the interface exceptions table where they can be
corrected. Once corrected, they can be processed into invoices.
Chapter 2 - Page 13
Overview of Receipts and Remittances
Overview of Receipts and Remittances

Receipts can be entered in one of three ways:
Manual: Which includes cash and miscellaneous receipts.
QuickCash: Which includes cash and AutoLockbox.
Automatic: Which includes credit cards, bills of exchange, direct debits, and ACH bank
account transfers.
Remittances are a group of receipts remitted to the same bank and bank account, similar to
bank deposit tickets.
Receipts that are applied to an invoice or customer account can be reversed or reapplied at any
time as long as they have not been purged from the system.
Note: Once entered and saved the receipt information can be transferred to the General Ledger.
They do not have to be reconciled or applied to an invoice.
Chapter 2 - Page 14
Overview of Collections
Overview of Collections
Identify past due items by reviewing information online and printing collections reports.
Contact the customer by sending statements, dunning letters or by a telephone call. Record the
customer contact activity and resolve any disputed items. Apply adjustments and record bad
debt.
Chapter 2 - Page 15
Overview of Tax
Overview of Tax
Oracle provides the ability to tailor the tax engine to the specific needs of your business.
Receivables is the application where final taxing occurs, all other applications that use the tax
tables supply an estimated tax.
Chapter 2 - Page 16
Oracle iReceivables
Oracle iReceivables Overview

Customers can perform extensive inquiries, dispute bills, pay invoices, and review account
balances. Bill disputes are automatically routed and processed, eliminating the need for
intermediaries or paper-based claims management, allowing companies to save money, reduce
processing time and improve customer service.
All transactions accessible via Oracle iReceivables are protected by Oracles standard SelfService Web applications security.
The intuitive user interface provides you with simple and effective access to Receivables data.
The practical, Web-based look and feel, is consistent with other Oracle Self-Service
applications, and offers distinct navigation indicators and a new step-by-step process flow.
Chapter 2 - Page 17
Oracle iReceivables Product Integration
Oracle iReceivables Product Integration

Oracle Receivables
for real-time transaction status and details
Oracle Trading Community Architecture
for real-time account access and customer information
Oracle iPayment
for online payment application and processing
Oracle Workflow
for automated credit memo and multi-print processing
Oracle Application Framework
for personalized display of account information
Oracle Bill Presentment Architecture
for customizable bill presentment templates
These are the products Oracle iReceivables integrates with. First, Oracle iReceivables
integrates with Oracle Receivables to provide real-time transaction status and details. Oracle
Chapter 2 - Page 18
iReceivables also integrates with Oracle Trading Community Architecture to provide real-time
account access and customer information. Oracle iReceivables integrates with Oracle
iPayment to enable online payment application and processing. Oracle iReceivables also
integrates with Oracle Workflow to provide automated credit memo and multi-print
processing. Oracle iReceivables integrates with Oracle Oracle Application Framework to
enable personalized display of account information. Lastly, Oracle iReceivables also integrates
with Bill Presentment Architecture, which provides customizable bill presentment templates.
Chapter 2 - Page 19
Overview of Oracle iReceivables Features
Overview of Oracle iReceivables Features

Anonymous User Login
The Anonymous User Login feature allows external customers to log in by only entering
an account number. Customers can access their customer account data without having to
register for a username and password. Companies can customize this feature to take the
users directly to the page they need to access the most, for example, the Account Details
page or the Home page.
One-Time Credit Card Payment
The One-Time Credit Card Payment feature allows the customers to make payments by
credit card on a one-time basis. The credit card information entered by customers is
immediately passed on for payment processing. After payment processing, the credit
card information is masked both in the database and on the payment page.
Service Charge
Using this feature, companies can apply service or convenience charges to the customer
payments made in Oracle iReceivables. Oracle iReceivables records the service charge
as an adjustment to the invoice. If the processing of online credit card payment incurs
Chapter 2 - Page 20
additional costs, companies can transfer these costs to their customers by applying
service charges to the customer payments.
Pay All Open Invoices
With this feature, customers can pay all their open invoices at the same time. This
feature expedites the payment process especially for those customers who have a limited
number of bills. For example, a patient may only have two or three health care bills
outstanding. The patient can just log into Oracle iReceivables and pay all of them with
one click.
Multi-Pay
The Multi-Pay feature allows the customers to select multiple invoices and pay all of
them at once using credit card or bank account transfer. The selected invoices will be
paid by one receipt and the receipt will record multiple applications to the paid invoices.
Multi-Print
The Multi-Print feature allows customers to select multiple invoices and print all of them
at once. The print format is defined in Oracle Receivables, including PDF, HTML, text,
XML, PostScript, and others. Once the print job is completed, the customers will receive
an e-mail notification containing the print request ID. Customers can enter the print
request ID in the Home page to retrieve the printed documents.
Custom Transaction Search
Using the Custom Transaction Search feature, companies can add their own custom
search-by attributes for transaction search in the Account Details page. For example, a
shipping company can allow its customers to search transactions by shipping attributes
such as service contract number or container number, in addition to the seeded search
attributes in Oracle iReceivables.
Custom Customer Search
With the Custom Customer Search feature, companies can add their own custom searchby attributes to search for customer accounts in the Customer Search page. The
customized search attributes can be added to the Search By choice lists. External
customers can use these extended attributes to search for transactions and their accounts
in the Customer Search page.
Display of Descriptive Flexfields
This feature allows the external customers to view descriptive flexfields in multiple pages
in Oracle iReceivables, including the Account Details, Invoice, and Payment pages. The
Account Details page displays the transaction-specific descriptive flexfields. The Invoice
and Payment pages display the invoice line-specific descriptive flexfields. The Payment
page displays the receipt-specific descriptive flexfields. Display of Descriptive
Flexfields has multiple benefits. First, companies can customize the flexfields to store
more transaction-specific information. Secondly, customers can view such information
through flexfields displayed in Oracle iReceivables. For example, an airline company
can display additional flight information associated with the airline charges, such as flight
number, arrival time, and departure time. This will help the customers to recognize the
charges more easily. As a result, the customers will pay their invoices faster.
Export
Chapter 2 - Page 21
The Export feature allows customers to export columns from the Account Details page in
the comma delimited format. Customers can also export the columns Invoice, Debit
Memo, Deposit, Chargeback, Credit Memo, Payment, and Credit Request pages. After
exporting the data, customers will be able to open it up in other applications such as
Microsoft Excel to conduct further analysis on their billing information.
Commitment Balance
Commitment or deposit is a common business practice for many companies. First,
customers make a prepayment, which is recorded as a commitment or deposit in Oracle
Receivables. Customers can then draw on this commitment as a line of credit to pay for
the purchases. When such a purchase is made, companies create an invoices against the
commitment and the commitment balance will be deducted accordingly. Oracle
iReceivables allows the customers to view their commitment details, the invoices applied
against the commitment, and the commitment balance online.
Duplicate Dispute Warning
When a user disputes on an invoice that has been previously disputed, Oracle
iReceivables will present the user with a warning before before the user can proceed with
the dispute process. The warning page intends to reduce the error of duplicate disputes.
Attachment
The Attachment feature allows the external customers to view and create attachments in
the Account Details and Invoice pages. With this feature, customers can easily view
existing attachments or add new attachments online. This enriches the information
available to both the customers and internal staff such as AR, collections, or customer
service representatives. As a result, companies can interact with their customers in a
more informed fashion. For example, lets say a customer wants to dispute an invoice
because the invoice data is inconsistent with the original purchase order. In this case, the
customer can attach the purchase order image to the invoice, and then make a note in the
dispute page to ask the collector to review this attachment. The collector, after receiving
the dispute, can review the attached purchase order and approve the dispute right away,
without having to ask the customer to e-mail or fax the purchase order to him. This saves
time for both parties and helps to resolve the dispute more quickly.
Chapter 2 - Page 22
Summary
Chapter 2 - Page 23
Chapter 2 - Page 24
Manage Parties and

Customer Accounts
Chapter 3
Manage Parties and Customer Accounts
Chapter 3 - Page 1
Chapter 3 - Page 2
Objectives
Chapter 3 - Page 3
Agenda
Chapter 3 - Page 4
Customer Overview
Customer Overview
A customer account represents the business relationship that a party can enter in to with
another party. The account has information about the terms and conditions of doing business
with the party. For example, you could open a commercial account for purchases to be made
by Vision Distribution for its internal use and a reseller account for purchases made by Vision
Distribution for sales of your products to endusers.
You can create multiple customer accounts for a party to maintain information about categories
of business activities. For example, to track invoices for different types of purchases, you can
maintain an account for purchasing office supplies and another account for purchasing
furniture.
You can also maintain multiple customer accounts for a customer that transacts business with
more than one line of business in your organization. You maintain separate customer profiles,
addresses, and contacts for each customer account.
A contact communicates for or acts on behalf of a party or customer account. A contact can
exist for a customer at the account or address level. A person usually acts as a contact for an
organization, but can also be a contact for another person. For example, an administrative
assistant could be the contact for an executive.
Chapter 3 - Page 5
Party Model Overview
Party Model Overview

The party model flows through the entire e-Business Suite. There is just one record to represent
both a prospect and a customer. The entity itself is recorded, such as a person or an
organization. However, customer terms are established, that record represents a prospect. Once
customer terms are recorded, that same record now represents the entity as your customer. So,
there are no separate lists to maintain and reconcile. In the Oracle e-Business Suite, there is one
record to represent Company ABC throughout its full life-cycle.
Each application uses different features of the party model. For instance, the Customer
Relationship Management Suite (CRM) applications use more details about party relationships
and new prospects. The Receivables and Order Management applications use more of the
customer accounts including payment terms, billing, and shipping information.
The party model contains a unique set of information about a person, organization, or
relationship. The tables store information such as parties, addresses, and bank accounts.
You are able to interact with the party model through the following:
Customer forms: Online entry and query of party and customer account information.
Party interface: Batch load of party information.
Chapter 3 - Page 6
Party and customer account merge: Merge parties and customer accounts. This
functionality is used after entering a party incorrectly, in duplicate, or due to a business
consolidation.
Chapter 3 - Page 7
Party Model
Party Model
A party is an entity that can enter into business relationships. A party is defined by information
about that party, not its relationships. For example, the name Vision Corporation is part of
the definition of a party with the Organization party type.
A relationship is defined by the characteristics or terms and conditions of that relationship. For
example, the attribute Marital Status is part of the definition of the Spouse of relationship.
The definition of a party is independent of its relationships. For example, a party, John
Smith, with the Person party type exists independent of any relationship entered by John
Smith.
A party site links a party with a location, indicating that partys usage of the location. This
location can be a customer account site which would be used within the context of a customer
account for business purposes like billing and shipping.
A location is a point in geographical space described by a street address.
A party relationship is a binary relationship between two parties like a partnership.
A contact point is means of contacting a party. For example, a phone number, e-mail address,
or fax number.
Chapter 3 - Page 8
Party Model and Relationships
Party Model and Relationships

The party model has tables that store party information about people or organizations and any
relationships between these parties.
A party is anything that can enter into a business relationship with another party. The party can
be an organization, a person or a relationship. This allows you to store information about your
relationships in one representation of people and businesses.
The party registry stores information about relationships between parties, such as:
Organizational hierarchies
Business relationships
Personal relationships
Organization contacts
In addition to the original relationship, the party registry stores the reciprocating data for the
relationship for example:
Marla is a Customer of the Phone Company. Relationship information about Marla:
Marla is an Employee of Business World. The Business World record also indicates it is
an Employer of Marla (Business Relationship)
Chapter 3 - Page 9
Marla is the Spouse of John. Johns record indicates he is the Spouse of Marla. (Personal
Relationship)
Marla is Related to Digital Image Corporation. Digital Images record indicates it is
Related to Marla.
Chapter 3 - Page 10
Party Model Components
Party Model Components

The party model in Release 11i allows you to enter a party as an organization or person and
then create party relationships.
In Release 11 the party definition was simply defined as a customer and the party relationship
as a party could not be defined.
Chapter 3 - Page 11
Managing Parties
Managing parties
When managing parties, you can:
Create customer account profile classes
Assign profile classes to customer accounts
Create and maintain party information
Define relationships between parties and between customer accounts. (Both reciprocal
and non-reciprocal)
Merge parties and customer account information
Review party and customer account information online and in reports
Chapter 3 - Page 12
Party Sites
Party Sites
Party sites are global but do not default in under different operating units. They are visible
under the original operating unit in which they were entered. To access them from other
operating units, you would query for that customer under the Site Number field and pick that
site from the list. After this is done, the address information will be available and can be shared
under the same site number.
Chapter 3 - Page 13
Customer Accounts
Customer Accounts
Information held in the registry level is universally true. It is independent of relationships.
Information held in the customer account level is about your business relationship. It is for
items like payment terms and billing preferences.
The financial rollup point is an account. It tracks the monetary portion of a partys purchases
and payments.
Party information is separate from the information about the relationships of the party. The
party model separates information about the organization or person party from the terms of the
relationship.
Additionally, the party model allows you to establish multiple relationships (also known as
party accounts) with the same organization or person party .
Addresses work in a similar fashion. You record an address for an organization or person once,
then reference it within the customer account layer, through the customer account site entity.
Chapter 3 - Page 14
Integrating Party Information
Integrating Party Information

You can enter party information directly into Oracle Applications, or import it through
interface tables.
Party information is shared throughout the E-Business Suite. The tables for the Customer
Master, however, are owned by the Trading Community Architecture.
In the ERP, specifically Receivables and Order Management, the terms Customer and
Customer Number are used. In the Customer Relationship Management Suite (CRM) the terms
used are Account and Account Id. Even though different terms are used, they are linked to the
same record in the table.
Chapter 3 - Page 15
Data Quality Management Overview

The DQM features in the Customers Workbench lets you:
Perform advanced searches for parties and customer accounts with userdefined criteria
in the Search Criteria window.
Prevent duplicate entries by determining if the customer account that you are creating or
updating is a potential duplicate of any existing account.
DQM must be set up to enable these features in the Customers Workbench. For example, if
DQM is not set up, the Find/Enter Customers window appears instead of the Search Criteria
window.
Chapter 3 - Page 16
Agenda
Chapter 3 - Page 17
Profile Classes
Profile Classes
Receivables, Vision Operations (USA) or Order Management Super User, Visions Operations
(USA)
(N) Customers > Profile Classes
You use Customer Profiles to group customer accounts with similar credit worthiness, business
volume, and payment cycles. For each profile class you can define information such as credit
classifications, payment terms, statement cycles, invoicing, and discount information. You can
also define amount limits for your finance charges, dunning, and statements for each currency
in which you do business.
Define your standard customer profiles in the Customer Profile Classes window. These profiles
contain generic options that you can use to group your customers into broad categories.
For example, you might define three categories: one for prompt paying customers; one for late
paying customers with high finance charge rates; and a third for customers who mostly pay on
time, with discount incentives for early payment. You can also use the profile class
DEFAULT, which Oracle Receivables provides.
Chapter 3 - Page 18
You can assign a profile class to customers and addresses through the CustomersStandard
window. The customer profile class you assign provides the default values, which you can
optionally customize to meet specific requirements for each customer or address.
Chapter 3 - Page 19
Profile Class Characteristics
Profile Class Characteristics

Every customer account must be assigned to a profile class. A profile class defines several
default values for customer accounts with similar credit terms and invoicing requirements.
After an account has been created, the default values can be modified based on the specific
characteristics of that customer account or account site.
For example, you may want to create a profile class for small manufacturers, called Small
MFG. Customer accounts assigned to this profile class might require credit checks before
orders will be fulfilled, given Net 30 payment terms, and receive quarterly statements. When
creating a specific new customer account, you could assign that account to the Small MFG
profile class. If the customer account develops credit problems in the future, you might then
modify that accounts payment terms to Cash On Delivery.
Within the Order to Cash process flow, the applications involved use the credit checking
feature differently. Credit checking is not used in Receivables. Order Management (OM) and
Credit Management utilizes credit checking. Credit check rules determine when an order has
exceeded the credit limit and sends a request to Credit Management to initiate a credit review.
OM determines which rules (usually defined by receivables personnel) are used, and when they
will be applied via the OM Transaction Type on a sales order.
Chapter 3 - Page 20
Practice - Create a Customer Profile Class

Overview
In this practice you will create a customer profile class
Assumptions
If you are not attending training at an Oracle University or Authorized Partner

Education Center, you must have access to an Oracle Application Vision database or
comparable training test instance on which to complete this Practice.
Replace XX in the Practice with a unique identifier such as your initials or a number.
(For Instructor Led Training classes, this number will be assigned to you). This is
necessary in order to create unique records within the database when performing the
Practice.
Tasks
Create a new customer profile class: XX-New
Responsibility = Order Management Super User, Vision Operations (USA)
1.

Name: XX-New
Description (unnamed field): XX New
2.
Use the following information to define your profile class:

Collector: Pat
Payment Terms: 30 Net
Match Receipts By: Transaction Number
Auto Cash Rule Set: Standard
Remainder Rule Set: Standard
Charge Interest : Unchecked
Statement Cycle: Monthly (25th day of every month)
Tax Printing Method: Itemize and Sum
Dunning Letter Set: STANDARD
3.
Use the following information to specify limits in USD

Min Receipt Amount: 15.00
Min Statement Amount: 100.00
Min Dunning Amount: 50.00
Min Dunning Invoice Amount: 50.00
Credit Limit: 100,000.00
Order Credit Limit: 10,000.00
Chapter 3 - Page 21
Solution - Create a Customer Profile Class

Create a new customer profile class: XX-New
1.
Navigate to the Profile Classes window

Name: XX-New
Description (unnamed field): XX New
2.
(T) Profile Class

Collector: Pat
Payment Terms: 30 Net
Match Receipts By: Transaction Number
Auto Cash Rule Set: Standard
Remainder Rule Set: Standard
Charge Interest : Unchecked
Statement Cycle: Monthly (25th day of every month)
Tax Printing Method: Itemize and Sum
Dunning Letter Set: STANDARD
3.
Leave all other defaults
4.
(T) Profile Class Amounts

Currency: USD
Min Receipt Amount: 15.00
Min Statement Amount: 100.00
Min Dunning Amount: 50.00
Min Dunning Invoice Amount: 50.00
Credit Limit: 100,000.00
Order Credit Limit: 10,000.00
5.
(I) Save.
Chapter 3 - Page 22
Managing Customer Account Profiles
Managing Customer Account Profiles

You can move a customer account from one profile class to another whenever it is deemed
necessary. To change the profile class, find the account and then select the new profile class
from the list of values under the Profile Transactions tab in the Customer window. You can
also assign profile classes at the site level of the customer if there is a saved, and active Bill-To
business purpose.
You can change one or more attributes of a profile class for a specific customer account. This
is called customizing the account profile class. It does not change any of the profile class
attributes for other customer accounts that share the same profile class.
Note: It is a best practice to only set credit limits through Credit Management, so I wanted to
change the focus of these slides away from credit limits.
Chapter 3 - Page 23
Updating Profile Classes
Updating Profile Classes

You can modify attributes in existing profile classes even after customer accounts are assigned
to them. However, when you try to save your changes to any saved profile class, you must
decide how you want the change to be applied.
You can choose one of these three options:
Do Not Update Existing Profiles: Only the profiles of new customer accounts created in
the future will reflect the changes.
Update All Profiles: The attribute is updated in all customer accounts that use this
profile.
Update All Non-customized Profiles: Profile classes set the default values initially
assigned to individual customer account profiles. If an attribute in an individual party
profile was customized to be different from its profile class, changes to the value of a
profile class attribute do not change the customized value of the attribute in the individual
customer account profile.
Chapter 3 - Page 24
Reviewing Profile Class Changes
Reviewing Profile Class Changes

When changes to a profile class cause changes to customer account profiles, Receivables
automatically generates the Customer Profile Copy concurrent program to review the changes.
This is an auditing report that summarizes all the changes made to the profile class.
Chapter 3 - Page 25
Agenda
Chapter 3 - Page 26

Oracle Trading Community Architecture (TCA) Data Quality Management (DQM) provides
functionality to keep party and customer account information free of duplicates as well as to
perform powerful searches on that information.
DQM must be set up to enable these features in the Customers Workbench. For example, if
DQM is not set up, the Find/Enter Customers window appears instead of the Search Criteria
window.
Chapter 3 - Page 27
Data Quality Management (DQM)
Data Quality Management (DQM)

Many applications in Oracles E-Business Suite contribute data to the Trading Community
Architecture (TCA) registry about parties, addresses, contacts, and contact points. Each
application must also efficiently and consistently retrieve data for use in transaction processing.
Duplicate records reduce the efficiency of transaction processing and the effectiveness of
business intelligence tools and procedures.
Chapter 3 - Page 28
How Does DQM Work?
How Does DQM Work?

The DQM process requires a few steps to acquire data into a staged schema and then evaluate
the party information for duplicates or matches.
Party data is stored in the TCA Registry.
DQM cleanses and standardizes the data using a set of transformation functions. The
cleansed data is stored in the staged schema.
Input records enter the process from online search or run a duplicate identification
process.
DQM cleanses the input records using the transformation functions in the highly
configurable match rules.
DQM compares the cleansed input records to the information in the staged schema using
the match rule and calculates a matching score.
The result of the comparison performed by DQM is a list of potential matches and their
calculated scores.
For more information on DQM refer to the Data Quality Management Advanced Topic.
Chapter 3 - Page 29
Fuzzy Search
Fuzzy Search
The fuzzy search method uses word replacement rules to map a word, abbreviation, or special
character that might be entered by a user as a search criteria to a similar word, abbreviation, or
special character.
For example, if a user might enter Blvd as a search criteria for an address search, you could
create a Word Replacement rule to retrieve records that contain Boulevard. In the Word
Replacement rule, Blvd is referred to as the Original word and Boulevard is the
Replacement word.
Over 3,000 Original and Replacement word pairs are seeded for use with the fuzzy search
method. To ensure the accuracy of the first fuzzy search that any user performs, you must
create the keys that link the Original and Replacement words by running the Generate Key for
Fuzzy Search concurrent program.
In the customer find/enter window you can do a fuzzy search and get the following results:
Person first name, enter Jim to find James
Organization name, enter AT and T to find AT&T
Address, enter St to find Street
Chapter 3 - Page 30
Query Word Replacement
Word Replacement
Trading Community Manager
(N) > Setup > Word Replacements
To use the fuzzy search method you must create Word Replacement Rules in the Word
Replacements window.
The steps for a search are:
Select the Type of word to be replaced.
Enter a word, word fragment, character, or abbreviation that a user might enter as a
search criteria in the Original Word column. In the Replacement Word column enter text
that equates to the Original Word entry. Save the record.
In the Generate Keys region, select Name or Address from the list of values for the Table
field in the Generate Keys region.
Select the New Rows Only check box if you only want to generate keys for new customer
records.
Click the Generate Keys button to run a concurrent program which generates the fuzzy
keys used by the fuzzy search method.
Chapter 3 - Page 31
Entry Methods
Entry Methods
Customer Interface
The Customer Interface allows you to import and validate current or historical customer
information from other systems into the E-Business Suite.
Standard Entry
Enter detailed party/customer account information, assign an address location code, select a
primary Bill-To, select a primary Ship-To, and link a Ship-To business purpose with a Bill-To
business purpose.
Quick Entry
The quick entry method allows you to quickly select the business purposes for an address by
using check boxes. However, you do not have the ability to specify a location code, select a
business purpose as a primary Bill-To or a primary Ship-To, or link a Ship-To with a Bill-To.
You can add these features later for this party by using the Standard Customer form.
Sales Order form
You may also enter a new customer directly from the Sales Order screen.
Chapter 3 - Page 32
Business Issues
Business Issues
Before Entering Party and Customer Account Information:
Specify naming conventions such as capitalization and abbreviations.
Determine the usage of Automatic Numbering. The Automatic Customer Numbering and
Site Numbering system options and the Automatic Contact Numbering profile options
selections automatically number parties, site location codes, and contacts; or select the
manual numbering option.
Define how to use classifications to group customers for pricing functionality like using
qualifiers and for reporting purposes. Classifications include: Customer Class, Customer
Type, Sales Channel, Category, and SIC.
Consider if Use the Allow Payment of Unrelated Invoices system option to permit
payment of unrelated customers invoices is appropriate.
Decide how to set up decentralized parties with multiple sites: as one party with multiple
sites, or as multiple customers each with one site.
Chapter 3 - Page 33
Business Purposes
Business Purposes
Consider these issues before you set up multiple business purposes:
You must have a valid address for use during transaction entry in Order Management and
Receivables.
Only one site can be designated as the primary site for each business purpose. If there are
multiple business purposes you are able to have multiple primary designations.
If you designate a primary site for Bill-To or Ship-To, it will default into a transaction
automatically. However, you can select a different site from the list of values.
These are standard business purposes:
Bill-to
Invoices are sent here for payment.
Ship-to
Where the goods are shipped.
Dunning
Dunning letters are sent to this location.
Legal
The legal location, which serves as the government point of contact.
Statements
Statements are sent to this location.
Marketing
Marketing literature such as product announcements are sent here.
Chapter 3 - Page 34
Multiple Sites and Business Purposes: Centralized Example
Multiple Sites and Business Purposes: Centralized Example

In this example, ABC Companys Headquarters is in New York, and all billing information
will be received there. Products will be shipped to the Paris, Washington, and Chicago
customer account sites.
Chapter 3 - Page 35
Multiple Sites and Business Purposes: Decentralized Example
Multiple Sites and Business Purposes: Decentralized Example

In this example, all locations have the ability to pay the invoices for the goods they received.
Each site has a Bill-To and Ship-To business purpose established for its site. We would
recommend each of these to be a separate party.
Chapter 3 - Page 36
Interface Data Entry
Interface Data Entry

Receivables, Vision Operations (USA)
(N) Interfaces > Customer
When importing party information from external databases, the data flows into temporary
interface tables, then on to Oracle master tables within the Receivables module. A report can
be run to view this interface from the external database. Any errors can be corrected with
PL/SQL within the temporary tables.
Importing Customer Data
All Customer data that you enter in the customers windows can be imported using the customer
interface.
Import profile class information such as payment terms, statement, automatic receipt, finance
charge, dunning, and invoicing information.
Updating Data
If data is maintained in an external system, use the interface to update the information at
regular intervals.
Preparation for Import
Chapter 3 - Page 37
Prior to running the Customer Interface it is important to prepare the environment to accept the
new data you wish to import. In some cases imported data will have values that may have not
been defined during earlier setups. Examples of information that can be imported to the
Customer record include: Collectors, Customer Bank Information, Dunning Letter Sets, Freight
Carriers, Payment Terms and Lookups. For a complete listing see the Receivables Users
Guide. As the Customer Interface will not create these records, it is important to pre-define
theses elements for the import process to run smoothly.
Note: The Customer Interface will not create location combinations for foreign locations. A
foreign location is one where the country segment is not the same as the Default Country from
the Receivables System Options window.
Chapter 3 - Page 38
Using Standard and Quick Entry

Receivables, Vision Operations (USA) or Order Management Super User, Vision Operations
(USA)
(N) Customers > Standard
(N) Customers > Quick
The attributes above can be set at the Customer header record to default to all customer sites.
Chapter 3 - Page 39

Linking Bill-to and Ship-to Locations:
A Ship-To address can have an associated Bill-To address.
The associated Bill-To address becomes the default during invoice entry when the Shipto location is selected.
You are able to select the checkbox Identifying an Address for a party Business Purpose
The Location attribute in the Business Purposes tabbed region of the customer account
addresses window, provides a simple way to name or identify an address. This location value is
used in transaction entry, receipts entry, create/approve/ confirm automatic receipts and
remittances, orders, and returns windows. It is also the first value that will appear in the list of
values on these documents.
To have Oracle automatically number locations, you can use the Automatic Site Numbering
system option. If you select the system option check box, TCA will uniquely number all the
customer account locations.
Chapter 3 - Page 40
Practice - Create a Customer using the Standard Data Entry Form

Overview
In this practice you will create a customer using the standard customer entry form.
Assumptions

Practice.
Tasks
Create a new customer: XX-Big City, with two addresses
1.
Navigate to the Find/Enter Customers window

Name: XX-Big City
2.
Create customer XX-Big City with the following information:

Profile Class: XX-New
Class: High Technology
Sales Channel: Commercial
Price List: Corporate
3.
Enter address information according to the following table:

Field
Value
Country
United States
Address
102 N. LaSalle
City
Chicago
State
IL
Postal Code
60601
County
Cook
Chapter 3 - Page 41
4.
This address is a non-primary Bill To address:

Location: IL Chicago
5.
This address is the primary Ship To address. Invoices should be sent to the IL Chicago Bill
To location.
6.
Specify salesperson information:

Salesperson: Abbott, Ms. Rachel
7.
Specify default order information.

Order Type: Mixed
Warehouse: Seattle Manufacturing
8.
Specify contact information.

Last Name: Cooley
First: Peggy
9.
Add a second address entering address information according to the following table:
Field
Value
Country
United States
Address
487 Beverly
City
Palo Alto
State
CA
Postal Code
94301
County
San Mateo
10. This address is the primary Bill To address.

Location: CA Palo Alto
11. This address is a non-primary Ship To address. Invoices will be sent to the primary
location:
12. Specify salesperson information:
Salesperson: Nelson, Mr. Brian
13. Specify default order information.
Order Type: Mixed
Warehouse: XX-IO
Chapter 3 - Page 42
14. Specify contact information.

Last Name: Allen
First: Spencer
Chapter 3 - Page 43
Solution - Create a Customer using the Standard Data Entry Form

Create a new customer: XX-Big City, with two addresses
1.

Name: XX-Big City
2.
(B) Find
3.
(B) New
4.
(T) Classification
Profile Class: XX-New
Class: High Technology
Sales Channel: Commercial
5.
(T) Order Management

Price List: Corporate
6.
(T) Addresses
7.
(B) New
8.

Field
9.
Value
Country
United States
Address
102 N. LaSalle
City
Chicago
State
IL
Postal Code
60601
County
Cook
(T) Business Purpose

Usage: Bill To
Primary: Unchecked
Chapter 3 - Page 44
10. (I) Save

11. (I) New Record
Usage: Ship To
Bill To Location: IL Chicago
Primary: Checked
12. (B) Open
13. (T) Details
Salesperson: Abbott, Ms. Rachel
14. (T) Order Management
Order Type: Mixed
Warehouse: Seattle Manufacturing
15. (I) Save, return to Customer Address form.
16. (T) Contacts: Telephones
Last Name: Cooley
First: Peggy
17. (I) Save
Place cursor in Country field at top of form
18. (I) New Record

Field
Value
Country
United States
Address
487 Beverly
City
Palo Alto
State
CA
Postal Code
94301
County
San Mateo
19. (T) Business Purpose

Usage: Bill To
Primary: Checked
20. (I) Save
Chapter 3 - Page 45
21. (I) New Record

Usage: Ship To
Bill To Location: CA Palo Alto
Primary: Unchecked
22. (B) Open
23. (T) Details
Salesperson: Nelson, Mr. Brian
24. (T) Order Management
Order Type: Mixed
Warehouse: XX-IO
25. (I) Save, return to Customer Address form.
26. (T) Contacts: Telephones
Last Name: Allen
First: Spencer
27. (I) Save
Chapter 3 - Page 46
Differences Between Standard and Quick Entry
Note: You are able to update information entered via the Quick Customer Entry form using the
Standard Customer Entry form. The data entered via either form updates the same tables. The
constraints are based upon the form, not the data.
Chapter 3 - Page 47
Practice - Create a Customer using the Quick Data Entry Form

Overview
In this practice you will create a customer using the quick customer entry form.
Assumptions

Practice.
Tasks
Create a new customer: XX-Quick
1.
2.
Name your customer XX-Quick and specify address information according to the following
table:
Field
3.
Value
Country
United States
Address
888 Market
City
San Francisco
State
CA
Postal Code
94100
County
San Francisco
This site will be both a Bill To and a Ship To site
Chapter 3 - Page 48
Solution - Create a Customer using the Quick Data Entry Form

Create a new customer: XX-Quick
1.

Name: XX-Quick
(B) Find
(B) New [for creating new customer]
2.
(T) Address
3.
(B) New [for creating new address]
4.

Field
Value
Country
United States
Address
888 Market
City
San Francisco
State
CA
Postal Code
94100
County
San Francisco
5.
(T) Business Purpose

Bill To: Checked
Ship To: Checked
6.
(I) Save
Chapter 3 - Page 49
Dun & Bradstreet (D&B) Integration
Dun & Bradstreet (D&B) Integration

The integration of Dun & Bradstreet (D&B) data products with Oracle Applications provides
on-line and batch processes that you can use to acquire and review customers demographic,
corporate relationship, financial, and credit risk data. Access to D&B data is available from
the credit application in Credit Management for new prospects or to update data for an existing
customer.
You can search for and purchase D&B information on specific companies from D&Bs
database of more than 60 million businesses worldwide. The information obtained from D&B
can be updated or expanded during future online sessions or by using the batch loading
process.
Chapter 3 - Page 50
D&B Data Formats
D&B Data Formats

The D&B data is available in the form of Global Data Products (GDP) files and BIR reports
that contain a wide variety of data elements.
For example, the Enterprise Management GDP provides detailed demographic, corporate
structure, risk, and financial information for integration with Oracle Applications. These D&B
data files contain data elements you can use to improve risk assessment procedures, make
better informed credit decisions, and improve customer acquisition and retention. Enterprise
Management includes the most complete set of data, scores, and ratings available about your
trading community.
The Business Information Report (BIR) provides many of the data elements from the D&B
database in a standard format. You can order a BIR, store an image of the report in your
database, and view the report whenever necessary. The BIR is stored in the Organization
Profiles table, so that historical information about BIRS can be maintained.
Chapter 3 - Page 51
D&B Online
D&B Online
Information can be purchased and retrieved from D&B for parties (organizations or persons)
that are prospects or that have an existing account. When you obtain D&B information about a
company that does not exist in your database, a new party is created using the D&B data.
To obtain D&B information for a party you may follow one of several scenarios:
If the party already exists, you can purchase D&B data to initially acquire or to update
the D&B data for the existing party.
If the appropriate party does not exist in your records, you can search the D&B database
to determine if data about the business is available in the D&B database.
If data is available from D&B for the new party, you can purchase that data from D&B.
Purchasing the data from D&B will automatically create a new party for you.
If data is not available from D&B for the new party, you can order an investigation from
D&B to gather the necessary data or you can manually create a new party using data you
have acquired from other sources.
D&B data can be viewed inside the credit review case folder and can be used for credit scoring
models.
Chapter 3 - Page 52
D&B Batch Loading
D&B Batch Loading

When you need to update a few parties or to investigate significant changes for one party, you
should use the online method to purchase and retrieve D&B information. Individual users can
efficiently search for and retrieve a partys D&B data online over the Internet.
If the D&B data for a large number of parties must be updated on a regular schedule or even
occasionally, batch loading would be the more efficient method. You can update all parties,
gather data only for new parties, or update parties that have not been updated since a specified
date. Batch retrieval and loading of D&B data is usually a regularly scheduled, automated
process set up and run by your Oracle Applications system administrator.
Chapter 3 - Page 53
Agenda
Chapter 3 - Page 54
Customer Account Relationships
Customer Account Relationships

(N) Customers > Quick or Standard (T) Relationships
Relationships exist between two customers and can be reciprocal or nonreciprocal. They allow
the following:
Payment of related invoices.
Sharing of pricing entitlements (Agreements and Commitments).
Consolidation of business addresses (Selection of a related customers ship-to address
during order entry).
Relationships are not transitive: If customer A is related to B and B is related to C, A and C are
not related. You must build the A to C relationship separately.
Under System Options you can select the check box Allow Payment of Unrelated Transactions
if you want to permit application of funds from one party to another unrelated party. If you do
not select this check box, a customer account relationship must be set up to apply payments
from one account to another.
Chapter 3 - Page 55
Practice - Create a Customer Account Relationship

Overview
In this practice you will create a customer relationship.
Assumptions

Practice.
Tasks
Create a relationship between XX-Big City and Business World (1608)
1.
2.
Find the XX-Big City customer
3.
Select the Customer Account record for Big City
4.
Define a reciprocal relationship with Business World (1608)
Chapter 3 - Page 56
Solution - Create a Customer Account Relationship

Create a relationship between XX-Big City and Business World (1608)
1.

Name: XX-Big City
2.
(B) Find
3.
Select the Customer Account record for Big City
4.
(B) Ok
5.
(T) Relationships
Name: Business World
Number: 1608
Type: Reciprocal
6.
Leave all other defaults
7.
(I) Save
Chapter 3 - Page 57
Agenda
Chapter 3 - Page 58

The Administration tab is not for implementation, but rather the setup and maintenance of TCA
entities, functionalities, or concepts that are used throughout the Oracle E-Business Suite.
Chapter 3 - Page 59
TCA Parties
TCA Registry
The TCA Registry is the single source of trading community information for all Oracle EBusiness Suite applications. Administration allows you to control the data in the Registry to
best fit your business needs.
Oracle Credit Management utilizes TCA parties to consolidate historical AR and OM data for
credit reviews. For example, if a party has 3 accounts related to it and each account has AR
data, all data will be consolidated for a global view of the partys credit worthiness and party
level credit limits can be shared by all accounts in the relationship.
Chapter 3 - Page 60
TCA Administration
TCA Administration Subtabs

Relationships: Set up the relationship types that can be used to create relationships among
entities in the TCA Registry.
Classifications: Set up the class categories and codes that can be used to classify entities
in the TCA Registry.
DQM: Set up Data Quality Management (DQM), which provides powerful search and
duplicate identification functionality.
Enrichment: Set up Third Party Data Integration to control the usage and display of third
party data along with user-entered information in the TCA Registry. You also set up your
integration with D&B.
Security: Set up data sharing groups and control how specific entities in the TCA
Registry can be accessed depending on user and responsibility privileges.
Chapter 3 - Page 61
Using Party Paying Relationships
Party Paying Relationships

In Receivables, a party paying relationship is a relationship where all corresponding accounts
and transactions that are associated with one party are accessible to another party. For example,
if you create a party paying relationship between Business World and Acme Worldwide, then
you can select from among both Business World and Acme Worldwide transactions when
applying a Business World receipt.
Chapter 3 - Page 62
Using Customer Account Relationships
Party Paying and Customer Account Relationships

With party paying relationships, you can define groups of related parties that are easy to create
and maintain in Relationship Manager. You can therefore use this flexibility to efficiently
model the complex business relationships within your trading community.
Note: Paying parties must have at least one account.
Chapter 3 - Page 63
Party Paying and Customer Account Relationships
Using Party Paying Relationships and Customer Account Relationships

Note: In Oracle Order Management's Sales Orders window, you can enter an agreement that
you defined for either a selected customer or related customers. Order Management recognizes
related customers, however, only if the relationships were built via customer account
relationships.
If you want to let a party pay for another party's transactions, you do not have to define
relationships for each of these. You can simply set the system option Allow Payment of
Unrelated Invoices to Yes.
You use the Customer Relationships Listing to view a listing of all relationships that exist for a
customer.
Chapter 3 - Page 64
Creating Party Paying Relationships
Chapter 3 - Page 65
Pay Within Paying Relationships
Pay Within Paying Relationships

The diagram on the following slide illustrates several parties within a Pay Within paying
relationship.
In this scenario, all accounts of each party in the relationship are available to all other parties in
the relationship for receipt application, commitment application, and so on.
Chapter 3 - Page 66
Party Paying Relationships Process Flow
Party Paying Relationships Process Flow

In other words:
Acme Worldwide can pay for Acme USA, Acme England and Acme West
Acme USA can pay for Acme Worldwide, Acme England, and Acme West
Acme England can pay for Acme Worldwide, Acme USA, and Acme West
Acme West can pay for Acme Worldwide, Acme USA, and Acme England
Chapter 3 - Page 67
Pay Below Paying Relationships
Pay Below Paying Relationships

If the parties in the same diagram on the previous slide are in a Pay Below paying relationship,
then all accounts of each child party in the relationship will be available to each parent party in
the relationship for receipt application, commitment application, and so on. In other words:
Acme Worldwide can pay for Acme USA, Acme England, Acme West, and its own
transactions.
Acme USA can pay for Acme West and its own transactions.
Acme England pays for its own transactions.
Chapter 3 - Page 68
Relationship Types and Relationship Groups
Relationship Types and Relationship Groups

If Business World wants to create a Pay Within paying relationship with Company A and a Pay
Below paying relationship with Company B, they must:
Define two different relationship types.
For each relationship type, assign one phrase to a relationship group, either Pay Within or
Pay Below.
Use the two relationship types to create two paying relationships, one for Company A
and one for Company B.
Chapter 3 - Page 69
Agenda
Chapter 3 - Page 70
Merge Parties or Customer Accounts
Merge Parties or Customer Accounts

(USA)
(N) Customers > Merge
(N) Customers > Party Merge
Merging a party is different than merging a customer account. The party is everything under
that party. The customer account merge is two accounts under one party. Merging party or
customer account information combines all information for two parties, customer accounts, or
account sites. You can delete or inactivate the merge-from party, customer account, and
account sites.
Before merging consider archiving the historical data for the absorbed party, customer account,
or account site. Also, consider that the information is being used by the entire e-Business suite
and will affect other applications.
Merging Incorrect Data
The most common reason to merge parties is to clean up data entered in error. For example,
data related to an existing party White Place might be entered in error for a new party created
as White Corp. You merge the data for these parties to consolidate all the data for White
Chapter 3 - Page 71
Place. Misspellings and the incorrect use of upper and lower case are also common reasons for
merging parties.
Merging Site Data
Another reason to merge party data is the consolidation or relocation of party sites. For
example, if a party closes a facility in Milan and moves all activity to an existing facility in
Rome, data related to the Milan site will be merged with the data for the Rome site.
Note: Because historical reporting will no longer be available for the Milan site, you should
carefully consider any merging.
Merging Party or Customer Account Data
A less common reason to merge party data is when two different parties merge and form a
single party.
Note: Because historical reporting will no longer be available using the parties prior names,
you should carefully consider any merging.
When merge processing is complete, Receivables automatically generates a party Merge
Execution report which can be printed or reviewed online.
After party data has been merged, there are no links between the previous party and its
transaction records. These transactions appear as if they had always belonged to the succeeding
party.
To automatically copy From addresses as To addresses, select Create Same Site.
Chapter 3 - Page 72
Party Merge
Party Merge
With the Party Merge feature you can consolidate duplicate parties, integrate an acquired party
into another party, or consolidate duplicate party sites of a party in the TCA party registry. The
related child entities that get merged or transferred include party relationships, contact
information, party profiles, customer accounts, and information obtained from third-party
sources.
The merging parties are referred to as the merge-from party and the merge-to party, or the
source and the target respectively. After the merge-from party is merged into the merge-to
party you can delete the merge-from, or source, party. By default the merge-from party is set to
a Merged status.
You must register party entities and party sites in the Party Merge dictionary. Some Oracle
applications, along with their party entities, are automatically registered at installation.
Registration specifies the names of the procedures required to merge the entities that interact
with the party entities. The Party Merge program uses the information in the Party Merge
dictionary to recognize which entities to merge.
Chapter 3 - Page 73
Agenda
Chapter 3 - Page 74
Reviewing Information
Chapter 3 - Page 75
Common Search Scenarios
Common Search Scenarios

(USA)
(N) Customers > Customers Summary
Online Searches
It is possible to use the above search scenarios to find customers online and review their
details.
While using the summary form to view multiple customers, you are able to view the
information or export it to a Excel spreadsheet using standard functionality.
Chapter 3 - Page 76
Reports
Reports
Customer Listing Detail/Summary
The mode of this report is changed via a report parameter. Use the Detail report to review
detail customer information entered for each customer. Use the Summary report to review
summary information about your customers. You can view customer name, customer number,
status, and any addresses and site uses you entered for your customers.
Customer Profiles Report
Use this report to review customer profile information assigned to each customer or customer
site. You can also review any changes made to your existing customer profiles in the Customer
Profile Classes window. If the profile option AR: Sort Customer Reports by Alternate Fields is
Yes, Receivables sorts information using the value of the Alternate Name field in the
Customers window.
Customer Relationship Listing
This report lets you review all customer relationships that have been defined. This report
includes the name and number of the primary and related customers, whether the relationship is
reciprocal, and any comments. The report lists all active relationships first followed by the
inactive ones.
Chapter 3 - Page 77
Agenda
Chapter 3 - Page 78
Required Customer Profile Setup Steps
Required Customer Profile Setup Steps

There are several setup steps that must be performed prior to implementing Customer Profile
Classes. These required steps will allow you to create a customer profile class that can then be
attached to the customer account record.
Chapter 3 - Page 79
Collectors
Collectors
(N) Setup > Collections > Collectors
Collectors are assigned to a profile class and can be updated on the customer record. When you
assign a collector to a
profile class, that collector becomes the collector for all customers assigned that profile class.
Collector names and telephone numbers can be printed on dunning letters sent to customers.
Receivables displays active collectors and their descriptions as list of values choices in the
Customers, Customer Profile Classes, and Customer Calls
windows. Receivables does not display inactive collectors in the list of values for these
windows.
You can make an existing collector inactive by unchecking the Active check box and then
saving your work. If the collector you want to
make inactive is associated with an active customer, Receivables displays a warning message.
Receivables provides a predefined collector called DEFAULT.
Chapter 3 - Page 80
Payment Terms
Payment Terms
Payment Terms can be attached to a profile class. The term can then default from the customer
this profile class is attached to, onto the Sales Order transaction, where it is a required field.
Payment Terms will also factor into Credit Checking in Order Management Transaction
processing.
For details on Payment term definition, refer to the Oracle Receivables User Guide.
Chapter 3 - Page 81
Optional Customer Profile Setup Steps
Optional Customer Profile Setup Steps

These setup steps will provide additional information to be placed on the Customer Profile
record. While they are not required, it may be helpful to implement these steps prior to creating
Customer Profile Classes to avoid the requirement of updating the Customer Profile record
with these data later.
Customer Profile Lookups
Lookups provide list of value selections when in a form. The Customer Profile Lookups
include: Account Status, Credit rating for customers, and Customer Credit Classification (do
not use Customer Credit Risk this is not currently used by any products).
Statement Cycles
These cycles control when you create customer statements.
Dunning Letters and Sets
Dunning Letters inform your customers of past due items and finance charges. Receivables
provides three predefined letters as well as ten letters that can be personalized. Additionally
you can create your own dunning letters. To use dunning letters they must be added to a
Dunning Letter Set. These sets combine a sequence of dunning letters into one group.
Chapter 3 - Page 82
Receivables provides one letter set called STANDARD which includes the three delivered
dunning letters.
AutoCash Rule
If you are using AutoCash, define your rule sets before defining system parameters or customer
profile classes. AutoCash determines the sequence of application methods Receivables uses
when applying receipts imported using AutoLockbox to open debit items.
Grouping Rules
Grouping rules indicate how to group transaction lines imported by AutoInvoice.
Credit Classifications
The credit classification describes the type of credit relationship that you have with the
applicant. The credit classification assignment determines the currencies that your enterprise
supports on the credit application or in the case folder.
Note: The classification defaults from the assigned profile class, but you can change it.
Chapter 3 - Page 83
Required Setup Steps for Customers
Chapter 3 - Page 84
Profile Options
Profile Options
System Administrator
(N) Profile > System
There are a number of Profile Options that will affect customer data or the windows used to
enter the data. Some of the key profile options are:
AR: Change Customer on Transaction: Determines whether to let users update customer
names in the Customer
windows.
AR: Enter Alternate Fields: Controls whether users can enter information in the Alternate
Name field in the Customers and Customer Addresses windows. Receivables also uses
this information when you choose Customer Name Sort as a parameter when printing
certain Receivables reports (for example, the Customer Listing Detail or Summary
report). Refer to the AR: Sort Customer Reports by Alternate Fields profile option
HZ: Bypass Find/Enter Window:Specifies if users can bypass the Find/Enter window and
directly enter the CustomersStandard and CustomersQuick windows. If you set this
profile option to No, then the user must navigate through the Find/Enter window each
Chapter 3 - Page 85
time they want to enter new customers in the CustomersStandard and CustomersQuick
windows.
HZ: Cleanse Fuzzy Key: If set to Yes, allows Receivables to create fuzzy keys by
removing all internal and trailing vowels (not leading vowels) and removing all double
letters in a word.
HZ: Display D&B button in Customer form: Enables the D&B Information button in the
CustomersStandard and CustomersQuick windows of Oracle
Receivables. Use this profile option only if you enable Dun and Bradstreet integration
with Receivables.
Default Country: This is the default source for the Country field for all address regions
and is used by the Flexible Address Formats feature, the Flexible Bank Structures feature,
and the Tax Registration Number and Taxpayer ID validation routines.
There are many more Profile Options that will affect Customers in the Order to Cash process.
For a complete listing of profile options, please refer to the Oracle Receivables User Guide.
Chapter 3 - Page 86
Optional Setup Steps for Customers
Optional Customer Setup Steps

These setup steps will provide additional information to be placed on the Customer Profile
record. While they are not required, it may be helpful to implement these steps prior to creating
Customer Profile Classes to avoid the requirement of updating the Customer Profile record
with these data later.
Customer Lookups
Lookups provide list of value selections when in a form. The Customer Lookups include:
Address Categories, Country Codes, Business Purposes, Customer Categories, Customer
Classes, Free on Board (FOB), Freight Carriers, Language (for language used at customer site),
Job Titles, Contact Titles (Mr. and Mrs, and so on), Communication Type, Relationship Type,
and State abbreviations.
Customer Bank Accounts
If you use Receivables, use the Banks window to define your internal banks, which you use for
receipts, and external banks, which are your
customers banks with which you do business. These customer bank accounts are used for
automatic receipts.
Payment Methods
Chapter 3 - Page 87
Receivables uses payment methods to account for your receipt entries and applications.
Payment methods also determine a customers
remittance bank information. This information can be used for transactions from credit card
payments to automatic receipts and bank charges.
Flexible Address Style
To enter customer, supplier, bank, check and remit to addresses in country specific formats,
you must set up flexible address formats. This is a multi step process that will allow you to
conform to post regulations for the countries you interact with.
Chapter 3 - Page 88
Flexible Address Formatting
Flexible Address Formatting

Flexible address formatting allows you to adapt the address style based upon the country the
address has been associated with.
There are two options when using flexible address formats:
Use Predefined Format
Customize Address Format
Oracle provides five predefined address styles or formats: Japanese, Northern European,
Southern European, South American, and United Kingdom/Asia/Australasia. For details on
these formats please consult the Receivables Users Guide. While all of the address styles have
been defined, none have been associated with a specific country.
To Customize Address Formats, you must follow a simple, yet multi step process.
Step 1: Setup Flexible Address Format
As the address formats are designed in a descriptive flexfield, we will use this functionality to
add to the list of available formats. There are several descriptive flexfields that must be
updated with a new context sensitive segment to increase the address format options. They are:
Chapter 3 - Page 89
Descriptive Flexfield
Displayed
Bank Address
Banks
Remit Address
Remitto Address, Customers
Payment Address
Payment Summary, Payment Overview
Site Address
Suppliers
After creating a context field value, associate segments appropriate for your new address
format. Remember to freeze and compile the flexfield.
For more information on creating context sensitive descriptive flexfields please refer to the
Oracle Application Flexfields Guide.
Step 2: Create Address Style Lookup
After you have created a new context field value you must now map the context field value
name to a new lookup code. Using the Application Developer responsibility navigate to the
Special Lookups window. There you will need to enter the following values:
Language
Code this must match the context field value you created in Step 1
Meaning this should be the description you gave the context field value in Step 1
Do not use start or ending dates for this lookup.
Step 3: Assign Style to Country
It is necessary to associate the style you created in Step 2 with a country on the Countries and
Territories window. You must do this step for all countries you wish to have a associated with
a flexible address format, custom defined, or delivered by Oracle.
For more detail regarding the flexible address format please refer to the Oracle Receivables
User Guide.
Chapter 3 - Page 90
Summary
Chapter 3 - Page 91
Chapter 3 - Page 92
Process Invoices Using

AutoInvoice
Chapter 4
Process Invoices Using AutoInvoice
Chapter 4 - Page 1
Chapter 4 - Page 2
Objectives
Chapter 4 - Page 3
Agenda
Chapter 4 - Page 4
AutoInvoice Process
Autoinvoice Process
The AutoInvoice process imports large numbers of transactions for seamless integration
from Oracle or non-Oracle systems.
- Invoices
- Debit memos
- Credit memos
- On-account credits
The AutoInvoice process also calculates taxes for the imported transactions, or passes the
tax through the tables where the tax is calculated.
Errors are easily corrected online with user interfaces.
Oracle Receivables uses grouping rules to import lines.
Note: You cannot import deposits or guarantees.
Chapter 4 - Page 5
AutoInvoice Integration
AutoInvoice Integration
In Oracle Receivables, you can create invoices from the following Oracle applications:
Order Management
Projects
Service
Property Manager
Oracle Receivables can create invoices from the following non-Oracle applications:
Legacy system (for transaction history)
Non-Oracle billing applications
Non-Oracle order entry applications
Chapter 4 - Page 6
What Occurs During AutoInvoice
What Occurs During AutoInvoice

When imported transactions are processed through the AutoInvoice program, the following
events happen:
Line, accounting, and sales credit information populates three Receivables interface
tables.
Lines are ordered and grouped by the rules defined.
Tax is calculated by the Sales Tax Engine.
GL (General Ledger) date is determined by the rules or, if rules are not used, from the
ship or sales order date.
GL accounts are assigned using AutoAccounting.
Tax, freight, commitments, and credit memos are linked to transaction lines based on the
Reference ID or Reference flexfield.
All transactions are batched by batch source name and request ID.
Validated lines are used to create the transactions.
Error lines remain in the Interface Table for correction
Chapter 4 - Page 7
AutoInvoice Interface Tables
AutoInvoice Interface Tables

Every line must use the RA_INTERFACE_LINES_ALL table. The other two tables are
optional.
RA_INTERFACE_LINES_ALL Table
This table contains information related to all transactions to be processed by AutoInvoice.
Transactions include invoices, debit memos, credit memos, and on-account credits. This table
holds the key data such as bill-to customer, ship-to customer, and transaction date.
Each record contains line, tax, freight, or finance charges information.
The Line_Type field identifies the type of information contained in the record.
A record can be a parent record: Line, Header Freight, or Charges; or a child record: Tax
or line-level Freight.
A child record is linked to the parent record using the Link-To Transaction flexfield.
RA_INTERFACE_DISTRIBUTIONS_ALL Table
Oracle Order Management does not use this table because AutoAccounting creates the
distributions in Oracle Receivables.
Chapter 4 - Page 8
This table contains accounting distributions to be used by the transactions defined in

RA_INTERFACE_LINES_ALL.
Accounts defined in this table override any accounts created using AutoAccounting.
You can choose to pass some or all account information to AutoInvoice. Any accounts
that are not passed will be derived using AutoAccounting.
Records in this table are linked to records in the RA_INTERFACE_LINES_ALL table
using the Transaction flexfield.
RA_INTERFACE_SALESCREDITS_ALL Table
This table contains all sales credit information for the transactions in the
RA_INTERFACE_LINES_ALL table.
The two tables are linked using the Transaction flexfield.
This table is required to track sales credits.
Chapter 4 - Page 9
Agenda
Chapter 4 - Page 10
Managing AutoInvoice System Options
Managing AutoInvoice System Options

(N) > Setup > System > System Options
AutoInvoice System Options are set in the AutoInvoice region of the Trans and Customers tab
of the System Options window.
Chapter 4 - Page 11
Transaction Batch Sources
Transaction Batch Sources

Assign a batch source type of Imported to invoices created by AutoInvoice.
The batch source allows you to:
Reject or automatically correct the tax code.
Reject transactions with invalid lines, or create transactions excluding the invalid lines.
Reject or automatically adjust the GL date if the transaction date falls in a closed period.
If the transaction date is in a closed period, you can adjust the date to the first GL date of the
next open or future period, or you can reject the transaction.
Chapter 4 - Page 12
Defining Transaction Batch Sources
Defining Transaction Batch Sources

(N) > Setup > Transactions > Sources
AutoInvoice calculates the revenue amount by multiplying the quantity and unit selling price.
Use the AutoInvoice Clearing account to post the difference between the passed and calculated
revenue amount.
If you do not want to use the AutoInvoice Clearing account, the passed revenue amount must
equal the calculated selling price times the quantity. (Passed revenue amount = Calculated
selling price x Quantity.)
Chapter 4 - Page 13
Grouping Rules
Grouping Rules
(N) > Setup > Transactions > AutoInvoice > Grouping Rules
In the example shown in this slide the invoices are grouped by Currency, Bill-to and lastly,
Transaction Flexfield Attribute 2, Order Type.
Grouping rules are mandatory and determine how transaction lines are grouped into
transactions.
Optionally, you can use line ordering rules to determine the order in which lines are
displayed on a transaction.
To uniquely identify imported transactions and link the tax, freight, commitments, and
credit memos, define the Transaction flexfields.
AutoInvoice validates your data by ensuring that the columns in Receivables Interface
Tables reference the appropriate values and columns in Receivables.
Chapter 4 - Page 14
Grouping Transaction Attributes
Grouping Transaction Attributes

Receivables provides two different types of transaction attributes: required and optional.
You cannot add or delete required transaction attributes, but you can always add optional
ones.
A default grouping rule is provided with Receivables which groups lines using required
transaction attributes.
Optional transaction attributes are available to create custom grouping rules.
Grouping and Ordering Rules must include required attributes and may include optional
attributes.
Required attribute examples: Bill-To Address, Currency, GL (General Ledger) Date, Primary
Salesperson.
Optional attribute examples: Accounting Rules, Sales Order, Tax Code.
Chapter 4 - Page 15
Grouping Rule Hierarchy
Grouping Rule Hierarchy

Assign Grouping Rules to Invoice Sources, Customer Credit Profile Classes, or System
Options.
AutoInvoice uses the following hierarchy to determine which Grouping Rule to use:
Invoice Source
Customer Credit Profile Class
System Options.
Chapter 4 - Page 16
Line Ordering Rules
Line Ordering Rules

(N) > Setup > Transactions > AutoInvoice > Line Ordering Rules
AutoInvoice uses Line Ordering Rules to order and number the lines grouped into transactions.
For example, you might want to use Line Ordering Rules to ensure that the highest invoice line
amounts are listed first.
If an Ordering rule is not defined, lines will appear on transactions in random order.
You can specify a Line Ordering Rule for each Grouping Rule.
You can also assign transaction attributes to your Line Ordering Rules. You can assign a
priority to these attributes for each of your invoice Line Ordering Rules. You can also specify
an ascending or descending order for each transaction attribute assigned to a rule. For example.
Create an invoice Line Ordering Rule with attribute SALES_ORDER_LINE.
Chapter 4 - Page 17
Transaction Flexfields
Transaction Flexfields
Transaction flexfields are descriptive flexfields that AutoInvoice uses to uniquely identify
transaction lines.
Because they are unique for each transaction line, they can also be used to reference and link to
other lines.
Receivables lets you determine how you want to build your transaction flexfield structure and
what information you want to capture.
Define a flexfield for each import source. Specify which one to use during import.
Use the Reference Flexfield to link a credit memo line to a transaction. This passes information
like order number, project number, and shipping information.
Chapter 4 - Page 18
Defining Transaction Flexfields
Defining Transaction Flexfields

(N) > Setup > Financials > Flexfields > Descriptive > Segments
Transactions Flexfields are descriptive flexfields that AutoInvoice uses to uniquely identify
transaction lines.
Define Transaction Flexfields in the Descriptive Key Segments window.
The Line, Link-To, and Reference structures must be identical.
Note: AutoInvoice always uses the Line Transaction Flexfield structure for both the
Link-to and Reference information when importing transactions. Define these flexfield
structures only if this information is to be displayed on a custom windows.
(Optionally), use transaction flexfield information for imported invoices in lists of values
throughout the product. Use the profile option AR: Transaction Flexfield QuickPick to
select the Transaction Flexfield Segment you want to display. For example, if you want
to be able to reference the order, you need to assign the transaction flexfield segment that
holds the order number to the AR: Transaction Flexfield QuickPick profile option. The
order number will then display in the reference column of all invoice lists for imported
invoices.
Chapter 4 - Page 19
Determining Tax Liability
Determining Tax Liability

AutoInvoice gives you the flexibility to handle all your taxing needs for the following tax
methods:
VAT (Value Added Tax)
Sales Tax
Sales tax is calculated by AutoInvoice using the tax rates associated with your shipping
address.
AutoInvoice automatically uses the Sales Tax Engine to calculate tax for the invoice lines.
You can import additional manual tax lines through the interface table.
Chapter 4 - Page 20
AutoInvoice Validation
AutoInvoice Validation
Validates lines for:
Accounting rules
Accounting periods
AutoInvoice validates your data for compatibility with Receivables. It ensures that the columns
in Receivables interface tables reference the appropriate values and columns in Recievables. It
checks for:
Existence: Ensures that the values for some columns are already defined.
Batch Sources: Ensures consistent values for fields in the Transaction Sources window.
Uniqueness: Ensures that the invoice number you supply is unique within a given batch
source.
Precision: Ensures that the amount and accounted amount have the correct precision.
Cross Validation: Ensures that column values agree with each other.
Chapter 4 - Page 21
Submitting AutoInvoice
Submitting AutoInvoice
(N) > Interfaces > AutoInvoice > (B) Single Request > (B) OK
The AutoInvoice Master Program can be submitted from the Standard Report Submission
(SRS) window. This process can be schedule to run on specific intervals using the SRS
scheduling features.
Process specific transactions or a range of transactions by entering report parameters as
listed on the slide above.
Use different selection criteria to submit individual transactions or groups of transactions.
Submit a maximum of fifteen instances.
Note: An instance refers to how AutoInvoice groups and processes your transactions.
Submitting a greater number of instances lets you import transactions into Receivables more
quickly.
Chapter 4 - Page 22
Implementation Considerations
Chapter 4 - Page 23
Agenda
Chapter 4 - Page 24
Correct Errors Overview
Correct Errors Overview

The AutoInvoice Exception Handling Windows can be used to correct errors that are in the
AutoInvoice Interface Table.
Records that pass validation are transferred into Receivables transaction tables.
Records that fail validation are called exceptions; these records remain in the
AutoInvoice interface tables.
Once you have corrected the errors, you must resubmit AutoInvoice.
Valid lines cannot be changed in the AutoInvoice Exception Handling windows. Only
those lines with errors can be changed.
Chapter 4 - Page 25
AutoInvoice Exception Handling Windows
AutoInvoice Exception Handling Windows

(N) > Control > AutoInvoice > Interface Lines
(N) > Control > AutoInvoice > Interface Exceptions
Interface Exceptions Window
Displays the interface ID, exception type, error message, and the invalid value associated
with each error.
Cannot edit data in this window, but you can view the error message and easily correct
the error by clicking the Details button.
Note: The error message and column name with erroneous data is displayed in the Message
column, and the value that needs to be corrected is displayed in the Invalid Value column.
Interface Lines Window
Displays all records in the interface tables that failed validation, provides an error
message, and can be used to correct invalid records.
Click the Details button, the window opens where the errors can be corrected. Buttons are
provided to correct specific types of errors.
Chapter 4 - Page 26
Correct errors in these windows.

Line Errors Window
Displays all errors associated with a specific line and can only be opened from the
Interface Lines window.
View all errors associated with a single line by clicking the Errors button in the Interface
Lines window.
Cannot edit data in this window.
Displays the interface ID, the error type, error message, and the invalid value.
Note: You might use this window when you access the Interface Lines window directly, which
does not display the error messages.The type indicates which button to click in the Interface
Lines window.
Chapter 4 - Page 27
Summary
Chapter 4 - Page 28
Process Invoices
Chapter 5
Process Invoices
Chapter 5 - Page 1
Process Invoices
Process Invoices
Chapter 5 - Page 2
Objectives
Process Invoices
Chapter 5 - Page 3
Agenda
Process Invoices
Chapter 5 - Page 4
Oracle Receivables Overview
Oracle Receivables Overview

Oracle Receivables provides the capability to create all the necessary transactions to correctly
bill customers, record payments, and perform adjustments to customers accounts. These
transactions include: invoices, credit memos, debit memos, guarantees, deposits, bills
receivable, adjustments, and chargebacks. The Oracle Receivables process consist of several
major steps. The Create Invoices and Print Invoices steps will be discussed in this topic.
Create Profile Classes: Defines several default values for customers with similar credit
terms and invoicing requirements.
Enter Customers: Creates information for the customer, defines the addresses for the
customer, and the business purpose(s) at each address.
Create Invoices: Uses AutoInvoice or manually created invoices to bill customers for
goods and services.
Print Invoices: Produces invoices to mail to customers.
Use iReceivables: Allows customers and employees to access customer accounts online
to see the status of invoices and receipts and to request credits on line.
Post Receipts: Permits posting of customer payments as they are received.
Process Invoices
Chapter 5 - Page 5
Perform Collections: Enables collectors to use informational windows and reports to

perform timely and accurate collection activities.
Process Invoices
Chapter 5 - Page 6
Transactions Overview
Transactions Overview
Transactions can be imported from Oracle Order Management, Projects, Service, Property
Management and non-Oracle systems. Transactions can also be created manually. In the
Transaction process, tax can be calculated, General Ledger accounts created, and customer
balances updated. Invoices can be printed and corrections can be entered, if necessary.
Process Invoices
Chapter 5 - Page 7
Transactions Workbench Windows
Transactions Workbench Windows

(N) > Transactions > Transactions Summary
The Transactions Summary window consists of a workbench, which has buttons that open
windows where the following can be done:
Create New transactions.
Create adjustments and credit memos.
Complete transactions.
Review transactions and cash applications.
Copy transactions.
Process Invoices
Chapter 5 - Page 8
Agenda
Process Invoices
Chapter 5 - Page 9
Invoice Entry Methods
Invoice Entry Methods

Enter standard invoices according to your business needs:
AutoInvoice: Import transactions from Oracle Order Management, other Oracle
applications, or legacy systems.
Manual Invoices: Enter transactions for invoices that do not originate in a feeder system,
such as invoices for miscellaneous items, services, or freight.
Process Invoices
Chapter 5 - Page 10
Creating a Standard Invoice Manually
Creating a Standard Invoice Manually

(N) > Transactions > Transactions
A Standard Invoice is created manually in Oracle Receivables using the following process.
Enter invoice header information: Identify the customer and type of invoice. Can be
modified to include transaction source.
Enter invoice lines: Record goods and services to be invoiced.
Enter sales credit: Optionally, record sales commissions.
Enter freight lines: Optionally, record freight charges.
Use AutoAccounting to create accounts: Create the General Ledger distribution accounts
by using preconfigured AutoAccouning Rules.
Complete Invoice: Finish the process and prepare the invoice for printing.
Process Invoices
Chapter 5 - Page 11
Invoice Components
Invoice Components
Invoices consist of three major components, Invoice Header, Customer Information, and Lines.
Invoice Header
Number: If the Batch Source specifies automatic invoice numbering then Receivables
assigns a number when you save the transaction or you can enter the number manually.
Source: Sets default values and AutoInvoice options. Controls numbering. Turns on
Automatic as well as enters the range of numbers for the system to use.
Class: Provides a dropdown list of classes of transactions, chargeback, credit memo, debit
memo, deposit, guarantee, and invoice.
Type: Determines whether Receivables amounts are recorded and posted to the General
Ledger.
GL Date: Sets the General Ledger period for posting of transaction distributions.
Customer Information
Ship-To Address: (Optional) Ship goods or provide services at this customer address.
Process Invoices
Chapter 5 - Page 12
Bill-To Address: Send the invoice to this customer address.

Lines
Item: Goods or services provide to the customer.
Price: Unit price or total amount to be charged the customer.
Quantity: Amount ordered or one when entering the total amount.
Process Invoices
Chapter 5 - Page 13
Transactions Window Tabs
Transactions Window Tabs

The tabs in the Transaction window is where the following information is entered:
Main: Customer Bill-to, Ship-to, Due Date, Terms, Salesperson and Commitment.
More: Invoicing Rule, Print Option, Default Tax, Status, Finance Charges, Cross
Reference, Original Transaction, Agreement, Dispute Amount and Date, Special
Instructions, Comments, Document Number, Print Date, and Purchase Order information.
Remit to, Sales: Remit-to-address, Sold To Customer and Number, and Sales Territory.
Paying Customer: Paying Customer Number and Location, Payment method, Customer
Bank information, and Expiration Date.
Notes: Date, Source, and Memo.
Commitment: Effective Dates, Amount, Item, Memo Line, Description , and Transaction.
(Used with Commitments).
Process Invoices
Chapter 5 - Page 14
Credit: Reason, Customer Reference and Date, Rules and Split Term Method, Credited
Transactions Source, Reference, Amount, GL Date, Number, Bill-to, Balance Due, and
Transaction Date. (Used with Credit Memos).
Process Invoices
Chapter 5 - Page 15
Required Transaction Information
Required Transaction Information

A number of fields are required during invoice entry. They include the following:
Date: Transaction date.
Source: List of values showing where transaction originates. New sources can be added
to the list of values.
Class: Classifies the transaction as an Invoice, Credit Memo, Debit Memo, Guarantee,
Deposit, or Chargeback.
Type: Determine whether a transaction updates open receivables, can be posted to your
General Ledger, Receivables calculates tax, and other defaults are entered.
GL Date: Enters the current date the transaction will use when transferring to the General
Ledger.
Bill-to: Determines where the final document is sent.
Terms: Records the payment terms for the transaction.
Remit-To: Provides your address information for the payment remittance.
Process Invoices
Chapter 5 - Page 16
Entering Invoice Dates
Entering Invoice Dates

An invoice date can be entered any time. This determines the due date only.
The General Ledger (GL) date determines when the transaction can be transferred to the
General Ledger. The GL date defaults to the transaction date if it is in a open period.
Otherwise, it defaults to the last day of the month of the current open period.
The Receivables calendar can be opened or closed independently of the General Ledger
calendar. (The General Ledger calendar is shared by Receivables so no separate setup is
required.)
Process Invoices
Chapter 5 - Page 17
Transaction Defaults
Transaction Defaults
Transaction defaults save data entry time and reduce errors. There are several sources for these
defaults.
Transaction Source defaults:
- Transaction type
- Transaction numbering
Transaction Type defaults:
- Transaction class
- Payment terms (if not set at the customer)
- Accounting
- Credit memos for invoices
- Invoice information for commitments
AutoAccounting defaults:
- Accounts for transactions
- Validates Accounts
Process Invoices
Chapter 5 - Page 18
Customer Record defaults:

- Ship-to and bill-to address
- Payment terms
- Salesperson
Accounting Rules default from:
- An item
- A standard memo line
Statement cycles default from the customer profile class.
Process Invoices
Chapter 5 - Page 19
Standard Invoice Line Types
Standard Invoice Line Types

(N) > Transactions > Transactions > (B) Line Items
There are three types of standard invoice line types that can be used during invoice entry.
Inventory item: Enter items available in inventory, using a list of values.
Standard Memo line: Enter non-inventory products or services, such as extended
warranties or maintenance contracts, using a list of values.
Free Form line: Enter a description.
Process Invoices
Chapter 5 - Page 20
Entering Freight Invoices or Lines
Entering Freight Invoices or Lines

(N) > Transactions > Transactions > (B) Line Items
If the transaction type assigned to this invoice allows freight charges, enter freight amounts.
Bill freight charges for the entire invoice or for each line:
Click the Freight button in the Transactions window to enter at invoice level.
Click the Freight button in the Lines window to enter at lines level.
Note: If you click the freight button at invoice level, then the freight charges apply to the
entire invoice. If click the freight charge at line level, it will apply to that particular line.
AutoAccounting determines the default freight account.
Note: Users can calculate and report tax on freight by creating inventory items with the type of
Freight. AutoAccounting identifies these standard invoice lines with an inventory item type of
Freight and derives your General Ledger accounts based on the rules you have defined for
freight transactions.
Process Invoices
Chapter 5 - Page 21
Entering Sales Credits
Entering Sales Credits

If the Require Salesperson check box in the Miscellaneous tab of the System Options
window is selected, a salesperson must be assigned to each invoice.
Receivables
(N) > Transactions > Transactions > (B) Sales Credits
Use the Sales Credits window to allocate sales credit among salespeople, and record both
revenue (credit based on invoice lines) and non-revenue sales credit (credit in excess of
your revenue sales credit such as bonuses or incentives). This information defaults to
line-level sales credits.
Note: The percentage of revenue sales credits must add up to 100%.
AutoAccounting will recalculate the revenue account assignment.
Additional non revenue sales credits (above 100%) can be assigned for bonus or
incentive purposes.
Process Invoices
Chapter 5 - Page 22
Allocate different percentages or to different salespeople by line, using the For This Line
region of the Sales Credits window. Access this window by clicking Sales Credits in the
Lines window.
Process Invoices
Chapter 5 - Page 23
Completing Transactions
Completing Transactions
When all required information has been entered, click the Complete button to complete (finish)
the invoice.
Payment schedules and aged receivable amounts are calculated when the Complete
button is selected.
Completed transactions can be transferred to the General Ledger.
Only completed transactions can be printed.
The requirements for Completing an invoice:
An invoice must have at least one line, or at the header level be a freight invoice.
The General Ledger date of the invoice must be in an open or future period.
The invoice sign must match the sign of the transaction type.
The sum of distributions for each line must equal the invoice line amounts.
If Calculate Tax for transaction type is set to Yes, tax is required on each line.
Process Invoices
Chapter 5 - Page 24
Practice - Create an Invoice

Overview
In this practice you will create a receivables invoice.
Assumptions

Practice.
Tasks
Create an Invoice
Responsibility = Receivables Manager
1.
Navigate to the Transactions window
2.
(N) Transactions > Transactions

Source: Manual
Class: Invoice
Type: Invoice
Create an invoice for XX-Big City using the following information:

Line Number
Item Number
Quantity
Unit Price
Tax
CS03755
10
1500 Location
CS32698
1750 Location
3.
Complete the invoice
4.
Note Transaction Number: ____________________________________
Process Invoices
Chapter 5 - Page 25
Solution - Create an Invoice

Create an Invoice
1.
Navigate to the Transactions window
(N) Transactions > Transactions

Source: Manual
Class: Invoice
Type: Invoice
2.
(T) Main
Ship To Name: XX-Big City
3.
(B) Line Items

Line Number
Item Number
Quantity
Unit Price
Tax
CS03755
10
1500 Location
CS32698
1750 Location
4.
(I) Save
5.
Close Lines Window
6.
(B) Complete
7.
Note Transaction Number: ____________________________________
Process Invoices
Chapter 5 - Page 26
Creating Invoice Batches
Creating Invoice Batches

(N) > Transactions > Batches
Invoice Batching can be used to create groups of invoices Batching provides checks and
balances not available in a single invoice. Some of the elements of a batch are:
The batch date defaults to the invoice date.
If a batch is entered, Oracle Receivables uses the source assigned to the batch for each of
the invoices.
Batches must match control and actual invoice counts and amounts.
Actual count and amount are updated as each invoice is entered.
A batch can contain invoices with different currencies.
Invoices can be printed by batch.
Oracle Receivables uses invoice batches to import invoice data.
Batch information identifies the originating system when importing transactions.
Process Invoices
Chapter 5 - Page 27
View Currency Details
View Currency Details Window

The window also displays currency conversion details such as the rate, rate date, and rate type.
For a transaction, the window displays:
Transaction header information
Conversion details
Transaction information. For each transaction, you see the total amount, plus the amounts
of any receipts, credit memos, adjustments, discounts, or bills receivable, converted to
each currency.
For a receipt, the window displays:
Receipt header information
Conversion details
A list of receipt applications. For each application, you see the amount that was applied
to the receipt. You see this amount in each currency. You can drill down from each
invoice to the invoice currency detail.
To open the View Currency Details window, use a responsibility associated with your primary
functional currency. Select a transaction in one of the following windows, then either choose
Process Invoices
Chapter 5 - Page 28
the View Currency Details option from the Tools menu, or choose the View Currency Details
icon in the toolbar.
Transactions
Transactions Summary
Balances
Receipts
Receipts Summary
Note: You must save a transaction before you can open the View Currency Details window for
it.
Process Invoices
Chapter 5 - Page 29
Agenda
Process Invoices
Chapter 5 - Page 30
Creating Copies of Invoices
Creating Copies of Invoices

(N )> Transactions > Copy Transactions
Use the Copy Transactions window to create recurring invoices for products and services sold
on a regular basis. A model invoice is used to copy a series of invoices in future periods.
Example:
Business Needs: A customer is billed for the same service every month.
Solution: For the first month, enter a new invoice that refers to the billed service. This
becomes the model invoice for the following months.
The model transaction must be complete.
Once the model transaction is copied, changes to the model transaction do not affect the
copied transaction.
The model transaction should be the open or closed transaction that exactly matches the
transaction(s) to recur.
Process Invoices
Chapter 5 - Page 31
Using Recurring Rules
Using Recurring Rules

(N) > Transactions > Copy Transactions
Oracle Receivables determines the date and frequency of the copied transactions, using the
rule, first transaction date, and number of times specified.
You cannot update the recurring schedule after it has been saved.
Oracle Receivables creates all invoice copies at one time.
Invoices that are created in unopened periods are created as incomplete.
If the batch source for the model invoice has automatic transaction numbering turned on,
Oracle Receivables automatically numbers each recurring transaction.
Each recurring transaction uses the batch source that is assigned to the model transaction.
Select one of the following rules to create the invoices on the specific schedule:
Annually: Once a year.
Semi-Annually: Same day every six months.
Quarterly: Same day every three months.
Process Invoices
Chapter 5 - Page 32
Bi-Monthly: Same day every other month.

Monthly: Same day every month.
Weekly: Every seven days.
Days: Interval based on the number of days entered.
Single Copy: One copy.
Process Invoices
Chapter 5 - Page 33
Practice - Copy an Invoice

Overview
In this practice you will create a copy an invoice.
Assumptions

Practice.
Tasks
Copy Invoice
1.
Navigate to the Copy Transactions window
2.
(N) Transactions > Copy Transactions
Query transaction you just created and create 6 invoices to be sent monthly
View the completed copy report

3.
Select your concurrent request for the program Recurring Invoice Program and view it
Process Invoices
Chapter 5 - Page 34
Solution - Copy an Invoice

Copy Invoice
1.
Navigate to the Copy Transactions window
(N) Transactions > Copy Transactions
2.
Query transaction you just created

3. Rule: Monthly
Number of Times: 6
3.
Accept all other defaults
4.
(I) Save
5.
Note Transaction Numbers:___________________________________________
View the completed copy report

6.
(M) View > Requests (B) Find
7.
Select your concurrent request for the program Recurring Invoice Program
8.
(B) View Output
Process Invoices
Chapter 5 - Page 35
Creating Invoices with Rules
Creating Invoices for Services

(N) > Transactions > Transactions > (B) Line Items > (B) Rules
Accounting Rules determine the revenue recognition schedules for invoices, while invoicing
rules determine when to recognize revenue for Receivables invoices.Invoicing Rules record the
receivable in the first (Bill in Advance) or last (Bill in Arrear) period of the service.
You can assign invoicing rules to invoices that you manually enter or import into
Receivables through AutoInvoice.
Once the invoice is saved, you cannot update an invoicing rule.
Process Invoices
Chapter 5 - Page 36
Accounting Rules
Defining Accounting Rules

(N) > Setup > Transactions > Accounting Rules
Accounting rules determine when to recognize revenue amounts.
Use Accounting, Fixed Duration type to recognize revenue over a specific number of
periods. Revenue can be spread evenly or a percentage can be specified for each period.
Default is even distribution.
Use the Accounting, Variable Duration type to recognize revenue by a percentage for the
first period. The remaining revenue is spread evenly across the number of periods that
you specify during transaction entry.
Process Invoices
Chapter 5 - Page 37
Assigning Accounting Rules to Invoice Lines
Assigning Accounting Rules to Invoice Lines

(N) > Transactions > Transactions > (B) Line Items > (B) Rules
Each invoice line can have a different accounting rule.
Oracle Receivables uses the First GL Date field in the Transactions window to determine when
to start recognizing revenue.
The number of periods in which revenue is recognized is determined by the value in the
Number of Accounting Periods field in the Transactions window.
Value defaults from fixed rule.
Value must be entered for variable rule.
Process Invoices
Chapter 5 - Page 38
Using Invoices With Rules
Process Invoices
Chapter 5 - Page 39
Example of Billing in Advance
Example of Billing in Advance

Because you are billing the customer for the entire invoice in the first accounting period, the
offset account must be Unearned Revenue. Revenue is considered earned only when services
or support has been provided.
With the Bill in Advance invoicing rule, Oracle Receivables updates the GL (General Ledger)
Date and invoice date of the invoice to the first accounting period for the accounting rule.
For example, if the GL Date of the invoice was originally 01JAN02, and revenue was spread
across 3 months, Oracle Receivables uses the GL Date of the invoice to 01JAN02.
Process Invoices
Chapter 5 - Page 40
Example of Billing in Arrears
Example of Billing in Arrears

Because Billing in Arrears bills the customer for the entire invoice in the last accounting
period, the offset account must be Unbilled Receivables.
With the Bill in Arrears invoicing rule, Oracle Receivables updates the GL Date and invoice
date of the invoice to the last accounting period for the accounting rule.
For example, if the GL Date of the invoice was originally 01JAN02, and revenue was spread
across 3 months, Oracle Receivables changes the GL Date and invoice date of the invoice to
01MAR02.
Process Invoices
Chapter 5 - Page 41
Deferred Accounting Rules
Deferred Accounting Rules

Use Deferred Accounting Rules to recognize revenue on demand using the Revenue
Accounting feature. Deferred Accounting Rules are enabled by selecting the Deferred Revenue
checkbox on the Invoicing and Accounting Rules window.
Process Invoices
Chapter 5 - Page 42
Revenue Recognition Program
Running the Revenue Recognition Program

(N) > Control > Accounting > Revenue Recognition
Accounting distributions are created only after you run the Revenue Recognition
program. Only new transactions are selected each time the process is run.
For Bill in Advance, the offset account to Accounts Receivable is Unearned Revenue.
- For Bill in Arrears, the offset account to Revenue is Unbilled Receivables.
Accounting distributions are created for all periods when Revenue Recognition runs.
When you use deferred accounting rules, the Revenue Recognition program creates a
single distribution per line that posts to an unearned revenue GL account.
Submit the Revenue Recognition program manually through the Run Revenue
Recognition window.
Submit the Revenue Recognition program automatically when posting to Oracle General
Ledger.
The program processes revenue by transaction, rather than by accounting period.
Process Invoices
Chapter 5 - Page 43
How Oracle Receivables Uses Statements
How Oracle Receivables Uses Statements

(N) > Print Documents > Statements
Statements communicate activity to your customers about invoices, credit memos, debit
memos, payments, on-account credits, chargebacks, deposits, and adjustments.
Oracle Receivables also prints your customers past due balances based on aging buckets.
You can enhance your statements by printing your own custom messages.
Process Invoices
Chapter 5 - Page 44
Making Adjustments Using Revenue Accounting
Making Receivables, Vision Operations (USA)

(N) > Transactions > Transactions or (N) Transactions > Credit Transactions
(N) > Control > Accounting > Revenue Accounting
The Revenue Accounting feature lets you adjust revenue.
Earn or unearned revenue
You can also adjust sales credits
- Transfer revenue sales credits between Salespersons (maintaining the 100% total)
- Add Non-revenue sales credits
You can adjust completed invoices and credit memos.
You can make adjustments at the transaction or line level.
Receivables uses AutoAccounting to generate the required accounting distributions.
Use the Revenue Accounting and Sales Credits window to manually perform these
adjustments.
Use the Revenue Adjustment API to automatically perform these adjustments.
Process Invoices
Chapter 5 - Page 45
Setup Details Report
Setup Details Report

You use the Setup Details report to view a wide range of information about the system setup
configuration in Oracle Receivables. Displaying setup information in a single report lets you
easily anticipate and correct possible setup errors when running large processes such as
AutoInvoice.
Report Parameters
Batch Source ID: Choose from the list of values the name of the transaction batch source
for which you want to see system setup details.
Max GL Date: Enter a cutoff general ledger date (DDMONYYYY) for the report. The
Setup Details report will contain information about the periods before the date you enter.
Transaction Type (optional): If you would like to see setup details for one particular
transaction type, choose the type from the list of values. If you do not choose a
transaction type, the Setup Details report will provide setup information for every
transaction type defined in the AutoInvoice interface tables.
Process Invoices
Chapter 5 - Page 46
AR: Use Statement Site and Dunning Site Profiles
AR: Use Statement Site and Dunning Site Profiles

The value for this option can be set by the system administrator at the site, application, and
responsibility levels, but cannot be viewed by the user.
Process Invoices
Chapter 5 - Page 47
Agenda
Process Invoices
Chapter 5 - Page 48
Invoice Transaction Flow
Invoice Transaction Flow

In Oracle Receivables, you can review and correct invoice, debit memo, deposit, guarantee,
credit memo, on-account credit memo, and chargeback information for transactions you enter
manually or import into Receivables using AutoInvoice. This slide shows an overview of the
Invoice process and the four scenarios that can occur when transactions need correcting.
Correct Invoice
Underinvoice
Overinvoice
Invalid transaction
- Void
- Delete
Process Invoices
Chapter 5 - Page 49
Invoice Correction Methods
Invoice Correction Methods

Overinvoicing: Occurs when an invoice is generated for an amount that is greater than the
amount actually due. The difference between the amounts can be credited or refunded to the
customer, or the invoice can be updated.
Underinvoicing: Occurs when an invoice is generated for an amount that is less than the
amount actually due. The difference between the amounts can be debited against the customer,
or the invoice can be updated.
Invalid Transactions: Transactions that were created in error.
Process Invoices
Chapter 5 - Page 50
Overview of Corrections
Overview of Corrections
Update Invoice: Update the line, tax, and freight amounts on the original invoice before it is
posted.
Debit Memo: Enter a new transaction for additional amounts not invoiced on the original
invoice.
Adjustment: Adjust line, tax, and freight amounts on the original invoice.
Credit Memo: Credit a specific invoice.
On-Account Credit: Credit the customers account. This credit does not initially apply to a
specific invoice.
iReceivables: Disputes an invoice. Enter a requested credit amount or percentage for lines, tax,
freight, or total. Credit memo request is routed through the approval process.
Note: Debit memos are not directly linked to invoices, but you can enter descriptive
references. Adjustments are linked to invoices.
Process Invoices
Chapter 5 - Page 51
Overview of Corrections (Continued)
Process Invoices
Chapter 5 - Page 52
Updating Invoices
Updating Invoices
Examples of activity that prevent you from updating an invoice are applying a receipt, credit
memo, or commitment against an invoice, or creating an adjustment for the invoice. If the
system option Allow Changes to Printed Transaction check box is cleared, then you cannot
update an invoice that has been printed.
Use the Update Invoice procedure to correct for overinvoicing as well as underinvoicing.
Process Invoices
Chapter 5 - Page 53
Creating Debit Memos
Creating Debit Memos

Debit memos are like invoices, but they are usually created for additional charges. You can:
Enter debit memos in the Transactions window.
Import debit memos through AutoInvoice.
Enter debit memos in the same way as invoices, but use the Debit Memo transaction type.
Debit memos cannot reference a specific invoice number. Generally, invoices should be used
whenever possible.
Process Invoices
Chapter 5 - Page 54
Creating Adjustments
Creating Adjustments
(N) > Transactions > Transactions Summary > (B) Adjust
When you create an adjustment Receivables automatically verifies that it is within your
adjustment approval limits.
If within your assigned approval limit for the currency of that item, Receivables updates
your customers balance to reflect the adjustment.
If outside your approval limits, Oracle Receivables creates a pending adjustment with a
status of Pending Approval, which will need to be approved by a higher level employee
with the proper approval limit.
Process Invoices
Chapter 5 - Page 55
Applying Different Types of Credits
Applying Different Types of Credits

(N) > Transactions > Credit Transactions
Respond to overinvoicing with credit memos and on-account credits.
Credit memos affect specific invoices; on-account credits affect customer balances.
Credit memos are entered in the Credit Transactions window; On-account credits are
entered in the Transactions window with the transaction class of Credit Memo.
Credit memos cannot be unapplied or reversed from the invoice once they have been
created; On-account credits can be moved.
Process Invoices
Chapter 5 - Page 56
Credit Memo Options
Credit Memo Options

(N) > Transactions > Credit Transactions
Use the Credit Balance button to credit 100% of the remaining invoice value.
Use the Credit Lines button to credit a specific line on the invoice with the related tax if
applicable.
If you enter credits in the Transaction Amounts region, the tax, if applicable to that
invoice, needs to be adjusted separately. Receivables does not calculate the tax in relation
to the lines.
Enter credit memos for a specific invoice or invoice line.
You can create a credit memo against:
- Open invoices.
- Closed invoices.
Batch credit memos to help identify data entry errors.
Reference invoices with no remaining balances to refer credits back to the original
invoices.
Process Invoices
Chapter 5 - Page 57
Use the Receipts window to apply these credits to other items.

The transaction type of the invoice to be credited must allow over application in case of a
credit memo created for an invoice with an outstanding balance of zero.
Select an existing invoice in the Credit Transaction field in order to create the credit
memo.
Process Invoices
Chapter 5 - Page 58
Practice - Create a Credit Memo

Overview
In this practice you will create a credit memo.
Assumptions

Practice.
Tasks
Create a credit memo associated with your first transaction
1.
Navigate to the Credit Transactions window
2.
(N) Transactions > Credit Transactions
Create a credit memo using the following information.

Specify the first transaction you created
Reason: Discount
Line %: 5
Process Invoices
Chapter 5 - Page 59
Solution - Create a Credit Memo

Create a credit memo associated with your first transaction
1.
Navigate to the Credit Transactions window
(N) Transactions > Credit Transactions

Specify the first transaction you created
2.
(B) Find
3.
Accept all defaults

Reason: Discount
4.
(T) Transaction Amount

Line %: 5
5.
(I) Save
6.
(B) Complete
Process Invoices
Chapter 5 - Page 60
On-Account Credit Options
On-Account Credit Options

To apply a credit to a customers account rather than to an individual invoice:
Enter on-account credits in the Transactions window.
Select transaction class Credit Memo.
Process Invoices
Chapter 5 - Page 61
Reversing Sales Credits
Reversing Sales Credits

When crediting any part of an invoice, Oracle Receivables automatically reverses sales
credits assigned to the appropriate salespeople.
Partial credits against sales credits default proportionately, but can be updated as long as
the sum of sales credits for the line equals the original line credit amount.
The AR: Allow Update of Existing Sales Credits profile option determines whether a user
can update existing sales credits or if additional sales credit records need to be created to
maintain an audit trail.
Process Invoices
Chapter 5 - Page 62
Creating Refunds
Creating Refunds
You must create a refund when the customer has already paid an invoice and requests money
back instead of a credit.
Oracle Receivables does not create checks and therefore does not complete the refund process.
If Oracle Payables has been installed, you can use the features of the two systems to process
refunds.
You would use a clearing account to offset the Receivables account in Receivables and the
Payables account in Payables.
If you do not have Payables installed, create a credit memo/debit memo for accounting, and
then send to your check writing system.
Example: A refund for a customer who returns goods and wants a refund for $200.
Enter a credit memo in Oracle Receivables to reduce revenue and create an amount due
to the customer.
- Debit Revenue
200 / Credit Receivables
200
Enter a debit memo in Oracle Receivables to transfer the amount owed to the customer to
a clearing account.
Process Invoices
Chapter 5 - Page 63
- Debit Receivables
200 / Credit Clearing
200
Enter an invoice in Oracle Payables to clear the clearing account and create an accounts
payable for the customer.
- Debit Clearing
200 / Credit Payables
200
Issue a check in Oracle Payables to send the refund to the customer.
- Debit Payables
200 / Credit Cash
200
Process Invoices
Chapter 5 - Page 64
Voiding Transactions
Voiding Transactions
If there is no activity against a transaction, and if it has not been posted to the General Ledger
(GL), you can void the transaction.
Changing Complete Status by clearing the Complete check box of the transaction.
Updating Transaction Type:
Set up a transaction type with the Open Receivables and Post to GL check boxes cleared.
Assign this transaction type to the transaction that you want to void and complete the
transaction.
Deleting Incomplete Transactions
If the system option Allow Invoice Deletion check box is selected, you can delete
incomplete transactions from Oracle Receivables.
Select Delete Record from the Edit menu or Delete Record icon form the toolbar to delete
invoices from the Transactions Summary window. Save the record once you have deleted
the transaction.
Process Invoices
Chapter 5 - Page 65
Agenda
Process Invoices
Chapter 5 - Page 66
Transaction Types
Process Invoices
Chapter 5 - Page 67
Define Transaction Types
Define Transaction Types

Suggestion: To be able to void a debit memo, credit memo, onaccount credit or invoice,
define a Void transaction type with Open Receivables and Post to GL set to No. Then, as
long as there is no activity against the transaction and it has not been posted to your general
ledger, you can make it invalid by simply changing the transaction type to Void.
Process Invoices
Chapter 5 - Page 68
Deposit Transaction Type
Deposit Transaction Type

If you set the AR: Deposit Offset Account Source profile option to Transaction Type, then
Receivables uses the Offset Account that you specify here to derive the offset account for
deposits. Otherwise, Receivables uses AutoAccounting to derive the deposits offset account.
Process Invoices
Chapter 5 - Page 69
Agenda
Process Invoices
Chapter 5 - Page 70
Reports
Reports
(N) > Reports > Listing > (B) Single Request > (B) OK for the Incomplete Invoice Report.
(N) > Reports > Accounting > (B) Single Request > (B) OK for the Invoice Exception Report.
Process Invoices
Chapter 5 - Page 71
Printing Transactions
Printing Transactions
(N) > Print Documents > Invoices > Single Request > (B) OK
Transaction documents, such as invoices and credit memos must be printed for
distribution to customers.
Depending on a specific statement schedule, statements and consolidated billing invoices
are generated for distribution to customers.
Transactions can be printed in batches or a specific range.
Print the details of each tax line by setting a tax printing option, Itemize By Line, on the
customers profile class.
Optionally, you can elect not to print transactions.
Process Invoices
Chapter 5 - Page 72
Process for Printing Transactions
Process for Printing Transactions

Preview First
Submit the Invoice Print Preview Report to see transactions that will be printed.
Select a list of transactions by specifying values for the report parameters.
Then Print
Print transactions by batch.
Print transactions that have not been printed.
Specify a range of transactions to print.
Specify other parameters, such as Transaction type, class, or customer.
Note: Oracle Receivables automatically prints the tax registration number defined in the
system options on customer invoices. Oracle Receivables uses the tax printing option specified
for the customers profile class, if entered. Otherwise, Oracle Receivables uses the option
specified for the Invoice Printing System Option.
Process Invoices
Chapter 5 - Page 73
Practice - Print a Transaction

Overview
In this practice you will print a transaction.
Assumptions

Practice.
Tasks
Print invoices
1.
Navigate to the Standard Request Submission window
(N) Print Documents > Invoices
2.
Enter Parameters:
Order By: Transaction Number
Transaction Number Low: your first transaction number
Transaction Number High: your first transaction number
3.
Note Request Number: __________________________
View printed invoices

4.
View your printed invoices.
Process Invoices
Chapter 5 - Page 74
Solution - Print a Transaction

Print invoices
1.
Navigate to the Standard Request Submission window
(N) Print Documents > Invoices
2.
Single Request (B) OK

Name: Invoice Print Selected Invoices
3.
Enter Parameters:
Order By: Transaction Number
Transaction Number Low: your first transaction number
Transaction Number High: your first transaction number
4.
(B) OK
5.
(B) Submit
6.
Note Request Number: __________________________
7.
(B) No
View printed invoices

8.
(M) View > Requests (B) Find
9.
Select line indicating the concurrent program Invoice Print Selected Invoices that has a
parent id referencing your request.
10. (B) View Output
Process Invoices
Chapter 5 - Page 75
Using Consolidated Billing
Using Consolidated Billing

(N) > Print Documents > Consolidated Billing Invoices > Single Request > (B) OK
Use the Consolidated Billing Invoice program to print a single monthly invoice that includes
all of your customers transactions for that period.
Customers are flagged to receive consolidated billing invoices through their customer
profile class.
The invoice format can be detail or summary. Both the detail and summary format
presents invoice totals. The detail format lists all line items.
Note: If Sales Orders with different payment terms are imported through the AutoInvoice
Interface from Order Management, the invoice that are created still appear on the Consolidated
Billing Statement.
Process Invoices
Chapter 5 - Page 76
Practice - Print Consolidated Billing

Overview
In this practice, you will create and use a payment term using the last day of the month option for
consolidated billing invoices.
Create a payment term with last day of the month option.
Assign your payment term to a customer.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Your instructor will provide login information.
Replace XX with the number provided by your instructor or your initials.
Use Receivables, Vision Operations (USA) or comparable Super User Receivables

responsibility.
Tasks
1.
Create a payment term with last day of the month option.
2.
Assign your payment term to your customer
Process Invoices
Chapter 5 - Page 77
Solution - Print Consolidated Billing

Create a payment term
1.
Navigate to the Payment Terms window:
(N) Setup > Transactions > Payment Terms
2.
Enter the Name and Description of <XX> Last Day.
3.
Select the Last Day of the Month check box.
4.
Enter First Installment: Includes Tax and Freight
5.
Enter the terms 100 percent due to 30 days.
6.
(I) Save.
Assign Payment Term

7.
Navigate to the Customers window.
8.
Find your customer by entering the name in the name field and (B) Find.
9.
Select the Bill To site.
10. Select the Business Purpose tab and (B) Open.

11. Select your payment term <XX> Last Day for the list of values in the Payment Terms field.
12. (I) Save.
Process Invoices
Chapter 5 - Page 78
Practice - Correct Errors

Overview
In this practice, you will query and correct AutoInvoice errors using the new AutoInvoice
Exception Handling feature.
Query records in the Interface Exceptions window.
Correct the error in the Interface Lines window.
Run AutoInvoice.
View AutoInvoice Report.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Your instructor will provide login information.
Replace XX with the number provided by your instructor or your initials.
Use Receivables, Vision Operations (USA) or comparable Super User Receivables

responsibility.
Tasks
1.
Query records in the Interface Exceptions window.
2.
Correct the error in the Interface Lines window.
3.
Run AutoInvoice.
4.
View AutoInvoice Report.
Process Invoices
Chapter 5 - Page 79
Solution - Correct Errors

Query Records in the Interface Exceptions
1.
Navigate to the Interface Exceptions window:
(N) Control > AutoInvoice > Interface Exceptions
2.
Run the query: (K) Ctrl + F11.
3.
View the various errors.
4.
Select a record and view the error message in the Message field.
Correct the Error

5.
Navigate to the Interface Lines window.
6.
(B) Details.
7.
Place cursor into the LINE_TYPE field and select Show Field from the Folder menu to
select a corresponding field name. If for example, you are correcting the payment terms; you
would select TERM_NAME from the list.
8.
Select a valid value from the list of values.

Process Invoices
Chapter 5 - Page 80
9.
(B) Error.
Verify that the line has not more errors. If it does, correct those errors also.
Write down the Sale Order Number: __________________________
10. Save your work.
Run AutoInvoice
11. Navigate to the Run AutoInvoice window.
(N) Interfaces > AutoInvoice > Single Request > (B) OK
12. Select: AutoInvoice Master Program.

13. Enter parameters:
Invoice Source: Order Entry
Default Date: Todays Date
14. Your Sales Order Number (so each person gets a chance to see results.)
15. (B) OK > (B) Submit
The other option would be to schedule this process to run on a regular basis.
Process Invoices
Chapter 5 - Page 81
View AutoInvoice Report

Navigate to the Requests window.
(M) View > Requests > (B) Find > (B) View Output
The top portion of the AutoInvoice Validation Report is a summary of the AutoInvoice
Exception Errors for quick reference. This report helps determine what errors need to be
corrected and can be used a tool to research the errors before entering the Interface
Exception window.
Process Invoices
Chapter 5 - Page 82
Process Invoices
Chapter 5 - Page 83
Agenda
Process Invoices
Chapter 5 - Page 84
Event-Based Revenue Management
Event Based Revenue Management

When first evaluating an invoice for revenue recognition or deferral, Receivables uses
information from Credit Management to determine a customers creditworthiness, and uses
contract details from your contracts solution to determine if any nonstandard contract
contingencies exist.
Process Invoices
Chapter 5 - Page 85
Automated Process
Automated Revenue Management Process

This automated revenue management process helps you to comply with the strict revenue
recognition requirements mandated by US GAAP and International Accounting Standards.
Note: Automated revenue recognition is possible only for invoices with a batch source type of
AutoInvoice. This process is not available for transactions that you manually create via the
Transactions workbench or Copy Transactions window.
Additionally, even if you enable this automated revenue recognition process, you can always
use the Actions Wizard to manually adjust revenue.
Process Invoices
Chapter 5 - Page 86
Evaluating Invoices for EventBased Revenue Management
Evaluating Invoices for EventBased Revenue Management

Once this decision is made, AutoAccounting creates the actual accounting distributions, either
via AutoInvoice (for invoices without rules) or via the Revenue Recognition program (for
invoices with rules). The Revenue Management Engine does not analyze collectibility for
invoices that are assigned deferred accounting rules. To recognize revenue for an invoice with
a deferred accounting rule, use the Actions Wizard.
Note: The timing of revenue recognition does not impact the timing of recognition of taxes,
freight, and finance charges. Recognition of taxes, freight, and finance charges occurs when the
receivable is created.
Suggestion: You can query an invoice in the Transactions workbench at any time to review the
invoices accounting distributions, or run the Deferred Revenue Audit Trail Report.
Process Invoices
Chapter 5 - Page 87
Collectibility Requirements for Revenue Recognition
Collectibility Requirements for Revenue Recognition

If an invoice satisfies these requirements, then the Revenue Management Engine immediately
recognizes revenue (for invoices without rules) or recognizes revenue according to the initially
assigned accounting rules (for invoices with rules).
If an invoice does not satisfy, or only partially satisfies, these requirements, then the Revenue
Management Engine immediately defers revenue.
The extent of the revenue deferral, and subsequent timing of revenue recognition, depends on
whether the unmet collectibility requirements are related to either the header or line level of an
invoice.
Process Invoices
Chapter 5 - Page 88
How Collectibility Requirements Relate to Invoices
Process Invoices
Chapter 5 - Page 89
Applying Receipts and EventBased Revenue Management
Applying Receipts and EventBased Revenue Management

If Receivables bases revenue recognition on receipt application, then the total amount of
revenue that is recognized can never exceed the original amount due on the invoice line, less
any applicable credit memos. If you later need to reverse a receipt after application, then
Receivables automatically moves the amount of the reversed receipt back to an unearned
revenue account.
Note: If you are applying a receipt to an invoice with rules, but you havent yet run Revenue
Recognition, then Receivables automatically runs Revenue Recognition for that invoice only.
Process Invoices
Chapter 5 - Page 90
Agenda
Process Invoices
Chapter 5 - Page 91
XML Receivables Documents
XML Messages
XML invoice documents always use this XML message:
Process Invoice: This XML message contains information for your customers invoices,
debit memos, credit memos, chargebacks, and deposits.
In addition, your customers can set up their systems to send this XML message back to you:
Confirm Business Object Document (Confirm BOD): Your customer can send this
XML message to tell you if your XML invoice document import was successful. This is the
standard OAG Confirm BOD XML message.
Process Invoices
Chapter 5 - Page 92
XML Invoices Process Flow
Process Invoices
Chapter 5 - Page 93
XML Invoices Process Flow
Process Invoices
Chapter 5 - Page 94
Sending XML Invoice Documents
Sending XML Invoice Documents-Other Prerequisites

You must process and transfer XML invoice documents before you run the concurrent
programs to print invoices. The Document Transfer program does not select receivables
transactions that the Print Invoice program already printed.
Process Invoices
Chapter 5 - Page 95
Confirming the Import Status of XML Invoice Documents
Confirming the Import Status of XML Invoice Documents

You and your customer can optionally implement any messages and activities that meet your
needs.
If you have set up the Process Invoice XML message for automatic receipt confirmation in
XML Gateway, then when your customer receives the invoice message, the customer sends a
Confirm BOD message back to your system.
These messages confirm the import status of an invoice document and provide reason codes for
import failures. The Oracle Payables import statuses and reason codes are mapped to
confirmation actions in Receivables.
Process Invoices
Chapter 5 - Page 96
XML Invoice Documents
Process Invoices
Chapter 5 - Page 97
Reviewing and Retransmitting XML Invoice Documents
Process Invoices
Chapter 5 - Page 98
Agenda
Process Invoices
Chapter 5 - Page 99
Promised Commitment Amounts
Reserve Commitment Balances

When the order is invoiced via AutoInvoice, Order Management or another feeder system
passes the promised amount to Receivables.
Receivables, then adjusts the invoice and reduces the deposit balance by the lesser of the
promised amount, the commitment balance, or the remaining amount due on the invoice.
Depending on the deposits transaction type, you can choose to include tax and freight when
applying a deposit to a transaction.
Process Invoices
Chapter 5 - Page 100
Summary
Process Invoices
Process Invoices
Bill Presentment Architecture

Chapter 6
Chapter 6 - Page 1
Chapter 6 - Page 2
Objectives
Chapter 6 - Page 3
Bill Presentment Architecture Overview
Bill Presentment Architecture Overview

BPA provides template-based configuration of bills for online presentment and printing,
including content selection, layout design, drilldown and grouping capability, and billing
template assignment. In identifying other sources of data, the physically presented bill is no
longer limited to information contained within Oracle Receivables. By separating bill
presentment from transaction accounting, Oracle BPA allows for more understandable and
comprehensive bills, increasing the likelihood and timeliness of bill payment.
Chapter 6 - Page 4
BPA Framework
BPA Processes
You then design billing templates, choosing the layout and content to determine how you want
billing data to appear in an online or printed bill, and assign the templates to customers or
customer categories. You can print bills individually or in batches from your billing templates
created within BPA or uploaded from external sources.
Your customers can view summarized billing information and drill down using hyperlinks to
detailed billing information and other related details necessary to understand and pay the bill.
Chapter 6 - Page 5
BPA Process Flow
BPA Process Flow

You can:
Design layout and select content for a bill
Display on bills information that is not stored in Oracle Receivables
Create hyperlinks that enable access to related billing information
Display summary and child lines
Provide online drilldown to invoice line details
Assign bill formats to specific customers or userdefined customer categories
Print invoices
Preview billing templates using realtime data
You accomplish this by first configuring the BPA architecture, and then defining templates and
assignment rules.
Chapter 6 - Page 6
Creating Templates
Defining Templates
Using the desktop icons, you can easily create or modify templates graphically. Content areas
can be split into as many areas as needed to create the desired layout. Content areas can be
moved, duplicated, formatted, updated, or deleted.
When you create or customize templates, you design the layout and contents of a primary bill
page and, if needed, a details page. The primary bill page has three content areas:
Header
This area includes information typically seen at the top of an invoice, such as the companys
logo, invoice number, date, customer name, billto address, shipto address, and terms.
Lines and Tax
This area contains the billing items, and can optionally include tax, for all transactions included
in the bill. This section typically includes the item number, item description, quantities, and
cost amounts.
Footer
This area includes information typically available at the bottom of an invoice, such as the total
for the bill, aging, additional notes to the customer, and other messages. You can create a
Chapter 6 - Page 7
details page for a template if your supplementary data source has a registered details page
view. The details page contains supporting billing information from your supplementary data
source such as Oracle Service Contracts.
Note: After creating your billing template, you can preview and print it using actual customer
data.
Chapter 6 - Page 8
Defining Assignment Rules
Defining Assignment Rules

When a user selects a bill to view or print, BPA applies the online or printed rules, in the order
you specify, to determine which template to use.
For example, you can define a rule to use a template to display bills that are more than
$10,000. Then, define a second rule to use a different template to display bills that are $10,000
or less.
You can assign different templates to be used for online bills and printed bills. You can also
specify different rule order for online and printed bills.
Note: For information on implementing Bill Presentment Architecture and setting system
profile options, please refer to the Oracle Receivables User Guide, Release 11i, Part No.
A8083805.
Chapter 6 - Page 9
Data Retrieval
Chapter 6 - Page 10
Registering Data Sources
Registering Data Sources

To make content items and hyperlinks available for your template designers to include in a
template, you must register and enable the supplementary data source where the content items
reside.
Oracle Receivables is already registered in BPA and enabled for use. It is the primary data
source. All other data sources are supplementary data sources. Other Oracle applications, such
as Oracle Order Management and Oracle Service Contracts, are registered in BPA, but you
must first enable them for use.
If you want to use an application or other source that is not seeded in BPA as a source of
content items, then you must register and enable the source as a data source. You can register
any application that interfaces billing transactions to Receivables. Applications that can be
registered include Oracle applications, third party applications, and legacy systems.
If you want a template to include a details page, then you must register a supplementary data
source and register a details page view to provide content items.
Chapter 6 - Page 11
Enabling Data Sources
Enabling Data Sources

To change the status of a data source, select a data source from the list of registered data
sources. From the list of values, select Mark as Enabled and click Go. After a data source is
enabled, you can view its details, but you cannot make any changes.
Note: Oracle Receivables is always enabled. Oracle Order Management and Oracle Service
Contracts must be enabled before you can use them as supplementary data sources.
You can disable a data source at any time, with the exception of Receivables. You cannot
disable Receivables as a data source because it provides the basic transaction line billing
information for Bill Presentment Architecture. You can update, synchronize flexfields, and
delete a data source only if its status is disabled. You can also view disabled data sources.
Warning: Do not disable a data source while creating or updating a template, or while
assigning templates to rules.
Chapter 6 - Page 12
Viewing Data Sources
Viewing Data Sources

When viewing a data source, you can sort its associated views by clicking on a column
heading. You can also drill down to view the details of the associated views, including the
database view name and the content items for the view.
Chapter 6 - Page 13
Creating Database Views
Creating Database Views

After registering new data sources, you must complete your BPA configuration by creating any
specific database views required, and then registering those views as data source views in
BPA. This lets you access additional billing information from the new data sources.
Some database views from Oracle Receivables and seeded applications, such as Oracle Service
Contracts and Oracle Order Management, are seeded as data source views in BPA.
You can create other database views for these applications to provide any additional data
required, but you must then register them as data source views in BPA.
There is no restriction on the number of views which can be created. However, lines, tax, and
the detail pages display area can have only one view.
Chapter 6 - Page 14
Registering Data Source Views
Registering Data Source Views

Before you can register a view, the status of the data source must be disabled.
To register a data source view, first select a display area for the view and then select a database
view.
Note: BPA supports registration of one Lines and Tax data source view, one Details Page data
source view, and multiple Header and Footer data source views.
Select the content items to be available for creating templates
Selecting a View
To register a data source view for a data source, first identify the display area for the view, and
click Register.
Then, use the search function to find the database view that you want to use as a source for
content items. For each view, enter a description and display name for the view. Create a
display name that easily identifies the source of the content items that can be selected from the
view. Later, the template designer selects content items based on this views display name.
Selecting Parameters
You can set parameters to retrieve specific values when a bill is displayed at run time.
Chapter 6 - Page 15
Viewing Data Source Views
Viewing Data Source Views

First, you open the View Data Source page by selecting a data source name.
Then select the view display name to open the View page. This page lists all items available in
a view.
Items are shown as:
Used in templates: Item is checked and check box is grayed out.
Available for use in templates: Item is checked and check box is active.
Not available: Item is not checked.
You can also access the View page by clicking the Views icon.
Note: For information on configuring hyperlinks, please refer to the Oracle Receivables User
Guide, Release 11i, Part No. A8083805.
Chapter 6 - Page 16
Template Management
Template Management
You use Template Management to create, update, and manage templates to present bills online
and for printing.
Using the icon tools, you can graphically:
Modify templates (duplicate and update)
Create templates
Create custom content items
Format text and layout
Preview templates using existing customer transactions
Upload external templates
Delete templates
Chapter 6 - Page 17
Modifying Templates
Modifying Templates
If you do not want to build an entirely new template, then you can copy an existing template
and modify it to suit your requirements. Select the Duplicate icon next to the template you
want to copy and enter a new template name and description.
After duplicating an existing template, you can select a different supplementary data source. In
the new template, content items from the old supplementary data source are removed. For
example, if you copy an Oracle Service Contracts (OKS) template and change the
supplementary data source to Oracle Order Management, the content items specific to OKS are
deleted from the new template.
If you change the tax format in a duplicated template, any content items related to original tax
format are deleted. For example, if you change the tax format from Custom to Oracle
Receivables Tax Printing Option, the content items specific to the Custom format are removed.
Chapter 6 - Page 18
Creating a New Template
Chapter 6 - Page 19
Uploading External Templates
Uploading External Templates

You can upload external files to be used as billing templates for printed bills instead of creating
a new template.
External templates can be any PDF or RTF file.
You can upload multiple language versions of the file as needed for a single template. After
uploading the file, you must map each field name in the template to a content item from a data
source view in BPA.
You cannot create grouping or drilldown or a details page for a billing template created from
an external file.
Supports invoice printing using external customer-provided templates.
Option to display itemized tax.
Chapter 6 - Page 20
Assigning Templates
Assigning Templates
Attribute
An existing predefined content item that is available in the Header area from Oracle
Receivables, the primary data source.
Condition
A matching state such as equals, is greater than, or is less than or equal to.
Value
A userdefined value that occurs on your invoices for the content item selected as the attribute.
You can select a value from the list of values, or enter a value. When you select a bill to view
online or print, BPA reviews the rules in the order you specify until it finds a match, and then
uses the template associated with the rule to format the bill.
BPA supports assignment of billing templates to different customers or customer categories
based on user-defined criteria. The ability to define assignment rules and order them by
preference, rules applied based on ordering and bill creation dates, choice of different
assignments and ordering for online and printed bills, and default templates and assignment
rule provided are some of the features of BPA.
Chapter 6 - Page 21
Defining Template Rules
Defining Template Rules

In the example shown in the slide, for ABC Company:
If the Bill To City value on the invoice is Seattle, then you want to use Template ABC1.
If the Bill To City is any city other than Seattle, then you want to use Template ABC2.
To do this, you can define one rule called ABCSeattle, as shown in the upper table, and assign
it to Template ABC1.
Note: When you order the rules, list ABCSeattle before the ABC rule.
Default Invoice Rule
BPA provides a default rule, the Default Invoice Rule. This rule assigns the Default Invoice
Template to present bills. If no other rule can match attributes and content item values, then the
default rule applies and BPA uses the default template to present the bill. This is true for
invoices for all supplementary data sources.
Note: If BPA does not find a match in any of the rules for an invoice with a supplementary
data source other than None, then it reviews the rules associated with the supplementary data
source None until a match is found.
Chapter 6 - Page 22
You cannot update the Default Invoice Rule. If you want to change the template assigned to
this rule, then create a new default rule with no attributes and order it before the seeded default
rule.
Chapter 6 - Page 23
Creating a New Assignment Rule
Creating a New Assignment Rule

Note: If you are adding the first rule for a data source, the Rule Order section will not be
displayed.
You can create as many rules as you need to assign templates to invoices. Each rule can be
composed of one or more attribute matching criteria. You can specify that a bill must match at
least one attribute criteria, or must match all criteria, in order to be displayed by the template
associated with the rule.
You can create a rule for any enabled data source. You must select a supplementary data
source or select None.
Chapter 6 - Page 24
Selecting Attribute Matching Criteria
Selecting Attribute Matching Criteria

You select an attribute from the Add Attribute list of values and click Go. BPA filters the list
of available conditions for the selected attribute.
Next, you select the condition for the rule.
Then, you add the attribute values for the rule.
Depending on the type of attribute used in the rule, you can select a value from a poplist, use
the flashlight to search for an attribute value, or enter a value.
For attributes with numerical or date values, such as Billing Date or Outstanding Balance, you
enter a value.
Chapter 6 - Page 25
Selecting Conditions for Rules
Selecting Conditions for Rules

The matching conditions available are:
Equals
Greater than, greater than or equal to, less than, and less than or equal to
Starts with
Contains
Chapter 6 - Page 26
Assigning a Template to a Rule
Assigning a Template to a Rule

When you assign a template to a rule, you enter a range of invoice dates. The bill creation date
corresponds to the date when the invoice was created in Receivables.
A bill creation date must be January 1, 1970 or later.
Bill creation dates cannot overlap within a rule. For example, if you assign two templates,
Template A and Template B, to a rule, then the bill creation dates for Template A cannot
overlap the bill creation dates for Template B.
The Bill Creation From date must be earlier than or equal to the Bill Creation To date.
Note: To assign a template to a rule, you must first click Add Another Row.
Chapter 6 - Page 27
Reordering Rules
Reordering Rules
If no match is found for a particular supplementary data source, the rules for the supplementary
data source None are checked until a match is found. The Default Invoice Rule applies if no
other matches are found.
To reorder rules, select the Reorder button available on the Assignment Rules page. You use
the shuttleboxes for online bills and printed bills to change rule order. If an external template is
assigned to a rule, then the rule appears only in the Print Bill Available Rules shuttlebox.
Viewing Online Bills
Internal users and external customers can view bills online using Oracle Receivables, Oracle
iReceivables, Oracle Collections. or other calling application. When a user selects a transaction
number, or icon if available, the assignment engine in BPA determines which template to use
to display the bill.
When viewing a bill, all the features and functionality of BPAs Interactive Preview, such as
drilldown to invoice details, or iReceivables, such as creating a dispute, printing bills, or
making a payment, are available to the user.
Chapter 6 - Page 28
Print Management
Print Management
When you create a template, you assign a page setup that determines the page size, margins,
and font used for the printed invoice. When you run a print request, BPA generates a PDF file
for each group of invoices, which is stored as the output file of the print request concurrent
program. Please note that BPA also generates a PDF file for a bill when you click Print in
Interactive Preview for a template.
Bill Presentment At Request Group
The Bill Presentment All request group is associated with responsibilities for BPA and contains
two concurrent programs:
Invoice Print BPA Master Program
Generate Stylesheet for BPA Templates
Invoice Batch Printing
BPA supports batch printing of invoices:
Batch print request submission and monitoring via Oracle BPA User Interface
Batch print request submission and monitoring via Oracle Receivables
Generation of printed invoice in PDF format
Chapter 6 - Page 29
Submitting Print Requests
Chapter 6 - Page 30
Creating and Updating Page Setups
Creating and Updating Page Setups

When you create a template in Template Management, you assign a page setup to format
invoices printed using that template. Seeded page setups include A4, Legal, and Letter. You
can modify seeded page setups.
Chapter 6 - Page 31
Summary
Chapter 6 - Page 32
Credit Management
Chapter 7
Credit Management
Chapter 7 - Page 1
Credit Management
Credit Management
Chapter 7 - Page 2
Objectives
Credit Management
Chapter 7 - Page 3
Agenda
Credit Management
Chapter 7 - Page 4
Set Up Oracle Credit Management
Set Up Oracle Credit Management

Credit policies are uniquely identified by the type of credit reviews that you perform at your
enterprise, as well as by the credit relationships that you have with your customers and
prospects. These two dimensions, known as the credit review type and credit classification,
constitute the foundation upon which Oracle Credit Management is based.
To set up Credit Management, you must:
Define credit analysts
Assign credit analysts to accounts
Define Credit Management lookups
Define Credit Management system options
Define scoring models
Assign automation rules (optional)
Define checklists
Verify usage rules
Define the credit hierarchy for your customers and prospects
Credit Management
Chapter 7 - Page 5
Define Credit Analysts
Define Credit Analysts

Before you can define credit analysts in Resource Manager, you must first define them as
employees in Oracle Human Resources Management System (HRMS). Later, when you are
ready to define your credit analysts, you import employees from HRMS into Resource
Manager and assign roles.
After you define a credit analyst, you can modify any of the analysts information, except the
employee and user names.
Note: You can assign the credit manager role to a credit analyst. A credit manager has access
to setup functionality.
Credit Management
Chapter 7 - Page 6
Assign Credit Analyst to Accounts
Assign Credit Analyst to Accounts

To assign a credit analyst to a customer or account, you update the assigned profile class. If the
applicant does not have an assigned credit analyst, or is a prospect, then any credit review for
that applicant is routed to the Credit Scheduler for analyst assignment
Credit Management
Chapter 7 - Page 7
Define Lookups
Define Lookups
For example, to identify an applicants potential credit risk, you must select a credit
classification, if not previously assigned, when entering a credit application. The credit
classification describes the type of credit relationship that you have with the applicant.
Credit Management provides you with High Risk, Low Risk, and Moderate Risk, but you can
optionally define new credit classifications to fit your business needs.
You use the Oracle Receivables Lookups window to define any additional lookups that you
require.
Credit Management
Chapter 7 - Page 8
Define System Options
Credit Management
Chapter 7 - Page 9
Define Scoring Models
Define Scoring Models

A scoring model consists of a group of data points, with scored ranges and a relative weighting
factor for each data point. During a credit analysis, Credit Management calculates a score from
0 to 100, with 0 representing the most risk and 100 representing the least risk.
The View Scoring Models page displays a table of all existing scoring models. You can view
and update the scoring models by clicking the respective inline icons, or you can define a new
scoring model.
You can assign a default scoring model to a credit checklist. Alternatively, you can generate
various whatif scenarios during a credit review by selecting different scoring models from
the case folder.
Credit Management
Chapter 7 - Page 10
Assign Automation Rules
Assign Automation Rules

Automation rules base credit decisions upon the credit score that the assigned scoring model
calculates. For each automation rule, you define recommendations for a related credit score
range. For example, if the credit score is below 50, you might want to automatically reject a
credit request.
The Automation Rules page provides you with an overview of all scoring models for which a
set of automation rules is defined. You can view and update existing sets of automation rules
by clicking the respective inline icons, or you can create a new set.
Note: This step is optional.
Credit Management
Chapter 7 - Page 11
Credit Checklist
Credit Checklist
For example, when a high risk customer seeks to increase its credit limit with your enterprise,
your credit policies might dictate a conservative approach until this customer relationship is
more established. In this scenario, you would use a conservative checklist to determine whether
to grant additional credit and what the credit limit should be.
The flexible setup procedures that follow reflect Oracle Credit Managements ability to meet
the demands of your enterprises particular credit policies.
Credit Management
Chapter 7 - Page 12
Credit Usage Rule Sets
Verify Credit Usage Rule Sets

For example, if a customer is assigned the Default profile class with a credit usage rule set that
includes USD, EUR, and CAD, then any transactions of those currencies are included in that
customers case folder for data points such as Count of Open Invoices or Amount of Open
Invoices.
In Oracle Order Management, credit usage rule sets define the set of currencies that will share
a predefined credit limit during the credit checking process, and enable the grouping currencies
for global credit checking.
Credit Management
Chapter 7 - Page 13
Define Credit Hierarchies

To provide global credit limits that are shared by some or all entities within a complex,
multinational organization, you can define credit relationships between parties using Oracle
Trading Community Architecture Relationship Manager.
You can define a credit hierarchy of parties, party relationships, hierarchy levels, accounts, and
account sites. Typically, the party object and party subject in a credit relationship represent a
parent and child, or HQ and division hierarchy. For each entity in the hierarchy, you can view
credit information, such as credit hold status, credit limits by currency, and credit review cycle.
Using Relationship Manager, you assign to your entities an existing relationship type, such as
Global Ultimate, or your own userdefined Credit Management relationship type. You then
link the relationships to Credit Management by assigning the relationship type to the AR:
Credit Hierarchy Type profile option. When you conduct a credit review for an entity that has
hierarchical relationships, Credit Management consolidates and displays all data for the entire
hierarchy.
Credit Management
Chapter 7 - Page 14
Define Customer Profile Classes
Define Customer Profile Classes

You can also define amount limits for your finance charges, dunning, and statements for each
currency in which you do business. Define your standard customer profiles in the Customer
Profile Classes window. These profiles contain generic options you can use to group your
customers into broad categories.
For example, you might define three categories: one for prompt paying customers; one for late
paying customers with high finance charge rates; and a third for customers who mostly pay on
time, with discount incentives for early payment.
You can also use the profile class DEFAULT, which Oracle Receivables provides.
Credit Management
Chapter 7 - Page 15
Customer Profile Classes: Credit Profile Tab
Credit Profile Tab in Customer Profile Classes form

Periodic Review Cycle
Defines the frequency of automatic reviews for a customer.
Note: Eligible reviews are processed via the Periodic Review Cycle concurrent program.
Credit Analysis
The credit analysis automatically is assigned to all parties, accounts, and sites which have
this profile class.
Credit Tolerance
The percentage upon which credit exposure is exceeded before an order will be placed on
credit holds. Credit holds automatically submit a credit request.
Credit Management
Chapter 7 - Page 16
Use Customers-Standard
Customers-Standard Window
If a profile is assigned to a customer and an address of the same customer, the options set at the
address level take precedence over those set at the customer level.
For statement site and dunning site profile amounts, however, Receivables uses the options at
the address level only if you set the AR: Use Statement Site & Dunning Site Profiles profile
option to Yes.
Credit Management
Chapter 7 - Page 17
Agenda
Credit Management
Chapter 7 - Page 18
Process Credit Reviews
Credit Review Process

During the credit review, the Credit Management Application workflow manages the process
flow of credit data collection and analysis, as well as the implementation of credit decisions. In
addition, Credit Management provides various tools that you can use to determine if your
credit policies are effective.
Credit Management
Chapter 7 - Page 19
Initiate a Credit Review
Initiate a Credit Review

For example, if a sales order is put on credit hold, then the credit hold process in Oracle Order
Management passes this information to the Credit Review Request API, which automatically
initiates a credit review. Other events, such as a quarterly review, can also trigger a credit
review.
Note: You can also use the Credit Review Request API to initiate a credit review from a non
Oracle system.
Credit Management
Chapter 7 - Page 20
Collecting Credit Data
Collecting Credit Data

The credit checklist indicates which data points are required for different types of credit
analyses and decisions, and can optionally indicate which scoring model will be used for the
review. In this way, the checklist enforces your enterprises credit policies.
If the checklist identifies required data points that already exist within Oracle Applications or
are calculable, such as available credit, aging, and so on, then Credit Management
automatically inserts that information directly into the credit application and case folder. If the
checklist requires data points that must be manually supplied, such as bank and trade
references, then a credit analyst must enter the required data into the credit application or case
folder.
Credit Management
Chapter 7 - Page 21
Analyzing Credit Data
Analyzing Credit Data

The Credit Analysis data pages comprise the universe of data points for the applicant. The
Credit Analysis data pages that are available off of the Analysis tab include:
Credit Analysis: Case Folder
Credit Analysis: Credit Summary
Credit Analysis: Billing and Payment Details
Credit Analysis: Aging Details
Credit Management
Chapter 7 - Page 22
Making a Recommendation
Making a Recommendation
Generally, a recommendation is specific to the type of review that was just concluded. For
example, a credit review that an order hold originally initiated would most likely result in a
recommendation to:
Increase the credit limit to accommodate the amount of the order and remove the order
from hold.
Deny the request for an increase in the credit limit and leave the order on hold.
Credit Management
Chapter 7 - Page 23
Implementing the Recommendation
Implementing the Recommendation

Receivables automatically implements the recommendation after all required parties have
approved it.
For example, if the recommendation indicates that the order should be removed from credit
hold, then the workflow will call the Remove Credit Hold API and pass the necessary
information, such as order ID, account ID, and so on, to initiate the process.
Credit Management
Chapter 7 - Page 24
Agenda
Credit Management
Chapter 7 - Page 25
Credit Management Application Workflow
Credit Management Application Workflow

For each credit review, the workflow checks the automation rules that you previously defined:
If the credit review is automated, then the workflow attempts to automatically make and
implement credit decisions without user intervention.
If the workflow stops due to conditions such as missing data, then the workflow routes
notifications to the appropriate credit analyst for resolution.
If a credit analyst was never assigned because the credit review was automated, then the
workflow notifies the user with the Credit Scheduler responsibility that a credit analyst
must be assigned. The Credit Scheduler can select the credit analyst to be assigned from
the List of Values. The assigned credit analyst then receives a notification that they have
a credit request in their queue.
If the credit review is not automated, then the workflow assigns the credit review to the
appropriate credit analyst and notifies the analyst about the assignment.
With unautomated credit reviews, credit analysts make recommendations, such as
increasing or decreasing the credit limit, after performing the credit analysis.
Credit Management
Chapter 7 - Page 26
Oracle Approvals Management (AME)
Oracle Approvals Management (AME)

Once you define the rules for a given application, the Oracle Approvals Management Engine
manages the approvals for that applications transactions.
If approval is required, then the workflow routes notifications according to the approval
hierarchy:
If the recommendation is approved by the appropriate personnel, then the workflow
automatically implements the decision.
If the recommendation is rejected as it is routed through the approval hierarchy, then the
workflow sends notifications to the appropriate personnel and updates the case folder.
If a credit analyst cannot be identified, then the workflow notifies the person assigned to the
Credit Scheduler role that a credit analyst assignment is required. The Credit Scheduler is a
role used in Credit Management to assign credit tasks to credit analysts.
Credit Management
Chapter 7 - Page 27
Agenda
Credit Management
Chapter 7 - Page 28
Review Credit Management Performance
Review Credit Management Performance

On the Performance tab, you can access simple views into the workload and effectiveness of
the checklists and scoring models that you have set up and used in credit reviews, including:
Credit Workload Quick Check
Top 10 Customer Credit Exposure
Customer Trends (Pay Trend)
Checklist Usage by Month
Scoring Model Usage by Month
Credit Management
Chapter 7 - Page 29
Agenda
Credit Management
Chapter 7 - Page 30
Use Relationship Manager

Relationship Manager lets you easily build, view, and edit relationships between entities. Using
Relationship Manager, you can:
View a single party and all its relationships
Create new relationships and edit existing relationships
Focus on a particular portion of a hierarchy and edit the hierarchical structure
Credit Management
Chapter 7 - Page 31
Identify a Credit Hierarchy
Use Relationship Manager

Using Relationship Manager, you assign to your entities an existing relationship type, such as
Global Ultimate, or your own userdefined Credit Management relationship type. You then
link the relationships to Credit Management by assigning the relationship type to the AR:
Credit Hierarchy Type profile option.
When you conduct a credit review for an entity that has hierarchical relationships, Credit
Management consolidates and displays all data for the entire hierarchy.
Credit Management
Chapter 7 - Page 32
Summary
Credit Management
Chapter 7 - Page 33
Credit Management
Chapter 7 - Page 34
Implement Customer
Invoicing
Chapter 8
Implement Customer Invoicing
Chapter 8 - Page 1
Chapter 8 - Page 2
Objectives
Chapter 8 - Page 3
Agenda
Chapter 8 - Page 4
Required Setup Steps for Transactions
Required Setup Steps for Transactions

Before you can use customer invoices, the following must be set up:
Customers: Define Customers including Bill To and Ship To address for transaction
processing.
Receivables Transaction Types: Assign to transactions. Transaction types add default
information to the transactions..
AutoAccounting: Specifies the General Ledger accounts of transactions that you enter
manually or import using AutoInvoice.
Payment Terms: Determine the payment schedule and cash discount information for
customer invoices, debit memos, and commitments.
Transaction Sources: Assign to transactions to control transaction and batch numbering
and provide default information.
Remit-to addresses: Informs customers where to send payments.
System and Profile Options: Provides default values for some Receivables operations,
such as how Receivables processes data and controls the actions users can perform.
Chapter 8 - Page 5
Receivables Transaction Types
Receivables Transaction Types

(N) > Setup > Transactions > Transaction Types
You must set up transaction types before you can enter invoices.
Transaction types can be used to set defaults and control activities on a transaction.
For each transaction type, you can select only one of seven transaction classes.
Transaction types determine:
Transaction Class. The Transaction Class determines:
- If the transaction can be posted to the General Ledger (GL).
- If the transaction is an open receivable.
- If tax must be calculated, or freight can be entered.
- The default credit memo type for an invoice.
- The default invoice type for a commitment.
Creation Sign: For the creation sign enter Positive, Negative, or Any Sign for the initial
sign of the transaction.
Chapter 8 - Page 6
Note
For guarantees and deposits, the creation sign must be Positive.
Operating Unit for your responsibility is displayed. You cannot change this value.
Chapter 8 - Page 7
Using Natural Application
Using Natural Application

Applications are applied differently depending on the values selected for the transaction type
options Natural Application Only and Allow Overapplication.
Natural Application Only Selected, Allow Overapplication Clear.
- Oracle Receivables allows any application that reduces the transaction amount
toward or to zero without changing the sign of the transaction.
- For example, if the transaction amount is +$500, Oracle Receivables allows the
applications as shown in the top section of the diagram.
Natural Application Only Clear, Allow Overapplication Selected or Clear.
- Oracle Receivables allows any application that reduces or increases the transaction,
even if the application changes the sign of the transaction as shown in the bottom
section of the diagram.
Chapter 8 - Page 8
AutoAccounting
AutoAccounting
(N) > Setup > Transactions > AutoAccounting
Oracle Receivables provides flexible setup for transaction accounting by using
AutoAccounting and determines the General Ledger (GL) accounts for invoices by
determining a value for each segment of the accounting flexfield.
When setting up AutoAccounting, rules define how Oracle Receivables should derive the
value for each segment. This can either be a constant value or a table.
For each account type, define the flexfield segments by selecting a table name or entering
a constant value. The tables that can be used for segment values are Transaction Types,
Salesperson, Customer - Bill To, Standard Line, Freight (for Freight Account only), and
Tax Code.
Chapter 8 - Page 9
Payment Terms
Payment Terms
(N) > Setup > Transactions > Payment Terms
Define standard payment terms to determine payment schedules and percentages of discounts
allowed.
The formula used to determine the amount due is:
- Amount Due = Relative Amount/Base Amount x Invoice Amount.
- For example: Relative Amount = 60%/Base Amount = 100% would be 60% of
Invoice amount.
Select the Credit Check check box to trigger Order Management credit check.
Enter the number of days before the due date that the invoice should be printed.
Allow discounts on partial payments by selecting the Allow Discount on Partial
Payments checkbox.
Specify how to allocate tax and freight on invoices with split terms: in the first
installment, or prorated across all installments.
Select the Last Day of Month check box or a specific day to send consolidated invoices.
Chapter 8 - Page 10
Transaction Sources
Transaction Sources
(N) > Setup > Transactions > Sources
Transaction sources are used to control transaction batching, numbering, and specify default
transaction types.
Select validation options for imported transactions.
Assign batch sources to invoices, debit memos, commitments, credit memos, and onaccount credits.
When setting up the Credit Memo Workflow, assign a Manual source.
Select the Copy Document Number to Transaction Number check box to use the same
value for both the document number and the transaction number for transactions assigned
to this source. You must check the box if using Gapless document sequences.
Note: For AutoInvoice feeds from the Service Contracts module, you must use the seeded
Transaction Source of OKS_CONTRACTS. For more information on Transaction Sources and
Autoinvoicing, refer to the Oracle Receivables User Guide or 11i Order to Cash: Process
Invoices Using AutoInvoice.
Chapter 8 - Page 11
Remit-to Addresses
Remit-to Addresses
(N > Setup > Print > Remit-to Address
Oracle Receivables automatically assigns all customers with bill-to addresses in the states and
countries defined in the Remit-To Addresses window to corresponding remit-to addresses.
Remit-to addresses can be printed on invoices to let customers know where to send
payment.
Assign each remit-to address to one or more state, country, and postal code combination.
Chapter 8 - Page 12
System Options Relating to Transactions
System Options Relating to Transactions

Header Level Rounding: Assigning a special account for rounding differences when
converting foreign currency transactions to your functional currency. The Header Level
Rounding is enabled on the Accounting tab. Caution: It cannot be disabled once the box
has been selected and Header Level Rounding adds an additional line to every transaction
regardless of the currency.
Automatic Journal Import: Automatically import the batches you transfer by checking
this box on the Accounting tab. The value becomes the default value on the Run GL
journal Import field in the Run General Ledger Interface window.
Allow Change to Printed Transactions: Allow updates to printed transactions by checking
this box on the Trans and Customer tab.
Allow Transaction Deletion: Allow transaction to be deleted from Receivable after it has
been saved by checking this box on the Trans and Customer tab. Caution: Do not enable
this option if using gapless numbering of transactions.
The following System Options were migrated from Profile Options since 11i.AR.H:
Chapter 8 - Page 13
Document Number Generation Level: Determines at what point Receivables

generates a document number for your transactions.
- Show Billing Number: Prints a unique billing invoice number when printing
consolidated billing invoices.
Note: There are system options relating to AutoInvoicing as well. For more information
on System Options relating to Autoinvoicing, refer to 11i Order to Cash: Process
Invoices Using AutoInvoice.
Chapter 8 - Page 14
Miscellaneous System Options
Miscellaneous System Options

On the Miscellaneous Tab in the System Options window are several parameters that affect
transactions.
Require Salesperson: Select this checkbox to require salespersons to be selected when
entering transactions.
Print Remit to Address: Check this box to print your remit-to address on your customers
statements.
Print Home Country: Select this option to print your home country on your invoices and
statement that refer to addresses in that country.
Source of Territory: Enter the Source of Territory to default into Salespersons,
Transactions, and Customers windows. Receivables uses the value to determine the
default territory for invoices and commitments. Selections are: Bill-To Site, Salesrep,
Ship-To Site, and None.
Chapter 8 - Page 15
Discount Basis: Use to calculate discounts for your invoices. The following are the
discount options:
- Invoice Amount
- Lines Only
- Lines, Freight Items and Tax
- Lines and Tax, not Freight Items and Tax
Accrue Interest: To automatically update the open balance in the Transactions workbench
for transactions that are past due.
Chapter 8 - Page 16
Profile Options
Profile Options
(N) > Profile > System
Profile Options control many functions in Receivables. For more detailed information, refer to
the Oracle Receivables User Guide, Appendix A.
AR: Allow Update of Existing Sales Credits: Determines whether a user can update
existing sales credits.
AR: Change Customer on Transaction: Determines whether you can update customer
names in the Transaction windows.
AR: Default Exchange Rate Type: Determine the default exchange rate to use when
converting foreign currency transactions to your function currency.
AR: Override Adjustment Activity Account Option: Determines whether you can
override the default adjustment account when entering or updating manual adjustments
and when updating automatic adjustments.
AR: Transaction Batch Source: Determines how information will be sorted when using
the value in the Customers Alternate Name field when running certain reports.
Chapter 8 - Page 17
AR: Use Invoice Accounting For Credit Memos: Determines whether to assign your
credit memo to the same accounts that are assigned to the invoice you are crediting.
Chapter 8 - Page 18
Implementation Considerations for Transactions
Implementation Consideration for Transactions

For AutoAccounting, when using a table as a source of a segment, make sure the General
Ledger accounts are defined for the source. With AutoAccounting, for example, if you
select the Company segment to be derived from the transaction type for Revenue, the
revenue account must be entered for all transaction types.
For payment terms, decide on discounting, consolidated billing, split payment terms, and
allocating tax and freight.
For transaction batch sources, select Value to import a record into AutoInvoice tables
using its actual name (non-Oracle system); select ID to use its internal identifier (Oracle
system). If you use an Oracle system, ID is quicker. Oracle can recognize a record
identifier, or ID, quicker than a value because the ID is usually just a few characters in
length. For example, it is quicker to read 2309 rather than Business World.
Chapter 8 - Page 19
Implementation Considerations for Remit-To Addresses
Implementation Considerations for Remit-To Addresses

Define lockbox addresses as remit-to addresses to let customers know where to send
payment.
To catch any missing assignments, set up a remit-to address assigned to a default
location. If you enter or import an invoice with an address that does not correspond to
any of your assignments, it uses the default remit-to address.
Chapter 8 - Page 20
Optional Setup Steps for Transactions
Optional Setup Steps for Transactions

The following are optional setup steps for customer invoices:
Accounting Rules: If your accounting method is Accrual, use rules to create revenue
recognitions schedules for your invoices.
Salespeople: To allocate sales credits to invoices, debit memos and commitments. If you
do not want to assign sales credits for a transaction, you can enter No Sales Credit.
Standard Memo Lines: To enter predefined lines for debit memos, on-account credits,
and invoices.
Document Sequencing: To assign unique numbers to documents and account for each
transaction that is entered.
Statements: To create statements to send to customers.
- Define Aging Buckets: To review and report on open receivables based on the
number of days each item is past due.
- Define Statement Cycles: To control when you create customer statements.
- Define Messages: To customized the content of customer statements.
Consolidated Billing: To create consolidated billing invoices to send to customers.
Chapter 8 - Page 21
Define User Profile Option: AR: Show Billing Number to Yes to display the
consolidated billing invoice number in Receivable windows and reports.
Define New or Update Existing Customer Profiles: To determine which customers
will receive a consolidated billing invoice.
Define Proxima Payment Terms: To determine the cutoff date and payment terms
used with consolidated billing invoices.
Assign Payment Terms: To the Bill-To Site of each customer that you set up to
receive a consolidated billing invoice.
Chapter 8 - Page 22
Accounting Rules
Defining Accounting Rules

Accounting rules determine when to recognize revenue amounts.
Use Accounting, Fixed Duration type to recognize revenue over a specific number of
periods. Revenue can be spread evenly or a percentage can be specified for each period.
Use the Accounting, Variable Duration type to recognize revenue by a percentage for the
first period. The remaining revenue is spread evenly across the number of periods that
you specify during transaction entry.
Use Deferred Accounting Rules to recognize revenue on demand using the Revenue
Accounting feature. Deferred Accounting Rules are enabled by selecting the Deferred
Revenue checkbox on the Invoicing and Accounting Rules window.
Chapter 8 - Page 23
Salespeople
Salespeople
(N) > Setup > Transactions > Salespersons/Resources
Define salespeople to allocate sales credit for transactions.
Determine the source of the Territory Flexfield default for the Transactions window by
entering a value in the Source of Territory field in the Miscellaneous region of the Define
System Options window.
Determine whether a salesperson is required when entering transactions by selecting the
check box for Require Salesperson in the Miscellaneous region of the System Options
window.
Chapter 8 - Page 24
Standard Memo Lines
Standard Memo Lines

(N) > Setup > Transactions > Memo Lines
Memo lines can be used to define goods or services which are sold frequently, but have not
been defined as inventory items such as Annual Maintenance Contracts or Consulting Services.
Select one of the following standard line types: Charges, Freight, Line, or Tax.
You can enter a tax code to associate with a standard memo line.
If the price is constant, you can enter a unit price which defaults when this memo line is
used.
Chapter 8 - Page 25
Setting Up Document Sequencing
Setting Up Document Sequencing

(N) > Application > Document > Define
Using the Document sequence number as the transaction number makes tracking
transactions easy.
Category creation is now automatic. You no longer have to create a category as a separate
step. When you create a transaction type in Oracle Receivables, the document sequencing
category is created. (This enhancement is only in Receivables.)
Note: For more information on Document Sequencing, refer to Oracle Applications System
Administration Guide.
Chapter 8 - Page 26
Setting Up Gapless Transaction Numbering
Setting Up Gapless Transactions Numbering

(N) > Setup > Transactions > Sources > (T) Batch Source
Gapless transaction numbering gives a better audit trail and meets legal requirements for some
countries.
If the Copy Document Number to Transaction Number check box is selected when
creating batch source, it is possible to have duplicate invoice numbers within a batch
source.
- For example, you have to the following settings: the Automatic Numbering check
box in the Batch Source window is selected, the Copy Document Number to
Invoice check box is selected in the Batch Source window, and the AR: Document
Number Generation Level system option is set to When the Transaction is
committed. You create an invoice with a transaction type that does not require
document sequencing so the invoice number is assigned from the batch source. You
create another invoice with a transaction type that requires document sequencing.
The invoice number is created from the document sequence number which has the
same numbering scheme as the batch source.
Chapter 8 - Page 27
To avoid this, assign a different numbering scheme to you document sequence and
attach sources.
To ensure gapless numbering, the Allow Invoice Deletion check box in the Systems
Options window should not be selected.
Note
When using the document sequencing, the original invoice number is saved to the underlying
tables (OLD_TRX_NUMBER column of the RA_CUSTOMER _TRX_ALL table). Though
not viewable from any window once the document sequence number is assigned to the
transaction, you can query the old transaction number by entering & in the transaction number
field while in query mode. Then press [Ctlr] + [F11] to run the query. When a small window
opens, enter the Where criteria for the OLD_TRX_NUMBER and click the OK button.
If you do not select the Copy Document Number to Invoice Option, Oracle Receivables do not
allow duplicate transactions within a batch.
Chapter 8 - Page 28
Setting Up Statements
Setting Up Statements
(N) Setup > Collections > Aging Buckets
(N) Setup > Print > Statement Cycles
(N) Setup > Print > Standard Messages
Statements communicate activity to your customers about invoices, credit memos, debit
memos, payments, on-account credits, chargebacks, deposits, and adjustments.
Define Aging Buckets for statements. Oracle Receivables also prints your customers
past due balances based on aging buckets.
Define Statement Cycles.
Define Messages (optional). You can enhance your statements by printing your own
custom messages.
Chapter 8 - Page 29
Consolidated Billing Invoices
Consolidated Billing Invoices

A Consolidated Billing Invoice includes the following information:
A beginning balance.
Payments received since the previous consolidated billing invoice.
An itemized list of new charges (invoices, credit memos, adjustment) in either summary
or detail format.
Separate reporting of taxes.
The total balance due for this customer.
Chapter 8 - Page 30
Setting Up Consolidated Billing
Setting Up Consolidated Billing

(N) > Setup > Transactions > Payment Terms
(N) > Customers > Standard > Addresses > (B) Open
Define payment terms for consolidated billing. The payment term becomes the selection
criteria that Receivables uses to select invoices to be part of the consolidated invoice.
Assign these payment terms to customers.
Assign consolidated billing to customers through the profile class.
Set the Show Billing Number system option to Yes to show the billing number in the
various transactions windows.
Note: This system option migrated from a profile option with 11i.AR.H.
Chapter 8 - Page 31
Transaction Printing Views Overview
Transaction Printing Views Overview

Transaction Printing Views are used for developers to access the transaction tables to
customize invoices. In the past, a developer had to be very familiar with the transaction tables
to be able to customize the invoices. Now, the developer does not need to know the tables
because the view extracts the information.
Although Oracle Receivables makes extracting transaction information easier, the person
who creates the customized invoice must still know SQL.
A view contains a SQL select statement.
You use views to select information from the tables, such as the transaction tables.
A view can reference multiple tables so that when you point to a view, Oracle
Receivables retrieves the data from these tables without needing to know all the tables.
There are modules that create the view structure for the transaction printing procedure.
- You must run these modules in the order in which that appear, because
dependencies exist between some of the files.
- For more information about these views, see the Oracle Receivables User Guide,
Release 11i, Appendix H.
Chapter 8 - Page 32
Transaction Printing Views
New Transaction Printing Views

AR_INVOICE_HEADER_V: The main view. It retrieves the header information of the
report. It has two parts, one of adjustments and one of nonadjustments.
AR_INVOICE_ADJ_V: Retrieves the details for an adjustment.
AR_INVOICE_LINES_V: Retrieved the line items of each transaction retrieved by
AR_INVOICE_HEADER_V.
AR_INVOICE_TAX_SUMMARY_V: Retrieved tax summary information for a
transaction.
AR_INVOICE_COMMITMENT_INFO_V: Retrieves commitment information for a
transaction.
AR_INVOICE_TOTALS_V: Retrieves the total amounts for all lines and associated
charges for a transaction (for example, lines, freight, and tax).
AR_INVOICE_INSTALLMENTS_V: Retrieves installment information for
transactions with multiple installments.
AR_INVOICE_COUNT_TERMS_V: Retrieves the number of terms for a transaction
(that is, transactions assigned to split payment terms.)
Chapter 8 - Page 33
Agenda
Chapter 8 - Page 34
Define Transaction Types in Order
Define Transaction Types in Order

Define transaction types in this order so that you can associate one type with another. For
example, define a credit memo first and then an invoice. Enter the credit memo in the Credit
Memo Type field when you create the invoice transaction type. When you create a credit
memo for the invoice, the credit memo transaction type is defaulted.
Chapter 8 - Page 35
Implementation Considerations for Document Sequencing

Enhancements
Implementation Considerations for Document Sequencing Enhancements

What type of document sequence should be used: Gapless, Automatic, or Manual?
Document sequences and batch source sequences should have different numbering
schemes. This is to prevent duplicate numbering before a transaction has a status of
Complete.
For gapless transaction numbering, do not allow deletion of invoices.
Chapter 8 - Page 36
Function Security
Function Security
If you exclude the Transactions: Dispute function from the Transactions workbench, it is
automatically excluded from the Collections workbench.
The Copy and Print activities can be accessed either from a button or from the menu.
Excluding the function disables access from the button. The system administrator must
remove access from the menu when defining menu structures.
You can set up the same function security for debit memos (DM), credit memos (CM),
and on-account credits (OnAcc) as for invoices (Inv). Additionally, you can also set
function security for applying on-account credits (OnAcc: Applications).
Chapter 8 - Page 37
Summary
Chapter 8 - Page 38

Receivables Student Guide-11i

Uploaded by

Document Information

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

Receivables Student Guide-11i

Uploaded by

Copyright:

Available Formats

11i Oracle Receivables

Copyright Oracle Corporation, 2005. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Profile Class Characteristics ..........................................................................................................................3-20

11i Oracle Receivables Fundamentals Table of Contents

11i Oracle Receivables Fundamentals Table of Contents

Practice - Copy an Invoice.........................................................................................................................5-34

11i Oracle Receivables Fundamentals Table of Contents

XML Invoice Documents ..............................................................................................................................5-97

11i Oracle Receivables Fundamentals Table of Contents

Analyzing Credit Data ...................................................................................................................................7-22

11i Oracle Receivables Fundamentals Table of Contents

Solution - Enter a Manual Receipt.............................................................................................................9-14

11i Oracle Receivables Fundamentals Table of Contents

Credit Card Refunds ......................................................................................................................................9-79

11i Oracle Receivables Fundamentals Table of Contents

Practice - Create a Tax Group....................................................................................................................11-31

11i Oracle Receivables Fundamentals Table of Contents

AutoReconciliation Overview .......................................................................................................................13-13

11i Oracle Receivables Fundamentals Table of Contents

Oracle Cash Management Reports ................................................................................................................13-84

11i Oracle Receivables Fundamentals Table of Contents

Practice - Reverse a Receipt (Required) ....................................................................................................14-78

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Thorough knowledge of the overall Oracle Receivables Process

Ability to navigate Oracle Applications

11i E-Business Suite Essentials for Implementers

How This Course Is Organized

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Oracle Receivables Users Guide

System release bulletins

Installation and users guides

International Oracle Users Group (IOUG) articles

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Use the SELECT command to view information stored in the

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Typographic Conventions in Code

DROP USER scott

CREATE ROLE role

SQL commands and SELECT userid

Typographic Conventions in Oracle Application Navigation Paths

(M) From the menu, select Query then Find.

(B) Click the Approve button.

11i Oracle Receivables Fundamentals Table of Contents

Typographical Conventions in Oracle Application Help System Paths

Under the General Ledger entry, expand Journals.

Under Journals, select Enter Journals.

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Copyright 2005, Oracle. All rights reserved.

11i Oracle Receivables Fundamentals Table of Contents

Order to Cash Lifecycle

Copyright Oracle, 2005. All rights reserved.

Order to Cash Lifecycle Overview

Order to Cash Lifecycle Overview

Copyright Oracle, 2005. All rights reserved.

Order to Cash Lifecycle Overview

Copyright Oracle, 2005. All rights reserved.

Order to Cash Lifecycle Overview

Order to Cash Lifecycle