Fee accounting where every rupee has a receipt and a ledger line
A fee register and an accounting system are not the same thing. Most school software gives you the first — a list of who owes what — and leaves the second to a spreadsheet the accountant reconciles by hand at the end of every month.
SkoolBook keeps the accounting side of fees as real records: a demand raised against a student, a receipt with a number that cannot skip, an allocation saying which demand the money settled, and a ledger line that is written once and never edited. The month-end reconciliation stops being a rebuild and becomes a read.
What you get
Fee heads and versioned structures
Tuition, transport, lab, uniform — each a head with its own tax treatment, priced by a structure version tied to a grade and an academic year. Changing next year's fees does not rewrite last year's.
Receipt numbers that cannot skip
Receipts are numbered from a per-branch sequence, so the series an auditor asks for is continuous. A cancelled receipt stays in the series, marked cancelled, rather than vanishing and leaving a hole.
An append-only student ledger
Every demand, payment, concession and refund is a ledger entry. Entries are never edited or deleted — a correction is a new entry — so the balance is always the sum of things that actually happened.
Cheques, DDs and post-dated instruments
An instrument has a lifecycle: received, deposited, cleared or bounced. A bounced cheque reopens the demand it was meant to settle rather than leaving it quietly marked paid.
Bank reconciliation against a real statement
Import the bank statement and match it to receipts. What matched, what did not, and what is still unexplained are three separate numbers, because folding them into one is how a reconciliation stops meaning anything.
Tally export, in Tally's own XML
Vouchers export as XML for import, or as CSV. Your accountant keeps working in the tool they already know instead of re-keying a month of receipts.
How it works
- 1
Define heads and structures
Set up fee heads once, then price them per grade per year as a structure version.
- 2
Assign students and generate demands
Put students on a structure and an instalment plan; demands are raised against them per instalment.
- 3
Collect and allocate
A receipt records the money; allocations say which demands it settled. Part payments are normal, not an edge case.
- 4
Handle what does not go smoothly
Concessions are approved rather than remembered; bounced cheques reopen their demand; refunds are their own approved record.
- 5
Reconcile and export
Match the bank statement, then hand your accountant a Tally-ready file.
Frequently asked
Can parents pay online through SkoolBook?
Not yet. The gateway path is built but no school is live on it, so we do not list online collection as something you can use today. Receipts currently record payments made by cash, cheque, DD or bank transfer.
Does it replace Tally?
No, and it is not trying to. It replaces the manual re-keying between your fee register and Tally. Vouchers export in Tally's own XML format so your accountant imports rather than retypes.
What happens when a cheque bounces?
The instrument is marked bounced and the demand it was allocated against reopens. The student's outstanding balance goes back up on its own, rather than staying settled because a receipt was issued.
Is the old fee register still there?
Yes. The v1 fee invoices keep working exactly as before and stay in step automatically — nothing a school already relies on was replaced or switched off.