AI BAS Preparation Support

No — categorically, and by design rather than by limitation. In Australia, preparing or lodging a BAS for a fee is a BAS service, and it can only be provided by an agent registered with the Tax Practitioners Board. That registration attaches to a person or a practice, carries obligations under the Code of Professional Conduct, and cannot be delegated to software. Our product does the preparation work that sits underneath a BAS: reconciling the file, coding the transactions, chasing the missing documents, and surfacing the GST treatments that do not look right. The registered agent then reviews that work, applies their professional judgement, forms their own view that the figures are correct, and lodges it under their own registration and their own accountability. Any vendor implying their software can lodge on your behalf, or that it removes your accountability as the agent, is describing something that does not exist.

It removes almost all of the work that is not judgement. Through the quarter it keeps coding current and reconciliations up to date, so the file is not three months behind when the deadline arrives. It chases missing documents from clients continuously rather than in a panic in the final fortnight. It cross-checks GST coding against each supplier’s and customer’s established treatment in that file and flags departures. It compares the quarter against prior quarters and surfaces movements that warrant an explanation. It itemises what is sitting in suspense and clearing accounts. It assembles the working papers and the supporting reconciliations into a reviewable package. What lands on your agent’s desk is a prepared file with the questions already asked — so their time goes to answering them rather than to finding them.

It can tell you how that item has been treated in that file historically, and it can tell you when a treatment departs from the pattern. It cannot tell you what the correct treatment is, and it will not pretend to. GST characterisation depends on the actual supply, the contractual arrangement and the client’s circumstances — the sort of thing that turns on facts a model does not have and a judgement it is not registered to make. The distinction matters practically, not just legally: an AI that confidently asserts a GST treatment is an AI that has replaced a considered decision with a plausible sentence. What it is genuinely good at is noticing that this supplier has been coded GST-free for two years and this bill has GST on it, and putting that in front of a person who can determine which is right.

It does not reduce them. As a registered agent you remain responsible for taking reasonable care to ascertain a client’s state of affairs and to apply the tax laws correctly — and using software to help you do that is unremarkable and long-established, in the same way that using accounting software has never transferred responsibility to the vendor. What changes is the quality of the material your reasonable care is exercised on: a reconciled file with anomalies flagged and documents attached supports a considered review far better than a rushed reconstruction in the last week of the quarter. The obligation to actually perform that review is unchanged. If anything, our position is that automation should make the review more real, not less — the whole point of removing the grind is that the professional attention has somewhere better to go.

The recurring, boring ones that survive a rushed review. GST claimed on a supplier who is not registered, or on a document that does not have the features of a valid tax invoice. GST claimed at the full rate on an expense with a known private component. A supplier whose treatment has silently changed mid-quarter. Bank fees and interest coded with GST. Wages, superannuation or ATO payments picked up with a tax code attached. A capital purchase coded to an expense account. A credit note applied without reversing the GST. Duplicated bills inflating input tax credits. None of these are clever catches — an experienced agent finds every one of them given time. The problem is that they are individually small and collectively numerous, and they are exactly what gets missed at 11pm on the 27th.

It addresses the mechanism that causes the scramble, which is the honest way to answer. BAS crunch is mostly a deferral problem: coding, reconciling and document chasing accumulate quietly through the quarter and all become due in the same fortnight, colliding with every other client’s identical deadline. Automating the accumulating work means the file stays close to current and the client chasing happens continuously, so the final fortnight is review rather than catch-up. What it will not do is make an unresponsive client answer, resolve a genuinely ambiguous transaction, or substitute for your agent’s review — and if a client hands you a shoebox on the 25th, the shoebox is still the problem. We would rather set that expectation now than sell you a quarter-end miracle.