What is lockbox processing, and when does it pay off?
Lockbox processing is a bank or provider service that collects customer payments at a controlled P.O. box, deposits the checks and sends your team the remittance data. It moves paper out of your office and gets cash into the bank sooner. Your ERP still has to apply that cash, and that is where most of the delay and error sits.
A payment collection service where customers mail checks and remittance advice to a P.O. box controlled by a bank or processor. The processor opens the mail, scans the items, captures the data, deposits the funds and delivers a remittance file for cash application. Related names are lockbox payment processing and lockbox check processing.
per Federal Reserve, Regulation CC and Check 21Paper checks still arrive at many distribution, manufacturing and 3PL businesses. Each one needs to be opened, matched to an invoice and deposited.
A lockbox moves that work to a facility built for it. The P.O. box sits at the bank, so mail never touches your office.
Customers keep paying the way they always have. You change where the envelope goes, not how the customer behaves.
The cash lands in your account faster because the bank deposits on the day it opens the mail. Your own team no longer waits for the courier, the mailroom and the branch run.
Governments run lockboxes too. The IRS sets out how its lockbox banks must handle paper remittances in Internal Revenue Manual 3.0.230. It is a useful public example of strict handling rules for opening, balancing and depositing mail.
Six steps take a payment from the customer's mailbox to a posted receipt in your ERP.
You print the lockbox address on invoices and statements. Only the bank has the key, so nobody on your side handles the check.
Staff open the mail in a controlled room. They scan the check front and back and the remittance stub or letter.
Software reads the amount, check number, payer and invoice numbers. Items it can't read go to a person for keying.
Check images can be deposited electronically as substitute checks or image exchange items under the Check 21 framework. Funds are credited the same day or the next.
The file is usually BAI2 or a bank-specific CSV. It carries one line per check with the invoice references the OCR found.
Someone, or an approved agent, matches each line to open invoices, posts the receipt and clears exceptions. This step decides your real DSO.
Banks usually sell three paper lockbox types, split by volume and by how much remittance data each item carries.
| Type | Typical payer and volume | What the processor does | Best fit |
|---|---|---|---|
| Wholesale | Business customers, fewer items, large dollar value, invoice-level remittance | Captures invoice numbers and amounts, handles exceptions by hand | Distributors, manufacturers, 3PLs, professional services |
| Retail | Consumers, thousands of small items, standard coupon | Reads the scan line, deposits, does little exception handling | Utilities, subscriptions, insurers |
| Wholetail | Mixed. A high volume of business payments with some retail features | Scan-line automation for standard items, manual capture for the rest | Companies with a large base of repeat payers and some one-off remitters |
Most readers of this page run a wholesale lockbox. The detail that matters is how much invoice data reaches the file.
Four ways to handle incoming payments, compared on the points controllers ask about first.
| Option | Who opens the mail | Strength | Watch for |
|---|---|---|---|
| Bank lockbox | Your bank | Deposit and the lockbox sit in one place, fast credit | Fixed file formats, less flexible exception handling |
| Outsourced provider | A specialist processor | Better data capture, custom reports, more remittance detail | Another party between you and the cash, so check deposit timing |
| In-house | Your own team | Full control, no per-item fee | Mail delay, staff time, check theft risk, branch deposit trips |
| Electronic lockbox (e-lockbox) | No one. Customers pay through the bank bill-pay or an online portal | No paper, structured remittance, fastest data | Only works for customers willing to switch |
Many companies run two at once: a wholesale lockbox for legacy payers and an electronic route for everyone else.
These numbers are illustrative. A distributor's wholesale lockbox receives six checks totalling $48,750 in one day. They cover 11 open invoices.
Four checks, together $37,850, pay their invoices exactly. One check for $7,800 pays invoice INV-2041, which was $9,000. The customer shorted $1,200 and wrote deduction code D-14 (damaged freight) on the stub.
The sixth check, $3,100, has no remittance and no invoice reference. Nobody can tell what it pays.
Float is the easy number. If the lockbox deposits two days sooner than the old mail-and-branch route, $48,750 earns about $13.36 more: $48,750 × 5% × 2 ÷ 365. That's small per batch, but across hundreds of batches the float saving and the lower handling cost add up.
The harder numbers sit in cash application. The $1,200 needs a deduction claim, and the $3,100 needs an owner by the end of the day.
Using the batch above. Account names vary by chart of accounts, so treat these as a pattern.
| Event | Debit | Credit | Amount |
|---|---|---|---|
| Lockbox deposit and cash application | Bank (or lockbox clearing) | Accounts receivable (applied) | $45,650 |
| Unreferenced check held | Bank (or lockbox clearing) | Unapplied cash | $3,100 |
| Short pay on INV-2041 (D-14) | Deductions, short-pay expense or deduction claim | Accounts receivable | $1,200 |
| Unapplied check identified and applied | Unapplied cash | Accounts receivable | $3,100 |
The first two lines together equal the $48,750 deposit. If the customer owes a discount, the $1,200 goes to Cash Discounts instead. If the claim is valid, it goes to short-pay expense.
Business Central. You can import a bank statement or lockbox file into the Payment Reconciliation Journal. The journal suggests matches to customer ledger entries and applies them. The Cash Receipt Journal covers manual entry, and Bank Account Reconciliation proves the deposit. Auto-match works well for exact amounts and clear references. It struggles with one check paying many invoices, short pays and missing remittance. A BAI2 file or a bank CSV needs an import format defined for it, and some banks need a custom data exchange definition. See Business Central documentation on Microsoft Learn.
Dynamics GP. Cash Receipts Entry and Receivables batches post the receipt and apply it to documents. We don't assume GP reads a lockbox file out of the box. Most teams use an add-on or a custom import, so confirm for your version before planning. See Dynamics GP documentation on Microsoft Learn.
NetSuite. Customer Payment applies cash to invoices, Customer Deposit records money before an invoice exists, and Deposit and Payment Application link the two. Importing a lockbox or bank file normally needs a SuiteApp or a CSV import map.
Where each one stops. None of them reads a messy remittance letter or decides what a $1,200 short pay means. That judgement still sits with a person, which is why we pair them with a cash application process that has an approval step. For platform specifics, see our Business Central and Dynamics GP pages.
Five exception types cause most of the manual work after a lockbox deposit.
Per-item fees depend on volume, the lockbox type and how much data capture you buy. Ask your bank for a fee schedule and compare the full cost, including exception handling, image archive and reporting.
The AFP Payments Cost Benchmarking Survey is the standard reference for what organisations pay to receive and process checks. Use its published ranges as a benchmark, not a quote.
Three metrics tell you if the lockbox works. Days from mail date to credit, which should fall. Percent of items auto-applied, which shows data quality. Unapplied cash older than 30 days, which shows the exception backlog.
DSO moves because cash is credited sooner and applied the same day. The float days you gain are real, but the larger DSO gain usually comes from faster application and fewer open exceptions. Read about remittance advice to see what data a good file should carry.
Check volume has fallen for years. The Federal Reserve Payments Study tracks that decline, while NACHA publishes ACH growth.
Customers are moving to ACH, RTP, card and bank bill-pay. Those routes give you structured data, and a few reach your account faster than a check.
But paper hasn't vanished in distribution, construction and facility services. Large payers still cut checks, and some small suppliers get paid by them.
Electronic lockbox bundles those digital payments into the same file format as the paper lockbox. Your ERP gets one feed, one set of rules and one exception queue. For ACH remittance detail, see EDI 820 payment remittance.
Skip it if you receive few checks. A few checks a week cost less to deposit by mobile capture than to run through a bank lockbox.
Skip it if most customers already pay by ACH or card. Then your problem is remittance matching, not mail.
Skip it if one or two key customers pay by wire. Those payments need a good bank feed, not a P.O. box.
Consider it when checks arrive in volume, staff spend hours opening mail, or deposits wait on a courier. That's when the lockbox earns its fee.
The lockbox gets the money into the bank. The agent does the matching work that follows, inside your ERP, and a person approves each posting.
The agent loads the BAI2 or CSV file and reads check images and remittance letters that OCR left unclear.
It matches each payment to open invoices, with a stated confidence and reason. It flags short pays with the deduction code and suggested claim.
Your cash application analyst checks the proposals and approves, changes or rejects each one. Nothing posts without that decision.
After approval, the agent creates the receipt in Business Central or your ERP and logs who approved what. See Human-in-the-Loop Agents.
We map your file format, matching rules and approval limits, and tune them as exceptions repeat. Start with Cash Application.
A bank or provider receives your customers' checks at a P.O. box, deposits them and sends you the payment data. Your team skips the mailroom and the bank run.
A normal P.O. box is collected by your staff. A lockbox is controlled by the bank or processor, who opens the mail, deposits the checks and sends you the data.
Many lockboxes deposit the day the mail is opened. Timing depends on the bank's cut-off times and your agreement, so ask for the stated deposit and availability schedule.
Usually BAI2 or a bank-specific CSV, plus check images. Your ERP may need an import format or add-on to read it, which is common with GP and NetSuite.
Not by itself. It captures the remittance data. Applying the cash to invoices and clearing exceptions happens in your ERP or by an agent working under approval.
Often not. If you get few checks, mobile deposit or a bank feed costs less. A lockbox pays off when volume is high and staff time on mail is large.
A paper lockbox handles mailed checks. An electronic lockbox collects online and bill-pay payments into the same file, so you work one queue.
Tell us your ERP, your bank's file format and your monthly check volume. We'll show you where cash application slows down and what an approval-first agent would change.
Facts on this page checked on 16 November 2026.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.