Customer Entry Lockbox Import Report ranges and options

Ranges

There are no ranges for this report.

Options

Lockbox File Directory

Leave this field blank.

Lockbox File Name

Leave the default value of lbx.in.

This option is not used to receive lockbox payments through BODs, but a value is required to run the report.

Post/Update Imported Transactions?

Select Yes to immediately update and post transactions that do not have errors. The next three options also affect processing.

Note: Select Yes to fully utilize inbound EDI 820 functionality. If you select No, you must update the transactions manually.
If Yes, Post Only Batches Ready?

If the Post/Update Imported Transactions? option is Yes, select Yes to only post the transaction if the check is ready to post.

Updates are made for only those checks that can be fully applied within the write-off limits that are defined in SA Administrator Options-Customers-Cash Receipts. If a transaction is not posted, it is flagged with an error in ETCC.

If No, Force Batches Un-Suspended?

If the Post/Update Imported Transactions? option is No, select Yes for this option to update all transactions to the General Ledger, including those payments that are not within the write-off limits.

Select No to update only those transactions that are within the write-off limits. If a transaction is not updated, it is flagged with an error in ETCC.

If Yes, Bank # to Post Imported Trans

If the Post/Update Imported Transactions? option is Yes, specify a valid bank number. This bank number is used to determine the GL account number to post check transactions against.

Dummy Customer for Unmatched Checks

Specify the dummy customer to post unmatched checks against.

Split Transactions (C)lear or (S)uspend

This option is used if these conditions are met:

  • Invoice transactions are included with a check transaction.
  • A check from one customer applies to other customer's scheduled payments

Specify C to match based on invoice number, instead of customer number.

Specify S to suspend any transactions where the customer number associated with the check cannot be matched to the invoice number.

Do Write-Offs?

Select Yes to apply the write-off limit to payments that do not fully pay an invoice. If the check transaction falls within the write-off limit, the balance remaining is written off. If the difference between the check amount and the invoice is higher than the write-off limit, it is not written off, unless you select Yes for the If Yes, Partial Pay if Outside Limit? option.

Select No to report these check transactions as exceptions without performing any write-offs.

If Yes, Partial Pay if Outside Limit?

If Yes is selected for the Do Write-Offs? option, select Yes to apply check transactions against invoice records regardless of the write-off limit. If a balance is due after matching check transactions to invoices, a new scheduled payment for an underpayment is created. If an overpayment was made, an unapplied cash transaction is created for the balance on that invoice.

Select No to create an unapplied cash transaction for check transactions that do not match the amount of the invoice. Unapplied cash transactions are suspended and require editing before processing if these one of these conditions are met:

  • No is selected for Update/Post Imported Transactions.
  • Yes is selected for Update/Post Imported Transactions and Post Only Batches Ready.
  • Yes is selected for Update/Post Imported Transactions, and No is selected for Post Only Batches Ready and Force Batch Un-Suspended.

Unapplied check transactions are not suspended if these conditions are met:

  • Yes is selected for Update/Post Imported Transactions.
  • No is selected for Post Only Batches Ready.
  • Yes is selected for Force Batch Un-Suspended.
Create ARSL Records?

Select Yes to create Customer Lockbox Setup records if these conditions are met:

  • The customer does not have a record.
  • A customer number is included on the check transaction.

The Customer Lockbox Setup records are created in the logged-in company number. The bank routing number and checking account number found on the check transaction record are used on the record.

Posting Date

Specify the date to assign to each transaction.

Leave the default value of **/**/** to use the current date. If updating a previous period, use the current date to keep an audit trail of the posting sequence. A posting date outside of the posting period causes balancing issues when you run the Customer Trial Balance Report or the Customer Balancing Audit Report.

Specify a number between -1 and -7 in the day segment to go back up to 7 days. For example, if you specify **/-7/**, the current date less 7 days is used for the date.

If you receive EDI 820 documents through Process RemittanceAdvice BODs, the posting date from a BOD overrides the value on the stored report.

Posting Period

Specify the calendar period to update.

Leave the default value of **** to use the current date. If you are on a calendar year or fiscal year, specify the calendar month. Specify the fiscal period if you are on a 13-period fiscal year.

To go back one period, specify -1 in this field. If you specify -1**, the period before the current period of the current year is used. For example, if the current period is 0820, 0720 is used for the report.

If you receive EDI 820 documents through Process RemittanceAdvice BODs, the posting period from a BOD overrides the value on the stored report.