- A base cadence runs five steps timed around the due date, but sector and customer behavior should adjust the timing, not override it.
- Email is the right default channel; phone calls and physical notices belong later, after automation hasn't resolved the account.
- A good reminder states the amount, due date, and one clear call to action, with multiple payment methods available.
- Segmenting by customer value and behavior signals (not just days late) protects important relationships while still collecting faster.
- Track DSO trend, on-time payment share, and complaint/opt-out rate before and after changes to prove the sequence is actually working.
Automated payment reminders are scheduled, rule-based messages — almost always email, sometimes SMS — sent around an invoice's due date to prompt payment without a person drafting or sending each one by hand. They're the earliest, lowest-friction stage of what's broadly called "dunning," but they're narrower than the full collections process: reminders prompt, they don't negotiate, escalate to legal action, or renegotiate terms.
This guide covers what actually makes a reminder sequence work: timing, channel choice, message content, and how to segment customers so the sequence collects faster without damaging good relationships.
What Automated Payment Reminders Are (and Aren't)
A reminder sequence is the set of scheduled messages that fire automatically based on an invoice's due date — before it's due, right at the due date, and after it goes overdue. It's automated in the sense that no one is manually deciding "should I email this customer today," not in the sense that it replaces judgment entirely.
It's worth being precise about scope: reminders are one stage of the broader dunning/collections process. Dunning also covers phone outreach, payment plans, credit holds, and eventually legal or agency escalation for accounts that never respond. This guide is specifically about the reminder stage — the automated messages that run before any of that heavier escalation starts.
A Cadence That Works
A commonly used reminder sequence runs five steps, timed around the due date:
| Step | Timing | Tone |
|---|---|---|
| Initial reminder | 10–15 days before due date | Neutral, informational |
| Follow-up reminder | 3–5 days before due date | Neutral, slightly more direct |
| Due-date reminder | On the due date | Direct, clear call to action |
| Post-due reminder | 3–5 days after due date | Firmer |
| Final reminder | 7–10 days after due date | Firmest, before escalating to a call or physical notice |
Sector context shifts these timings somewhat. Banks and fintech companies often compress the pre-due-date window to a single reminder about a week out, plus one more one to two days before the deadline. Subscription and utility services more often remind five to seven days before the due date, matching how those bills tend to be budgeted for. Treat both as starting points to adapt, not fixed rules — your own customer base and payment behavior should shape the exact timing more than any published example.
It's also worth reading cadence advice with a critical eye. One widely cited guide to this topic recommends sending "no more than four reminder emails per month" in one section, while its own general sequence lists five emails across a billing cycle — an internal inconsistency in a single piece of published advice. That's not a reason to distrust the whole cadence concept; it's a reason to treat any single "best practice" list as a starting point to adapt rather than a rule to copy exactly, and to sanity-check the specifics before you lock in a cadence of your own.
Channel Mix: Email First, Escalate Deliberately
Email is the right default channel for the automated stage of reminders — it's cheap to send at scale, easy to template, and doesn't require real-time availability from either side. Running it through a dedicated transactional email service rather than a general marketing platform matters for deliverability, since reminder emails need to reliably land in an inbox, not a spam folder.
Phone calls and physical notices belong later in the sequence, after the final automated reminder has gone out and the account still hasn't responded. Running phone outreach in parallel with the earliest automated reminders is usually unnecessary friction for accounts that would have paid on their own — it's a tool for the accounts the automated stage didn't resolve, not a parallel track from day one.
What a Good Reminder Message Includes
The content of the message matters as much as its timing. A well-designed reminder typically includes:
- A subject line that states what, why, and when — for example, naming the invoice and due date directly rather than a vague "Reminder" subject.
- A short, mobile-friendly body that a reader can act on without opening a separate document.
- A masked account reference, the amount due, and the due date, stated plainly near the top.
- One clear call to action — typically a "Pay Now" button or link to a payment portal, not several competing links.
- Multiple payment methods available from that link, so the method isn't the thing standing between the customer and paying.
- Basic branding and trust signals, so the message is recognizable as legitimate rather than something that looks like a phishing attempt.
- A check against customers who've already paid — nothing undermines trust in an automated system faster than a reminder for a balance that's already settled.
Embedding a one-click payment link and offering multiple payment methods directly in the message removes friction at the exact moment someone has decided to act — and that friction reduction is commonly cited as one of the more reliable ways to shorten actual time-to-pay, independent of how firm the message's tone is.
Segment by Relationship, Not Just by Days Late
Treating every overdue account the same way — same tone, same escalation timeline — misses an obvious variable: not every late payment carries the same relationship risk. A more effective approach varies both tone and escalation path by customer value and by behavior signals, such as whether the customer has actually opened previous reminders.
In practice, that might mean a shorter, more direct cadence for small-balance or lower-risk accounts, where firmness carries little relationship cost, and a more measured, relationship-preserving cadence for large strategic accounts, where the same firm tone sent on a rigid schedule could create friction with a customer worth protecting. Automating the mechanics of a reminder sequence doesn't mean every account has to run through an identical one.
Behavior signals add a second layer on top of account value. A customer who consistently opens every reminder but still pays a few days late is a different case than one who hasn't opened any of them — the first may simply be slower-paying but engaged, while the second may need a channel change (a phone call, rather than a fourth unopened email) rather than another identical message. Segmentation, done well, is really about matching the next action to what you already know about how that specific customer is behaving, not just how much they owe.
Why This Actually Reduces DSO (and What to Be Skeptical Of)
It's tempting to assume automated reminders work because an automated message is somehow more persuasive than one a person would send. That's not really the mechanism. The actual value is consistency: automation removes the lag between an invoice becoming overdue and someone noticing and acting on it. A human-run process depends on someone remembering to check an aging report; an automated one fires on schedule regardless.
Be skeptical of dramatic, unsourced statistics that show up in vendor content on this topic — large multiples on "volume handled," precise day-counts on predicting who will pay late, or single case-study numbers presented as if they generalize. Some published guides on this exact topic include figures of that kind with no visible source or methodology behind them. Treat any number like that the same way you'd treat an ROI claim from a software vendor: useful as a hint, not as evidence until you can see how it was actually measured.
Measuring Whether Your Sequence Is Working
A reminder sequence isn't something you set up once and leave alone. Three signals are worth tracking on an ongoing basis: how DSO trends after you change the cadence or message content, what share of invoices get paid before versus after the due date, and whether complaint volume or unsubscribe/opt-out requests rise when you tighten the schedule or firm up the tone. None of these require special software beyond what most invoicing or AR systems already report — the point is to actually look at them before and after a change, rather than assuming a new template or tighter cadence helped just because it felt more aggressive.
If a firmer sequence doesn't visibly move payment timing but does generate more complaints, that's a sign the added firmness is a cost without a corresponding benefit for that segment — exactly the kind of thing a blanket, un-segmented cadence can hide.
Choosing a Cadence You'll Actually Stick To
Start from a base cadence — five steps, timed around the due date — and adapt it by segment rather than applying it uniformly to every customer. Keep the message itself simple: clear amount, clear due date, one call to action, multiple ways to pay. Measure whether it's actually working by watching response time and complaint rate, not by assuming a published "best practice" number applies to your business.
The goal of automated payment reminders isn't to automate harder. It's to remove the lag that lets overdue invoices sit unnoticed, while keeping enough judgment in the loop that your best customers never feel like they're being chased by a machine.
Is this the same as dunning?
No. Dunning is the broader collections process, including phone outreach, payment plans, and legal or agency escalation. Automated payment reminders are the earliest, lowest-friction stage of it.
How many reminders is too many?
There's no single correct number. Match the cadence to the customer relationship and watch for diminishing returns or complaints rather than following a fixed count from any one source — as the cadence inconsistency above shows, even published "best practice" lists don't always agree with themselves.
Does automation remove the need for judgment on large accounts?
No. Automation handles the routine scheduling and sending. Relationship-sensitive accounts still warrant a human decision on tone, timing, and whether to deviate from the standard sequence at all.



