Managing COD Cash Flow in a Courier Business

A courier business in Bangladesh holds a strange position: enormous amounts of cash pass through its hands every day, and almost none of it belongs to the company. COD cash flow is the movement of that money — from a customer’s hand at the doorstep, into a rider’s bag, through a branch cashbox, into a bank or mobile wallet, and out again to the merchant. Managing it badly is the fastest way for an otherwise healthy courier operation to collapse, because the failure mode is not losing profit. It is spending someone else’s money.

This post covers how COD cash flow actually behaves in a courier business, the timing gaps that create both risk and opportunity, and the operating rules that keep the cash engine safe as volume grows.

The core problem: you are a custodian, not an owner

Take an illustrative day: your riders collect 500,000 taka in COD. Your actual revenue from that day — delivery charges and COD fees — might be 40,000 taka. The other 460,000 taka is merchant money in transit. It sits in your bags, boxes, and accounts, but it is a liability, not income.

The danger is that in a cashbox, your 40,000 and their 460,000 look identical. When fuel needs paying, salaries come due, or a new branch needs a deposit, the merchant float is right there, liquid and tempting. Courier companies that dip into it start a countdown: as long as new collections keep coming in faster than payouts go out, the hole stays hidden. The moment volume dips — a slow month, a merchant leaving, an Eid holiday week — payouts bounce, word spreads, and merchants pull out at exactly the moment the company can least afford it.

The first rule of COD cash flow is therefore structural, not clever: merchant money and company money must be separated in your records from the moment of collection, even while the physical cash is mixed in the same bag.

Mapping the cash cycle

COD cash moves through five stages, and each stage has a holding time:

1. Doorstep to rider. Cash collected at delivery. Held by the rider for hours.
2. Rider to branch. End-of-day deposit at the branch or hub. Held overnight to a day.
3. Branch to bank. Branch cash banked or moved via agent banking or mobile financial services. Held one to two days depending on branch location and banking access.
4. Verification. Collections matched to parcels, exceptions resolved, merchant ledgers updated. This runs in parallel if your COD reconciliation is daily — or adds days if it is not.
5. Payout. Net amounts sent to merchants by bKash, Nagad, or bank transfer on the settlement cycle.

Add the stages up and you get your cash cycle: the average number of days between a customer paying at the door and the merchant receiving their money. For a well-run operation on a twice-weekly payout cycle, that might be three to four days. For a loosely run one, it stretches to a week or more — and every extra day is more cash at risk, held in more hands, across more branches.

The float: risk and responsibility

The money in transit at any moment is your COD float. Illustrative math: if you collect 500,000 taka a day and your cash cycle is four days, roughly 2,000,000 taka of merchant money is inside your operation at all times.

That float creates three obligations:

• Security. Two million taka spread across rider bags and branch cashboxes is a physical risk. Deposit limits, cash pickup routines, and insurance thresholds all scale with float size. Deposit limits and per-parcel verification cover the doorstep-to-branch leg of this risk.
• Traceability. At any hour, you should be able to say how much of the float is with riders, how much in branches, and how much in bank accounts awaiting payout. If that question takes a day to answer, the float is unmanaged.
• Restraint. The float is not working capital. Some businesses earn modest interest on floats held in bank accounts — but the principal is untouchable. Where your actual earnings come from is a separate question, covered in how courier companies make money.

Cash flow rules that keep the engine safe

Bank daily, or as close as your geography allows

Cash sitting in a branch overnight is unproductive and unprotected. Metro branches should bank daily. Remote branches with limited bank access can use agent banking or scheduled cash escort to a hub. The measure to watch is cash-on-hand at close of business per branch — set a ceiling and treat breaches as incidents.

Never fund operations from the float

Operating expenses come from earned revenue: your delivery charges and fees, invoiced and separated in the ledger. If revenue does not cover expenses, that is a pricing or volume problem to fix honestly — not a hole to paper over with merchant money.

Match payout cycles to verification speed

Promising daily payouts sounds like a sales advantage, but if your reconciliation takes two days, you will either pay unverified amounts or miss the promise. Set the cycle you can hit every single time, then shorten it as your verification gets faster. Predictability beats raw speed for merchant trust — merchants plan their restocking around a payout date they can rely on.

Forecast the lumps

COD volume in Bangladesh is seasonal and spiky. Eid campaigns can double daily collections for two weeks; monsoon flooding can slow returns of undelivered parcel cash from upazila branches. Each spike swells the float and stresses every stage of the cycle. Forecast the big ones and pre-arrange banking capacity, extra cash pickups, and payout liquidity before the surge, not during it.

Watch three numbers daily

• Collections vs deposits. Total COD marked collected today against total cash actually deposited. Any persistent gap is a reconciliation failure in the making.
• Float by stage. How much is with riders, in branches, in banks. Rising rider-stage float means deposits are slipping.
• Payables vs available cash. Total verified merchant payables against liquid cash earmarked for payouts. This ratio should never surprise you on payout day.

Where visibility comes from

None of the rules above survive contact with growth if the data lives in spreadsheets updated nightly. The numbers you need — float by stage, unverified collections, merchant payables — are aggregates of thousands of parcel-level events, and they are only trustworthy if every event is captured at the source.

That is the case for running the operation on a system built for it. A COD management platform records collection at the doorstep, deposit at the branch, and payout at settlement as linked events, so the float is computed rather than estimated. Dashboards in reports and analytics turn the three daily numbers into something an owner checks over morning tea instead of a report the accounts team assembles by Thursday.

Drix was designed for exactly this operating reality in Bangladesh: parcel-level cash tracking from collection to bKash, Nagad, or bank payout, with branch cash positions and merchant payables visible in real time.

Cash discipline is the business

Plenty of courier companies in Bangladesh have grown on thin margins. Almost none survive a broken cash cycle, because the float amplifies every weakness: sloppy reconciliation becomes missing money, slow banking becomes theft exposure, and one dipped-into payout becomes a merchant exodus.

The encouraging part is that COD cash flow responds quickly to discipline. Daily banking, separated ledgers, verified payouts, and three numbers watched every morning will stabilize most operations within a single payout cycle.

Drix gives courier businesses the visibility that discipline requires — live float tracking, automated merchant ledgers, and settlement records in one place. If you want to see your cash cycle end to end instead of reconstructing it from spreadsheets, book a free demo and we will map your current flow against what the system tracks automatically.