Daily payment reconciliation is the control that proves every taka received matches an order, invoice or refund, and that every payout from a gateway, mobile wallet or courier is accounted for. When it works, nobody notices. When it fails, the symptoms look like finance problems but usually start in operations: orders without payment references, payments without orders, refunds recorded twice, and cash-on-delivery remittances that nobody checks.
The cost of fixing that is rarely a single software licence. It is a mix of process design, integration, analyst time, exception handling and audit evidence. This guide sets out those lines so you can budget for a realistic programme rather than a tool that automates only the easy half.
What a daily reconciliation process covers
- Mobile financial services: merchant collections, refunds, charges and settlement timing.
- Card and gateway payments: authorisations, captures, voids, chargebacks and fees.
- Bank transfers: deposits that arrive with incomplete references.
- Cash on delivery: courier remittances, holds, returns and deductions.
- Internal records: orders, invoices, credit notes and refunds that must tie back to the bank or wallet.
What drives the cost
- Number of channels. Each gateway, wallet, bank account and courier adds its own file format, settlement cycle and fee structure.
- Transaction volume and order value. Volume affects tooling and staffing; value affects the control strength and approval layers you need.
- Payout timing. Daily settlement is easier to reconcile than weekly or irregular payouts, especially when refunds are netted off.
- Reference quality. If customers pay without an order ID, matching becomes manual investigation rather than a rules engine.
- Current systems. A modern commerce platform with webhooks and a clean order table is cheaper to integrate than a legacy system with manual exports.
- Audit expectations. Banks, investors and enterprise customers may require evidence of segregation of duties, exception approval and retained records.
The cost model, line by line
1. Process design and controls
Document the flow from order to cash for each channel. Define who can approve a refund, write off a variance or change a matching rule. This is usually a short consulting engagement, but it determines whether the later automation is auditable or merely faster at producing an unexplained number.
2. Integration and data capture
You need reliable imports from gateways, wallets, banks and couriers, plus a stable order record. APIs and webhooks reduce manual uploads, but plan for retries, duplicates and late settlement files. Error handling should follow a consistent contract so failed events are visible rather than silently dropped; RFC 9457 is a useful reference for machine-readable API errors.
3. Matching rules and exception workflow
Most transactions should match automatically on amount, reference and date, with tolerance for fees and partial refunds. The expensive part is the exception queue: duplicate payments, split settlements, chargebacks, courier deductions and customer references that contain the wrong order number. Budget for a queue with owners, ageing and resolution codes, not just a dashboard.
4. Reporting and audit trail
Daily totals, unresolved items and a close checklist should be visible to finance and operations. Every adjustment needs a reason, an approver and a timestamp. If an auditor cannot reconstruct why a line was closed, the control is weak even when the bank balance agrees.
5. Run costs and people
Someone must own the daily close, investigate exceptions and liaise with the gateway or courier. Estimate analyst hours per day, add a supervisor review, and include cover for leave. Automation reduces hours but rarely removes the need for a named owner.
6. Contingency and reconciliation reserve
Keep a reserve for chargebacks, courier shortfalls and unidentified deposits. The reserve is not a slush fund: it needs an ageing report and a review date. Writing off differences without investigation hides leakage and weakens next year's budget case.
Build, buy or managed service?
- Build when you have high volume, unusual channels and an engineering team that can own the matching logic. Expect ongoing maintenance as providers change formats.
- Buy a reconciliation module when your commerce or accounting platform already supports your channels. Check whether it handles mobile wallets and courier remittances, not only cards.
- Use a managed service when the process is stable but you lack finance-operations capacity. Keep ownership of approvals and bank access inside the company.
Our commerce systems team builds reconciliation into payment and order workflows, and our pricing page explains how implementation and monthly support are scoped.
How to build a defensible budget
A workable monthly model is platform fee + amortised integration + analyst hours + exception handling + reporting. Add a separate line for provider fees, because gateway and wallet charges are a cost of accepting payments, not a cost of reconciling them. If a vendor bundles both, ask for the split.
Before you buy, measure the current state for one month: number of unmatched items, hours spent, value of unexplained differences and age of the oldest open item. That baseline does two things. It sizes the problem honestly, and it lets you calculate payback as leakage avoided + hours saved against the new run cost. Do not claim payback from headcount reduction unless you will actually remove or redeploy the role.
A 90-day plan
- Days 1–15: map every channel, settlement cycle and fee. Collect one month of statements and order exports.
- Days 16–30: define the daily close checklist, approval limits and exception reason codes.
- Days 31–50: integrate the two highest-volume channels. Automate matching on amount, reference and date.
- Days 51–65: add the exception queue and an ageing report. Assign owners and resolution targets.
- Days 66–80: run parallel reconciliation for two weeks and compare results with the manual process.
- Days 81–90: retire the duplicate spreadsheet, document the control and set a monthly review.
Questions to ask a vendor
- Which gateways, mobile wallets, banks and couriers do you integrate with today, and how are new formats added?
- How do you handle partial refunds, chargebacks and netted fees?
- Can we define our own matching rules and tolerances without a change request?
- What happens when a settlement file arrives late or twice?
- Who approves write-offs, and what audit trail is retained?
- What is the exit plan if we move to another platform?
Metrics that matter
- Automatic match rate and number of open exceptions.
- Age of the oldest unresolved item and value of unexplained differences.
- Hours spent on the daily close.
- Duplicate payments and refunds caught before payout.
- Days to close the month, not just the day.
Reconciliation also improves fraud detection because anomalies surface early. For the wider operating model, read how daily payment reconciliation matures year by year.
Sources
- Bangladesh Bank. Mobile Financial Services Statistics. Accessed 17 November 2026.
- Bangladesh Bank. Payment Systems Department. Accessed 17 November 2026.
- PCI Security Standards Council. PCI Security Standards. Accessed 17 November 2026.
- bKash. Developer Portal. Accessed 17 November 2026.
- Internet Engineering Task Force. RFC 9457: Problem Details for HTTP APIs. Accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.