The Deadline That Moved: Keeping Your Register Current
BAS cycles change, ASIC review dates shift, clients switch lodgment status. Here's how to keep your compliance register accurate instead of quietly wrong.
Most firms don't miss deadlines because they forgot to look. They miss them because the register they were looking at was out of date. A client moved from quarterly to monthly BAS. A new company was registered and its annual review date never made it onto anyone's list. A tax return client became a non-lodger, or a non-lodger became a lodger, and the change lived in one person's memory instead of in the system everyone actually checks.
The dangerous deadlines aren't the ones you can see. They're the ones that quietly changed underneath you while your list stayed the same.
Why compliance dates drift
An obligation register feels like a fixed thing — a stable list of who owes what, and when. In practice it's constantly moving, and the movement rarely arrives with a clear signal.
- BAS frequency changes. A client crosses the GST turnover threshold and shifts from quarterly to monthly reporting, or elects to change. The due dates you had are now wrong for the whole year.
- IAS obligations appear and disappear. PAYG instalment obligations start, stop, or change amount based on prior-year results and ATO notices. An IAS you weren't tracking last quarter is suddenly due.
- ASIC review dates you never captured. A client incorporates a new entity. The annual review date is set by ASIC on registration — and if nobody adds it to your workflow, it sits outside your lodgment program entirely until a late fee arrives.
- Lodgment status changes. A client leaves, a new one arrives, an entity is deregistered, someone becomes a non-lodger. Each change should add or retire an obligation.
- Concessional dates shift. Tax agent lodgment program dates depend on a client's prior-year lodgment history. Lodge one return late and next year's concessional date can move.
None of these are exotic. They happen across an average client base every single month. The question isn't whether your obligations change — it's whether your register keeps up.
The two-register trap
Firms often end up with the same deadline recorded in more than one place: the lodgment program on one side, a spreadsheet of ASIC review dates on the other, and a set of recurring calendar reminders somewhere in between. Each was built to solve a real gap. Together they create a worse problem — when a date changes, you have to remember to change it everywhere, and you almost never do.
So the spreadsheet says quarterly and the practice management software says monthly. The calendar reminder fires for a client who left six months ago. The ASIC list has a review date the lodgment program has never heard of. Everyone's technically tracking the deadline. Nobody's tracking the same one.
The fix isn't more diligence. It's one register that every obligation flows into, so a change updates in a single place and everybody sees the same truth.
What a current register actually needs
Keeping compliance dates accurate is less about the calendar and more about the connection between client data and obligations. Good accounting client management software treats an obligation as something attached to a client record, not a standalone reminder — so when the client changes, the obligations can change with them.
Obligations tied to the client, not to a date
When BAS is a property of the client — with its reporting frequency, method and responsible staff member — changing the frequency updates every future due date at once. You're not editing a list of dates; you're changing one setting and letting the dates recalculate. That's the difference between a register that drifts and one that stays true.
ASIC in the same view as everything else
An annual review date is an obligation you owe on the client's behalf, exactly like a BAS or a tax return. It belongs in the same register, on the same board, with the same ownership and reminders. Kept in a separate spreadsheet, it's the deadline most likely to slip — not because it's hard, but because it lives where nobody looks weekly. In Finye, ASIC review dates sit alongside BAS, IAS and tax return obligations, so the whole compliance picture for a client is one view rather than three.
New clients and new entities that self-populate
The moment you onboard a client or record a new entity, its obligations should be created — the correct BAS cycle, the annual review date, the return type. Relying on someone to manually add each obligation after onboarding is how new work quietly falls outside the register in its first year, which is precisely when a missed date does the most reputational damage.
Changes that leave a trail
When a client moves from quarterly to monthly, you want to know when it changed and who changed it. A register that records the shift — rather than silently overwriting last quarter's assumptions — lets you answer the ATO, the client and your own future self with confidence.
A practical routine for keeping it accurate
Software keeps the mechanics current, but a light habit keeps the inputs honest. A few things worth doing on a regular cadence:
- Review status changes monthly. New clients, departed clients, new entities, deregistrations — confirm each has added or retired the right obligations.
- Check frequency shifts each quarter. Flag any client whose turnover, payroll or instalment position may have changed their reporting cycle, and update the register before the cycle turns.
- Reconcile ASIC review dates once a year. Cross-check your register against the corporate register so no annual review is sitting only in someone's memory.
- Retire what's dead. A late reminder for a client who left is noise, and noise trains people to ignore the register. Removing stale obligations is as important as adding new ones.
The point of a register is trust
A compliance register only works if people believe it. The first time someone finds a due date that's wrong — a BAS on the old frequency, an ASIC date that was never there — they start double-checking everything, and you're back to spreadsheets and memory. Accuracy isn't a nice-to-have; it's the entire value.
That's why client accounting works best when obligations live with the client record and update themselves as the client changes. When your practice management software holds one register — BAS, IAS, tax returns and ASIC reviews together, tied to live client data — the deadline that moved moves with you, instead of leaving you looking at a list that was quietly wrong.