School fees, one ledger
The fee ledger your school actually reconciles.
Students, fee plans, invoices, receipts, discounts and defaulters in one book. Money is stored as whole paisa, never floats, and nothing financial is ever edited — a mistake is fixed with a reversing entry, so the history stays true.
We deploy it for your school and send one setup link. Nothing to install, no terminal.
01
Fee collection fails in the gaps between spreadsheets.
A register book, a fee-plan sheet, a receipts file and a WhatsApp group. Each is right on its own and none of them agree at month end, so the defaulters list is a guess and the term close takes a week.
Three records, no book
Receipts in one file, plans in another, discounts in a third. The real balance exists only in the bursar's head.
Discounts and fines drift
A concession applied twice, a fine waived verbally. With no audit trail both are absorbed silently.
Defaulters by memory
Who owes what by which due date is rebuilt by hand every month, so follow-up always starts late.
02
How a term actually runs
Set the plan once, collect against it all term, close the day and the term without rebuilding anything by hand.
Set the fee plan
Per class and term, with discounts, fines and due dates defined up front — not negotiated at the counter.
Collect and receipt
Cash, bank or partial. Every receipt is numbered, printed or sent, and lands on the student ledger immediately.
Close day and term
Day close balances the cash drawer, statements give each family their position, and the defaulter list is by due date.
03
What is in the box
Fee plans and invoices
Class, term, concessions and due dates generate the invoices instead of a clerk typing them.
Receipts for partial payment
Part payments, multiple modes and advance adjustments, each with its own numbered receipt.
Discounts and fines with approval
A concession or a waived fine is a decision with a name against it, not an edit.
Defaulter lists by due date
Who is overdue, by how much, since when — ready to send, not rebuilt by hand.
Year rollover and archive
Promotion with repeaters, closed years archived, balances carried with an audit trail.
Student import from Excel
Import the roster with row-level error reporting, so a bad row does not abort the file.
04
How it is sold
One installation per school, on your own server or ours, quoted by size. The floor is 1,000 students — below that a spreadsheet genuinely is cheaper.
Quoted per installation
One school, one instance, one book. No per-seat billing and no student-count surprises mid-term.
1,000-student floor
We quote per installation and will say so plainly if your roll is below the floor where this pays for itself.
Deployed for you
We stand up the instance and send a single link. Your team never sees a terminal.
05
Questions, answered.
Do we need someone technical to run it?
No. We deploy the instance and send one setup link. The only people who ever see the server are ours.
Where does the data live?
On your own box or on ours — one instance per school. It is not a shared multi-tenant account.
Can a mistake be corrected?
Yes, by reversing entry. Nothing financial is ever edited or deleted, which is what makes the audit trail worth having.
Does it handle mid-term fee changes?
Yes. A revised plan is applied going forward and the ledger keeps the history of what was charged before.
Can receptionists take payments without seeing everything?
Roles are enforced on the server, not just hidden in the interface. A receptionist can receipt without touching reports.
See your own term in it.
Send us one class, one term and the fee plan. We will load it into a demo instance and show you the close.