Mobile money is a rail, not an exception
Mobile money is a payment rail in Rwanda, not an exception. Treating it as an exception is how reconciliation gets painful — MoMo receipts pile up in a spreadsheet, references drift from invoice numbers, and month-end becomes a translation exercise.
Here is the reconciliation loop that works. Four steps, run daily, takes about 15 minutes once you’re practiced.
Step 1: capture the reference at receipt
Every MoMo payment has a transaction reference. Capture it as soon as you record the payment — before the customer leaves, before the tab closes. Without the reference, reconciliation later becomes guesswork.
Step 2: map ref to invoice immediately
If you know which invoice this payment covers, tag it now. If you don’t, record the payment as unallocated — but record it. Unallocated payments with a captured reference can be matched next week. Unrecorded payments are just lost.
Step 3: reconcile against the MoMo statement weekly
At the end of each week, pull your MoMo statement (MTN and Airtel both support CSV export). Compare the statement to the payments recorded in your ledger. Three possible outcomes per row: matched, missing in ledger, missing in statement. The second two are the ones to investigate immediately — not at month-end.
Step 4: auto-rule the repeats
After a month of this, you’ll notice patterns. Customer X always pays on Fridays. Customer Y pays in round 500K chunks across multiple invoices. Customer Z pays under a cousin’s name. Build allocation rules for the common patterns — most tools support them — and you cut reconciliation time in half again.
Don’t wait for direct MoMo-to-ERP integrations to solve this. Capture the reference manually today; the integration will backfill against the refs you already have when it arrives.
Reconciliation isn’t glamorous. It’s the least interesting part of finance. But it’s also the part that determines whether you trust your own numbers — and whether the RRA does, too.