To automate BAS and GST reminders for accounting clients, you connect your practice's due-date data (from Xero, your workpapers, or a lodgement register) to an automation tool like Zapier or n8n, then trigger a timed sequence of emails and SMS messages that ask each client for their documents at set intervals before the ATO due date. The system chases the client, logs who has responded, and only escalates to a human when a deadline is genuinely at risk. Done properly, it removes the most repetitive and easily-forgotten task in the quarterly cycle without letting anything slip.
This article is for practice managers and partners at small-to-mid accounting firms who lodge BAS for a book of clients and are tired of manually emailing the same reminder to 40 people every quarter. It assumes you already use Xero (or similar) and want a concrete build, not a theory lecture.
Why the BAS reminder problem is worth automating
Chasing clients for records is high-volume, low-judgement work. Every quarter the same pattern repeats: you email everyone, a third respond promptly, a third respond after a nudge, and the last third only move when someone calls them the week before lodgement. The judgement part — reviewing the numbers, deciding what to lodge — stays with your team. The chasing part does not need a person at all.
That makes it an ideal first automation. It is predictable, it runs on a fixed calendar, and the cost of forgetting is real: late lodgement risks penalties for the client and a difficult conversation for you. If you are weighing this against other admin tasks, our guide to what admin work to automate before hiring another staff member is a useful sanity check.
What are the ATO quarterly BAS due dates?
The reminder sequence has to be anchored to the real lodgement calendar. For standard quarterly BAS lodged through a registered tax or BAS agent, the ATO generally allows a later concession date than self-lodgers get. As a rough map of the quarterly cycle:
| Quarter | Period covered | Standard due date (self-lodge) | Typical agent concession |
|---|---|---|---|
| Q1 | Jul – Sep | 28 October | Later date via agent |
| Q2 | Oct – Dec | 28 February | 28 February |
| Q3 | Jan – Mar | 28 April | Later date via agent |
| Q4 | Apr – Jun | 28 July | Later date via agent |
Verify these against the current ATO calendar before you build. Concession dates and lodgement program dates change, some clients are monthly lodgers, and public holidays shift due dates. Never hard-code a date into your automation that you have not checked for the current year. The safest design pulls the due date from your practice software rather than a static table.
The building blocks you need
A working reminder system has four parts:
- A source of truth for due dates. This is your lodgement register, Xero's due-date fields, or a practice management tool like FYI, Ignition, or a simple Airtable base. Each client record needs their BAS frequency, their due date, and whether they have submitted this period.
- An automation engine. Zapier for a straightforward build, or n8n if you want more control and lower per-task cost at volume. Our comparison of n8n vs Zapier for professional services firms covers which suits your situation.
- A messaging channel. Email for the detail, SMS (via Twilio, ClickSend or similar) for the short, hard-to-ignore nudge close to the deadline.
- A response tracker. Somewhere the system marks a client as "documents received" so it stops chasing them. This can be as simple as a status column in your Airtable base or a tag in your practice software.
How to build the reminder sequence, step by step
Here is a practical sequence for a quarterly BAS client. Adjust the timing to your firm's internal deadlines, which should sit comfortably ahead of the ATO date.
- Set your internal cut-off. Decide when you need documents in hand to lodge without stress — say, 14 days before the ATO due date. Every reminder counts backwards from there, not from the ATO date itself.
- Reminder 1 (21 days before your cut-off): a friendly email. "Your [quarter] BAS is coming up. Please send through your records by [date]." Include exactly what you need and how to send it.
- Reminder 2 (10 days before cut-off): a follow-up email, only to clients not yet marked as received. Slightly firmer, restating the date.
- Reminder 3 (3 days before cut-off): an SMS. Short and specific: "Hi [name], we still need your BAS records to lodge on time. Reply or call us today."
- Escalation (at cut-off): instead of another automated message, the system creates a task for a staff member to call the client personally. This is the point where a human takes over.
The critical design rule: every step checks the response tracker first. A client who sent their records after reminder 1 should never receive reminder 2. Nothing damages trust faster than an automated system chasing someone who has already done the thing.
Pulling due dates from Xero instead of hard-coding them
The more robust version of this build reads the activity statement due date directly rather than relying on a spreadsheet you update by hand. Xero holds BAS period and due-date information, and its API can surface it to your automation engine, so the sequence recalculates itself each quarter. For the broader picture of what Xero can feed into automations, see our practical guide to Xero AI automation for accountants.
If an API build is more than you want to take on initially, start with a maintained Airtable or Google Sheet as the source of truth and upgrade later. A manual register that actually gets updated beats an elegant integration that nobody owns.
Where AI genuinely helps — and where it doesn't
Most of this workflow is plain automation: triggers, conditions and messages. That is deliberate. You do not want a language model deciding when a lodgement is due.
Where AI earns its place is in the softer edges. It can draft warmer, client-specific reminder copy so every message doesn't read like a form letter. It can summarise which clients are outstanding into a plain-English digest for your Monday morning. It can categorise incoming client replies — "sent everything", "partial", "question" — so your team triages faster. These are the same kinds of admin wins we cover in AI for accountants: 5 admin tasks you can automate.
Keep AI away from anything involving the actual numbers, the lodgement decision, or a client's specific tax position. Those stay with your registered agents. Automation chases the documents; people do the accounting.
What goes wrong, and how to catch it early
- Stale due dates. The single biggest risk. If a date is wrong, the whole sequence fires on the wrong schedule. Verify against the current ATO calendar every year and test one quarter before trusting it fully.
- Chasing clients who already replied. This happens when the response tracker isn't updated in real time. Make marking a client "received" a one-click action your team actually does, or automate it from your document intake.
- Messages landing in spam. Sending 40 identical emails from an automation tool can trip spam filters. Send from your real domain with proper authentication, and vary the copy slightly.
- SMS to wrong or old numbers. Clean your client contact data before you switch SMS on. A failed text is invisible unless you check delivery reports.
- Over-messaging. Three reminders plus a call is firm but reasonable. Five automated nudges in a fortnight reads as harassment. Resist the urge to add more steps.
Because this workflow touches client contact details and BAS information, it should sit inside your firm's data-handling obligations. Our overview of AI and client data under the Australian Privacy Act is worth reading before you connect systems that move personal information around.
When you shouldn't automate this yet
If your client data is messy — wrong emails, missing phone numbers, no reliable record of BAS frequency — fix that first. An automation built on bad data will confidently send the wrong message to the wrong person at scale. Spend a quarter cleaning your register before you automate the chasing.
Likewise, if you only lodge for a handful of clients you speak to regularly, a full automated sequence is overkill. A shared checklist and a recurring calendar reminder may serve you better. Automation pays off when the volume is high enough that manual chasing genuinely costs you hours each quarter.
What it costs and who owns it
The running cost is modest: an automation tool subscription plus SMS charges per message. The real cost is the initial build and, more importantly, ownership. Someone in your firm has to own the response tracker and verify the dates each year. An automation nobody maintains quietly drifts out of date and becomes a liability. For realistic figures, see how much AI automation costs for a small firm in Australia.
If you want a shortlist of automations worth building before this one — and a sense of how they fit together across a practice — our free guide, 10 AI Workflows to Save 10+ Hours a Week, walks through the highest-value places to start and how to sequence them without overwhelming your team.
Common questions
What data do I need before automating BAS reminders?
You need a reliable record for each client showing their BAS lodgement frequency, their due date for the current period, a valid email address and mobile number, and a status field marking whether they've submitted their documents. If any of that is inaccurate, clean it before you automate, because the system will send wrong messages at scale otherwise.
Should reminders be timed to the ATO due date or my own deadline?
Time them to your internal cut-off, not the ATO date. Set a cut-off comfortably ahead of the lodgement deadline, then count reminders backwards from there. This gives your team time to review and lodge without a last-minute scramble, and builds a buffer for clients who respond slowly.
Can I pull BAS due dates automatically from Xero?
Yes. Xero holds activity statement period and due-date information, and its API can pass that to an automation tool like Zapier or n8n so your sequence recalculates each quarter. If an API build is too much initially, use a maintained spreadsheet or Airtable base as your source of truth and upgrade later.
Is it worth adding SMS or is email enough?
Email works well for early reminders because it carries detail about what you need. SMS is far more effective for the final nudge close to your cut-off, since texts are read quickly and rarely ignored. A common approach is two emails followed by one SMS, then a personal phone call if the client still hasn't responded.
What part of this should stay human?
Keep the lodgement decision, the review of the numbers, and any advice about a client's tax position entirely with your registered agents. Automation should only chase documents and track responses. The final escalation, when a deadline is genuinely at risk, should also be a personal phone call rather than another automated message.
Want these ideas working in your firm? We build controlled AI workflows for Australian professional services firms — starting with a free automation audit.