Operations
The office work, done where the records already are.
Fees, staff, leave and communication all depend on knowing who is enrolled in which class. When that lives in the same system, most of the administration disappears rather than moving.
Fees
A fee structure is defined once per class and session — tuition, transport, laboratory, whatever the school charges — and invoices are generated from it. Because the structure knows the class and the class knows the student, nobody assembles a billing list.
Payments are taken at the counter or recorded against an online transfer. Each one produces a numbered receipt, updates the outstanding figure and appears in the day’s collection immediately. Part payments are allocated across invoices oldest first.
Outstanding is a live view, sorted by how long money has been owed, so a follow-up call goes to the right family rather than the whole class.
Staff
Staff records carry designation, department, contact details and joining date. Roles decide what each person can reach: eleven are defined for a school, from school administrator to driver, and each is a set of specific permissions rather than a level. A school can add its own.
Staff attendance can be marked from a device inside a geofence around the campus, with the decision made on the server against coordinates held in the database.
Communication
Notices go to an audience — everyone, a role, a class, a section — and appear in the portals of exactly those people. Internal mail runs between staff and families inside the system, so a conversation about a child stays on the record rather than on someone’s personal phone.
A school can connect its own mail server, so fee reminders and results arrive from the school’s address rather than ours.
A payment taken at 11:04 changes the outstanding figure at 11:04.
Fee setup
- Fee heads
- Structures per class and session
- Due dates
- Late fee rules
Billing
- Invoice generation
- Part payments
- Allocation across invoices
- Refunds
- Cancellations
Collection
- Counter collection
- Numbered receipts
- Daily collection view
- Outstanding by class
- Payment history
Staff
- Staff records
- Roles and permissions
- Staff attendance
- Geofenced check-in
- Leave approval
Communication
- Notices by audience
- Internal mailbox
- Your own SMTP server
Administration
- School profile
- Branding and colours
- Academic sessions
- Audit log
Next step
Ready to run your school on one platform?
Tell us how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. The demonstration follows that rather than a script, and we will be straightforward about the modules that are not built yet.
What a demonstration involves
- Thirty to forty minutes, on a call, with your screen or ours
- Roughly how many students and staff you have
- What you use today for fees and attendance
- Whether you run one campus or several
No obligation, and no pricing pressure on the first call. If SchoolOS is the wrong fit for your school we would rather say so then.