The Rolling Deadline Wall: Seeing Every Obligation at Once
BAS, IAS, tax returns and ASIC reviews don't queue politely. Here's how to build a single view of every compliance deadline so nothing slips through.
Most practices don't miss deadlines because they're lazy. They miss them because the obligations live in different places. BAS dates sit in one head, ASIC annual review dates arrive by post to whoever opens the mail, and tax return due dates depend on a lodgment program schedule that few people actually read end to end. Each obligation is manageable on its own. Stacked together, across a few hundred clients, they form a rolling wall of dates that never stops moving.
The firms that stay calm through BAS quarters and October aren't working harder. They've just made every obligation visible in one place, well before it's due. Here's how to build that.
Why compliance deadlines are uniquely hard to track
Compliance dates behave differently from ordinary work. Three things make them slippery:
- They're externally set. You don't choose when a BAS is due or when an ASIC annual review falls — the date is fixed by the client's registration and reporting cycle, not by your capacity.
- They repeat on different clocks. Monthly IAS, quarterly BAS, annual tax returns and annual ASIC reviews all cycle at different rhythms, so the mix of what's due changes every month.
- They're spread across systems. ATO obligations sit in the portal, ASIC review dates arrive independently, and your tax return list depends on your lodgment program. No single source tells you everything.
The result is that no one person can hold the full picture. And when the picture lives only in individuals' heads, it walks out the door when someone takes leave or resigns.
The four obligation streams you're actually tracking
Before you build a view, name what goes into it. For most Australian firms, the compliance calendar is really four overlapping streams:
1. BAS and IAS
Activity statements are the highest-frequency obligation and the easiest to lose count of. Monthly IAS clients, quarterly BAS clients, and clients on both create a constant drip of due dates. Whether you're lodging or the client self-lodges, you still want the date on your radar so you can prepare, review or chase.
2. Tax returns
Income tax returns are governed by the lodgment program, which staggers due dates based on client type and prior-year lodgment status. This is where a lot of firms get caught: they assume everything is due 15 May, forget the earlier dates for clients with prior-year returns outstanding, and lose the concessional dates they were entitled to.
3. ASIC annual reviews
Every company has an annual review date tied to its registration anniversary. Miss it and there are late fees and, eventually, deregistration risk. These dates are easy to overlook because they don't come through the same channel as ATO work and they land year-round rather than clustering in quarters.
4. Ad hoc and one-off obligations
FBT returns, TPAR, superannuation guarantee statements, deferrals you've negotiated — the long tail. Individually rare, collectively enough to trip you up if they live on sticky notes.
Building the deadline wall
The goal is a single view where anyone in the firm can see what's due, for whom, when, and who owns it — without opening five systems. A few principles make that view actually work.
Attach obligations to the client, not to a person's memory
Each obligation should be a data point on the client record: this company has an ASIC review on this date, this client lodges quarterly BAS, this entity has a tax return due on this lodgment-program date. Once the obligation is structured data rather than tribal knowledge, it survives staff turnover and leave.
This is where good accounting client management software earns its keep. In Finye, compliance obligations sit against the client record and generate work items on your boards automatically as their due dates approach — so a quarterly BAS client produces a BAS job each quarter without anyone remembering to create it. The client list drives the calendar, not the other way around.
Make recurring work recur automatically
Anything that happens on a fixed cycle — monthly IAS, quarterly BAS, annual returns — should be generated by a recurring job template, not created by hand each period. Manual creation is where things get skipped: one busy week, one distracted moment, and a client silently drops off the list. Recurring jobs mean the obligation appears whether or not anyone was paying attention.
Use lead time, not the due date
A deadline wall built on due dates alone is a wall you hit. Build in lead time so work surfaces early enough to actually do it. A tax return due 15 May shouldn't first appear on someone's board on 14 May. Set jobs to open weeks ahead, with internal target dates that sit comfortably before the statutory date. The statutory date is the cliff; your internal date is the fence.
Track status, not just dates
Knowing something is due isn't enough — you need to know where it is. Not started, awaiting client records, in progress, in review, ready to lodge, lodged. A board that shows status against every obligation turns "is the Smith BAS done?" from a conversation into a glance.
The review rhythm that keeps the wall honest
A deadline view is only as good as the habit around it. Two rhythms matter:
- A weekly compliance stand-up. Fifteen minutes looking at what's due in the next two to four weeks, what's stuck, and what's waiting on clients. This catches the "waiting on records" jobs that quietly age past their date.
- A monthly forward look. One session each month to eyeball the next quarter's shape — which weeks are heavy, where BAS clusters collide with ASIC reviews, whether you need to start chasing records earlier than usual.
The forward look is what turns a compliance calendar from a reactive alarm system into a capacity-planning tool. When you can see that late April and early May are stacked, you can pull work forward in March instead of drowning later.
What good looks like
You know the wall is working when a few things become true. Any staff member can answer "what's due for this client and when" without asking around. Nobody discovers an ASIC review after the late fee has hit. Deferrals you've arranged are tracked as new dates, not forgotten concessions. And when someone goes on leave, their obligations don't leave with them — they're visible to whoever picks up the work.
None of this requires a separate tax return software for tracking, a spreadsheet for BAS, and a diary reminder for ASIC. The point of consolidating client accounting and practice management into one system is exactly this: every obligation, every client, every due date, in one view that the whole firm trusts. Get that right and compliance season stops being a scramble and starts being a schedule.