The verdict in three sentences
Mobile money reconciliation means crossing three sources that never perfectly agree: the order, the gateway statement and the operator settlement. In 2026 the average discrepancy is 2-5% of transactions, and catching it by hand takes 3-7 days versus under 24 hours with an automated dashboard. The real decision isn't CSV or API but weekly manual or automated daily — and automation saves 12-20 hours/month while cutting losses.
Operator CSV export vs status API (2026)
Both data-collection methods have limits. 2026 comparison.
| Criterion | Operator CSV export | Status API |
|---|---|---|
| Frequency | daily/weekly | real time |
| Discrepancy detection delay | 3-7 days | <24 h |
| Manual effort | high | low (automatable) |
| Data-entry error risk | high | none |
| History | limited to the file | complete |
| Integration cost | none | medium (initial dev) |
| Manageable volume | a few hundred | thousands |
CSV works at launch but doesn't scale. The status API, once integrated, feeds a dashboard that catches discrepancies before the customer complains.
Three sources to cross and alert thresholds
Serious reconciliation compares the same amounts across three planes. 2026 reference points.
| Source | What it says | Delay | Associated fees |
|---|---|---|---|
| Order (your DB) | expected amount | instant | 0 |
| Gateway / webhook | confirmed amount | near-instant | collection fee |
| Telco statement (settlement) | amount actually paid | T+1 (MTN Ghana) | 1-1.75% |
| Order vs gateway gap | double-count, failure | <24 h | — |
| Gateway vs settlement gap | fees, holds, disputes | T+1 to T+3 | — |
Operational rule: fire an alert as soon as the discrepancy exceeds 0.5% of the day's volume. Below that it's noise; above it, it's a signal to investigate immediately.
Mini case study
Akosua runs an online grocery in Accra: 350 transactions/day, 105,000 GHS/day in volume. With weekly manual matching she caught discrepancies (3% on average, ~3,150 GHS/day) after 3-7 days, once stock was already shipped and disputes hard to settle. Switching to a daily dashboard crossing order, gateway and MTN Ghana settlement (T+1, 1.5% fee), she now catches any gap over 0.5% within 24 hours. Gain: ~16 hours/month of manual reconciliation saved and a sharp drop in late-dispute losses.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
CSV or API for reconciliation?
CSV to start at low volume, API once you pass a few hundred transactions/day. The API feeds an automated dashboard that catches discrepancies in under 24 hours instead of 3-7 days.
What discrepancy rate is normal in 2026?
Between 2 and 5% of transactions depending on operators and webhook quality. Above 5%, look for an idempotency or reference-mapping problem rather than blaming the operator.
What alert threshold should I set?
A discrepancy above 0.5% of daily volume warrants immediate investigation. Below that it's statistical noise tied to settlement delays.
How much time does it really save?
Between 12 and 20 hours/month for a merchant at a few hundred transactions/day, by replacing weekly manual matching with an automated daily dashboard.
Why cross three sources and not two?
Because order vs gateway catches failures and duplicates, but only the telco settlement reveals fees, holds and missing transfers. Without the third source you don't know what actually landed in your account.
Let's talk about your project. We build your daily reconciliation dashboard crossing orders, gateway and settlements. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
