Why wallet payments need their own routine
In Ghana, Mobile Money moves large volumes of everyday payments, from market stalls to school fees and supplier settlements. Operators such as MTN, Telecel and AT run wallets under Bank of Ghana rules, and interoperability through GhIPSS lets money move between networks and bank accounts. The convenience brings a recording problem: a business may receive hundreds of small credits.
Unlike a bank transfer, a wallet credit may carry limited reference text, and the sender’s name displayed may be a personal name that does not match the customer on your invoice. A spouse, a driver or an employee may pay on the customer’s behalf, so name matching alone is unreliable.
A dedicated reconciliation routine solves this. It turns a stream of anonymous credits into a clear statement of which invoices were settled, which are partly paid and which remain open.
A pharmacy that takes 150 wallet payments a day, mostly between 10 and 200 cedis, cannot rely on memory or on screenshots in a phone gallery. A structured daily total at closing time catches problems the same evening.
Setting up the weekly reconciliation
Choose a fixed day each week. Download or copy the wallet statement for the period, and list each credit with date, time, amount, sender number or name and transaction ID. Then match each credit to an invoice, using the amount and the reference text first and the sender second.
Mark each line with one of three statuses: matched, partly matched or unmatched. For partly matched items, record the balance still owed. For unmatched items, set a time limit, such as five working days, to find the source, after which the item is posted to a suspense account for your accountant to review.
Use the transaction ID as your anchor. Operators can confirm a transaction by its ID, which is invaluable in a dispute with a customer who insists that they paid.
Keep two columns for dates: the date on the wallet statement and the date you posted the entry. A long gap between them signals a process problem.
Fees, reversals and failed payments
Each channel has its own fee structure, and fees can vary by amount and by who bears them. Record them as costs, separate from sales, using the operator’s published tariff or the fee shown on the statement. Keep copies of tariff announcements for audit purposes.
Reversals occur when a payment is sent to the wrong number or is cancelled. A reversal appears as a debit on the statement and must be matched to the original credit. If you do not record it, the invoice looks paid when it is not.
Failed or pending payments should not be counted as received. Ask the customer for the confirmation message, then check the statement. Only mark an invoice settled when the credit is visible in the wallet.
Fees on large amounts can be significant, so periodically compare the fees you paid with what the tariff says you should have paid. A deduction larger than the tariff is a reason to contact the operator with the transaction ID.
Receipts and communication with customers
A customer who pays by MoMo expects proof. Give a receipt referencing the invoice number, the amount received and the transaction ID. A receipt closes the loop, helps the customer’s own bookkeeping and cuts down on repeat questions.
For recurring customers, a simple statement every month listing invoices, payments and balances prevents arguments. Keep the wording factual and avoid blaming the customer for late payments.
Be careful with messages. Never ask a customer to share a wallet PIN or a one-time code, and warn your staff that fraudsters impersonate operators. A message from you should only contain an invoice number, an amount and the correct payee details.
For deposits on large orders, issue a receipt that states the balance outstanding and the date it is due, so the customer is never unsure about what remains.
Tying wallet balances to the accounts
Treat each wallet as a bank account in the books. The opening balance plus credits minus debits and fees should equal the closing balance shown by the operator. If it does not, find the difference before posting a plug figure.
When wallet money is cashed out or moved to the bank, record the movement as a transfer between accounts, not as a sale or expense. Two entries should exist: one out of the wallet and one into the bank, matching in amount and date.
Use 4softerp.net to hold the entries for each company and compare them with the statements. It does not import wallet statements automatically, so you or your accountant enter or upload the data.
Review wallet access quarterly. Who knows the PIN, who can approve transfers, and does anyone who left the business still have access?
Limits of the ecosystem’s tools
4invoices.net issues PDF invoices and keeps an archive, so you can show a customer what was billed. It does not connect to MTN, Telecel, AT or any bank, and it does not confirm that a payment arrived.
The reconciliation described here is therefore a manual or accountant-assisted process. Its value lies in discipline: one sheet, one routine, one owner. That is enough to turn Mobile Money from a source of disputes into a record you can defend.
Keep a short written procedure for the person who covers when the usual reconciler is absent. A procedure of one page, with the day, the steps and the folder location, prevents gaps.