What is auto lockbox in oracle applications?

Lockbox is a service provided by banks by which your company gets the customers payments
directly to a lockbox interface tables and creates receipt for the payments deposited into your
account. If you have an Auto Lockbox, the bank records the information that you request such as
check number, check amount, numbers and amount for the invoices to be paid.
Oracle provides you with the tools to:

* Oracle interface tables for the data received from the bank
* Validate the data to see if it is accurate, complies with the controls provided
* Correct the data
* Apply the receipts to the customer’s open invoices.
A typical Lockbox transmission contains various different records, each with relevant data.
Controls are provided at each level to ensure that the transmission was successful and to verify
that the count and dollar amounts are consistent with what the bank indicated. These controls are
at the transmission, Lockbox, batch and receipt levels. The records also contain information such
as your bank account (by Lockbox) and the details for the receipts the bank received. The
Lockbox may be used for checks, wires and any other receipts that you receive. You define what
the data from the bank will look like and how you will use it. 
Oracle Accounts Receivables Module provides the feature such that the customer can directly
make the payment for their invoices in the Bank. The Bank would send a data file in an agreed
transmission format which we import in Receivables through Auto Lockbox. After successful
import the Receipts get created in the final stage.
This is a three step process
1) Validate the data file
2) Import the data file which created the Post Batch
3) Run the Post Batch  (i.e. Post Quick Cash) which would actually create the Receipts and
applies against the Invoice on the Information provided in the data file.
Following are the main tables for auto lockbox
AR_PAYMENTS_INTERFACE_ALL
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_RCPT_LINES_ALL
AR_CASH_RECEIPTS_ALL
AR_CASH_RECEIPT_HISTORY_ALL
AR_DISTRIBUTIONS_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
AR_PAYMENT_SCHEDULES_ALL
The steps on how to define auto lock box are given below:
Define the bank, branch and bank account 
2. Define Receipt Class for Auto Lockbox 
3. Define Receipt Source 
4. Define Auto cash Rule set 
5. Define Customer - Attach the receipt method and create the customer bank account (Branch
number and account number together decides the MICR number) 
6. Define Lockbox (Setup --> Receipts --> Lockboxes --> Lockboxes) 
7. Define Transmission Formats (Setup --> Receipts --> Lockboxes --> Transmission Formats) 
8. Modify (or create a new one) the existing control file to suit the above formats 
9. Run Auto lockbox 
10. Submit Validation 
11. Submit Post Quick cash.
AUTOLOCK BOX SETUP IN R12
Posted by Raju ERP
Introduction:
AutoLockbox is a service that commercial banks offer corporate customers to enable them
to outsource their accounts receivable payment processing. 
AutoLockbox eliminates manual data entry by automatically processing receipts that are
sent directly to your bank. You can also use AutoLockbox for historical data conversion. 
For example, you can use AutoLockbox to transfer receipts from your previous accounting
system into Receivables.
AutoLockbox ensures that the receipts are accurate and valid before transferring them into
Receivables.

AutoLockbox is a three step process:

1. Import: During this step, Lockbox reads and formats the data from your bank file into
interface table AR_PAYMENTS_INTERFACE_ALL using a SQL *Loader script.
2. Validation: The validation program checks data in this interface table for compatibility
with Receivables. Once validated, the data is transferred into QuickCash tables
(AR_INTERIM_CASH_RECEIPTS_ALL and
AR_INTERIM_CASH_RCPT_LINES_ALL) . At this point, you can optionally query your
receipts in the QuickCash window and change how they will be applied before submitting
the final step, Post QuickCash.
3. Post QuickCash: This step applies the receipts and updates your customers balances.
These steps can be submitted individually or at the same time from the submit Lockbox
Processing window.

Responsibility: Receivables Manager
Navigation: Interfaces > Lockbox

After you run Post QuickCash, Receivables treats the receipts like any other receipts, you can
reverse and reapply them and apply any unapplied, unidentified, or on-account amounts.
Importing Data from the data file provided by Bank:
 

 
Setup
Define Bank and Bank Branches
Define Internal Remittance Bank and Bank Branch where checks from customer are
deposited. This is the bank which sends the data file for lockbox transmission.

Responsibility: Cash Management Manager

Navigation: Setup > Banks > Banks.
Remittance Bank Account
Define Internal bank account.

Responsibility: Cash Management Manager

Navigation: Setup > Banks > Bank Accounts

1. Enter the Account Owner (the legal entity that owns the account.) and Use (the types of
functions that this bank account is going to be used for: Payables, Payroll, Receivables, or
Treasury or all).
 2.Enter the Bank Account Information
3. Enter Account Controls. A Cash Account is required
 4.Enter Account Access and Contacts as required 
Define Receipt Classes

Define Receipt classes to determine the required processing steps for receipts to which you
assign payment methods with this class. 
Enter the Payment Method to assign to this receipt class.

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Receipt Classes
Assign Bank Account to Payment Method

Receivables uses payment methods to account for the receipt entries. One can assign multiple
banks to each payment method, but only one bank account can be primary account for each
currency.
Assign the payment method to the customer against whose invoice the receipt is going to be
applied to.

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Receipt Classes
Define Receipt Source

Define receipt batch sources and assign the receipt class, payment method, and remittance bank
account fields to this source.

 Receipt batch source type should be Manual.

 Receipt batch sources can use either automatic or manual batch numbering. (Should be
Automatic Batch numbering if to be used for Lockbox process).
Responsibility: Receivables Manager
Navigation: Setup > Receipts > Receipt Sources
Define Lockbox 
Bank Tab

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Lockboxes > Lockboxes > Bank Tab
Define Lockboxes to use the Receivables Autolockbox program

 Select an operating unit.

 Enter the lockbox Number provided by your bank.
 Enter the receipt Batch Source for this lockbox. You must enter a batch source that uses
automatic numbering. Receivables enters the bank name and account, address,
contact person, and accounting flexfield information associated with this batch source.
 Enter the Bank Origination Number provided by your bank. This number uniquely
identifies the bank branch that sends you lockbox information.
Receipts Tab

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Lockboxes > Lockboxes > Receipts Tab

 Enter the Batch Size you want the Lockbox Validation program to assign to each receipt
batch.
 Enter your GL Date Source. This can be 
o Constant Date: Receivables uses the date you enter in the GL Date field of the
Submit Lockbox Processing window. If you do not enter a date when you
choose Constant Date, Receivables does not validate your data. If you choose this source
and the lockbox transmission's deposit date is not
defined, Receivables displays an error message indicating that you must define
a deposit date to submit the lockbox.
o Deposit Date: Receivables uses the date that your bank deposits your receipts.
o Import Date: Receivables uses the date on which you import your receipts.
 If you are using this lockbox to transfer foreign currency receipts and you did not specify
exchange rate type in the bank file, enter an Exchange Rate Type.
 Enter the Receipt Method to assign to this lockbox. The default is the receipt method
associated with the receipt batch source you entered.
 If you want AutoLockbox to be able to transfer receipts without billing locations into
Receivables, uncheck the Require Billing Location check box. If this box is checked,
AutoLockbox will only validate the receipt if the billing location is provided.
Choose a Match Receipts By method. (If Autoassociate is set to Yes)
 Transaction Number: Match receipts with transaction numbers.
 Balance Forward Billing Number: Match receipts with balance forward billing numbers.
To use this method, the customer must be enabled for balance forward billing. 
Lockbox uses the balance forward billing number to identify the customer. Post QuickCash
then uses this customer's AutoCash Rule Set to determine how to apply the receipt to each
invoice.
 Sales Order: Lockbox uses this number to determine the corresponding invoice number.
 Purchase Order: Lockbox uses this number to determine the corresponding invoice
number.
 Hook: Match receipts to any other type of matching number that is passed with this
transmission. 
This is a custom matching method that you define. Lockbox uses this number to determine
the corresponding invoice number.
Choose whether to Match on Corresponding Date for transactions in this Lockbox transmission.
1. Always: Always verify that the date for the transaction or other matched item is the same
as the date specified in this transmission.
2. Duplicates Only: Only verify that the matching date and the specified date are the same if
duplicate matching number were found and Lockbox needs to determine which is correct.
3. Never: Ignore the specified date. This is the default value.

Transactions Tab

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Lockboxes > Lockboxes > Transactions Tab
 If you do not want the Lockbox Validation program to use the debit item number to
determine a customer, open the Transactions tabbed region, uncheck the AutoAssociate box.
By default, the Lockbox Validation program uses an invoice or debit memo number to
determine the customer with which the receipt should be associated (if there is no customer
information or MICR number in your Lockbox transmission).
 Auto Associate: Check the AutoAssociate check box.

Note: Ensure that all invoices to which any single receipt will be applied belong to the same
customer. And also ensure that the matching numbers within the transmission are unique
 If using Oracle Trade Management, then select the Evaluate for Claim Eligibility check
box if you want Lockbox to automatically create claims for eligible remittance
lines.
A remittance line's eligibility for claim creation depends on your system options setup. 
If you select this box but the remittance line is not eligible for claim creation, then Lockbox
handles receipts according to the selection that you make in the next step.
 Choose how Lockbox will handle Invalid Transaction Number: If the receipt record is
associated with multiple invoices, but one of the invoices is invalid. Depending on how you
set this option, Lockbox will:
1. Post Partial Amount as Unapplied: Apply the receipt to the valid transactions,
then import the remaining receipt amount with a status of Unapplied.
2. Reject Entire Receipt: Do not import the receipt (it will remain in
theAR_PAYMENTS_INTERFACE table). 
You need to edit the invalid record(s) in the Lockbox Transmission Data window, then
resubmit the Validation step for the receipt before Lockbox can import it into
Receivables interim tables.
 Select the appropriate line level cash application option:
1. None: Receivables does not perform line level cash application for the Lockbox
run. 
None is the default line level cash application option for new setups and migrated data.
2. Oracle Lease Management: Receivables calls Oracle Lease Management to
resolve the matching numbers and populate the invoice, invoice lines, and actual
amounts to be applied to the invoice lines.
 3. Custom: Receivables calls a seeded custom program to resolve the matching
numbers and populate the invoice, invoice lines, and the actual amounts to be applied to
the invoice lines.

Define Transmission Format

Define the Transmission Format which Auto Lockbox uses when importing data into
Receivables.

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Lockboxes > Transmission Formats
Following are valid record types:

1. Batch Header: A Batch Header marks the beginning of a specific batch. 

Batch Headers usually contain information such as batch number, deposit date, and lockbox
number.
2. Batch Trailer: A Batch Trailer marks the end of a specific batch. 
Batch Trailers usually contain information such as batch number, lockbox number, batch
record count, and batch amount.
3. Lockbox Header: A Lockbox Header marks the beginning of a specific lockbox.
Lockbox Headers usually contain information such as destination account and origination
number.
4. Lockbox Trailer: A Lockbox Trailer marks the end of a specific lockbox.
Lockbox Trailers usually contain information such as lockbox number, deposit date,
lockbox amount, and lockbox record count.
5. Overflow Receipt: An Overflow Payment usually contains invoice information for a
specific payment such as batch number, item number, sequence number, overflow
indicator, invoice number, debit memo number, or chargeback number, and debit item
amounts. 
Receivables combines the overflow and payment records to create a logical record to
submit payment applications.
6. Receipt: A Payment usually contains information such as MICR number, batch number,
item number, check number, and remittance amount.
7. Service Header: Service Header records contain general information about your
transmission.
8. Transmission Header: A Transmission Header marks the beginning of a specific data
file. 
Transmission Headers usually contain information such as destination account, origination
number, deposit date, and deposit time.
9. Transmission Trailer: A Transmission Trailer marks the end of a specific data file. 
Transmission Trailers usually contain information such as total record count.
Define Transmission Fields
Setting up Transmission Fields

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Lockboxes > Transmission Formats
Select a record type , click on Transmission Fields.
  

1. Choose Transmission Fields. Identify the characteristics of your transmission format

records. You specify the size, order, and format of each transmission record. Receivables
lockbox transmission program only validates fields that you define in your transmission
format. 
The transmission format must be fully compatible with how you organize data in your
lockbox file.
2. Enter Start and End Position numbers for this record type. 
These positions determine how Receivables identifies the starting and ending position of
your field type when you import data from your bank file.
3. Enter the Field Type to assign to the start and end positions (see Valid Field Types
below).
4. Enter either Left or Right in the Justify field to indicate from which side Receivables will
start reading data in the transmission field. For example, if you enter Left, Receivables
starts reading data from left to right. The default is Left.
 5. Enter the type of character that your bank places in the extra spaces for this field type in
the Fill Symbol field. Valid values are Blank or Zero.
6. If the field type is related to a date, enter the Date format your bank uses, or select from
the list of values. 
This field is required when Field Type is either Deposit Date or Receipt Date.
7. If the field type is related to time, enter the Time format your bank uses. This field is
required when your Field Type is Deposit Time.
8. Enter either Yes or No in the Format Amount field to indicate whether you want
Receivables to reformat the amount transmitted (optional). 
If you enter Yes, Receivables will round the amount to the same degree of precision and the
same number of decimal places as your functional currency format. 
For example, if your functional currency is USD (precision = 2) and you set this option to
Yes, a value of 50000 in the bank's data file will be formatted as 500.00; otherwise, this
value will not be formatted and will appear as 50000.
This field is required when your Field Type is Amount Applied 1-8, Batch Amount,
Lockbox Amount, Remittance Amount, or Transmission Amount.
9. Enter a value that indicates that there are additional overflow records for your
transmission record (optional). For example, in the Default format the overflow indicator is
0.
10. Enter a Description for the field type you are defining (optional). Use field descriptions to
help you recognize what information is contained in a particular field type.

Valid Field Types

When defining your transmission fields, you can choose from the following field types:

 Account: Your customer's bank account.

The bank account number and the transit routing number make up your customer's MICR
number.
 Alternate Name: The alternate name for this customer.
 Amount Applied 1 to 8: The amount applied to each invoice, debit memo, or
chargeback. 
 Each payment or overflow payment record can accommodate up to eight debit item numbers.
For cross currency applications, this is the amount to apply in the transaction currency and
corresponds to the Amount Applied field in the Applications window.
 Amount Applied From 1 to 8: Used for cross currency receipt applications, this is the
amount applied to each transaction in the receipt currency. 
Each payment or overflow payment record can accommodate up to eight debit item numbers.
This field corresponds to the Allocated Receipt Amount field in the Applications window.
 Attribute 1 to 15: Use attributes to enter Descriptive Flexfield segments. 
Attributes can only be assigned to Payment records, and they become the Descriptive
Flexfield data in the QuickCash, Receipts, and Applications windows.
 Bank Transaction Code: A code defined for each account that is used by your bank to
uniquely identify the kind of transaction in a bank statement (for example, debit, credit, void).
This is also used by Oracle Cash Management to determine a receipt's effective date.
 Batch Amount: The total receipt batch amount for a specific bank batch.
 Batch Name: The name of the batch for a specific bank batch.
 Batch Record Count: The total number of payment records in a specific bank batch. 
The total number of all batch record counts equals the Lockbox Record Count. This does not
include overflow payments, headers, or trailers.
 Billing Location: Your bank will be able to transmit the billing location of the payment.
You must only specify the field name and the field positions that the billing location occupies
in the transmitted data file.
 Comment: Any comments you want to associate with this transmission.
 Currency Code: The currency of the payment. For cross currency payments, you can
also enter the Invoice Currency Code (see below). If you do not enter a value in this field,
AutoLockbox derives the currency code from the information that is provided in the Amount
Applied and Amount Applied From fields.
 Customer Bank Branch Name: The name of your customer's bank branch.
 Customer Bank Name: The name of your customer's bank.
 Customer Number: The identification number of the customer who submitted a
payment.
 Customer Reason 1 to 8: The customer's reason why their payment shows a discrepancy
(used by Oracle Trade Management).
 Customer Reference 1 to 8: Customer comments about this payment.
 Deposit Date: The date the bank receives and deposits your customer's payment.
 Deposit Time: The time at which the bank receives and deposits your customer's
payment.
 Destination Account: Your business's bank account. Your business may have more than
one bank account.
 Effective Date: The date on which the bank determines a customer's balance to apply
interest (used by Oracle Cash Management's Cash Forecasting feature).
 Exchange Rate: The exchange rate associated with this payment if you are using
AutoLockbox to import foreign currency receipts.
 Exchange Rate Type: The exchange rate type used to convert a foreign currency receipt
to your functional currency. Values include Corporate, Spot, or User.
 Invoice 1 to 8: The invoices, debit memos, and chargebacks to which you apply your
payment. 
Each payment or overflow payment record can accommodate up to eight debit item numbers.
 Invoice 1 to 8 Installment: The installment number for this invoice.
 Invoice Currency Code 1 to 8: The currency of the transaction. This field is used for
cross currency receipt applications. This field is optional.
 Item Number: A sequence number that your bank assigns to a specific payment. This
number associates an invoice with a receipt.
 Lockbox Amount: The total payment amount in a specific lockbox.
 Lockbox Batch Count: The total number of bank batches in a specific lockbox.
 Lockbox Number: The identification number for a specific lockbox.
 Lockbox Record Count: The number of payment records in a specific lockbox (this
does not include overflow payments, headers, or trailers).
 Matching Date 1-8: The dates to use to match receipts with transactions if you are using
the Match on Corresponding Date option for this Lockbox.
 Origination: The bank origination number provided by your bank. This number uniquely
identifies the bank branch that sends you lockbox information.
 Overflow Indicator: This type indicates whether there are any additional overflow
records for this payment.
 Overflow Sequence: A sequence number that your bank assigns to each overflow
payment.
 Receipt Method: The receipt method associated to this lockbox.
 Payment Number: The identification number of a payment. For example, a check
number.
 Receipt Date: The date your customer made a payment.
 Record Identifier: A number that identifies the kind of transmission record. You specify
this number in the Identifier field in the Transmission Formats window.
 Remittance Amount: The amount of a payment.
 Remittance Bank Branch Name: The name of the bank branch from which this
payment originated.
 Remittance Bank Name: The name of the bank from which this payment originated.
 Status: The status of this payment.
 Total Record Count: The total number of transmission records in a bank file. This
includes headers, trailers, payments, and overflow records.
 Trans to Receipt Rate 1 to 8: The exchange rate used to convert the receipt amount
from the receipt currency to the transaction currency. 
This field is used for cross currency receipt applications when the receipt and transaction
currencies do not have a fixed exchange rate (the euro and all NCUs have fixed exchange
rates with each other). If the currencies have a fixed rate, this field is optional (AutoLockbox
derives the rate to use in this case).
 Transit Routing Number: The number that uniquely identifies your customer's bank.
The transit routing number and the customer bank account number make up your customer's
MICR number.
 Transmission Amount: The total amount of payments for a bank file.
Define AutoCash Rule Sets

Define AutoCash Rule Sets to determine the sequence of rules that Post QuickCash uses to
update Customers account balances.
Responsibility: Receivables Manager
Navigation: Setup > Receipts > AutoCash Rule Sets

  

Open Balance Calculation

1. Enter the type of Discount you want to automatically give to your customer for this
AutoCash Rule Set. Choose one of the following Discount options:
o Earned Only: Your customer can take earned discounts according to the receipt
terms of sale. 
You negotiate earned discount percentages when you define specific receipt terms.
You can enter this option if Allow Unearned Discounts is set to Yes in the System
Options window. In this case, Receivables only allows earned discounts for this
AutoCash Rule Set.
o Earned and Unearned: Your customer can take both earned and unearned
discounts. An unearned discount is one taken after the discount period passes. 
You cannot choose this option if the system option Unearned Discounts is set to No.
 o None: Your customer cannot take discounts (this is the default).
2. Check the Items in Dispute check box if you want to include transactions in dispute when
calculating your customer's open balance.
3. Check the Finance Charges if you wish to include late charges when calculating your
customer's open balance.
Automatic Matching Rule

Define the Automatic Matching Rule for this AutoCash Rule set.

1. If this rule set will include the Apply to the Oldest Invoice First rule, choose how you
want to apply anyRemaining Remittance Amount. Receivables uses this value to determine
how to enter the remaining amount of the receipt if none of the AutoCash Rules within this
rule set apply.
o Choose 'Unapplied' to mark remaining receipt amounts as Unapplied.
o Choose 'On-Account' to place remaining receipt amounts On-Account.
2. To automatically apply partial receipts when using the Apply to the Oldest Invoice First
rule, check theApply Partial Receipts check box. 
A partial receipt is one in which the receipt minus the applicable discount does not close
the debit item to which this receipt is applied.
The applicable discount that Receivables uses for this rule depends upon the value you
entered in the Discounts field for this AutoCash Rule Set. If you exclude late charges (by
setting Finance Charges to No) and the amount of your receipt is equal to the amount of the
debit item to which you are applying this receipt minus the late charges, Receivables
defines this receipt as a partial receipt.  In this case, Receivables does not close the debit
item because the late charges for this debit item are still outstanding.
If Apply Partial Receipts is set to No, this AutoCash Rule Set will not apply partial receipts
and will either mark the remaining receipt amount 'Unapplied' or place it on-account,
depending on the value you entered in the Remaining Remittance Amount field.
AutoCash Rules

1. Enter a Sequence number to specify the order of each rule in this AutoCash Rule Set
(optional). Receivables uses the rule assigned to sequence 1, then sequence 2, and so on
when applying receipts using this AutoCash Rule Set.
2. Enter one or more AutoCash Rules for this AutoCash rule set. Choose from the following
AutoCash rules:
o Apply to the Oldest Invoice First: This rule matches receipts to debit and credit
items starting with the oldest item first. 
This rule uses the transaction due date when determining which transaction to apply
to first. This rule uses the values you specified for this AutoCash Rule Set's open
balance calculation to determine your customer's oldest outstanding debit item. Post
QuickCash uses the next rule in the set if any of the following are true:
 all of your debit and credit items are closed.
 the entire receipt amount is applied.
 it encounters a partial receipt application and Allow Partial Receipts is set
to No for this AutoCash Rule Set.
 the next oldest debit item includes late charges and Finance Charges is set
to No for this AutoCash Rule Set
This rule marks any remaining receipt amount 'Unapplied' or places it on-account,
depending on the value you entered in the Remaining Remittance Amount field for
this AutoCash Rule set .

o Clear the Account: Post QuickCash uses this rule only if your customer's
account balance exactly matches the amount of the receipt. If the receipt amount does
not
exactly match this customer's account balance, Post QuickCash uses the next rule in
the set. This rule calculates your customer's account balance by using the values
you specified for this AutoCash Rule Set's open balance calculation and the number
of Discount Grace Days in this customer's profile class. This rule also includes all of
this customer's debit and credit items when calculating their account balance. This
rule ignores the value of the Apply Partial Receipts option.
This AutoCash Rule uses the following equation to calculate the open balance for
each debit item:

Open Balance = Original Balance + Late Charges - Discount

Receivables then adds the balance for each debit item to determine the customer's
total account balance. The 'Clear the Account' rule uses this equation for each invoice,
chargeback, debit memo, credit memo, and application of an Unapplied or On-
Account receipt to a debit item.
 Note: The discount amount for each item depends upon the payment terms of the item
and the value of the Discounts field for this AutoCash Rule Set. The number of
Discount Grace Days in this customer's credit profile, along with the payment terms
assigned to their outstanding invoices, determine the actual due dates of each debit
item.
o Clear Past Due Invoices: This rule is similar to the Clear the Account rule
because it applies the receipt to your customer's debit and credit items only if the total
of these items exactly matches the amount of this receipt. However, this rule only
applies the receipt to items that are currently past due. 
A debit item is considered past due if its due date is earlier than the receipt deposit
date. This rule considers credit items (i.e. any pre-existing, unapplied receipt or credit
memo) to be past due if the deposit date of the receipt is either the same as or later
than the deposit date of this pre-existing receipt or credit memo. In this case, this rule
uses a pre-existing receipt or credit memo before the current receipt for your
AutoCash receipt applications.
If this AutoCash Rule Set's open balance calculation does not include late charges or
disputed items, and this customer has past due items that are in dispute or items with
balances that include late charges, this rule will not close these items. This rule
ignores the value of the Apply Partial Receipts option.
o Clear Past Due Invoices Grouped by Payment Term: This rule is similar to
the Clear Past Due Invoices rule, but it first groups past due invoices by their
payment term, and then uses the oldest transaction due date within the group as the
group due date. When using this rule, Receivables can only apply the receipt if the
receipt amount exactly matches the sum of your customer's credit memos and past due
invoices. 
A debit item is considered past due if the invoice due date is earlier than the deposit
date of the receipt you are applying. For credit memos, Receivables uses the credit
memo date to determine whether to include these amounts in the customer's account
balance. 
Credit memos do not have payment terms, so they are included in each group.
o Match Payment with Invoice: This rule applies the receipt to a single invoice,
debit memo, or chargeback that has a remaining amount due exactly equal to the
receipt
amount. This rule uses the values that you enter for this AutoCash Rule Set's open
 balance calculation to determine the remaining amount due of this customer's debit
items. For example, if Finance Charges is No for this rule set and the amount of this
receipt is equal to the amount due for a debit item minus its late charges, this rule
applies the receipt to that debit item. 
If this rule cannot find a debit item that matches the receipt amount, Post QuickCash
looks at the next rule in the set. This rule ignores the value of the Apply Partial
Receipts option.

Sample Control File

LOAD DATA
APPEND

-- Type 4 - Lockbox Header

INTO TABLE AR_PAYMENTS_INTERFACE

WHEN RECORD_TYPE = '1'
(STATUS CONSTANT 'AR_PLB_NEW_RECORD',
RECORD_TYPE POSITION(01:01) CHAR,
LOCKBOX_NUMBER POSITION(02:09) CHAR,
DEPOSIT_DATE POSITION(11:21) DATE 'DD-MON-YYYY'
NULLIF DEPOSIT_DATE=BLANKS,
DESTINATION_ACCOUNT POSITION(23:47) CHAR,
ORIGINATION POSITION(49:58) CHAR )

-- Type 2 - Receipt

INTO TABLE AR_PAYMENTS_INTERFACE

WHEN RECORD_TYPE = '2'
(STATUS CONSTANT 'AR_PLB_NEW_RECORD',
RECORD_TYPE POSITION(01:01) CHAR,
ITEM_NUMBER POSITION(03:06) CHAR,
REMITTANCE_AMOUNT POSITION(08:17) CHAR,
TRANSIT_ROUTING_NUMBER POSITION(18:26) CHAR,
ACCOUNT POSITION(28:37) CHAR,
CHECK_NUMBER POSITION(39:46) CHAR,
CURRENCY_CODE POSITION(48:50) CHAR,
EXCHANGE_RATE POSITION(53:61) CHAR,
CUSTOMER_NUMBER POSITION(63:76) CHAR,
RECEIPT_DATE POSITION(78:88) DATE 'DD-MON-YYYY'
NULLIF RECEIPT_DATE=BLANKS,
INVOICE1 POSITION(90:109) CHAR,
MATCHING1_DATE POSITION(111:121) DATE 'DD-MON-YYYY'
NULLIF MATCHING1_DATE=BLANKS,
AMOUNT_APPLIED1 POSITION(123:138) CHAR,
INVOICE2 POSITION(140:159) CHAR,
MATCHING2_DATE POSITION(161:171) DATE 'DD-MON-YYYY'
NULLIF MATCHING2_DATE=BLANKS,
AMOUNT_APPLIED2 POSITION(173:188) CHAR,
LOCKBOX_NUMBER POSITION(190:196) CHAR
)

-- Type 3 - Overflow Receipt

INTO TABLE AR_PAYMENTS_INTERFACE

WHEN RECORD_TYPE = '3'
(STATUS CONSTANT 'AR_PLB_NEW_RECORD',
RECORD_TYPE POSITION(01:01) CHAR,
ITEM_NUMBER POSITION(03:05) CHAR,
OVERFLOW_SEQUENCE POSITION(07:08) CHAR,
OVERFLOW_INDICATOR POSITION(10:10) CHAR,
INVOICE3 POSITION(12:31) CHAR,
MATCHING3_DATE POSITION(33:43) DATE 'DD-MON-YYYY'
NULLIF MATCHING3_DATE=BLANKS,
AMOUNT_APPLIED3 POSITION(45:59) CHAR,
INVOICE4 POSITION(61:80) CHAR,
MATCHING4_DATE POSITION(82:92) DATE 'DD-MON-YYYY'
NULLIF MATCHING4_DATE=BLANKS,
AMOUNT_APPLIED4 POSITION(94:108) CHAR,
LOCKBOX_NUMBER POSITION(110:117) CHAR
)

Sample Data File

1JMARTINE 08-NOV-2011 1632811897361982730000000 0000000287

20001 0000001000736198273 0000000000 PAYMENT1 USD 000000000 00000000001007 08-
NOV-2011
3 0001 01 9                   123 08-NOV-2011                                                                  JMARTINE

Running Lockbox

Responsibility: Receivables Manager
Navigation: Interfaces > Lockbox
Import

 If you are importing a new bank file, check the New Transmission check box, then enter
a new Transmission Name. 
If you are resubmitting an existing lockbox transmission, you can select a name from the list
of values.
 Enter the name of the datafile along with path and extension.
 Enter the name of the control file with out extension. Make sure that the control file is in
$AR_TOP/bin directory.
 Select the transmission Format from list of values.
 In the Alternate Name Search field, select Manual or Automatic if you are importing a
bank file with a Japanese Zengin character set. Otherwise, select None.
The default value is None.
Validation

 Check the Submit Validation Check box.

 Enter the Lockbox Number to validate. If this is not a new transmission, the default
lockbox number is the number used for the original step of this transmission. If you specified
Lockbox Number as a value to be imported from the bank file when you defined your
transmission format, or if the transmission format shows that a number already exists,
Receivables skips this field. 
You must enter a lockbox number if Submit Validation is Yes and the lockbox number is not
specified in your bank file.
 To apply receipts to transactions belonging to unrelated customers, check the Allow
Payment of Unrelated Invoices check box.
 If you defined your GL Date as Constant Date in the Lockboxes window, you must enter
a GL Date; if you specified a GL Date of Deposit Date or Import Date, Receivables uses this
as the GL date.
 Enter a Report Format. Enter All to include all records processed in this transmission. 
Enter Rejects Only to include only records that failed validation.
 To transfer only the lockbox batches in which all records pass the validation step to the
QuickCash tables, check the Complete Batches Only check box. 
If you do not check this check box, Receivables will transfer any receipts within a batch that
pass validation, even if others are rejected.
 If the Post Partial Amount as Unapplied box is checked, Lockbox will import a receipt
that is listed to be applied to several invoices, even if one or more of the invoices are invalid
and Lockbox could not apply to them. In this case, Lockbox transfers the receipt into
QuickCash with an unapplied amount, and you can then manually apply payment to a valid
invoice(s) using the Applications window.

Note: When AutoLockbox imports a receipt with an unapplied amount into QuickCash,
Receivables retains the invalid matching numbers in the Application Notes field in the
Receipt History window. You can also display the Application Notes field in the Receipts
Summary or QuickCash windows by choosing Show Field from the Folder menu.

If the Reject Entire Receipt box is checked and AutoLockbox encounters an invalid
transaction number, the receipt that Lockbox cannot fully apply will remain in the
AR_PAYMENTS_INTERFACE_ALL table. In this case, you need to edit the invalid
record(s) in the Lockbox Transmission Data window, then submit the Validation step again
for the receipt.
Post Quick Cash:

 To apply the receipts and update your Customers balances, check Submit post QuickCash
check box.
Save your work. Receivables displays the Request ID of your concurrent process and generates
the Lockbox Execution report.
Maintain Transmission Data

Responsibility: Receivables Manager
Navigation: Receipts > Lockbox > Maintain Transmission Data

Use the Lockbox Transmission Data window to delete and edit transmission data imported into
Receivables from your bank using Lockbox. 
You can correct your lockbox data in this window for receipts that fail validation, then resubmit
the validation step to import these receipts.
Use the Lockbox Execution report to help you determine which transmission records you need to
correct to ensure that your validation processes succeed.
If you are updating information, be sure to update only those fields that have data corresponding
to the transmission format used to submit the import process.
Note: The Lockbox Transmission Data window is a Folder window.
You can customize the appearance of this window by selecting options from the Folder menu.
For example, you may choose to add the Alternate Name and Customer Name fields to your
default folder.

1. Enter or query the lockbox transmission. Within each transmission, Receivables displays
the lockbox and batch records first, followed by the receipts and overflow records. The
lockbox import program assigns a date to transmission records that you import into
Receivables and displays transmissions by date when you query them in this window.
2. To review error messages, place the cursor in the Status field, then choose Edit Field
from the Edit menu. This field is set by the validation process.
3. Enter Comments about this transmission (optional). Receivables transfers comments for
batch header records to the Receipt Batch after you run Post QuickCash. Receivables
transfers batch header comments if the batch header does not include comments. You can
review and update comments about a batch in the Receipt Batches window.
4. If the error is contained in the control, receipt, or application information, you can make
changes to the invalid records by selecting the record, then choosing one of the following:
o Receipt: Choose this button to review and edit specific receipt information. You
can change the values of fields that are included in your transmission format.
o Receipt Attributes: Choose this button to review and maintain receipt descriptive
flexfield information imported with your lockbox transmission. 
You can change the values of fields that are included in your transmission format.
o Applications: Choose this button to review and maintain application information
for each receipt within this transmission. You can apply a receipt to debit or credit
items. When applying to credit items, Receivables increases the amount of the receipt
that can be applied to debit items by the amount of the credit. You can apply up to
eight transactions to each receipt record. To apply more than eight transactions, use
overflow records for your receipt. Each overflow record can be used to apply an
additional eight transactions to the receipt. Use the Status field to review errors for
specific receipt applications.
Select the Cross Currency Data region to review information about cross
currency receipts
 o Control: Choose this button to review the lockbox transmission control
information that corresponds to this transmission record. You can change the values
for fields that are included in your transmission format.

Important: Lockbox formats receipt amounts during the validation step. Therefore,
values in the Lockbox Control window do not contain decimals.
5. Save your work and Resubmit the transmission for validation.
1.

AUTO INVOICE

In Oracle Apps R12

Auto Invoice is a powerful, flexible tool you can use to import and validate transaction data from
other financial systems and create invoices, debit memos, credit memos, and on–account credits
in Oracle Receivables. You use a custom feeder program to transfers transaction data from an
external system into the Auto Invoice interface tables. Auto Invoice then selects data from the
interface tables and creates transaction in Receivables. Receivables rejects transactions with
invalid information to ensure the integrity of your data. You can run Auto Invoice together with
Customer Interface or separately.

Oracle Receivables can create invoices from the following Oracle applications:  Oracle Order
Management, Oracle Projects, Oracle Service, and Oracle Property Manager.
Oracle Receivables can create invoices from the following non-Oracle applications:  Legacy
system (for transaction history), Non-Oracle billing applications, and Non-Oracle order entry
applications.
Oracle Receivables uses three interface tables for Auto Invoice:
1. RA_INTERFACE_LINES
2. RA_INTERFACE_DISTRIBUTIONS
3. RA_INTERFACE_SALESCREDITS
Auto Invoice transfers transaction data from the above three interface tables into the following
Receivables tables:
 RA_BATCHES_ALL
 RA_CUSTOMER_TRX _ALL
 RA_CUSTOMER_TRX_LINES _ALL
 RA_CUST_TRX_LINE_GL_DIST_ALL
 RA_CUST_TRX_LINE_SALESREPS_ALL
 AR_PAYMENT_SCHEDULES_ALL
 AR_RECEIVABLE_APPLICATIONS_ALL
 AR_ADJUSTMENTS_ALL
RA_INTERFACE_LINES:
 This table contains information relating to all transactions to be processed by Auto
Invoice.
 Transactions include invoices, debit memos, credit memos, and on-account credits.
 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 linelevel Freight.
 A child record is linked to the parent record using the Link-To Transaction flex field.
RA_INTERFACE_DISTRIBUTIONS:
 This table contains accounting distributions to be used by the transactions defined in
RA_INTERFACE_LINES.
 Accounts defined in this table override any accounts created using AutoAccounting.
 You can choose to pass some or all account information to Auto Invoice. Any accounts
that are not passed will be derived using Auto Accounting.
 Records in this table are linked to records in the RA_INTERFACE_LINES table using
the Transaction flexfield.
 Not required if AutoAccounting determines GL distributions.
RA_INTERFACE_SALESCREDITS:
 This table contains all sales credit information for the transactions in the
RA_INTERFACE_LINES table.
 The two tables are linked using the Transaction flexfield.
 Not required if not tracking sales credit.
What occurs during auto-invoice:
1. Populates the RA_Interface_Lines, RA_Interface_distribution and
RA_Interface_salescredit tables.
2. Lines are grouped and ordered by the grouping rule and line ordering line. 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.
3. Tax, freight, commitments and credit memos are linked to transaction line by transaction
line, transaction reference and transaction link-to descriptive flex fields. To uniquely identify
imported transactions and link the tax, freight, commitments and credit memos, define the
Transaction flexfields.
4. GL date is determined.
5. GL accounting code combinations are assigned using auto accounting rule.
6. TAX is determined.
7. All transactions are batched.
8. Validated lines are used to create the transaction.
When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice
Validation Report.
Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice
Interface Exceptions window. Depending on the error, changes may need to be made in
Receivables, the feeder program or the imported records in the interface tables.

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.
Types of transaction flexfields:
 Invoice Header (optional): Specifies invoice header information
 Line (required): Uniquely identifies invoice lines
 Link-To (optional): Link tax and freight to invoice lines
 Reference (optional): Links credit memos to transactions
What is inside AutoInvoice?
AutoInvoice is a tool consists of 3 main programs. Each program will have unique nature of
work to do and they are called internally except Purge program whose execution is derived on
the setup otherwise ready to execute stand alone.
 Master (RAXMTR)
 Import (RAXTRX)
 Purge (RAXDEL)
1] Auto Invoice Master program:
Selects and marks records in the interface tables to  be processed based on the parameters the
user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has
no report output.
 Gathers statistics, it means it gathers the stats on interface tables and set the stats on
certain indices on interface tables.
 Marks interface records for processing by marking request_id.
 Submits multiple workers for Parallel Processing by creating instances for request.
2] Auto Invoice Import Program:
Validates the selected record and creates transaction if it passes validation. Any record that fails
validation is left in the interface table with an error code. Depending on the setup, related records
may be rejected as well. This program has an output file called Auto Invoice Execution report,
which you can view by clicking the View Report button in the Requests window.
 Workhorse of Auto invoice
 Validates data
 Inserts records
 Deletes interface data
 Only when system option purge set to ‘Y’
3] Auto Invoice Purge Program:
Deletes records from the interface tables. If you set the Purge Interface Table system option to
No in Define System Option window, Auto Invoice does not delete processed records from the
interface tables after each run, and we must submit Auto Invoice Purge Program periodically to
clean up the interface tables. This program only deletes transaction lines that have been
successfully imported.
AutoInvoice Exception Handling:
Records that fail validation are called ‘Exceptions’
 Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL.
 Errors can be corrected in the Exception Handling window.
 Once corrections are made, Auto invoice must be resubmitted.
 Records that pass validation get transferred to Receivables tables.
AutoInvoice Exception Handling Windows:
 Interface Exception window displays exception messages associated with all invalid
records.
 Interface Lines window displays records that fail validation, provides an error message
and can be used to correct the errors.
 The Line Errors windows displays errors associated with a specific line, and can only be
opened from Interface Lines window.
 Interface Exceptions window displays Interface Id, Exception Type, Error Message and
Invalid Value associated to the error.
 Data cannot be edited in this window, but error can be viewed and corrected by clicking
the Details button.
 Error Message and Column name with invalid data are displayed in the Message column,
and the invalid value that needs to be corrected is displayed in the Invalid Value column.

AUTOINVOICE SETUP FOR R12

Posted by Raju ERP

1. Define Common Accounts Receivable Configuration

Common Accounts configuration pertains to the Accounting Flexfield setup. This is done in the
General Ledger (GL) application. The assumption of this case study is that you have already
defined your accounting flexfield segments, and can create and complete manual transactions
using the Transaction Workbench.

2. Manage Receivables Descriptive Flexfields

Oracle Receivables uses the transaction flexfields to uniquely identify each transaction line that
is imported though AutoInvoice. 

AutoInvoice is capable of using information from four types of transaction flexfields:

 Line Transaction Flexfield
 Link-to Transaction Flexfield
 Reference Transaction Flexfield
 Invoice Transaction Flexfield
  

For this case study, you need to setup a Line Transaction Flexfield as shown below.

Click on the segments button to create the following rows. The values in the field Column are not
shown completely, they are INTERFACE_LINE_ATTRIBUTE1 and
INTERFACE_LINE_ATTRIBUTE2 respectively.
3. Manage Receivables Profile Options
 
A. Security Profile
There are three profile options which govern access to data partitioned by organizations. 

MO: Operating Unit 

R11i profile option that will be maintained for those products and customers not leveraging
Multiple Organizations. 

MO: Security Profile 

The MO Security Profile controls the list of operating units that a responsibility can access.
So you would assign the Security Profile that you just created to this profile option. The
lowest level you can set the profile option for is the responsibility level.

MO: Default Operating Unit 

This allows you to specify an operating unit that will be the default when you open
different subledger application pages. Because users can access multiple operating units,
you may want to set up a default operating unit rather than forcing users to constantly
have to choose one during data entry.  When we talk about the User Preferences later, you
can also specify a different default operating unit than the one assigned to this profile
option.  
B. AR: AutoInvoice Gather Statistics
This profile option determines if the AutoInvoice Master program analyzes and gathers
information about the interface tables each time AutoInvoice is run. Analyzing tables ties
up system resources, but in some cases may address AutoInvoice performance issues.

If the value for this profile option is set to Yes, or is null, AutoInvoice analyzes the interface
tables and gathers statistics. If the value is set to No, AutoInvoice does not analyze the
interface tables. 

This profile option can be set by the system administrator at the site, application,
responsibility, and user levels. The user can also update this profile option.
C. AR: Default Exchange Rate Type
This option determines the default exchange rate to use when converting foreign currency
transactions to your functional currency.
Valid values are: 
 Corporate Exchange Rate - An exchange rate you define to standardize rates. This
rate is usually a standard market rate determined by senior financial management for
use throughout the organization.
 Spot Exchange Rate - An exchange rate to perform a conversion based on the rate
on a specific date.
 User Specified Rate - An exchange rate to specify when entering a foreign currency
transaction.
D. AR: Maximum Lines per AutoInvoice Worker
This profile option lets you set a maximum number of lines per AutoInvoice worker. The
value for this option can be set by the system administrator at the site, application
responsibility, and user levels, but cannot be updated by the user. This profile option has
no default value. 
E. AR: Use Invoice Accounting For Credit Memos

This profile option determines whether to assign your credit memo to the same accounts
that are assigned to the invoice you are crediting. 

The value for this option can be set by the system administrator at the site,
application,responsibility, and user levels, but cannot be updated by the user.  
Note:

If you are interfacing data from Project Accounting, you need to set this profile to No at the
application level for Oracle Projects. This setting will then allow data to be passed into
RA_INTERFACE_DISTRIBUTIONS_ALL table for Projects Invoices.

F. Sequential Numbering
Sequential Numbering assigns numbers to documents that you create in Oracle financial
products. For example, when you are in a window that creates invoices, each invoice
document can be numbered sequentially. 

Sequential numbering provides a method of checking whether documents have been posted
or lost. 
Not all windows within an application can be selected to support sequential numbering. 

Sequential Numbering has the following profile option settings:

 Always Used - You may not enter a document if no sequence exists for it.
 Not Used  - You may always enter a document.
 Partially Used - You will be warned, but not prevented from entering a document,
when no sequence exists.

Only system administrators can change this profile option. Users can see this profile option,
but they cannot update it. 

This profile option is visible and updatable at the site, application, and responsibility
levels. 
4. Manage Transaction Types

The data you insert into the interface table will be associated to a particular transaction type.
Create an invoice transaction type which will be used when we insert data into the Interface
table.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Transaction Types

  

Note: If you also want to run a test case to import a Credit memo, create a Credit Memo
transaction type as shown below, otherwise you don't need to create a Credit Memo transaction
type.

 
5. Manage AutoAccounting Rules

AutoAccounting enables you to create default accounts for revenue, receivable, freight, tax,
unearned revenue, unbilled receivable, late charges, bills receivables accounts, and AutoInvoice
clearing (suspense) accounts.

In the following screen, the source for the third segment is 'Transaction Types'. When the default
accounting is generated for the Receivable account, the accounting flexfield will pull the third
segment from the Receivables account defined for the transaction type. If we cross-reference this
to the screenshot from the previous task, the value for the third segment is 1210, coming from
01-000-1210-0000-000 defined for Receivables account.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > AutoAccounting
During AutoInvoice, you are interfacing data with the intention of creating complete transactions
automatically. Hence, you are advised to complete the setup for AutoAccounting so that
AutoInvoice can determine the GL accounts to use for your interfaced transactions, and process
them completely without errors and without the need for manual intervention.
6. Manage AutoInvoice Line Ordering Rules

If you want the data in your interface table to be created in a particular sort order, define Line
Ordering Rules.

The following screenshot shows a Line Ordering Rule, that references the same fields we used in
the Line transaction flexfield defined in Task 2 above.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > AutoInvoice > Line Ordering Rules

7. Manage AutoInvoice Grouping Rules

Grouping rules specify attributes that must be identical for lines to be created as one transaction.
Grouping rules always include the mandatory attributes, and to this is added optional attributes
that you define in your grouping rule.

The following screenshot shows a Grouping Rule that uses the Line Ordering Rule defined
in Task 6 above.
Responsibility: Receivables Manager
Navigation: Setup > Transactions > AutoInvoice > Grouping Rules

8. Manage Receivables Payment Terms

Payment terms let you define the due date to be calculated for transactions. When you interface
data, it ismandatory to provide either a TERM_ID or a TERM_NAME in the
RA_INTERFACE_LINES_ALL table (depending on how you have set up your transaction batch
source). Although there is a defaulting mechanism for payment term when entering transactions
manually in the form, this is defaulting is not available during AutoInvoice, because it would
significantly slow down the performance of the process.

The following screenshot shows a Payment term we will use in our interface data.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Payment Terms
9. Manage Transaction Sources

Batch sources define default information such as transaction type and automatic numbering.
There are two types available: Manual and Imported. AutoInvoice requires a batch of type
Imported.

The following screenshot shows a Transaction source we will use to interface data via
AutoInvoice. Highlighted below is the transaction type we created earlier, here we are
associating it to this Imported Batch Source.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources
Following screenshots show the sub-tab for the Transaction Sources form:

The AutoInvoice Options tab highlights the Grouping rule created earlier.  The setup indicates
this batch will group data as specified in this grouping rule
The following screenshots show the rest of the sub-tabs of this form, including Customer,
Accounting, Salescredit and other information. You need to define whether the data you will
interface provides the Value or the ID so that AutoInvoice can validate the data.

Customer Information tab:.

 

Accounting Information tab:

Other Information tab:
Sales Credit Validation tab:
10. Manage Receipt Classes and Methods

To default a payment method to the transactions you interface via AutoInvoice, you need to
define a Receipt Class and Method for your transaction to use. 

Responsibility: Receivables Manager
Navigation: Setup > Receipts > Receipt Classes
11. Manage Receivables Customer Profile Classes

Oracle Receivables provides a profile class DEFAULT. 

If necessary, you can define different customer profile classes to categorize your customers. You
can associate Customer Profile classes to customer records you create later. By using a profile
class you default certain attributes/fields into the customer records to make customer
maintenance more efficient.

The following screenshot defines a new customer profile class, to which we associate the
Payment Term from Task 8 and the grouping rule from Task 7. 
Responsibility: Receivables Manager
Navigation: Customers > Profile Classes

12. Create Customer

Create customer record to use for interface data, at this point we reference various setup data we
created earlier.

The following screenshot shows the various sub-tabs at the ACCOUNT profile level.

On the Account Profile tab, we associate to this customer record the customer profile created
in Task 11, the payment term from Task 8 and the Grouping Rule from Task 7 created earlier.

Responsibility: Receivables Manager
Navigation: Customers > Customers
Payment Details tab: here we associate to this customer record the Receipt method created
in Task 10. 
We have defined the Receipt method at the ACCOUNT level profile. If this customer has only
one site, or all the Sites of this customer will use the same Receipt method, there is no need to set
up Payment Details at the Site Level.

However, if there will be multiple sites for this account, and each site that uses a Receipt method
different from that set at the ACCOUNT level, then you will need to set up the Payment Details
at the SITE level as shown below.
13. Manage Receivables System Options

The settings in System Options that impact AutoInvoice are in the Trans and Customers tab. The
following screenshot shows recommended settings for fields in the 'AutoInvoice' Section. Also
highlighted is the Grouping rule we defined earlier.

Log file message level = 10 provides the most detailed debug messages, and is useful when you
are debugging or troubleshooting.

Responsibility: Receivables Manager
Navigation: Setup > System > System Options
14. Manage Receivables Accounting Periods

Open or close periods in your accounting calendar to control the recording of accounting
information for these periods. Since the objective of AutoInvoice is to create new transactions,
the goal is to have these transactions impact open GL periods.

Ensure that the GL_DATE value you provide in the next task is within an open period.

Responsibility: Receivables Manager
Navigation: Control >  Accounting > Open/Close periods

15. Manage Remit-To Address

Define a Remit-To Address so that customers know where to send payment for their invoices.

Responsibility: Receivables Manager
Navigation: Setup > Print > Remit To Address > Create Remit-To Address
16. Define Shipping Parameters:

Navigation: Order Management --> Setup --> Shipping --> Shipping Parameters.

In General Tab.

In Pick Release Tab:

In Shipping Transaction Tab:
17. Define Transaction Type Line:

Navigation: Order Management --> Setup --> Transaction Type -->Define.

In Shipping Tab:
In Finance Tab:
Save your work.

18. Define Transaction Type Order:

Navigation: Order Management --> Setup --> Transaction Type --> Define

In Main Tab:
Click On Assign Line Flows:
Save your work.

19. Define Grants and Roles:

Navigation: Order Management --> Setup --> Shipping --> Grants and Role Definitions -->
Grants.
20. Testing AutoInvoice:  AutoInvoice Import Process

Once the data is inserted into the Interface table, we are ready to submit the AutoInvoice Import
Process
Responsibility: Receivables Manager
Navigation: Interfaces > AutoInvoice
To monitor the progress of the process, 
Navigation: View > Requests
click on Find Button

 
 

21. Review Invoice Created by AutoInvoice

To verify whether AutoInvoice created the invoice successfully, view the invoice in the
Transaction workbench.

Responsibility: Receivables Manager

Navigation: Transactions > Transactions

Then run a Query using View > Query By Example

Enter the following filters:
 Batch Source name = 'TIP BATCH SOURCE'
 Reference field =
 for the Invoice: enter the value you provided for interface_line_attribute1 = 'TIP
SAMPLE INVOICE 1'
 for the Credit memo (if you also ran this test): enter the value you provided for
interface_line_attribute1 = 'TIP SAMPLE CM 1' or  'TIP SAMPLE CM 2'
 for the Invoice with rules: enter the valud you provided for
interface_line_attribute1 = 'TIP RULE INVOICE 1'
 

Then execute the query.

Click on Line Items button to see invoice lines.