A reminder nobody sees does not do the job of a reminder.
Most schools already know this from the accounts desk. The invoice was raised on time. The due date was clear. The notice went up in the portal. And yet, a week after the due date, the same staff members are working down a list of names with a phone in hand, explaining to parents that a payment was expected and repeating information that has been sitting on a screen the parent never opened.
That gap between a notice being sent and a notice being read is where most fee follow-up work is created.
Why the portal alone falls short
ScolaOS has run automated fee reminders for a while. Two scheduled jobs handle them: one fires three days before an invoice's due date, and another runs weekly for invoices that have gone overdue. Both draw on live fee data, so the amount, the invoice and the due date in the reminder are the real ones rather than a figure someone typed into a broadcast.
Until now, both delivered to one place: the in-app notification in the parent portal and parent app.
For parents who check the portal regularly, that works. The problem is that many do not. A parent logs in when there is a reason to, and a fee reminder is precisely the kind of thing that is meant to create the reason. Waiting for the parent to arrive at the notice inverts the whole point of a reminder.
The result is familiar. Reminders go out on schedule, the accounts team assumes parents have been informed, and then the follow-up calls start anyway. The automation was real; the reach was not.
What changed
The same reminder schedule now delivers over WhatsApp, SMS and email in addition to the in-app notification.
Nothing about the timing has changed. The pre-due reminder still goes three days before the due date, and the overdue reminder still runs weekly for unpaid invoices. What has changed is where the reminder lands: instead of only sitting in the portal until the parent visits, it arrives on channels that parents already watch through the day.
This is the same principle the platform already applies elsewhere. ScolaOS runs a full WhatsApp messaging stack, with managed message templates, event mappings, delivery webhooks that report status back, quotas and analytics. Email and SMS providers have been part of the platform for transactional sends such as one-time passwords and individual notices. Fee reminders now use that existing communication layer rather than living in a channel of their own.
How the reminders work
The mechanism is deliberately simple, because a fee reminder should not need a project to run.
- Invoices carry due dates. Fee invoices, due dates and outstanding amounts are already held against each student's record.
- The pre-due job runs. Three days before a due date, a reminder is generated for the invoices that are still unpaid.
- Overdue invoices are chased every seven days. The job checks daily, but a given invoice only generates a further reminder once a week: seven days after the due date, then fourteen, and so on while it stays unpaid. A family that pays within the first week is never chased.
- Delivery fans out. Each reminder is delivered as an in-app notification and, where the channel is configured and available, over WhatsApp, SMS and email.
Because the reminders are generated from live invoice data rather than an exported list, a parent who paid yesterday is not chased today. There is no separate list to maintain, and no export step for someone to forget.
What schools need in place
Each channel depends on a provider being configured, and availability depends on the school's plan. WhatsApp, SMS and email are separate services with separate accounts and separate costs, so a school that has only email configured will see reminders go out over email and the portal, and nothing more. Confirming what your plan covers is worth doing before you switch anything on.
WhatsApp deserves a specific note. Business messaging on WhatsApp operates under template approval and consent rules in most regions, which means outbound messages generally have to use an approved template and be sent to recipients who fall within the platform's messaging policy for your region. This is a WhatsApp requirement rather than a ScolaOS one, but it shapes how schools should plan the rollout. Schools should check their obligations under local rules and under WhatsApp's own business policy before relying on it as a primary channel.
What it means day to day
For the accounts team. Reminders reach parents on channels they actually check, so the follow-up call becomes the second step rather than the first. The defaulters view, with its filters for class, section and days overdue, remains the place to work from when a case genuinely needs a person. What shrinks is the volume of calls whose entire content is "your fee is due."
For parents. The notice arrives where the parent already is. A parent who has not opened the school portal in a fortnight still gets the reminder, with the invoice and the due date, rather than discovering the shortfall later.
For school leadership. Fee communication becomes consistent across the school. Every parent with an unpaid invoice gets the same reminder on the same schedule, rather than depending on whether a staff member got to that section of the list.
An illustrative scenario
A school raises term fee invoices in the first week of the term with a due date at the end of the month. Three days before the due date, the pre-due reminder goes out. Under the old behaviour it appeared in the portal, and the parents who log in regularly acted on it. The rest did not see it, and the accounts team spent the first two weeks of the following month calling families to explain a due date that had already passed.
With the same reminders now going out over WhatsApp, SMS and email as well, the notice reaches parents on the channel they use daily, and the calls that follow are the ones where there is genuinely something to discuss: a payment plan, a disputed line item, a family in difficulty.
(This scenario is illustrative and does not describe a specific customer.)
Using reminders well without overwhelming families
Automation makes it easy to send more messages than anyone wants to receive. A few points are worth holding to.
- Keep the schedule as it is. The pre-due and overdue reminders exist because they map to the two moments that matter. Adding noise around them trains parents to ignore the channel.
- Get invoice data right first. A reminder is only as good as the invoice behind it. Wrong amounts or stale due dates become wrong messages, delivered faster and to more people than before.
- Pick channels deliberately. Enabling every channel for every reminder is not automatically better. Consider which channels your parent community actually uses.
- Handle exceptions as people, not messages. Families on a payment arrangement or in genuine hardship need a conversation. Automated reminders should not be the school's whole approach to collection.
- Watch the delivery status. The WhatsApp stack reports delivery status back through webhooks. A channel that is silently failing is worse than one that was never enabled.
Frequently asked questions
When are fee reminders sent?
On two schedules. One reminder goes out three days before an invoice's due date. After the due date, an unpaid invoice generates a further reminder every seven days, so a family that settles within the first week is not chased at all.
Which channels do reminders go to?
The in-app notification in the parent portal and parent app, plus WhatsApp, SMS and email where those channels are configured and available on the school's plan.
Do we need anything set up before reminders go out over WhatsApp, SMS or email?
Yes. Each of those channels needs a provider configured, and availability depends on your plan. Without a configured provider for a channel, reminders continue to go to the parent portal.
Are there rules around sending fee reminders on WhatsApp?
There are. WhatsApp business messaging operates under template approval and consent rules in most regions, so outbound messages generally need to use an approved template and comply with WhatsApp's business policy. Schools should check what applies in their region before making WhatsApp their main reminder channel.
Do parents get reminded about invoices they have already paid?
No. Reminders are generated from live invoice data, so an invoice that has been settled does not generate a further reminder.
Does this replace the defaulters list?
No. The defaulters view, with its class, section and days-overdue filters, is still there for the cases that need a person. Reminders reduce how many of those cases start as a cold call.
Is this part of fee management or a separate module?
It is part of fee management. ScolaOS is Education Infrastructure as a Service, so reminders read from the same invoice records the fees module uses rather than from a copied list, and they send through the same communication stack the rest of the platform uses.
Conclusion
Automated reminders were never the hard part. Reach was.
Moving the existing fee reminder schedule onto WhatsApp, SMS and email closes the gap between a reminder being sent and a parent seeing it. The accounts team keeps the same schedule and the same fee data, and spends less of its week repeating a due date over the phone.
ScolaOS is built by Terra System Labs Pvt Ltd, which is ISO 27001:2022 compliant for information security and ISO 9001:2015 compliant for quality management, and is a Startup certified company. Fee and parent contact data is handled under the access controls described on the security page.
Want to see how this would run on your fee cycle? Book a demo, or look through the platform, apps and pricing pages in your own time.