Invoice reminder schedule: when to email, call, and pause follow-ups
Build a practical overdue-invoice follow-up schedule with example timing, clear stop conditions, and rules for promises, disputes, and reported payments.
A reminder schedule should depend on the invoice’s current state, not just the number of days overdue. Start with a verified balance, send a helpful email, follow up if there is no response, and pause automated outreach when the client replies, disputes a charge, or reports payment.
What is a reasonable invoice reminder schedule?
A workable starting point is a reminder shortly after the due date, a second email about a week later, and a phone follow-up if email has not resolved the issue. Those intervals are a policy choice, not a universal rule or a promise of better recovery.
Choose timing around your clients’ billing process. A corporate client waiting for purchase-order approval is different from a client who never received the invoice. The schedule should give the team consistency without overriding new information.
For a concrete industry example, CollBox describes email outreach on days 1 and 7 past due and a specialist phone follow-up around days 10–14. Its later outreach varies with the response, and disputes are returned to the business. Source: CollBox’s published process. The example below is an adaptable operating plan, not a reproduction of a vendor’s service commitment.
An example follow-up plan
| Point in the process | Suggested action | Check before acting |
|---|---|---|
| Invoice issued | Confirm delivery and payment instructions | Correct recipient, agreed terms, accurate amount |
| Shortly after the due date | Send a friendly first reminder | No payment, credit, dispute, or extension |
| About a week after the first reminder | Ask whether payment is scheduled | No useful reply or recorded payment |
| After unanswered email follow-up | Call the authorized billing contact | Contact policy, previous attempts, account context |
| Client responds | Route the response to the right next step | Is this a question, promise, dispute, or payment report? |
| Payment recorded | Match funds and stop invoice reminders | Correct invoice and remaining balance |
Do not read this table as permission to contact every client at the listed intervals. Your agreements, client communication preferences, and applicable requirements come first. Use an approved schedule and have a person review exceptions.
The four events that should change the schedule
A reply arrives. Stop treating the account as unanswered. If the client needs an invoice copy, send it and record the new review date. If a staff member must answer a question, assign that task instead of sending another generic reminder.
A payment date is proposed. Separate a request from an approved commitment. A client asking for Friday does not necessarily have approval to pay Friday. Once agreed, record the amount, date, and owner, then schedule a verification check.
A charge is disputed. Pause routine demands for the disputed amount and route the explanation to someone who can investigate. Preserve the original message and invoice details. Do not let a follow-up tool invent a settlement or revise a charge.
Payment is reported. Check the billing or payment record. Do not mark the invoice paid solely because an email says so, and do not keep sending “still unpaid” messages while a known payment is being reconciled.
How to prevent duplicate reminders
Give each invoice one outreach owner, even if several systems are involved. If your accounting platform already sends reminders, decide which messages it owns before adding another service or agent.
Keep a shared event history with the last contact date, channel, recipient, result, and next action. Staff should be able to tell whether an email went out this morning without searching three inboxes. Before sending, check for a newer event than the one used to create the draft.
An example: Cake prepares a reminder at 9:00 AM. At 9:02, the client tells an employee payment was sent. At 9:05, the queued reminder should be rechecked against that update. A saved draft is not a reason to ignore more recent information.
What should happen after a missed promise?
First verify that the payment did not arrive under a different reference or after a processing delay. If it remains unpaid, follow up on the specific commitment rather than restarting the generic first-reminder sequence.
A suitable message is: “We had noted [date] for payment of [amount]. Our records still show the balance outstanding. Has the payment been sent, or should we discuss the next step?”
Repeated missed commitments should go to the account owner. They may need to review the relationship, billing accuracy, or available options. A longer automated sequence is not always the right answer. Use a payment commitment log to make those handoffs concrete.
How to judge whether the schedule is working
Track results for the same invoice group over a defined period. Useful measures include verified payments, resolved billing questions, promises kept, duplicate messages, and time spent handling exceptions. Email opens alone do not show cash recovery.
Compare the cash recovered with what similar invoices would likely have generated without the change. Keep write-offs, credits, and partial payments separate. The recovery ROI guide explains how to avoid crediting all incoming cash to a reminder program.
Common questions
Should reminders continue every week indefinitely?
No. Set a review point where a person evaluates the account. Repetition without a response can indicate the wrong contact, a disputed invoice, or a problem outside the reminder workflow.
Should email and phone outreach use separate schedules?
They can have different steps, but they should share one account history. A successful call should change the email plan. A payment confirmation should stop both channels for that invoice.