The Deadline Register: One View of Every Obligation You Owe
BAS, IAS, tax returns and ASIC reviews live in different tools with different rhythms. A single obligation register turns scattered dates into work you can actually run.
Ask most practice owners where their compliance deadlines live and the honest answer is: everywhere. The BAS cycle sits in one place. Tax return due dates come off the lodgment program. ASIC annual review dates arrive by post or email, one company at a time. IAS instalments turn up when they turn up. Each obligation has its own source, its own format and its own way of surprising you.
The problem isn't that any one deadline is hard to find. It's that there's no single view of everything you owe, across every client, at once. Without that view, deadlines get managed reactively — you deal with the one in front of you and hope nothing behind it slips.
Four calendars pretending to be one
A typical firm is tracking at least four distinct obligation types, each on a different clock:
- BAS — monthly or quarterly, with due dates that shift depending on whether you lodge through the BAS/tax agent portal and whether the client is on your program.
- IAS — PAYG and GST instalments that don't always line up neatly with the BAS cycle.
- Income tax returns — staggered across the lodgment program from October through to May the following year, with dates that depend on the client's prior-year lodgment status and entity type.
- ASIC reviews — annual review dates tied to each company's registration anniversary, plus the payment deadline and any changes to company details that need lodging within their own windows.
Each of these arrives on its own rhythm. When they live in separate spreadsheets, separate portals and separate memories, the firm has no way to look forward two weeks and see the true shape of what's coming. You see the fire, not the fuel.
Why the spreadsheet stops scaling
Most firms start with a compliance spreadsheet, and for a while it works. One tab for BAS clients, one for tax returns, maybe a column for ASIC dates. Someone owns it. Someone updates it.
The trouble is that a spreadsheet records a date but doesn't do anything with it. It doesn't assign the work. It doesn't tell you whether the return is actually underway or still waiting on the client. It doesn't know the client signed the engagement letter, or that you're missing the source documents. It's a list of dates sitting next to a completely separate list of jobs, and keeping the two in step becomes its own recurring task.
As the client list grows, the gap between "the date is in the spreadsheet" and "the work is done" widens. That gap is where missed deadlines live — not in dates nobody recorded, but in dates that were recorded and then quietly disconnected from any actual work.
An obligation should be a piece of work, not a diary note
The shift that fixes this is treating every compliance obligation as a work item, not a calendar entry. A due date on its own is passive. A work item has an owner, a status, a set of steps and a client attached to it. When the quarterly BAS is a job on a board rather than a cell in a spreadsheet, you can see at a glance whether it's not started, in progress, waiting on the client or ready to lodge.
This is the core of proper account practice management software: the deadline and the work are the same object. You don't maintain a register of dates and a separate pipeline of jobs. The obligation generates the job, the job carries the date, and the date drives when the job appears on someone's list.
In Finye, recurring compliance work is built to run this way. BAS and IAS cycles recur on their schedule and spin up the next job automatically, so a client's quarterly obligation never depends on someone remembering to create it. Tax return jobs and ASIC review dates sit alongside them on the same boards, tied to the same client records — so "what's due in the next fortnight" is one view across every obligation type, not four tabs you cross-reference by hand.
The dates that move — and the ones that don't
Compliance deadlines aren't all fixed, and that's exactly why a live view matters more than a static list.
Lodgment program dates depend on the client's history. A new client, or one who lodged late last year, may not get the concessional dates you assumed applied. ASIC annual review dates are anchored to registration anniversaries that don't care about your quarter-end. A spreadsheet copied from last year quietly carries forward assumptions that may no longer hold.
When obligations are tracked as live work items against each client record, the date reflects that client's actual position — not a generic template. And because the record is one record, updates to the client's details flow through to the obligations attached to them, rather than being maintained separately in a compliance tab that drifts out of date.
Where the client fits in
A large share of missed deadlines aren't really the firm's fault in the narrow sense — the return was ready to go except for one document, or the signature, or the confirmation that never came back. The deadline was known. The blocker was the client.
This is where good accounting client management software earns its place. When the obligation, the outstanding request and the client are connected, the chase can be built into the workflow instead of added to your to-do list. A portal request tied to a specific job lets the client see what's needed and when, and follows up on your behalf. The obligation register and the client-facing request are two views of the same underlying work — not disconnected systems you have to reconcile.
Building the register
If you're moving away from scattered tracking, the practical steps are straightforward:
- List every obligation type you're responsible for — BAS, IAS, income tax, ASIC reviews, and anything else with a statutory date.
- Attach each to a client record, not a spreadsheet row, so the date and the client stay bound together.
- Set the recurring ones to recur, so the next cycle appears without manual effort.
- Give every obligation an owner and a status, so "tracked" and "done" are visibly different states.
- Make the client-facing chase part of the job, not a separate reminder you have to send by hand.
The goal isn't a prettier calendar. It's a single, live view of every obligation the firm owes — one where a due date is never just a date, but a piece of work that someone owns and the system keeps moving. That's the difference between knowing your deadlines and actually running them.