Preventing Discount Abuse: Keeping a School's Discount Policy Honest

A sibling discount policy is one specific case of a broader problem: almost every school ends up running several different discount types at once — staff, early-payment, scholarship, and the informal "let's work something out" arrangement a bursar grants under pressure — and each one is an opportunity for the real rate collected to drift away from the published rate, quietly and without anyone deciding it should. None of this requires dishonesty to happen; unchecked discretion does it on its own.

The discount types worth distinguishing

• Published, rule-based discounts — sibling tiers, a staff-children discount, an early-full-payment discount. These are the easy ones, because the rule is fixed and either a student qualifies or doesn't.
• Need-based waivers or scholarships — usually approved case by case, often for a specific term or session rather than indefinitely, and meant to be reviewed rather than carried forward automatically.
• Ad hoc arrangements — a bursar or admin granting a one-off reduction to retain a family that's struggling to pay, outside any published policy. These are the riskiest category precisely because they're informal by nature.

Why the ad hoc category quietly costs the most

A single discretionary discount looks harmless in isolation — a few thousand naira off one family's balance to keep a good relationship or avoid a difficult conversation. The problem is that these decisions rarely get reviewed in aggregate, so a school can reach the end of a term having given away a meaningful share of expected revenue through a series of individually reasonable-looking decisions that nobody added up. Worse, once one family knows an informal reduction is possible, word travels, and the exception quietly becomes an expectation other families start asking for too.

The same risk applies to staff discounts specifically if eligibility isn't re-checked: a staff member's children should stop qualifying the moment that staff member leaves, but if the discount was applied as a flag on the student rather than tied to the parent's current employment status, it can keep running by default long after it should have ended.

What a sound approval process looks like

• Any discount outside the published, rule-based tiers requires a named approver who isn't the same staff member recording the payment — separating who grants a discount from who processes the transaction it affects is the single biggest control against both abuse and simple mistakes.
• Every discretionary discount is logged with who approved it, when, and the stated reason — not because every reason needs to hold up to audit, but because a decision nobody has to write down is a decision nobody really made deliberately.
• Discretionary and need-based discounts have an explicit expiry (end of term, end of session) rather than running indefinitely by default — a waiver meant to help a family through one hard term shouldn't silently become a permanent fixture because no one revisited it.
• Staff and sibling eligibility re-evaluates automatically when the underlying fact changes (employment ends, a sibling withdraws), rather than relying on someone remembering to manually remove it.
• Periodically, someone outside day-to-day fee processing reviews the total discretionary discount given against the published policy, specifically to catch drift before it becomes a pattern rather than after.

Related questions