October Means BAS Again: Building a Quarterly Rhythm That Runs Itself

The first-quarter BAS lands in October and asks an awkward question: did anything actually change since the promises you made yourself in July? For businesses that scrambled through the last statement, this is where the promise gets audited. The honest goal isn't heroic BAS preparation. It's a quarterly rhythm in which the BAS becomes a by-product of habits that were happening anyway.

A report, not a project

A BAS pulls a small set of figures from your accounting file: GST collected and paid, PAYG withholding, any instalments. If the file is accurate and current, producing those figures is roughly an hour's work including review. Every hour beyond that is the file being made accurate retroactively — the quarter's uncoded transactions, the missing receipts, the accounts nobody reconciled. So the fix never lives in BAS week. It lives in the ninety days before. Businesses for whom the BAS is a non-event aren't better at BAS; they're better at Tuesdays.

The weekly habits that do the real work

Four standing habits carry the whole system, and none of them needs to run long.

• Code the bank feed weekly. Rules handle the recurring transactions; a human handles the rest. A week's coding takes minutes over a coffee. A quarter's takes a lost weekend, done worse.
• Capture receipts at the moment. Phone photo straight into the accounting file, especially for the expense categories where missing paperwork means forfeited GST credits.
• Invoice in the same week the work happens. So the revenue and the GST collected on it are simply true, and your debtors clock starts sooner as a bonus.
• Reconcile monthly. Bank balances agreeing with the file, payroll reports matching the ledger, the GST accounts passing a sanity glance.

Do these and the data is continuously lodgement-ready, which carries a benefit nobody mentions: your management numbers are continuously decision-ready too. The deadline, reframed, is just the government enforcing a bookkeeping discipline you should want for your own sake — a case we make from several angles across our finance pages.

The fortnight before lodgement

Even with clean habits, run a light checklist in the two weeks before your due date, held as a recurring calendar entry with a named owner. First week: a final coding sweep, bank and card reconciliations completed, oddities resolved (the duplicate, the mystery deposit, the personal expense on the business card). Second week: generate the draft activity statement, compare it against last quarter's, have your BAS agent review it if you use one, then lodge and schedule the payment. The comparison step matters more than it sounds, because a figure that moves sharply without a story is either a business change worth knowing about or a coding error worth catching before the ATO does.

Put the cash aside as you go

Preparing the statement and paying it are different problems. The GST you collect and the PAYG you withhold were never yours; they're the ATO's money passing through your account. Move a suitable slice of takings into a separate tax-savings account as revenue arrives, at whatever cadence matches your banking, and payment day becomes an administrative transfer rather than a scramble. Your accountant can help you set the proportion for your particular mix; the mechanism matters more than the exact setting.

What the rhythm buys you

Due dates vary with how you lodge — statements lodged through a registered agent typically run to a different timetable than self-lodgement — so confirm your actual dates with the ATO or your agent and calendar the checklist backwards from there. Then notice the compounding return: the same weekly habits that make October boring also make bank conversations easier, pricing decisions sharper and year-end cheaper, because your accountant stops billing you to repair the past. A boring BAS isn't a compliance achievement. It's a symptom of a business that knows its own numbers all year round.