The Deadline Register You Can't See All at Once
BAS, IAS, tax returns and ASIC reviews all land on different cycles. Here's how to stop tracking them in four separate places and see the whole obligation load at once.
Most practices don't miss deadlines because they forget what the deadlines are. They miss them because the obligations live in four or five different places, and no one person ever sees the full picture at the same time.
BAS cycles sit in one spreadsheet. IAS obligations for pay-as-you-go instalment clients are tracked differently again. Tax return due dates depend on the client's lodgment history and whether they're on a tax agent's program. ASIC annual reviews land on the anniversary of each company's registration — dates that have nothing to do with the financial year and everything to do with when the entity was set up.
Each system is probably fine on its own. The problem is the seams between them. When your compliance load is spread across tools that don't talk to each other, the risk isn't any single deadline — it's the one that falls into the gap.
Why four calendars become zero calendars
A spreadsheet of BAS due dates works until the person who maintains it takes leave. The ASIC review dates sit in your corporate register software, which only the person who handles company secretarial work logs into. Tax return cycles are tracked by whoever runs the lodgment program report. IAS obligations get remembered because someone has done them so many times they've become muscle memory.
None of this is a system. It's a collection of habits held together by a few experienced people. And the moment one of those people is busy, sick, or newly hired, the coverage drops without anyone noticing.
The tell-tale sign is the scramble. If lodgment season involves someone cross-referencing three reports to work out what's actually due and who's doing it, you don't have a register. You have a reconstruction exercise that you repeat every quarter.
What a single obligation view actually needs
Good client accounting software doesn't just store a list of due dates. It connects each obligation to the client, the entity, the person responsible, and the current status of the work. That connection is what turns a date into something you can manage.
A proper compliance view should let you answer these questions in seconds, without opening anything else:
- What's due in the next 30 days, across every obligation type, not just BAS?
- Which of those have work already in progress, and which haven't been started?
- Who owns each one, so nothing sits in the assumed-someone-else's-job zone?
- What's blocked because a client hasn't sent records or signed an engagement?
Notice that only one of those questions is about the date itself. The rest are about the state of the work. A deadline you can see but can't act on is just a warning light with no instructions attached.
ASIC reviews are the ones that catch firms out
BAS and IAS cycles are regular and predictable, so most firms build routines around them. Tax return due dates follow the lodgment program, which is at least documented. ASIC annual reviews are the quiet risk because they're scattered across the year on registration anniversaries, carry fees and late penalties, and often sit with whoever happens to handle company matters rather than with a defined process.
When a company's review date passes without action, the client gets the ASIC notice before you do. That's a bad position to explain. The fix isn't more diligence — it's putting those anniversary dates into the same register as everything else, so they surface alongside the BAS and returns you're already watching.
From static dates to live work items
The shift that makes the difference is moving obligations from a static list into live work items. A due date on a spreadsheet does nothing. A work item that appears on a board, assigns itself to a person, carries a deadline, and shows its own status is something the practice can actually run on.
This is where account practice management software earns its place. In Finye, compliance obligations aren't a separate calendar you maintain by hand — they're recurring jobs tied to each client's record. A quarterly BAS generates its work item automatically. An ASIC review appears ahead of the registration anniversary. Tax return obligations flow from the client's profile. Each one lands on a board with an owner and a due date, so the whole obligation load across BAS, IAS, returns and ASIC reviews is visible in one place rather than reconstructed from several.
Because the client records, the compliance tracking and the work boards sit in the same system, the deadline and the work never drift apart. When a client hasn't sent their records, the blocked job is visible against the deadline it threatens — not hidden in an inbox you'll check later.
Building the register once, properly
If you're moving away from scattered tracking, the work is mostly front-loaded and done once. A practical sequence:
- List every obligation type you handle — BAS, IAS, income tax returns, FBT, ASIC annual reviews, and anything else recurring. Don't assume; actually write them out.
- Attach each one to the right clients and entities. This is where duplicates and stale data get caught. An accurate client register is the foundation everything else sits on.
- Set the cycle and the lead time. Don't just record the due date — record when work should start, so the obligation surfaces early enough to chase records and leave a buffer.
- Assign an owner to each. Every obligation needs a name against it, not a team.
- Make the whole thing recurring so next quarter's register builds itself instead of being rebuilt from scratch.
Once that structure exists, lodgment season stops being a reconstruction job. The register is already there, already current, already assigned. You're managing work, not hunting for what the work even is.
The point of a single view
The goal of accounting client management software in this context isn't fancier reminders. It's removing the moment where someone has to read six screens to work out what the practice owes the ATO and ASIC this month.
When every obligation lives in one register — tied to the client, the owner and the live status of the work — nothing depends on a single person remembering it. The deadline that used to fall through the gap between your tools has nowhere left to fall, because there's only one place for it to be.