Designing a fee structure you will not have to unpick in January

Start with heads, not with totals

The most common structure in an Indian school is one number per class per term, with the breakdown living in a circular. It works until the first question arrives: a family paying only transport, a sibling on a tuition-only concession, an auditor asking how much of last year's collection was hostel income.

Split the fee into named heads from the start — tuition, admission, examination, transport, hostel, library, activity — even where every student in a class pays all of them. A head is not extra work; it is the unit that everything downstream reads.

• Reporting becomes possible: income by head, comparable across terms, tied to the accounts rather than assembled by hand.
• Partial billing becomes possible: a day scholar who takes the bus, a boarder who does not.
• Relief becomes precise: a concession applies to tuition without silently discounting the transport the school still has to pay for.
• Tax treatment differs by head — and a single blended number makes that impossible to represent honestly.

Categories beat exceptions

Every school has students who do not pay the standard amount: staff wards, siblings, RTE admissions, scholarship holders, a trustee's decision. There are two ways to represent them and only one of them survives.

The wrong way is to edit the individual invoice. The right way is to define the category once, price it once, and let the invoice be generated correctly — with genuinely individual decisions handled as an approved concession posted on top. The test is simple: if you cannot answer "how many students pay the sibling rate, and what did that cost us?" without opening invoices one by one, the exceptions are in the wrong place.

Instalments: a schedule, not a second ledger

Families ask to pay in parts, and schools reasonably agree. The trap is building the instalment plan as its own set of records, which immediately creates two versions of what is owed — and they diverge the first time somebody pays an odd amount, or pays twice, or pays late.

Keep one invoice as the truth and let the plan be a view over it: dated milestones whose covered, due and overdue states are derived from what the invoice has actually received. Then a part payment updates one number, the plan re-derives, and there is nothing to reconcile between the two.

Late fees you can defend

A late fee is a policy that gets applied thousands of times without a human looking, so it needs to be boring and bounded.

1. Choose flat or percentage, and write down which. A percentage on a large annual invoice compounds into a number no principal wants to defend in a meeting.
2. Give it a grace period. Payments cross weekends and bank holidays; a fine that lands on day one converts an administrative delay into a grievance.
3. Cap it. An uncapped daily fine on an unpaid term fee eventually exceeds the fee, at which point the school stops applying it and the ledger stops meaning anything.
4. Apply it as a line, once. A fine is an invoice line with its own reason, applied one time per rule per invoice — never a silently increased total, and never applied twice because a job ran again.
5. Preview before you commit. Fines are applied in batches. Seeing the list and the total before it lands is the difference between a policy and an incident.

How this works in Vidyapeeth360

A fee structure is built from heads, each carrying its own HSN/SAC and rate, and priced by class and category. Amounts are treated as inclusive of any tax that applies, so what the parent sees on the notice is what the parent pays; the split is back-computed for the records rather than added on top. Your school's own tax position stays a question for your adviser.

Invoices carry their heads as lines, with concessions posted as negative lines against them, so the invoice always shows both what was billed and what was relieved. Invoice and receipt numbers come from one atomic per-school register — never from counting existing rows, which collides the moment two are raised at once or one is cancelled. Voiding an invoice makes it financially inert rather than merely marked: it cannot be paid, and it stops counting towards outstanding.

Instalment plans are a derived planning aid over the invoice's own cumulative payments, not a second ledger — so a part payment cannot make the plan and the invoice disagree. Fines are configured as rules with a grace period and a cap, previewed as a list with its total, and applied as a reconciled invoice line, idempotent per rule per invoice.

Where a school bills monthly or quarterly, demand generation is an opt-in that raises the current period's invoices through the same path a manual invoice takes, keyed on the billing period so a re-run cannot double-bill a family. That is the whole feature: fee structures that generate correctly, instalments that derive, and fines that stay bounded.

If you are setting this up for the first time, spend the time on heads and categories. Instalments and fines are settings you can change in October; the shape of the bill is not.