Never miss a BAS deadline: building a compliance calendar that works
A BAS deadline compliance calendar that tracks BAS and IAS due dates across every client automatically, so nothing slips through the cracks.
Most practices have a story about the BAS that almost got missed. A client switched from quarterly to monthly reporting, the spreadsheet did not get updated, and the only person who knew was on leave the week it was due. The lodgment scraped in late, the ATO applied a failure-to-lodge penalty, and the partner spent an afternoon writing an apology email instead of doing client work.
The problem is rarely effort. It is the tool. A shared spreadsheet that one person maintains is the single most common way Australian accounting and bookkeeping firms track BAS and IAS due dates, and it is also the most fragile. This article looks at why that approach breaks down, and how a proper BAS deadline compliance calendar tracks obligations across every client automatically.
Why the spreadsheet always breaks
A lodgment tracker in a spreadsheet works fine for a dozen clients. It starts to creak at fifty, and it becomes genuinely risky past a hundred. The reasons are structural, not a reflection of how careful your team is.
- One owner, single point of failure. The spreadsheet lives in one person's head as much as in the cells. When they are away, sick, or leave the firm, the corporate memory walks out the door with them.
- Due dates are not static. Quarterly BAS deadlines shift when they fall on a weekend or public holiday. The ATO's lodgment program concession dates for tax agents differ from the standard dates. Hand-maintained spreadsheets rarely keep up.
- Client changes get missed. A client moves from quarterly to monthly GST reporting, registers for PAYG instalments, or deregisters for GST entirely. Each change should ripple through the calendar. In a spreadsheet, someone has to remember to make the edit.
- No link to the actual work. A row that says "Q2 BAS due 28 Feb" tells you a date. It does not tell you whether the work has started, who is doing it, or whether you are still waiting on records from the client.
Every one of these is a place where a deadline can quietly disappear. The fix is not a better spreadsheet. It is a system that knows your obligations and your clients, and keeps the two in sync without anyone maintaining a list by hand.
How a compliance engine tracks due dates automatically
Finye's compliance engine is built around the obligations a practice actually carries: BAS and IAS, income tax returns, ASIC annual reviews, and other recurring lodgments. Instead of a flat list of dates, it models each obligation against the client it belongs to and the rules that govern when it is due.
You set up an obligation once for a client, for example a quarterly BAS, and the engine calculates the due date for every period from there. Because it understands the Australian financial year and the standard quarterly cycle, it works out the next due date, rolls it forward each period, and adjusts for the lodgment timing that applies. You are not retyping dates four times a year for every client on your book.
When something changes, you change the obligation, not a hundred calendar entries. Move a client to monthly IAS and the schedule recalculates. Add a new client during onboarding and their obligations join the calendar straight away. The point is that the due dates are derived from rules and client data, so they stay correct without manual upkeep. If you are still weighing up tools, our comparison page sets out how this differs from generic task lists.
Seeing every client on one dashboard
A calendar is only useful if you can see it the way you work. Finye surfaces compliance two ways, and both draw from the same engine.
The compliance dashboard gives the whole practice a single view of what is coming up: obligations that are due soon, ones that are overdue, and the spread of work across the next periods. A principal can open it on a Monday morning and know immediately whether the firm is on track for the quarter, without chasing anyone for a status update.
The per-client view answers the other question your team asks all day: what does this particular client owe, and when. When you open a client, you see their obligations and due dates in context alongside their contacts and work. It is the difference between hunting through a shared file and having the answer where you are already standing.
Because everyone reads from the same source, there is no version that is out of date sitting on someone's desktop. The calendar is the system of record, not a copy of it.
Turning a due date into work that gets done
Knowing a BAS is due is half the job. The other half is making sure someone actually prepares and lodges it. This is where a calendar that lives next to your practice management earns its keep.
In Finye, compliance sits alongside work items and recurring jobs. A quarterly BAS is not just a date on a dashboard; it can be a templated recurring job that generates the work item each period, ready to assign, with the checklist and subtasks your team follows every time. Status workflows show you what has started, what is waiting on client records, and what is ready to lodge. Nothing depends on one person remembering to create the job.
That connection between the obligation and the work is what a spreadsheet can never give you. The deadline and the doing are in the same place, so a due date is never just a number that no one acted on.
Making the change without a big migration
Firms hesitate to move off a spreadsheet because the spreadsheet, for all its faults, is theirs and it is familiar. The practical path is to bring your clients and their obligations into Finye, set the recurring patterns once, and let the engine take over the dates from there. Client and contact records can be kept in step through Xero two-way sync, so you are not maintaining two sources of truth for who your clients are.
Once it is set up, the maintenance burden largely disappears. You add obligations when you onboard a client and adjust them when a client's circumstances change. The day-to-day work of recalculating dates, rolling periods forward, and flagging what is overdue happens on its own.
A missed BAS is rarely a failure of competence. It is a failure of the system meant to catch it. If your firm is still relying on a spreadsheet that one person keeps alive, it is worth seeing what an automatic compliance calendar looks like in practice. Create a free Finye account to set up your obligations, or look at the pricing plans to see what suits your practice.