The Obligation That Doesn't Belong to a Return

ASIC annual reviews and IAS instalments slip because they don't sit inside your tax-return workflow. Here's how to track the obligations that fall between the cracks.

Most practices run their compliance year around the big, obvious deadlines: the tax return season, the quarterly BAS cycle. These are the jobs that anchor your work-in-progress, your billing, and your capacity planning. They live in your tax return software and your workflow boards because they're the reason clients pay you.

But not every obligation belongs to a return. And the ones that don't are exactly the ones that quietly slip.

The obligations that live outside your main workflow

Think about what actually generates an ATO or ASIC penalty for your clients. It's rarely the return you're already tracking closely. It's the obligation that doesn't map to a lodgment job:

ASIC annual company reviews. These arrive on the company's registration anniversary, not on any tax cycle. There's no return to prepare, just a solvency resolution, a review of the company statement, and payment. Because there's no meaty piece of work attached, it's easy for the date to pass unnoticed until a late fee lands.
IAS instalments. Monthly or quarterly instalment activity statements for PAYG withholding or PAYG instalments don't feel like 'real' compliance work. They're small, repetitive, and often near-automatic. That's precisely why a missed one is so easy to overlook.
Payment deadlines that differ from lodgment deadlines. A BAS might be lodged on time but paid late. The lodgment side sits in your workflow; the payment side often sits nowhere at all.
TPAR, FBT, and other annual one-offs. These come round once a year, don't fit the quarterly rhythm, and get forgotten precisely because they're infrequent.

Each of these is a discrete obligation with its own date, its own owner, and its own consequence if missed. But they don't naturally attach to the jobs your practice already watches. So they end up living in someone's memory, a spreadsheet tab, or a diary reminder that nobody else can see.

Why 'we track it in Xero' isn't enough

Xero and similar ledgers will surface some of these obligations — a BAS due date, an activity statement to prepare. But your ledger's job is the numbers, not the practice's accountability. It won't tell you which staff member owns the ASIC review for a client whose company anniversary falls next Tuesday. It won't chase the client for the signed solvency resolution. It won't escalate when the obligation is three days out and nobody has touched it.

This is the gap between client accounting — the numbers and the ledger — and accounting practice management software, which runs the practice around the work. A ledger records what happened. Practice management decides what happens next, who does it, and by when. Compliance deadlines are a practice-management problem long before they're an accounting problem.

Build a single obligation register, not a pile of jobs

The fix isn't to create a job for every obligation and hope it gets worked. It's to keep a single register of every obligation across your whole client base, with the four things each one needs:

The date. Both lodgment and payment where they differ.
The owner. A named person, not a team or a queue.
The status. Not started, in progress, awaiting client, ready, done.
The source. So you know whether it's ATO, ASIC, or client-driven, and where the underlying data lives.

When you can see all of that in one place — sorted by due date, filtered by owner — the obligations that used to hide in the gaps become just as visible as the tax returns. An ASIC review due next month sits on the same wall as a BAS due next week. Nothing is 'the small thing we always forget' because nothing is off the list.

Recurring obligations should regenerate themselves

The other trap is treating annual and quarterly obligations as one-off events. When you complete a quarterly IAS, the next one should appear automatically with its date, owner, and status already set. When an ASIC review is done, next year's review should already be on the register. If your team has to manually create each recurrence, they will eventually forget one — usually the one for the quiet client you don't think about much.

Good accounting client management software handles this by treating the obligation as a recurring series, not a single task. Each instance closes and the next opens on schedule. Your register never has a hole in it because completion and creation are two ends of the same loop.

Where Finye fits

This is exactly the problem Finye is built to solve. Its compliance-deadline tracking treats BAS, IAS, tax returns, ASIC annual reviews, and other obligations as recurring items on a rolling deadline wall — each with a date, an assigned owner, and a live status. You see every obligation across every client at once, not scattered across returns, ledgers, and someone's calendar.

Because Finye runs the practice around the work rather than lodging anything itself, it doesn't care whether an obligation has a return attached. An ASIC review with no lodgment sits alongside a quarterly BAS with a full prep job behind it. Both are visible, both have an owner, both escalate when they're close to due and nobody has moved them. The two-way Xero sync keeps the underlying client and entity data accurate, so the ABNs and ACNs driving your ASIC dates aren't quietly wrong.

The practical test

Ask yourself one question about your current setup: if the staff member who 'just knows' the ASIC reviews left tomorrow, would anything slip?

If the answer is yes, those obligations aren't really tracked — they're remembered. And remembered obligations are the ones that turn into late fees, awkward client calls, and the kind of avoidable penalty that erodes trust in your firm.

The obligations that don't belong to a return are the ones most worth putting on a system. They have no natural home in your workflow, no invoice to remind you they exist, and no client email prompting the work. Give them a register, a date, an owner, and a status — and the deadlines that used to fall between the cracks become just another line on the wall.