AI for BAS Agents

No. It prepares, you lodge. The AI assembles the material a BAS relies on — coded transactions, substantiation, reconciliations, and a list of the items it thinks warrant your attention — and stops there. A registered BAS agent reviews that material, forms their own view on the GST treatment, and lodges under their own registration. This is not a technical limitation we intend to remove later; it is the correct boundary. Lodgement carries a declaration, a declaration carries responsibility, and responsibility sits with a registered human agent. This product is not registered with the Tax Practitioners Board, does not provide BAS services, and does not hold itself out as able to.

Beyond the obvious regulatory answer, there is a client-protection reason that is often overlooked. The safe harbour provisions in the taxation administration law can protect a taxpayer from certain administrative penalties where they engaged a registered agent, provided all relevant information to that agent, and the shortfall resulted from the agent’s error rather than the taxpayer’s. That protection is built around the existence of a registered agent in the chain. A client who lodged directly off an automated tool has no such position. So the boundary is not just about our compliance — the registered agent is a substantive part of what your client is buying, and it is worth saying so when you price your work.

The messy stuff is precisely what it flags rather than what it silently decides. Straightforward transactions with a clear supplier, a valid tax invoice and an unambiguous treatment get coded and presented for your review with high confidence. The awkward categories go into an exception queue: mixed supplies where a single invoice contains both taxable and GST-free lines, purchases from suppliers with no ABN quoted where withholding may be in play, transactions that look like they might be input-taxed, and anything where the client’s description and the supplier’s description disagree. You get a short list of genuine judgement calls instead of nine hundred lines to scan for the twelve that matter.

It automates the chase, which is most of the problem, but it does not automate the client. The AI compares the ledger against the substantiation it holds, works out precisely which transactions lack a valid tax invoice or receipt, and requests those specific items from the client — not a vague "please send anything outstanding" email, which is why the generic version never works. It follows up on a schedule, escalates only where a human is genuinely needed, and stops immediately on receipt. What it cannot do is make a client who has lost the receipt produce it. What it does do is discover that fact in week two of the quarter rather than in the last week before the twenty-eighth.

Yes, and the distinction is configured per client file because it materially changes what the AI should be looking at. On a cash basis, the timing hinges on when payment occurred, so the reconciliation of payments against invoices is the critical path and unpaid invoices are noise for that quarter. On accruals, the invoice date drives it and the debtors and creditors listings matter far more. Getting this wrong is one of the classic ways a BAS goes sideways, so it is set explicitly during onboarding rather than inferred. If a client changes basis, that is a configuration change we would expect you to tell us about — the tool does not guess at something with that much consequence.

Both, because the two roles have different bottlenecks and you are carrying both. Your bookkeeping bottleneck is the per-file margin — volume clients consuming hours the fixed fee never covered. Your BAS agent bottleneck is the quarterly compression, where four weeks of every quarter absorb work that could have been spread across thirteen. Automation helps each of them in a different way, and the sequencing matters: fixing the ongoing coding and substantiation flow through the quarter is what makes the BAS window survivable, not doing anything clever in the last fortnight.