Lockbox in AR

AutoLockbox (or Lockbox) is a service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. A lockbox operation can process millions of transactions a month. AutoLockbox eliminates manual data entry by automatically processing receipts that are sent directly to the bank. 

AutoLockbox is a three step process: 

1. Submit Import: During this step, Lockbox reads and formats the data from your bank file into AutoLockbox tables using an SQL *Loader script.

2. Submit Validation: The validation program checks data in the AutoLockbox tables for compatibility with Receivables. Once validated, the data is transferred into QuickCash tables. At this point, we can optionally query the receipts in the QuickCash window and change how they will be applied before submitting the final step, Post QuickCash. 

3. Submit Post QuickCash: This step applies the receipts and updates your customer's balances. 

These steps can be submitted individually or at the same time from the submit Lockbox Processing window. After we run Post QuickCash, Receivables treats the receipts like any other receipts; 

Lockbox Process Flow

Lockbox Interface Table:

When you run the Import step of AutoLockbox, Receivables stores receipt data from the bank file in the Lockbox Interface table AR_PAYMENTS_INTERFACE. 

Read more »

Oracle Autoinvoice Interface Tables

AR Invoice Interface Tables

• RA_INTERFACE_LINES_ALL

- This table stores transaction header and line information.

- AutoInvoice uses Transaction Flexfields to uniquely identify each transaction that we import  into Receivables.

- AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices

• RA_INTERFACE_DISTRIBUTIONS_ALL

-  If we do not use AutoAccounting, we must enter accounting distributions for the transactions.

- If the accounting distributions are for transactions that use accounting rules, we must enter the percentages, but not the amounts.

- If the accounting distributions are for transactions that do not use accounting rules, we can enter either the percentages or amounts, depending on the value we entered for the batch source.

- Distributions in this table are linked to the appropriate transaction lines in the ra_interface_lines via the transaction flexfield. Though the distribution for 'REC' account class is at the invoice level, it may be linked to any transaction line of the invoice in ra_interface_lines. AutoInvoice will then correctly transfer all distributions to RA_CUST_TRX_LINE_GL_DIST_ALL.

• RA_INTERFACE_ERRORS_ALL

- This table stores information about interface lines that failed validation and were not imported into Receivables tables.

- Receivables uses the information in this table to generate the AutoInvoice Validation Report - - AutoInvoice identifies all errors for each transaction line, thus reducing multiple validation and correction cycles. When we resubmit AutoInvoice, the program deletes the errors for each line selected for processing. When all of the records have been successfully processed, AutoInvoice purges any remaining data in this table.

- Use the Interface Exceptions window to view all of the errors in

 RA_INTERFACE_ERRORS_ALL.

• RA_INTERFACE_SALESCREDITS_ALL

- This table stores sales credit information for the transactions.

- This table must be populated if the AutoAccounting is set up to derive segment values based on the salesrep. If AutoAccounting does not depend on salesrep, then the value we enter in the Required Salesrep field of the System Options window and Allow Sales Credits field in the Transaction Sources window will determine whether we must enter sales credit information.

Read more »