The Deadline That Depends on the Client You Haven't Chased
ATO and ASIC deadlines aren't fixed — many shift based on lodgment status, agent concessions and client responses. Here's how to track the ones that move.
Every practice owner knows the headline dates. BAS quarters. The 15 May concession. ASIC annual review on the company's registration anniversary. You could recite them in your sleep. But the deadlines that actually bite aren't the fixed ones — they're the ones that depend on something you haven't done yet, or something the client hasn't done yet.
A client's tax return due date can hinge on whether their prior-year return was lodged on time. An ASIC annual review payment date is set, but the 28-day window to respond before penalties accrue depends on when the company statement issues. An amended BAS, a new client with a messy lodgment history, a late PBC list — all of these quietly reshape the deadline you thought you knew.
Treating compliance dates as static is where firms get caught. The real skill is tracking deadlines that are conditional — and knowing which condition is still open.
Why the standard calendar isn't enough
Most firms run their compliance year off a lodgment-program spreadsheet or a shared calendar. It lists the concessional dates for BAS, IAS, income tax returns and ASIC reviews. That's a fine starting point, but it assumes two things that often aren't true:
- That every client sits in the standard category. A new client who lodged late last year may have lost their concession and sit on an earlier date. A client who ceased trading mid-year has a part-year obligation the calendar never anticipated.
- That the deadline isn't waiting on an input. You can't lodge a return you don't have the records for. The BAS due date is fixed; the date you can actually start depends entirely on when the client hands over their data.
So the deadline on the calendar is really two dates pretending to be one: the date the obligation is due, and the date the work can realistically begin. When those drift apart, the gap is where overdue lodgments live.
The three ways a deadline moves
1. The client's lodgment history changes the date
Tax agent concessions are generous, but they're conditional on good standing. Pick up a client with outstanding prior-year returns and their current obligations may not carry the usual concessional dates. If your register still shows the standard 15 May, you're planning around a date the ATO doesn't recognise for that client.
The fix is to record the real, client-specific due date against each obligation — not the generic one — and to flag when a client's status is unknown or in question. A deadline you can't verify should never sit in your register looking settled.
2. The obligation itself appears or disappears
A company deregisters. A sole trader registers for GST and picks up quarterly BAS. A client moves from monthly IAS to quarterly. ASIC updates a company's review date after a change of details. Each event adds, removes or shifts an obligation — and none of them announce themselves on your spreadsheet.
This is the quiet failure mode: the deadline that should exist but was never entered, because the triggering event happened between calendar rebuilds. The client registers for GST in August, and nobody adds the September-quarter BAS until a reminder lands in November.
3. The work can't start until the client responds
This is the most common and the most frustrating. The due date hasn't moved — but your capacity to meet it has, because you're still waiting on bank statements, a signed engagement letter, or an answer to one question. The deadline is fixed; the runway shrinks every day the reply doesn't come.
Here the problem isn't your register at all — it's the chase. If the deadline and the outstanding client request aren't connected in your system, you find out you're blocked when you open the file, not when the request first went unanswered.
Building a register that moves with the obligation
A compliance register earns its keep when it reflects reality on any given morning, not the plan you set in July. A few principles help:
- Store the client-specific due date, not the generic one. Each obligation should carry the date that actually applies to that client, given their lodgment status and agent position.
- Tie each deadline to an owner and a next step. A date with no owner is a date no one is watching. A deadline with no next action is one that's quietly stalled.
- Link the deadline to what it's waiting on. If the job can't start until a PBC item arrives or an engagement letter is signed, that blocker should be visible on the deadline itself — so a looming date and an unanswered request are never two separate facts in two separate screens.
- Re-derive dates when the trigger changes. A new GST registration should create the BAS obligations automatically. A deregistration should close them. The register should respond to events, not wait for the next manual rebuild.
Where good client accounting software helps
This is the gap generic tools leave open. A spreadsheet can't know a client registered for GST. A calendar can't tell you a return is blocked on a missing document. And a tax return software product handles the lodgment itself — but it isn't built to run the practice around the obligation: the tracking, the chasing, the ownership, the buffer before the date arrives.
That's the role of proper account practice management software. In Finye, compliance obligations live on boards alongside the work items that satisfy them, and recurring jobs for BAS, IAS and ASIC reviews generate on schedule rather than being rebuilt each season. Because client records, the portal, engagement letters and two-way Xero sync all sit in one system, the deadline and the thing it depends on aren't scattered — a blocking PBC request, an unsigned engagement letter or a client that hasn't replied shows up against the job it's holding up. The register tracks the obligation; the practice tracks the work around it.
The habit worth building
Stop asking "what's due this month?" and start asking "which of these deadlines depends on something that isn't settled yet?" The fixed dates look after themselves. It's the conditional ones — the client you haven't verified, the obligation that just appeared, the reply you're still waiting on — that turn a comfortable buffer into a late-night scramble.
A register that only shows dates is a wish list. A register that shows dates, owners and what each one is waiting on is a plan you can actually run a lodgment season on.