SASRA Compliance for SACCOs: What Actually Needs to Be in Your Reports
The SACCO Societies Regulatory Authority exists to make sure a member's savings are exactly as safe as the SACCO says they are. That means SASRA cares less about how a SACCO keeps its books and more about whether the numbers in those books are true, current, and reconcilable — which is precisely where spreadsheet-based record-keeping tends to fall apart under scrutiny.
Deposit-taking vs. non-deposit-taking: the reporting gap
Non-deposit-taking SACCOs (BOSA — Back Office Service Activities only) file less frequently and with a narrower scope: member shares, savings, and loan books, largely on an annual and quarterly basis.
Deposit-taking SACCOs (those licensed to run FOSA — Front Office Service Activities, effectively operating like a bank) carry a materially heavier obligation: monthly prudential returns, capital adequacy ratios, liquidity ratios, and provisioning for non-performing loans — all of which assume the SACCO's ledger can produce an accurate trial balance on demand, not just at year-end.
What examiners actually check
- Member share capital and savings balances reconcile exactly to the general ledger — no "adjustment" entries that exist only to make two spreadsheets agree.
- Loan classification and provisioning follow the prescribed ageing categories (normal, watch, substandard, doubtful, loss) consistently, not by manual judgment case-by-case.
- Capital adequacy and liquidity ratios are calculated from live balances, not a snapshot that was accurate when it was pulled three weeks ago.
- Every material transaction — a large withdrawal, a loan write-off, a dividend declaration — has an audit trail showing who approved it and when.
Where spreadsheet-based SACCOs get exposed
A spreadsheet can hold the numbers. It can't enforce that a loan officer and a different approver signed off on a disbursement, or that a member's share balance was actually debited when a withdrawal was recorded elsewhere. That gap is invisible day-to-day and becomes very visible the moment an examiner asks for a reconciliation that a spreadsheet was never built to guarantee.
A proper core banking ledger closes that gap by design: every transaction — a deposit, a loan disbursement, a dividend run — posts to the same double-entry ledger the moment it happens, with maker-checker approval built into anything sensitive. SASRA return packs, CRB submission files, and member statements become an export of live data, not a rebuild project every reporting period.
See how Sacco Suite keeps every SASRA return a live export, not a rebuild.
Explore Sacco Suite