Finance & compliance
The money, and the paperwork the law wants
Fees invoiced and collected however a family can pay. Statements that reconcile themselves. Payroll with the statutory deductions worked out. And the privacy obligations of the Personal Data Protection Act, 2022 built into the product rather than added at the end.
Invoice the term, take the money any way it comes
One invoice per student per term, with the discounts and scholarships your school actually grants. Payment arrives by mobile money, bank transfer or cash at the office — and lands against the same invoice either way.
- Fee structures per class level, with sibling and staff discounts
- Instalment plans where a family needs one
- M-Pesa, Tigo Pesa, Airtel Money, CRDB and NMB
- A TRA-ready receipt for every payment, issued the same day
Payroll that already knows the rates
PAYE bands, NSSF, NHIF, WCF and SDL are computed from the salary you set — not from a spreadsheet a bursar maintains and nobody else can check. Every run is approval-gated, and every payslip is a record.
- PAYE, NSSF, NHIF, WCF and SDL from statutory rates
- Overtime, allowances and deductions per staff member
- Draft → approve → pay, with the approver named
- Payslips staff read in their own account
The rest of the finance office
What a bursar stops doing by hand
Bank reconciliation
Import an M-Pesa, CRDB or NMB statement and let it match itself against invoices. What doesn't match is a short list, not an afternoon.
Financial reports
Daily cash-up, collection rate, aged debtors and a term-on-term view — the numbers a board asks for, ready before they ask.
Parents pay from the phone
A parent with an outstanding balance can settle it from their own portal, and see the receipt appear against the invoice.
Every figure is traceable
Who invoiced, who discounted, who received, who approved — an audit trail that answers the question before an auditor asks it.
Privacy
Built for the Personal Data Protection Act, 2022
A school holds more sensitive data about children than almost any other organisation in a district. The obligations that come with that are in the product, not in a policy document.
Your data is isolated at the database
Every table enforces row-level security per institution. It is not a filter in application code that a bug can forget — the database itself refuses to return another school's rows.
People see only what their job needs
Nine role families with capability-level permissions, and a rule we hold to everywhere: if someone cannot use a thing, they do not see it. No teasing panels, no permission errors.
Data-subject requests have a queue and a clock
Access, correction, erasure, restriction and objection each have their statutory deadline tracked, and the request is worked in the product rather than in somebody's inbox.
Two-step verification where it matters
Enforced per institution, with recovery codes a head can reprint, and step-up checks on the actions that change money or permissions.
Ready to run your institution without the paperwork?
Register in minutes, or ask us for a guided walkthrough on your own data.