The verdict in three sentences
Manual multi-rail reconciliation is a sink of time and errors: 1 to 2 hours a day to match receipts across card, bank transfer and mobile money with your orders. An automated dashboard driven by webhooks plus CSV export cuts that to a few minutes of review and surfaces the 1 to 3% orphan transactions the human eye misses. The return on investment is quick: roughly NGN 130,000 of labour time saved per month.
Why multi-rail reconciliation breaks down
Each rail has its own export format, labels and payout schedule. Reconciling by hand means opening three files, hunting for matches and chasing discrepancies. The typical causes are well known.
| Cause of discrepancy | Typical frequency | Effect |
|---|---|---|
| Timeout (customer charged, status pending) | 3 to 6% of tx | Order not confirmed |
| Duplicate (double-click, retry) | 1 to 2% of tx | Double-charge risk |
| Missed webhook | 1 to 2% of tx | Status never updated |
| Partial / rounding amount | < 1% of tx | Accounting gap |
| Untracked refund | variable | Balance skewed |
Overall, 1 to 3% of transactions stay orphaned at day's end. On 200 transactions/day that is 2 to 6 lines to investigate each evening.
The automated workflow
The principle: each rail sends a webhook on payment confirmation, your system updates the order status, and a daily CSV export per rail serves as source of truth for automatic matching. The dashboard shows KPIs at end of day.
| KPI | Definition | Target |
|---|---|---|
| Confirmed transactions | Valid webhook + order | > 97% |
| Pending transactions | Awaiting confirmation | < 3% |
| Gross amount collected | Sum of payments | reference |
| Rail fees | Commission taken | 1.5 to 2.5% |
| Net amount | Gross minus fees | to settle |
| Orphan transactions | No match | to investigate |
This table generates automatically each evening. The employee only handles the handful of orphan lines instead of reconciling everything by hand.
Mini case study
Chidi runs an online shop in Lagos with 200 transactions/day across card, transfer and mobile money. Before, an employee spent 1.5 hours a day reconciling, about 39 hours a month. At NGN 3,500 loaded per hour, that was roughly NGN 136,500/month. After the dashboard, review drops to 15 minutes a day (orphan lines only), about 6.5 hours/month, or NGN 22,750. Saving: about NGN 113,000/month, plus the systematic detection of pending transactions that would otherwise be lost.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
How many orphan transactions should I expect?
Budget 1 to 3% of daily volume. On 200 transactions/day that is 2 to 6 lines to check each evening, mostly timeouts and missed webhooks.
Is the webhook enough, or do I also need the CSV export?
Both are complementary: the webhook updates status in real time, the rail's CSV export is the source of truth to catch missed webhooks. Reconciliation cross-checks the two.
What do I do with a pending transaction at end of day?
Poll the status via the rail's API. If the customer was actually charged, confirm the order; otherwise let it expire or trigger a clean retry with an idempotency key.
What is the real ROI?
For a shop at 200 tx/day, the 2026 order of magnitude is roughly NGN 110,000 to 135,000/month of labour saved, not counting recovered revenue on pending transactions.
Does it work across multiple countries?
Yes, the same dashboard consolidates card, transfer and mobile money rails across countries, each with its export format normalised on import.
Let's talk about your project. We set up your multi-rail reconciliation dashboard and you get your evenings back. 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.
