Automatic reminders for payment schedule
If the client has selected payment with a payment schedule in the booking or you have set it up manually, they will always be informed of this obligation in time -- automatically by the application. Reminders are sent as email notifications. Learn how to set up payment templates in the payment templates manual.
Reminder 1: Upcoming payment notification
Informs the client that a scheduled payment will be due on their programme booking in a few days (depending on the setup).
- The reminder must be enabled in Settings → Billing & Payments → Payment settings → Scheduled-payment notifications, where you can specify the number of days before the payment is created when the notification should be sent.

-
The notification before the payment is created is sent according to the formula: Due date - Number of days due - Number of days before payment creation
-
You can edit the text in Communication --> Message Templates, under the template titled: Upcoming Payment.
-
To communicate the date when the payment will be created, use the dynamic tag:
SCHEDULED_AT_DATE
Reminder 2: Payment created notification
Informs the client that a new scheduled payment has been created on their booking. The date when the payment is posted and the notification sent follows the formula: Due Date - Number of days due.
-
Set the payment due date in Settings → Billing & Payments → Payment settings → Payment acceptance policy, where you can specify the number of days.

-
Customize the text in Communication --> Message Templates, under the template named: New payment.
-
To communicate the due date, use the dynamic tag:
DUE_DATE
Reminder 3: Overdue payment notification
Informs the client that the booking has not been paid by the due date.
- It is sent on the due date if the booking is in an unpaid/partially paid status.
- Edit the text in Communication --> Message Templates, under the template titled: Missed payment.
- To communicate the due date, use the dynamic tag:
DUE_DATE
Understanding the three notification types
Clients often confuse these three notifications. Here is a clear distinction:
| Notification | When it is sent | Purpose | Template name |
|---|---|---|---|
| Upcoming payment | Before the debt is created (configurable days) | Informational — tells the client a payment will be due soon | Upcoming Payment |
| Payment created | When the instalment debt is posted | Action required — tells the client to pay | New Payment |
| Overdue payment | On or after the due date, if unpaid | Urgent — the payment is past due | Missed Payment |
Common confusion: "I already paid but got a reminder"
This happens when:
- The client paid before the debt was created (e.g., after receiving the "upcoming payment" notification).
- The payment was received by the bank but auto-pairing has not yet processed it (GoCardless syncs once daily; email-notification pairing is near real-time).
- The system sent the next scheduled notification before the payment was matched.
The client sees what looks like an overdue notice, but it was actually the "upcoming" or "payment created" notification for a future scheduled payment. The wording of these notifications should clearly distinguish them.
Notification timing
All payment notifications are processed in a nightly batch. This means:
- Notifications may arrive in the early morning hours (e.g., midnight to 6 AM).
- The send time is not configurable per programme or globally.
- If this timing causes client complaints, consider adding a note in your notification template explaining that the email was generated automatically overnight.
The "zeroth" notification (advance notice)
You can enable a notification that is sent before the first instalment is created. This gives the client advance notice that they will receive a payment request soon. It acts as a fourth touchpoint in addition to the three reminders above.
Enable this in Programme → Settings → the Price tile → Price and payment → Payment reminder settings.
These are on by default, and there are two ways to time them
Payment reminders do not have to be switched on. A new programme already has them, which is why a provider who configured nothing can still find clients being chased — including for a class that has not started.
Open the programme, go to Price and payment, scroll to the bottom, and use Change on the Payment reminders settings card.

Switching them off
Change the status of scenarios → Not activated. That is the off switch. (Delete on the card removes the whole configuration rather than pausing it.)
The two timings
The group is called Settings for sending payment reminders, and the choice inside it is the setting people most often have wrong, because the two behave completely differently:
| Mode | When reminders go out | What counts as the due date |
|---|---|---|
| Sending a reminder before the start of the programme | Counting back from the first session | The class start date — its own note says the due date equals the start date of the class, meaning the first session |
| Sending a reminder after the booking | Counting forward from when each person booked | Set separately, see below |
First reminder and Second reminder are both a number of days. In the "after the booking" mode they count from the booking, so two people who book a month apart are chased a month apart.
Days from date of enroling when payment is due is a third, independent number. It does not follow the first or second reminder and can be set higher or lower than either.
Reminders only reach bookings created after you activated the setting. The card shows the activation date. Switch it on today and the people already owing you money are not chased — only those who book from now on.
Changing that number does not move the instalments you already have
This is the single most reported confusion about payment timing, and the fix shipped in November 2026.
Days from date of enroling when payment is due only ever applied to instalments created
after you changed it. Everything already planned kept the dates worked out under the old
number — so one company ended up with two sets of rules running side by side, and a payment
plan that did not match the setting on the screen.
There is now a Check planned installments action beside the setting. It shows you the impact first and changes nothing until you confirm:
| The preview tells you | Why it matters |
|---|---|
| How many instalments would have their dates changed | The size of what you are about to do |
| How many would be created at the next automatic run | Their new creation date is today or earlier, so the payment is raised and the client notified straight away — with no advance notice |
| How many advance notices would go out at the next run | Same reason, one step earlier in the sequence |
| How many already had their advance notice | It is not sent twice |
| How many are skipped because their plan has stopped | A stopped plan is left alone |
Then Update installments, or Leave as is — which keeps the planned dates and lets only new instalments follow the current setting.
Due dates do not move. Ever. The action shifts when the payment is created and when the advance notice goes out. What the client owes, and by when, is untouched. If what you actually want to change is the due date, this is not the tool.
Save first. The check runs against the saved settings, not the ones still on screen. Zooza will tell you so rather than quietly checking the old values.
If a payment says it was created on a date you did not expect — 31 October when you set the due day to the 15th — that is the creation date, not the due date. They are two different numbers, and this action is what brings the first into line.
Reminders do not stop when the class starts
The most common misreading of the table above. "Before the start of the programme" is where the countdown starts from — it is not a deadline after which reminders stop.
Since mid-2026 these notifications are triggered by the booking's status, not by the calendar. While a booking sits in Awaiting payment and the notification is switched on, it keeps being sent — including after the first session has been taught. Before that change they were tied to the class start date, which is where the belief comes from.
So "can I send a reminder 7 days after the course starts?" is really two questions:
- Will somebody who still has not paid be chased once we have started? Yes, already.
- Can I set a reminder to go out on day 7 after the start? Not as a date. Use Sending a reminder after the booking and count from the booking instead, which is usually what you actually want — it chases each person on their own clock rather than everybody at once.
There is now a third reminder
Added in November 2026. Third reminder sits under the first and second in the same Payment reminders settings card, in both timing modes. Leave it at 0 or empty and it is off, which is how every existing programme starts.
The three have to stay in order, and Zooza enforces it as you type:
| Mode | Order required |
|---|---|
| Before the start of the programme | The numbers count down: the first reminder is the largest, the third the smallest. They are days before the start |
| After the booking | The numbers count up: the first reminder is the smallest, the third the largest. They are days after booking |
The third reminder has its own system email template, Third reminder, listed beside the first and second under Communication → Templates. Like the other two it is read-only.
Worth thinking about before you switch it on. A client who has ignored two emails rarely reads the third, and open rates fall with each one. What often works better is stopping the service — if an instructor can see an unpaid booking, the session arguably should not be taught — or reaching people on WhatsApp, where an unpaid-booking nudge is actually read.
There is no longer a ceiling on how early a reminder can go out
If you set a long lead time — 40 days before the start, or 360 — and nothing was ever sent, that was a real limit, not your setup. Reminders stopped working somewhere above 35 days and nothing said so, in the settings or here.
That ceiling was removed in the November 2026 rebuild. Long lead times now fire as configured, which matters for trips and camps sold months ahead.
Two other things that rebuild settled, and which explain timing questions:
- Reminders go out at 09:00 on the reminder's day — not at the session's time, and not overnight.
- A reminder missed because of an outage is sent at most one day late. After that it is skipped rather than arriving as a surprise days later.
Handling unpaid bookings automatically
Further down the same panel is a separate decision: what should happen to a booking that is still unpaid when the programme starts.
The control is named after the timing you chose above. With reminders counted from the programme start it reads "Handle unpaid bookings automatically 1 hour before the programme begins"; with reminders counted from the booking it reads "…automatically after the period you set following the booking". Same setting, wording that follows your own choice — so do not go looking for the first version if you picked the second mode.

| Option | Which bookings it acts on |
|---|---|
| Leave unpaid bookings as they are | None. The default, and the safe choice. |
| All unpaid bookings | Enrolled bookings with status Unpaid, Down payment unpaid or Final payment unpaid. Partially paid bookings are never affected. |
| Without down payment | Only enrolled bookings with status Down payment unpaid. |
| Unpaid bookings that have received at least one reminder | The same bookings as All unpaid bookings, narrowed to those a reminder has actually reached. |
The last option exists only in the programme-start mode. Switch the timing to count from the booking and it disappears from the list — but if it was already selected it stays selected, unlisted. So a rule can be running on "has received a reminder" while the list in front of you does not offer it. Re-pick deliberately after changing the mode.
Move bookings without a down payment to the waitlist is the gentler alternative — the place is freed but the person keeps their position rather than disappearing.
Once you pick anything other than Leave unpaid bookings as they are, a second choice appears — What happens to these bookings:
| Outcome | What you are left with |
|---|---|
| Delete | The booking is removed together with its history. The client gets the automatic deletion email. |
| Cancel | The booking stays, cancelled, with the reason Cancelled automatically for non-payment. The client gets the standard cancellation email. |
Cancel is the one to pick if you ever need to explain what happened. A cancelled booking still shows in the client's record and in the cancellation reporting; a deleted one leaves nothing to point at. It was added in November 2026, so a rule you configured before then is still set to delete.
If the programme also has the auto-cancel-unpaid automation switched on, both run. Zooza says so on the screen: the two act under different conditions and whichever fires first wins. Having both is not an error, but it does mean the outcome you configured here is not necessarily the one that happens.
Read this before switching deletion on. Only a booking with a payment assigned to it counts as paid. If you reconcile bank transfers by hand, or import statements with any delay, a parent who has genuinely paid can still be deleted because the money has not been matched to their booking yet. In that situation leave it on Leave unpaid bookings as they are.
Turn off scheduled payment notifications
If you want to stop all payment reminder emails for your clients, you can disable them globally.
Go to Settings → Billing & Payments → Payment settings → Scheduled-payment notifications and turn off the Send scheduled payment notifications toggle.
When this is off:
- The upcoming payment (pre-notice) email is not sent.
- The payment created email is not sent.
- The overdue payment email is not sent.
What is not affected: the payment confirmation email (sent when a payment is successfully processed) — that notification is not controlled by this toggle and is always sent.
Archiving a class stops its reminders
Archiving a class or a whole programme takes it out of operation, and unpaid bookings inside it stop receiving payment reminders.
This matters if you archive last term's classes to tidy the list. Anyone who never paid stays unpaid — the debt does not disappear — but they stop being chased about a programme that is no longer running.
If reminders are still going out for something you archived, check that you archived the class, not just hid it from the booking form. Hiding a class from the form only affects new registrations.
Suppress duplicate payment emails (cooldown)
If clients receive multiple payment notifications for recurring charges in quick succession, the cooldown setting can help.
When the master notifications toggle is on, you can set a cooldown in the Scheduled-payment notifications card in Settings → Billing & Payments → Payment settings. The setting reads: "For customers paying via stored card or direct debit, skip the 'payment created' email if the previous payment in this plan was less than N months ago."
If a previous scheduled payment in the same series was processed within the configured window, the at-creation email for that booking is suppressed.
Who the cooldown applies to: Stripe stored card and GoCardless inbound clients only.
Who always gets the email regardless of cooldown:
- Clients paying by bank transfer (manual recording)
- The first payment in any series
Default: notifications on, cooldown = 0 months (no suppression).
Suppressed notifications: When a notification is suppressed by the cooldown, there is no visible indicator in the admin panel. The suppression is logged server-side only. If you need to verify whether a notification was sent, check the client's message history in Communication.