Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Payments & Reconciliation 6 min read

Cash on delivery reconciliation cost in Bangladesh: a scoping guide

What drives cash on delivery reconciliation cost in Bangladesh, the cost lines to budget, and how to scope a pilot without inventing savings.

E
EncryptTechBD · 0 comments
Euro banknotes and coins scattered on a surface
Photo: Martin Vorel / StockSnap

Cash on delivery looks simple from the storefront: the customer pays the rider, the courier sends the money, the seller records the sale. Behind that sentence sit three clocks that rarely agree. The courier remits on its own cycle, the order status changes when delivery is confirmed, and the ledger records cash when finance books it. Reconciliation is the work of making those clocks tell the same story.

That work is where money quietly leaks. A returned parcel is marked delivered. A partial delivery is paid in full. A courier fee is deducted twice. A marketplace settlement arrives net of charges nobody can identify. This guide explains what drives the cost of fixing that, how to build a budget without pretending there is one price, and how to scope a first pilot.

What reconciliation has to match

A useful reconciliation links seven things:

  • Order: the customer, the items, the agreed price and the delivery charge.
  • Consignment: the courier's tracking number and the parcel it belongs to.
  • Delivery event: delivered, partial, refused, returned to origin or lost.
  • Cash collected: what the rider actually took, including any adjustment.
  • Courier fee: delivery charge, return charge, weight adjustment and any penalty.
  • Settlement batch: the remittance that groups many consignments into one bank transfer.
  • Ledger entry: the accounting record that recognises revenue, fees and cash.

If any of these lacks a shared key, the reconciliation becomes a manual investigation. The cost is not the software. It is the hours spent finding the link.

The factors that move cost

  1. Order volume. Cost follows consignments, not revenue. A high-value, low-volume business can have a simpler reconciliation than a low-value, high-volume one.
  2. Number of couriers. Each provider has its own file format, remittance cycle, deduction rules and dispute process.
  3. Partial delivery and returns. These create the majority of exceptions because one order becomes several financial events.
  4. Payment mix. Cash, mobile financial services, card and bank transfer each produce different evidence and different timing.
  5. Marketplace sales. A marketplace may settle net of commission, fees and refunds, so the seller's ledger must model deductions the storefront never shows.
  6. Accounting system. A system with an open API and a clean chart of accounts is cheaper to integrate than one that requires monthly spreadsheet imports.
  7. Warehouse and branch count. Multiple dispatch points add allocation and cash-handover rules.
  8. Who owns the exception. If three departments can edit the same record, every investigation starts with a disagreement.

The cost model

Price the work in these lines, and ask every provider to use the same structure:

  • Process mapping: documenting the current flow from order to bank credit, including every spreadsheet and phone call.
  • Courier integration: ingesting delivery and remittance files or APIs, with error handling for missing or late files.
  • Matching engine: rules that link order, consignment, settlement and ledger entry, plus a score for uncertain matches.
  • Exception workflow: a queue with an owner, an age, a reason code and an audit trail.
  • Ledger integration: posting revenue, fees, returns and cash movements to the accounting system with a reversible batch.
  • Cash controls: separation between the person who confirms a remittance and the person who posts it.
  • Reporting: unmatched value, ageing, write-offs and courier-level variance.
  • Training and documentation: who runs the daily close, who approves an adjustment and what they sign.
  • Run cost: hosting, file transfer, monitoring and the hours to maintain courier rules.
  • Internal time: your finance and operations staff in workshops, testing and data cleanup.

A sizing model you can defend

Use your own counts rather than an industry average:

monthly exceptions = consignments per month x exception rate

review hours = monthly exceptions x minutes per exception / 60

close days = working days from period end to signed reconciliation

For illustration only, if a business handles 4,000 consignments a month and one in twenty becomes an exception at six minutes each, that is 200 exceptions and 20 hours of review before any accounting adjustment. The figure is not a benchmark. It is a way to test whether a proposed fix addresses the volume you actually have.

Build, buy or manage

  • Buy an existing reconciliation module: fastest if your couriers and accounting system are already supported. You accept its matching rules and its reporting.
  • Build a custom matching layer: justified when courier rules, marketplace deductions or branch cash handling are specific to your business. It requires an owner after launch.
  • Managed reconciliation: a partner runs the daily close. Useful when no one internally owns the process, but you must retain approval authority and access to the evidence.

Questions to ask a vendor

  1. Which couriers and payment methods are supported today, and how is a new one added?
  2. How are partial deliveries, returns and lost parcels represented?
  3. What happens when a remittance file arrives late or is missing a consignment?
  4. Can an adjustment be reversed, and who can approve it?
  5. How does the system prevent the same remittance from being posted twice?
  6. What evidence is kept for each match and each write-off?
  7. Who owns the data if we end the engagement?
  8. What is the monthly run cost, and what is billed per transaction or per courier?

A 90-day plan

Days 1-15: map the current flow and count exceptions by type for one settlement cycle. Days 16-30: agree the matching keys and the exception reasons, then clean the worst master data. Days 31-60: run a parallel reconciliation for the highest-volume courier, comparing the new result with the manual one line by line. Days 61-75: add the remaining couriers and the ledger posting, with a reversal test. Days 76-90: move to a daily close, publish the exception report and agree the monthly review.

Controls and metrics

  • Unmatched value: the amount and count still open at the end of each day.
  • Exception ageing: how many items are older than the agreed resolution window.
  • Write-off rate: value written off as a share of cash collected, reviewed monthly.
  • Recovery rate: disputed courier deductions recovered after evidence is submitted.
  • Days to close: the time from period end to a signed reconciliation.
  • Duplicate postings: should be zero, and any occurrence needs a root-cause note.

If you need a reconciliation flow that fits Bangladeshi courier and payment operations, start with Commerce Systems. The pricing page explains how integration and support are scoped. For the daily control that keeps the ledger honest, read how daily payment reconciliation matures.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes