Case study · School Systems · 2026

The Sosera Group of Schools:
244 pupils, one digital fee ledger.

A Nairobi school running PlayGroup to Grade 6 was billing every pupil for fees they did not owe. Owldid rebuilt the whole session's ledger on its school system and reconciled 231 of 238 balances to the shilling.

Published 22 September 2026 · Owldid · 7 min read · Industry: Education · Location: Nairobi, Kenya

The Sosera Group of Schools is a private Nairobi school of 244 pupils across 11 classes, from PlayGroup through PP1 and PP2 to Grade 6 on the CBC curriculum. It was not running on paper — it was running on an ageing Smart School ERP, which is a harder problem, because a school trusts a system it can log into. Owldid moved it onto the Owldid school system during 2026 and rebuilt the fee ledger from the ground up.

The short version: Owldid migrated The Sosera Group of Schools — 244 pupils, 11 classes — off its old ERP onto the Owldid school management system, rebuilding 3,665 invoices and 4,873 payments for the 2026 session, keeping the original receipt number on 4,127 of those payments, and reconciling 231 of 238 pupil balances exactly against the old system before the school was asked to trust the new one.

244
Pupils, 11 classes migrated
3,665
Invoices rebuilt correctly
231/238
Balances reconciled exactly
4,127
Receipts keeping their old number

The problem: a system that billed every pupil for everything

Sosera's fees are banded. A Reception child, a Grade 3 child and a Grade 6 child sit in three different brackets, and each pays only their own. The old ERP had been charging every pupil all three brackets at once, two and three times over, producing a flat bill of KES 168,760 against children who owed a fraction of it. Nobody on the school side had done anything wrong: the system said that was the balance.

Three consequences followed, and they are the same three every school with a mis-billing system eventually gets:

  • No one could quote a balance with confidence. Statements had to be corrected by hand before a parent saw them, which meant the office, not the system, was the source of truth.
  • Arrears were unreadable. When the billed figure is wrong, the debt figure is wrong, and a term's collection target is guesswork.
  • The data could not simply be exported. The old system served its pupil and fee lists through a script that was never handed to the browser, so there was no export button and no tidy CSV to import. Every figure had to be read out of the running system and then checked back against it.

What "going digital" actually had to mean here

For a school that already has a computer system, digitising is not about buying software. It is about getting one ledger that the office, the parent and the head all read the same way — and proving it matches the money that has already been collected.

So the brief Owldid worked to was not "move the data across". It was: every pupil billed their own bracket and nothing else; every shilling already paid still present, under its own receipt number; and a balance the office can read aloud to a parent without checking a notebook first.

What Owldid did

  1. The roster first. 244 pupil records in 11 classes, with PP1 kept as the school actually runs it — split into BLUE, RED and YELLOW streams rather than flattened into one class to suit the software. Phantom and duplicate records were removed before a single shilling was touched.
  2. The fee structure rebuilt. Each grade band was defined once — school fee, meals, exam, and where they apply, transport and lunch as per-pupil assignments rather than blanket charges — so a pupil is billed their own bracket and only their own.
  3. The session ledger rebuilt line by line. 3,665 invoices and 4,873 payments for the 2026 session, itemised on the server so that every invoice can be opened and read rather than trusted.
  4. Receipt numbers carried across. 4,127 payment rows kept the receipt number the parent already holds on paper.
  5. Term 3 fed in and reconciled. When the school moved into Term 3, 794 bill lines were raised for 233 pupils at the correct Term 3 rates, then every pupil balance was compared against the old system, one by one.
  6. The timetable, too. 627 lesson slots for all 11 classes were transcribed from the school's scanned sheets so the week lives in the system rather than on a wall.

The reconciliation — the part that decides whether a school trusts you

The migration was not declared finished when the data moved. It was declared finished when the numbers agreed. Balance by balance, 231 of 238 pupils matched the old system exactly. The remaining seven were not quietly adjusted to make the report look clean — they were written into a check-list and handed to the bursar to rule on.

That pass also found something the school could not have seen on its own: 17 receipts that had been recorded in the old system, then deleted from it. They showed up as pupils whose balance was off by the exact value of a receipt. In a school of this size, that is the difference between a parent being chased for money they have already paid and a parent being left alone.

The rule Owldid migrates by: a difference you cannot explain is not rounded away, it is listed. A migration that hides seven mismatches to report "100%" is a migration the school finds out about in week four of the term, in front of a parent.

What the school runs on now

  • Per-pupil billing. Own-bracket fees, with transport and lunch assigned to the pupils actually on them and billed only to those pupils.
  • Receipts that survive an argument. Every counter payment prints one A5 receipt with a counterfoil — the school keeps half, the parent keeps half, and it carries the receipt number.
  • Statements per pupil, in the school's own crested ledger style, printable for a parent on the spot.
  • A term pointer the school owns. When it moves into a new term, unpaid arrears and any credit carry forward automatically instead of being re-typed.
  • The payment channel the school actually uses. Sosera banks its fees, so every payment shows and prints as Bank; M-Pesa Daraja is in the same system for schools that collect by Paybill.
  • Balances by SMS to parents through Africa's Talking, in bulk or one at a time, with the message editable before it goes.

What is not done yet — and why we are saying so

Attendance registers, exams, CBC strand and sub-strand grading and printed report cards ship in the same Owldid system, at no extra cost, and Sosera is not yet using them. The fee ledger was taken first on purpose: that is where the school's money and its risk were. Attendance and grading are phase two, and the timetable that phase needs is already loaded.

We would rather publish that than claim a school of 244 pupils switched everything on in a weekend. If a vendor tells you the whole school went digital in three weeks, ask them which module the bursar opened on the Monday.

What this costs, if your school needs the same thing

Owldid's school management system is sold as a monthly subscription: KES 9,999 per month for schools under 500 pupils, with no upfront licence and no setup fee. That figure is Owldid's own price for its own system — fees, attendance, exams, CBC reports, parent SMS and M-Pesa are all included rather than sold as modules. Migrating an existing school's ledger is quoted on what the old system will let us read out of it.

Related reading: School management software in Kenya (2026) · CBC report card templates · M-Pesa Daraja for school fees

Questions schools ask before they move

Can a Kenyan school change management systems without losing its fee history?

Yes. When Owldid moved The Sosera Group of Schools onto its school management system in 2026, it rebuilt 3,665 invoices and 4,873 payments for the session rather than starting the ledger from zero, and reconciled 231 of the school's 238 pupil balances to the exact shilling against the old system. The seven that did not match were listed for the bursar to rule on instead of being quietly adjusted.

What happens to old receipt numbers when a school migrates?

They should be carried, not reissued. In the Sosera migration Owldid kept the original receipt number on 4,127 payment rows, so a parent holding a paper receipt from the old system can still be found by that number in Owldid. Reconciliation also surfaced 17 receipts that no longer existed in the old system at all — money the school would otherwise have argued about.

How long does a school fee data migration take in Kenya?

Owldid's Sosera migration ran in stages across 2026 rather than as a single weekend cutover: the roster and classes first, then the fee structure, then the full session ledger, then a reconciliation pass at the start of Term 3. A school that can export clean data moves far faster; Sosera's old ERP could not be exported from, so every figure had to be read from the running system and checked back against it.

Does the Owldid school system handle attendance and CBC grading as well as fees?

Yes. Attendance registers, exams, CBC strand and sub-strand assessment and printed report cards are part of the same Owldid school system as the fee ledger, at no extra cost. At Sosera the fee ledger was deliberately taken first, because that is where the school's risk was; attendance and grading are the next phase rather than something already running.

How much does a school management system cost in Kenya?

Owldid's school management system is sold as a monthly subscription: KES 9,999 per month for schools under 500 pupils, with no upfront licence or setup fee. That is Owldid's own price for its own system, not a market average, and it includes fees, attendance, exams, CBC reports, parent SMS and M-Pesa.

Changing school systems — or stuck inside one that bills wrong?

The first question we will ask is not about features. It is whether your current system will let you read your own fee ledger back out of it. Send us a term's statements and we will tell you what a clean migration looks like.

Start a project → WhatsApp +254 113 333 522

← All case studies · Next case study: Bridgerose Academy →