Lockbox batch files

A batch file is created for each lockbox by the Customer Entry Lockbox Import Report. To ensure that check payments are posted on the correct day, each batch file is created and associated with a specific date. The batch file contains different segments that are constructed from the data transmitted from the bank, and data built internally during the import.

Note: Batch files are created by the Customer Entry Lockbox Import Report when you run it in update mode. They are deleted as soon as the update process is completed.

Unless you are processing an EDI 820in transmission through the Customer Entry Lockbox Import Report, multiple transmissions can be processed in the same lockbox file. This might occur if you have set up a different lockbox for each location, or division, or if you receive eBill credit card or ACH payments throughout the day. A separate batch file and journal is created for each lockbox transmission. A single LBX.IN file is created for each system company.

This table shows the layout of a batch file:


Customer (AR) Lockbox batch file
Transmission Header (ARBCT): Created from Type 1 records Lockbox Header: Created from Type 2 records
Batch Header Record (ARBCB) - Created from Type 3 records Check Record (ARBCH) - Created from Type 4 records Line Detail Records (ARBCL) - Created from Type 5 records
Write-Off Records (ARBCLW) - Created during batch maintenance

If the imported transactions are not posted and updated by the Customer Entry Lockbox Import Report, the full batch file is created, including header and line detail records.

You can edit data in the ARBCH and ARBCL records before posting to AR and GL. You edit the data by selecting the specific customer or check record in Customer Lock Box Entry.