The AP→AR leak is a vendor cost that lands after the customer invoice went out — a late accessorial, an amendment fee, a D&D pass-through — and gets absorbed as a write-off because nobody re-opens a billed job. It is not a billing error: the vendor’s charge is correct and gets paid. The leak is on the other side — the charge was billable to your customer and never was. On forwarder net margins of roughly 3–4%, one absorbed fee can erase a shipment’s entire profit, which is why the fix — flag every post-invoice cost for re-billing while the job is warm — pays for itself faster than anything else on the desk.
Why does this cost hide so well?
Because it arrives correct, arrives late, and falls between two teams. AP’s job is to verify the vendor’s charge and pay it — which it does, properly. AR’s job ended when the customer invoice went out on Tuesday. The amendment fee that lands Thursday belongs to both and therefore to neither. One job generates financial events across weeks — a job departing week one may not see its final vendor invoice for six — so the question “did anything arrive after we billed?” has to be asked continuously, per job, by someone whose job it actually is. Usually it is no one’s.
What does one leak cost?
Run the arithmetic on a single box — illustrative numbers, but honest shape. A job with $2,000 of revenue at a 4% net margin earns $80. A $150 amendment fee absorbed as a write-off doesn’t dent that job’s profit; it deletes it and takes the next job’s with it. The industry version of the same story: margins restated from 18% to 13% after late invoices landed — an illustrative figure, but any controller who has watched a “final” job P&L decay for six weeks will recognise the direction. On thin margins, leakage isn’t a hygiene issue. It’s existential.
The $2,000/$80/$150 example above is illustrative, not a benchmark. Substitute your own average job revenue and margin — or let the calculator do it with your volumes.
Why is “while the job is warm” the whole game?
Because re-billing has a half-life. A supplementary line sent three days after the original invoice, while the shipment is still in your customer’s inbox, is routine. The same line three months later is an awkward call, a dispute, or — most often — a decision that it isn’t worth the relationship friction, at which point the write-off becomes policy. Speed is not a nice-to-have here; it is the difference between a recovered cost and an absorbed one.
What does the fix look like?
A flag, not a heroic quarterly audit. The desk already matches every incoming vendor invoice to its job — so it also knows when that job’s customer invoice went out. Any cost arriving after that timestamp gets flagged and routed for re-billing while the job is warm. It works because reconciliation and billing share one platform: the payable side lives here, and the receivable side — getting that re-bill collected — lives with our sibling desk at receivables-ai.com. The full leak-to-recovery loop is mapped in the complete guide.
From reading to watching.
Everything on this page runs live on a working match desk. Bring one week's vendor invoices and watch every line meet its job file.
Book the working session