The Deadline That Moves When the Client Does
ASIC review dates, BAS cycles and lodgment concessions all shift based on the client — which means your compliance calendar can't be static. Here's how to track deadlines that move.
Most practices build their compliance calendar once. Quarterly BAS in the last week of each cycle, monthly IAS for the PAYG withholders, tax returns queued against the lodgment program, and ASIC annual reviews slotted in on the company's registration anniversary. Then they treat it as fixed for the year.
The problem is that almost none of these dates are actually fixed. They move — and they move for reasons that live inside the client, not inside your calendar. A client changes their GST reporting cycle. A company deregisters a subsidiary. A new PAYG instalment obligation appears mid-year. A late lodgment knocks a client off their concession. Each of these quietly shifts a deadline, and if your calendar doesn't shift with it, you find out when the client rings about a penalty.
The four deadlines and why each one drifts
It's worth being specific about how each obligation actually moves, because the causes are different.
BAS
A client's BAS cycle isn't a property of your practice — it's a property of their ATO registration. A business under the GST turnover threshold can be monthly, quarterly or annual. When their turnover crosses $20 million they're pushed to monthly whether they like it or not. When a new entity registers for GST partway through a year, its first BAS period rarely lines up with the neat quarterly grid you've drawn. If you're tracking BAS as "Q1, Q2, Q3, Q4" for every client identically, you'll misfile the ones who don't fit the grid.
IAS
Instalment activity statements appear and disappear based on PAYG instalment and withholding status. A client who takes on their first employee suddenly owes an IAS in the months between quarterly BAS. A client whose instalment income drops below the threshold gets varied out of the obligation entirely. The obligation itself is conditional — it's not a date you set once, it's a status you monitor.
Tax returns
Income tax return due dates are the most misunderstood, because for tax agents they're governed by the lodgment program, not the statutory date. And the lodgment program is a moving target. A client who lodges late loses their concessional date and reverts to 31 October the following year. A new client who joins your practice mid-year may or may not have picked up the agent concession, depending on when they were added to your client list with the ATO. The due date you assume and the due date the ATO holds can differ by five months.
ASIC annual reviews
The review date is the anniversary of the company's registration — clean enough, until the company structure changes. New companies get added to a client's group. Old ones get deregistered. A trust gets a corporate trustee added. Each event either creates a new review obligation or removes one, and none of them announce themselves in your workflow.
Why static calendars fail quietly
The failure mode here is subtle. A static compliance calendar doesn't break loudly — it drifts. Ninety percent of your obligations stay where you put them, so the system looks like it's working. It's the other ten percent — the client who changed cycles, the new entity, the concession that lapsed — that generate the penalty notices and the awkward calls.
And because these misses come from client-side changes rather than internal ones, the usual fix — "we need to be more organised" — doesn't touch them. The obligation moved. Being more organised about the old date doesn't help.
Treat obligations as living records, not calendar entries
The shift that actually solves this is to stop thinking of a deadline as a date on a calendar and start thinking of it as a record attached to the client that carries its own status. The right accounting client management software holds each obligation — every BAS period, every IAS, every return, every ASIC review — as its own tracked item, with its own due date derived from that client's actual registration details, not a generic grid.
When an obligation is modelled this way, three things become possible:
- The due date can be driven by the client's real cycle. A quarterly client and a monthly client generate different BAS obligations automatically, rather than being forced into the same schedule.
- Concessional dates can reflect the lodgment program. A tax return sits against the agent-concession date the client actually holds, not the statutory fallback — and if that concession is at risk, the obligation shows it.
- Structural changes propagate. Add a company to a client group and its ASIC review obligation appears. Deregister one and it stops generating work.
This is where the line between client accounting software that tracks the numbers and practice software that tracks the obligations matters. Your ledger tells you what happened. Your practice system needs to tell you what's owed, when, and to whom — and to keep that answer current as the client changes underneath it.
Where Finye fits
Finye tracks ATO and ASIC compliance deadlines as rolling obligations tied to each client, so BAS, IAS, tax returns and ASIC reviews carry their own due dates and statuses rather than living on a spreadsheet you rebuild every July. Because client records sync two ways with Xero and hold the ABNs, ACNs and registration details behind each entity, the deadlines it surfaces reflect the client as they actually are — not as they were when you set the calendar. It doesn't lodge anything for you; it makes sure nothing falls off the list before you get to it.
A practical starting point
You don't need to rebuild everything to close the drift. Start with the obligations most likely to move:
- Audit your BAS cycles against each client's actual ATO registration, not your assumed grid. Flag anyone who registered mid-year or crossed a turnover threshold.
- Confirm lodgment concessions for every client whose return date you've assumed, especially clients who joined in the last twelve months or lodged late last cycle.
- Reconcile your ASIC review list against the companies actually in each client group after any structural changes.
Do that once, then hold each obligation as a living record that updates when the client does. The deadlines stop drifting — not because you watch them harder, but because they're finally attached to the thing that actually moves them.