School Payroll in Kenya: Staff Records That Outlive the Bursar

Every school has one. A payroll spreadsheet that only one person can open without breaking it. The bursar built it over years, colour-coded the columns in a logic only she remembers, and buried the formulas three tabs deep. It works beautifully, right up until the morning she resigns, falls ill, or takes leave at the worst possible time. Then payday arrives and nobody can say with confidence what each of forty staff should be paid, or why.

This is not a small risk. Staff pay is the largest recurring cost most Kenyan schools carry, and it is the most legally exposed too: get a statutory deduction wrong and the liability sits with the employer, not the employee. Yet the whole operation often rests on one undocumented file and one person's memory.

This article is about fixing that without buying complexity you do not need: the staff record everything hangs on, the TSC and BOM distinction, leave you can actually track, payroll with the deductions a Kenyan employer must handle (named correctly), and why the record must outlive whoever runs it.

The spreadsheet only one person understands

The problem with the one-person spreadsheet is not that it is a spreadsheet. It is that it is a single point of failure wearing the costume of a system.

Think about what that file actually is. It holds salaries, allowances, deductions and bank details for your entire staff, and it lives on one laptop, in one head. There is no record of who changed what, so when a figure looks wrong you cannot tell a typo from a deliberate adjustment. Formulas rot silently: a copied cell reaches one row short, and a new teacher is quietly left off the run. When the person who built it goes, the knowledge goes too.

There is also no memory. A spreadsheet shows you this month, rarely what someone earned two years ago, when their contract was last renewed, or how much leave they have taken. The moment you need that history, for an audit or a dispute, you are reconstructing it from paper and guesswork. It can tell you a number today, but not who set it, when, or why.

Start with the staff record, not the payslip

The instinct is to think of payroll as a monthly calculation. It is better understood as the last step of something you should have been keeping all along: a complete, current record of every person the school employs.

A proper staff record holds more than a name and a salary. It holds personal and next-of-kin details, national ID and KRA PIN, the bank account or M-Pesa number pay is sent to, the role and department, the start date, the contract type, the agreed gross pay and any allowances, and the documents that back all of it. Teaching staff and support staff both, from the deputy to the groundsman.

Once that record exists and is trusted, payroll stops being a separate exercise: the monthly run simply reads from it. Nobody re-types a salary, because it lives in one place. The record is the source, and everything downstream draws from it rather than duplicating it.

This is where accuracy is won or lost. If the underlying record is right, payroll is arithmetic. If it is scattered across a contract file, a WhatsApp message and a bursar's memory, every payday is a small act of archaeology.

Two kinds of staff in the same staff room: TSC and BOM

Kenyan schools carry a distinction that trips up many payroll setups, because two people doing similar work can be paid by completely different masters.

Teachers employed by the Teachers Service Commission (TSC) are on the national government payroll: the school does not pay their salary, the TSC does. Board of Management (BOM) staff and support staff are employed and paid by the school itself. The same staff room can hold both, side by side, one paid centrally and one paid by the school.

Here is the trap. Even though the school does not pay TSC teachers, it still needs a full record for them: leave, duties, cover, contacts. But payroll must run only for the people the school actually pays. Blur the two and you invite two costly mistakes: paying someone the TSC already pays, or losing a BOM contract that quietly lapsed. Keep the employer of record explicit on every staff profile, so it is always obvious who pays whom.

The school is the record-keeper for all its staff, but the paymaster for only some of them. Mark the employer of record on every profile, and payroll can never pay the wrong person.

Leave you can actually track

Leave is where informal systems fail most quietly, because a mistake does not show up until two teachers are absent on the same day and there is nobody to take the class.

Annual, sick, maternity and paternity, compassionate, study: each kind of leave has its own rules, and each eats into cover. When balances live in a drawer or a head, staff cannot see what they have left, approvals happen by memory, and disputes cannot be settled because nothing was recorded. Term planning suffers too, because whoever builds the timetable has no reliable picture of who is available.

A shared leave record fixes the visible problem and a hidden one. Visibly, everyone sees current balances, pending requests, and who is out on any given day. Invisibly, leave connects to payroll: unpaid leave, or leave that affects an allowance, flows into the pay run rather than being forgotten at month end. The point is that "how many days do I have left?" has the same answer for the teacher, the head, and the payslip.

Payroll and the deductions a Kenyan employer must get right

This is the part with legal teeth. As an employer, a Kenyan school must deduct the correct statutory amounts from staff pay and remit them to the right body, on time. Getting the names and mechanics right matters, because each deduction has its own authority and its own deadline.

The main ones a school handles are:

• PAYE (Pay As You Earn): income tax deducted from salary and remitted to the Kenya Revenue Authority (KRA), calculated on graduated tax bands and personal relief set in law.
• NSSF (National Social Security Fund): a pension contribution with both an employee and an employer portion.
• SHIF (Social Health Insurance Fund): the health contribution administered by the Social Health Authority (SHA), which replaced the former NHIF. If your documents or software still say "NHIF", that is the field this now maps to.
• Affordable Housing Levy: a deduction from pay with a matching employer contribution, remitted to KRA.

Two honest cautions. First, the exact rates, bands and thresholds are set by law and have changed more than once in recent years, so this article does not quote figures: confirm the current ones with KRA, the SHA, and your accountant. Second, because the numbers move, the deductions must be configurable, not baked in. A payroll you cannot update when the law changes will be wrong the month after the next Finance Act.

You do not want software that knows the rates. You want software that lets you set them, and remembers what you set. Rates change by statute; the record of how you applied them is what protects the school in an audit.

Payslips that end the monthly argument

A payslip is not a courtesy. It is the document that turns "my pay is short" from an argument into a five-second check. A clear one shows gross pay, each allowance, every deduction on its own line, and the net figure that lands in the account. When a teacher can see exactly what PAYE, NSSF, SHIF and the housing levy took, the suspicion that someone is being shortchanged simply evaporates. Consistency matters as much as content: the same layout every month, on the same date, builds a quiet trust that is hard to win any other way.

There is a compliance dividend too. Kept properly, the run of payslips is the school's own evidence that it deducted and paid what it should, exactly what you want on hand if a question is ever raised.

Why the record must outlive the bursar

Come back to the bursar who resigns. The deepest reason to move off the one-person spreadsheet is not convenience. It is that staff and pay records are an institutional asset, and an institution cannot depend on one person's continued presence to know what it owes and to whom.

A record that outlives any individual gives you three things a personal file never can. Continuity: a new bursar inherits a working system on day one, not a mystery. An audit trail: changes are attributable and dated, so the school can always answer who changed a salary and when. And portability: the history belongs to the school, and can be exported on demand rather than trapped on a departed employee's laptop.

Staff data is also personal data. The same principle that governs learners' records applies to employees': the school, not a vendor and not a former staff member, is the controller of that data. Payroll history, contracts and bank details are exactly the kind of sensitive information a school is accountable for keeping safe and being able to retrieve.

Payroll is not a monthly task. It is the running record of the school's largest obligation. Build it so it survives resignations, illness, handovers and audits, because all four are certain to come.

Where Opero fits

Opero is a school operating system, and HR and payroll is one part of it rather than a bolt-on. Because it draws on the same people data as the rest of the school, a staff member's details are entered once and shared across the system, instead of being re-typed into a separate program.

In practice, staff records, leave tracking, and payroll with configurable statutory deductions live together, payslips come from the same record, and the whole history stays under the school's control and can be exported. It is the same backbone that connects the rest of a modern school's operations, and it follows the same principle as automated fee collection: Opero runs the system, and the school keeps its own data.

We do not pretend the software files your returns or replaces your accountant. It keeps the record complete, current, and yours, so payday is arithmetic on trusted numbers rather than a scramble to reconstruct them.

Key takeaways

• The risk in a payroll spreadsheet is not the spreadsheet, it is the single point of failure and the missing history behind it.
• Payroll should read from a complete staff record, not exist as a separate monthly calculation.
• Keep the TSC and BOM distinction explicit: the school records all staff but pays only some.
• Track leave in a shared record so balances, cover and pay stay in sync.
• Name the statutory deductions correctly (PAYE, NSSF, SHIF, housing levy), keep the rates configurable, and confirm current figures with KRA, the SHA and your accountant.
• Issue clear, consistent payslips, and build the record so it outlives whoever runs it.

Frequently asked questions

Is NHIF still deducted, or has it changed? The NHIF was replaced by the Social Health Insurance Fund (SHIF), administered by the Social Health Authority (SHA). If older documents or software still reference NHIF, SHIF is what now takes its place. Confirm the current rate and rules with the SHA, as they are set in law and have changed.

Do we run payroll for our TSC teachers? No. Teachers employed by the Teachers Service Commission are paid by the TSC, not the school. You still keep their records for leave, duties and contacts, but your school payroll runs only for the staff the school itself employs, such as BOM and support staff.

What happens to our payroll history if our bursar leaves? That is precisely the case a proper system is built for. When records live in the school's own system rather than a personal file, a new bursar inherits complete, dated history the school can export at any time.

See it on your own school's shape

The fastest way to judge whether this fits your school is to see your own staff structure inside it, TSC and BOM side by side, leave and deductions where they belong.

Book a demo and we will walk through staff records, leave and payroll on a setup that matches your school, then show you exactly how the record stays yours.