The Deadline You Track Twice: One Register for BAS, IAS and ASIC

BAS in one spot, ASIC reviews in another, tax returns in your lodgment program — here's why splitting compliance dates across systems quietly costs you, and how to fix it.

Ask most Australian practices where their compliance deadlines live, and you'll get more than one answer. BAS and IAS dates come out of the lodgment program. Tax return due dates sit there too, more or less. But ASIC annual review dates? Those are in a spreadsheet, or a calendar reminder someone set up two years ago, or — honestly — in nobody's head at all until the invoice arrives from ASIC and a late fee has already started ticking.

The problem isn't that any single date gets forgotten. It's that no one place shows you every obligation the firm owes, across every client, at once. When compliance is tracked twice — once for lodgments, once for everything else — you're relying on people to remember which system to check for which obligation. That's the gap where a missed ASIC review or an unlodged IAS slips through.

Why compliance dates end up scattered

It happens for a sensible reason. The obligations genuinely come from different places and behave differently:

BAS and IAS run on the ATO cycle — monthly or quarterly, with dates that shift depending on whether you lodge electronically through a tax or BAS agent.
Tax returns have due dates that depend on the client's entity type, prior-year lodgment status and whether they're on your agent list.
ASIC annual reviews aren't tax at all. They fall on the anniversary of a company's registration, they're not in your ATO lodgment program, and the payment window is tight — 2 months from the review date before late fees apply.

Because ASIC reviews don't come down the same pipe as ATO obligations, they get managed separately. And separate is where things get missed. A practice can have immaculate BAS tracking and still cop an avoidable ASIC late fee on behalf of a client, simply because the review date lived in a different tool than the one everyone actually opens each morning.

The cost of tracking the same thing twice

Splitting deadlines across systems isn't just untidy. It creates real, repeating work:

You reconcile in your head. To answer "what's due this month?" someone has to check the lodgment program and the ASIC spreadsheet and whatever calendar holds the odd one-off. The answer is only ever as good as the person's memory of where to look.
Nobody owns the second list. The lodgment program has a clear owner. The ASIC spreadsheet often doesn't — it's "maintained" by whoever set it up, until they go on leave or leave the firm.
Dates drift out of sync. A client restructures, adds an entity, or deregisters a company. The change gets made in one place. The other place keeps showing the old picture.
Extensions get assumed. A lodgment date you thought you had shifts, or doesn't apply to a particular client, and the spreadsheet never reflected the concession in the first place.

None of these is dramatic on its own. Together they mean the practice is carrying risk it can't see — and doing manual cross-checking that a single view would eliminate.

What one deadline register looks like

The fix is conceptually simple: every obligation the firm is responsible for, for every client, in one register. Not one for lodgments and one for everything else — one, full stop.

A single register means you can ask real questions and get real answers:

What's due in the next 14 days, across BAS, IAS, returns and ASIC reviews combined?
Which of those already have a job on the go, and which have nothing started?
Who owns each one — and where's it up to right now?
Which clients have an ASIC review coming that isn't attached to any work item yet?

The last question is the one that catches firms out most. An ASIC review date with no job behind it is the exact obligation that gets missed, because there's nothing in a workflow prompting anyone to act.

Deadlines and the work should be the same object

Here's the part that matters. A deadline register is far more useful when the dates aren't a static list you maintain by hand, but are tied to the actual client record and the actual work. That's the difference between account practice management software that tracks obligations and a spreadsheet that lists them.

In Finye, compliance obligations sit against the client record and flow onto your work boards as jobs. Recurring obligations — quarterly BAS, an annual review, the yearly return — are set up once as recurring jobs, so next period's work appears automatically instead of being rebuilt from memory. The deadline register then shows every obligation across the practice in one view, whether it's an ATO lodgment or an ASIC review, with the job status attached so you can see not just when it's due but where it's up to.

Because Finye is built as accounting client management software rather than a standalone calendar, the register and the work are the same thing. Close the job, and the obligation is dealt with. Add a new entity for a client, and the review date belongs to a record that already lives in the system — not a row you have to remember to copy into a second sheet.

Getting your obligations into one place

If your deadlines are currently split, the move to a single register is worth doing deliberately:

List every obligation type the firm actually handles. BAS, IAS, income tax returns, FBT, ASIC annual reviews, TPAR, super obligations — whatever applies to your client base.
Pull ASIC review dates out of the spreadsheet. These are the ones most likely to be living outside your main system. Get them attached to the relevant company records.
Set recurring obligations up once. Anything that repeats on a cycle should generate its own next instance, so nobody re-creates it each period.
Attach an owner to every recurring obligation. A date with no owner is a date at risk.
Check the register weekly, not the individual systems. One view, reviewed on a rhythm, replaces the mental reconciliation you were doing across tools.

The goal isn't a prettier list. It's confidence that when you look at what's coming, you're looking at everything — not everything except the obligations that happened to live somewhere else. Compliance is the core of what a practice owes its clients. It shouldn't be the thing you track twice and hope you covered both times.