The Deadline Calendar You Rebuild Every Lodgment Season
Most firms track BAS, IAS, tax returns and ASIC reviews across spreadsheets, Xero and memory. Here's how to run one living compliance calendar instead.
Every lodgment season, a version of the same scene plays out in Australian practices. Someone opens a spreadsheet that was last reliable three months ago. Someone else cross-checks it against the Tax Agent Portal and the client list in Xero. A third person remembers that one client who always lodges monthly, and another who moved from quarterly to monthly after a cash-flow wobble. By the time the list looks trustworthy, half a day is gone — and that list starts rotting the moment it's finished.
The problem isn't that firms don't know their deadlines. BAS, IAS, tax returns and ASIC annual reviews are all knowable, published and predictable. The problem is that the information lives in too many places, and no single source stays current without constant manual effort.
Why the deadline calendar keeps falling apart
Compliance dates aren't hard to find. What's hard is keeping a live, accurate, firm-wide view of which client owes what, by when, and who's responsible. A few forces work against you:
- Obligations change. A client shifts from quarterly to monthly BAS. A new entity needs an IAS. A company deregisters. Each change should ripple through your calendar, but usually it only lives in one person's head.
- Cycles overlap. December quarter BAS, FBT season, tax return extensions and ASIC review dates all stack up in ways that aren't obvious until the week they land.
- The data is split. Client details sit in your client accounting system. Lodgment status sits in the portal. Who's doing the work sits on a whiteboard, a job board or in email.
So the calendar gets rebuilt — not improved, rebuilt — because nobody trusts last season's version enough to just update it.
The three failure points in most compliance tracking
1. Obligations aren't attached to the client record
When a client's BAS cycle lives in a spreadsheet rather than on the client's actual record, every change becomes a two-step task: update the client, then remember to update the tracker. The second step is the one that gets skipped. Over a year, your tracker drifts from reality, and you only find out when something's late.
The fix is to treat the obligation as a property of the client, not a line in a separate document. If a client's record knows it has quarterly BAS, monthly IAS and an annual ASIC review in March, the calendar builds itself from the client list — and updating the client is the only thing you ever do.
2. Deadlines exist without owners
A date on a shared calendar with no name against it belongs to everyone, which means it belongs to no one. The classic overdue lodgment is rarely one nobody knew about — it's one everyone assumed a colleague was handling. Every compliance deadline needs a single responsible person and a visible status, so "in progress" and "waiting on the client" are never confused with "done".
3. No buffer between the internal date and the real date
If your team works to the ATO's actual due date, you have zero room for a client who sends their records late, a query that needs a partner's eyes, or a portal outage on the last day. Smart firms set an internal deadline a week or two ahead of the statutory one and manage to that. The external date is the cliff edge; the internal date is where the work is supposed to be finished.
What a living compliance calendar actually looks like
A calendar you can trust has a few characteristics that a rebuilt-every-season spreadsheet never has:
- It generates recurring work automatically. Quarterly BAS shouldn't be a thing someone remembers to create four times a year. The obligation recurs, so the job recurs — appearing on a board with the right due date, assignee and checklist already attached.
- It reflects reality, because it's built from your client data. Add a client, set their obligations once, and they're in every future cycle. Change a cycle, and future jobs follow.
- It shows status at a glance. Not just a date, but where each job sits — not started, waiting on PBC, in review, lodged.
- It warns you early. Approaching internal deadlines surface before they're urgent, so a buffer exists by design rather than by luck.
This is where practice management software earns its place. The difference between a tax return software tool and genuine accounting client management software is exactly this: one helps you prepare and lodge a single return, the other runs the whole obligation around it — knowing who the client is, what they owe, when it's due, who's doing it and whether it's moved.
Where Finye fits
Finye isn't a lodgment tool and it isn't a ledger — it's the layer that tracks the obligations and runs the practice around the work. Compliance dates for BAS, IAS, tax returns and ASIC reviews sit against each client's record, so your calendar is built from your client list rather than rebuilt from scratch each season. Recurring jobs generate automatically on their cycles, land on a board with an owner and a due date, and surface before the statutory deadline so your internal buffer holds. Because client details sync two ways with Xero, the record that drives your calendar stays accurate without double entry.
The result is a calendar that updates when your clients change — not one you reconstruct every quarter.
How to move off the rebuild cycle
You don't need to fix everything at once. A practical order:
- Audit obligations by client. For each client, confirm BAS cycle, IAS requirements, tax return status and ASIC review date. Do this once, properly.
- Attach obligations to the client record in your client accounting system, not a separate sheet.
- Set recurring jobs so each obligation generates its own work automatically on schedule.
- Assign an owner to every recurring job — no unassigned deadlines.
- Set internal due dates ahead of statutory ones and work to those.
After one full cycle, you'll notice the difference: next quarter's BAS run isn't a half-day of spreadsheet archaeology, it's a board that's already populated, already assigned and already accurate. The calendar stops being a seasonal project and becomes something that simply runs — which is what compliance tracking was always meant to be.