The three moments that matter
Effective reminder schedules are built around three states, not one blast.
- Upcoming — a configurable number of days before the due date
- Pending — the day after the due date passes unpaid
- Overdue — repeating on a set cadence, capped so nobody is spammed
Send to the payer, not just the student
In school and coaching contexts the student is rarely the payer. Reminders should reach linked parent accounts as well, and the fee status should be visible in the parent portal alongside receipts, so a parent can confirm a payment landed instead of asking the office.
Idempotency: why duplicates happen
Naive reminder jobs re-send whenever they run. A correct implementation logs each reminder against the invoice and the reminder type, so a job that runs twice in a day still sends once. HTS-LMS keeps a reminder log for exactly this reason.
Make the receipt do the work
Every payment should produce a receipt the payer can keep, carrying your institute's contact details, and every student should have a statement showing what was billed, what was paid and what is open. Disputes end quickly when both sides can see the same document.
What to measure after a month
Track the share of invoices settled before the due date and the average days-to-payment. If the first number rises and the second falls, the schedule is right. If neither moves, your reminders are probably reaching the student and not the payer.
Frequently asked questions
- Can we control how often overdue reminders repeat?
- Yes. In HTS-LMS the cadence and the maximum number of overdue reminders are both configurable, along with how many days before the due date the upcoming notice goes out.
- Do reminders work for cash-paying families?
- Yes. The reminder is driven by the invoice's unpaid state, not by the payment method, and stops as soon as a payment is recorded against it.