Chasing unpaid invoices is the job nobody in a small business wants. It gets pushed to Friday afternoon, then to next week, and by the time someone sends the email the invoice is a month overdue and the conversation is harder than it needed to be. Automated invoice reminders fix the timing problem: the follow-up goes out when it should, every time, without anyone remembering to do it.
Automated invoice reminders are scheduled emails or SMS messages that your accounting or workflow software sends when an invoice is about to fall due or has become overdue. A good setup sends three to five reminders on a fixed schedule, stops the moment payment is recorded, and hands disputes, payment plans and repeat late payers to a person.
This guide covers how to choose between the reminders built into your accounting software and a connected reminder workflow, a starting schedule, sample wording, the rules that decide when a person takes over, and the mistakes that make automated reminders feel robotic.
What are automated invoice reminders?
An automated invoice reminder is a message triggered by an invoice's due date and payment status rather than by a person. The software checks which invoices are still unpaid, works out how many days they are from (or past) the due date, and sends the matching message from a set of approved templates.
There are two common ways to run them:
- Built-in reminders inside your accounting software. Both Xero and MYOB Business include invoice reminder settings that email customers before or after the due date using templates you edit. Xero documents the setup in its guide to setting up invoice reminders.
- A connected reminder workflow built with an automation platform such as Make or n8n. It reads invoice and payment data from Xero, MYOB or QuickBooks, applies your own rules, sends messages by email or SMS, and records what happened in your CRM or job management software.
Either way, the reminder is only as good as the payment data behind it. If bank transactions are not reconciled promptly, the software cannot tell who has paid, and customers who have already paid will get chased.
Why automate invoice reminders instead of chasing manually?
Manual chasing fails for predictable reasons. It depends on one person checking the aged receivables report, it stops when that person is busy or on leave, and the tone drifts depending on how frustrated they are that day. Customers notice the inconsistency: some get chased on day two, others not until day forty.
Automation does not make customers pay. What it does is remove the delay between an invoice becoming overdue and the customer being told, and it makes every customer's experience consistent. That consistency matters for cash flow and for relationships, because a polite, predictable reminder is easier to receive than a sudden, irritated phone call.
It also frees the person who used to do the chasing to spend their time on the accounts that genuinely need a conversation.
Built-in reminders vs connected automation: which do you need?
For many small businesses, the reminders already built into Xero or MYOB are enough. A connected workflow becomes worth it when reminders need to depend on information outside the accounting system, or when different customers need different treatment.
| Factor | Manual chasing | Built-in Xero or MYOB reminders | Connected reminder workflow |
|---|---|---|---|
| Set-up effort | None | Low: edit templates and timing | Moderate: rules, connections and testing |
| Channels | Whatever the person uses | Email, SMS and internal alerts | |
| Stops when paid | Only if someone checks | Yes, once payment is recorded | Yes, once payment is recorded |
| Rules by customer group or invoice value | Ad hoc | Limited | Yes |
| Escalation to a person | Ad hoc | Manual, from the aged receivables report | Automatic task or alert at a set stage |
| Updates CRM or job system | Rarely | No | Yes |
| Best for | Very low invoice volume | Simple terms, one customer type | Mixed customers, approvals, several systems |
A useful test: if you can describe your follow-up process as "the same three emails for everyone", start with the built-in reminders. If your description includes words like "except", "unless" or "depending on", you probably need a connected workflow. Our Invoice Reminder Automation is built for that second case.
How to set up automated invoice reminders in 7 steps
The same sequence works whether you use built-in reminders or a connected workflow.
- Fix your payment terms first. Make sure every customer has the right terms recorded (for example 7, 14 or 30 days) and that invoices show a clear due date. Reminders built on wrong due dates will be wrong every time.
- Make paying easy. Include a payment link or clear bank details on every invoice and every reminder. A reminder that makes the customer hunt for how to pay is a wasted message.
- Get reconciliation up to date. Reminders stop based on recorded payments. If reconciliation runs a week behind, set reminders to start later or catch up on reconciliation before switching them on.
- Decide your schedule. Choose how many reminders, at which points, and whether any go before the due date. The schedule below is a sensible starting point.
- Write the templates. Keep each message short, include the invoice number, amount, due date and a payment link, and step the tone from friendly to firm.
- Set exclusions and escalation rules. Turn reminders off for customers on payment plans, disputed invoices and accounts you manage personally. Decide the point at which a person takes over.
- Test, then watch the first month. Send each template to yourself, check merge fields and links, then review every reminder that goes out for the first few weeks before trusting it to run on its own.
If your invoices start in a job management system such as ServiceM8, Tradify or Simpro, as many trades and home service businesses do, check that jobs flow into your accounting software with the correct customer and due date first. That handoff is often where reminder problems really start, and it is the kind of connection our systems integration work covers.
What should an automated invoice reminder schedule look like?
There is no single correct schedule. It depends on your payment terms, your customers and how much risk you can carry. This is a reasonable starting point for 14 or 30 day terms:
| When | Purpose | Tone |
|---|---|---|
| 3 days before due | Courtesy notice with payment link | Helpful |
| 1 to 3 days after due | First overdue reminder | Friendly, assumes an oversight |
| 7 to 10 days after due | Second reminder, asks them to reply if there is a problem | Polite but direct |
| 14 to 21 days after due | Final automated reminder, states the next step | Firm |
| After the final reminder | Task created for a person to call | Personal conversation |
Two adjustments are common. Businesses on 7 day terms often drop the pre-due notice and start a day or two after the due date. Businesses with a few large commercial customers often add an internal alert before the first overdue reminder, so someone can check whether the customer's accounts payable team needs a purchase order number or a different contact.
How should an overdue invoice reminder email be worded?
Good reminder wording is short, specific and easy to act on. Every reminder should include the invoice number, amount, due date and a way to pay, and it should come from an address the customer can reply to, not a no-reply mailbox.
First overdue reminder
Hi Sam, a quick reminder that invoice 1042 for $1,280.00 was due on 3 October. If it has already been paid, thank you and please ignore this. Otherwise you can pay securely here: [payment link]. Just reply if anything on the invoice needs checking.
Final automated reminder
Hi Sam, invoice 1042 for $1,280.00 is now 21 days overdue. Please arrange payment this week using the link below, or reply to let us know when payment will be made. If we have not heard back by Friday, a member of our team will call you to discuss the account.
Notice what the final reminder does not do: it does not threaten, add fees that were never agreed, or pretend to be a debt collector. If your terms of trade allow late fees or interest, mention them in your terms and on the invoice from the start, not for the first time in a reminder.
When should a person take over from automation?
Automation should handle the routine follow-up. People should handle anything that needs judgement. Build these handoffs into the rules from day one:
- Disputes. If a customer replies questioning the work, the amount or the invoice details, reminders on that invoice should pause and the reply should go to a person.
- Payment plans. Once someone agrees a plan, standard reminders should stop for that customer.
- Repeat late payers. A customer who reaches the final reminder on several invoices needs a conversation about terms, not another email.
- High-value invoices. Many businesses require a person to approve reminders above a set amount.
- Key relationships. Long-standing commercial customers may be better served by a phone call from the account owner.
This is where a connected workflow earns its keep. It can read replies, recognise that a customer is disputing an invoice or asking for more time, pause the sequence and create a task with the context attached. That combination of fixed rules and AI for reading replies is how we approach workflow automation generally: AI interprets, rules decide, people handle exceptions.
If a payment dispute with another business escalates beyond what a conversation can resolve, the Australian Small Business and Family Enterprise Ombudsman provides information and dispute support for small businesses.
Common mistakes with automated payment reminders
- Chasing customers who have already paid. Almost always caused by slow reconciliation. It is the fastest way to make customers resent automation.
- Reminding on disputed invoices. Nothing damages a relationship faster than an automated "friendly reminder" on an invoice the customer has already told you is wrong.
- Too many messages. More than five reminders on one invoice rarely helps. Escalate to a person instead.
- No reply path. Customers reply to reminders with questions and remittance advice. Make sure replies reach someone.
- Set and forget. Review templates, timing and the exclusion list at least every quarter, and whenever your payment terms change.
Privacy and record-keeping considerations
Invoice reminders use customer contact and billing details, so the usual privacy obligations apply. Businesses covered by the Privacy Act should handle that information in line with the Australian Privacy Principles, and it is good practice for every business regardless.
In practice that means giving any reminder tool access only to the invoice and contact data it needs, keeping a record of what was sent and when, and making sure SMS reminders go only to numbers customers have provided for account contact. Keep reminders strictly about the account. Adding promotions to a payment reminder can change how the message is treated under the Spam Act 2003, and it muddies the message anyway.
For broader guidance on terms, invoicing and getting paid, business.gov.au's payments and invoicing section is a useful starting point.
How much does it cost to automate invoice reminders?
The built-in reminders in Xero and MYOB are part of the software you already pay for, so the main cost is the time to set up templates and rules. Check that your plan includes invoicing and reminders.
A connected reminder workflow is a build. At IT Your Service, a single workflow starts from $500 and a workflow spanning several systems, such as accounting, CRM and job management software, starts from $1,500. The final price is confirmed in writing after a free audit. See our pricing page for what is included.
If you are new to the idea of connecting systems, our guide to what workflow automation is explains the basics. Otherwise, the best first step is simple: open your aged receivables report, look at how many invoices are past due right now, and ask whether a consistent schedule would have caught them sooner. If you want help working that out, book a Free Audit.