RE5 common mistakes
RE5 · Understand the traps and how to avoid them.
In scenario questions, they treat factual product explanations as advice - e.g. a representative who quotes a fund's fees, explains a policy's waiting period or reads out a product's terms is labelled as having 'rendered financial services by giving advice', and any recommendation or proposal of a financial nature is treated as mere information.
Memorising the word 'advice' without the statutory definition's exclusions, so every client interaction that transfers information feels like advice. The exam deliberately builds scenarios on the boundary (factual advice, objective information, administrative actions) to test the definition, not common sense.
What to do instead
Memorise the definition as a three-part test: a recommendation, guidance or proposal of a financial nature, in respect of a financial product, made or offered to a client. Then drill the exclusion list until you can recite it (factual advice, objective information, administrative actions) and, on every scenario, decide first whether the content was a recommendation or merely a factual or objective statement.
They assume that being employed by, contracted to or 'working under the brand of' a licensed FSP automatically authorises a person to render financial services, and they assume a representative may render any product category the FSP is licensed for. They also miss that the appointment must be in writing and that the FSP must notify the Registrar of appointments and terminations.
Workplace intuition ('I work there, so I'm covered') conflicts with the Act's two-step structure: the FSP is licensed and the representative is separately authorised by written appointment, limited to the FSP and the product categories concerned. Candidates learn the licensing chapter and the representatives chapter as separate topics and never connect them.
What to do instead
Learn the chain explicitly: FSP licensed for specific product categories → written appointment of the representative by that FSP → representative fit and proper → Registrar notified. For each scenario, ask two questions: is this person appointed in writing by this FSP, and is the product category within the FSP's licence? If either answer is no, the conduct is unauthorised regardless of the employment relationship.
They treat the fit and proper assessment as a gate that is passed once - at appointment or licensing - and then answer that a representative who is later sequestrated, convicted of fraud or who stops doing CPD remains 'competent until the licence is next renewed'.
Study material presents fit and proper as a licensing checklist, so it reads as a snapshot. Candidates also conflate licence renewal with re-assessment of personal fitness.
What to do instead
Anchor the phrase 'at all times' to the four pillars (honesty and integrity, competence, operational ability, financial soundness). Practise questions by asking 'what changed after appointment?' - any change to those pillars triggers a duty on the representative to disclose and on the FSP to reassess and, where necessary, act and notify the Registrar.
When asked whether a representative is 'competent', they accept one element as sufficient - for example, twenty years of industry experience with no qualification, or a completed qualification with no regulatory examination - or they dismiss continuing professional development as optional because it is not part of the original appointment.
Competence is a composite requirement in the Determination, but candidates memorise the list of elements as a list of alternatives. Years of practical experience feel like the strongest possible proof of competence, which biases the answer.
What to do instead
Write competence as a checklist that must be fully ticked: qualification and/or experience as prescribed for the category, the regulatory examination at the required level, and ongoing CPD that is planned and recorded. In any question, name the element that is missing rather than judging the person as broadly 'experienced enough'.
They describe the Code of Conduct as a statement of best practice, guidance or a set of recommendations, and they assume it binds the FSP only - so a representative's breach of a disclosure or suitability rule is treated as a service-quality issue rather than a contravention.
Everyday usage of the word 'code' suggests voluntary ethics guidance. Candidates also study the Code under 'conduct standards' and the Act under 'enforcement', and never link a Code breach to regulatory consequences.
What to do instead
Recast the Code as subordinate legislation: it is binding on providers and representatives, and a contravention is non-compliance with the Act that can support a compliance finding, a directive, a penalty or debarment. When a question describes a Code breach, immediately ask what the regulator and the FSP must do about it, not whether it was good practice.
They place the required disclosures only at the start of the relationship and only in general terms - 'the client was told who the representative was at the first meeting' - and they omit items such as the representative's capacity and status, the FSP's licence and product categories, remuneration or commission, and conflicts of interest, or they fail to repeat disclosure when circumstances change.
Disclosure is learned as a list to be memorised, so candidates recall that disclosure happens 'upfront' but lose the content and the timing rule (before or at the time the service is rendered, and again whenever there is a material change).
What to do instead
Build a disclosure script with two columns: what must be said and when. Include identity and capacity, the FSP and its licence status and categories, whether the representative is an employee or independent, remuneration and commission, and conflicts of interest. Then test yourself by asking, for each item, 'would the client know this before they acted?'
They allow retrospective file-building: the record of advice, the client's needs and objectives, and the reasons for the recommendation are reconstructed after the transaction, or only the transaction documents are kept. In answers, they accept a file that contains the application form but no evidence of the advice, the client profile or the disclosures.
In practice administration focuses on getting the product issued, so the paper trail around advice feels secondary; candidates then project that habit into the exam and cannot see why an incomplete file is a compliance failure.
What to do instead
Treat the client file as evidence that must exist before or at the point of advice: client profile and needs, the advice given and its basis, disclosures made, and the transaction record, retained and retrievable for the required five-year period. On every record-keeping question, ask 'could an inspector reconstruct the conversation from this file alone?'
They mix up accountability for supervision and compliance inside the FSP - answering that the compliance officer 'supervises the representatives', or that the representative under supervision is responsible for their own monitoring, or that supervision is only needed once the representative has passed the regulatory examination.
Job titles in the industry blur together, and supervision is studied as a fit and proper condition rather than as a governance duty. Candidates also invert the logic: they think supervision ends when competence is proved, when in fact it is required precisely because competence is incomplete.
What to do instead
Draw the reporting lines once and reuse them: the governing body of the FSP is accountable; the key individual manages and oversees the activities and must ensure compliance for those activities; the compliance function monitors and reports; the supervisor oversees the representative who does not yet meet all competence requirements, and records that supervision. Supervision is a condition of the appointment, not a phase that ends at exam success.
They send every dissatisfied client straight to the FAIS Ombud, and they treat the Ombud as an appeal route against the FSP or as a body that can award any amount and whose determination can be appealed to a tribunal. They also overlook the internal complaints process and its time limit.
The Ombud is the memorable, 'consumer-friendly' part of the syllabus, so it becomes the default answer for every grievance. The procedural path - complaint to the FSP first, a resolution period, then the Ombud - is less vivid and gets skipped.
What to do instead
Memorise the sequence as a flow: complaint to the FSP → internal resolution within the prescribed period (six weeks) → if unresolved or the client is dissatisfied, the Ombud. Then add the jurisdictional limits: the Ombud cannot deal with a matter not first raised with the FSP (unless the FSP has had its time and failed), determinations are binding subject to review by a court, and there are monetary and subject-matter limits on what the Ombud may determine.
They attribute debarment to the Registrar alone, or to the Ombud, and when a scenario involves an FSP debarring a representative they skip the procedural steps - written notification of the intention, reasons, an opportunity to make representations, and reporting the debarment to the Registrar - and they confuse debarment with suspension or withdrawal of the FSP's licence.
'Debarment' sounds like a regulator's sanction, so the FSP's own statutory power to debar is overlooked. The enforcement domain also bundles several distinct powers, and candidates memorise the list of sanctions without matching each power to the body that holds it.
What to do instead
Build a two-column table: FSP powers (debar a representative, with the prescribed procedure and reporting to the Registrar) versus Registrar powers (suspend or withdraw a licence, directives, penalties, and referral for appeal to the tribunal). For every enforcement question, first identify who is acting, then check whether the required procedure was followed - the procedure is usually where the marks are.