SAP Lockbox vs. Electronic Bank Statement | ERP Corp
SAP Controlling Conference attendees participating in a presentation

Search Posts

By Lennart Ullmann and Claus Wild

An SAP lockbox file can use invoice-level remittance details to clear customer open items for check payments. An electronic bank statement (EBS) records bank account activity across multiple transaction types. Here’s how the two files work together and which accounts each step affects.

How the Lockbox and Bank Statement Files Differ

A bank lockbox service collects customer payments and sends the company a file with payment and remittance details. When the file includes invoice numbers and the amounts applied to them, SAP can use those details to match and clear customer open items in Accounts Receivable. In the classic SAP ERP process described here, lockbox is typically used for check payments.

An electronic bank statement reports activity on the bank account, including transactions such as deposits, transfers, and charges. How much remittance detail it provides depends on the bank and file format. A lockbox deposit may appear as one amount on the statement even when the lockbox file contains multiple checks and invoice references.

How the Two Files Post When Used Together

Table 1 shows the classic SAP ERP posting example from the original excerpt. The account labels describe their roles. The accounts and posting behavior in your system depend on your configuration.

Table 1. Example debit and credit entries for a lockbox deposit
Processing StepDebitCredit
Lockbox bank posting Bank clearing account for Accounts Receivable Incoming checks clearing account
Lockbox customer posting Incoming checks clearing account Customer account. Clear the matched invoices.
Electronic bank statement posting Main bank account Bank clearing account for Accounts Receivable. Clear the corresponding lockbox deposit.

In this example, the lockbox clears customer invoices and the bank statement clears the deposit from the bank clearing account. If you use both files, review the posting rules with a sample deposit to confirm that each feed handles its part of the process and that customer payments are posted only once.

SAP S/4HANA Context

The example comes from SAP ERP. For an SAP S/4HANA implementation, check the lockbox import and bank statement processing documentation for your edition and release before applying the example.

Glossary

Bank Clearing Account

An interim G/L account that holds postings until they can be matched and cleared. In the example above, the bank statement posting clears the corresponding lockbox deposit.

Cash Application

Matching incoming customer payments to the invoices or other receivables they pay.

Electronic Bank Statement (EBS)

A file from the bank that reports account activity such as deposits, transfers, and charges. SAP uses the statement data to post or clear items according to the configured rules.

Lockbox

A bank service that collects customer payments, typically checks in the classic U.S. process, and sends the company a file with payment and remittance details.

Open Item Clearing

Matching offsetting entries so they are recorded as cleared in SAP. For example, a fully matched payment clears the corresponding customer invoice.

Posting Rule

Configuration that tells SAP how to post a bank statement item, including which accounts to debit and credit and whether to attempt clearing.

Remittance Information

Details that identify what a payment is for, such as invoice numbers and the amount applied to each invoice.

Reference Materials

Adapted from Electronic Bank Statement and Lockbox in SAP ERP by Lennart Ullmann and Claus Wild.

Find Out Why Your SAP Lockbox Payment Didn’t Clear

Start with one payment that left a customer invoice open or a deposit in a clearing account. ERP Corp can help you check the invoice reference, the lockbox posting, and the bank statement clearing rule to pinpoint where the payment stopped clearing.

Get Help with SAP Lockbox Clearing