Proof of delivery in ABL is one of the quiet details that determines whether an invoice is financeable or only looks financeable. A borrower may have issued a valid invoice, recorded the sale, and included the receivable in the aging, but an asset-based lender still needs evidence that the customer received the goods or services and has a collectible obligation.
That evidence matters during lender screening, field exams, borrowing-base reporting, refinancing, and workout discussions. If invoice support is incomplete, a lender may exclude the receivable, add a reserve, delay closing, increase verification sampling, or treat the account as a recurring documentation problem. The dollar impact can be large when the missing support sits inside the largest customers, newest invoices, or invoices close to the eligibility cutoff.
This article is an educational borrower guide, not legal, tax, accounting, investment, or financing advice. DCE does not lend, underwrite, fund, approve, broker, or guarantee financing. The goal is to help management teams prepare cleaner receivable support before a lender, factor, or field examiner asks for it.
Why proof of delivery affects receivable eligibility
An ABL borrowing base starts with accounts receivable, but it does not stop there. Lenders test whether the receivable is valid, collectible, properly aged, free of known disputes, and supported by documentation. Proof of delivery is part of that chain. It helps show that the invoice is not only recorded in the accounting system but also tied to a completed shipment, service milestone, or accepted deliverable.
The issue is practical. If the customer later says the product never arrived, arrived short, arrived damaged, was rejected, or is still awaiting acceptance, the lender may not want that invoice in the eligible base. This is why receivable eligibility is closely connected to the accounts receivable aging report, the eligible receivables framework, and the supporting documentation kept behind each material invoice.
| Documentation item | What it helps prove | Common lender concern if missing |
|---|---|---|
| Invoice | Amount billed, customer, date, terms, and description of goods or services. | The receivable may not match the aging, contract, purchase order, or shipping records. |
| Purchase order or contract | Customer authorization and pricing basis. | Customer may dispute price, quantity, scope, or authorization. |
| Bill of lading or carrier record | Shipment occurred and goods left the borrower’s control. | Invoice may be viewed as unsupported or premature. |
| Delivery confirmation | Customer, warehouse, or carrier confirmed receipt. | Customer may claim non-delivery, shortage, damage, or late shipment. |
| Acceptance or milestone support | Service, project, or custom goods met the billing trigger. | Invoice may be subject to future acceptance, retainage, or offset. |
Where borrowers get tripped up
The most common mistake is treating proof of delivery as an operations file rather than a collateral file. Shipping, customer service, warehouse, sales, and accounting teams may each hold part of the answer. The field examiner, however, needs the pieces to reconcile quickly: invoice, order, shipment, delivery, customer acceptance, credit memo history, and cash receipt.
A second mistake is relying on one generic report when the customer relationship needs more detail. Retail, big-box, government, healthcare, transportation, and project-based customers may have portals, routing guides, delivery windows, acceptance standards, shortage claims, or deduction processes that do not show up cleanly in the aging. If those issues create repeat credits or short pays, they also connect to dilution and reserves. The dilution reserve guide explains how credits, returns, and disputes can compress availability even when invoices were originally valid.
How proof-of-delivery gaps show up in a field exam
In a field exam, the examiner usually tests a sample of invoices from the A/R aging and follows each item back through the borrower’s records. The sample may emphasize large balances, new invoices, old invoices, customers with credits, related-party questions, or accounts that recently paid slowly. If the borrower cannot support the sample cleanly, the examiner may expand testing or recommend ineligibles and reserves.
That does not mean every invoice needs a perfect paper file. It means the company should know where support lives, how quickly it can retrieve it, and whether the support actually proves the billing event. The ABL field exam data room guide covers the broader reporting package, but proof-of-delivery readiness deserves its own checklist because it is usually assembled across multiple systems.
A borrower checklist for lender-ready invoice support
Before lender outreach, renewal, refinance, or a field exam, management should build a simple support map for the receivables that matter most. Start with the largest customers and the invoices that are new enough to support availability but old enough to raise collection questions if documentation is weak.
- Match invoice to order. Confirm that the invoice ties to a purchase order, contract, rate sheet, sales order, or other customer authorization.
- Match order to shipment or service completion. Keep bills of lading, carrier records, warehouse releases, time records, milestone approvals, or service completion evidence accessible.
- Confirm delivery or acceptance. Identify whether the lender will expect a signed delivery ticket, portal acceptance, customer receiving record, carrier proof, or milestone certificate.
- Track shortages and disputes separately. Do not bury known short pays, deductions, returns, or credit memos inside an aging footnote. Explain them in a dispute schedule.
- Reconcile support to the aging. Invoice numbers, customer names, dates, amounts, and open balances should tie cleanly to the A/R aging and general ledger.
- Document customer-specific rules. For major customers, note routing-guide penalties, chargeback patterns, portal timing, acceptance windows, and recurring documentation requirements.
What lenders want to see in the first conversation
A lender does not need every backup document in the first meeting, but the borrower should be able to explain its receivable process calmly and specifically. The strongest answer is usually operational, not promotional: how invoices are generated, when delivery is confirmed, where support is stored, how disputes are logged, when credit memos are issued, and how the A/R aging ties to the borrowing-base certificate.
This is why proof-of-delivery preparation belongs inside the broader ABL credit package. A lender-ready package does not simply say “our receivables are good.” It shows the reports, controls, and exception process that let a lender verify the receivables without reconstructing the company’s operations from scratch.
How DCE can help prepare the package
DCE can help borrowers pressure-test the receivable support package before lender outreach. That may include reviewing the A/R aging, identifying high-risk customers or invoice types, mapping invoice support by system, organizing field-exam data room materials, and building a concise explanation for known disputes, credits, or documentation gaps.
If you are preparing for an ABL refinance, factoring transition, renewal, or first lender meeting, submit the situation for direct review. We can help you organize the invoice-support package, borrowing-base narrative, and lender-ready questions before the process turns into a documentation fire drill.