Blog · Compliance
A practical 2026 guide to the Tax Practitioners Board Code of Professional Conduct, confidentiality under section 355-25, lodgment responsibility, and how registered agents can adopt tools like Claude without tripping the rules.
The short answer. Neither the ATO nor the Tax Practitioners Board has banned AI in Australian tax or accounting practice. The ATO is actively digital-first and treats modern tooling as a positive signal. What they require is unchanged: registered agents must meet the Tax Agent Services Act 2009, the TPB Code of Professional Conduct — particularly confidentiality (item 6) and competence (item 7) — and protect taxpayer information consistent with section 355-25 of the Taxation Administration Act 1953 and the Privacy Act 1988. AI is treated as a junior staff member: supervised, reviewed, and signed off by the agent.
Every registered tax agent, BAS agent, and tax (financial) adviser in Australia is bound by the TPB Code of Professional Conduct in Division 30 of the Tax Agent Services Act 2009. Two items are the pressure points for AI use.
You must not disclose information acquired in the course of providing tax agent services to a third party without the client's permission or a legal duty to do so. A consumer AI tool that trains on inputs, or where it is unclear whether a provider processes data outside Australia, can push you into breach territory. The mitigations are familiar from every other cloud service your practice already uses:
You must ensure tax agent services are provided competently. In an AI context that means two things: you understand the tool's limitations (it can confidently produce incorrect technical content), and you review the output before it goes to a client or the ATO. An AI-drafted Division 7A memo that isn't checked by a competent human is a Code item 7 problem, not an AI problem.
The ATO's own operating model is overwhelmingly digital. Single Touch Payroll, pre-fill, Online services for agents, myGovID-based authentication, and the ATO's internal use of machine learning for risk scoring all point in the same direction: the ATO wants the tax system digitised, and well-governed technology adoption by agents is consistent with that direction. There is no "paper trail" nostalgia in modern ATO guidance, and nothing in ATO materials suggests that drafting a client letter with AI is any different from drafting it with Word's spell-checker.
Section 355-25 of Schedule 1 to the Taxation Administration Act 1953 makes it an offence for a taxation officer to disclose protected taxpayer information outside the exceptions. Strictly, the direct binding target is tax officers and certain other entities handling tax information; tax agents' confidentiality obligations run primarily through TPB Code item 6 and the Privacy Act 1988. In practice the effect for your practice is the same: taxpayer information is protected by law and cannot be sent into any environment that doesn't give you proper control over how it is processed. If you wouldn't email a client's full tax file to a free consumer webmail account, don't paste it into a free consumer AI chatbot either. The paid Claude Team and Enterprise plans are built for this — no training on your data, a DPA, and enterprise controls.
Through 2024 and into 2025 the TPB issued and refreshed guidance on the responsible use of AI by registered agents. The through-line is consistent:
Supervision is the recurring word. Treat AI output exactly as you would treat the first draft from a graduate accountant: useful, time-saving, not yet signable.
The three professional bodies have published complementary positions.
None of the three has prohibited AI. All three expect governance, training, and supervision.
Yes. The ATO cares about the accuracy of the return and the validity of the agent's declaration, not the keyboard it was typed on. The tax agent's declaration under section 388-65 of Schedule 1 to the Taxation Administration Act 1953 certifies that the statement is true and correct — that obligation is unchanged whether the schedules were prepared by hand, by a junior, by practice management software, or with AI assistance.
The practical consequence: an AI-generated workpaper, covering letter, or narrative is fine. It must be reviewed by a competent person before it informs a lodgement, and the agent's review is what makes the lodgement valid. Responsibility doesn't transfer to the tool, ever.
FAQ
Has the ATO banned AI use by tax agents?
No. The ATO itself is pursuing a digital-first strategy and treats well-governed technology adoption as a positive signal. Neither the ATO nor the TPB has prohibited AI. What is required is unchanged: compliance with the Tax Agent Services Act 2009, the TPB Code of Professional Conduct, confidentiality obligations and the Privacy Act 1988.
Does putting client information into Claude breach section 355-25?
Section 355-25 primarily binds taxation officers handling protected information. For registered agents the binding confidentiality duty is TPB Code item 6, supported by the Privacy Act 1988 and the Australian Privacy Principles. Using a paid Claude plan where Anthropic contractually does not train on your conversations, combined with anonymised references where practical, is how most Australian practices manage the risk.
Can an AI-prepared return be lodged?
Yes, provided the registered agent reviews the return, confirms accuracy, and signs the declaration under section 388-65. The TPB and ATO treat AI output the same way as work prepared by a junior: supervised, reviewed, and certified. Responsibility never transfers to the tool.
What does the TPB say about AI specifically?
TPB guidance issued in 2024 and refreshed through 2025 makes clear that AI use is permitted but that registered agents remain accountable for Code obligations — especially confidentiality (item 6), competence (item 7), honesty and integrity (item 1), and acting lawfully in the client's best interests (item 4). Supervision of AI output is required.
Do CPA Australia and CA ANZ allow members to use AI?
Yes. Both support responsible adoption. CPA Australia has released member resources on generative AI in practice; CA ANZ has published AI ethics guidance aligned with APES 110. The consistent message is that AI assists, judgement and responsibility remain with the member.
What should I document if the TPB or ATO reviews my AI use?
Keep a written AI use policy, a record of approved tools and the plan they run on, your approach to anonymising or minimising client data, evidence that AI drafts are reviewed before delivery or lodgement, and staff training records. That paper trail demonstrates the supervision and competence the TPB expects.
This article is general information for Australian registered agents and accounting practices. It is not legal or professional advice. Always review current ATO, TPB, and professional body guidance for your specific circumstances.
Claudable trains Australian accounting and tax practices on Claude Cowork with a compliance-aware framework that aligns with TPB Code expectations.