The ASIC Review Date That Isn't in Your Lodgment Program
BAS and tax returns show up in every deadline tracker. ASIC annual reviews often don't — and that's where quiet, avoidable penalties come from.
Most practices have a handle on their ATO obligations. BAS quarters are predictable, IAS instalments follow a rhythm, and income tax returns sit inside the lodgment program with dates you can lean on. The system that trips people up is the one that runs on a different calendar entirely: ASIC.
ASIC annual reviews don't follow the financial year, they don't follow the lodgment program, and they don't send the same volume of reminders the ATO does. They land on the anniversary of a company's registration — which means every company client has its own date, scattered across all twelve months. If your compliance tracking is built around ATO cycles, ASIC is the obligation most likely to slip through unnoticed until a late fee arrives.
Why ASIC reviews get missed
The ATO trains you to think in cycles. Everyone's Q1 BAS is due on the same date. Tax returns cluster around the lodgment program deadlines your agent portal reminds you about. You build habits around shared due dates.
ASIC breaks that habit. A company registered on 14 March gets its annual review statement in March every year. The next client, registered in August, gets theirs in August. There's no season, no batch, no single week where you sit down and 'do the ASIC ones'. The review fee falls due, the company details need confirming, and any changes — directors, shareholders, registered office, addresses — need to be lodged inside strict windows.
Miss the payment window and late fees apply. Miss the 28-day window to notify a change of details and you're looking at separate penalties. None of this shows up in a tax return software workflow, because it isn't a return. It's a standing obligation that lives outside the lodgment program most tools are built around.
The spreadsheet problem
The common workaround is a spreadsheet: one tab with every company client, their ACN, their review date, and a column for whether this year's review is done. It works right up until it doesn't. Someone forgets to update it after a new company client is onboarded. A director change gets actioned in one place but the review date doesn't get recalculated. The person who maintained the sheet goes on leave, and nobody else quite trusts the dates in it.
The deeper issue is that the spreadsheet lives apart from the work. It tells you a date is coming but it can't create the job, assign it, chase the client for confirmation, or mark it complete. You end up managing the obligation in one system and the actual task in another — which is exactly how obligations get lost.
Treat ASIC as an obligation, not a memory
The fix isn't a better spreadsheet. It's treating every ASIC review the same way you treat a BAS: as a tracked obligation with a date, an owner, and a linked piece of work.
Good accounting client management software should let you record the obligation once and have it recur. When you onboard a company client, you capture the ACN and the registration anniversary, and the review obligation generates itself every year without anyone remembering to add it. The date drives a work item; the work item carries the checklist — confirm details, check for changes, lodge any variations, invoice the ASIC fee if you pass it on, and record completion.
What a single deadline view changes
When ASIC reviews sit in the same register as your ATO obligations, a few things stop happening:
- Nothing hides in a monthly gap. You see March's ASIC reviews next to March's IAS instalments, not on a separate tab you only open when you remember to.
- The change window stops being a surprise. If a client tells you about a new director in conversation, the obligation to notify ASIC within 28 days is visible as its own item, not something you hope you'll action later.
- Handover survives leave. The obligation belongs to the practice, not to the person who built the spreadsheet. Anyone can see what's due and who owns it.
This is where a proper deadline register earns its place. Finye tracks ATO and ASIC obligations together — BAS, IAS, income tax returns and ASIC annual reviews — each with its own due date, owner and linked work item, so the review that falls on a company's registration anniversary shows up alongside everything else you owe that month.
The details that trigger obligations
ASIC obligations aren't only about the annual review fee. They're triggered by data changes, and that's where accurate client records matter. If your ABNs and ACNs are entered inconsistently, or a company name is spelt two ways across systems, you get confusion at exactly the moment precision counts.
Keeping the client record clean — one accurate ACN, one registered name, one registered office on file — means the obligation attaches to the right entity every time. This is the quiet value of client accounting that treats the client record as a single source of truth rather than something re-entered across a portal, a ledger, and a compliance sheet. When the record is right, the obligation is right, and the reminder fires on the correct date.
A simple audit to run this week
Whatever system you use, run this check:
- List every company and trust-with-corporate-trustee client and confirm you have their ACN and registration anniversary recorded.
- Check that each has an ASIC review obligation tracked for the coming twelve months — not just the ATO ones.
- Confirm one person or role owns each review, and that the owner isn't a spreadsheet cell.
- Verify that a change of company details creates a visible 28-day task, not a mental note.
The obligation you don't want to explain
Clients forgive a lot, but a late fee that was entirely within your control is a hard conversation. 'We missed your ASIC review' isn't a technical failure — it's a tracking failure, and clients know the difference.
The practices that never have that conversation aren't more diligent by nature. They've simply designed the miss out of their process by putting every obligation — ATO and ASIC — into one view that generates its own work and chases its own dates. When your account practice management software treats an ASIC review with the same seriousness as a BAS, the anniversary date stops being something you have to remember and becomes something the system already knows.