Every courier company in Bangladesh runs on a quiet act of trust: handing a rider a bag of parcels in the morning and expecting a bag of cash back at night. With cash on delivery dominating e-commerce payments, a single rider on a busy Dhaka route can be carrying 30,000 to 50,000 taka by mid-afternoon. Rider cash handling — the rules, tools, and habits that govern that money between doorstep and deposit — is where COD security is actually won or lost.
Most cash losses in courier operations are not dramatic robberies. They are process failures: a deposit accepted without counting, a shortage “settled later,” a rider who learned that nobody checks. The eight practices below are the ones that consistently separate tight operations from leaky ones. They protect the company’s money and — just as importantly — protect honest riders from suspicion they do not deserve.
1. Record every collection at the doorstep, not at the depot
The single highest-impact change most courier companies can make: riders log each collection at the moment it happens, ideally in a rider app, with the amount, parcel ID, and timestamp. End-of-day recall is where discrepancies breed — a rider who delivered 22 parcels cannot reliably reconstruct 22 amounts at 8 pm, and a dishonest one does not have to.
Doorstep recording also captures the messy realities that cause disputes later: the customer who paid 2,000 against a 2,500 parcel and kept fewer items, the discount a merchant authorized by phone. Recorded in the moment, these are data. Recalled at night, they are arguments.
2. Give every rider a known expected total
Before a rider leaves the hub, the run sheet should state exactly how much cash he will hold if every delivery succeeds. As deliveries complete, the expected number adjusts for failures and partials. At day’s end, there is one correct deposit amount — computed, not negotiated.
This works both ways. The company knows what to expect; the rider knows exactly what he owes. Ambiguity is the enemy of both accountability and fairness.
3. Set cash-carry limits and mid-day deposits
Decide the maximum cash a rider may carry, and build routes and drop-offs around it. An illustrative policy: any rider holding more than 30,000 taka must deposit at the nearest branch or authorized point before continuing. High-value COD parcels — electronics, for example — might be scheduled early in the route so the biggest amounts spend the least time on the road.
Limits cap two risks at once: the loss from any single incident (theft, snatching, a lost bag) and the temptation that grows with the size of the bundle.
4. Verify deposits per parcel, on the spot
When the rider deposits at the branch, the cashier matches the cash against the parcel-by-parcel collection record — never against a verbal total. The count happens in front of the rider, both parties confirm, and the rider leaves with a receipt showing he is cleared.
If the deposit is short, the specific parcels are identified immediately, while the doorstep is hours old rather than days. This per-parcel match is one half of a discipline that continues into the back office; the full flow is covered in our COD reconciliation guide.
5. Never let shortages age
An unresolved shortage is a loan the company never agreed to make. Every gap gets a same-day reason code: customer dispute, partial delivery, genuine loss, or rider liability. If the reason is rider liability, the recovery terms are documented immediately — not “we will adjust it from your salary sometime.”
Two rules keep this fair. First, small honest errors should be survivable; a blame culture teaches riders to hide problems instead of reporting them. Second, patterns matter more than incidents: one 200 taka shortage is noise, the same rider short three Thursdays running is a signal. That signal only exists if every shortage is logged, even the ones you waive.
6. Separate cash custody from status updates
A parcel marked “delivered” and cash received are two different facts, and your process should treat them separately. The delivery status feeds customer notifications and merchant dashboards; the cash record feeds settlement. When one person or one field controls both, the classic fraud becomes possible: mark delivered, keep the cash, and let the gap surface weeks later as a merchant complaint.
Modern rider management systems enforce this by design — the app records delivery outcome and collected amount as distinct entries, and back-office COD tracking matches cash against status automatically, so a delivered-with-no-cash parcel raises a flag the same day instead of hiding in the pile.
7. Rotate routes and audit randomly
Familiarity is good for delivery speed and bad for cash control. A rider who runs the same route for a year builds relationships with customers — mostly a good thing, but it also creates room for informal arrangements: cash held “until tomorrow,” personal credit extended on the company’s money, or collusion on fake failed deliveries.
Periodic route rotation and random audits keep the system honest without accusing anyone. An audit can be as simple as calling five of a rider’s customers from yesterday: did the parcel arrive, how much did you pay, did you get what you ordered? Ten minutes of calls, done unpredictably, changes behavior across the whole fleet.
8. Pay riders well, on time, and in the open
The cheapest cash security measure is a rider who has more to lose than to gain. Riders who are paid late, or whose incentives are opaque, are being trained to see the cash bag as leverage. Riders who are paid fairly and on schedule, with transparent per-delivery incentives they can check themselves, overwhelmingly protect the system that pays them.
Hiring matters here too — verified references, guarantor documentation, and a probation period with lower cash limits are standard in well-run Bangladeshi courier operations. Broader team practices are covered in our post on rider management best practices.
A quick illustration: how the practices compound
Consider an illustrative operation with 20 riders each collecting 25,000 taka a day — 500,000 taka daily through rider hands, roughly 13 million a month at 26 working days. If loose process leaks even a quarter of one percent of that — unresolved shortages, quiet write-offs, one bad actor — that is over 30,000 taka a month, silently. The practices above cost mostly discipline, not money, and they close exactly that kind of leak. The point of the example is not the specific numbers; it is that small percentage leaks on large cash throughput are always bigger than they feel.
Where software fits
Every practice above is enforceable on paper for five riders. At twenty, fifty, or across multiple branches, paper enforcement decays — checks get skipped on busy days, and busy days are when leaks happen.
This is what courier management software does structurally. With Drix, each rider’s run sheet carries expected amounts automatically, doorstep collections are logged in the rider app with timestamps, branch deposits are validated per parcel, and shortages create trackable exceptions that cannot silently age. Supervisors see rider-level cash positions live, so the question “who is holding how much right now” always has an answer.
The same data doubles as fairness infrastructure: honest riders get a clean, provable record, disputes resolve from timestamps instead of memory, and incentives calculate from verified deliveries.
Trust, but verify — systematically
Rider cash handling is not about distrusting riders. It is about building a system where honesty is easy to prove and problems surface in hours, not weeks. Companies that get this right lose less money, keep better riders, and settle merchants faster — the three things that compound into a courier business people trust.
Drix gives Bangladeshi courier companies that system out of the box: rider apps for doorstep collection, per-parcel deposit matching, live cash positions, and exception tracking that feeds straight into merchant settlement. See how it would work with your fleet — book a free demo and we will walk through a full day’s cash cycle, from first doorstep to final deposit.
