The Deadline You Discovered Late: Building a Buffer Into Your Calendar
Most missed lodgments aren't missed on the due date — they're missed weeks earlier, when the work should have started. Here's how to build lead time into your compliance calendar.
Ask any practice owner about their worst compliance moment and it rarely involves a due date they didn't know about. It involves a due date they knew perfectly well — and discovered, three days out, that the return couldn't be finished in time. The client hadn't sent the last piece. The reviewer was on leave. Nobody had actually started.
The ATO and ASIC don't care why. A late BAS attracts a failure-to-lodge penalty. A late ASIC annual review racks up late fees that climb the longer they sit. And every one of these is avoidable, because the deadline was never the problem. The lead time was.
The gap between 'due' and 'doable'
A due date is a single point. The work behind it is a stretch of time. A quarterly BAS due on the 28th might need client records by the 14th, a review by the 21st and sign-off by the 26th. If your calendar only shows the 28th, you're flying blind on everything that has to happen first.
This is the trap in most compliance tracking. Firms build a list of due dates — often just the ATO lodgment program dates, sometimes copied into a spreadsheet — and treat the due date as the trigger to act. By then it's too late to absorb any friction. A client who's slow to respond, a query from the reviewer, a staff member out sick: any one of them turns a comfortable job into a scramble.
Good client accounting isn't about knowing when things are due. It's about knowing when things need to start.
Every obligation has a lead time
Different obligations need different runways. Worth mapping them deliberately rather than treating them all the same:
- BAS and IAS. If you prepare from client-supplied records, the real deadline is when you need those records — usually a week or two before lodgment, more if the client is historically slow.
- Tax returns. The longest lead time of all. A company return might need a signed engagement, source documents, a draft, client review and sign-off. That's weeks of elapsed time, not days of effort.
- ASIC annual reviews. These are predictable to the day — the review date is fixed to the company's registration anniversary. But they live outside your lodgment program, so they're the ones most likely to surprise you. The fee falls due after the review date, and the window to pay before penalties is tight.
- ASIC changes. Director changes, address updates and share changes all carry statutory notification windows measured from when the change happened — not from when you got around to it.
Once you know the lead time for each type of work, your calendar stops being a wall of due dates and becomes a schedule of start dates.
The buffer is where the value is
Build a buffer and something changes in how the practice feels. Instead of reacting to deadlines, you're working ahead of them. The client chase starts early enough that a slow response doesn't blow the job. The reviewer sees drafts with time to raise queries. Sign-off happens with days in hand, not hours.
The buffer also gives you somewhere to absorb the inevitable. Someone will be sick. A client will go quiet at exactly the wrong moment. A return will turn out more complex than the last one. A firm running to the wire on every job has no capacity for any of it. A firm with a fortnight's buffer barely notices.
What a buffered calendar looks like in practice
The mechanics matter less than the discipline, but here's the shape of it:
- Work items dated to start, not due. Each job carries both its statutory due date and the date you actually need to begin. Your board shows what to pick up this week, driven by start dates.
- Client requests fired ahead of the start date. If you need records by the 14th, the request goes out on the 1st — with automated follow-ups so the chase runs itself.
- Review and sign-off built into the timeline. These aren't afterthoughts squeezed into the final day. They're scheduled stages, each with their own slot.
- A single register covering every obligation. BAS, IAS, tax returns and ASIC reviews in one view, so nothing lives in a program you don't check.
Why the spreadsheet can't do this
A spreadsheet of due dates will happily tell you the 28th is the 28th. What it won't do is prompt you on the 1st that a job needs starting, chase the client while you're not looking, or show you which returns are quietly running out of runway. It's a static list, and lead time is a live thing.
This is where dedicated account practice management software earns its place. In Finye, every obligation — BAS, IAS, tax returns and ASIC reviews — sits in one deadline register, and each maps to work items on a board with their own timelines. Recurring jobs template themselves each period, so the quarterly BAS or annual review appears with its start date already set, not just its due date. The client portal fires document requests ahead of time and follows up automatically, so the runway you built doesn't get eaten by a slow reply. And because ASIC review dates live in the same register as everything else, they stop being the surprise that arrives with a late fee attached.
The point isn't the software for its own sake. It's that lead time is only useful if something acts on it. A calendar that only knows due dates leaves the acting to you, in the last available hour. A system built around start dates does the acting early, while there's still room to move.
Start with your worst near-miss
If you want a place to begin, think back to the last obligation you finished too close to the wire. Work out how much earlier it should have started to feel comfortable. That gap is your lead time for that kind of work. Apply it across the board, and the deadline you discover late becomes the deadline you were always ready for.
Compliance dates don't move. What you can move is when you start — and that single change is the difference between a practice that scrambles and one that simply delivers.