Small businesses in Kenya often face payment reconciliation problems when recorded payments don't match bank or mobile money statements, invoices or customer accounts. Common issues include missing transactions, duplicate entries, incorrect payment allocations, timing differences and unreconciled M-Pesa or bank receipts.
Identifying these discrepancies early helps businesses keep customer balances accurate, maintain reliable cash records and make informed financial decisions.
What are common payment reconciliation problems?
Payment reconciliation problems usually come down to six common issues. Below, we’ll look at what each issue looks like, why it happens, how to check it and how to prevent it from happening again.
Unmatched payments
A payment hits your M-Pesa or bank account, but you cannot tell which customer or invoice it belongs to. It usually happens because of missing, incorrect or unclear payment information.
What usually goes wrong?
- M-Pesa Till: You may see only the payer’s name and part of a phone number.
- M-Pesa Paybill: The customer may enter the wrong account number or an unclear reference.
- Bank transfer: The narration may show only the payer’s name.
- Third-party payments: A customer may pay from a relative’s or employee’s phone.
How to match the payment
Check the transaction code, amount, date and payer details against your open invoices. If there is no clear match, contact the payer using the available details. Until you have confirmed the payer, record the amount as an unallocated receipt. Do not assign it to a customer or invoice based on a guess.
How to prevent it
Ask customers to use the invoice number as the Paybill account number and print this instruction on every invoice. For M-Pesa payments, you can also ask customers to share the confirmation message after payment.
Duplicate entries
A customer suddenly shows a credit balance, or your books show more money received than your M-Pesa or bank statement. It usually happens because the same payment was recorded twice.
What usually goes wrong?
- M-Pesa SMS and statement: Someone records the payment from the SMS and enters it again from the statement.
- Two staff members: Different people record the same payment.
- Customer paid twice: The customer makes two separate payments for the same invoice.
How to check the payment
Search your books using the M-Pesa transaction code. If the same code appears twice, the payment was recorded twice, and you should remove the duplicate entry. If two different codes show the same amount, confirm with the customer whether they paid twice. If they did, refund the extra amount or carry it forward against the next invoice.
How to prevent it
Record the M-Pesa transaction code in the receipt reference field. Assign one person to record receipts for each payment channel so the same transaction is not entered twice.
Missing transactions
Your statement does not match your books, or a customer says they paid, but their balance is still outstanding. This usually means a transaction was missed.
What usually goes wrong?
- Bank deposits: Direct deposits, PesaLink transfers or bank charges are missed.
- M-Pesa payments: Weekend, after-hours or withdrawal transactions go unrecorded.
How to check the payment
Match every statement line to your books. Any unmatched line needs to be recorded.
How to prevent it
Record transactions from the downloaded statement, not SMS alerts. Check M-Pesa transactions daily and review weekend entries on Monday.
Incorrect amounts
Fees, charges, part payments or deductions can cause a mismatch between the invoice raised and the amount received.
What usually goes wrong?
- Payment fees: M-Pesa or bank charges reduce the amount received.
- Part payment: The customer pays only part of the invoice.
- Tax deduction: The customer deducts withholding tax before paying.
How to check the payment
Calculate the difference. Match it to a known fee, tax deduction or part payment. Record fees separately, request the withholding certificate or leave the invoice balance open as applicable.
How to prevent it
Record the full invoice amount against the customer and record payment charges separately as expenses. This keeps both balances accurate.
Timing differences
Your books and statement differ at month-end, but the difference clears early the following month. This usually happens when transactions are recorded on different dates.
What usually goes wrong?
- Uncleared cheques: A deposited cheque has not cleared yet.
- Late payments: A payment made on the last day appears in the next statement.
- Paybill transfers: Money reaches the bank after the customer has paid.
How to check the payment
List items recorded in your books but missing from the statement. Check the next statement for each one. If an item remains outstanding for more than two weeks, investigate it further.
How to prevent it
Keep M-Pesa and bank accounts separate in your books. Record transfers between them correctly and maintain a short list of outstanding items each month.
Customer account mismatches
One customer shows an unpaid balance while another has an unexplained credit, even though total receipts match the statement. This usually means a payment was allocated to the wrong customer.
What usually goes wrong?
- Similar names: A payment is posted to the wrong customer.
- Third-party payments: A director or employee pays for the company.
- Wrong invoice: A payment is applied to another invoice.
How to check the payment
Compare customer credit balances with overdue invoices for the same amount. If you find a match, correct the allocation and add a brief note explaining the change.
How to prevent it
Give each customer a unique code, use invoice numbers as payment references and send monthly statements. This helps catch allocation errors early.
How do you investigate a reconciliation difference?
Work through one account at a time. The same steps apply to bank reconciliation and M-Pesa accounting.
- Choose one account and one period, for example, your Paybill for September.
- Check that the opening balance in your books equals the opening balance on the statement. If it does not, fix the earlier month first.
- Download the full statement for the period.
- Tick each statement line that matches a book entry by transaction code and amount.
- List the statement lines left unticked.
- List the book entries left unticked.
- Compare the remaining difference with the patterns in the table below.
- Record each correction with a date and a note, and move anything still unexplained to suspense.
- Confirm that the adjusted book balance now equals the statement balance.
How to prevent recurring reconciliation errors?
Most repeat errors stop once everyone follows the same few rules. These controls suit a business with one or two people handling the money.
- Use one reference format. The invoice number goes in the Paybill account field, and the M-Pesa or bank code goes in every receipt entry.
- Match M-Pesa daily and the bank weekly, then close each month only when both agree.
- Separate duties where you can. The person who collects money should not be the only person who records it.
- Review the suspense account every week and clear anything older than 30 days.
- Write down how to treat charges, reversals and part payments so every staff member records them the same way.
- Lock or mark reconciled months so nobody edits them later without approval.
These rules deal with the accounting errors Kenya’s small businesses report most often, and they make it far easier to find a mistake when one still happens.
How can automation reduce reconciliation effort?
Most accounting software Kenyan businesses use can import a bank statement and match it against your books by amount, date and reference. Matched items clear on their own, so you spend your time only on the items left over. Many tools also flag possible duplicates and let you create entries for charges or receipts that appear only on the statement. Linking this with invoicing software means every receipt already carries an invoice number.
Automation has limits you should plan for. It cannot identify a payer when the reference is missing. It can suggest the wrong match when two customers pay the same amount on the same day. Statements must usually be in a supported CSV or Excel format.
Someone still needs to review suggested matches and the suspense account, since payment matching problems caused by poor references come back if the reference rule is ignored.
Start with references. Once every payment carries an invoice number or transaction code, most reconciliation issues become easy to trace, and the fear of hidden errors fades because each shilling has a clear home. Add a daily M-Pesa check and a weekly bank check, and treat anything that stays unexplained for more than a few days as a warning sign.
If you keep your books in TallyPrime, you can import bank statements in Excel or CSV format and match book entries with bank entries, then review only what remains unmatched. See how bank reconciliation works in TallyPrime.
Frequently asked questions
- What should I do when I cannot identify who made a payment?
Record it in an unallocated receipts or suspense account and keep the statement line as evidence. Contact the number or name shown and ask your sales staff whether a customer mentioned paying. If the payer stays unknown after a set period, ask your accountant how to treat it, since the sender may still request a reversal.
- Why do duplicate transactions appear in accounting records?
Beyond the manual causes covered under duplicate entries, duplicates often come from systems. Importing the same statement twice, syncing sales from a point-of-sale device and also entering them by hand or a device that syncs late can each create a second copy. Checking for repeated transaction codes after every import catches these.
- How should payment reversals be recorded?
Record the reversal as a new entry on the date it happened and quote the original transaction code. Leave the original entry in place so the trail stays complete. If the reversed payment was already allocated to an invoice, the invoice goes back to unpaid.
- What causes differences between a bank statement and accounting records?
Apart from fees and timing, look for standing orders and loan repayments the bank took directly, bounced cheques, interest credits and foreign currency receipts converted at a different rate. These rarely appear in the books until someone reads the statement line by line.
- How should M-Pesa transaction charges be accounted for?
Record each charge as an expense in a separate ledger, such as bank and M-Pesa charges. Record the full amount against the customer or supplier and the charge on its own line. Keep the downloaded M-Pesa statement as your supporting record.
- How can businesses reduce payment reconciliation errors?
Cut the number of payment channels. One Paybill or Till and one bank account are far easier to track than several numbers. Never let staff accept business payments on personal phones, and train everyone who records money on the same written rules.
- Should every payment have an invoice or reference number?
Yes. A reference is the only reliable way to link money to a customer or supplier. In Kenya, it also matters for tax, because all persons in business are required to issue electronic tax invoices through eTIMS. Expenses without a valid electronic tax invoice cannot be claimed.
