Author: <Author>
Creation Date: December 16, 2011
Last Updated: December 16, 2011
Document Ref: <Document Reference Number>
Version: DRAFT 1A
Approvals:
<Approver 1>
<Approver 2>
BR.100Aar Accounts Receivable Application Setup Doc Ref: <Document Reference Number>
December 16, 2011
Document Control
Change Record
1
Reviewers
Name Position
Distribution
Note To Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document
control purposes.
If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.
Contents
Document Control.......................................................................................ii
Setup Cash Basis Accounting/AR: Define System Options for Cash Basis
Accounting................................................................................................21
Setup Cash Basis Accounting/AR: Run Script for Cash Basis Accounting.23
Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Signature Approval
Date
SubWorkflow Name
Setup Accounts
Receivable
Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Signature Approval
Date
SubWorkflow Name
Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Signature Approval
Date
SubWorkflow Name
Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Signature Approval
Date
SubWorkflow Name
Status
Open Balance
Calculation:
Finance Charges
Automatic Matching
Rule:
AutoCash Rules:
Receivables>Setup>System>QuickCodes>Receivable
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to maintain Oracle Receivables QuickCodes.
<Receivables QuickCodes>
Type
Description
User Maintainable
QuickCodes
Name Meaning Description Start Date End Date Enabled User Maintainable
Receivables>Setup>System>QuickCodes>Demand Class
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to maintain existing and to define additional QuickCodes for your shared QuickCode types.
<QuickCodes (Demand_Class)>
Type
Application
Description
Access Level
Receivables>Setup>Transactions>AutoInvoice>Line Ordering
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define and review your Ordering Rules for Invoice Lines.
Description
Effective
Start Date
End Date
Order By
Receivables>Setup>System>System Options
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Oracle Receivables system guidelines to control how Oracle Receivables works for you.
Accounting
Accounting Method
Name
Accrue Interest
Allow Unearned
Discounts
Discount on Partial
Payment
Discount Basis
Tax Account
Unallocated Revenue
Account
Automatic Journal
Import
Tax
Tax Method Tax Registration Number
Location Flexfield
Structure
<Rounding Options>
Calculation Level
Rounding Rule
Reporting Currency
Precision
Minimum Accountable
Unit
Allow Override
Customer Site
Customer
Product
Revenue Account
System Options
Tax Code
<Exception Rates>
Use Customer Exemptions
Use Item Exemptions
Use Item Tax Rate Exceptions
<AutoInvoice>
Tuning Segments
Accounting Flex
System Items
Territory
<Customers>
Automatic Customer Automatic Site Numbering
Numbering
DEFAULT
Create Reciprocal Customer Grouping Rule Name
Miscellaneous
<Auto Receipts>
Invoice per Commit Receipts per Commit
Receivables>Setup>Transactions>Payment Terms
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter Payment Terms that reflect the way you do business.
<Payment Terms>
Name
Base Amount
Description
Cutoff Day
Credit Check
Allow Discount on
Partial Payments
First Installment
Discount Basis
Effective Dates:
From
Effective Dates:
To
<Payment Schedule>
Sequence Relative Amount Days Date Day of the Month Months Ahead
Discounts
% Days Date Day of Month Months Ahead
Receivables>Setup>System>System Options
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to assign a reporting Set of Books.
Receivables>Setup>Transactions>Rules
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define your Accounting Rules to create revenue recognition schedules for your invoices.
Type Active
Schedule:
Name Description
Type Active
Schedule:
Name Description
Type Active
Schedule:
Receivables>Setup>Financials>Calendars>Calendars
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to open and close your accounting periods.
Name
Description
Periods
Receivables>Setup>Transactions>AutoAccounting
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: You must use this form before you enter any Transactions to specify how you want Oracle Receivables to determine the
general ledger accounts for your Transactions.
<Automatic Accounting>
Type
Segments:
Setup Cash Basis Accounting/AR: Define System Options for Cash Basis Accounting
Receivables>Setup>System>System Options
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Assign an Unallocated Revenue Account in order for AR to credit this account you over-apply a cash receipt to an invoice
with an outstanding balance equal to zero.
Accounting
Setup Cash Basis Accounting/AR: Define Transaction Types for Cash Basis Accounting
Receivables>Setup>Transaction>Transaction Types
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define different Transaction types for Cash Basis Accounting.
Receiva To GL Status
ble
Allow Tax Creations Sign Natural Application Rule Set Allow Overapplication
Freight Calculation Application
Only
Description Value
Receivable
Account
Freight Account
Revenue Account
Clearing Account
Unbilled Account
Unearned
Account
Invoice Type
Credit Memo
Type
Start Date
End Date
Setup Cash Basis Accounting/AR: Run Script for Cash Basis Accounting
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: To be able to use Cash Basis accounting, run the SQL script to create Cash Basis Accounting tables.
Receiva To GL Status
ble
Allow Tax Creations Sign Natural Application Rule Set Allow Over-Application
Freight Calculation Application
Only
Description Value
Receivable
Account
Freight
Account
Revenue
Account
Clearing
Account
Unbilled
Account
Unearned
Account
Invoice Type
Credit Memo
Type
Start Date
Description Value
End Date
Receivables>Setup>Transactions>Sources
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define your debit memo, credit memo, deposit, guarantee, and Invoice Batch Sources.
<Invoice Sources>
Type Active
Type Active
Type Active
Sales Credit
Receivables>Setup>Collections>Collectors
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to identify your Receivables Collectors.
<Collectors>
Name Description Correspondence Name Telephone Number Active
Receivables>Setup>Transactions>Adjustment Limits
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Approval Adjustment Limits for each of your users.
Receivables>Setup>Receipts>Distribution Sets
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to create Receivables Distribution Sets for your other receipt payments.
<Distribution Sets>
Name
Yes
Active
Description
Total %
Receivables>Setup>Receipts>Receivable Activity
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define as many Receivable Activities as you require.
<Receivable Activity>
Name Description
Type
Accounting Distribution
Set
GL Account Active
GL Account Description
Name Description
Type
Accounting Distribution
Set
GL Account Active
GL Account Description
Receivables>Setup>Receipts>Receipt Class
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the processing steps that you want to require for your Payment Methods.
<Receipt Classes>
Receipt Class:
Payment Method:
Automatic Receipts:
Receipt Class:
Require Confirmation
Payment Method:
Automatic Receipts:
<Remittance Banks>
Bank Name Branch Name
Primary
GL Accounts
Cash Receipt
Confirmation
Remittance Factoring
Unapplied Unidentified
Receipts Receipts
On Account Unearned
Receipts Discounts
Earned
Discounts
Description
Formatting Programs
Remittance
Transmission
Remittance Print
Factoring
Transmission
Factoring Print
Receivables>Setup>Receipts>Receipt Sources
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define your Receipt Sources.
<Receipt Sources>
Name Description
Receipt Class
Bank Account
Name Description
Receipt Class
Bank Account
Receivables>Setup>Collections>Aging Buckets
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define the Aging Buckets that you need to meet your reporting needs.
<Aging Buckets>
Name
Description
Type
Status
Name
Description
Type
Status
Receivables>Setup>Print>Statement Cycles
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define customer Statement Cycles.
<Statement Cycles>
Name
Description
Interval
Active
Cycle Dates:
Receivables>Setup>Print>Standard Messages
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Standard Messages that you want Oracle Receivables to print on the bottom of your customers’
statements.
<Standard Messages>
Name Type Start Date End Date Message
Receivables>Setup>Print>Dunning Letters
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to specify general criteria about your Dunning Letters such as status and review date.
<Dunning Letters>
Name
Description
Active
Review Date
Days Overdue
Name
Description
Active
Letter Sequence:
Staged Dunning
Dunning Level:
From To Minimum Days
Receivables>Setup>Transactions> Salespersons
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter your Salespersons.
<Salespersons>
Name Number
Active
Revenue Account
Freight Account
Receivable Account
Assignments:
System Administration>Profile>System
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to set a value for each Profile option to specify how Oracle Receivables controls access to and processes
data. The system administrator sets and updates profile values.
Receivables>Setup>Tax>Codes
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter and maintain other tax rates that are not based on your customer’s shipping address.
Rate
Effective Dates:
Tax (Code) From To Tax Type Tax Rate % Sign
CR / DR
Control
Effective Dates: Allow Ad Inclusi Allow Inclusive
Tax (Code) From To Exempt hoc ve Tax Override
Accounting
Effective Dates:
Tax (Code) From To Tax
Description
Effective Dates:
Tax (Code) From To Tax Name Description
Receivables>Setup>Tax>Groups
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter and maintain Tax Groups.
Group Name
Group Description
Effective (From)
Effective (To)
<Tax Codes>
Rate
Tax (Code) From To Name Tax Rate Sign Inclusive Compounding
% Tax Precedence
CR / DR
Condition
Tax (Code) From To Classification Ship to Location
Receivables>Customers>Profile Classes
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define standard Profile Classes.
Credit:
Collector Tolerance
Credit Check
Receipts:
Statements:
Cycle
Send Format
Terms:
Finance Charges:
Days in Period
Invoicing:
Dunning:
Credit Limit
Receivables>Customers>Standard
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Standard profile classes.
<Customers>
Customer Name Number
Classification
Use Reference
Class Category
Salesperson Carrier
Marketing
Number of Employees Year Established
Competitor
Revenue:
Mission Statement
Addresses
Address
Business Purposes
Usage Location Bill to Location Primary Active
Telephones
Area Code Telephone Number Extension Type Primary Active
Contacts: Telephones
Contact Name:
Contact
Telephones:
Contacts: Roles
Contact Name:
Contact Roles:
Description Primary
Bank Accounts
Account Name Account Number Currency Primary Effective Dates:
From To
Payment Methods
Effective Dates:
Payment Method Name Primary From To
Profile: Transaction
Profile Class
Credit:
Terms:
Receipts:
Cycle
Dunning:
Send Format
Finance Charges:
Days in Period:
Invoicing
Profile: Amounts
Currency
Relationships
Related Customer:
Receivables>Setup>Print>Remit-To Addresses
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to maintain your customer’s Remit-To Addresses, that you want Oracle Receivables to print on your
statements and dunning letters.
<Remit-To Addresses>
Country
Address
Alternate Name
City
State
Postal Code
Province
County
Country
Address
Alternate Name
Receipts From:
Postal Codes:
Country State From To
Receivables>Setup>Receipts>LockBoxes>LockBoxes
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define your Lockbox. You use the Automatic LockBox Transmission to enter receipts automatically using
electronic LockBox information provided by banks.
<LockBoxes>
Number Active
Batch Source
Bank Name
Bank
Address Contact
Accounting Flexfield
Receipts
Batch Size
GL Date Source
Receipt Method
Receipt Matching
Match Receipts By
Match on Corresponding
Date
Transactions
Auto Associate
Receivables>Setup>Receipts>LockBox>Transmission Formats
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Transmission Formats used by Oracle Receivables Automatic LockBox Transmission.
<Transmission Formats>
Name
Description
Active
Transmission Records:
Transmission Fields
Position
Start End Field Justify Fill Symbol Date Time Format Amount Overflow
Type Indicator
Receivables>Setup>Transactions>Memo Lines
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define standard line items for debit memos, on-account credits, debit memo reversals, chargebacks, and
invoices.
Description
Type
Tax Code
Unit of Measure
Revenue Account
Account Description
Invoicing Rule
Accounting Rule
Active Dates:
(From)
Name
Description
Type
Tax Code
Unit of Measure
Revenue Account
Account Description
Invoicing Rule
Accounting Rule
Active Dates:
(From)
Receivables>Setup>Tax>Locations
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter and update your Locations and their associated Tax Rates.
<Locations>
State
Locations:
State Description Tax Account
<Rates>
Effective Dates: Postal Codes:
Tax Rate % Override From To From To
County
Locations:
County Description Tax Account
<Rates>
Effective Dates: Postal Codes:
Tax Rate % Override From To From To
City
Locations:
City Description Tax Account
<Rates>
Effective Dates: Postal Codes:
Tax Rate % Override From To From To
Receivables>Setup>Tax>Authorities
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to enter and maintain your Authorities.
<Tax Authorities>
Effective Dates:
Authority Enabled From To
Receivables>Setup>Tax>Exceptions
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form to define Item Tax Rate Exceptions.
Description
Receivables>Setup>Tax>Exemptions
<Customer Short Name> Process: Business Area: Date:
<Process Name> <Business Area> <Date>
Control Number: Priority(H, M, L): Process Owner:
<Control Number> <Priority (H, M, L)> <Process Owner>
Description: Use this form when you want to fully or partially exempt a customer or item from a specific tax code.
Location
Number
Site
<Exemptions>
Exemption Effective Dates
Item
Description
<Exemptions>
Exemption Effective Dates
Item Low
Item High
<Exemptions>
Exemption Effective Dates
Tax Rates
Open Issues
ID Issue Resolution Responsibility Target Date Impact Date
Closed Issues
ID Issue Resolution Responsibility Target Date Impact Date