School OS runs the school office on one record per child — fees, students, certificates, compliance, academics, transport and parent communication — so nothing is typed twice and no two screens disagree. The fee office is live today, down to the till count at the end of the day; the rest is being built on the same foundation.
Live today: fees, receipts, concessions, late fees, refunds, reminders, day close, transfer certificates, APAAR readiness
Most school software is a dozen products in one login. School OS is one system: the student the fee office bills is the student the class teacher marks present and the one the transfer certificate is written for. What is live today is marked; the rest is on its way.
Fee structure, dues, the counter, receipts, concessions, late fees, refunds, reminders, day close with the till counted. Below in detail.
Admission, guardians, classes and sections, year-end promotion, leavers closed out, transfer and bonafide certificates; the staff register with every post and date. Admissions pipeline, staff attendance and payroll next.
The register of papers the school holds and when each lapses; the calendar of returns, challans and inspections — what is due, by when, and what was filed; APAAR readiness. UDISE+ returns and RTE claims next.
The morning register: mark the class, correct a mark, read the month; who is absent today and who is under 75%. Timetable, homework, exams and report cards — including the NEP holistic progress card — next, on the same student record.
Buses and their drivers from the staff register, routes and stops, which child rides which and since when; the driver's manifest, stop by stop, with a number beside every name. Boarding by trip next.
Printed fee reminders are live. WhatsApp and SMS through the school's own registered identity, online payment into the school's own account, and a parent app follow.
Not a spreadsheet with a login page. The fee structure, the counter and the ledger are one system, so they cannot disagree with each other.
Tuition monthly, computer fee quarterly, annual charges once, admission fee only in the year a child joins. Set it per class; the dues follow.
A student admitted in July is billed for nine months, not twelve. One who leaves in September is billed through September. No manual adjustment.
₹4,000 against ₹11,600 settles the oldest dues first. The remainder stays outstanding, exactly — and the receipt says what it covered.
Upload the student list you already keep. Every problem in the file is reported at once — before a single row is written.
The accountant collects. The principal reads. Only an administrator can change what a fee is or cancel a receipt.
Sibling discounts and scholarships are recorded as concessions, not quietly smaller fees — so you can always see what was given away.
Numbered in an unbroken series and printed on ordinary A4 paper from the office printer you already own. Amounts are computed once, on the server, so the paper and the ledger always agree.
These are the design choices behind that, not marketing claims.
Cancelling a receipt does not erase it. It stays, marked cancelled, alongside a matching correction on the ledger.
What a student owes is worked out from every charge and payment each time it is asked for. There is no stored total that can drift.
Every change is logged, and each entry is sealed against the one before it — so an altered record announces itself.
Each school is isolated inside the database itself, not merely filtered by the application. Backups run nightly to two separate providers.
When online payment arrives it will settle into the school's own merchant account. We are not in the middle of your collections.
Nightly to two independent providers, each verified by reading the backup back — and the restore has actually been practised, not just configured.
School OS is in active development and not yet generally available. This is what works today and what is still coming.
| Capability | Status |
|---|---|
| Students, guardians, classes, spreadsheet import, year-end promotion | Working |
| Staff register: teaching and non-teaching, posts, joining and leaving | Working |
| Fee structure, demand generation, concessions, late fees, one-off charges | Working |
| Counter: collection, part payments, receipts, cancellation, refunds | Working |
| Day close with the till counted, reports, exports, tamper-evident audit | Working |
| Defaulters list, printed fee reminders, and who was reminded when | Working |
| Leaver close-out, transfer and bonafide certificates | Working |
| APAAR readiness | Working |
| Compliance register and calendar: papers held, filings due, what was done | Working |
| UDISE+ return and RTE claims | Planned |
| Attendance: the daily register, the month grid, absentees and the 75% line | Working |
| Exams, report cards | Planned |
| Transport: buses, routes, stops, who rides which, the driver's manifest | Working |
| Boarding by trip | Planned |
| Online payment via the school's own gateway | Planned |
| Parent app, WhatsApp and SMS | Planned |
We are looking for a small number of schools to shape what gets built next. You get the software and a direct line to the person building it.