Details
SAP Lock Box
A company can create ‘lockbox’ accounts at a bank that are used as payment collection accounts for customer receivables. The company informs its customers that all payments should be submitted to one of its established bank lockbox accounts at a designated remittance address. A lockbox account is usually a designated post office box which has the company name but the customer payments are actually received by the bank.
SAP lockbox utilization results in two primary business benefits: funds collection and remittance information delivery. The major benefits are that the company is able to recognize the funds more quickly, and the customer’s check is cashed in a more timely manner. The bank collects the payments along with the customers’ remittance information which indicates the open items the customer is paying. Data entry clerks at the bank manually enter the information into an electronic file for transmission to the company in groups of checks called batches.
These electronic files are typically transferred nightly to the company which owns the lockbox. The files can be in one of two standard banking industry formats: BAI or BAI2. They can also be transmitted via EDI using the ANSI X.12 823 for lockbox remittances. A combination of the two is not uncommon where a BAI format is delivered within an EDI message.
Customer identification is the primary task of the initial (SAP) data processing of each lockbox payment. Finding the corresponding document clearing information is the second task. Lockbox programs RFEBLB00 for BAI and BAI2 formats and RFEBLB30 for EDI format attempt to identify the customer first by MICR number (ABA/bank account number combination) and then by invoice number. It is strongly recommended that companies maintain the bank details on their customer master records. The MICR numbers must be unique across banks configured within SAP. Additionally, the MICR and customer account number also need to uniquely identify a single customer within the system. If a customer is identified by the document number but the bank details do not correspond to the MICR number, they can be added via the optional batch input session. This allows the SAP system to ‘learn’ customer bank accounts via repeated use of the lockbox service. Processing statistics in future lockbox remittances will greatly improve with repeated use of this option.
This document explain about step by step configuration and processes for SAP Lock Box functionality.
Additional Information
| Doc Code | SEBK100190 |
|---|---|
| Doc Title | SAP Lock Box Configuration Documents |
| Author | SAP E Books |
| Document For | SAP Consultant |
| Subject | SAP Concept and Configuration |
| Language | English |
| File Details | 84 Pages / 1 File |
| File Format | PDF / ZIP |
| Size (Approx) | 870 KB |
| Sap Version | Up to ECC 6.0 |
| Doc Version | V 1.0 / 10th Feb 2010 |
| Download as > | Add to cart > Check out > Payment > Download |
You may also be interested in the following product(s)
SAP MM Material Management Complete DocumentsRegular Price: $375.00 Special Price: $335.00 |
SAP IS Utility Complete Project DocumentsRegular Price: $365.00 Special Price: $320.00 |
Complete set of SAP CO DocumentsRegular Price: $477.00 Special Price: $427.00 |
SAP SD Sales and Distribution Complete DocumentsRegular Price: $315.00 Special Price: $280.00 |
SAP Funds Management BCS Complete Implementation DocumentsRegular Price: $162.00 Special Price: $145.00 |





