The goods left on Monday. The invoice went the same week. The terms say thirty days. So why does the cash routinely arrive in week six — and why does nobody in the business feel they did anything wrong? For many distributors, part of the delay sits not in collections but in the query loop: the quiet machinery of discrepancies, credit notes and restarted approval cycles that sits between a delivery and its payment, adding days at every turn while everyone involved behaves reasonably.
If you want to reduce DSO, chasing harder is the blunt instrument. The sharper one is making invoices unarguable in the first place. This article traces where the days actually go, gives you two measurements that locate the problem in your own ledger, and works through the fixes in the order they pay back.
Anatomy of the six weeks
Follow one imperfect invoice through a typical cycle. The day counts are illustrative; the stages are not:
| Stage | What happens | Illustrative days added |
|---|---|---|
| Invoice raised | Compiled from delivery notes days after fulfilment rather than at delivery | +2 |
| Query raised | Customer's goods-in count disagrees with the invoice on one line; in this example the whole invoice parks | +3 |
| Investigation | Delivery note found, driver asked, warehouse checked; nobody can prove the doorstep | +2 |
| Credit note | Credit note raised and sent; depending on the customer's AP process, the corrected balance may re-enter approval | +2 |
| Payment run | The corrected invoice misses one payment run and waits for the next | +3 |
| Added to the 30-day terms | ≈ +12 days — delivered Monday, paid around day 42: week six |
Notice three structural features. One disputed line can hold the whole invoice — many AP processes match the full document before paying any of it (partial-payment practice varies by customer), and with consolidated invoicing one disputed drop can then hold a week of drops. Corrections can restart clocks, where the customer's approval process treats the credited invoice as new work or the fix misses a payment run. And the delay compounds silently: no stage looks unreasonable, so no stage gets fixed.
Two numbers that locate your problem
Clean invoice rate: the percentage of invoices accepted and processed without a billing query, amendment or credit caused by an invoice or delivery error — payment timing is tracked separately, as a collections outcome. Measured this way, it separates a collections problem (clean invoices paid late) from an accuracy problem (invoices that could not survive the goods-in check). The fixes for the two are entirely different.
The query-delay diagnostic: alongside headline DSO, compare the average days-to-pay of queried invoices with clean ones. This is an internal diagnostic, not an accounting-standard DSO variant — and turning the gap into money needs value weighting, because days times invoice count is not cash. Each queried invoice contributes its value × its excess delay in receivable-pound-days; the financing cost is that total × your annual cost of capital ÷ 365. Illustratively: a £2,000 invoice paid 14 days later than comparable clean ones is 28,000 receivable-pound-days — about £6.14 of financing at an 8% cost of funds. Summed across a year's queried invoices, that figure is the business case for everything below.
The fixes, from source accuracy to collections
1. Invoice what was actually delivered
Invoice disputes have many parents — PO mismatches, pricing, VAT treatment, duplicates, master-data errors — but for distributors one class looms large: delivery mismatch. The invoice says what was ordered, the customer received what was delivered, and the difference — a short, a substitution, a refusal — becomes finance's problem a week later. Generating the invoice from the delivery record, adjusted at the door, removes a major source of delivery-mismatch queries at origin. This fix comes first because it deletes a whole class of queries at source rather than resolving them faster.
2. Attach the proof to the invoice
For the disputes that remain, resolution speed is set by how fast you can demonstrate the doorstep: signature, photos, timestamps, recorded quantities. When the proof sits on the order record, the “investigation” stage can shrink from a search across paper to a direct record lookup.
3. Raise the invoice at delivery, not at week-end
Batching invoice runs adds pure, silent days. An invoice raised on fulfilment removes your own creation lag and puts the document into the customer's process sooner — while the delivery is still fresh enough to check without an argument. When payment falls due is set by terms; what you control is when the process starts.
4. Handle credits at the visit
Where a return or refusal is known at the door, capturing it there — linked to the invoice it corrects — means the credit note goes out with the correction already agreed, instead of after a fortnight of correspondence.
5. Make paying frictionless, then chase systematically
Statements that show a clean, current position; reminders that escalate on a schedule rather than when someone remembers; a payment link or card option for customers who will pay now if it takes a minute. Collections discipline belongs at the end of the list not because it is unimportant, but because applied to inaccurate invoices it mostly generates queries faster.
Where RouteMagic fits
RouteMagic attacks the loop at its origin. The final invoice is generated on fulfilment from the delivery record itself — quantities as delivered, adjustments captured at the door — with signature and photo ePOD attached to the same order, so the invoice matches the doorstep and the proof is one click away when questioned. Returns captured at the visit link straight to their credit notes. Statements with aging — and dunning messages that escalate by aging bucket — run the systematic chasing, the Customer Portal lets B2B customers see their invoices and pay online, and the whole flow syncs both ways with the accounting package. The pattern shows up in cleared customer results: About Roofing reports 18% fewer delivery disputes and two hours saved daily on sales reconciliation since moving its operation onto the platform (case study).
Conclusion
Six-week cash on thirty-day terms is often less a story about bad payers than about invoices that could not survive the customer's goods-in check, and a correction loop where every reasonable step adds days. The durable fix runs upstream of collections: invoice exactly what was delivered, carry the proof on the record, start the clock at fulfilment, and settle corrections at the door rather than by correspondence. Then let systematic statements and easy payment do the chasing. Start with the two measurements — clean invoice rate, and the days-to-pay gap between queried and clean invoices — because together they tell you whether your DSO problem is accuracy or collections, and they price what fixing it is worth in cash terms — and whichever answer your ledger gives, it will be the first evidence-based conversation the business has had about where the six weeks actually go.
