Staff Costs in a SACCO: Payroll, Allowances & the Wage Bill You Can Explain
Staff costs are the largest controllable expense in most SACCOs and the one members scrutinise hardest. Payroll that computes on date-effective rules, sitting allowances that survive questioning, and the difference between a wage bill and a wage bill you can explain.
In a SACCO the wage bill sits in an unusual position. It is the largest controllable cost, it is paid from members' money, and it is discussed at a meeting attended by the people whose money it is. That combination means staff costs need to be not merely correct but explainable — and the two are genuinely different standards.
A payroll can be entirely accurate and still fail at an AGM, because "we paid what the contracts say" is an assertion. What answers a question is a breakdown showing where the cost sits, what changed since last year, and why.
Get the statutory part right and stop discussing it
PAYE, NSSF, SHIF and the housing levy are the mechanical part of Kenyan payroll and the part that consumes disproportionate attention when it is handled badly. The single most useful property of a payroll system here is not the arithmetic — it is that the arithmetic is date-effective.
Statutory rates change. A payslip from before a change must continue to compute on the rules that applied then, otherwise reopening a historical payslip silently rewrites it, and every P9 and reconciliation built on it becomes unreliable. Rules held as versioned, date-effective sets are what makes a historical payslip reproducible — which is exactly what an auditor tests.
The demonstration worth asking any vendor for
Open a payslip from before the last statutory rate change and show it computing on the old rules. It takes thirty seconds and it separates systems that store payroll results from systems that can reproduce them. We state no rates or bands anywhere here — confirm current rates with KRA and your adviser.
One boundary to be plain about: there is no iTax, NSSF or SHA portal submission. The computation, the payslips and the P9 certificates are produced; filing remains your process. Kenya is the one market where statutory payroll is turnkey in this product, and even here the submission is not. The full treatment is in PAYE, NSSF, SHIF and housing levy.
Allowances are where the scrutiny lands
Basic salaries rarely cause trouble at an AGM. Sitting allowances, per diems, travel reimbursement and honoraria do — partly because they are visible, partly because they attach to committee members, and partly because they are frequently the least documented payments a SACCO makes.
| Payment | The question asked | What has to exist beforehand |
|---|---|---|
| Sitting allowance | How many meetings, at what rate, approved by whom? | An attendance record, and a rate set by a body with authority to set it |
| Per diem and travel | Was the travel necessary and did it happen? | An authorisation before travel and evidence after |
| Honoraria | On what basis was this determined? | A decision recorded at the time, by a body other than the recipient |
| Overtime | Was it approved before or after it was worked? | Approved records tied to specific dates |
The common thread is that each needs a record created before or during the event rather than at payment. A sitting allowance supported by an attendance register is unremarkable. The same allowance supported by a schedule prepared at payroll time is a target, however honest it is.
A sitting allowance backed by an attendance register is unremarkable. The same payment, supported by a schedule assembled on payroll day, is a target — regardless of whether every meeting happened.
Present the wage bill the way it will be questioned
Staff costs broken down before anybody has to ask
Illustrative, in KES. The 18% headline invites a difficult discussion; the four lines beneath it close it. Every one of those drivers is a decision that was already made and approved — the failure is presenting the total without them, which converts approved decisions into apparent drift.
Cost per branch, not just per SACCO
A SACCO operating several branches needs staff cost attributable to each, and this is where most fall back on estimates. Without it, the question of whether a branch justifies itself cannot be answered — and branch expansion is one of the decisions members most often question.
Attributing staff cost by branch or department turns "the new branch has increased costs" into "the new branch costs 3.8 million a year and has brought in this much", which is a discussion with an answer in it. It requires only that employees carry a department or location and that the payroll analysis groups by it.
Payroll is not an ordinary expense
Two controls matter more here than for other spending, because payroll is recurring, large, and processed by a small number of people.
-
Preparation and approval are separate permissions
Whoever prepares the run does not approve it. This is the single most important payroll control and it is a permission setting rather than a policy statement.
-
Review the change list, not the payroll
Nobody usefully reviews four hundred payslips. What is reviewable is what changed since last month — new starters, leavers, changed compensation, unusual allowances. That list is short and it is where errors live.
-
Reconcile before the money moves
Gross, deductions and net against the previous period, with the differences explained. Five minutes, and it catches the error that would otherwise be found by an employee.
-
Lock the period once paid
A payroll period that remains editable after payment is a reconciliation that can silently stop being true.
What we do and do not do
What AWRA OpsHub does today
- Kenyan statutory payroll — PAYE, NSSF, SHIF and housing levy computed on date-effective, versioned rule sets.
- Payslips and P9 certificates produced from those computations.
- Configurable pay components for allowances, so sitting allowances and honoraria are named lines rather than lump sums.
- Attendance, leave and approved overtime feeding the run as inputs rather than typed figures.
- Separate preparation and approval permissions, with the payroll run lockable once complete.
- Employee records with compensation history, by department or location, so cost per branch is derivable.
What it does not do
- No iTax, NSSF or SHA submission. Filing remains your process; the computation and the certificates are ours.
- No sitting-allowance or meeting-attendance module. Attendance at committee meetings is your record; the payment is a pay component.
- No staff loan or advance ledger. SACCO staff loans, where they exist, are handled in your core system, not as a payroll object here.
- No board or committee remuneration governance. Who may set what rate is a governance question the system records the outcome of, not one it enforces.
The third line matters for SACCOs specifically, since staff frequently hold member loans with their own employer. Those live in core banking; if a deduction flows to payroll, it arrives as a component you enter rather than as an integrated balance.
Our take
Keep preparation and approval in different hands, review the change list rather than the payroll, and make sure every allowance has a record created before payment rather than at payment. Then present the wage bill as four drivers instead of one total — the increase members would have questioned turns out to be decisions they already approved.
See payroll in AWRA OpsHub
Date-effective statutory rules, payslips and P9s, configurable allowance components, approval separation and lockable runs.
Explore payrollFrequently asked questions
Does the system file our PAYE and statutory returns?
No. There is no iTax, NSSF or SHA portal submission — the computation, the payslips and the P9 certificates are produced here and filing remains your process. Kenya is the one market where we claim turnkey statutory payroll, and even here that claim stops at the submission. Any vendor telling you filing is automated is worth questioning closely about exactly which portal and exactly how.
What should we check before approving a payroll run?
The change list rather than the payroll itself. Nobody usefully reviews four hundred payslips, but new starters, leavers, changed compensation and unusual allowances is a short list where the errors actually live. Then reconcile gross, deductions and net against the previous period and explain the differences before the money moves — five minutes, and it catches what an employee would otherwise find for you.
How do we justify sitting allowances at an AGM?
With an attendance record created at the meetings and a rate set by a body with the authority to set it, both existing before payment. The payment itself is unremarkable when that evidence exists and looks like a target when the supporting schedule was assembled on payroll day — regardless of whether every meeting genuinely happened. There is no attendance module for committee meetings, so this is a register you keep.
Can we see staff cost per branch?
Yes, provided employees carry a department or location, which is what lets payroll analysis group by it. This matters more in a SACCO than in most organizations because branch expansion is one of the decisions members question hardest, and "the branch costs this much and brings in that much" is a discussion with an answer in it, while "costs have gone up since we opened it" is not.
How are staff loans from the SACCO handled?
In your core banking system, where the member account lives — there is no staff loan or advance ledger here. Where a repayment is deducted through payroll, it arrives as a pay component you enter rather than as an integrated balance that reconciles itself. Keep the authoritative balance in one place and treat the payroll deduction as an instruction from it, not as a second record of the same debt.
