A deep dive into COD reconciliation
COD is the dominant payment method in emerging markets. But reconciling cash between drivers, dispatch, and bank statements is where most distributors lose money. Here's how to fix it.
The COD problem nobody talks about
In Pakistan, UAE, and KSA, cash-on-delivery is not a side payment method. For most distributors, it is the primary payment method — 60% to 95% of B2C and small-B2B transactions settle in cash.
That cash flows through your business like this:
- Customer pays the driver in cash
- Driver collects cash from 30-80 stops in a day
- End of shift, driver brings cash to dispatch
- Dispatch counts cash, deposits to bank
- Bank statement arrives next day
- Finance reconciles to invoices
At every step, money goes missing. Not because everyone is a thief — but because reconciliation is so hard that small errors compound.
Where the money leaks
We have audited COD operations at 20+ distributors. The leaks are consistent:
Leak 1: Driver shortages (1-3% per shift) Driver collects PKR 145,000. Hands in PKR 144,200. Where did 800 rupees go? Maybe change wasn't returned. Maybe a customer paid in 1000-rupee notes and got change in 500s wrong. Maybe the driver bought lunch. Without per-stop tracking, you cannot tell.
Leak 2: Wrong-customer reconciliation (0.5-1%) Driver was supposed to collect 2,500 from Ali Stores. Got 2,500 from Hassan Mart instead (similar names, same area). Both are marked paid in your system. Three weeks later you re-bill Ali Stores who insists he paid. Customer angry, money in dispute.
Leak 3: Bank deposit slip drift (0.2-0.5%) Cashier deposits PKR 1,250,000 to bank. Slip says 1,250,000. Bank statement shows 1,249,500. The cashier swears it was full. Maybe miscount. Maybe shrinkage. With weekly reconciliation cadence, you discover this 7 days late.
Leak 4: Returned/refused orders (2-5%) Order was COD 5,000. Customer refused at the door. Driver brings product back. Your system still shows order as out-for-delivery. Cash never came. SKU sits in returns bay for weeks. Inventory wrong, AR wrong, driver compensation wrong.
Total leaks: 4-10% of COD revenue, depending on your discipline. At PKR 100M of monthly COD, that's PKR 4-10M lost monthly. Annualized: maybe more than your entire IT budget.
What proper reconciliation looks like
- Per-stop cash recording. Driver records collected amount at each stop, in the app, before moving to the next. Not at end of day. Not from memory.
- Driver daily handover with countersigned slip. Both driver and dispatch initial the count. Photo of cash stack saved.
- Cashier deposit slip uploaded same-day. Photo of bank deposit slip attached to the daily close.
- Automated bank statement matching. Daily bank statement (or web-scraped balance) compared to expected deposit. Variance flagged within 24 hours.
- NDR workflow for refused stops. Driver marks "refused" with reason and photo. System auto-creates return-to-warehouse task. Order reverts to "returned" status, not "delivered."
Done right, your COD leak drops to under 0.5%. That's not a small win — at scale, that is the difference between healthy margin and operating at a loss.
How DistroOps handles this
Our delivery + COD modules tie together:
- Driver mobile app records cash per stop with photo capture
- End-of-shift handover screen with cashier countersign
- Bank statement import (CSV or API) for daily auto-match
- Variance dashboard for finance
- Per-driver leak reports (which driver consistently runs short?)
We have customers who recovered 6% of revenue in the first 90 days just from tightening this loop. Not from extra sales. From plugging leaks they didn't know they had.
The hard part
The hardest part of fixing COD reconciliation is not the software. It is the operational discipline. Drivers don't like recording per-stop cash if they have been doing it from memory for 10 years. Cashiers don't want a second sign-off slowing down their cash count.
The software has to make the new process faster than the old way, or it will not stick. That is what we designed for. Each new step takes seconds, not minutes. Drivers actually prefer it because it protects them from being blamed for variances that weren't theirs.
If you are reading this and your COD reconciliation is still on Excel, you are leaking. Maybe 3%, maybe 8%. The first step is measuring it. The second step is fixing it.
Take it for a spin
Try DistroOps free for 14 days
No credit card. Full access. Cancel anytime.
More articles
Why emerging-market distributors need mobile-first software
Most Western distribution software assumes warehouse workers and salespeople sit at desks. In Pakistan, UAE, and KSA, that's rarely true. Here's what mobile-first really means.
ZATCA Phase 2: what KSA distributors need to know
Saudi Arabia's ZATCA e-invoicing Phase 2 is here. We break down what changed, what the compliance deadlines are, and how to prepare.
Choosing between a traditional ERP and modern SaaS for FMCG
You've been quoted PKR 50M for a SAP implementation. Is it really worth it? A practical comparison framework for FMCG distributors.