Oracle Receivables Lockbox: Frequently Asked Questions (FAQ) (Doc ID 1075485.1)

10/27/2017 Document 1075485.
Oracle Receivables Lockbox: Frequently Asked Questions (FAQ) (Doc ID 1075485.1)
In this Document
Purpose
Questions and Answers
1. Is it mandatory to always use import step of lockbox for importing the bank data?
2. What table needs to be populated is using Lockbox via a custom program?
3. How can the data be reviewed after it is successfully imported and validated?
4. Where can I review receipts that failed during validation?
5. What are the various transmission status possible?
6. Why does the Status of AR_TRANSMISSIONS not change when deleting batch and receipts
Symptoms
Explanation
7. Can I apply a QuickCash Receipt to Multiple Transactions?
8. Can I apply a receipt to another customer's transaction?
9. Can I apply a Quickcash receipt against open receipts?
10. When is the Autocash Rule used?
11. What are the various Autocash rule options?
12. How are the discounts handled in post quick cash?
Setup Considerations
How are discounts calculated in lockbox
13. Where is the data stored after validation?
14. How to purge the data from interface and interim tables?
15. What are the various stages in the lockbox process and can I execute all the steps in one single request?
16. How to obtain detailed log from lockbox when there are errors during execution?
17. What are the things to check when receiving the error "Lockbox with this number does not exist in this transmission".
18. How is the org_id populated by Lockbox in case of multi org environment when it is not specified in the data file?
19. Can a single data file have data belonging to multiple organizations?
20. Can I create a single Transmission record Type which includes both receipt and application details.
21. How are customers identified by Lockbox?
22. Control Count And Control Amount Of Remittance Batch is Not Updated After Receipt Reversal
23. Receipt batch was posted by lockbox twice thus creating duplicate receipts
Explanation
Solution
24. The batch type of some of the Lockbox batches in the Batches Summary form is Manual-Regular while other Lockbox
batches are Manual-Quick.
25. How can the Receipt Information Descriptive Flexfield Information be imported through AutoLockbox?
25. How to enter the MICR number manually in the bank form in order for theLockbox process to recognize it.
26. When applying receipts imported using Lockbox, in the Post QuickCash mode, 'Receipt Write-Off' Receivable Activity
is not available
27. Does Autolockbox allow to import receipts for multiple lockboxes in one transmission file from the bank?
28. Is it Possible To Schedule A Lockbox Processing Request?
29. How to Setup Lockbox To Create Claims for Trade Management
Setup Required:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v57g0gm52_202&id=1075485.1 1/39
10/27/2017 Document 1075485.1
30. Can Autocash Rule Place A Receipt On Account If Entire Receipt Can't Be Applied?
31. Can lockbox apply receipts to an inactive customer record?
32. How to Purge Lockbox Transmission History From AR_TRANSMISSIONS_ALL
33. What is the filename for the control file of the transmission format?
Is it mandatory to use one of these 3 scripts?
Can these scripts be modified?
Are all 8 record types required(as in ardeft.ctl), or just 3 (as in arxmpl.ctl), or can all records be the same record type,
as you have in the flat file you are loading from?
34. How To Use AutoCash Rules to Apply Receipts Imported Using Lockbox
35. During the AutoLockbox process, Post QuickCash failed to apply a receipt with the status of UNAPPLIED using the
AutoCash Rule CLRACCT (Clear the Account)
36. How To Run A Lockbox Without Entering The Lockbox Number
37. Lockbox Receipts created as Unapplied instead of 'On Account', as setup in the autocash rule set
Following circumstances concur:
Solution:
38. How can a new Date Format be set up for Lockbox transmission formats?
39. Can Adjustments be created through Lockbox?
40. How to default the bill to location in Lockbox?
41. How To Populate The Field "Customer Reference" Displayed In Receipt Application Window For Lockbox Receipts
42. How Can User Apply Single Receipt To More Than 8 Invoices Using Lockbox Process
43. How Lockbox handles Receipt Number using Fill Symbol and Justify setup?
Case I
Case II
Explanation:
44. How to Derive The Check Digit in The Transit Routing Number?
Symptoms
How to derive the check digit to correct the MICR number:
United States
Validation Rules
Check Algorithm for Routing Transit Number
For Example:
Other Countries
45. What are the Order and Defaults used by Lockbox Autoassociate to Identify Customers?
46. How to populate Global attributes in AR_RECEIVABLES_APPLICATIONS_ALL when using Lockbox in Brazilian
Localizations?
47. Receipt has INVALID APPLICATIONS for all records, valid as well as invalid?
48. How are miscellaneous cash identified through AutoLockbox?
49. How does Lockbox process the match if there are several different occurrences of the Matching Number?
50. When does AutoLockbox consider an invoice to be a duplicate?
51. How does On Account rule in Autocash Lockbox work?
Example: case A:
Example: case B:
52. If Customer only gives the Consolidated Billing Number as part of the autolockbox file will it apply the receipt to all
invoices associated with that CBI number?
53. Why is Lockbox receipt is rejected with duplicate MICR number?
10/27/2017 Document 1075485.1
54. Can Output Be Reduced In The Lockbox Execution Report?

55. ARXLBSUB: When Submitting Lockbox Cannot Manually Enter A GL_DATE
56. Is it possible to automate the creation of Claims for receipt balances that are not linked to any invoice?
57. Where does the value for transmission_request_id come from?
58. ARLPLB: Log File is Extremely Large and Seems to Repeat Itself.
58. Batch Type Can Be Changed After Lockbox Has Been Processed
59. Records Deleted From AR_PAYMENT_SCHEDULES_ALLAre Still Displayed In The Lockbox Transmission History
Window
60. What Tables Are Updated When Lockbox Finds a MICR Number?
61. Can a Bank File in BAI2 Format Be Defined As A Transmission Format?
62. Lines Have Been Deleted From the Maintain Transmission Form (ARXLPIM )
63. How To Put Lockbox Receipts On-Account
64. Can Lockbox Be Submitted From the Command Line?
65. What is the File Name For Post Quickcash Execution Report
66. Importing a receipt via Lockbox, Apply Date on the receipt application is defaulting to Receipt Date and not System
date like a manual receipt application via the form.
67. Lockbox import does not import data according to the column break-down specified in the control file.
68. Does the AR lockbox process allow tab delimited control files?
69. How to use customer_reference and customer_reason in AutoLockbox
70. Evaluate for Claims Eligibility Field is Missing from Lockbox Form
71. Can a file have multiple batches for the same Lockbox number, origination, and account?
72. Does The Receipt To Receipt Application Functionality Work With Lockbox?
73. Why Lockbox Creates And Apply Receipts Even When There is ERROR Batch amount does not equal sum of receipt
amounts
74. How AutoLockbox Applies Receipts
75. Will Lockbox apply to all transactions belonging to a SO/PO?
76. Why does Lockbox allow applying a receipt to same transaction twice?
Feedback
Community Discussions
References
APPLIES TO:
Oracle Receivables - Version 11.5.10.0 and later

Information in this document applies to any platform.
Form:ARXLPIM.FMB - Maintain Lockbox Transmission Data
Form:ARXLBSUB.FMB - Submit Lockbox Processing
Executable:ARLPLB - Process Lockboxes
Form:ARXLBHIS.FMB - View Transmission History
PURPOSE
Oracle Receivables (AR): Receipts Workbench Information Center > Note 1075485.1
This document discusses some of the commonly asked questions about Auto Lockbox process in Oracle Receivables. All
features mentioned are current as of the latest release till 12.1.3.
10/27/2017 Document 1075485.1
Since this document is long and contains a variety of issues/information, we suggest you use the string search (CTRL-F)
function to find keywords in this document that pertain to the issue you are researching.
QUESTIONS AND ANSWERS
1. Is it mandatory to always use import step of lockbox for importing the bank data?
It is not necessary to use the import step of lockbox, data can be imported through SQL*Loader or any other custom program
to populate data in the interface table.
2. What table needs to be populated is using Lockbox via a custom program?
Data need to be populated in AR_PAYMENTS_INTERFACE_ALL.
3. How can the data be reviewed after it is successfully imported and validated?
After successfully import and validate receipts using Lockbox, we can review them in the QuickCash window. Use the
Transmission region in the Receipt Batches window to query all receipt batches that were included in one transmission and to
update or delete any receipt information.
We can review Lockbox receipts before or after you run Post QuickCash. If we have submitted Post QuickCash for this lockbox
transmission, you can review these receipts only in the Receipts or the Adjustments window.
4. Where can I review receipts that failed during validation?
You can review receipts that failed the validation step in the Lockbox Transmission Data window.
Responsibility: Receivables Manager
Navigation: Receipts > Lockbox > Transmission History
Receivables keeps track of each lockbox transmission you submit through the Submit Lockbox Processing window.
Use the Lockbox Transmission History window to review information about your lockbox transmissions such as the
origination date, the number and amount of records in a transmission, and the number and amount of receipts that
passed the validation step.
The Control Count and Amount fields display the total number and amount of records in this lockbox transmission. The
Validated Count and Amount fields display the total number and amount of receipts in this transmission that passed the
validation step.
A status of OOB Out of Balance means: One or more of the receipts in this transmission was rejected during validation.
Go to Maintain Transmission Data to view the detail of this receipt. There is no need to update the status or delete the
record.
Navigation: Receipts > Lockbox > Maintain Transmission Data

.
5. What are the various transmission status possible?
A Lockbox transmission can have one of the following statuses:
New: This transmission has been imported into Receivables but has not yet been validated.
Out of Balance: One or more of the receipts in this transmission was rejected during validation.
Open: All of the receipts in this transmission have been successfully validated and transferred into Receivables. Post
QuickCash has not yet processed these receipts.
Closed: All of the receipts in this transmission have been successfully processed by Post QuickCash. You can review
these receipts in the Receipts window.
6. Why does the Status of AR_TRANSMISSIONS not change when deleting batch and receipts
Symptoms
10/27/2017 Document 1075485.1
Receipts are being deleted before Lockbox validation has been run
Status of AR_transmissions does not change when deleting batch and receipts
Unused transmission names are included in Transmission Name field LOV
Transmissions have no content
Receipts are not shown in the Maintain Lockbox Transmission Data Form
No receipts in AR_PAYMENTS_INTERFACE_ALL
Before the validate Lockbox receipts step has been run, the transmission will have status NB, that is new, in the
AR_TRANSMISSIONS table.
Explanation
This is intended behavior:
If these receipts are deleted before validation, the status will not be updated in the AR_TRANSMISSIONS table, and the
transmission will remain open.
Post QuickCash can be submitted even when no more batch and receipt exists for the transmission. It will just update
ar_transmissions set status='CL'
The status is updated to 'CL' by submitting Post Quick Cash from the lockbox screen. Creating and closing a
transmission can be done only in the lockbox form.
7. Can I apply a QuickCash Receipt to Multiple Transactions?
You can apply a QuickCash receipt to several transactions by choosing an application type of Multiple
. You then select to which
transactions you want to apply this receipt in the Applications window. Receivable does not actually update your customer's
balance until you run Post QuickCash.
You can apply a receipt to a transaction even if the GL date is in a future accounting period or the transaction currency is
different from the receipt currency.
To apply a QuickCash receipt to several transactions:
1. Navigate to the Receipt Batches window

Navigation: Receipts > Receipt Batches
2. Query or enter the QuickCash batch.
3. Choose Receipts.
4. If this is a new batch, enter receipt information and choose an Application Type
5. Choose the Multiple button.
6. Enter a transaction or open receipt, or select one from the list of values.
7. Enter the amount of the receipt to apply to this transaction.
8. Can I apply a receipt to another customer's transaction?
You can also apply a receipt to other customer's transactions if the system option Allow Payment of Unrelated Invoices is set
to Yes.
9. Can I apply a Quickcash receipt against open receipts?
You can also apply a QuickCash receipt against open receipts that are in the same currency. To net receipts, you apply a
receipt against another open receipt, and then apply the resulting unapplied receipt balance to a transaction.
Open receipts include receipts that have:
Unapplied cash
On-account cash
Open claim investigation applications
You can also apply one receipt against another receipt that has an open claim investigation application. A claim investigation
application results from either a non invoice-related deduction or an overpayment of Multiple. If the receipt currency is
different from the batch currency, specify exchange rate information.
10. When is the Autocash Rule used?
10/27/2017 Document 1075485.1
When you run Post Quickcash to apply your customer's receipts, Receivables tries to use each Autocash rule within an
Autocash rule set to find out the transaction to apply.
11. What are the various Autocash rule options?
Following are the Autocash rules you can use:
Match Payment with Invoice

Clear the Account
Clear Past Due Invoices
Clear Past Due Invoices Grouped by Payment Term
Apply to the Oldest Invoice First
Note: When using this rule, Receivables applies receipts to your customer's debit and credit items starting with the
item having the oldest due date. Receivables uses the values that you entered for the open balance calculation and
your automatic matching rules to determine your customer's oldest outstanding item.
12. How are the discounts handled in post quick cash?
Receivables uses the discount values that you assigned to your AutoCash rule set along with the payment terms, discount
grace days, system options, transaction date, and receipt apply date to determine whether to include discount amounts.
Setup Considerations
1. System options Allow Unearned Discounts and Discount on Partial Payment.

The navigation to System Options setup is:

Navigation: Setup > System Option > Miscellaneous Tab
10/27/2017 Document 1075485.1
Select check box for Discounts on Partial Payments and Allow unearned discounts
2. The Payment Terms screen also has a check box for Allow Discount on Partial Payments which must be set.
10/27/2017 Document 1075485.1
Navigation: Setup > Transactions > Payment Terms.
3. Customer must be assigned a profile set to Allow Discounts:

10/27/2017 Document 1075485.1
Navigation: Customers > Profile Classes
4. Enhancement request Bug 9288902 SETUP OPTION NOT TO CALCULATE UNEARNED DISC FOR APPLICATIONS VIA
LOCKBOX introduces a new functionality on how discounts are handled
This patch will introduce a new checkbox A pply Unearned Discount in :

Lockbox Submission Screen
Receipt Batches Quick Cash Screen
The Lockbox/Postbatch screen will apply the unearned discount based on this option. This option will be enabled only if
the system option Apply Unearned Discount is checked
A new parameter Apply Unearned Discount is added to the concurrent program Postbatch Master Program
and the
calculation of unearned discounts by PostQuick Cash program submitted through SRS is based on the value chosen for
this parameter. If the checkbox Apply Unearned Discountin the system options in not set, then unearned discount will
not be calculated irrespective of the value chosen for the parameter Apply Unearned Discount
during the SRS
submission.
5. The discount can be manually overridden in the Receipts window.
How are discounts calculated in lockbox
When executing lockbox, discounts are calculated by the Post QuickCash execution program:
1. If you choose any of the AutoCash rules, Post QuickCash first takes into account the maximum discount available
before trying to apply the receipt.
For example, you are using Apply to the Oldest Invoice First as your AutoCash rule and your oldest invoice is $1000.
The payment term associated with this invoice allows a maximum discount of $100 and your receipt amount is $6000.
Post QuickCash first applies the $100 discount, which reduces the remaining amount of the invoice to $900, and then
applies $900 of the receipt to close the invoice.
After the application, you are left with $5100 to apply to the next oldest invoice.
2. If you are using one of the matching rules, such as Match Payment with Invoice, the receipt must match the invoice
after the discount is taken.
For example, if you have an invoice for $1000 and a maximum discount of $200, your receipt must be $800 before Post
QuickCash can apply it to the invoice.
10/27/2017 Document 1075485.1
See: Post QuickCash., page 6-110 When the Discount Amount Exceeds the Maximum Discount When the discount
amount exceeds the maximum discount, Receivables uses the maximum discount as the discount taken.
Receivables uses the following formulas to determine the earned discount amount and the maximum discount:
Earned Discount = (Receipt Amount * Discount Percent) / 1 - Discount Percent
Maximum Discount = Discount Taken * Amount Due Original - Highest Discount
13. Where is the data stored after validation?
Data gets imported to interim tables after successful validation.

The tables are
AR_INTERIM_CASH_RECEIPTS
AR_INTERIM_CASH_RECEIPT_LINES
14. How to purge the data from interface and interim tables?
Archive/Purge programs can be executed to purge the processed data.

Please ensure the following:
1. Submit Lockbox Validation Processing and ensure it runs without errors before running the Archive/Purge programs.
2. Before data is purged from AR_PAYMENTS_INTERFACE, run Post QuickCash before the Archive/Purge programs. Before
data is purged from
AR_INTERIM_CASH_RECEIPTS
AR_INTERIM_CASH_RECEIPT_LINES
15. What are the various stages in the lockbox process and can I execute all the steps in one single request?
The various stages in lockbox are as below:
1. Import
2. Validation
3. Post Quickcash
These steps can be submitted individually or at the same time from the submit Lockbox Processing window.
16. How to obtain detailed log from lockbox when there are errors during execution?
1. Set Profile Option AR: Debug Level for Lockbox and PostBatch to 3.
2. After setting the profile, re-submit lockbox program and check the log for more details.
17. What are the things to check when receiving the error "Lockbox with this number does not exist in this
transmission".
Please re-test the issue with a new transmission and then submit import and validation.
If there is no header information being passed though it is defined in the Transmission format, please include the same
in the data file and re-test the issue.
18. How is the org_id populated by Lockbox in case of multi org environment when it is not specified in the data
file?
In case of multi org environment The org_id is populated based on the Operating Unit selected while submitting lockbox
program.
19. Can a single data file have data belonging to multiple organizations?
No, Since the Org id is populated based on the operating unit selected while submitting lockbox program you can only have
data pertaining to one org per data file.
20. Can I create a single Transmission record Type which includes both receipt and application details.
10/27/2017 Document 1075485.1
Yes a single Transmission Record Type can be used to include the details of payment and overflow payment.
Transmission Format need to be defined in such a way so that it includes the mandatory information related to receipt and the
invoice to which the receipt need to be applied.
21. How are customers identified by Lockbox?
AutoLockbox can validate your customer data based on the following attributes . If no match is found, the receipt is imported
as Unidentified receipt. This unidentified receipts can be identified and then applied from the Quick cash window or the receipt
window.
1. Customer Number: If you provide a customer number for receipts that you import through AutoLockbox, Receivables
can identify the customer to which the receipt belongs .
2. MICR Number: The MICR (Magnetic Ink Character Recognition) number that appears on each receipt relates the
customer to a bank. Lockbox only uses MICR numbers to associate a customer with a receipt when the MICR number is
passed and the customer number is not included in the transmission format.
A MICR number consists of two segments. The first segment is the Transit Routing number, this identifies the
bank from which your customer draws their check. The second segment identifies your customer's bank account.
If the data file is having a new MICR number, and AutoLockbox was able to identify the customer using another
method, Receivables stores the new number for future reference.
If customer number was also passed along with the MICR in the first run both get associated.
If there is a invoice number to which this receipt need to be applied then MICR will be associated with the
customer of the invoice and stored.
If there are multiple invoices then they should belong to same customer.
Receipts are imported as unidentified for the first time when the data file has only MICR number and no invoice
details through which system can identify the customer. In this case as system can not associate this number
with the customer hence receipt is created as unidentified. After that when we apply the receipt to an invoice
that MICR will be associated with the customer of the invoice, so in the subsequent imports when MICR is
provided then system will associate it to the customer and import the receipt as unapplied if no invoices
mentioned or applied if the invoice details are provided.
MICR number should be valid and for the validation process please refer
See section How to Derive The Check Digit in The Transit Routing Number? in Note 1075485.1 which describes
how check digit is derived in MICR number.
3. AutoAssociate: If the customer cannot be identified from either the MICR number or the customer number (for
example, if the transmission does not include this information), you can use AutoAssociate to determine the customer
using matching numbers. A matching number can be a transaction number, consolidated billing invoice number, sales
order number, purchase order number or another custom defined number.
4. Associate Receipts with Billing Locations: Receivables also lets you track receipts for each of your customer's billing
locations. To use this feature, you must include a billing location in your transmission format, data file and the flag
'Require Billing Location for Receipts' should be set to Yes. This option should be set to yes both at system options and
at the setup of Lockbox.
The setting at the system options level determines whether PostQuickCash can process receipts with / without
billing locations.
10/27/2017 Document 1075485.1
If the box is checked at the Lockbox, the receipt will be validated only if the billing location is provided.
10/27/2017 Document 1075485.1
22. Control Count And Control Amount Of Remittance Batch is Not Updated After Receipt Reversal
This is the intended functionality, the control totals on the Main Remittance window will reflect the total count and amount in
the batch (including reversed receipts), and the count and amount on the Maintain Remittances window will show the running
total for the current selection, that does not show the reversed receipts.
23. Receipt batch was posted by lockbox twice thus creating duplicate receipts
Explanation
1. A Receipt is considered to be a duplicate by LockBox (which will cause an error message and not post twice) when all
following criteria is met:
same receipt number
same amount
same currency
same customer number
same batch
Any receipt that doesn't meet all above criteria will be allowed to post twice by Receivables. The system will not prevent
user from entering a second receipt against an invoice even if the receipt number is the same as a previous receipt.
The reason is this transaction can be a legitimate transaction under certain conditions and we can't make it an error.
Note: If proper controls are not in place, it is possible to re import and reapply receipts that Auto Lockbox has
already processed. We recommend that you establish standard operating procedures to ensure that users do not
process the same bank file more than once using Auto Lockbox.
2. The import phase only does validation on whether or not the data file has the same information setup as the control file
and that the required fields are present in the control file. The data itself is not validated until the validation stage.
It is at this point that the user will be warned of duplicate records which can be deleted in the maintain lockbox
transmission data form, but only if they are duplicated in the same batch.
A receipt will only be detected as a duplicate if it is in the same batch
3. Enhancement request Bug 673426 has been raised requesting a change to the Lockbox program so that it detects
when an entire batch is imported a second time
Please monitor this enhancement request via My Oracle Support
As a workaround, check what data is still in the AR_INTERIM_CASH_RECEIPTS table and the
AR_PAYMENTS_INTERFACE table and delete any duplicated records from the AR_PAYMENTS_INTERFACE table
Solution
Reverse every receipt in the batch one by one.

Navigation: Receipts > Receipts
Query the receipt to reverse.

Choose Applications.
Choose Reverse.
Enter the reversal date, category, and reason.
Choose Reverse, Receivables will generate a number for the reversal.
10/27/2017 Document 1075485.1
24. The batch type of some of the Lockbox batches in the Batches Summary form is Manual-Regular while other
Lockbox batches are Manual-Quick.

Navigation: Receipts >Batches Summary
Query Batch Source=Lockbox%
The state of Post QuickCash affects the batch type
1. When the Process Lockbox is submitted without the Submit Post QuickCash, the batches come through as Manual-
Quick
2. The batch will switch to Manual-Regular from Manual-Quick after Post Quick Cash is submitted and there are no
transactional issues.
3. The batch will remain in a Manual-Quick & Open status even after submitting Post Quick Cash if there are receipt
applications that need to be cleaned up.
4. Once everything is cleaned up and Post QuickCash is submitted, the batch will switch to Manual-Regular and closed if
all receipts are applied and match the control count & amount.
25. How can the Receipt Information Descriptive Flexfield Information be imported through AutoLockbox?
Receipt Information context sensitive descriptive flexfield data is stored in AR_CASH_RECEIPTS_ALL in

ATTRIBUTE_CATEGORY and ATTRIBUTE(N) columns;
however, ATTRIBUTE_CATEGORY column is not available from the lov for the field type in the Transmission fields form
accessed by Navigating to :

Navigation: Setup > Receipts > Lockboxes > Transmission Formats
Transmission Formats definitions are used for validation purposes only and Lockbox does not validate the
ATTRIBUTE_CATEGORY column thus not defining this Field Type in the Transmission Formats form does not prevent Lockbox
from bringing it in to the AR_CASH_RECEIPTS_ALL table.
Thus, as long as you modify the control file to populate the ATTRIBUTE_CATEGORY column of the
AR_PAYMENTS_INTERFACE_ALL table the Lockbox process will populate the AR_INTERIM_CASH_RECEIPTS_ALL table and
Post QuickCash will populate the AR_CASH_RECEIPTS_ALL table with the ATTRIBUTE_CATEGORY information that was passed
from the transmission file. You do not have to add the ATTRIBUTE_CATEGORY field type to the Transmission Formats.
25. How to enter the MICR number manually in the bank form in order for theLockbox process to recognize it.
If the MICR number is NOT in the system yet and is imported in the lockbox data file, then the MICR bank will be
created on the fly. The receipt will need another means such as AutoAssociate (to an invoice number) to identify. The
next import with the MICR number should allow to identify on this MICR.
If you are manually entering a MICR bank, you will enter under
Responsibility:Receivables Manager
Navigation: Setup > Receipts > Banks.
Lockbox uses the following sql logic when looking at the MICR:
SELECT bank_branch_id
FROM ap_bank_branches
WHERE ((bank_num = <Transit Routing Number> AND bank_number is null)
OR ( bank_name = <Transit Routing Number>
and bank_branch_name = <Transit Routing Number>));
bank_num = Transit Routing Number
10/27/2017 Document 1075485.1
bank_name = Transit Routing Number
bank_branch_name = Transit Routing Number
Thus, looking at the header bank record:
1. You can either have a bank name as anything (i.e. Lockbox Bank) and a bank_num (transit routing number)
entered. Bank_num is on the right hand side in the Number field of Bank Branch.
2. Or you can have your bank name equal your transit routing number AND the bank_branch_name equal your
transit routing number.
26. When applying receipts imported using Lockbox, in the Post QuickCash mode, 'Receipt Write-Off'
Receivable Activity is not available
This is intended functionality.

The receipt-write off Receivable Activity is only available in manual receipts.
27. Does Autolockbox allow to import receipts for multiple lockboxes in one transmission file from the bank?
Yes, Autolockbox does allow multiple lockboxes in one transmission file; however the bank origination number for these
lockboxes should be same.
28. Is it Possible To Schedule A Lockbox Processing Request?
The only supported way to submit lockbox is via the Lockbox Submission form. Unfortunately this is the
limitation of the product as the form is designed to perform certain validations prior to spawning the request to process
lockbox.
Enhancement Request BUG 2755435 ADD LOCKBOX CONCURRENT PROGRAM -ABILITY TO SCHEDULE has already been
logged requesting for this functionality.
29. How to Setup Lockbox To Create Claims for Trade Management
Setup Required:
Create a Transmission Format with Customer Reference and Customer Reason.

10/27/2017 Document 1075485.1
Create or Update Lockbox definition with Evaluate for Claim Eligibility flag checked.
Navigation: Setup > Receipts > Lockboxes > Lockboxes
10/27/2017 Document 1075485.1
Using the System Options > Claims tab you can indicate claim handling preferences.
Navigation: Setup > System > System Options
Setup the Claim Investigation GL Account on Receipt Class/Receipt Method

Navigation: Setup > Receipts > Receipt Classes
10/27/2017 Document 1075485.1
Define a receivables activity of type Claim Investigation for each combination of

receipt class and receipt method.
Navigation: Setup > Receipts > Receivable Activities
10/27/2017 Document 1075485.1
Make sure that Profile Option AR: Allow Overapplication In Lockbox is 'No'
Set the transaction type to not allow overapplication
Navigation: Setup > Transactions > Transactions Types
10/27/2017 Document 1075485.1
Verify that you have completed all the required setups in Trade Management. A claim creation request to Trade
Management will fail if the user has not defined the required setup for a claim. The required setup includes
Claim Reasons
Default Reasons
Claim Type
Owner.
Prior to any other validation, this check should be done if the either Unmatched remittance lines preparation is set to yes or
the create claims checkbox is checked in the Receivables System Options
window. If the setup verification fails, then the
program should error out and update the log file to indicate that the setup in Trade Management is not complete.
During PostBatch, Trade Management is called. Trade Management will attempt to translate the customer reason code
provided by the QuickCash entry. If the reason cannot be translated, the default code defined in Trade Management will be
assigned. Once the claim has been created, Trade Management will respond back to the Receivables call with the claim
number and access to the claim reason.
For more information, please take check Oracle Receivables User Guide R12, page 4-104 - How AutoLockbox Creates Claims.
30. Can Autocash Rule Place A Receipt On Account If Entire Receipt Can't Be Applied?
According to Oracle Receivables User Guide R12 this is not possible
In the example used, a receipt for $600 is received and is applied first to receipt #124 for $300, then to receipt $123 for $200.
The Remaining receipt balance of $100 is placed on account because the Apply Partial Receipts
Matching Rule is set to "No".
As an alternative to AutoCash, one might consider implementing a Custom Matching Rule.

This API is defined on page 7-113 of the AR User guide and allows custom SQL code to use in defining how receipts are
matched.
31. Can lockbox apply receipts to an inactive customer record?
Yes, Lockbox can apply to an invoice if the customer is inactive. This is because an inactive customer may have open invoices
to pay still.
32. How to Purge Lockbox Transmission History From AR_TRANSMISSIONS_ALL
10/27/2017 Document 1075485.1
There is no program to delete this data.
Deleting the row corresponding to the transmission from this table, would clear the same from the Lockbox Transmission
History form. You may take a backup of the table before performing the same. After you run the delete make sure to issue a
COMMIT; statement to finalize your changes to the database.
33. What is the filename for the control file of the transmission format?
Use the Transmission Formats window to define the transmission format that Lockbox uses when importing data into
Receivables.
Transmission formats specify how data in your lockbox bank file is organized so it can be successfully imported into the
Receivables interface tables. The control file used by SQL Loader maps the data in the bank file to tables and columns in the
Oracle database.
The transmission format must match the control file that you create.
You can define as many transmission formats as you want.
4 sample loader scripts are provided with Oracle Receivables:
Example (arxmpl.ctl): A format that contains an example of lockbox header information, several
receipt records, and overflow receipt records. Arxmpl.ctl reads only 3 different record types (1, 2, and 3).
Default (ardeft.ctl): A standard BAI (Bank Administration Institute) format used by most of the banks.Ardeft.ctl reads 8
record types (1, 2, 5, 6, 4, 7, 8, 9).
Convert (arconv.ctl): A standard format used for transferring payment information from others systems
Zengin (arzeng.ctl): A format used to import bank files in the Japanese Zengin format.
Is it mandatory to use one of these 3 scripts?
Yes, you need to use one of the SQL*Loader scripts provided as it is a validation
program as well. - if your Bank is using standard BAI Transmission format you could use "ardeft.ctl", else other one.
The Bank Administration Institute (BAI) is a professional organization devoted exclusively to improving the competitive
position of banking companies through strategic research.
BAI conducts a number of major strategic studies each year and has proven to be the best resource for Standards in the
United States.
Other countries have reviewed BAIs findings and have adopted their format.
Can these scripts be modified?
Yes
You use an SQL*Loader control file to import data from bank files to Receivables. If you define a different transmission
format or edit the existing Default or Convert formats, you must edit the SQL*Loader control file before you can import
data into Receivables.
The transmission format is used by the validation program to ensure that data is correctly transferred from the bank file into
Receivables.
Are all 8 record types required(as in ardeft.ctl), or just 3 (as in arxmpl.ctl), or can all records be the same record type,
as you have in the flat file you are loading from?
Your bank file may contain only a few of all the record types, however, you should define your transmission format to only
include those record types which your Bank file is using. The interface works fine with just one record type (detail).
However, if any data file contains records for more than one batch, it is necessary to include a batch trailer record for each
batch.
10/27/2017 Document 1075485.1
34. How To Use AutoCash Rules to Apply Receipts Imported Using Lockbox
1. Include the MICR or customer number in the source datafile

2. Do not include matching numbers in your datafile, otherwise, Post Quick cash will apply the receipt to each transaction
for which it can find a match.
3. Specify an AutoCash Rule set for your customer's profile class
Responsibility:Receivables Manager
Navigation: Customers > Profile Classes
Otherwise, Receivables uses the AutoCash Rule set in the System Options window
Navigation: Setup > System > System Options
10/27/2017 Document 1075485.1
35. During the AutoLockbox process, Post QuickCash failed to apply a receipt with the status of UNAPPLIED
using the AutoCash Rule CLRACCT (Clear the Account)
This is expected functionality.
CLRACCT AutoCash Rule can only apply the receipt if the receipt amount matches the customer's open balance.
Receivables includes all open debit and credit items when calculating the customer's open balance.
Open credit items include credit memos, on-account credits, and on-account and unapplied cash.
A receipt with a status of UNAPPLIED cannot be applied by the CLRACCT AutoCash Rule if the total amount of the
customer's balance does not match the amount of the receipt or has a credit balance.
For more information see

Oracle Receivables Implementation Guide Release 12.1
AutoCash Rule Sets
Receipts 6-3
36. How To Run A Lockbox Without Entering The Lockbox Number
Set up a transmission format where Record type Lockbox Header and Lockbox Trailer are defined and set up the
columns as per your requirement.
Now when a lockbox run is being submitted,select the above transmission format and the lockbox number field get
greyed out.
10/27/2017 Document 1075485.1
37. Lockbox Receipts created as Unapplied instead of 'On Account', as setup in the autocash rule set
Following circumstances concur:
Lockbox is setup to Match by Transaction.

Autocash Rules have been setup at the System Level, Customer level and Site level.
The Remaining Remittance amount is set to ON ACCOUNT for autocash rules.
Navigation: Setup > Receipts > AutoCash Rule Sets
For the receipts not having a corresponding invoice number, partial receipts are being created as Unapplied, instead as
On Account
Solution:
1. If a Remainder Rule Set is not entered, Receivables marks the remaining amount Unapplied.
2. Identify a Remainder Rule Set to specify how Post QuickCash applies any leftover receipt amounts created by a partial
receipt application.
3. The auto cash rule set to be used for lockbox applications needs to be set in the field Remainder Rule Set
in Profile tab
of the Standard Customer form.
Navigation: Customers >Standard
10/27/2017 Document 1075485.1
38. How can a new Date Format be set up for Lockbox transmission formats?
The date formats for Lockbox Transmission Formats are seeded and cannot be updated.
To see which are available:
Responsibility : Receivables manager

Navigation: Setup > System > Quickcodes > Receipts
Press F11
In the 'Type' field enter the following: TRANS_DATE_FORMATS
Ensure the description states: 'Lockbox Transmission Date Formats'
39. Can Adjustments be created through Lockbox?
No. We cannot Create Adjustments through Lockbox, as Lockbox is only intended to bring in the receipts (with or
without application)
You can use the Adjustments API program to create adjustments .
For more information on Adjustments API please refer to Document 808758.1, Oracle Receivables Adjustments API:
Sample Scripts
40. How to default the bill to location in Lockbox?
Defaulting is done in arlvbl.lpc.

It is done only when the require billing location flag of the lockbox is set.

Navigation: Setup > Receipts > Lockboxes
10/27/2017 Document 1075485.1
To use this feature, you must include a billing location in your transmission format, data file, and flag the Require Billing
Location should be set to Yes. This can be set at System Options and the Lockbox setup.
10/27/2017 Document 1075485.1
If the box is checked at the Lockbox level, the receipt will be validated only if the billing location is provided. The
setting at the system options level determines whether Post QuickCash can process receipts with / without billing
locations.
If you want to default location without setting the flag, the only way will be to use lockbox hook procedure.
41. How To Populate The Field "Customer Reference" Displayed In Receipt Application Window For Lockbox
Receipts
Please make sure that you populate the column CUSTOMER_REFERENCE1 in table AR_PAYMENTS_INTERFACE_ALL.
42. How Can User Apply Single Receipt To More Than 8 Invoices Using Lockbox Process
Use overflow records to record the extra lines.

User can have one line as the receipt, and optionally applied on 8 invoices, and then you can have different record types for
your overflow records.
Oracle Receivables Implementation Guide Release 12.1

page 4-122:
Overflow Sequence: (Lockbox Transmission Data window) A type of bank file record that stores additional receipt
information that could not fit on the receipt record.
Each Overflow record must have a receipt record as a parent. Typically, an Overflow record will store additional invoice
numbers and the amount of the receipt to apply to each invoice.
If there are multiple overflow records for a receipt record, each overflow record will have an overflow sequence.
Also, from Oracle Receivables Reference Guide

Part No. E13512-03
B-79
10/27/2017 Document 1075485.1
Assigning Values To Overflow Records

If your record type is an Overflow record, enter the following columns with the values described. Some of these values are
mandatory, while others are optional.
Overflow records allow you to transmit additional information about a receipt that does not fit on the receipt record, such
as batch number, item number, sequence number, invoice number, debit memo number, or debit item amounts. The most
common use for this record type is to import additional invoice numbers to which the receipt should be applied.
An overflow record can have up to eight invoice applications.
OVERFLOW_INDICATOR
Receivables uses this column to indicate overflow records for the current receipt. You determine your overflow indicator in
your transmission format. To identify the last overflow record, enter a value that is different from your overflow indicator.
For example, in the BAI transmission format, '0' indicates an overflow record. You have three overflow records for a
receipt, the first two records have '0' as the overflow indicator and the third record has '9'. Since the third record is not '0',
it is identified as the last overflow record.
You must enter a value for all overflow records.
OVERFLOW_SEQUENCE
Enter a sequential number to indicate the order of overflow records. Within each receipt, the Overflow Sequence usually
begins with 1.
43. How Lockbox handles Receipt Number using Fill Symbol and Justify setup?
Case I
For payment Number in transmission format

Justify > Right
Fill Symbol >Zero
Check Number 0007008x08
Receipt is created as 7008x08. In this case leading zeros are truncated.
Case II
For payment Number in transmission format

Justify -> Left
Fill Symbol->Blank
Check Number 00001234
Receipt is created as 00001234. In this case leading zeros are not truncated.
Explanation:
In Case I, the fill symbol is "zero" and the "Justify" is "Right". So, the zeros on the left are trimmed.
In Case II, the fill symbol is "blank" and the "Justify" is "Left". So any spaces on the right will be trimmed. Since there are no
blanks onto the right of the check number, nothing is trimmed.
44. How to Derive The Check Digit in The Transit Routing Number?
10/27/2017 Document 1075485.1
Symptoms
While executing the lockbox program it is throwing

ERROR MICR NUMBER REFERS TO MORE THAN ONE CUSTOMER.
Verified that the provided MICR number refers to only one customer.
Under these circumstances, the issue is system failed to create a bank account with the specified MICR number.
How to derive the check digit to correct the MICR number:
When entering new bank accounts, different countries can have certain rules governing the format and content of the
following related fields:
Bank Number
Branch Number
Account Number
Check Digit
The following points are applicable to all the countries:
For all fields, white spaces and hyphens ('-') are removed before checking the number.
The Bank and Branch Number might be mandatory depending upon the country-specific rules.
The Account Number is mandatory for all countries.
The Check Digit is might be mandatory depending upon the country-specific rules.
United States
Validation Rules
The fields are checked for validity by adopting the following rules:
Field Rules
Bank No validation.
Number
Branch
Number This field is labeled as 'Routing Transit Number'.
Length should be a maximum of 9 numeric characters.
If the length is less than 9, then it is converted to a 9 digit number by prefixing it with as many leading
zeroes as is necessary.
Note that on padding the number to 9 digits, the first 8 digits cannot be all zeroes.
For example, 001 and 000007 are invalid Routing Transit Numbers because on padding to 9 digits, they
become - 000000001, 000000007, and thus having 8 leading zeroes.
A check algorithm is applied on the Routing Transit Number.
Account No Validation
Number
Check No Validation
Digit
Check Algorithm for Routing Transit Number

10/27/2017 Document 1075485.1
1. The ninth digit of the Number field is used to represent the Check Digit.
2. A calculated Check Digit is computed from the remaining 8 digits using Modulus10 algorithm.
3. Multiply each digit in the Routing Transit Number by a weighting factor. The weighting factors for each digit areas given
in the following table:
Digit Factor
1st 3
2nd 7
3rd 1
4th 3
5th 7
6th 1
7th 3
8th 7
4. The digits of the Routing Transit Number are multiplied by the associated factor.
The computed sum is then calculated by summing the totals.
5. Subtract the sum from the next highest multiple of 10. The result is the calculated Check Digit. This should be the same
as the 9th digit of the Branch Number or Routing Transit Number, else the Branch Number or Routing Transit Number
is invalid.
For Example:
Digit Value Factor Result
1st 0 3 0
2nd 7 7 49
3rd 6 1 6
4th 4 3 12
5th 0 7 0
6th 1 1 1
7th 2 3 6
8th 5 7 35
Total 109
So the Check Digit = 1 (110 minus 109)
In this example, the Routing Transit Number '076401251' will pass validation.
Note: When a new MICR is uploaded, the receipt is created as unidentified and it is correct.
The receipt is manually identified after creation but the next imported receipt with the same MICR number should be able to
identify the customer and this is not happening, the second lockbox import alsocreate the new receipt as unidentified.
This can happen if the branch number is less than 9 characters. Due to padding of leading zeroes and the Lockbox will fail to
retrieve the customer record using the bank information as the branch number will be stored with leading zeroes in the IBY
tables.
10/27/2017 Document 1075485.1
In order to identify the customer in subsequent runs, one needs to provide the full branch number with leading zeroes for
system to identify the customer using the MICR number.
Other Countries
For detailed information on Country Specific Bank Account Validations please check:
Oracle Cash Management User Guide
Release 12.1
Part No. E13483-03
Country Specific Bank Account Validations F-1
45. What are the Order and Defaults used by Lockbox Autoassociate to Identify Customers?
Lockbox includes a variety of matching options.

The system cycles through these options in a predetermined order and when a matching number is found, it verifies that the
match_by type is correct and links that customer to the receipt.
If however no Match_By is found on the associated Customer Site, Customer Profile or Lockbox, the system uses a default
value of "Invoice" (aka Transaction). You must therefore specify an alternate match by at one of the levels listed above if you
wish to match using anything other than "invoice".
Customers wishing to match using more than one match by criteria or wishing not to define match by may choose to
implement the custom lockbox hook matching program. This is a stored procedure that is called during all lockbox processing.
The AR user guide documents this program on page 4-102 in a section titled "Implementing a Custom Matching Rule". Users
can code the arp_lockbox_hook stored procedure to perform the match in any way you wish. This program is passed all the
important parameters from the interface table and you can then pass back the matching customer and invoices. The code to
modify is located in $AR_TOP/admin/sql/ARRLBHKB.pls.
Enhancement Request Bug 1093523 has also been logged to request that the default be changed from INVOICE to ANY. This
enhancement request has not yet been approved by product management.
Documentation Bug 3721189 has also been logged to clarify in the AR User Guide the process used by AutoAssociate to find a
customer when no Match By option is specified.
46. How to populate Global attributes in AR_RECEIVABLES_APPLICATIONS_ALL when using Lockbox in

Brazilian Localizations?
AutoLockbox is not designed to handle Brazilian Localizations.

Brazilian Localizations has a "Bank Return" process that creates receipts from files sent to the bank.
So the system is working as intended.
47. Receipt has INVALID APPLICATIONS for all records, valid as well as invalid?
When following circumstances concur:
auto-associate is ON.
Customer information (customer number or MICR number) is not provided in the data file.
Receipt includes one or more invalid applications.
Then all application records are marked as invalid.
To identify the paying customer using auto-associate, all application numbers must be valid and for the same customer. If any
of them are invalid, or from a different customer, all applications are regarded as invalid.
48. How are miscellaneous cash identified through AutoLockbox?
10/27/2017 Document 1075485.1
Lockbox only processes invoice related receipts. You must use the application to enter miscellaneous receipts, with a type of
'Misc'.
49. How does Lockbox process the match if there are several different occurrences of the Matching Number?
The Matching Number type is setup at Lockbox setup ( Match Receipts By

field).
It may also be overwritten at the customer or customer site levels.
Lockbox will go over the possible Matching Number Types in the order mentioned above. It will look for a transaction
with the same number, where one of the following is true:
1. The Matching Number type at the Lockbox setup agrees with the type Lockbox is searching on, and there's no override
for the customer. Or:
2. The Matching Number type at the customer/customer site level agrees with the type Lockbox is matching on.
The first one found is a match.
50. When does AutoLockbox consider an invoice to be a duplicate?
Invoice numbers are only required to be unique within a batch source. A customer can have duplicate invoice numbers as long
as they belong to different batch sources; however, AutoLockbox cannot automatically apply a payment to these invoices.
If a customer has more than one invoice with the same number within a Lockbox transmission, AutoLockbox will reject the
application (i.e. the record will remain in the interface table) because it cannot determine to which invoice to apply the
payment.
In this case, the receipt will either be left as Unapplied (if the customer number or MICR number is provided) or Unidentified
(if the customer number or MICR number is not provided).
However, you can manually apply a receipt(s) to these invoices in:
The Applications window, if you have already submitted Post QuickCash.

The QuickCash window, if you have not yet submitted Post QuickCash.
51. How does On Account rule in Autocash Lockbox work?
Example: case A:
If a receipt for $100 had no valid applications found during validation step, then it will go through autocash rules. Autocash
rule set can be for example:
1. oldest first
2. on account
If only one old invoice open for $90 is found by autocash rule 1, the receipt
is applied to that invoice. Next autocash rule 2 will put the remaining $10 on account.
Result: 90 applied, 10 on account.
Example: case B:
If the receipt for $100 had a valid application to an invoice for $90, then $10 remain unapplied. Autocash rules will ignore this
receipt during postbatch, because it already is being partially applied.
Result: 90 applied, 10 unapplied.
However, it can also go through remainder amount autocash rule set and the $10 can be put on account, the same as with
case A.
52. If Customer only gives the Consolidated Billing Number as part of the autolockbox file will it apply the
receipt to all invoices associated with that CBI number?
10/27/2017 Document 1075485.1
The Consolidated Billing number is used only to identify the customer.

The Autocash rules apply for invoice payment application.
This may or may not include all invoices associated with the Consolidated Billing Number.
53. Why is Lockbox receipt is rejected with duplicate MICR number?
If a MICR number is shared with more than one customer, the receipt is rejected.
Customers that are associated, must have unique MICR numbers.
54. Can Output Be Reduced In The Lockbox Execution Report?
There is no options to print less information on this report.

You can Run Post QuickCash separate from Import and Validation, that way the report will just print the Post QuickCash
Execution Report.
55. ARXLBSUB: When Submitting Lockbox Cannot Manually Enter A GL_DATE

Navigation: Interfaces > Lockbox
To be able to enter the gl_date, set the GL Date Source to Constant
If it is set to deposit date or system date then it will use either of these dates for the gl_date and will not allow a date to be
entered

Navigation: Setup > Receipts > Lockboxes > Lockboxes
10/27/2017 Document 1075485.1
56. Is it possible to automate the creation of Claims for receipt balances that are not linked to any invoice?
Lockbox currently supports automatic claim creation, but does not support the autoamtic creation of claims unless an invoice
number is supplied. Users can manually apply unmatched balances using the quickcash form after the valiation step is run or
through the Receipt Workbench after the PostBatch is completed.
Enhancement Request Bug 3854688 has been logged to request that the functionality be expanded to allow for claims to be
automatically created for receipt balances that are not linked to any transaction.
57. Where does the value for transmission_request_id come from?
The transmission_request_id is the same value as the concurrent request request_id.

The request_id is generated from the sequence FND_CONCURRENT_REQUEST_S.
58. ARLPLB: Log File is Extremely Large and Seems to Repeat Itself.
Responsibility: System Administrator

Navigation: Profile > System
Query up the profile AR: Application GL Date Default

Select one of the following from the LOV:
Later of Receipt GL date and Invoice GL date

Later of Current date, Receipt and Invoice GL date
Save your record
58. Batch Type Can Be Changed After Lockbox Has Been Processed
10/27/2017 Document 1075485.1
Once quick cash has ended, the batch source has no relavance.
We do not post to GL by batch and we do not apply cash by batch after the initial application.
Lockbox creates a quick cash batch. However, a quickcash batch is only quickcash until it is posted. Then it automatically
becomes a manual batch.
59. Records Deleted From AR_PAYMENT_SCHEDULES_ALLAre Still Displayed In The Lockbox Transmission
History Window
The details being shown in the Lockbox Transmission History form are picked up from the view AR_TRANSMISSIONS and in
turn from the table AR_TRANSMISSIONS_ALL.
This table stores information about each Lockbox transmission. Each row includes the original transmission request ID, the
transmission date, time, count, and amount.
You use this information to review the status of your transmissions. The primary key for this table is
TRANSMISSION_REQUEST_ID.
Deleting the row corresponding to the transmission from this table, would clear the same from the Lockbox Transmission
History form. You may take a backup of the table before performing the same. After you run the delete make sure to issue a
COMMIT; statement to finalize your changes to the database.
60. What Tables Are Updated When Lockbox Finds a MICR Number?
The transit routing number will be inserted into the AP_BANK_BRANCHES table.
The bank account number will be inserted into the AP_BANK_ACCOUNTS table.
The relationship between the customer and a MICR number is realized in the AP_BANK_ACCOUNT_USES table.
In R12, with the inclusion of the IBY module, other tables might be affected, please log a SR with AP for further clarification.
61. Can a Bank File in BAI2 Format Be Defined As A Transmission Format?
Enhancement Request Bug 4951683 ORACLE LOCKBOX DOES NOT CONFORM TO BAI2 STANDARD was logged and has been
approved.
This enhancement request has been approved, but it is not currently scheduled and there is no estimated delivery date. The
Enhancement Request can be monitored via MetaLink by following these steps:
1. Select Document ID (Knowledge Base, Forum or Bug) in the Quick Find poplist
2. Enter the Bug number in the text field.
3. Click on Go.
4. The bug number and subject appear.
5. Click on the bug number in the results window.
6. Click on Bookmark.
7. Monitor periodically by clicking My Headlines then the Bookmarks button.
62. Lines Have Been Deleted From the Maintain Transmission Form (ARXLPIM )
The data can be retrieved from the file originally sent by the bank.
If this file no longer exists and there is no backup then it will not exist anywhere else on the system.
It will be necessary to ask the bank to resend the information so that it can be re-imported into lockbox.
63. How To Put Lockbox Receipts On-Account

Navigation: Set Up > AutoCash Rule Sets
1. Query the AutoCash Rule Set

2. Under the Automatic Matching Rules
3. select On-Account for the Remaining Remittance Amount field
4. Enter the Autocash Rules you want to use.
10/27/2017 Document 1075485.1
Post QuickCash uses this rule first to check for validate applications.
If no transaction could be applied the receipt amount will be put on-account.
Also the remaining portion of a receipt will be put on-account after all transactions have been applied following the Autocash
Rule assigned.
64. Can Lockbox Be Submitted From the Command Line?
Running Lockbox from the command line is not supported.

When you submit a process from the command line, there are no edits done on the values in any of the parameters before
processing.
When you submit certain processes thru the forms, the editing is done before the submission is allowed.
The General Ledger Transfer (ARGLTP), Autoinvoice (RAXTRX), Customer Interface (RACUST), Tax Interface (ARITXI),
Autoadjustments are other examples where this is not supported.
65. What is the File Name For Post Quickcash Execution Report
ARXLPLB.rdf is the report only for Lockbox validation report.

There is no .rdf file for Post QuickCash Execution Report.
Post QuickCash execution report is generated by Pro-C code that is part of the executable ARCABP.
66. Importing a receipt via Lockbox, Apply Date on the receipt application is defaulting to Receipt Date and not
System date like a manual receipt application via the form.
This is working as intended.
Current functionality of the Product allows Lockbox to import the receipt and apply date will be same as receipt date and not
system date. Reason for this behavior:
"The meaning of apply date as it has been designed is the date that a receipt provided by a customer was applied to the
invoice that the customer intended to pay. This date is used when determining average days late, early pay discounts and
collection effectiveness. The apply date should be as close to the receipt date as possible. This is particularly true for lockbox
where the bank has received payment and deposited it into a remittance bank account. The customer has paid invoices. The
receipt customer's account should not be effected by the processing policies of the receiving company. The Manual Receipts
form is not intended to enter receipts in manually. Its primary intent is to provide users the ability to resolve unapplied cash or
movement of applications due to credit memos, adjustments etc."
67. Lockbox import does not import data according to the column break-down specified in the control file.
System uses load-balancing servers, but the control file has not been synched in both (all) the load balancing servers.
Resynch the load balancing servers.
68. Does the AR lockbox process allow tab delimited control files?
When creating a new transmission format, can the control file utilize tab delimited formats as is the case with normal
SQL*Loader files?
At this time, the lockbox control file can only be a fixed length file formats.
The system does not allow for Tab Delimited (or any other delimited file formats) when loading data through the lockbox
process.
69. How to use customer_reference and customer_reason in AutoLockbox
The columns customer_reference1..8 and customer_reason1..8 are reserved for Claims/Deductions only. You CANNOT use this
field for your own use. This field is used if you are creating a claim/deduction for the receipt.
This is also true when you use the online screens.
10/27/2017 Document 1075485.1
If you need to store some information for the receipt, consider using the Receipt Information descriptive flexfield.
In Lockbox setup change your transmission format and your control file to populated Attribute1....10.
70. Evaluate for Claims Eligibility Field is Missing from Lockbox Form
In order to see the Evaluate for Claims Eligibility

field you need to haveTrade Management installed.
If you have Trade Management installed but field Evaluate for Claims Eligibility
is missing, run the following SQL to check if TM
is properly setup:
SELECT cm_trx_type_id, billback_trx_type_id

FROM ozf_sys_parameters;
If either or both of the fields above are returned as null, then set them up.
Responsibility: Oracle Marketing Online

Navigation: Administration tab > Marketing > Claims > System Parameters.
71. Can a file have multiple batches for the same Lockbox number, origination, and account?
There is no benchmark for the number receipt batches in one Lockbox transmission file.
Yes the standard functionality allows you to import multiple receipt batches (with different batch names) in one Lockbox
transmission file for the same Lockbox number, origination and bank account combination.
72. Does The Receipt To Receipt Application Functionality Work With Lockbox?
Receipt to receipt netting does not work with Lockbox, however you can do the following:
Manually apply a receipt imported via lockbox to another receipt.

Utilize the post quickcash utility in the form to apply lockbox receipts.
You cannot fully automate the lockbox receipt to receipt matching and application process.
73. Why Lockbox Creates And Apply Receipts Even When There is ERROR Batch amount does not equal sum of
receipt amounts
This was discussed with the Product management Lockbox will create receipts and apply them if the receipt and application
data is valid.
Batch amount and transmission amount are control validations for users to verify that if any receipt data is missing from the
data file.
74. How AutoLockbox Applies Receipts
1. If Lockbox is able to identify the customer for a receipt and the transaction number is provided , Lockbox applies the
receipt to this transaction.
2. If the transaction number is not provided and Autoassociate is set to Yes, Post QuickCash uses the matching rules
defined for the customer site, customer or Lockbox to apply the receipt. The setting of Match Receipts By Option tells
what type of matching number is passed in the transmission.
If Matching Rules fail, Post QuickCash applies the receipt using the AutoCash rules set .
If AutoCash rules also fail, Lockbox assigns the receipt a status of Unapplied.
3. If the transaction number is not provided and Autoassociate is set to No, Post QuickCash assigns the receipt a status of
Unapplied.
75. Will Lockbox apply to all transactions belonging to a SO/PO?
No, Lockbox applies to the invoice with max(trx_number) if any amount remains in receipt it will apply based on auto cash
rule. The lockbox validation applied the receipt to the invoice with maximum trx_number if two or more invoices with the same
10/27/2017 Document 1075485.1
SO# or PO# for the same customer exist. The remaining amount of the receipt, if any, will be applied by using the auto cash
rule.
76. Why does Lockbox allow applying a receipt to same transaction twice?
This is intended functionality.

Lockbox and Quickcash form was changed to allow multiple applications to the same invoice to support managing deductions
and integrating Trade management with AR.
However, if you are using the Receipt API or Receipt form, you will not be allowed to apply a receipt to the same transaction
twice. If you attempt to do so, you will get the error:
"You have paid the same invoice twice. Please correct. "
Feedback
To provide feedback on this note, click on the Rate this document link.
Community Discussions
Still have questions? Use the live

My Oracle Support Receivables Community window below, to search for similar discussions or
start a new discussion on this subject.
10/27/2017 Document 1075485.1
Receivables - EBS (MOSC)

in Oracle E-Business Suite (MOSC)
Overview Content People Subspaces
ANNOUNCEMENT: ERs to Receivables My Oracle Support Community Ideas! Your Ideas Count!
YOUR COMMUNITIES ASK RECEIVABLES - EBS (MOSC)
Spaces Type your question
Find Space ASK IT
Type to begin your search
Oracle Receivables White Papers
Most Popular Knowledge Documents
Most Popular Troubleshooting Documents
Related Information Centers
Welcome to the Oracle Receivables

Community!
The Oracle Receivables (AR) Community provides broad access to
REFERENCES
NOTE:808758.1 - Oracle Receivables Adjustments API: Overview, Sample Scripts, Known Issues
BUG:1093523 - LOCKBOX MATCHING#: PROVIDE ANOTHER CHOICE TO MATCH THE FIRST 'HIT' IT FINDS
BUG:2755435 - ADD LOCKBOX CONCURRENT PROGRAM -ABILITY TO SCHEDULE
BUG:3721189 - CLARIFY MATCH BY DEFAULTS USED TO IDENTIFY CUSTOMERS AND TRANSACTIONS
NOTE:1362278.1 - Information Center: Overview of the Receipts Workbench in Oracle Receivables (AR) 11.5 and later
BUG:3854688 - ALLOW FOR AUTOMATIC CLAIM CREATION FOR UNAPPLIED RECEIPT BALANCES VIA LOCKBOX
BUG:673426 - LOCKBOX VALIDATION SHOULD DETECT WHEN AN ENTIRE BATCH IS IMPORTED 2ND TIME
BUG:9288902 - REW : SETUP OPTION NOT TO CALICULATE UNEARNED DISC FOR APPLICATIONS VIA LOCKBOX
NOTE:1075485.1 - Oracle Receivables Lockbox: Frequently Asked Questions (FAQ)
Didn't find what you are looking for?

Oracle Receivables Lockbox: Frequently Asked Questions (FAQ) (Doc ID 1075485.1)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oracle Receivables Lockbox: Frequently Asked Questions (FAQ) (Doc ID 1075485.1)

Caricato da

Copyright:

Formati disponibili

10/27/2017 Document 1075485.

Oracle Receivables Lockbox: Frequently Asked Questions (FAQ) (Doc ID 1075485.1)

54. Can Output Be Reduced In The Lockbox Execution Report?

Oracle Receivables - Version 11.5.10.0 and later

QUESTIONS AND ANSWERS

2. What table needs to be populated is using Lockbox via a custom program?

Data need to be populated in AR_PAYMENTS_INTERFACE_ALL.

4. Where can I review receipts that failed during validation?

Responsibility: Receivables Manager

Navigation: Receipts > Lockbox > Transmission History

Navigation: Receipts > Lockbox > Maintain Transmission Data

5. What are the various transmission status possible?

A Lockbox transmission can have one of the following statuses:

This is intended behavior:

7. Can I apply a QuickCash Receipt to Multiple Transactions?

1. Navigate to the Receipt Batches window

8. Can I apply a receipt to another customer's transaction?

9. Can I apply a Quickcash receipt against open receipts?

10. When is the Autocash Rule used?

11. What are the various Autocash rule options?

Following are the Autocash rules you can use:

Match Payment with Invoice

12. How are the discounts handled in post quick cash?

1. System options Allow Unearned Discounts and Discount on Partial Payment.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Payment Terms.

3. Customer must be assigned a profile set to Allow Discounts:

Navigation: Customers > Profile Classes

This patch will introduce a new checkbox A pply Unearned Discount in :

How are discounts calculated in lockbox

13. Where is the data stored after validation?

Data gets imported to interim tables after successful validation.

Archive/Purge programs can be executed to purge the processed data.

The various stages in lockbox are as below:

21. How are customers identified by Lockbox?

Please monitor this enhancement request via My Oracle Support

Reverse every receipt in the batch one by one.

Responsibility: Receivables Manager

Query the receipt to reverse.

Responsibility: Receivables Manager

Query Batch Source=Lockbox%

The state of Post QuickCash affects the batch type

Receipt Information context sensitive descriptive flexfield data is stored in AR_CASH_RECEIPTS_ALL in

Responsibility: Receivables Manager

bank_num = Transit Routing Number

Thus, looking at the header bank record:

This is intended functionality.

28. Is it Possible To Schedule A Lockbox Processing Request?

29. How to Setup Lockbox To Create Claims for Trade Management

Create a Transmission Format with Customer Reference and Customer Reason.

Setup the Claim Investigation GL Account on Receipt Class/Receipt Method

Define a receivables activity of type Claim Investigation for each combination of

According to Oracle Receivables User Guide R12 this is not possible

As an alternative to AutoCash, one might consider implementing a Custom Matching Rule.

31. Can lockbox apply receipts to an inactive customer record?

32. How to Purge Lockbox Transmission History From AR_TRANSMISSIONS_ALL

There is no program to delete this data.

Is it mandatory to use one of these 3 scripts?

Can these scripts be modified?

1. Include the MICR or customer number in the source datafile

This is expected functionality.

For more information see

36. How To Run A Lockbox Without Entering The Lockbox Number