Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
AIM
BR.100 ACCOUNTS RECEIVABLE
APPLICATION SETUP
J2 Global Inc
Author: Syed
Creation Date: 11-June -2018
Last Updated:
Document Ref:
Version: 1.0
Approvers
S No. Name Designation Sign
1 Sandra
2 Naresh Racharla
1
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.
Document Control.....................................................................................................................
Setup Cash Basis Accounting/AR: Define System Options for Cash Basis
Accounting..................................................................................................................................
Setup Cash Basis Accounting/AR: Define Transaction Types for Cash Basis
Accounting..................................................................................................................................
Setup Cash Basis Accounting/AR: Run Script for Cash Basis Accounting....................
Workflow Setup Task Responsibility Due Date QA Responsibility QA Due Date Signature Approval
SubWorkflow Name
Receivables 12-June-18
AR: Define AutoCash Rule Sets
Receivables 12-June-18
AR: Define Receivables Quick
Codes
Receivables 12-June-18
AR: Define Demand Class
QuickCode
Receivables 12-June-18
AR: Define Invoice Line
Ordering Rules
Receivables 12-June-18
AR: Define System Options
Receivables 12-June-18
AR: Define Payment Terms
Receivables 12-June-18
AR: Define Invoicing and
Accounting Rules
Receivables 12-June-18
AR: Open/Close Accounting
Periods
Receivables 12-June-18
AR: Define Automatic
Accounting
Receivables 12-June-18
Setup Cash Basis Accounting AR: Define an Unallocated
Revenue Account
Receivables 12-June-18
Setup Cash Basis Accounting AR: Define System Options for
Cash Basis Accounting
SubWorkflow Name
Receivables 12-June-18
Setup Cash Basis Accounting AR: Define Transaction Types for
Cash Basis Accounting
Setup Cash Basis Accounting AR: Run Script for Cash Basis Receivables 12-June-18
Accounting
SubWorkflow Name
Status Active
AutoCash Rules:
Receivables>Setup>System>QuickCodes>Receivable
J2 Global Inc Process: Business Area: Date:
AR System Setup Receivables <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.
QuickCodes
R01 R01 – SD Insufficient Clients available bank balance is not Date Entered Y
funds sufficient to cover amount of the debit
Y
R02 R02 – SD Account Account number is no longer active Date Entered
Closed
Y
R03 R03 – SD No Account number is consistent with the Date Entered
Account/Unable to bank format, but the bank is unable to
Locate identify the individual client
Y
R04 R04 – SD Invalid Account number is not consistent with Date Entered
account number the format of the clients bank
Y
R05 R05 – SD No Prenote Client Bank does not have a pre Date Entered
on file notification in their ACH
authorization file and will not accept
dollar value entries until obtained
R06 Return per ODFI Returned per originating banks Date Entered Y
request
R07 Client revoked Client has revoked authorization for Date Entered Y
authorization ADP to process this type of transaction
R09 Uncollected funds Client has sufficient funds, but due to Date Entered Y
transactions in the process of collecting
the cash reserve is under the amount of
debits
R10 Client advises not Client Does not wish to make future Date Entered Y
authorized payments by automated collections
R11 No response from Client has not responded to the pre Date Entered Y
client regarding pre note
note
R13 Non participating DFI Clients bank is not a member of ACH Date Entered Y
and can not receive items by electronic
transmission
R16 Account Frozen Funds in the clients account are not Date Entered Y
available due to bank or legal action
R18 Bad Effect Entry Date Invalid effective entry date Date Entered Y
R19 Amount field error Invalid characters in amount field Date Entered Y
R23 Biller refused payment Payment was refused by biller Date Entered Y
R24 Duplicate entry Bank has returned duplicate entry Date Entered Y
R25 Addenda Rc’d. Ind. Err Addenda record indicator error Date Entered Y
R26 Addenda Type Code. Addenda type code invalid Date Entered Y
Err
R27 No Orig. Trace San Dimas origination trace number is Date Entered Y
number missing
R28 Check digit error Transit/ABA check digit is incorrect or Date Entered Y
there are non-numeric characters in the
Transit/ABA
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
J2 Global Inc Process: Business Area: Date:
AR System Setups Receivables <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.
Effective
01-June-18
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
Discount Basis
Tax Account
<Rounding Options>
Calculation Level
Rounding Rule
Reporting Currency
Precision
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
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: To
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:
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:
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
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.
Receivabl To GL Status
e
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
Receivabl To GL Status
e
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
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
GL Account Active
GL Account Description
Name Description
Type
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
Automatic Receipts:
<Remittance Banks>
Bank Name Branch Name
Primary
GL Accounts
Cash Receipt Confirmation
Remittance Factoring
Earned Discounts
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
First Second
Description
Type
Status
First Second
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:
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 hoc Inclusive Allow Inclusive
Tax (Code) From To Exempt Tax Override
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 Precedence
Tax
CR / DR
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
Yes
Tax Registration Number Active
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 Roles:
Description Primary
Payment Methods
Effective Dates:
Payment Method Name Primary From To
Credit:
Terms:
Receipts:
Cycle
Dunning:
Send Format
Finance Charges:
Days in Period:
Invoicing
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
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
GL Date Source
Receipt Method
Receipt Matching
Match Receipts By
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:
Start End Field Justify Fill Symbol Date Time Format Amount Overflow Indicator
Type
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
Name
Description
Tax Code
Unit of Measure
Revenue Account
Account Description
Invoicing Rule
Accounting Rule
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
<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
Tax Rates
Open Issues
ID Issue Resolution Responsibility Target Date Impact Date
Closed Issues
ID Issue Resolution Responsibility Target Date Impact Date