Blog · Regulatory
A practical 2026 guide for AFSL holders, authorised representatives and Responsible Managers. Report 798, REP 775, s912A general obligations, DDO, SOA quality, record keeping and breach reporting — what the regulator has actually said and what it means for your practice.
The short answer
Yes. ASIC has not restricted AI use in licensed financial services. The regulator's consistent position across Report 798, REP 775 and public statements from Chair Joe Longo in 2024 and 2025 is that the existing obligations apply in full — s912A general obligations, the FASEA Code of Ethics, the best interests duty, DDO under RG 274, record keeping under s912G and breach reporting under s912DAA. The licensee owns the outcome. The AI tool is a drafting assistant, not a defence.
Between 2023 and late 2025, ASIC moved from scoping AI use to publishing structured expectations. The most relevant documents for financial advisers:
The practical read: ASIC is not drafting a bespoke AI rulebook. It is applying the Corporations Act 2001 and the FASEA Code as written, to a new class of tool.
Section 912A of the Corporations Act sets the general obligations every AFSL holder operates under. Three limbs matter most for AI deployment:
The FASEA Code applies to every relevant provider on the Financial Advisers Register. Two standards carry most of the AI weight:
The licensed adviser's name on the SOA is the point of professional responsibility. That does not move when an AI tool enters the workflow.
DDO requires issuers and distributors to take reasonable steps to ensure financial products reach consumers in their target market. For advisers, that lands most visibly in product shortlisting. If AI tools are used to pre-filter products against a client's circumstances, three guardrails apply:
The SOA is the single most scrutinised document in Australian advice. Where AI drafts it, the licensed adviser's review is what makes it compliant. In practice:
Reviewer responsibility is not a tick-box. It is the step where the s961B best interests duty is discharged.
Section 912G requires AFSL holders to retain records sufficient to demonstrate compliance with their obligations. For AI-assisted work, that extends to the workflow itself:
Seven years is the standard retention period. This mirrors the audit trail most practices already keep for paraplanner-drafted work — it is a format change, not a new obligation.
The reportable situations regime applies to AI-related breaches the same way it applies to any other cause. A materially misleading SOA, a fee-for-no-service outcome, a privacy incident involving client financial data — each attracts the 30-day reporting clock from the point the licensee has reasonable grounds to believe a reportable situation has arisen. The presence of an AI tool is neither a defence nor an automatic aggravator. What ASIC will examine is the governance around the tool: did the licensee have reasonable steps in place?
For AFSL holders rolling AI into their advice workflow in 2026, a workable ASIC-aligned framework:
None of this is new regulatory ground. It is the s912A general obligations, applied methodically to a tool the regulator expects licensees to govern.
FAQ
Does ASIC allow AI in financial advice?
Yes. ASIC has not banned AI use in licensed financial services. Its position, consistent across Report 798, REP 775 and public statements from Chair Joe Longo, is that existing obligations — the general obligations under s912A, the FASEA Code of Ethics, DDO under RG 274 and the best interests duty — apply in full. The licensee remains responsible for outputs whether or not AI was involved.
Do I need to tell clients I used AI to draft their SOA?
ASIC has not mandated a specific AI disclosure to retail clients, but FASEA Standard 5 requires informed consent and Standard 2 requires honesty. If AI materially shaped the advice (not just formatting), good practice is to note the use of AI drafting tools in your FSG and engagement letter. Many AFSL holders are updating these in the 2026 review cycle.
What records should I keep when AI is used to draft advice?
Section 912G requires records sufficient to demonstrate compliance. For AI-assisted work, keep the prompt, the AI output, the adviser's edits and the final signed document on the client file. Seven years is the standard retention period. This mirrors the paraplanner audit trail most practices already maintain.
Is an AI-generated SOA a breach of the best interests duty?
No, provided the licensed adviser retains professional judgment and the SOA genuinely reflects the client's circumstances and goals. The best interests duty under s961B is a duty of the adviser, not the tool. An SOA that is AI-drafted but adviser-reviewed, personalised and accurate meets the standard. One that is rubber-stamped without genuine review would not.
When is an AI issue a reportable situation under s912DAA?
If AI contributes to a breach of a core obligation — a materially misleading SOA, a fee-for-no-service outcome, or a privacy breach — the reportable situations regime applies the same way it would for any other cause. The 30-day clock starts when the licensee has reasonable grounds to believe a reportable situation has arisen.
Does ASIC's Report 798 apply to financial advisers?
REP 798 focuses on general and life insurers, but ASIC has been explicit that its themes — governance, explainability, consumer outcomes, fair treatment, oversight — apply across licensees. Advisers using AI for SOA drafting, portfolio commentary or client triage should read REP 798 as a signal of regulatory expectation across the broader AFSL population.
Claude Cowork training for Australian financial advisers — ASIC-aligned workflows, licensed adviser sign-off retained, SOA drafting compressed by 70%.
From A$249 per person · Team (up to 5) A$549 · Implementation from A$3,500