Xero overdue invoice reminders: adding SMS and a human
Xero already emails payment reminders. Here is when that is enough, and the API build that adds a text, a personal email and a handover for the rest.
What you get from this guide
- What Xero's built-in reminders do, and when they are all you need
- The gap: email only, one voice, no handover to a person
- The Accounting API calls and published rate limits
- A three-rung ladder that adds a text and a human at the right moments
- The reconciliation trap that makes automations chase paid invoices
What Xero already does
Xero has automatic invoice reminders, and they are good. Its invoicing page describes them plainly: Xero emails payment reminders for you, before or after the due date; you choose when and how often to send them; and with your bank connected, Xero stops sending reminders once payment arrives.
That last point matters more than it looks. The hardest part of any invoice chasing automation is knowing the invoice has been paid, and Xero's own reminders get that from the ledger itself. Anything you build outside has to work to match it.
Do this before anything else
When the built-in reminders are enough
Be honest with yourself here, because a build you do not need is pure cost.
- Your customers pay by card or bank transfer from the emailed invoice, and most pay after the first or second reminder.
- You raise a modest number of invoices and already look at the overdue list each week.
- Your customers are businesses with an accounts payable inbox, where email is the right channel.
If all three describe you, stop here. The cases where a custom layer earns its keep look different: trades and home services invoicing homeowners who read texts and ignore email, a long tail of small overdue invoices nobody has time to ring about, or a need to treat a large late invoice differently from a small one.
What they do not do
| Need | Xero reminders | Custom ladder on the API |
|---|---|---|
| Email before and after the due date | Yes | Yes, but let Xero do it |
| Stops when payment is reconciled | Yes | Yes, by re-checking the invoice before each send |
| Text message | Described as email | Yes, from your own registered number |
| Different handling by invoice size | Check your settings | Yes, any rule you can write |
| Hand over to a named person with history | No | Yes |
| Pause one customer mid-dispute | Check your settings | Yes, a flag on the record |
Where the table says check your settings, that is deliberate. Xero's help centre covers the reminder options in detail and they change over time, so read your own settings screen rather than trusting any third-party summary, this one included.
The API you build on
Xero publishes its Accounting API as an OpenAPI specification. The base URL is https://api.xero.com/api.xro/2.0, authentication is OAuth 2.0, and every request needs a xero-tenant-id header naming the organisation. Four endpoints do the work.
| Endpoint | What the specification says | Used for |
|---|---|---|
| GET /Invoices | Retrieves sales invoices or purchase bills; accepts where, order, Statuses, ContactIDs and paging | The daily overdue pull |
| GET /Invoices/{InvoiceID} | Retrieves one invoice | The re-check before every send |
| GET /Invoices/{InvoiceID}/OnlineInvoice | Retrieves a URL to an online invoice | The pay link in each message |
| POST /Invoices/{InvoiceID}/Email | Sends a copy of a specific invoice to the related contact via email | An optional resend rung |
Invoice statuses in the specification are DRAFT, SUBMITTED, DELETED, AUTHORISED, PAID and VOIDED. An overdue invoice is one that is AUTHORISED, past its DueDate, with an AmountDue above zero. The read scope listed for these endpoints is accounting.transactions.read, with accounting.transactions for the email endpoint.
Rate limits are in Xero's developer FAQ on limits: 5 concurrent calls, 60 calls per minute and 5000 calls per day for each connected organisation, and 10,000 calls per minute across an app. Exceeding a limit returns a 429 with a Retry-After header, and responses carry X-DayLimit-Remaining and X-MinLimit-Remaining. Xero states the limits are the same for all apps.
On the automation side, n8n ships a Xero node with get, get all, create and update operations for invoices and contacts, and its documentation points to the HTTP Request node for anything else, such as the email endpoint.
The reminder ladder
This ladder assumes Xero keeps sending its own emails and your workflow only adds what Xero does not. Adjust the days so no rung lands on the same day as a Xero reminder.
| Rung | Days overdue | Channel | Tone |
|---|---|---|---|
| Xero | Before due, then 7 | Xero's email | Standard reminder |
| 1 | 10 | SMS | Friendly, assumes it was missed, includes the pay link |
| 2 | 21 | Personal email from a named role | Direct, asks if there is a problem with the invoice |
| 3 | 30 and over | Task for a person | A phone call, with the history in front of them |
An illustrative sum, with invented figures purely to show the arithmetic: 40 invoices a month at an average of 500, with 10 percent reaching 21 days overdue, is 4 invoices and 2,000 sitting unpaid at any time. Getting those paid 10 days sooner does not create revenue. It moves cash earlier. Value the build on that basis, not on recovered sales.
The build
Create the Xero app and connect
Register an app in the Xero developer portal, complete the OAuth 2.0 connection to your organisation and note the tenant id. In n8n, the Xero credential handles the token refresh for you.
Pull overdue invoices daily
Schedule one run each morning, after reconciliation if you can. Request authorised sales invoices and page through the results.
Daily overdue pull
GET https://api.xero.com/api.xro/2.0/Invoices
?Statuses=AUTHORISED
&where=Type=="ACCREC"
&order=DueDate ASC
&page=1
Authorization: Bearer <access token>
xero-tenant-id: <tenant id>
Accept: application/json
Keep rows where DueDate is before today
and AmountDue > 0Compare each due date with today's date in the workflow itself, which keeps the request simple and easy to test. One call per page per day keeps you far inside the 5000 daily calls.
Upsert the state record
One row per invoice id: contact name, phone, email, amount due, due date, rung, last_sent and a paused flag. New invoices are inserted at rung zero. Existing rows only have their amount due refreshed.
Work out which rung is due
Compare days overdue with the ladder. If the invoice has crossed a threshold and that rung has not been sent, it is due. Skip anything paused, and skip any contact without consent for the channel that rung uses.
Re-check the invoice, then send
Immediately before sending, call GET /Invoices/{InvoiceID}. If the status is PAID or the amount due is zero, close the record. Otherwise send the message with the invoice number, the amount due and the online invoice link, then store the rung and the time.
Handle replies
Route inbound texts and emails to a person and pause the record automatically. A reply saying the invoice is wrong must never be answered with the next reminder.
Escalate past the last rung
At rung three, create a task for a named person with the invoice link and every message sent. The automation's job ends there. What happens next is a conversation, and possibly a decision about whether you keep working for that customer.
Message copy
Rung 1 - SMS at 10 days overdue
Hi {first_name}, it is {business}. Invoice
{invoice_number} for {amount_due} was due on
{due_date} and looks unpaid. You can pay here:
{online_invoice_link}
If you have already paid, thank you and please
ignore this. Reply STOP to opt out.Rung 2 - personal email at 21 days
Subject: Invoice {invoice_number} - is anything wrong?
Hi {first_name},
Invoice {invoice_number} for {amount_due} is now three
weeks past its due date. If there is a problem with the
invoice or the work, tell me and I will sort it out.
If it has simply slipped, you can pay here:
{online_invoice_link}
{sender_role}, {business}
{phone}Keep the amount and the invoice number as literal fields from Xero. The line about having already paid is there because of the reconciliation gap, and it turns a potential irritation into a non-event.
Testing and measuring it
Invoice chasing is the one automation where a mistake lands on a paying customer, so test it harder than anything else you run. Start in a test organisation, not your live books.
- Connect the app to the test organisation first. Create an invoice to a contact with your own email and phone, approve it, and set the due date in the past.
- Run the daily pull and confirm the invoice appears once, with the right amount due.
- Run it again the same day and confirm no second message is sent for the same rung.
- Record a full payment against the invoice, run the pull, and confirm the record closes with no message.
- Record a part payment on another invoice and confirm the message quotes the remaining amount due, not the original total.
- Set the paused flag on a record and confirm it is skipped.
- Send the workflow more requests than it needs in a loop and confirm it backs off on a 429 using the Retry-After header.
When you move to your real organisation, run the workflow in a dry-run mode for a week. Have it write what it would have sent to a sheet, without sending. Read that sheet each morning against your own knowledge of who has paid. Every row that makes you wince is a rule you have not written yet: a customer on a payment plan, an invoice in dispute, a contact whose phone number belongs to someone who has left.
Then measure the right thing. The number that matters is how long invoices take to be paid, not how many messages went out. Take your average days to pay for the three months before, and compare it with the three months after. Xero already shows who has paid and what is outstanding, so you do not need to build reporting for this. If days to pay has not moved after a quarter, the ladder is not the problem and the terms, the deposit policy or the customer mix probably is.
Keep one manual control. A person should be able to stop all sending with a single switch, and should use it whenever the bank feed has not been reconciled for a few days. An automation that chases on stale data does damage quickly.
Where these builds go wrong
- Building a full email sequence that duplicates what Xero already sends for free.
- Running the daily pull before bank reconciliation, so paid invoices get chased.
- Not re-checking the invoice immediately before the send.
- Texting customers who never agreed to texts, or from an unregistered US number.
- Chasing a disputed invoice because nobody could pause a single record.
- Using OR conditions in the where filter when the Statuses parameter is faster.
- Firing parallel requests and hitting the limit of 5 concurrent calls.
- Treating a 20,000 invoice like a 200 one. The big one deserves a call on day one overdue.
US texting needs registration first, covered in the A2P 10DLC guide. If you are on QuickBooks, read QuickBooks invoice chasing instead. Sector pages for accounting firms and HVAC and plumbing cover where this sits among other workflows, and AI automation cost covers budgets.
Sources checked
Checked in November 2026 against Xero's own pages and published specification.
FAQ
- Does Xero send overdue invoice reminders automatically?
- Yes. Xero's invoicing page says that Xero emails payment reminders for you, before or after the due date, that you choose when and how often to send them, and that with your bank connected Xero stops sending reminders once payment arrives. For many small businesses that is the whole answer and nothing needs building.
- Can Xero send invoice reminders by text message?
- Xero describes its automatic payment reminders as emails. If you want a text to go out for an overdue invoice, you read the invoice from Xero's API and send the message from your own messaging provider. In the US that means registering your number for A2P 10DLC first, and only texting customers who agreed to be contacted that way.
- What are Xero's API rate limits?
- Xero's developer FAQ lists a concurrent limit of 5 calls in progress at one time, a minute limit of 60 calls and a daily limit of 5000 calls, each per connected organisation, plus an app-wide limit of 10,000 calls per minute. Going over returns an HTTP 429 with a Retry-After header. A once-a-day overdue check uses a tiny fraction of that.
- How do I find overdue invoices through the Xero API?
- Call GET /Invoices on the Accounting API. The endpoint accepts a where filter, a Statuses parameter and paging. Ask for sales invoices, which have the type ACCREC, with the status AUTHORISED, then keep those with a due date before today and an AmountDue above zero. Xero's own specification recommends the explicit Statuses parameter over OR conditions in the where filter for faster responses.
- Will my reminders clash with Xero's own?
- They will if you run both on the same day. Either let Xero own the early reminders and start your sequence after its last one, or turn Xero's reminders off for the customers your workflow handles. Decide which before you build. Two reminders for the same invoice on the same morning looks careless.
- How does the automation know an invoice has been paid?
- It asks Xero again immediately before sending. An invoice that has been fully paid shows the status PAID and an amount due of zero. The catch is timing: a payment that has reached your bank but has not been reconciled in Xero still looks unpaid. Reconcile before the daily run, or accept that an occasional reminder will cross with a payment and word the message accordingly.
- Can the API resend the invoice email itself?
- Yes. Xero's specification includes POST /Invoices/{InvoiceID}/Email, described as sending a copy of a specific invoice to the related contact via email. It is useful for a rung that simply says here is the invoice again. It sends Xero's standard invoice email, so for wording you control, send your own message with the online invoice link instead.
- I use QuickBooks, not Xero. Is the approach the same?
- The ladder and the stop-on-payment logic are the same; the API calls differ. The QuickBooks invoice chasing guide on this site covers that build, including the query and the copy for each rung.
- Should the reminder text include a payment link?
- Yes, where you can. Xero's API has an endpoint that retrieves a URL to an online invoice, and a message with a direct link removes the most common reason for delay, which is the customer not being able to find the invoice. Keep the link as a literal value from Xero and never construct it yourself.
Done for you
Want overdue invoices texted, tracked and handed to a person at the right moment?
We build the layer Xero's reminders leave out: the daily pull, the state table, the re-check before every send, registered texting and the handover. The audit that scopes it is free.
The consult is free, and you keep whatever we build.
Keep building
The rest of the cluster
QuickBooks Invoice Chasing: The Real Ladder
Soft at 1-7 days, firmer at 8-14, a human at 15+: the QBO query, stop-on-payment logic and copy for each rung.
Read the guideA2P 10DLC Guide for SMS Automation Builds
Brand then campaign, the sole proprietor route and its caps, published fees, and the real rejection reasons.
Read the guideAutomated Review Requests After Every Job
Completion vs payment vs delay, what Google's policy forbids, and a two-message sequence that catches complaints first.
Read the guideFree AI Automation Audit Template
Score every recurring task and rank the top three worth automating before you build anything.
