A proof of delivery is not compliance paperwork — it is money paperwork. Many customers’ payment terms run from receipt of the signed POD, so your invoice can be gated on a document sitting in a driver’s cab. Paper PODs historically take 5–14 days to surface after delivery, and every one of those days is pure DSO. The discipline: collect the POD as the delivery completes, attach it to the shipment, and invoice the day the box lands — not the day the paper does.
Why does a delivery receipt gate your invoice?
Because your customer’s accounts-payable team will not pay for a delivery they cannot prove happened. Contract terms frequently start the payment clock at receipt of the signed POD, and even where they don’t, an invoice without one invites the cheapest dispute in the book: “send us the POD first”. The shipment was flawless, the delivery was on time — and the cash is hostage to a signature on a piece of paper nobody has scanned yet.
Where do 5–14 days go?
Into the most analog stretch of the move. The signed sheet rides in the driver’s cab until the shift ends, joins a pile at the depot, waits for the weekly paperwork run, gets scanned, then waits again to be matched to the right shipment file. The industry’s working range for paper POD lag is 5–14 days after delivery — a stretch during which the job is done, the costs are booked, and the revenue is legally uninvoiceable for many customers.
What does ePOD actually change?
It deletes the transit of paper. Industry reports credit electronic POD with DSO reductions of 30–50% — the ranges vary widely by study, so treat the number as directional — but the mechanism is not in dispute: the POD lag is the single most compressible stretch of a forwarder’s order-to-cash cycle, because nothing in it adds value. It is a document commuting.
What does collect-at-delivery discipline look like?
- Chase on the milestone, not the calendar: the delivery event triggers the POD collection the same day — not a weekly sweep of what’s missing.
- Attach, don’t file: the POD lands on the shipment record itself, where billing and the customer’s accounts team can both reach it.
- Unblock the invoice immediately: the day of delivery becomes the day of invoicing, because the gating document already exists.
- Escalate the stragglers: a POD still missing after the window becomes an exception with an owner, not a surprise at month-end.
This is how the desk runs it: as deliveries complete, it collects the POD and attaches it to the shipment, so the document your invoice is gated on exists the day of delivery — the flow is on how it works. What happens to the invoice after that is its sibling desk’s territory: Receivables AI. Run the cash-cycle math on your own volumes in the calculator, and see the guide for where POD sits in the milestone chain.
Put the watch on your boxes.
Everything on this page runs live in a working tracking desk. Bring ten shipments on the water and watch the updates land before the questions do.
Book the working session