Delivered three weeks ago, customer paid cash, remittance report has no entry — the collected-but-never-remitted shipment is rare but real. The audit and escalation path for COD money that disappeared into the pipeline.
How it happens
Collection marked, delivery closed, but the AWB slips the remittance run — processing misses, RTO-flagged-in-error, or the rider's deposit didn't reconcile. It's not theft usually; it's a reconciliation gap that your audit has to catch.
The monthly audit
Remittance report → match AWBs to delivered COD orders → the missing entries are the follow-up list. Sellers who skip this lose real money slowly — at COD scale, a few un-remitted orders monthly adds up to a bad week of margin.
The escalation packet
AWB, delivery proof (POD/OTP record), collected amount, the absence from remittance reports — a complete ticket that says 'this delivered, cash collected, money never arrived'. Written escalation with the packet gets movement; phone complaints don't.
The structural protection
Reconcile monthly so nothing ages past the dispute window. On chronically-leaky carriers, the pattern is a carrier-choice signal — COD trust is the whole job; a network that loses it doesn't deserve the lane.
Pure Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Reconcile remittance monthly
Delivered-but-unremitted AWBs surface in the diff.
Keep delivery proof ready
POD/OTP record is the evidence that collection happened.
Escalate in writing with the packet
AWB + delivery + amount + report absence.
Change carriers on patterns
Chronic remittance loss is a relationship problem.
