Ask merchants in Bangladesh why they left their last courier, and delivery speed is rarely the first answer. The first answer is money. Merchant payment settlement — getting collected COD cash back to the seller, accurately and on time — is the single biggest trust factor between a courier company and its merchants. A seller can forgive a late parcel. A seller cannot forgive a late payout, because that payout is their restocking budget.
Yet in most growing courier operations, settlement is the process held together with the most tape: Excel ledgers, manual bKash sends, WhatsApp screenshots as payment proof. This post breaks down why payouts get delayed, what a clean settlement process looks like, and how to fix the bottlenecks before merchants start moving volume elsewhere.
What merchant payment settlement involves
Settlement sounds simple: collect cash at the doorstep, pay the merchant. In practice, every payout is a small calculation with several moving parts:
- COD collected for each of the merchant’s delivered parcels in the cycle.
- Delivery charges deducted per parcel, which vary by zone — inside Dhaka, suburban, outside Dhaka — and by weight.
- COD fees, typically a percentage of the collected amount.
- Return charges for failed deliveries, if your rate card includes them.
- Adjustments — partial deliveries, damage claims, promotional discounts, previous cycle corrections.
The net of all that goes out through the merchant’s preferred channel: bKash, Nagad, or bank transfer. Multiply this by two or three hundred merchants on different payout cycles, and settlement becomes an accounting operation in its own right.
An illustrative example: a merchant had 40 parcels delivered this week collecting 60,000 taka in COD. Delivery charges total 3,400 taka, the 1% COD fee is 600 taka, and two returns carry 130 taka in return charges. Net payable: 55,870 taka. Every number in that calculation must be defensible, because the merchant will check it against their own records — good merchants always do.
Why payouts get delayed
1. Settlement waits on reconciliation that has not happened
You cannot pay out cash you have not verified. If rider deposits are not matched to parcels daily, the accounts team must choose between paying from unverified numbers (and eating the errors) or holding payouts until the numbers are checked (and eating the merchant complaints). Most choose delay. The root cause is upstream — covered in detail in our COD reconciliation guide — but the merchant experiences it as “my payment is late again.”
2. Manual calculation of deductions
When delivery charges live in one spreadsheet, the merchant rate card in another, and returns in a third, computing one merchant’s net payable means cross-referencing all three. One accounts person can do maybe 30–40 accurate merchant statements a day this way. At 200 merchants on a weekly cycle, the math stops working and cycles slip.
3. Disputes freeze the whole payout
A merchant disagrees with one deduction, so the entire payout waits while someone investigates. Without parcel-level records, “investigating” means digging through rider run sheets from last week. A dispute over 200 taka delays a 50,000 taka payout by three days.
4. Payment execution is manual
Even after the amount is settled, someone has to send 200 individual bKash or Nagad transfers, or prepare a bank file, and then record each transaction reference by hand. Manual execution invents its own errors: a payout sent to the wrong wallet number, a transfer recorded twice, a payment sent but never logged.
5. Cash is not actually available
Sometimes the delay is not process — it is cash flow. Branch cash has not been banked, or collected COD has been used to cover operating expenses. This is the most dangerous version, because it means merchant money is funding the courier’s operations. If this sounds familiar, fix the cash discipline before touching the settlement process — no payout schedule survives an operation that spends its float.
What a healthy settlement process looks like
Fixed, published payout cycles
Merchants plan around predictability. Whether you settle daily, every other day, or twice weekly, publish the cycle and hit it every time. A courier that pays every Tuesday and Friday without fail beats a courier that sometimes pays in 24 hours and sometimes in six days — even if the average is faster. Set cycle expectations during onboarding so they are never a surprise; our merchant onboarding playbook covers how to document this from day one.
Statements before payments
Every payout ships with a statement: each parcel, its COD amount, its deductions, and the net. When merchants can see the math, most disputes never happen. When a dispute does happen, it is about one line item, not the whole payout — so you pay the undisputed amount on schedule and resolve the line item separately.
Parcel-level ledgers
The merchant’s balance should be a running ledger built from parcel events: delivery adds COD collected, each charge posts as its own line, each payout clears the balance. Ledgers make every balance explainable at any moment — which is exactly what a merchant asks for when they call.
A merchant panel instead of a phone line
Half of a settlement team’s day disappears into calls asking “how much do I get and when?” A self-service merchant panel answers that question before it is asked: live balance, pending COD, upcoming payout date, downloadable statements, and payment history with transaction references. Merchants who can see their money trust you with more volume.
Recorded settlement channels
Every bKash, Nagad, or bank payment gets logged with its transaction ID against the payout it fulfilled. When a merchant says “I never received Tuesday’s payment,” the answer takes ten seconds, not a forensic hunt through someone’s phone history.
Fixing settlement: where to start
If your payouts are chronically late, fix things in this order — each step unlocks the next:
- Reconcile daily. Verified cash is the raw material of settlement. Until rider deposits match parcels every day, nothing downstream can be fast.
- Centralize the rate card. Delivery charges, COD fees, and return charges per merchant must live in one system that calculates deductions automatically, not in the accounts team’s memory.
- Automate statement generation. The statement should fall out of the parcel ledger with zero manual assembly.
- Separate disputes from payouts. Pay the clean amount on cycle; hold only the disputed lines.
- Log every payment against its statement. Channel, transaction reference, timestamp.
Courier businesses that run this loop tightly often find they can shorten their payout cycle — moving from weekly to every-other-day settlement — because the bottleneck was never the cash, it was the verification. And faster documented payouts are one of the strongest sales arguments a courier has when pitching new merchants.
Where software carries the load
Settlement is a calculation and record-keeping problem, and it is exactly the kind of work software should absorb. In a COD management system like Drix, the chain is connected end to end: a rider’s verified collection posts to the merchant’s ledger, charges apply automatically from the merchant’s rate card, statements generate per cycle, and payouts are recorded with their bKash, Nagad, or bank references.
The merchant sees all of it in their own panel — pending COD, processing amounts, paid history — which turns “where is my money” calls into a dashboard they check themselves. For the operations side, settlement dashboards show exactly how much is payable, to whom, and when, so cash planning stops being guesswork.
Payout speed is a growth lever, not just an accounting duty
In a market where merchants routinely split volume across two or three couriers, settlement performance decides who gets the bigger share. Fast, accurate, transparent payouts are the cheapest merchant retention tool a courier business has — and the hardest one for a competitor to match if they are still running on spreadsheets.
Drix gives Bangladeshi courier companies the full settlement chain: verified COD in, automatic deductions, cycle-based statements, and payment records across bKash, Nagad, and bank transfers, with a merchant panel that answers questions before they become calls. See how your payout cycle could run — book a free demo and bring your current rate card with you.
