The verdict in three sentences
When payments arrive through four operators (M-Pesa, MTN MoMo, Airtel Money, and local wallets), each day produces 0.3 to 1.2 % orphan transactions — collected but never matched to an order. The key is a three-key matching model (merchant reference + amount + timestamp) plus knowing each operator's settlement delay. Properly tooled, a merchant closes the daily books in under 30 minutes instead of several hours.
Settlement delays change everything
A transaction that's "successful" on the customer side isn't credited the same day across operators. Confusing payment with settlement is the number-one source of discrepancies.
| Operator | Customer confirmation | Merchant settlement | Typical orphan rate |
|---|---|---|---|
| Fast wallet (e.g. M-Pesa) | Immediate | T+0 | 0.2 - 0.5 % |
| MTN MoMo | Immediate | T+2 | 0.6 - 1.2 % |
| Airtel Money | Immediate | T+1 | 0.4 - 1.0 % |
| Local operator | Immediate | T+1 to T+2 | 0.5 - 1.1 % |
This lag is why you never reconcile "live": an MTN transaction confirmed Monday only appears on the settlement statement Wednesday.
The three-key matching model
To match automatically, combine three identifiers. None is sufficient alone.
| Matching key | Reliability | Weakness |
|---|---|---|
| Merchant reference alone | 95 % | Missing if USSD truncated |
| Amount alone | 60 % | Duplicate identical baskets |
| Timestamp alone | 40 % | Bursts within the same second |
| Reference + amount | 98 % | Rare collisions |
| Reference + amount + timestamp | 99.5 % | Near zero |
The remaining 0.5 % — the orphans — go to manual review: a reference lost on the operator side, an unrecorded refund, or a forgotten test payment.
Closing workflow in under 30 minutes
- CSV export or API pull of all four operator statements (5 min).
- Automatic three-key matching (instant).
- Review orphans, typically 3 to 12 lines per day (10-15 min).
- Validate and export to accounting (5 min).
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
James, who runs a restaurant, takes 420 orders per day split across a fast wallet (55 %), a second operator (30 %) and MTN (15 %). At an average 0.8 % orphan rate, that's about 3.4 transactions/day to investigate. Before tooling, his bookkeeper spent 2 hours/day matching by hand. With three-key matching, she handles the 3-4 orphans in 12 minutes and closes in 25 minutes total. Gain: ~1 h 35/day, nearly 40 hours/month freed up.
FAQ
What is an orphan transaction?
A collection on the operator statement with no matching order in your system, or the reverse. 0.3 to 1.2 % appear per day depending on operators.
Why not reconcile in real time?
Because settlement differs: a fast wallet credits T+0 but MTN credits T+2. Reconciling before settlement creates false discrepancies. Match on settlement statements, not customer confirmations.
How long for a well-tooled daily close?
Under 30 minutes, including 10-15 minutes for orphan review alone, versus several hours of manual matching.
Is CSV export enough or do I need an API?
CSV works up to a few hundred transactions/day. Beyond 500-1,000/day, an API integration automates the export and avoids handling errors.
How do I lower the orphan rate?
By enforcing a unique, untruncated merchant reference on every payment and systematically recording refunds: that drops the rate below 0.3 %.
Let's talk about your project. We'll set up your multi-operator reconciliation and a closing dashboard that runs in under 30 minutes. 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.
