FREE N8N TEMPLATE · FINANCE & ADMIN

Every weekday morning in Sydney time, this n8n workflow pulls approved sales invoices that are past due from Xero, works out how overdue each one is, and sends one polite reminder per stage: gentle, firm, then final. Each stage goes once per invoice and is logged in Google Sheets. Invoices marked as disputed or on hold are skipped, and the bookkeeper gets a Slack summary of everything the run did.

DIFFICULTY
Intermediate
SET-UP TIME
About 45 minutes
NODES
15
CHECKED AGAINST
n8n 2.41
  • Xero
  • Gmail
  • Google Sheets
  • Slack

LAST REVIEWED OCTOBER 2026

xero-overdue-invoice-reminders.n8n.jsonLOCKED

Get the free workflow

Leave your email to copy the workflow and paste it straight onto your n8n canvas.

FREE · NO CREDENTIALS INCLUDED · CLOUD OR SELF-HOSTED

001 / HOW IT WORKS

Step by step, node by node

  1. 01Run on weekday mornings

    A Schedule Trigger fires at 8:30am Monday to Friday. The workflow timezone is set to Australia/Sydney, so the run follows daylight saving changes without any edits.

  2. 02Load your reminder settings

    A Set node holds the day thresholds for each stage, the dispute marker text, your business name, sender name, reply-to address and payment details, so you can change them without touching code.

  3. 03Get overdue invoices from Xero

    The Xero node fetches sales invoices with status Authorised, an amount still due, and a due date before today. Draft, paid and voided invoices are never included.

  4. 04Read the reminder log

    Google Sheets returns the Reminder log tab, which records every reminder already sent and any invoice your team has marked On hold or Disputed.

  5. 05Work out the reminder stage

    A Code node calculates days overdue in Sydney time and picks gentle, firm or final. It skips invoices whose Xero reference contains the dispute marker, invoices on hold in the sheet, and stages already sent.

  6. 06Decide whether to send

    An If node passes only invoices that need a reminder today. In parallel, every decision goes to the summary step, including skipped and on-hold invoices.

  7. 07Look up the customer contact

    The Xero node fetches the contact for each invoice to get the billing email address and first name. A Filter node drops contacts with no email address so nothing fails silently.

  8. 08Send the right reminder

    A Switch node routes each invoice to one of three Gmail nodes with fixed wording: a friendly nudge, a firmer request for a payment date, and a final notice saying someone will call.

  9. 09Log the reminder

    Every email sent is appended to the Reminder log with the invoice number, contact, stage, days overdue, amount and time, which also stops the same stage being sent twice.

  10. 10Brief the bookkeeper in Slack

    A Code node groups the run into reminders queued at each stage, invoices skipped as disputed or on hold, and final notices already sent that now need a phone call, then posts it to Slack.

TIERED OVERDUE INVOICE REMINDERS FROM XERO
◷Weekday Mornings≡Reminder SettingsXGet OverdueInvoices▦Read Reminder Log{}Work Out ReminderStage⑂Should We Send?XGet CustomerContact▽Has EmailAddress?⑂Pick ReminderStage@Send GentleReminder@Send FirmReminder@Send Final Notice▦Log Reminder Sent{}Build BookkeeperSummary#Post Summary toSlack

THE REAL WORKFLOW YOU IMPORT · NODE NAMES AS THEY APPEAR IN N8N

002 / WHY IT EXISTS

Chasing late payments is one of the jobs owners and bookkeepers put off. Writing each reminder by hand takes time, the tone drifts depending on the day, and it is easy to forget who was already chased last week. Meanwhile overdue invoices quietly age, and the cash sits in someone else's bank account.

This template is for Australian businesses that invoice from Xero and want consistent, courteous follow-up without handing control to a robot. The wording is fixed and reviewed by you, disputed invoices are left alone, and a person sees a daily summary. Escalation beyond the final reminder, such as a phone call, stays with your team.

WHO IT'S FOR

  • →Service businesses and trades that invoice customers from Xero
  • →Bookkeepers who manage accounts receivable for several clients
  • →Owners who want reminders sent on time without writing each email
  • →Finance teams that need a log of every reminder sent

003 / WHAT YOU NEED

Tick them off as you go. Nothing is saved; it's just a checklist.

004 / SET IT UP

  1. 01

    Import the workflow JSON into n8n and read the Setup Notes sticky note.

  2. 02

    Create a Xero OAuth2 credential and select your organisation in Get Overdue Invoices and Get Customer Contact.

  3. 03

    Open Reminder Settings and set the day thresholds, business name, sender name, reply-to address and your real payment details.

  4. 04

    Create the Google Sheet with a Reminder log tab and the headers Log key, Invoice number, Contact, Tier, Days overdue, Amount due, Sent at and Status, then paste the sheet ID into both Sheets nodes.

  5. 05

    Read the three Gmail nodes and adjust the wording to match how you speak to customers. Keep the tone factual and courteous.

  6. 06

    Connect Gmail and Slack, and choose the channel in Post Summary to Slack.

  7. 07

    Before activating, point the Gmail nodes at your own address, run the workflow manually and check the emails and the Slack summary.

  8. 08

    Agree with your team how to mark disputes: add DISPUTED to the invoice reference in Xero, or add a row to the Reminder log with Status set to On hold.

Get the workflow↑

005 / MAKE IT YOURS

  • +Attach the invoice PDF to each reminder by fetching it from Xero's Invoices endpoint with an HTTP Request node.
  • +Add an online payment link, such as the Xero invoice URL, to each email so customers can pay straight away.
  • +Change the thresholds or add a fourth stage for very old invoices that routes to your debt recovery process instead of an email.
  • +Exclude key accounts or government customers with their own payment terms by checking a contact group in Xero.
  • +Use an AI chat model to draft a personalised note for the final stage, sent to the bookkeeper for approval rather than straight to the customer.

FOR AUSTRALIAN BUSINESSES

Australian businesses chasing their own invoices should still follow the ACCC and ASIC debt collection guideline: be accurate, courteous and avoid contact that could be seen as harassment, which is why the wording is fixed and each stage is sent only once. The schedule runs in Australia/Sydney time; change the workflow timezone if you are in Perth, Brisbane or Adelaide. Amounts are shown in the invoice currency from Xero, so GST-inclusive totals match what the customer received. Keep the Reminder log with your other records; the ATO expects business records to be kept for five years. Customer names and emails are personal information under the Privacy Act 1988, so restrict who can open the log sheet.

Need it hosted in Australia? →

006 / TOOLS IN THIS WORKFLOW

007 / QUESTIONS

Anything else is quicker to answer on a call. Thirty minutes, free, with the people who would build it.

No. Each stage is logged in Google Sheets with a key made from the Xero invoice ID and the stage, and the workflow skips any stage already sent. A customer gets at most three emails per invoice: gentle, firm and final.

We set up n8n end to end: hosting in Australia, connecting your systems, testing with real data and handing over documentation.

Book a free call→