The Deadline Owner: Who Actually Answers for a Late BAS?
A missed BAS or ASIC review is rarely one person's fault — it's usually nobody's job. Here's how to assign clear ownership to every ATO and ASIC obligation.
Ask most practice owners who is responsible for a specific client's quarterly BAS and you'll get a confident answer. Ask who is responsible for every BAS, IAS, tax return and ASIC annual review across the whole client base — this quarter, next quarter, and the one after — and the answer gets vaguer. It becomes "the team" or "the compliance calendar" or "we've got a system for that."
The problem is that "the team" can't be held to account, and a calendar doesn't chase anyone. When a deadline slips, the post-mortem almost always lands on the same finding: the obligation existed, everyone could see it, and no single person had actually taken ownership of getting it done. It fell through the gap between people, not off the edge of the calendar.
Why deadlines slip even when you track them
Every firm tracks deadlines somewhere. Spreadsheets, a whiteboard, the due-date list inside your lodgment software, reminders in Outlook. Tracking a due date is not the hard part. Australian compliance dates are published, predictable and mostly fixed.
What tracking doesn't do is answer the question that matters when things go wrong: whose problem is this right now? A due date tells you when. It doesn't tell you who, and it doesn't tell you what state the work is in.
Consider a single quarterly BAS. Between the obligation appearing and the lodgment happening, the work passes through several hands:
- Someone has to request the source data from the client.
- Someone has to chase it when it doesn't arrive.
- Someone has to prepare and reconcile.
- Someone has to review.
- Someone has to lodge and confirm.
If the same due date is "owned" at every stage by whoever happens to touch it next, then it's owned by no one in particular. The client who hasn't sent their records sits in limbo because chasing them is technically five people's job and therefore nobody's.
Two kinds of ownership you're probably conflating
Firms tend to blur two very different responsibilities into one word — "owner" — and it causes real confusion.
The obligation owner
This is the person accountable for the outcome: the BAS gets lodged on time, the ASIC review gets actioned, the tax return goes in before the due date. This person doesn't necessarily do every task. They're the one who answers for it. There should be exactly one obligation owner per obligation, and it should never be "the team."
The task owner
This is whoever holds the current step. It changes as the work moves — from the person chasing documents, to the preparer, to the reviewer. Task ownership is fluid by design. Obligation ownership must not be.
When a deadline is at risk, the obligation owner is the person you go to. They can see where the work is stuck and either unstick it or escalate. Without that role, escalation has nowhere to go, and the first time the partner hears about a problem is when the ATO does.
Map ownership across the whole obligation type, not just the client
Here's a distinction that trips up growing firms. It's easy enough to say "Priya looks after the Nguyen family group." But obligations don't respect client boundaries evenly. Priya might own the Nguyen tax returns while a bookkeeper owns their monthly IAS and someone in admin owns the ASIC annual review that lands on the company anniversary.
That's fine — as long as each of those obligations has a named owner. The failure mode is when the ASIC review has no owner at all because it isn't part of the regular BAS rhythm and quietly falls outside everyone's mental model of the client. ASIC annual reviews are notorious for exactly this: they arrive on the registration anniversary, not the tax calendar, so they sit outside the quarterly grind and get forgotten until a late fee appears.
What good ownership looks like in practice
You don't need new software to think about ownership clearly — but you do need a system that lets you record it against every obligation and see it in one view. This is where account practice management software earns its place over a general to-do list or the due-date screen in a tax return tool.
A capable accounting client management software setup should let you:
- Generate recurring obligations automatically from each client's profile — BAS cycle, IAS frequency, income tax, ASIC review date — so nothing depends on someone remembering to create the job.
- Assign a single obligation owner to each recurring job, separate from whoever currently holds the active task.
- Show every upcoming obligation on one rolling wall, filtered by owner, so each person sees exactly what they answer for and by when.
- Track status independently of the due date — waiting on client, in prep, in review, ready to lodge — so a deadline that's three weeks out but stuck at "waiting on client" surfaces as a risk now, not the night before.
In Finye, recurring compliance jobs are created from each client's obligations and land on a shared board with a named owner and a live status. The rolling deadline view lets a manager scan every BAS, IAS, return and ASIC review in one place and immediately spot the ones that have a due date but no movement — the early warning that ownership has gone quiet.
The weekly question that prevents most misses
Once ownership is explicit, your compliance rhythm changes shape. Instead of a frantic scramble as each deadline approaches, you run a short, regular review built around one question, asked of each owner: "Which of your obligations are at risk, and what's blocking them?"
Because ownership is singular, there's always someone to ask. Because status is separate from the due date, "at risk" means something concrete — the work isn't moving — rather than simply "getting close." And because everything sits on one wall, nothing outside the normal cycle, like an ASIC review, can hide.
This is the quiet advantage of treating client accounting as a system of owned obligations rather than a calendar of dates. Dates are easy. They're published a year in advance. The hard part has always been human: making sure that for every single obligation, one identifiable person can honestly say, "Yes, that's mine, and here's exactly where it stands."
Get that right and late lodgments stop being a recurring surprise. They become the rare exception you saw coming — and had time to fix.