Receipting used to be a housekeeping task. A parent paid, someone wrote a receipt, the book went in a drawer, and it mattered only if there was a dispute.
That is no longer the whole story. Records that were previously an internal convenience are now the evidence a school relies on when an auditor or the Kenya Revenue Authority asks a question, and the schools that find this stressful are almost always the ones whose records live in more than one place.
This guide is about getting receipting into a state where compliance stops being an annual scramble — without adding work for the bursar.
Read this first. Tax obligations differ by institution and change over time. Nothing here is tax advice. Confirm what applies to your school with KRA directly or with your own auditor, and treat any vendor's summary of the rules — including ours — as a starting point rather than an authority.
Where schools actually come unstuck
The problem is rarely dishonesty, and it is rarely one big error. It is fragmentation. In a typical school with manual or partly manual finance, the record of a single term's income can be spread across:
- a receipt book at the front office
- an M-Pesa statement downloaded monthly
- a bank statement reconciled separately
- a spreadsheet the bursar maintains
- and a set of WhatsApp messages where a parent sent proof of payment
Every one of those is defensible on its own. Together they are almost impossible to reconcile into a single, consistent account of what the school received — especially months later, when the person who knew the context has moved on.
The symptoms are familiar: figures that do not match between reports, receipts that cannot be produced on request, and a finance team that spends the weeks before an audit reconstructing rather than reporting.
What eTIMS changes
eTIMS is KRA's electronic Tax Invoice Management System. The direction of travel is clear enough: invoices and receipts move from paper and local spreadsheets into a system where they are transmitted electronically and can be verified.
For a school, the practical implication is not really about the technology. It is that the receipt has to be generated by the transaction rather than typed afterwards. Once receipting is a by-product of the payment, transmission becomes automatic and the reconstruction problem disappears. Where receipting is a separate manual step, no amount of integration will save you, because the gap opens before the software is ever involved.
The receipting discipline that holds up
Whatever system you use, these five habits are what make records defensible:
- One receipt per payment, generated automatically. No manual issuing, no second book for exceptional cases.
- One place for all channels. M-Pesa, bank, cheque and cash post into the same ledger. If a channel has its own spreadsheet, that spreadsheet is your weak point.
- Searchable by learner. You should be able to produce every receipt for one admission number in seconds, without knowing the date.
- Corrections are visible, not silent. Reversals and repostings stay in the audit trail. A record that can be quietly edited is not evidence.
- Daily, not termly. Reconcile every day. An exception found the same morning takes two minutes; the same exception found in November takes an afternoon of detective work.
The daily habit is the one schools skip and the one that does most of the work. Our guide on collecting fees via M-Pesa Paybill covers what that daily routine looks like in practice.
Reports you should be able to produce on demand
A useful test of whether your records are in order: can you produce each of these today, without preparation?
| Report | Why it is asked for |
|---|---|
| Receipted income for a period | The base figure everything else reconciles against |
| Income by channel | Shows M-Pesa, bank and cash agree with their own statements |
| All receipts for one learner | Settles a parent dispute in one step |
| Invoiced vs receipted | Shows what was billed against what actually came in |
| Reversals and adjustments | Demonstrates corrections were recorded, not hidden |
| Expenditure by votehead | Connects income to how it was spent — see the budgeting guide |
If any of those takes more than a few minutes, that is the gap to close — and it will be the same gap that hurts at audit.
How Mzizi handles it
Mzizi generates the receipt when the payment is recorded, whichever channel it arrived on, and keeps M-Pesa, bank, cheque and cash in one ledger against the learner's account. Reversals and corrections stay in the audit trail. The finance reports above are standard rather than custom work, and the system supports direct eTIMS submission so receipts do not have to be re-entered anywhere else.
What it will not do is fix records that were never captured. If a term's payments were taken at the gate and written in a book, the reconstruction still has to happen once. The point of getting this right is that it only has to happen once.
More detail on the finance side is on the school ERP page and the M-Pesa fee collection page.