AWRA OpsHub Search

School ERP in Kenya: A Buyer's Guide for Bursars & Directors (2026)

A buyer's guide for directors and bursars — what school operations software must handle in Kenya: fees reconciliation, term-cycle procurement, boarding stores, staff payroll, and the asset register the board keeps asking about.

Schools & Education Washingtone Aura 9 min read

A school is three businesses wearing one uniform: a service business that bills fees and must collect them, a logistics operation that feeds and supplies hundreds of people on a term calendar, and an asset-heavy institution with labs, buses, dormitories, and kitchens to maintain. Most "school software" serves the first business — admissions, exams, sometimes fee invoices — and leaves the bursar running the other two on exercise books.

This guide is about those other two businesses: the operations side, where most of a school's money actually moves and most of it leaks.

Where school money actually leaks

  • The store. Rice, beans, cooking oil, detergent — boarding consumables bought by the lorry and issued by the cup, with no stock card between the two.
  • Term-start procurement. Everything is urgent in the first week of term, so quotations are theatre and prices are whatever the regular supplier says.
  • Fees that almost reconcile. M-Pesa here, three bank accounts there, cash at the office — and a bursar spending evenings matching narrations to student names.
  • Assets without custody. Lab equipment, sports gear, kitchen appliances — issued to departments, returned never, replaced annually.
  • Casual wages. Groundsmen, cooks, term-time staff paid in cash with records that would not survive one KRA question.

The capability checklist

1. Stores and consumables control

The school store needs real inventory: receipts against purchase orders, daily issues to the kitchen against expected consumption per student count, and stock counts that make the storekeeper's numbers public. A boarding school that starts measuring kitchen issues per student-day typically finds 10–20% of consumable spend was evaporating.

2. Procurement on the term calendar

Term dates are known years ahead — there is no excuse for emergency buying in week one. The system should hold procurement plans tied to the calendar, run real quotations for the big term contracts (food supply, transport, uniforms), and enforce approval thresholds so the deputy's signature means something. Our procurement policy template adapts directly to school boards.

3. Fees reconciliation

Invoicing per student per term, payments arriving by M-Pesa, bank, and cash — matched to students automatically, with arrears visible per class and per family. The full discipline is in our fees reconciliation guide.

4. Asset registers with custodians

Every microscope, bus, and cooker registered with a named custodian and location — the discipline in our school asset register guide — so the January question "where are the lab thermometers?" has an answer other than a shrug.

5. Payroll with statutory

Teachers on payroll, support staff, and term-time casuals — PAYE, NSSF, SHIF, and housing levy computed on current rules, with casuals paid through proper records instead of envelope arithmetic.

Questions for any vendor

Make them show, not tell

  • A term's consumables: PO → delivery → store → daily kitchen issues → variance report.
  • A fee payment arriving by M-Pesa and matching to the right student automatically.
  • Arrears by class, by stream, and by family — on one screen.
  • An asset issued to the science department, verified physically, and traced after a staff exit.
  • A casual worker paid for eight days with PAYE handled.
  • The board report: term spend vs budget, store variances, arrears — generated, not typed.

Then apply the same commercial diligence as any Kenyan institution buying software: the 10 provider questions and the three-year cost math. For how AWRA answers all of this, see ERP for schools in Kenya.

Bring one term's chaos to a demo

One store, one fee stream, one asset room — see them run governed for a full term cycle.

See AWRA for schools

Frequently asked questions

We already have a school management system for exams and admissions. Does this replace it?

Not necessarily — academic systems and operations systems solve different problems and often coexist. AWRA governs the money-and-materials side: stores, procurement, fees reconciliation, assets, payroll. If your academic system already does fee invoicing well, start with stores and procurement, where the leakage is.

How big does a school need to be for this to pay off?

The trigger is boarding or scale: a 300-student boarding school moves more consumables than most shops move stock. Day schools with significant assets, staff payroll, and multi-stream fee collection also recover the cost quickly — typically from store variance alone.

Can parents pay by M-Pesa directly?

Yes — payments to the school's till or paybill reconcile against student invoices, with the matching automated and exceptions listed for the bursar rather than the bursar doing all the matching by hand.

Who in the school runs the system day to day?

The bursar and storekeeper are the primary users; the principal and board get dashboards and reports. Role-based access keeps the storekeeper in stores and the accounts clerk in fees — with every action attributed.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center