What reconciliation must answer
For every transaction, finance should know who paid, what they paid for, which invoice changed, whether a receipt was issued and whether the money appears in the expected M-Pesa account.
Finance systems and business decisions · 9 min read
How to match M-Pesa collections to invoices, investigate exceptions and close each day with a defensible payment record.
For every transaction, finance should know who paid, what they paid for, which invoice changed, whether a receipt was issued and whether the money appears in the expected M-Pesa account.
Use the transaction reference, amount, payer phone, invoice number and payment time. Customer names can vary and one customer may settle several invoices, so name-only matching creates avoidable errors.
Automatically or manually match clear transactions. Place incomplete, duplicated, reversed or unidentified items in an exception queue. Never hide unmatched money by assigning it to the nearest-looking invoice.
Compare system receipts and invoice allocations with the M-Pesa statement. Record who reviewed exceptions, what changed and which items remain open for the next day.
Practical checklist
Keep learning
A practical Kenyan workflow for moving a WhatsApp enquiry into a professional invoice, M-Pesa STK request, confirmed payment and receipt.
Read nextWhat Kenyan businesses should include in professional quotations and invoices, with downloadable starting templates.
Read nextWhen spreadsheets remain useful—and when connected customer, payment, delivery and finance workflows become safer.
Read next