A receivable has both money and meaning
A supplier receives a check for $9,800. That amount alone does not explain whether the customer is paying one invoice, several invoices, a partial balance or an invoice less a disputed deduction. A lockbox service addresses two connected tasks: collecting and depositing incoming payments, and extracting the accompanying information so the seller can apply the cash to accounts receivable. The paper check is one object; the explanation of what it pays is another.
The traditional arrangement directs customer mail to a location processed by a bank or its service operation. Instead of the seller's staff opening mail, endorsing checks, preparing deposits and rekeying remittance details, the service performs contracted steps and returns payment data and images. Bank of America's treasury-management explanation describes both faster receivables deposits and remittance information. [1] This is a collections service wrapped around payment processing, rather than a new payment rail.
The operating chain
A conceptual workflow begins with mail receipt, opening and sorting. Staff or equipment separates payments, remittance documents and other correspondence. Check images and relevant document data are captured, batch totals are reconciled, and eligible items enter the collection process. The service then makes agreed information available to the seller, which imports it into its receivables system. Exceptions go to a decision or research queue instead of being assumed to have matched successfully.
Treasury's General Lockbox Network description illustrates these separate functions: capturing check and remittance images, forwarding check information for settlement, balancing batches, recording payments and making information available through files or reporting systems. [2] That federal example is useful for understanding the architecture, but its eligibility and operating policy should not be generalized to commercial businesses. The bank account receiving value and the system recording invoice settlement remain distinct endpoints.
At each handoff, totals can reconcile while individual allocations remain wrong. Ten payments adding to $100,000 can all be deposited correctly while two customers' receivables are misapplied. A deposit-control total therefore answers whether the payment batch is complete; it does not independently answer whether every invoice was credited properly. Good design preserves both dollar-level reconciliation and item-level provenance.
Wholesale and standardized remittances
A standardized remittance coupon can carry an account reference in a predictable place. A business-to-business payment may arrive with a multi-page explanation covering many invoices, credits and deductions. Those are different data-processing problems even if both end in check collection. The service design should match the actual remittance mix instead of assuming that a single automated extraction rate describes every document type.
U.S. Bank markets lockbox services with imaging, information access and digital receivables features, while its wholesale lockbox materials show exception-review workflows. [3, 4] These are examples of commercial offerings, not evidence that every bank includes the same functionality or that the advertised benefits occur automatically. A buyer needs its own requirements for fields, document retention, file formats, delivery frequency and exception handling. The bank's product name alone does not specify which accounts-receivable tasks the customer still performs.
A useful test set includes ordinary payments, multi-invoice payments, missing references, credit notes and inconsistent totals. The aim is not merely to demonstrate that a scanner reads clean examples. It is to determine how uncertainty is represented and where a human decision becomes necessary. A service that confidently outputs the wrong invoice number can create more rework than one that clearly flags an unresolved document.
Cash receipt is not cash application
Imagine a hypothetical $9,800 check accompanied by instructions to settle Invoice A for $6,000 and Invoice B for $4,000, less a $200 claimed deduction. The bank can deposit $9,800 without deciding whether the deduction is commercially valid. The seller might apply $6,000 to A and $3,800 to B, leaving B with $200 outstanding pending review. Alternatively, a documented policy might move the deduction to a separate dispute workflow. These are accounting and commercial decisions, not facts the check-processing rail can infer.
The control is that total cash applied must equal $9,800 and the remaining exposure must remain visible somewhere appropriate. Writing off $200 without authority would make the customer balance look settled at the cost of hiding a concession. Applying $10,000 merely because the remittance lists that invoice total would overstate receipts. The worked example demonstrates why extracting text and deciding what the text means are different services.
If the payment has no usable reference, the seller may record unapplied cash while investigating. That can be the honest intermediate state. It should not be confused with lost money, nor should it be treated as an invitation to choose an invoice simply to clear the queue. A record linking the payment, image, payer evidence and subsequent decision permits later correction without destroying the original audit trail.
Faster collection releases working capital
Consider an illustrative company receiving $50 million of annual check collections, assumed evenly distributed over 250 collection business days. Average daily receipts are $200,000. If a lockbox consistently reduces the pre-deposit processing delay by two business days, the steady-state amount released from that delay is approximately $400,000. This is a simplified float model: actual benefits depend on timing, weekends, receipt geography, cutoff rules, collection availability and variability in payment volumes.
At an assumed 6% annual marginal funding cost, financing $400,000 less would save about $24,000 per year. The company has not created $400,000 of new annual sales or earned $400,000 every year. It has accelerated an existing stream of collections and, under the model, reduced the average funding requirement. Treating the released balance as recurring income would overstate the economic benefit.
Suppose the service costs $18,000 a year and genuinely saves $12,000 of internal labor that can be removed or productively redeployed. The illustrative annual benefit is $24,000 plus $12,000 minus $18,000, or $18,000 before implementation, exception work and other costs. If labor remains fully staffed with no alternative use, the cash savings may be smaller than the accounting estimate. The model should distinguish eliminated expense, freed capacity and merely shifted work.
The data benefit can exceed the float benefit
Bank of America's 2022 Intelligent Receivables announcement describes combining payment information and remittance detail across electronic and paper channels. [5] This broader receivables architecture matters because a company moving away from checks can still face the same matching problem. A faster rail does not guarantee that the invoice reference travels with the money in a form the seller can use.
Consider a company whose deposit process is already fast but whose staff spends hours finding what each payment covers. Its strongest business case may be reduced unapplied cash and research effort rather than another day of collection speed. The relevant measures include payment-to-application time, automatic match accuracy, aged exceptions and the number of times staff must contact a customer for clarification. A higher automated match rate is beneficial only if the matches are correct.
Data quality also affects commercial behavior. Incorrectly unpaid invoices can trigger unnecessary collection calls or shipment holds. Incorrectly paid invoices can conceal a genuinely overdue balance. Neither error changes the original bank deposit, but both affect customer service and credit decisions. The lockbox's contribution is therefore partly financial operations infrastructure: making a real cash event usable by the systems that manage customer obligations.
Exception handling is part of the product
An exception queue needs an owner, a deadline and an authority model. A bank may ask the customer to review an ambiguous item or supply missing data under a contracted decisioning service. The seller needs a backup for absences and a clear understanding of what happens if no response arrives. Historical demonstrations or marketing screenshots should not be treated as the customer's operative cutoff schedule; actual service terms and implementation instructions govern.
A sound review process distinguishes image-quality problems, insufficient remittance data, amount discrepancies and commercial deductions. Each requires different evidence. Approving a questionable image for collection does not approve a write-off. Correcting a transcription error does not authorize a change to a customer's legal obligation. Separating these decisions makes responsibilities clearer and reduces the risk of granting a payment-processing user excessive authority over accounting adjustments.
Returns create another handoff. Money credited after deposit may later be reversed when an item is returned or otherwise adjusted under applicable rules. The receivables system needs the link back to the original payment and allocation. Otherwise, operations can show a paid invoice while treasury sees that the related cash was removed. Lockbox processing does not make a check irrevocable or erase the seller's exposure to a failed collection.
Treasury's post-2025 boundary
The federal Treasury Financial Manual states that after December 31, 2025, Treasury lockbox services are provided only on an exception basis, and agencies must seek an exception or waiver annually. It connects the transition to electronic federal collections with Executive Order 14247. The General Lockbox Network page also says the Bureau of the Fiscal Service is not accepting new lockbox requests. These are material qualifications to any present-day description of the federal service. [2, 6]
They do not amount to a general prohibition on commercial lockboxes. Commercial banks continue to describe their own services, subject to their terms. [1, 3] An analyst should distinguish a federal agency's permission to use a Treasury collection channel from a private company's choice of bank receivables services. Using a historical federal manual as an unqualified sales description in October 2026 would miss that distinction and the change in eligibility.
Buying a collection workflow, not a magic matching engine
A practical evaluation maps where checks arrive, how often information is missing, how payment files enter the ledger and who handles unresolved items. It then prices the entire workflow: service fees, integration, image access, document storage, exception labor and transition costs. Concentrating activity in a provider can simplify operations, but it also makes continuity, alternate routing and data-export arrangements more important.
The best outcome is not simply that deposits move faster. It is that the company knows which money arrived, what it is intended to pay, what remains uncertain and how later adjustments will be reconciled. A lockbox can improve cash timing and reduce manual work. It cannot by itself decide every commercial deduction, guarantee collection finality or turn an unexplained receipt into a correctly settled receivable.
Sources
- Bank of America, Treasury Management Help; lockbox description checked October 4, 2026SourceBack to text: ↑1↑2
- Bureau of the Fiscal Service, General Lockbox Network; current service and no-new-requests statementOfficial sourceBack to text: ↑1↑2
- U.S. Bank, Cash, check and digital payment acceptance; checked October 4, 2026SourceBack to text: ↑1↑2↑3
- U.S. Bank, Wholesale Lockbox exception-review comparison; product workflow illustrationSource · PDFBack to text: ↑1↑2
- Bank of America, Intelligent Receivables enhancements; October 2022SourceBack to text: ↑
- Treasury Financial Manual, Volume I, Part 5, Chapter 4600; exception-only lockbox service after December 31, 2025Official sourceBack to text: ↑