ROA vs SOA in Australia explained: when each applies, where firms get it wrong, and a 3-question framework to choose right every time.
The cost of delivering financial advice in Australia keeps rising. Adviser numbers have fallen 48% since 2018. Paraplanning queues are longer. Turnaround times are slower. And every week, another firm asks the same question: can we use an ROA here instead of an SOA?
The question itself reveals the problem.
Most firms treat the choice between a Record of Advice and a Statement of Advice as a compliance threshold. A gate they either need to pass through or can skip. But that framing misses the real opportunity.
The ROA vs SOA decision is not just a documentation question. It is an operational design decision that directly affects how fast your firm can move advice from meeting to client, how much that process costs, and how confidently your compliance team can stand behind the result.
Firms that understand this distinction properly build faster advice workflows. Firms that treat it as a box-ticking exercise either over-document everything (expensive and slow) or under-document selectively (risky and defensible only until someone checks).
The Corporations Act sets out three situations where an ROA may substitute for an SOA.
First, further advice where the client's relevant circumstances have not significantly changed since the last SOA or ROA. This is the most common scenario in practice and the one that creates the most confusion.
Second, advice that does not include a recommendation to acquire or dispose of a financial product and where no remuneration, commission, or other benefit is received in connection with the advice.
Third, advice about an investment amount of less than $15,000 where the client has not previously been given advice by the same provider (or a related provider) about financial products in the same class that, combined, exceeds $15,000.
ASIC's FAQ on ROAs adds important colour to that first scenario. "Significantly different" is not a mechanical test. It requires the adviser to make a genuine assessment of whether the client's circumstances, objectives, financial situation, or needs have materially changed in ways that affect the basis for advice.
That assessment needs to be recorded. If your file note does not explain why the ROA pathway was appropriate, you have a gap that only becomes visible when someone reviews the file.
Many firms default to thinking of an ROA as a "short SOA." That is incorrect and it leads to operational mistakes in both directions.
An SOA carries specific disclosure requirements. It must include the advice, the basis for the advice, the provider's remuneration and associations, warnings where relevant, and information about the client's right to request further details. The structure is prescribed by law.
An ROA has fewer formal content requirements, but it still needs to record the advice provided and the basis on which it was given. Under ASIC Corporations Instrument 2024/508, the record must also capture the information relied on to demonstrate that client interest priority obligations were met.
That second point is relatively new in its emphasis and it matters.
An ROA is not a lighter compliance obligation. It is a different documentation pathway that still requires a clear record of what was advised, why, and on what basis. Firms that treat it as a permission to write less are missing the point.
The practical difference is this: an SOA is a formal document you hand to the client before implementation. An ROA is a record that must be available if requested, and must exist regardless. Both need to stand up to the same scrutiny if a complaint lands or ASIC asks questions three years later.
Three patterns show up repeatedly in advice businesses that struggle with ROA vs SOA decisions.
Some firms, especially those with conservative compliance cultures, require an SOA for every piece of advice regardless of whether the conditions for an ROA are met.
The intention is understandable. The impact is not.
Over-documenting drives up paraplanning cost, extends turnaround times, and creates a bottleneck that limits how many clients your firm can serve. When an SOA takes two to four weeks and costs $1,500 to $3,000 in paraplanning time, producing one where an ROA would suffice is not cautious. It is wasteful.
With adviser numbers in Australia at roughly 15,135 as of March 2026 and the FAAA arguing that the shortage is structural, capacity is not something firms can afford to spend on unnecessary documentation.
The opposite failure. A firm uses ROAs routinely for ongoing clients but the file note does not explain why the ROA pathway was available.
The note might say "annual review, no significant changes" without specifying what was actually assessed. That is not a defensible record. It is a statement of conclusion without evidence.
ASIC has been clear that the assessment of whether circumstances have significantly changed is a substantive obligation. Recording the outcome without showing the work creates a gap that becomes expensive during complaints handling, breach assessment, or audit.
In multi-adviser firms, the ROA vs SOA decision often varies by individual habit rather than firm policy. One adviser uses ROAs for most review clients. Another defaults to SOAs. A third uses ROAs but structures them differently each time.
The compliance team then inherits variability that is difficult to supervise at scale. And when paraplanning receives a case, the first question is always: "What are we producing here?" That question should already have a clear answer based on firm process, not individual preference.
Instead of treating ROA vs SOA as a one-off decision, build a structured assessment into your advice workflow. Three questions are enough.
Question one: is this further advice where the client already has a current SOA or ROA?
If no, you need an SOA. Full stop.
If yes, proceed to question two.
Question two: have the client's relevant circumstances changed significantly since the last advice document?
This requires a genuine assessment covering objectives, financial situation, needs, risk profile, and any life events. If there has been a significant change, you need an SOA.
If circumstances are materially the same, an ROA may be appropriate. Record what you assessed and why you concluded the change was not significant.
Question three: does the advice include a product acquisition or disposal recommendation with associated remuneration?
If the advice involves buying or selling financial products and remuneration is involved, the ROA pathway under the second limb is not available. Check whether the first limb (further advice, no significant change) applies instead.
This is not a complex framework. But formalising it removes the guesswork and gives compliance teams a consistent basis for supervision.
If the threshold test supports an ROA, the document still needs substance. A defensible ROA for an ongoing advice client should include the following.
The purpose and context of the interaction. Annual review, strategy adjustment, insurance reassessment, or a specific client request.
The assessment of client circumstances. What was reviewed and whether anything material has changed. Be specific. "Reviewed employment status, super balance, insurance cover, estate planning. No material change since March 2025 SOA" is far more useful than "circumstances unchanged."
The advice provided and the reasoning behind it. This is where most ROAs fall short. If you recommended switching an investment option, rebalancing a portfolio, adjusting contributions, or maintaining the current strategy, say why. The reasoning is the record.
Any risks, trade-offs, or limitations discussed with the client. If you flagged sequencing risk on a drawdown strategy, or noted that the client declined insurance advice, record it.
The information relied on. Under the updated record-keeping focus, you need to capture the inputs that informed the advice. Reference the fact find, portfolio data, product information, modelling, and any third-party documents used.
The client response and agreed next steps. Did they agree to proceed? Request more time? Decline part of the recommendation? Who is responsible for implementation?
None of this requires a 50-page document. A well-structured ROA for an ongoing client might be two to five pages. The discipline is in completeness and consistency, not volume.
This is the part most firms miss when they think about ROA vs SOA.
The choice between document types is not a standalone compliance question. It is a workflow design question that affects everything downstream.
When your firm has clear rules for when an ROA applies and a standardised structure for what it contains, three things happen.
First, paraplanning becomes faster. The paraplanner knows what they are producing before they start. No back-and-forth to clarify scope, no rewriting because the format was wrong, no wasted effort on an SOA that could have been an ROA.
Second, compliance review becomes more efficient. Reviewers know what to expect. They can assess an ROA against a known standard rather than interpreting each one as a unique document. Supervision at scale becomes possible.
Third, the firm can serve more clients without proportional increases in admin headcount. If annual reviews for clients with stable circumstances can be processed through a standardised ROA workflow instead of a full SOA cycle, the capacity gain is significant.
This is where the numbers matter. If an outsourced SOA costs $2,000 and takes two weeks, but a well-structured ROA can be produced internally in a day, the difference across 100 annual reviews is $200,000 in paraplanning cost and months of calendar time.
That is not a compliance distinction. That is an operating model decision.
AI can accelerate both SOA and ROA production. But the value differs depending on how your firm uses each document type.
For SOAs, AI is most useful in drafting the structural sections: client circumstances, strategy rationale, product analysis, and disclosure content. The document is long and complex enough that a strong first draft saves significant paraplanning time. This is where tools that generate 50-page advice documents earn their keep.
For ROAs, the AI opportunity is different and arguably more impactful at scale.
Because ROAs are produced more frequently for ongoing clients, the cumulative time cost is enormous even though each individual document is shorter. AI that can take a meeting transcript, assess it against the existing client record, identify what has changed, and produce a standardised ROA draft is solving a high-volume, high-repetition problem.
The critical requirement is that any AI-assisted ROA workflow must preserve the assessment step. The system should not assume an ROA is appropriate. It should prompt the adviser to confirm that the threshold test is met and record the basis for that decision.
This is where advice-specific platforms differ from generic AI tools. A general meeting transcription tool will give you a summary. It will not ask whether the circumstances have significantly changed since the last SOA, flag missing fact find data, or structure the output to meet record-keeping obligations.
related: AI-built Statements of Advice
Firms that get the ROA vs SOA framework right tend to share a few characteristics.
They have a written policy that defines when each document type applies, not as a guideline but as a process standard that advisers follow.
They use a consistent template for ROAs that maps to the required elements. The template is not optional.
They record the threshold assessment in the file note, every time. The assessment of whether circumstances have significantly changed is part of the meeting workflow, not an afterthought.
They review ROAs with the same rigour as SOAs. Lighter documentation does not mean lighter supervision.
And they measure the impact. Turnaround time. Cost per document. Rework rates. Compliance review exceptions. These are the numbers that tell you whether your workflow is actually working.
The firms that do this well do not just save money. They create capacity. They reduce risk. And they build a documentation practice that holds up when it matters most: when a client complains, when a breach needs assessing, or when a regulator asks to see the file.
If your firm is still debating ROA vs SOA on a case-by-case basis, the fix is not a better template.
The fix is a clear decision framework embedded in your advice process, supported by consistent documentation standards, and reinforced by supervision that holds everyone to the same approach.
Get that right and the document type becomes a natural output of the workflow rather than a judgement call made under time pressure at the end.
The cost of advice in Australia is not coming down by itself. Adviser numbers are still falling. Client expectations are still rising. The firms that thrive will be the ones that find ways to deliver more advice, faster, without compromising the quality of the record.
ROA vs SOA is one of the clearest places to start.
See how advice firms are boosting capacity without compromising compliance or trust. Book a demo to see AdviseWell in action.
.png)
