Treat FNS41820 study as labelling practice under time pressure. For every client statement you read, decide three things: whether the interaction is factual information, general advice, or personal advice; whether the client is retail or wholesale in that context; and which document and disclosure obligations attach. Then test your own written work with a traceability check: can a reviewer connect each recommendation to the recorded objectives, financial situation, and needs? Build a five-week routine around these two checks and use the rubric in the final section to judge when your case-study answers are genuinely finished.
General advice vs personal advice: labelling what the interaction actually is
Personal advice is provided when one or more of a client's objectives, financial situation, and needs have been considered; general advice is a recommendation or opinion given without that consideration. The label determines warnings, documents, and conduct obligations.
Start from the trigger, not the tone of the conversation. A factual statement about a product, such as what a term deposit pays or what a managed fund invests in, is information, not advice. The moment you add a recommendation or opinion, you are giving general advice, which must carry a warning that it does not consider the person's circumstances. If you have considered the person's objectives, financial situation, or needs, the interaction becomes personal advice, which brings a best interests style obligation and, for retail clients, documentation expectations. Note that general advice can be given directly to a person; the classifier is whether circumstances were considered.
Worked scenario: a branch customer says, "I have $20,000 sitting in my transaction account and I want a better return." A staff member compares term deposit rates at length and concludes, "the 12-month term deposit is the best option for you." The plausible mistake is treating this as harmless product information. The phrase "for you", combined with the customer's stated amount and goal, means the customer's situation has been considered, so the statement is personal advice delivered without a fact-find or authority. The better decision is either to stay strictly within factual information about rates and features, or to refer the customer to someone authorised for personal advice. The label matters because the framework attaches protections to personal advice that the customer did not receive here.
| Attribute | Factual information | General advice | Personal advice |
|---|---|---|---|
| What triggers it | A question answered with facts only | Facts plus a recommendation or opinion | A recommendation made after considering the client's objectives, situation, or needs |
| Typical wording | "This fund invests in listed shares." | "A balanced fund may suit investors like you." | "Based on your goals and situation, I recommend..." |
| Key disclosure | None required for the statement itself | A warning that the person's circumstances have not been considered | Warnings plus documentation of the basis of advice and remuneration |
| Conduct expectations | Accuracy | Accuracy and the required warning | Best interests conduct, fact-finding, and documented reasoning |
Retail and wholesale clients: why the classification changes the paperwork
Australian financial services law distinguishes retail from wholesale clients using defined tests covering the client's nature, financial position, and the transaction context. Retail clients receive the stronger disclosure and dispute-resolution protections.
Learn the concept as a default-plus-exception structure. A client is treated as retail unless a recognised wholesale category applies, such as professional investors, large businesses meeting size tests, or persons certified as sophisticated in defined contexts. The consequences are what you must be able to state: disclosure documents, advice documentation, and external dispute resolution access are built primarily around retail clients, so a wholesale classification removes or reduces several of those protections. The tests are contextual, meaning the same organisation can be retail for one product or transaction and wholesale for another.
A short application case shows why assumptions fail. A company director with a substantial property portfolio assumes the business is automatically a wholesale client for all services. The better decision is to run the applicable tests for the specific service being provided and record the conclusion in the file, because relying on an untested assumption means the client may have received a service stripped of protections they were entitled to. In practice this means your study notes should pair each wholesale category with two things: the kind of evidence that supports it and the protections that turn off once it applies. That pairing is what case-study questions ask you to reason through.
Fact-finding: connecting every recorded fact to a decision you must later justify
A fact-find should collect objectives, financial situation, and needs in enough depth to give a reasonable basis for the advice, with every entry capable of being traced to a recommendation or an explicit scoping decision.
Distinguish the two layers of a fact-find. Hard facts are measurable: income, assets, liabilities, existing insurance, superannuation balances, and current holdings. Soft facts are interpretive: goals, time horizons, risk tolerance, family commitments, and preferences. Both layers matter, and they fail differently. Missing hard facts make a recommendation unquantifiable, while shallow soft facts make the reasoning indefensible. A file should also record the source and date of each item, because a reviewer assessing the basis of advice reads the fact-find as evidence, not as background colour.
In-section exercise: take a blank fact-find template and, for every field, write one sentence naming the advice decision that field would drive. For example, an investment time horizon field drives product selection and risk framing; a dependants field drives insurance needs analysis. Fields with no link are either candidates for removal or signals you need follow-up questions. Expected observations: risk tolerance cannot be captured by a yes or no answer, so you should end up writing scenario-based probes, such as how the client would react to a defined fall in their portfolio, and you should notice that several template fields only matter for particular advice scopes.
Products and markets: comparing features against needs instead of reciting descriptions
Product knowledge at this level means mapping the features, risks, fees, and access constraints of common product classes, such as deposits, managed funds, insurance, and superannuation, onto a specific client's circumstances and objectives.
Anchor each product class to the concepts that drive suitability. Liquidity describes how quickly value can be accessed; time horizon measures how long the client can leave money invested; the risk-return trade-off links higher expected returns to wider outcome ranges; diversification describes spreading exposure; and insurance needs analysis links cover types to the consequences of death, illness, or disability. When you compare two products, compare them through these lenses: a term deposit and a managed fund differ less in headline numbers than in certainty, access, and who bears market risk.
Build a needs-to-feature matrix as your core practice method. For a case-study client, list their needs down one axis and candidate product features across the other, then mark each intersection as a match, a mismatch, or a neutral fit, with a one-line justification. This trains the reasoning style assessments look for when they ask you to explain a recommendation rather than name a product. The self-check is simple: if you cannot explain a mismatch, such as why an inaccessible high-return product fails a client who may need funds within a year, you do not yet know the product class well enough.
Advice documents: what the basis section must let a client verify
Personal advice to retail clients is documented in a statement of advice showing the basis of the advice, the advice itself, and remuneration and association information; a record of advice can apply in defined situations where no statement was given at the time.
Learn the document family by function rather than by name alone. A financial services guide tells the client who they are dealing with and how complaints are handled. A statement of advice is the substantive record for personal advice: the basis section states the client circumstances relied on, the advice section states the recommendations, and further sections cover remuneration and any associations that could influence the advice. A record of advice covers personal advice given without a statement of advice in the circumstances that permit it. General advice instead relies on shorter warning statements. The discipline to internalise is that the basis and the advice are read together.
Worked scenario: a draft statement of advice recommends a balanced managed fund, but the attached fact-find records only the client's age and income. The plausible mistake is submitting the document because the recommendation line is technically present and the fees are disclosed. The better decision is to go back and record objectives, needs, and risk attitude, or to narrow the advice scope to what the file actually supports, because a reviewer reading the basis section cannot verify that the recommendation follows from the client's circumstances. This matters because the document is designed to let the client, and any later reviewer, test the reasoning; a gap between basis and advice is a substantive defect in the advice process, not a formatting issue to tidy up before submission.
Ethics and conflicts: testing whether a rationale survives without the incentive
Professional conduct means identifying remuneration and associations that could influence a recommendation, disclosing them clearly, prioritising the client's objectives, and handling personal information confidentially. Conflicts are addressed through disclosure, avoidance, or structural controls.
Define the concepts precisely so you can recognise them in a case study. A conflict of interest exists where a benefit, relationship, or incentive could reasonably influence, or appear to influence, the recommendation. The regulatory response operates on several levels: the client must be told about remuneration and relevant associations, the provider owes conduct obligations toward the client's interests, and personal information collected during fact-finding must be protected. Distinguish a conflict itself, which is a structural fact about the situation, from a breach, which occurs when the conflict is not disclosed or not managed.
Practical exercise with an expected observation: take a scenario with three product options where one pays the provider more, and write two separate rationales for your chosen recommendation. The first states the client-need reasoning only; the second adds the full disclosure statement. The expected observation is diagnostic: if your need-based rationale only makes sense when the higher-payment option is selected, the file has a conflict worth escalating or rescopeing, whereas a rationale that survives on client grounds alone simply needs clean disclosure. Practise this pattern until writing the disclosure feels like part of the reasoning, not an appendix added at the end.
A five-week preparation sequence with a self-check rubric
Sequence the topics so each week produces an applied output: labelled statements, classified client cases, a drafted fact-find, a drafted basis-and-advice pair, then a full case study reviewed against the rubric below.
Week one: learn the advice-type definitions, then classify a set of twenty mixed statements as information, general advice, or personal advice, writing one sentence of justification each. Week two: work through client classification cases, pairing each wholesale category with its supporting evidence and the protections that change. Week three: complete the fact-find field-linking exercise from section three on two different case clients. Week four: draft a statement of advice basis and advice section for one client and deliberately break the traceability, then repair it. Week five: complete one full case study end to end and review it with the rubric. Adapt the sequence to your training organisation's materials and assessment requirements.
Use the rubric as learning milestones, not as a prediction of any assessment outcome. Score each item and rework anything below your own target before moving on. The observations to expect: classification decisions become fast and consistent, your fact-find drafts stop containing unlinked fields, and your written rationales start naming the client circumstance that drives each recommendation without prompting.
- Classification check: out of twenty mixed statements, you can label each one correctly and state the trigger, for example which circumstance was considered, in at least eighteen cases.
- Client classification check: for three case clients you can state retail or wholesale treatment, the test relied on, and two protections that change as a result.
- Fact-find check: every field in your draft links to a stated advice decision, and soft facts use scenario-based probes rather than yes or no answers.
- Document check: a reviewer reading your basis section can connect each recommendation to a recorded client circumstance without asking you anything.
- Ethics check: your rationale survives when the incentive is removed, and your disclosure names the benefit, the parties, and where the client can find more detail.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.