Pricing and billing
Dunning schedule planner
Turn one overdue invoice into the four reminder dates and reminder text to send for it.
Free, no accountIn your browser
Named in every reminder's text below.
What the customer owes on this invoice.
The day the invoice was due, written as 2027-01-31 or 31/01/2027.
Leave this blank to use today. Set a day to see which of the four reminders would already be due by then.
Result
Nothing to plan yet
Enter the invoice's due date to see the reminder schedule.
What this is
This dunning schedule planner takes one invoice - its amount and its due date - and works out the four calendar dates an escalating reminder schedule falls on, day 1, 7, 14 and 30 after the due date, with the actual reminder text to send at each stage already naming the invoice, the amount and exactly how overdue it is.
Dunning is the escalating series of reminders a business sends for an invoice that has gone past its due date - a gentle nudge at first, firmer wording as the days without payment add up, and a final notice at the end of the run. Four stages, a day after the due date, a week, two weeks and a month, is a common shape for that escalation.
Every reminder's own "days overdue" is worked out from the two actual dates, the reminder's and the invoice's due date, rather than written down as a fixed number - so it is always the true gap between them, whatever the due date itself turns out to be.
How to read the result
The facts row restates the invoice as entered: its number, its amount, its due date and the day the schedule is being counted from. The table below lists the four reminder dates and how many days overdue each one represents.
Each reminder also appears as its own finding with the exact text to send at that stage, ready to copy into an email or a message - naming the invoice, the amount, and how many days overdue the invoice is by that point.
Common mistakes
What goes wrong most often, and how to tell.
- Expecting this to actually send a reminderIt drafts dates and text only. Nothing here emails, texts or notifies anyone - every reminder still has to be copied out and sent by hand, or by whatever system a business already uses to send one.
- Assuming a reminder date in the past means it already went outThis plan has no record of what was actually sent, and no way to know whether an invoice was paid at any point along the way. A reminder date sitting before today is only a date that has arrived, not a notice that was acted on - that is worth checking separately, every time.
- Treating the four-stage schedule as fixed for every businessDay 1, 7, 14 and 30 is one common escalation, not a rule. A business with a shorter payment cycle, or a different relationship with the customer, may reasonably want these reminders closer together or further apart.
Questions
What people ask about this tool.
- No. It plans the four reminder dates and drafts the text for each one, but nothing here sends an email, a text or any other notification - every reminder still has to be sent by a person, or by whatever system already handles that.
- Each of the four reminder dates is the invoice due date plus a fixed number of days - 1, 7, 14 and 30 - and "how overdue" each one says is the exact gap between that reminder date and the due date, worked out from the two dates themselves rather than written as a fixed number anywhere.
- The schedule is still built the same way, counted forward from that due date - if it is already in the past, some or all of the four reminder dates will already have arrived too, and a finding says how many. This plan has no idea whether those reminders were ever actually sent.
- No. It has no connection to any invoicing or payment system, so it cannot tell a paid invoice from an unpaid one - re-run it with updated details, or simply stop sending reminders, once payment actually arrives.
Use it from the API
The same check, as one request.