Skip to main content

Guide

School fee management: keeping billing and collection straight

Fee structures, invoices, receipts, concessions and the reports that tell you what is actually outstanding.

By The EDUTIG team at RNDSOLPublished Updated 7 min read

Fee collection is usually the first thing institutes digitize, and often the last thing they connect properly to real accounting. The result is a fee module that tells you who paid, but not whether your books actually balance.

Why “who paid” isn't enough

A fee collection log answers one question. A proper fee ledger answers several more: which account did this money post to, does this month's trial balance actually balance, and can you produce an audit-ready trail for a specific discount or waiver six months later. That difference matters most during external audits or when a parent disputes a balance.

What a well-built fee system needs

  • A hierarchical chart of accounts underneath fee collection, not a flat list of transactions.
  • Per-student fee ledgers that show the full history of invoices, payments, discounts, and dues for any single student on demand.
  • Automated invoicing tied to enrollment, so fee invoices generate from actual enrollment data instead of manual entry.
  • Bank reconciliation that matches imported bank statements against recorded vouchers, flagging variances instead of hiding them.
  • Budget versus actuals reporting, so department heads see overspending before it becomes a year-end surprise.
  • An approval trail on adjustments. Every discount, waiver, or correction should be traceable to who approved it and when.

Multi-branch institutes need one more layer

If your institute operates more than one campus, fee accounting needs to consolidate across branches while still supporting branch-level reporting and closing. Handling this in separate spreadsheets per branch is exactly the kind of manual reconciliation a proper system should eliminate. See our guide on multi-branch operations for what else changes at that scale.

Where EDUTIG stands on this

EDUTIG's fees and finance area covers the billing and collection side: fee structures, invoices for a class, section or selected students, receipts, concessions and reversals, plus collection, outstanding, defaulter ageing and per-student ledger reports. Expenses and financial reports sit alongside them.

What it is not is a double-entry accounting system. There is no general ledger, trial balance or bank reconciliation in EDUTIG, so most schools keep their accountant's software for statutory accounts and use EDUTIG for the fee and expense side. If a vendor tells you their fee module is also your accounting system, ask to see the trial balance.

FAQ

Common questions

Questions institutes ask when tightening up fee accounting.

What is the difference between a fee ledger and a collection log?

A collection log records who paid what. A fee ledger goes further: it keeps each student's billed amount, concessions, payments and outstanding balance together, so you can answer what a family owes without adding up receipts. EDUTIG keeps a per-student fee ledger of this kind.

Does a fee system replace our accounting software?

Usually not, and you should be careful with any vendor who says it does. Fee software handles billing and collection; statutory accounts need a general ledger, trial balance and bank reconciliation. EDUTIG covers the fee and expense side and reports on it, but it is not a double-entry accounting system, so most schools keep their accountant's software alongside it.

How do we keep concessions and discounts under control?

Decide who may approve a concession before you start, and record every one against the student rather than by adjusting the invoice amount. That way the outstanding figure and the reason for it stay visible, instead of a reduced bill with no explanation attached.

How often should we check fee figures?

Monthly at minimum, and weekly during a collection period. The longer a discrepancy sits, the harder it is to trace back to the receipt or adjustment that caused it.

Every module

Twelve areas, one set of records behind all of them.

Compare them all