How to Send Invoice Reminders on a Schedule That Works
How to send invoice reminders automatically, starting before the due date, with a named person at each end so that stalled queries turn into two-minute answers.
To send invoice reminders well, automate them on a defined schedule that starts before the due date, and make sure there is a named person at each end who can answer a question. A short, neutral reminder that arrives while the invoice can still be processed on time does more than several that arrive after it has missed a cycle.
Reminders are the quiet middle of collections. They sit between a correct invoice and a real chase, and when they run on their own they prevent most chases from ever being needed.
How to send invoice reminders: begin before the due date
Most people think of a reminder as something that follows a missed deadline. The better idea is to send the first one early. A short, neutral message a few days before payment is due arrives at a moment when the invoice can still be processed on time.
After the due date, the same invoice has already missed a payment cycle at the customer's end. A late reminder can ask for money, but an early one can prevent the delay in the first place. That difference in timing is the reason the order matters so much.
A schedule with a shape
The guide describes the sequence in plain terms: a reminder before the due date, a prompt on the day, and follow-ups on a defined schedule afterwards. Setting it out as a table makes the logic visible.
| Stage | Purpose | Tone |
|---|---|---|
| Before the due date | Catch problems while the invoice can still be processed on time | Short and neutral |
| On the due date | Prompt payment on the day | Plain and administrative |
| After the due date | Follow up on a defined schedule | Consistent, then stepping up |
The exact intervals are yours to choose. What matters is that they are defined in advance and the same for every customer. When a reminder goes beyond the automatic steps and a real person has to step in, the next stage is covered in how to chase an overdue invoice.
Why automation is the point
Automating reminders is not a convenience. It changes the character of the message. Reminders sent on a schedule are consistent, unemotional and impersonal in the right way. Reminders sent when a founder remembers are erratic, late, and unintentionally carry the founder's mood.
Consider what that means in practice. On a worried day, a hand-written reminder can sound sharp. On a day when you like the customer, it may never be sent at all. A scheduled message does neither, because nobody has to decide anything. It simply arrives.
Keep the first messages neutral
Early reminders should assume an oversight, because it usually is one. They do not accuse and they do not demand. They tell the customer what is due and when, and make it easy to act.
- State what the invoice covers and the due date.
- Show the reference to quote when paying.
- Make clear whom to contact with a question.
- Leave out blame, because most late payment is a process matter.
That last point is worth keeping in mind. Most late payment is a process failure, not unwillingness. A reminder that treats it that way is far more likely to bring a useful reply than one that assumes the worst.
A named human at each end
Automation covers the timing. It cannot cover a question. So alongside the schedule you need a person at each end: someone at the customer who actually processes payment, and someone on your side whom they know to contact.
The reason is stated bluntly in the guide. A large share of stalled invoices are stalled on a query nobody raised, such as a line item someone did not recognise or a missing document. A named contact converts a silent delay into a two-minute exchange.
| End | What you need | What it prevents |
|---|---|---|
| Their side | The person who actually processes payment | Reminders landing with someone who cannot act |
| Your side | A person they know to contact with a question | A query going unasked because nobody knows where to send it |
Why this matters more with larger customers
With a small customer, the person who bought from you may well be the one who pays. As customers grow, that stops being true. The buyer is frequently not the payer, and may not even know there is a problem.
That is why the contact details you collect at the start matter. Knowing who approves the invoice and who processes it lets your reminder reach someone who can do something. This follows directly from asking how the customer pays, which how to invoice correctly covers in detail.
What reminders cannot do
An automatic reminder is a prompt, not a cure. If the invoice itself was defective, a reminder will simply repeat the problem more often. If the customer is disputing the amount, a reminder will not settle it and may make things worse.
So keep one eye on the replies. A reply that raises a query is a signal that the case has left the automatic path and needs a person. Telling the types of problem apart is the subject of how to handle a late paying customer.
Write the ladder before you need it
Reminders are the lowest rung of a longer ladder. The guide recommends deciding in advance what happens at every stage: a reminder before the due date, a prompt on the day, a follow-up shortly after, a phone call, a more formal message, a pause on work and whatever final step you are prepared to take.
Deciding this in advance is what makes escalation calm and consistent, not emotional and erratic. In the moment you will either avoid it because you like the customer, or overreact because you are worried about cash. Automating the first rungs removes that temptation from the stage where it would do the most damage.
Keep a record of what was said
Every reminder and every reply belongs in a record. The guide's advice is to keep, in one place, what was invoiced, when, to whom, what has been paid, what is overdue and by how long, and what has been said about it.
That record is what lets a person step in without starting from nothing. It also feeds the monthly look at everything outstanding, which is described in how to review collections monthly.
Setting it up in a short list
- Choose the schedule: before the due date, on it, and after it.
- Write a neutral wording for each step and stop there.
- Put the schedule on automatic, so no one has to remember it.
- Name a contact on your side and find the right one on theirs.
- Record every reminder and every reply in one place.
- Decide the point at which a person takes over.
The whole set-up is an afternoon of thought. After that, the reminders do their quiet work without anyone being in the mood for it.
Reminders and the customer's own cycle
Customers run payments on a cycle, and that is why timing matters so much. If the invoice reaches the person who approves it after the cycle has closed, it waits for the next one. A reminder before the due date gives you a chance to catch that while there is still time to act.
This is also why asking about the cycle at the start is so useful. Once you know when payments are run, you can place the first reminder to land ahead of it. A message that arrives a few days before is no longer a nag. It is a useful nudge at the point where it can change the outcome.
What a good reminder contains
| Element | Why it helps |
|---|---|
| The invoice and what it covers | The reader does not need to hunt for context |
| The due date | It is unmistakable what is being asked |
| The reference to quote | The payment can be matched to the invoice |
| A named contact | A question has somewhere to go |
Keep it short. A reminder is not an essay. Its job is to make the right action obvious to a busy person.
Check that the schedule is working
Automatic does not mean forgotten. Once a month, glance at whether the reminders went out and what came back. A schedule that quietly stopped working is worse than none, because you believe the job is being done.
This check belongs naturally in the monthly look at everything overdue. If an invoice is late despite your reminders, ask whether they reached the right person, and whether the invoice was correct to begin with. The reminder cannot repair either of those.
Frequently asked questions
Why send a reminder before the invoice is due?
Because it arrives while the invoice can still be processed on time. A reminder sent after the due date comes when the invoice has already missed a cycle.
Why should reminders be automatic?
Scheduled reminders are consistent and unemotional. Reminders sent when a founder remembers tend to be erratic and late, and they carry the founder's mood without meaning to.
What does a named human at each end do?
They turn a silent delay into a quick exchange. Many stalled invoices are waiting on a query nobody raised, and a known contact makes asking easy.
Do reminders replace phoning the customer?
No. They handle the routine cases, and a call handles the stalled ones. Email is easy to ignore, so move to the phone once the automatic steps have not worked.
The full method, with the checklists, is in The Getting Paid Playbook, a free 34-page playbook.