What a Kenyan SACCO actually needs from a core system

A practical checklist for Kenyan SACCO boards: one member ledger, FOSA and BOSA, loans, M-Pesa, USSD, and SASRA-ready reporting — not a generic ERP demo.

Most SACCO boards we sit with already have software. The pain is rarely “we have no system.” It is that members live in one place, loans in another, the M-Pesa paybill in a workbook, and SASRA season is spent reconstructing the year.

If you are choosing or replacing a core in Kenya, start from how a society actually runs — cashiers on Monday morning, credit on Wednesday, finance at month-end, the board at quarter-end — not from a vendor’s module list.

One member. One number. Every product.

A member should have one identity across shares, deposits, loans, dividends, and next of kin. When FOSA and BOSA drift apart, you get two balances, two names, and an auditor who does not trust either. Front office and back office can have different products. They cannot have different people.

Loans that match how Kenyan SACCOs lend

Guarantors, shares as security, check-off, top-ups, restructuring, and arrears that credit officers can work — not a generic bank origination flow. The committee still decides. The system should show exposure, collateral, and history without a side spreadsheet.

Channels members already use

Paybill collections should post to the same ledger the cashier sees. USSD balances and SMS loan alerts should read from that ledger, not from a second database someone updates on Fridays. If the channel and the core disagree, members will believe M-Pesa.

Controls the external auditor can walk

Maker-checker on sensitive postings, branch limits, role-based access, and an audit trail. SASRA-regulated deposit-taking SACCOs are held to a higher bar; even non-DT societies now get asked harder questions by members and county governments. A core that cannot export a clean trail will cost you more in the last two weeks of the year than it saved in licence fees.

A go-live you can phase

Big-bang cutovers fail in societies with branches and messy history. Ask the vendor how tellers keep working while you migrate products. Ask who sits on the floor in week one. Ask what happens to last year’s loan schedule. If the answer is a training PDF, keep looking.

Vecta Stream builds SACCO core around that list — members, FOSA and BOSA, loans, M-Pesa, USSD, SMS, and reporting — and we stay after go-live. If you want a walkthrough, see the product or write to us in Nairobi.