8.1 Disclosures Before Rendering a Financial Service
Key Takeaways
- Before rendering a financial service, the provider must disclose identity and capacity: the representative’s name, that they act for a named authorised FSP, and the contractual/appointment status that explains the relationship with the client.
- Whether the representative is rendering services under supervision must be disclosed proactively — not only if the client asks.
- Contact details of the provider (and how to reach the FSP) and the availability of the complaints process must be made known at the earliest reasonable opportunity before the service unfolds.
- FAIS section 13(1) themes reinforce that a representative may only act within appointment for a licensed FSP and must not hold out as authorised in a false capacity.
- Exam trap: distinguish always-required material pre-service disclosures from information that is only needed if asked or only if a particular fact applies (for example certain optional cover details when irrelevant).
8.1 Disclosures Before Rendering a Financial Service
Quick Answer: Before rendering a financial service, a provider (FSP and its representatives) must, at the earliest reasonable opportunity, disclose who they are, that they act as a representative of a named authorised FSP, whether they are under supervision, how the client can contact them/the firm, that a complaints process is available, and the contractual/appointment status that explains the relationship. These section 3 themes of the General Code of Conduct (GCOC) are proactive duties — not optional extras reserved for inquisitive clients.
Task 4 of RE5 (adhere to the specific Codes of Conduct) expects you to apply disclosure rules in realistic client conversations. Chapter 7 introduced the disclosure framework and conflicts. This chapter turns the framework into practice sequences: what must be said before the service (this section), while rendering the service (8.2), about provider/product supplier roles (8.3), and about fees and remuneration (8.4).
Why “before rendering” is a separate exam bucket
RE5 scenarios often start at the first meeting, first call, or first digital engagement. The Code’s logic is simple: a client cannot make an informed decision about a product if they do not yet know who is speaking, for whom, with what authority, and how to complain if things go wrong.
Pre-service disclosures therefore sit upstream of product talk:
| Stage | Focus |
|---|---|
| Before rendering (GCOC s 3 themes) | Identity, capacity, supervision, contacts, complaints path, contractual status |
| While rendering (GCOC s 4 themes) | Product features, risks, obligations, cooling-off, tax of material nature, performance caveats |
| Provider / supplier / service identity (GCOC s 5 themes) | Who supplies the product vs who renders the service; advice vs intermediary service |
| Fees & remuneration (GCOC s 7 themes) | Nature, amount/basis, payer, frequency, influencing incentives |
If you dump product features first and only mention “I’m with an FSP” after the client has signed, you have already failed the timing discipline taught for RE5.
FAIS section 13(1) themes — appointment and holding out
Section 13(1) of the FAIS Act deals with representatives: a person may not act as a representative of an authorised FSP unless appointed as such, and must act within the conditions of that appointment. Linked practical rules (including holding-out and register themes taught across Task 8) mean a representative must not create the impression that they are:
- an independent FSP when they are only a representative;
- authorised for products outside appointment scope;
- free of supervision when they are under supervision; or
- employed by a product supplier when they are not.
Pre-service disclosure is how the client sees the true capacity. A business card that says “Independent Wealth Partner” while the person is a tied representative of FSP X is a classic honesty and disclosure failure.
Core pre-service disclosures (GCOC section 3 themes)
Study materials map section 3-type duties to a practical checklist. For RE5, be able to list and apply the following.
1. Name and status as representative of a named FSP
Disclose:
- your full name (as the person rendering the service);
- that you are a representative (or, where applicable, that the person dealing with the client is the FSP itself / a key individual acting for the FSP);
- the full name of the authorised FSP you represent;
- that the FSP is an authorised financial services provider (licence identity themes — clients should be able to verify the firm).
Exam phrasing that scores: “I am Sipho Dlamini, a representative of ABC Financial Services (Pty) Ltd, an authorised FSP.”
Wrong phrasing: “I’m with the bank / the insurer” when you are actually a representative of a separate intermediary FSP distributing that bank’s or insurer’s products — unless that is factually true and clearly explained.
2. Whether rendering services under supervision
If you are appointed under supervision (fit and proper / BN 194 supervision framework), that fact must be disclosed to the client. It is not confidential HR information. Clients are entitled to know that competence is still being completed under oversight.
| Situation | Disclosure duty |
|---|---|
| Representative under supervision | Must disclose supervision status |
| Fully competent representative (not under supervision) | No false claim of supervision; do not invent “under supervision” either |
| Client never asks | Disclosure is still required — proactive |
Exam trap: “Disclose supervision only if the client asks.” That option is almost always wrong on RE5. Supervision status is a standard capacity disclosure.
3. Contact details
Provide workable business contact details so the client can reach the representative and/or the FSP (telephone, email, physical/postal address as required by firm process and Code practice). Contact details support ongoing service, complaints, and record integrity. A disposable number that dies after the sale is inconsistent with professional disclosure.
4. Availability of the complaints process
Before the relationship deepens into product choice, the client should know that the FSP has an internal complaints process and how to access it (or at least that it is available and where to find the procedure). Later chapters cover Ombud escalation after internal handling fails; here the point is awareness at the front door.
You do not need to read the entire complaints manual at the first handshake. You do need to make the process visible and available, not hidden until a dispute explodes.
5. Contractual status themes
Explain the nature of the contractual relationship relevant to the engagement, for example:
- whether the client will contract with the product supplier (insurer, CIS manager, bank) with the FSP acting as intermediary;
- whether the FSP will have a mandate or advisory agreement with the client;
- any agency or binder-type arrangement that changes how the service is delivered (at a high level appropriate to pre-service clarity — deeper product-supplier relationship detail also appears under section 5 themes in 8.3).
Contractual status disclosure prevents the client from thinking they have hired “the insurer’s employee” when they have actually hired an independent intermediary, or vice versa.
“Earliest reasonable opportunity” — timing in practice
Disclosures must be made at the earliest reasonable opportunity. Practical teaching points:
- First substantive contact — Identify yourself and the FSP before diving into product recommendations.
- Before advice or transaction — Capacity and firm identity must be clear before the client relies on you.
- Plain language — Use clear English (or another language the client understands in line with firm practice); jargon-heavy licence numbers alone are not “plain.”
- Durable form where appropriate — Written disclosure packs, welcome letters, advice records and call-opening scripts are common firm tools. A signature on a pack helps, but substance still matters if the pack was never explained.
- Remote channels — Phone, video and online journeys still require the same identity and capacity facts; digital scripts must not skip them.
Always-required vs “only if applicable / only if asked” (critical exam trap)
RE5 loves options that mix mandatory pre-service facts with conditional or on-request information.
| Information type | Typical RE5 treatment |
|---|---|
| Named FSP; rep status; supervision status; contact details; complaints process availability | Always required at earliest reasonable opportunity before/as service starts |
| Material product risks, cooling-off, fees for the specific transaction | Required when rendering that service / product (see 8.2–8.4) — not optional |
| Personal salary, school results, hobbies, home address, FSP profit, names of other clients | Not required client disclosures |
| Some operational details only relevant if a fact exists (e.g. certain guarantees or cover when held) | Disclose whether cover is held when the Code requires that category of disclosure (see 8.3) — do not invent cover |
Prep-guide style example:
Question theme: “Must a representative disclose that they are under supervision?”
Correct idea: Yes, proactively.
Wrong idea: Only if the client asks; only to the FSCA; keep it confidential.
Another trap: claiming every possible piece of firm information (annual profit, all other client names) must be disclosed “before service.” That overstates the Code and is as wrong as under-disclosing identity.
Worked scenarios (insurance, investments, banking)
Scenario A — Short-term insurance (personal lines):
Nomsa cold-calls a client about car insurance. She launches into premium comparisons without saying who she is.
Correct approach: Open with name, FSP, representative status, supervision status if applicable, and that complaints procedures exist; then discuss needs and products. Honourable contact also requires regard to the client’s convenience (no abusive timing).
Scenario B — CIS investment advice:
Johan is under supervision for Category I CIS. He tells a client he is a “senior portfolio strategist” for the CIS manager and never mentions FSP Y or supervision.
Analysis: False holding-out + missing pre-service disclosures. Section 13(1) appointment themes and GCOC section 3 themes are both in play.
Scenario C — Banking deposit product:
A bank-employed representative appointed under the bank’s FSP licence meets a client to open a fixed deposit. She correctly names the bank FSP and her role, provides branch contact details, and points to the complaints leaflet in the welcome pack before discussing rates.
Analysis: Pre-service disclosure done properly; product-rate and early-withdrawal risk talk follows under during-service rules (8.2).
Scenario D — “Client didn’t ask”:
A manager says, “Only tell them you’re under supervision if they ask — it kills conversion.”
Correct response: Refuse. Supervision disclosure is required. Manager pressure does not create a Code exemption.
Link to FAIS objects and treating customers fairly
Pre-service disclosure supports the FAIS object of protecting clients by preventing anonymous or misleading market conduct. It is also the first practical expression of treating customers fairly: the client knows the human and the firm behind the recommendation.
RE5 exam tips for this section
- Memorise the pre-service checklist: named FSP, rep status, supervision, contacts, complaints availability, contractual status themes.
- Supervision disclosure is proactive.
- Section 13(1) = appointment / may not act as rep without authority — connect to honest capacity disclosure.
- Reject options that say “only if the client asks” for core identity and supervision facts.
- Keep product-risk detail for section 8.2; do not empty the whole Code into the first minute, but never skip identity.
Before rendering a financial service, which disclosure about capacity is required at the earliest reasonable opportunity?
A representative is rendering services under supervision. When must this be disclosed to the client?
Which combination best reflects pre-service disclosures under GCOC section 3 themes?
How does FAIS section 13(1) support pre-service disclosure practice?