M-Pesa collections that post to the same member ledger

Why Kenyan SACCO paybill collections fail when M-Pesa lives in a workbook. Post deposits, loan repayments, and shares to the same member ledger.

Members already pay how they live: a Safaricom paybill, sometimes Pochi, sometimes a bank slip at the branch. The failure mode we see most is not “we have no paybill.” It is that M-Pesa is a daily Excel, the core is a weekly upload, and credit officers cannot see who paid this morning.

Keep the paybill members already know

Changing a paybill to “launch digital” is how you lose collections for a month. A decent implementation keeps the shortcode, maps account references to member numbers, and posts into shares, deposits, or loan accounts according to rules the board has approved. The member should not have to learn a new number because you bought software.

Unallocated money is a governance problem

If the reference is wrong, the money still arrived. Parking it in a suspense account that nobody works is how you get angry members and a bloated asset you cannot explain. The core needs a queue: unmatched receipts, a maker-checker allocation, and an SMS that says we received it and we are matching it — not silence until Friday.

Loan repayments are not deposits

A collection that always hits savings will understate arrears and overstate liquidity. Product-level posting — loan, shares, ordinary savings, FOSA current — has to be explicit. If cashiers override it all day, your policy is theatre.

USSD and SMS belong on the same ledger

A balance on USSD that disagrees with the teller is worse than no USSD. Self-service is only safe when it reads the core, not a cache someone refreshes when they remember. The same is true of loan-due SMS: if the file is exported on Monday, you will nag people who paid on Tuesday.

Vecta Stream wires paybill, USSD, and SMS into SACCO core so cashiers, credit, and members are looking at the same person. Messaging · SACCO system · Talk to us.