The Deadline No One Owns Until It's Overdue
BAS, IAS, tax returns and ASIC reviews all have hard dates — but ownership is where most firms slip. Here's how to make every obligation belong to someone.
Every accounting and bookkeeping practice knows the dates. The 28th for quarterly BAS. The 21st for monthly IAS. The staggered tax return concessions that come with being a registered agent. The annual ASIC review that lands on the anniversary of a company's registration. None of this is a mystery.
And yet deadlines still get missed. Not because nobody knew the date, but because nobody clearly owned the work leading up to it. A deadline sitting in a shared calendar or a lodgment program is a fact, not a task. It doesn't chase itself. It doesn't know whose desk it belongs on. It just waits — quietly — until it's suddenly overdue and everyone's asking who was supposed to handle it.
Why compliance dates fall through the cracks
The dates themselves are the easy part. The failure points sit in the space between knowing a deadline exists and someone actually doing the work in time. In most firms, that space is filled with a patchwork of tools that don't talk to each other:
- The lodgment program knows the tax return and BAS concession dates, but it doesn't track ASIC review dates at all.
- ASIC review dates live in corporate register software or a spreadsheet someone updates once a year.
- IAS obligations are half-remembered, half-derived from what the client did last quarter.
- The actual work — collecting records, preparing figures, getting a signature — sits in email, in someone's head, or in a job that never got assigned.
When your obligations are scattered across three or four places, no single view tells you what's due, when, and who's on it. So the deadline you track twice ends up being the deadline nobody actually owns.
Ownership is the missing field
The fix isn't a better calendar. It's treating every compliance obligation as a piece of work with a name attached to it — from the moment the date is known, not the week it's due.
Think about what an ASIC annual review actually involves. It's not just a date. It's confirming the company details are current, sending the company statement, following up if there are changes, chasing payment of the annual fee, and confirming the solvency resolution. That's a sequence of steps, and each one needs an owner. When the review date sits alone in a register with no linked work item, all of that quietly becomes the responsibility of whoever happens to notice first.
The same applies across the board:
- A BAS isn't done when you know it's due — it's done when someone has the records, prepared the figures, had them reviewed and lodged them.
- An IAS needs the same discipline, just more frequently and with less fanfare, which is exactly why it slips.
- A tax return under a concession date can feel far away in July and suddenly urgent in April — with the buffer eaten by one client who's slow to respond.
Every one of these should exist as an assigned work item well before the due date, so the question "who's got this?" has an answer before it becomes urgent.
One register for BAS, IAS and ASIC
This is where consolidating your compliance tracking pays off. When BAS, IAS, tax return and ASIC review dates all live in one system alongside the work itself, three things change.
You see everything due in one place
Instead of cross-referencing your lodgment program against a separate ASIC register against a spreadsheet of IAS clients, you look at one list. Filtered by date, by client, by staff member. The ASIC review date that isn't in your lodgment program stops being invisible, because it's in the same view as everything else.
Recurring obligations generate their own work
Quarterly BAS, monthly IAS and annual reviews are predictable. They should generate the work automatically. In Finye, recurring jobs create the work item, assign an owner and set the deadline off the back of each obligation — so a new BAS quarter doesn't depend on someone remembering to spin up a job. The obligation and the task arrive together, already owned.
The register stays current because it's the same system you work in
Registers go stale when updating them is a separate chore. When your client accounting records, entity details and compliance dates live in the same place your team does the work — and when that data stays in step with Xero — the register isn't a document you maintain on the side. It's a byproduct of running the practice.
Build the buffer in, don't hope for it
Knowing the date and owning the work still leaves one gap: the buffer. A tax return due in May doesn't mean you start in May. An ASIC review sent on the due date leaves no room for the client to spot an error. Good account practice management software lets you set an internal target ahead of the statutory date, so the work surfaces on your team's boards with time to absorb a slow response or a review that bounces back.
The practices that never miss deadlines aren't the ones with better memories. They're the ones who assume something will go slightly wrong — a client who's away, a signature that takes a week, a figure that needs a second look — and give themselves the days to handle it.
Make the deadline belong to someone
A compliance calendar tells you what's due. It doesn't tell you what's done, what's blocked, or who's carrying it. The shift that stops deadlines slipping is small but fundamental: stop treating obligations as dates to remember and start treating them as work that belongs to a person from day one.
That means one register for BAS, IAS, tax returns and ASIC reviews. It means recurring jobs that create and assign the work automatically. It means client details that stay current because they're part of the same system your team already uses. And it means an internal buffer built into the calendar, not left to luck.
Do that, and the phrase "the deadline no one owns" simply stops applying — because every deadline has a name against it long before it's ever at risk of being overdue.