School fee management software built for how Indian schools actually bill
Most schools do not have a fee problem — they have a fee *reconciliation* problem. The structure lives in a spreadsheet, the concessions live in the correspondent's memory, the invoices live in a printed book, and nobody can answer "what is this family actually supposed to pay this year" without three phone calls.
SkoolBook's fee module makes the structure itself the source of truth: defined per grade, per academic year, with tuition, CGST and SGST, uniform, books, transport and other components modelled separately rather than collapsed into one number. Every invoice is derived from it, and every deviation from it is an approval with a name and a timestamp attached.
What you get
Structures per grade, per academic year
Tuition, CGST, SGST, uniform, books, transport and other fees are separate fields — not one lump sum. When the board changes next year, you version the structure instead of rewriting a spreadsheet.
Concessions become an audit trail, not a favour
A concession is requested against a specific invoice with a stated reason, routed to a finance approver, and applied only after an explicit decision. Who approved what, and why, stops being tribal knowledge.
Fee structures need approval before they go live
A draft structure is proposed, reviewed and approved or rejected. Nobody publishes a year's fees to every parent by accident.
Parents see their own invoices, and only their own
Every family gets the same view your office has, in the parent portal and the mobile app — which removes most of the phone calls that fee season generates.
Isolated per school by the database, not by a WHERE clause
Each school's data sits in its own Postgres schema with row-level security on top, so one school's finance data is structurally unable to appear in another's.
How it works
- 1
Define the structure
Set the components for each grade and academic year — tuition, GST, transport, books, uniform, other.
- 2
Send it for approval
The structure sits in draft until a finance approver signs off, so the published number is always a decision, not a typo.
- 3
Invoices derive automatically
Every student's invoice comes from their grade's approved structure, so the arithmetic is done once, not per family.
- 4
Handle exceptions on the record
Concession requests carry a reason and an approver. The exception is visible; it doesn't live in someone's head.
Frequently asked
Does SkoolBook handle GST on school fees?
Yes — CGST and SGST are first-class fields on every fee structure rather than something you calculate outside the system and paste in, so invoices and reports stay consistent with what was actually approved.
Can parents pay fees online through SkoolBook?
Online payment collection is on the roadmap and not yet live. Today SkoolBook is the system of record for what is owed, what was approved, and what has been marked paid — your existing collection method continues to work alongside it. We would rather tell you that up front than discover it during implementation.
Can we give a concession to one family without changing the grade's structure?
Yes. A concession is raised against that family's invoice and approved separately, leaving the grade's structure untouched and the exception fully traceable.
Can different branches have different fee structures?
Yes — structures are defined per branch as well as per grade and academic year, so a multi-branch school does not have to compromise on one shared number.