SACCO Management System in Kenya: What SASRA Returns Need

It is the 12th, Form 4 is due at SASRA on the 15th, and somebody in finance is rebuilding the loan aging in Excel from a ledger export because the classification report the SACCO management system prints does not agree with the balances. If that is how your quarter ends, the system is not finished, whatever its brochure says about SASRA reports.

The returns are where it shows, because each one is a computation over state the system has to have kept: every loan's arrears in two units, deposit balances at a Wednesday close, which borrowers sit on the board or the payroll. We read the rules the way a developer building that system has to, from the Sacco Societies (Deposit-Taking Sacco Business) Regulations, 2010, which SASRA still publishes as its deposit-taking regulations and cites on its 2026 licensing list, and from the return templates themselves. That list is the specification CloudSpinx, an ERP and infrastructure consultancy in Kenya, would hold any SACCO system to, including one we build.

What SASRA's returns ask the system for

A deposit-taking SACCO files Forms 1, 2, 3, 6, 7 and 9 every month and adds Forms 4 and 5 at each quarter end, all due by the 15th of the following month. That is 80 dated returns a year, before the annual Form 8 and the newer templates on SASRA's forms page, among them 2B, 4B and the quarterly complaints Forms 11 and 12. Forms 1 to 8 each end in a declaration signed by an authorizing officer and a countersigning officer, and SASRA's 2026 list licenses 176 SACCOs to take deposits.

The ratios behind Forms 1 and 2 are hard floors. Regulation 9 wants core capital of at least KES 10 million, at least 10% of total assets and at least 8% of total deposits, and institutional capital of at least 8% of total assets. Regulation 13 wants 15% of savings deposits and short-term liabilities held in liquid assets. Miss capital adequacy and regulation 12 lets SASRA suspend lending and stop the SACCO taking deposits, so a ratio the system computes wrongly in the flattering direction is the expensive kind of bug.

Form 9 carries a timing gap worth knowing. The template's notes describe a monthly report by the 15th. The regulation as SASRA publishes it is stricter: notify the Authority of every board approval of a loan to a director or employee within fourteen days of that approval. A system that flags insider borrowers when the loan is approved serves both.

A SASRA loan classification runs on two clocks

Regulation 41 gives every arrears class, watch to loss, two tests, joined by "or". Here are watch and substandard as SASRA publishes them:

(b) Watch loans, being loans whose principal or interest have remained un-paid
    for one day to thirty days or where one installment is outstanding;
(c) Substandard loan, being loans not adequately protected by the current
    repayment capacity and the principal or interest have remained un-paid
    between thirty one to one eighty days or where two to six installments
    have remained outstanding;

Doubtful and loss follow the same pattern: 181 to 360 days or seven to twelve installments, then more than 360 days or more than twelve. Regulation 44 sets the loan loss provision at 1%, 5%, 25%, 50% and 100% from performing down to loss.

On a loan repaid monthly the two tests land within days of each other, because an installment is a month. On a loan repaid weekly they come apart in the first week. Other frequencies split them too: fortnightly and daily the same way, quarterly the other way, with the days test reaching substandard on day 31 while the second installment is still two months off.

Count the first missed installment as day 0. On day 7 the second installment falls due unpaid: by days the loan is watch (5%), by installments it is substandard (25%). On day 84 the thirteenth falls due: by days it is still substandard (25%), by installments it is loss (100%). On a KES 100,000 balance that is a provision of KES 25,000 or KES 100,000, before the discounted value of any security, which Form 4's instructions deduct from substandard and worse.

The regulation does not say which test wins when they disagree. On our reading that leaves it to the credit policy, written down before the auditor asks, and either way the system has to count both. One that stores only days in arrears cannot apply the installment test without rebuilding it from the repayment schedule, and the gap stays invisible until somebody checks a weekly product by hand. If you are not sure which way yours classes a weekly loan two installments behind, ask whoever runs it, or send us the loan products and their repayment frequencies on WhatsApp at +254 713 403 044 and we will tell you where each one lands under both tests.

More of regulations 40 to 43 ends up as code. A missed interest payment makes the entire principal delinquent (regulation 40). Interest on substandard, doubtful and loss loans is suspended and may not be booked as income, and accrued interest across the whole portfolio may not exceed thirty days of its earnings (regulation 42). A restructured loan may be reclassified once it has performed for six months or made six installments, and no loan may be restructured more than once in its life, so the restructure count is a field and Form 4 reports those loans in five rows of their own. Collateral needs a register and a revaluation every three years (regulation 43).

Liquidity is counted on Wednesdays

Regulation 14 tells a SACCO to "calculate the average monthly balance of its deposits and borrowings at the close of business on every Wednesday of each week", and when the Wednesday is a public holiday, on the Tuesday before. Form 2, the monthly return under the same regulation, sets net liquid assets against short-term liabilities and prints the gap to the 15% floor.

That turns Wednesday's close into an event. Either the system snapshots the balances when the day closes, or it rebuilds them later, and a rebuild from posting dates lets a back-dated entry made on Friday quietly change Wednesday. Take the snapshot, or keep entry timestamps and rebuild the books as they stood at the close.

SASRA's return-forms page also carries Form 2B, a consolidated daily liquidity report: opening balances, the day's receipts and payments, mobile money as its own line, and BOSA and FOSA deposits split, with closing balances over total deposits and over FOSA deposits. The 2010 text never names a daily return. Regulation 14(3) lets the Authority require other information it needs to evaluate compliance with the liquidity requirements, which on our reading is the power a daily form rests on. A system that can produce it on any morning is the safe build.

What a loan has to carry from the day it is approved

Some of the returns cannot be produced later, however good the reporting layer, because the data was never captured. Form 4B, the sectoral lending return, sorts loans and advances under SASRA's sector classification into 8 sectors and 67 activity codes, from tea and dairy farming to school fees and burial expenses. Coding every loan by hand at filing time is a guess dressed as data, so the code goes on the application. The insider flag, the restructure count and the collateral's valuation date are the same: captured when they happen, or rebuilt in a spreadsheet every quarter.

Deposits have their own. Form 3 counts accounts and balances in five bands, from under KES 50,000 to over KES 1,000,000, across non-withdrawable, savings and term deposits, with accrued interest. An account with no transaction for six months is dormant and goes into a separate accounting record, and after five years without contact the funds may be deemed abandoned (regulation 27).

The backup rule was written for a fireproof safe

Regulation 76 asks for a daily handover that a system has to be built to give: copy "all its critical information to a memory device and store in a fireproof safe on a daily basis", store weekly backups off-site, and keep a log of what was stored, where, when, who sent it and who ran the backup. Its list of critical records includes each member's shares, savings deposits and loan balances, investments, bank balances and a financial report listing the asset, liability and equity accounts. Regulation 78 adds a written disaster preparedness plan approved by the board, and regulation 49 requires a disaster recovery site.

None of that goes away when the system runs in a data center or at the vendor. On our reading the SACCO still owns the daily copy and the log, so the system needs an export of at least those records that a staff member can run every day, and the hosting or support contract has to say where the weekly off-site copy lives. These are SASRA's rules, not CBK's outsourcing guideline, which binds Banking Act institutions. That is where a SACCO's obligations overlap our disaster recovery and evidence work.

Testing a SACCO management system against the returns

Pick the last quarter end. Ask the system for Forms 1 to 5 as at that date, today, with nobody opening a spreadsheet, and set them beside what was filed. Then ask it for total deposits at the close of the last Wednesday of that quarter, and for the class of a weekly loan two installments behind. Every line that does not come straight out lands in one of three places: a report nobody built or built wrong, a field nobody captured, or a snapshot nobody kept. The first is a report to write or fix. The last two need the system changed, and the history behind them backfilled or rebuilt before the return can be trusted.

If every form already comes out of the ledger, the auditor has no findings on the returns and nobody opens Excel between the 1st and the 15th, keep the system you have. Returns alone are no reason to replace one that files them. Scope matters too: this covers deposit-taking SACCOs, and the societies SASRA authorizes for non-withdrawable deposits sit under the 2020 Regulations, which we did not read for this.

Where a gap is real, closing it on an open framework such as Odoo or ERPNext is the custom ERP work for SACCOs we offer, and it sits next to integrations like KRA eTIMS from inside the ERP. When the answer is a new system, we handle the move with you, with member, share, deposit and loan balances checked against the last filed returns before the old system goes dark.

To start, tell us on the ERP scoping form which of Forms 1 to 9 come straight from your system, which pass through Excel and which are typed, plus the system you run and roughly how many loans it carries, or send last quarter's Forms 1 to 5 on WhatsApp at +254 713 403 044. Keep Form 9 back, it names people. You get each return marked from the system, rebuilt by hand or missing, what closing each gap takes, and whether that is a report, an extension or a replacement. Reading the returns costs nothing and commits you to nothing.