If a business is registered for GST, it has to lodge a BAS for every reporting period, including the ones where nothing happened. No sales, no purchases, no payroll, it does not matter. The obligation sits with the registration, not the activity. The ATO does not send a reminder when a nil period comes around, so the clock just starts on the due date and keeps running until the statement lands. This catches clients out more often than it should. A business that pauses for a quarter, goes quiet while the owner is travelling, or simply has a slow period assumes there is nothing to do because there is nothing to report. That assumption is wrong, and the same logic applies to businesses winding down: until the GST registration is formally cancelled with the ATO, the lodgement obligation stays live, so a firm managing a closure needs the deregistration processed before assuming the BAS cycle has ended.
What actually happens if a nil BAS is late
The important thing to understand is that a nil BAS is a real lodgement obligation, and a late one can attract a Failure to Lodge penalty like any other statement. The penalty accrues as one penalty unit for every 28-day period, or part of one, that the statement is overdue, capped at five penalty units for a small entity. The dollar value of a penalty unit is set by the ATO and indexed periodically, so rather than quote a figure that changes, the point to hold onto is the shape: it grows in steps for each 28 days late and stops at five steps. Even at the cap it is not an enormous sum per statement, but it is real, and it compounds. A client dormant for several quarters can rack up multiple capped penalties, one per missed period, which is how a business that "had nothing to report" ends up with a meaningful bill built entirely from nil statements.
There is an important nuance that cuts the other way, and it is worth knowing precisely. The ATO's general practice is that it will not issue a Failure to Lodge penalty for a late-lodged activity statement where the result is nil or a refund. That is genuinely helpful for dormant clients, but it is an administrative concession, not a guarantee, and it has real exceptions: it does not apply if a penalty was already raised before the statement was lodged, and the ATO can still act where there is a pattern of late lodgement rather than a one-off. So the nil result softens the penalty risk, but it does not remove the obligation, and a firm managing dormant clients cannot build its process around ATO goodwill. The safer default is to treat a nil period exactly like any other quarter.
Why this is a workflow problem, not a tax problem
The reason missed nil BAS lodgements are so common is that they are invisible until they are overdue. There is no transaction to reconcile, no figure to prompt anyone, nothing to make the period feel like work, so a dormant client quietly falls out of the review rhythm and nobody notices until a notice arrives. That makes this a process failure rather than a knowledge failure, which is good news, because process failures are fixable. The fix is to treat dormant client periods as an active workflow task rather than a gap: flag the clients who are likely to go quiet, schedule their nil lodgements the same way you schedule everyone else's, and make sure any genuine closure has the GST registration cancelled before the next period begins. A missed nil BAS is one of the most avoidable exposures on the books, because the work of lodging a nil statement is trivial. The only thing that ever goes wrong is forgetting it exists.
