Handling Outstanding Balances When a Student Withdraws or Graduates
A student withdraws or graduates partway through a term with an unpaid balance still outstanding, and the question of what to do with that invoice isn't as obvious as it first looks — it genuinely depends on the situation, and the wrong default (either auto-cancelling it or silently leaving it active) creates real problems either way.
Why this isn't a simple yes/no
Auto-cancelling an outstanding invoice the moment a student is marked withdrawn sounds tidy, but it isn't always correct — a family that owes money and is withdrawing specifically because they stopped paying shouldn't have that debt quietly erased. On the other hand, leaving every departing student's invoice active forever isn't right either — a student who genuinely completed the term and graduated normally, with a small final balance that's about to be settled anyway, doesn't need to stay flagged as a collections case indefinitely.
The honest answer is that this is a case-by-case decision, which means the system shouldn't make it automatically either way — it should surface the open balance clearly at the moment of withdrawal/graduation and let a human decide: cancel it (the school is writing it off or it was already resolved outside the normal flow) or leave it collectible (the school still intends to pursue it).
What to check before deciding
- Has any payment or credit already been applied to this invoice? If so, cancelling it outright can silently lose track of real money that moved — this should be flagged for manual review rather than cancelled automatically.
- Is the family's full payment history visible at the moment of the decision, not just this term's balance — a family with a strong payment history and a small final-term balance is a very different situation from one with a long pattern of non-payment.
- If the student has siblings, does their fee status (discount eligibility, family account linkage) need updating too, now that the roster has changed?
Reversing a mistake
Withdrawals and reactivations happen — a student marked withdrawn by mistake, or one who leaves and later returns to the same school. Whatever system handles this should be able to cleanly reverse a wrongly-cancelled invoice and reactivate a returning student's records without creating duplicate invoices for the same term, since a term/student pairing should only ever have one true invoice regardless of how many times status changes.
Related questions
Should a school automatically cancel a withdrawn student's unpaid invoice?
Not automatically — it depends on why the family is withdrawing and whether the school intends to pursue the balance. The safer default is surfacing the open invoice for a human decision rather than silently cancelling or silently leaving it active.
What if a payment was already applied before a student withdraws?
That invoice shouldn't be cancelled outright — it should be flagged for manual review, since cancelling it could lose track of real money that already moved against it.
Can a mistakenly withdrawn student be reactivated without losing their invoice history?
Yes, this should be a clean reversal — reactivating a student should restore or recompute their existing invoice for the current term rather than generating a fresh duplicate, since a student should only ever have one true invoice per term.