Checks haven’t gone away. Despite the growth of ACH, virtual cards, and digital payment networks, a significant share of B2B payments still arrives by check—particularly in industries like healthcare, construction, and the public sector. For finance teams handling that volume, lockbox payments are a daily reality. And how well you manage lockbox processing directly affects your cash flow, your DSO, and how much time your AR team spends on work that shouldn’t require human hands.
This post explains what a lockbox payment is, how lockbox banking works, where the processing complexity comes from, and what modern automation actually does about it.
What is a lockbox payment?
A lockbox payment is a check payment that customers send to a bank-managed post office box rather than directly to your company. The bank collects the mail, scans the checks, deposits the funds into your account, and transmits the payment data to your AR system.
The term “lockbox” refers to the secure PO box the bank controls. Your customers are given this address on their invoices instead of your company’s mailing address. From that point forward, the bank handles the physical side of check collection—you receive the data.
Lockbox banking has been part of corporate treasury management since the 1940s, when companies first realized that cutting days off the mail and deposit cycle had a direct impact on available cash. The mechanics have changed significantly since then, but the underlying idea is the same: get funds into your account faster by outsourcing the collection step to your bank.
How does lockbox banking work?
Lockbox banking follows a defined sequence. Knowing where each step sits helps you understand where manual effort accumulates and where automation creates leverage.
Mail collection. The bank collects checks from the PO box multiple times a day, including weekends and public holidays in many cases. This alone removes the delay of checks sitting unprocessed in an internal mailroom.
Scanning and imaging. Each envelope is opened, the check and any accompanying payment documentation are separated, and both are digitally scanned. The bank creates a record of what arrived, when, and from whom.
Deposit. The bank deposits the checks into your account, typically on the same business day. This is the core cash flow benefit of lockbox banking—funds clear faster than they would through internal processing.
Data transmission. The bank sends you a file containing check images, payment amounts, payer information, and whatever structured data it was able to capture from the payment documents. This file is the starting point for your AR team’s work.
That file is also where the complexity begins. The bank can tell you a payment arrived. It can’t tell you how to apply it.
What are the two types of lockbox payments?
Not all lockbox payments are the same, and the distinction matters when you’re evaluating automation.
Retail lockbox is designed for high volumes of standardized consumer payments. Utility bills, insurance premiums, and subscription payments are typical examples. The checks are predictable in format, the amounts are relatively small, and the payment documentation is usually a standard tear-off stub. Retail lockbox processing is well-suited to high-speed scanning and OCR because the inputs are consistent.
Wholesale lockbox handles B2B payments. These are typically higher-value, lower-volume transactions accompanied by far less predictable documentation. A single wholesale lockbox payment might cover multiple invoices across different purchase orders, with backup materials ranging from a clean EDI file to a handwritten note or nothing at all. This variability is what makes wholesale lockbox processing genuinely difficult to automate with off-the-shelf bank tools alone.
Most enterprise AR teams deal primarily with wholesale lockbox payments, which is why bank-provided data capture is rarely sufficient on its own.
What makes lockbox processing complex?
Lockbox processing is the work that happens after the bank file arrives: identifying which open invoices a payment covers, handling discrepancies, and posting the cash in your ERP. In simple cases, it takes minutes. In complex B2B environments, it can absorb hours of AR team time every day.
Several factors drive that complexity.
Missing or incomplete payment documentation. Banks capture what’s in the envelope. If a customer sent a check with no accompanying documentation, or with a poorly formatted stub, the data file reflects that. Your team has to track down the missing information—often by calling the customer or cross-referencing against open invoices manually.
Multi-invoice payments. A single lockbox payment frequently covers multiple invoices, sometimes dozens. Matching that payment correctly requires your team to identify each invoice, verify the amounts, and handle any line-item discrepancies—all before the cash can be posted.
Short payments and deductions. Customers routinely pay less than the full invoice amount. They take deductions for early payment discounts, returns, freight claims, or disputed line items. Each of these requires a judgment call: is the deduction valid? Who needs to approve it? How should it be coded? Without a structured process for collections and dispute management, these exceptions pile up fast.
Multi-bank complexity. Large organizations often maintain lockbox banking relationships with more than one bank, across multiple geographies. Each bank delivers data in a different format, on a different schedule, through a different portal. Consolidating that into a single coherent view of incoming cash requires either significant manual effort or the right integration layer.
ERP posting rules. Even when a payment is matched correctly, posting it to your ERP involves applying the right accounting codes, handling currency conversions for international payments, and complying with internal approval workflows. Any mismatch between the payment data and your ERP’s rules creates an exception that someone has to resolve.
How does lockbox automation address this?
The gap between what lockbox banking delivers and what AR teams actually need to post cash is where automation creates the most value. A modern lockbox automation solution doesn’t replace the bank’s role—it picks up where the bank leaves off.
AI-powered data enrichment
The bank sends a file with check images and basic payment data. An AI-powered solution like Serrala’s lockbox enrichment takes that file and goes further:
- Reads check images and any attached documentation using OCR and intelligent document recognition
- Extracts invoice numbers, PO references, customer identifiers, and payment amounts regardless of how they’re formatted
- Cross-references extracted data against open invoices in your ERP to identify matches
- Learns from each transaction, improving match rates over time as the model recognizes each customer’s payment patterns
The result is a payment file that arrives at your AR team already enriched—structured, matched where possible, and flagged for human review only where a genuine exception exists.
Automated matching and exception routing
High-confidence matches go straight to cash posting without anyone touching them. This is what the industry calls straight-through processing (STP)—a payment received, matched, and posted in your ERP with no manual intervention.
Exceptions are a different matter. Rather than dumping unmatched payments in a queue for someone to figure out, a well-designed lockbox automation solution routes each exception to the right person with full context: the check image, the extracted data, the candidate invoice matches, and any relevant customer history. That information cuts resolution time from hours to minutes.
Cash application at scale
Lockbox processing feeds directly into cash application—the process of posting matched payments to your ERP and updating open receivables. When lockbox data arrives clean and pre-matched, cash application becomes a largely automated step rather than a labor-intensive one. That has a measurable effect on DSO, on the accuracy of your AR ledger, and on the amount of time your team spends on transactional work versus higher-value analysis. We’ve explored how AI is reshaping cash application in more depth if you want to follow that thread.
What does an automated lockbox processing workflow look like?
For most organizations, automated lockbox processing sits inside a broader AR automation platform as part of the order-to-cash cycle. The end-to-end flow looks like this:
- Check receipt — customer mails a check to the bank-managed lockbox PO box
- Bank processing — the bank scans, deposits, and transmits check images and payment data
- AI enrichment — lockbox automation software extracts and structures the payment data
- Invoice matching — the system identifies matching open invoices in the ERP
- Exception routing — unmatched or partially matched payments are flagged with full context and routed to AR
- Cash posting — matched payments are posted to the ERP automatically
Steps 3 through 6 are where traditional lockbox banking ends and automation takes over. Organizations that run this process manually concentrate their effort in those same four steps—which is also where the errors, delays, and DSO impact tend to accumulate.
Who still relies on lockbox payments?
Lockbox banking is not a legacy service that’s quietly fading out. Checks remain a standard payment method across a range of industries and transaction types, and the organizations that receive them need a reliable way to process them at scale.
Healthcare and insurance see high check volumes from payers, third-party administrators, and government programs. Construction and real estate rely on check payments for project milestones and retainage releases. Government and public sector entities continue to issue check payments as standard practice in many jurisdictions. And across B2B commerce broadly, many buyers—particularly larger enterprises with established payment processes—continue to pay by check for control, documentation, or contractual reasons.
Even companies that have largely shifted to electronic payments typically maintain lockbox banking services for a subset of customers. That subset creates a workload that doesn’t go away on its own, and its impact on working capital management is real.
Key takeaways
- A lockbox payment is a check routed through a bank-managed PO box, giving companies faster access to funds by moving collection and deposit to the bank
- Lockbox banking has been a core treasury tool since the 1940s and remains actively used across healthcare, construction, public sector, and B2B commerce
- Retail lockbox handles standardized consumer payments; wholesale lockbox handles complex B2B payments with variable and often incomplete documentation
- Lockbox processing—the work of matching payments to invoices and posting cash—is where manual effort concentrates and where automation creates the most value
- AI-powered lockbox automation extends what lockbox banking delivers: enriching raw bank data, matching payments to open invoices, routing exceptions, and enabling straight-through processing
- Automating lockbox processing reduces DSO, improves cash application accuracy, and frees AR teams from transactional work
Frequently asked questions
What is a lockbox payment?
A lockbox payment is a check payment that customers send to a bank-managed post office box rather than directly to your company. The bank collects the checks, deposits the funds, and transmits payment data to your AR system. Lockbox banking was developed to speed up cash collection by moving the deposit step to the bank, reducing the time between a customer mailing a check and the funds clearing in your account.
What is the difference between retail and wholesale lockbox?
Retail lockbox handles high volumes of standardized consumer payments, typically with predictable formats and small amounts. Wholesale lockbox handles B2B payments, which tend to be larger, more complex, and accompanied by inconsistent documentation. Wholesale lockbox processing is significantly harder to automate because the payment data varies so much from customer to customer.
What is lockbox processing?
Lockbox processing is everything that happens after the bank delivers a payment file: extracting payment details, matching the payment to open invoices in your ERP, handling exceptions like short payments or missing documentation, and posting cash. Banks handle the physical collection and deposit. Lockbox processing is the AR team’s responsibility—unless it’s automated.
How does AI improve lockbox processing?
AI-powered solutions read check images and payment documents using OCR and intelligent document recognition, extract structured data regardless of format, and match payments to open invoices automatically. The model improves with each transaction, learning individual customer payment patterns over time. The result is higher straight-through processing rates and fewer manual touches per lockbox payment.
What is straight-through processing, and why does it matter for lockbox payments?
Straight-through processing (STP) means a payment is received, matched, and posted in your ERP without any human intervention. For lockbox payments, STP is the goal of automation. Higher STP rates mean faster cash posting, lower DSO, and less time spent by AR teams on transactional work.
Does lockbox automation integrate with SAP and other ERPs?
Yes. Lockbox automation solutions are built to integrate with major ERP platforms including SAP, Oracle, and Microsoft Dynamics. The matching and posting steps depend on live access to open invoice data in your ERP, so seamless integration is a fundamental requirement, not an optional feature.
Is lockbox banking still relevant as B2B payments go digital?
Yes. While electronic payment adoption is growing, checks remain standard in several industries and for certain transaction types. Most organizations with diverse customer bases continue to receive a meaningful volume of lockbox payments alongside their electronic payment channels. That volume requires a managed, scalable approach to lockbox processing regardless of how the rest of your payment mix shifts.
What is the impact of lockbox processing on DSO?
DSO measures the average time it takes to collect payment after a sale. Slow lockbox processing delays cash posting, which keeps receivables open longer and inflates DSO. Automating lockbox processing accelerates the path from payment receipt to posted cash, which directly reduces DSO and improves the accuracy of your working capital picture.
