_edited.png)
SoA Compliance Requirements Australia: What Every Adviser Needs to Know
Find out if your SoAs would pass scrutiny today. No obligation.
A Statement of Advice is arguably the most scrutinised document in providing financial advice. This guide covers what the law requires, what ASIC looks for and where advisers most commonly fall short.
_edited.png)
What is a
Statement of Advice?
A Statement of Advice (SoA) is a document that must generally be provided to a retail client when a financial adviser provides personal financial product advice on behalf of an Australian Financial Services (AFS) licensee.
​
The SoA explains the advice being provided and sets out the basis on which the advice has been prepared. It records the client's relevant objectives, financial situation and needs, the recommendations being made, and the reasons those recommendations are considered appropriate.
​
Under the Corporations Act 2001 and ASIC Regulatory Guide 175 (RG 175), the SoA should clearly demonstrate the link between what the adviser knows about the client and the advice that has been recommended. It may also disclose fees, remuneration, associations or conflicts of interest, and any significant risks or consequences associated with the recommendations.
​
In essence, an SoA tells the story of the advice and explains why the recommendations are considered appropriate for the client's circumstances.
The legal framework governing SoAs
SoA obligations draw from several sections of the Corporations Act 2001, working together rather than in isolation. Understanding the full framework matters, because ASIC reviews SoAs against all of these provisions - not just the content checklist in s947B.
CORE CORPORATIONS ACT PROVISIONS
Mandatory content for SoAs issued by an authorised representative - mirrors s947B with minor differences, including the requirement to name the licensee
Mandatory content for SoAs issued by a financial services licensee
Additional disclosure obligations where advice involves replacing one financial product with another
Best Interest Duty - the overarching obligation the SoA must demonstrate compliance with. Section 961B(2) provides a safe harbour: completing seven prescribed steps is taken to satisfy the duty.
The appropriateness obligation - advice must be appropriate to the client's specific objectives, financial situation and needs, separate from and in addition to the best interests duty
The warning obligation - where advice is based on incomplete or inaccurate client information, the adviser must warn the client
What must be included in an SoA
Under sections 947B and 947C, every SoA must address the following elements. Satisfying these content requirements is necessary but not sufficient - the document must also demonstrate best interests (s961B) and appropriateness (s961G).
01
The advice
A clear statement of what is being recommended: the products, strategies or actions the client is being advised to take or not take
02
Basis for the advice
An explanation of how the advice was reached - how the client's objectives, situation and needs were weighed, and how recommendations address them. Must reflect genuine best interests analysis, not a pro forma rationale.
03
Adviser identity
Describe the service and how customers or clients can benefit from it.
04
Remuneration & benefits
Describe the service and how customers or clients can benefit from it.
05
Conflicts of interest
Any financial or non-financial interests, direct or indirect, that could reasonably have influenced the advice
06
Warnings (s961H)
Where advice rests on incomplete or inaccurate client information, the adviser must flag what is missing and warn that the advice may not fully reflect the client's circumstances
07
Product replacement disclosure
(switching)
Where advice rests on incomplete or inaccurate client information, the adviser must flag what is missing and warn that the advice may not fully reflect the client's circumstances
What ASIC expects beyond the content checklist
An SoA that ticks every content box under s947B can still fail an ASIC review. The best interest duty (s961B) and the appropriateness obligation (s961G) set a higher bar - one focused on substance, not just form.
Demonstrating best interests, not just asserting it
Section 961B(1) requires advisers to act in their client's best interests. Section 961B(2) provides a safe harbour through seven prescribed steps: identify client objectives and needs; make reasonable inquiries where information is incomplete; confirm competence to provide the advice; investigate suitable strategies and products; base recommendations on those investigations; ensure the advice is appropriate to the client's circumstances; and prioritise the client's interests. The SoA must show these steps were taken in substance - not just referenced in passing.
Appropriateness under s961G
Even where the best interest process is satisfied, advice must separately pass the appropriateness test - it must suit this client's specific objectives, financial situation and needs. An SoA that documents the process but recommends something objectively unsuitable will still breach s961G.
Client-specific goals and circumstances
ASIC has consistently found fault with SoAs containing generic objectives - "to grow wealth", "to protect assets" - with nothing more specific. The document should reflect the actual conversation: what the client said they want, by when, and subject to what constraints.
Product suitability reasoning
Where a specific product is recommended, the SoA should explain why that product was selected over alternatives - not with an exhaustive comparison, but enough to show the choice was deliberate and client-focused.
Tailored risk disclosure
Risk disclosures must be specific to what the client is being recommended and their circumstances. A standard-issue risk paragraph that could appear in any SoA does not meet the standard.
How detailed does an SoA need to be?
There is no mandated length. ASIC acknowledges that the appropriate style, content, layout and length will vary with the scope and complexity of the advice being given. A scaled or limited-scope SoA can be brief - provided it addresses every required element for that scope.
​
What fails is not brevity but incompleteness. A long document that still doesn't connect advice to the client's circumstances is no more compliant than a short one. And a short document that genuinely addresses best interests, appropriateness and all relevant disclosures for its scope is entirely acceptable.
​
A useful review test: could a compliance reviewer, reading the SoA cold with no other context, identify who this client is, what was recommended, why it was in their best interests, why it was appropriate to their circumstances, and what alternatives were considered and set aside? If any of those questions are left unanswered, the document needs more work.
Common SoA compliance failures
An SOA that ticks every content box under s947B can still fail an ASIC review. The best interest duty (s961B) and the appropriateness obligation (s961G) set a higher bar - one focused on substance, not just form.
Best interests not demonstrated
The s961B(2) safe harbour steps are referenced but not evidenced; the document asserts best interests without showing the work.
Appropriateness not addressed
the s961G obligation is treated as automatic once best interest is satisfied; it is not.
Vague client objectives
Goals lack specificity, timelines or constraints, making it impossible to assess whether the advice addresses them.
Generic risk disclosure
Standard risk language not tailored to the products recommended or the client's individual situation.
Incomplete remuneration disclosure
Ongoing fees, platform costs, indirect benefits or referral fees (Reg 7.7.11) not captured.
Fact-find not documented
Key client information gathered verbally but not recorded in the SoA or a contemporaneous file note.
Switching disclosure absent
s947D costs and lost benefits not documented where a product replacement was recommended.
Scope not defined
Where scaled or limited advice is given, the document does not state what was and was not considered, leaving it open to challenge.
How RegiReview helps
Producing compliant SoAs isn't just about understanding the obligations. It's about applying them consistently, across every file, under the time pressure of a real practice - and keeping pace with a regulatory framework that continues to shift.
​
RegiReview gives advisers and licensees the tools to do that.
Review SoA documents against current Corporations Act and ASIC requirements before they reach clients
Identify specific gaps - not just where a section is weak, but what's missing and how to address it
Build consistency across your practice and reduce the risk of licensee audit findings
Stay across ASIC updates and DBFO reforms without tracking them manually
Go deeper
Explore the full suite of articles on this subject
_edited.png)