Skip to content

Work directly with Muki · Kenya

M-Pesa Payment Reconciliation in Kenya

Know which payments belong to which customer—and which still need review.

M-Pesa reconciliation connects incoming payment records to the invoices, accounts or bookings they should settle. Muki helps Kenyan businesses design and implement matching workflows that reduce repetitive checking while keeping uncertain payments visible to a reviewer. This is useful when funds reach the business account but customer balances, receipts and management reports do not agree.

Match receipts using reliable references

A reconciliation workflow starts with a trusted payment source and a clear account or invoice reference. Provider transaction IDs help identify repeated records, while references and agreed business rules support allocation. Amount and phone number alone can be ambiguous: several customers may pay the same amount or use another person to pay. The design should distinguish confirmed matches, suggested matches and payments that cannot be safely allocated.

Handle partial payments, overpayments and exceptions

Real collections include one payment covering several invoices, part-payments, incorrect references, reversals and money received before an invoice exists. The workflow should make these cases explicit rather than force every receipt into a single automatic rule. An authorised user can review unresolved items, split or adjust allocations where allowed, and retain a record of the change. Financial treatment and reversal rules must be agreed with the person responsible for your accounts.

Worked example: two M-Pesa payments for one invoice

In this fictional example, a customer owes KSh 12,000 on invoice INV-1042. They pay KSh 7,000 with the correct reference. The system records the receipt and leaves KSh 5,000 outstanding. The second payment of KSh 5,000 arrives with reference INV-1402. The system sets it aside for review and keeps the balance open. A reviewer compares the original M-Pesa transaction ID and the payment details with the customer confirmation and invoice record. Once the match is confirmed, they apply the second receipt to INV-1042 and record who approved it and why. The ledger now shows KSh 12,000 received, two distinct receipts and a KSh 0 balance. If the same receipt is imported again, its transaction ID prevents a second posting. Request a reconciliation review below and share an anonymised example of the payment issue your team needs to solve.

Use the payment sources your business can access

Depending on your account and system, the project may use supported API notifications, eligible transaction retrieval services or authorised statement imports. Historical recovery is not guaranteed by having a new API connection. We confirm available dates, file formats, account access and data completeness before promising a backfill. Sensitive customer information should be shared through an agreed secure channel, using anonymised examples during initial discovery.

Reconcile totals before switching over

A pilot should compare a defined period of source payments with imported receipts, allocations and remaining exceptions. For example, a property team may need receipts linked to tenant accounts; a hotel may need deposits linked to booking balances. Acceptance measures can include matching coverage, outstanding exceptions and time spent reviewing them. These are project measures to establish with your data, not claimed results from an unverified case study.

Questions before booking

Can every M-Pesa payment be matched automatically?

No. Missing or incorrect references and shared payment amounts can make allocation uncertain. The system should route ambiguous records for review rather than guess.

Can you reconcile payments from previous months?

Historical work depends on the statements or API records available to your business and the quality of the matching ledger. Date coverage and completeness are assessed before quoting.

Can this work with rent, school fees or hotel bookings?

Those workflows can be assessed when the destination system provides suitable access. Each needs its own reference rules, permissions and handling for partial or excess payments.

Is reconciliation the same as STK Push?

No. STK Push initiates a payment request. Reconciliation checks received payment records and connects them to the correct business records.

Official technical references

Provider requirements and access can change. Confirm the current specifications during discovery.

Published product evidence

Integration case studies

Real product workflows, with source links and clear evidence limits. These are not invented client testimonials or measured customer outcomes.

Integrations, IT services & local support

Find the help you need.

Hire Me Chat on WhatsApp