Responsibility Receivables Manager
19. Choose Value if you use this batch source to import data from a non–Oracle system
20. Select the Accounting Information tab.
21. Select “Id” to indicate how AutoInvoice validates your Invoice and Accounting Rule data for this batch source.
22. Select “Id” to indicate whether you want AutoInvoice to validate the identifier for this batch source.
23. Select the Derive Date check box to derive the default rule start date and default GL date from the ship date, rule start date, order date and the default date that you supply when you submit AutoInvoice.
If Oracle Inventory is installed, this must be selected.
24. Select “Id” to indicate that AutoInvoice validates your Payment Terms for this batch source using identifiers.
25. Select “Percent” to indicate that AutoInvoice validates your Revenue Account Allocation data for this batch source.
26. Select the Other Information tab.
27. Select “Id” to validate other data except for Agreement, Sales Territory, and Related Document.
28. Select the Sales Credit Validation tab.
29. Select “Id” for first two options to validate information using identifiers for this batch source.
30. Select Percent to validate sales credits based on percent.
31. Save your work.
For more information, see the Transaction Batch Sources section in the Oracle Receivables User Guide.
5.4.8 Define Remittance Banks
Required
Define all of the banks and bank accounts you use to remit your payments. You can define as many banks and bank accounts as you need.
If you already defined your remittance banks when setting up Oracle Public Sector Payables, then proceed to the next step.
For more information, see the Defining Banks section in the Oracle Receivables User Guide.
Prerequisites
You must install Oracle Payables.
Responsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > Receipts > Banks
5.4.9 Define Receipt Classes
Required
Define receipt classes to specify whether receipts are created manually or
automatically. For manual receipts, you can specify whether to automatically remit it to the bank and/or clear your accounts. For automatic receipts, you can specify a remittance and clearance method, and whether receipts using this class require confirmation.
For more information, see the Receipt Classes section in the Oracle Receivables User Guide.
Prerequisites
NoneResponsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > Receipts > Receipt Classes
5.4.10 Define Payment Methods
Required
Define the payment methods to account for your receipt entries and applications and to determine a customer’s remittance bank information. When defining
payment methods, you must enter a receipt class, remittance bank information, and the accounts associated with your payment receivables type. You can also specify accounts for confirmation, remittance, factoring, bank charges, and short–term debt.
For more information, see the Payment Methods section in the Oracle Receivables User Guide.
Prerequisites
You must define receipt classes and your banks.
Responsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > Receipts > Receipt Classes
5.4.11 Define Aging Buckets
Required (prerequisite for general loss provision functionality)
Define aging buckets to review and report on open receivables based on the number of days each item is past due. For example, the 4–Bucket Aging bucket that
Receivables provides consists of four periods: –999 to 0 days past due, 1 to 30 days past due, 31–61 days past due, and 61–91 days past due.
For Oracle Lease Management, you need to define aging buckets which you use to create loss provisions.
For more information, see the Aging Buckets section in the Oracle Receivables User Guide.
Prerequisites
NoneResponsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > Collections > Aging Buckets
5.4.12 Define System Options
Required
Define your accounting, discount, tax, and invoice system options to control how Receivables works. System options determine your accounting method, set of books, accounting flexfields, whether you use header or line–level rounding, and control the default operation of the AutoInvoice and Automatic Receipt programs.
System options also control how Receivables calculates tax on your transactions.
You must specify a tax method, choose a Location Flexfield Structure, indicate whether to compound tax, select the address validation to use, and define tax defaults and rounding options. As you can set up your system to calculate Sales Tax, Value Added Tax, or Canadian Tax, we recommend that you carefully review the appropriate implementing tax essay before defining your system options.
For more information, see Defining Receivables System Options in the Oracle Receivables User Guide.
Prerequisites
Define your set of books (Oracle General Ledger User Guide).
Define AutoCash Rule sets.
Define Grouping Rules.
Define Key Flexfield segments.
Responsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > System > System Options
5.4.13 Define Tax Options
Required
Set up the remaining features of Receivables tax, which were not part of the system options set-up, by defining tax–specific profile options, tax codes and rates, tax Lookups, tax exceptions and exemptions, tax authorities, and tax groups.
Oracle Lease Management requires that you calculate sales tax on quotes and billing items.
For more information, refer to the appropriate implementing tax essay in the Oracle Receivables Tax Manual. You can also reference the Oracle Receivables User Guide.
Prerequisites
You must define your Oracle Receivables system options.
Responsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > Tax (There are nine forms within the Tax directory you may need to configure when defining tax options.)
5.4.14 Define Receivables Lookups
Required
Lookup names display as list of value choices throughout Oracle Applications to help speed data entry and accuracy. Receivables provides many lookups types for you. Some lookup types can be updated to suit your business needs. You cannot update a lookup type if Receivables requires those settings for its own internal use.
You can create new lookup types and define as many additional lookups as you want in the Receivables Lookups window. For Oracle Lease Management, you need to define two additional lookups, described in the Guidelines below.
You cannot change lookup name values after you save them. To remove an obsolete lookup you can: disable the code, enter an end date, or change the meaning and description to match a replacement code.
A lookup is any defined value that was not defined in a setup window. Use the Oracle Purchasing Lookups window to review and maintain sets of values, or lookups that you use in Payables.
For more information on defining your Receivables lookups, see the Oracle Receivables User Guide.
Prerequisites
NoneResponsibility
Oracle Receivables Administrator
Module
Oracle Receivables
Navigation
Setup > System > QuickCodes > Receivables
Guideline
You must define the following Oracle Lease Management-specific lookups. To do so, within the QuickCodes > Receivables page enter a query of type CUSTOMER_
CATEGORY. Add two blank lines and add the two new lookups with these values:
5.5 Set Up Payables
Required
Oracle Lease Management links with the Oracle Payables module to let you make disbursements to pay vendor or supplier invoices. Items that you would typically need to set up include defining or specifying: payables lookups, invoice currency, payment currency, currency exchange types and rates, payment terms, tax codes, withholding tax groups, document categories, pay groups, and open payables periods.
The specific setup steps of Oracle Payables that directly impact Oracle Lease Management include:
■ Section 5.5.1, "Define Payment Terms"
■ Section 5.5.2, "Define Payables Lookups"
■ Section 5.5.3, "Define Purchasing Lookups"
■ Section 5.5.4, "Define Suppliers"
■ Section 5.5.5, "Define Insurance Providers"
For more information on setting up Oracle Payables, see the Oracle Payables User Guide.
5.5.1 Define Payment Terms
Required
You need to define payment terms that you can assign to an invoice to
automatically create scheduled payments when you submit an approval for an invoice. You can define payment terms to create multiple scheduled payment lines Table 5–2 Lookups for Oracle Lease Management
CODE MEANING DESCRIPTION
Insurer Insurance Agent Insurance Agent
Insurance_Agent Insurance Agent Insurance Agent
and multiple levels of discounts, and you can create an unlimited number of payment terms. Payment terms have one or more payment term lines, each of which creates one scheduled payment.
For more information on defining payment terms, see the Oracle Payables User Guide or the Oracle Applications Help, available in Oracle Payables.
Prerequisites
NoneResponsibility
Accounts Payable Super User