Compliance

AI and client consent: what TPB(GS) 55/2026 actually requires in your engagement letter

Advisory Stack Australia editorial team

TPB(GS) 55/2026 draws a distinction that is widely misreported. You must obtain each client's permission before divulging their information to a third party — which can include entering client information into AI tools, depending on how those tools are configured and used. Separately, the TPB recommends that when you obtain that permission you tell the client where data will be stored and whether AI tools may be used. The first is mandatory; the second is recommended.

What the guidance is, and what changed from the draft

TPB Guidance Statement TPB(GS) 55/2026, 'The use of Artificial Intelligence and the Code of Professional Conduct', was issued on 22 July 2026. It is a final instrument, not a draft.

The exposure draft was TPB(I) D62/2026, issued in March 2026 with submissions closing on 21 April 2026. The change in reference — from an Information Sheet to a Guidance Statement — reflects the TPB renaming its Practice Note series to Guidance Statements on 30 April 2026. It is a naming convention shift, not a downgrade in status. Content still citing the draft is out of date.

The consent requirement, precisely

Paragraph 23 is the operative provision, and its wording repays close reading. Practitioners must obtain permission from each client prior to divulging client information to a third party — which, the TPB says, can include entering client information into AI models and tools, depending on how these tools are configured and used.

When obtaining that permission, the TPB says it is recommended that the practitioner clearly inform the client about the proposed disclosure, including to whom and where the disclosure will be made, where data will be stored, and whether AI tools may be used.

So the honest answer to 'must I tell clients I used AI?' is: not as a standalone obligation. The mandatory duty is obtaining permission for third-party disclosure. Telling the client that AI is involved is recommended practice, and it is the sensible course — but conflating the two overstates the rule.

The carve-out nobody has resolved

The qualifier 'depending on how these tools are configured and used' is doing a great deal of work in that paragraph, and the TPB does not resolve it.

It implies that not every use of an AI tool amounts to disclosure to a third party. A tool that processes data without retaining it, or one operating within infrastructure the firm already controls, may sit differently from pasting client details into a public chatbot. But the guidance does not draw that line, so practitioners are left to assess each tool on its configuration.

The practical response is to document the assessment: what the tool does with client data, where it is processed, whether it is retained, and on what basis you concluded that consent was or was not required.

Which Code items are engaged

The guidance maps AI use onto existing obligations rather than creating new ones:

  • Code item 6 — confidentiality: you must not disclose information relating to a client's affairs to a third party without the client's permission
  • Code item 7 — competence: services provided by you or on your behalf must be provided competently
  • Code item 8 — you must maintain knowledge and skills relevant to the services you provide
  • Code item 9 — reasonable care in ascertaining a client's state of affairs
  • Code item 10 — reasonable care to ensure the taxation laws are applied correctly

Verification is an obligation, not a suggestion

Paragraph 16 addresses accuracy directly: AI models may hallucinate or provide inaccurate information and cannot be relied on as a replacement for tax knowledge, experience or expertise. The TPB says practitioners should verify and review AI-generated content for accuracy throughout each step of the workflow, and should establish processes to understand and contest AI outputs.

Paragraph 25 puts the due diligence obligation on the practitioner, and extends it to internally developed or modified tools as well as commercial ones — a point firms building their own automations often miss.

The TPB's framing throughout is that AI is a tool that may assist tax practitioners, but it does not replace professional judgement or transfer responsibility.

What the guidance does not cover

One significant gap is worth knowing. The final guidance contains no paragraph dealing with cross-border disclosure or overseas storage of client data.

That does not mean offshore processing is unregulated — it means the obligation sits elsewhere, in Australian Privacy Principle 8 under the Privacy Act, rather than in the TPB guidance. Any claim that the TPB regulates offshore AI processing is incorrect. Given that many widely used AI tools process data overseas, this is a question a firm should answer separately from its TPB analysis.

A practical checklist

For a firm updating its engagement documentation:

  • Identify each AI tool in use, including internally built automations, and assess whether its configuration involves disclosure to a third party
  • Where it does, ensure permission is obtained — via engagement letter, signed consent, or an appropriately worded general authority
  • Follow the TPB's recommendation: state where data will be stored and that AI tools may be used
  • Assess overseas processing separately under APP 8
  • Document the verification process so the review of AI output is evidenced, not merely asserted
  • Record the due diligence performed on each tool, commercial or internal

The bottom line

The TPB has not restricted AI use. It has confirmed that existing obligations apply unchanged, and identified consent and verification as the two places where AI use most directly engages the Code. A firm that gets the permission right, verifies output before relying on it, and keeps evidence of both is doing what the guidance asks.

This article is general information for registered practitioners and reflects the guidance as issued. Read TPB(GS) 55/2026 itself before setting firm policy.

Authoritative sources

This article is general information for registered practitioners, not personal tax advice. Advisory Stack is a technology platform used by registered tax agents; the registered practitioner remains the adviser of record and is responsible for verifying any output before relying on it.

Related guides

See it in your practice

Advisory Stack is in invite-only pilot for Australian TPB-registered tax and BAS agents. Apply to join the beta — free during the pilot.

Apply to join the pilot