Fee concessions, scholarships and sibling discounts
The standard fee structure is easy to automate. The exceptions are where disputes, leakage and audit trouble begin, and where good system design pays for itself.
Fees & Finance4 min readPublished
Key takeaways
- Exceptions, not the base fee, are where fee management usually breaks down — sibling discounts, staff concessions, scholarships and one-time waivers each need a rule, not a memory.
- Requesting and approving a concession should be two separate steps, with the reason and any documents recorded against it.
- Third-party receivables from sponsors and scholarship bodies need their own tracking so the money does not fall between accounts.
- A 'concession leakage' report — discounts lacking approval or documentation — is often the single most revealing view for management.
The usual types of exceptions
Ask a school accountant which part of fee management causes the most headaches, and the answer is rarely the base fee. It is the exceptions: the sibling who was promised a discount, the staff ward whose concession applies only to tuition, the scholar whose sponsor pays in two instalments, the family granted a one-time waiver by the principal in a hallway conversation.
Each exception is reasonable on its own. Collectively, they are a major source of inconsistency, disputes and unexplained gaps between what should have been collected and what was.
Most institutions handle several kinds:
- Sibling discounts, often on the second or later child
- Staff-ward concessions, sometimes a percentage of specific fee heads
- Merit or academic scholarships, linked to results or entrance performance
- Need-based assistance, granted after review
- Sports, arts or other talent-based concessions
- Early-payment or annual-payment discounts
- Sponsored or government-funded seats, where an outside party pays all or part of the fee
- One-time waivers, for a specific circumstance or a late fine
What goes wrong when exceptions are handled manually
- A discount is applied at the counter, with no record of who approved it or why
- The same family receives different concessions in different terms, without explanation
- A sibling link is missing, so the discount is missed or applied to the wrong child
- A concession applies to the wrong fee head, for example to a transport charge it was never meant to cover
- A scholarship ends, but the concession keeps being applied
- Sponsor payments arrive late and nobody tracks the balance owed by the sponsor
- At year end, the total value of concessions given is unknown
None of these are dishonest acts. They are what happens when policy lives in people's memories.
Design principles for handling exceptions well
1. Define concessions as rules, not one-off edits. Each type should have a name, an eligibility description, the fee heads it applies to, a percentage or fixed amount, and a validity period. When a student is assigned the concession, the system applies it consistently every time an invoice is generated.
2. Separate requesting from approving. The person who proposes a concession should not be the one who approves it. A simple two-step workflow, with the reason recorded and attachments where relevant, prevents casual discounts and protects staff from pressure at the counter.
3. Set limits and escalation. For example, the accountant may apply standard, pre-approved categories, while anything above a threshold goes to the principal or the trust. Thresholds are policy choices for each institution.
4. Keep a full audit trail. Every concession should show who requested it, who approved it, when, on what basis, and any documents attached. When a parent disputes a receipt months later, the answer is one click away.
5. Track third-party receivables. For sponsored seats and scholarships paid by outside bodies, record the expected amount, the parties owing it and the payments received, so the money does not fall between accounts.
6. Review validity automatically. Scholarships that depend on academic performance or attendance should flag for review at defined points, rather than continuing by default.
Reports every management team should see
- Total concession value per term, by category
- Concessions by approver
- Students with more than one concession stacked together
- Sponsored and scholarship receivables outstanding
- Concessions nearing expiry
- Difference between gross fee billed and net fee billed
A "concession leakage" report, showing discounts that lack approval or documentation, is often the most revealing view of all.
Be transparent with families
Show the concession clearly on the fee statement and receipt, with the gross fee, the concession and the net payable. Parents are more likely to trust a system that explains itself, and they raise fewer queries at the counter.
Takeaway
Fair, consistent concessions are a matter of policy and of process. When rules, approvals and records all live in one place, an institution can be generous where it wants to be, and still know exactly what that generosity costs.
See how configurable fee structures work in practice: explore online fee collection.
See this workflow in Pii Aura
Explore the matching module or book a guided ERP demo for your school, college, or institution group.