Payment collection and reconciliation answer different questions
Collection asks: did the customer pay?
Reconciliation asks: can the business prove which obligation that payment settled, and do the merchant and provider records agree?
A customer can be fully paid while finance reconciliation is still open.
The reconciliation chain
- Invoice or recurring obligation.
- Payment attempt or customer-initiated payment.
- Provider transaction/reference.
- Match to the correct customer/account and billing period.
- Settlement/fee evidence where relevant.
Payment matching comes before full reconciliation
Matching answers which invoice the transaction belongs to. Reconciliation then checks whether the amount, provider reference and downstream finance records agree.
This is why an invoice can be marked paid before the settlement batch has been fully reconciled.
Why recurring businesses need more than a transaction export
A monthly business needs to know not only that KES 3,000 arrived, but which November invoice it satisfied. Provider exports alone do not always contain the merchant's complete commercial context.
Typical reconciliation exceptions
- Wrong account/reference.
- Amount mismatch.
- Duplicate success.
- Provider payment with no invoice match.
- Invoice marked paid without supporting transaction evidence.
- Settlement mismatch or missing downstream record.
Reconcile continuously where possible
Daily or near-real-time matching turns month-end into reporting instead of detective work. Exceptions are easier to solve while the payment is recent and support context is still available.
Useful metrics
- Automatic match rate.
- Unmatched transaction count and value.
- Paid-to-reconciled lag.
- Duplicate-payment incidents.
- Manual reconciliation touches.
- Settlement exceptions.
M-PESA-specific implementation
The separate M-PESA reconciliation workflow covers C2B fields such as TransID and BillRefNumber, as well as how Transaction Status can support secondary reconciliation.
Collection, matching and reconciliation are three steps
Collection is the movement of money from customer to merchant/provider route. Matching identifies which customer and invoice the transaction belongs to. Reconciliation checks that the commercial ledger, provider evidence and downstream finance records agree.
A business can succeed at collection and still have poor reconciliation if references are wrong or provider transactions are never matched to invoices.
A simple recurring-payment example
A member owes KES 3,000. M-PESA confirms a KES 3,000 transaction with a provider reference. The billing system matches that transaction to the November membership invoice, marks the invoice paid and later connects it to the settlement evidence. Each step answers a different question.
Why exceptions need separate categories
- Unmatched payment: money arrived but the invoice is unknown.
- Amount mismatch: the transaction and invoice differ.
- Duplicate success: more than one successful payment maps to one obligation.
- Settlement exception: customer payment is valid but downstream finance evidence differs.
Separating those categories helps the right team act without reopening customer collection unnecessarily.
Sources
- Safaricom C2B API: https://developer.safaricom.co.ke/apis/CustomerToBusiness
- Safaricom Transaction Status API: https://developer.safaricom.co.ke/apis/TransactionStatus
