Study guide

11.2 Creating, Keeping & Retrieving Records Correctly

RE5 Regulatory Examination — Representatives South Africa

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the RE5 Exam Exam Format, Pass Mark, Booking & Logistics How to Prepare Using Tasks & Qualifying Criteria

2 Chapter 1: The FAIS Act as a Regulatory Framework

1.1 Purpose of the FAIS Act & Client Protection 1.2 Subordinate Legislation Map 1.3 Key Role-Players under FAIS

3 Chapter 2: Financial Products & Services

2.1 Definition & Types of Financial Products 2.2 Financial Services: Advice vs Intermediary Service 2.3 Applying Product Knowledge in the FAIS Environment

4 Chapter 3: Compliance Officers

3.1 Role & Function of the Compliance Officer 3.2 CO Duties, Approval, Independence & Reporting

5 Chapter 4: Maintaining the FSP Licence

4.1 Requirements to Obtain & Maintain an FSP Licence 4.2 How Representatives Help Maintain the Licence 4.3 Display of Licences & Authorisation Visibility

6 Chapter 5: Licence Risk, Undesirable Practices & Offences

5.1 Suspension, Withdrawal & Lapse of Accreditation 5.2 Undesirable Business Practices 5.3 Authority Remedies if Practices Continue 5.4 Offences under the FAIS Act

7 Chapter 6: Key Individuals

6.1 Roles & Responsibilities of Key Individuals 6.2 KI Management & Oversight Duties 6.3 When a KI Loses Honesty/Integrity — Impact on Representatives

8 Chapter 7: GCOC Duties & Conflicts of Interest

7.1 General & Specific Duties of a Provider 7.2 Identifying & Managing Conflicts of Interest 7.3 Disclosure Rules Framework & Impact on the FSP

9 Chapter 8: Disclosure Duties in Practice

8.1 Disclosures Before Rendering a Financial Service 8.2 Disclosures While Rendering a Financial Service 8.3 Provider, Product Supplier & Service Disclosures 8.4 Fees, Commission & Remuneration Disclosures

10 Chapter 9: Advice Process, Custody & Applying the Code

9.1 The Advice Process, Suitability & Record of Advice 9.2 Custody of Financial Products & Client Funds 9.3 Applying the General Code in Day-to-Day Practice

11 Chapter 10: Internal Complaints & Termination of Agreements

10.1 Internal Complaint Handling under the GCOC 10.2 Following Firm Complaints Procedures as a Representative 10.3 Termination of Client Agreements

12 Chapter 11: Record-Keeping Requirements

11.1 Record-Keeping under the FAIS & FIC Acts 11.2 Creating, Keeping & Retrieving Records Correctly

13 Chapter 12: FIC Act & Anti-Money Laundering Duties

12.1 FIC Act Requirements that Apply to FSPs 12.2 FIC Impact on Representative–Client Interactions

14 Chapter 13: The FAIS Ombud

13.1 Role & Authority of the FAIS Ombud 13.2 Ombud Process, Jurisdiction & Outcomes

15 Chapter 14: Representatives & Fit and Proper Requirements

14.1 Roles & Responsibilities of Representatives 14.2 Honesty, Competence, Experience, RE & CPD 14.3 Distinguishing Advice from Intermediary Services

16 Chapter 15: Register of Representatives, Supervision & Losing Fit and Proper

15.1 Purpose & Requirements of the Register of Representatives 15.2 When a Representative Must Work under Supervision 15.3 Disclosure Duties while under Supervision 15.4 Implications if a Representative No Longer Meets Fit and Proper

17 Chapter 16: Debarment of Representatives

16.1 Purpose of Debarment & When It Applies 16.2 Debarment Process & FSCA Notification 16.3 Recourse for a Debarred Representative

11.2 Creating, Keeping & Retrieving Records Correctly

Key Takeaways Explain This Topic AI

Create records contemporaneously — complete advice, disclosure, instruction and complaint notes when the interaction happens, not weeks later from memory

Store records securely with access control, backup and confidentiality; electronic records are acceptable if accessible and readily reducible to written form

Retrieve complete files promptly when lawfully required by the Authority, compliance officer, key individual, or client — GCOC themes include availability for Authority inspection within prescribed timeframes

Do not destroy, alter or backdate records during the retention period; early destruction and fabricated reconstruction are integrity failures

High-yield scenarios include a missing record of advice, a client requesting a copy, and inspection readiness when compliance or the Authority samples files

Last updated: August 2026

11.2 Creating, Keeping & Retrieving Records Correctly

Quick Answer: Record-keeping skill has four legs: (1) create accurate records contemporaneously ; (2) keep them securely under firm procedures for the full FAIS/GCOC/FIC retention periods; (3) retrieve them promptly when the Authority , compliance officer , key individual , or client lawfully requires access; and (4) never destroy, fabricate or backdate during the retention window. A missing record of advice , a botched client copy request , or an unprepared inspection are exam and real-world failure modes.

From statutory map to operating skill

Section 11.1 answered what must be kept and for how long . This section answers Task 5’s second qualifying criterion: can you create, keep and retrieve records correctly as a representative inside an FSP’s systems?

Regulators do not grade your memory. They grade the file . Ombud determinations often turn on whether the provider can show what was disclosed, what needs were recorded, which products were compared, and what the client decided. Compliance monitoring under section 17 samples the same files. Your personal credibility and the FSP’s licence standing both depend on operational discipline.

  • Skill 1 — Create accurate records contemporaneously
  • Why timing matters

A record written while the facts are fresh is evidence. A “reconstruction” written after a complaint is advocacy — and if it invents details, it becomes an honesty and integrity problem.

Contemporaneous practice means:

Completing the record of advice (or equivalent advice documentation) as part of the advice process, not “when I have a quiet Friday”;

Logging client instructions when received (including telephone instructions) with date, time, substance and any risk warnings given;

  • Capturing disclosures made (or confirming that standard disclosure packs were delivered and explained);
  • Opening a complaint record the same day a complaint is recognised, even if investigation continues later;

Filing FICA identification and verification artefacts when onboarding, not after the product is already in force and forgotten.

What “accurate” means

Accuracy is not volume. A ten-page template full of unchecked boxes is worse than a shorter file that truthfully shows:

  • Element Accurate record shows
  • Client information used Material needs, objectives, financial situation, risk tolerance as actually obtained
  • Products considered Real alternatives considered — not a fake list written after the sale
  • Why this product Link between needs analysis and recommendation
  • Disclosures Material risks, fees, cooling-off, provider identity, supervision status where applicable
  • Client decision Acceptance, rejection, or decision to proceed against advice — with warnings recorded
  • Limitations Incomplete information supplied by the client and how that limited the advice
  • Scenario A — Missing record of advice

Facts: Six months after placing a retirement annuity, the client complains that the product was unsuitable. The representative insists the advice was perfect. The file contains an application form and a commission schedule, but no record of advice , no needs analysis, and no note of products considered.

Analysis:

Under the GCOC advice rules, a record of advice must document the basis of the advice (information used, products considered, reasons for the recommendation).

Under GCOC section 3(2) , systems must record and retrieve material documentation relating to the financial service.

Without that record, the FSP cannot demonstrate suitability review, complaint handling becomes defensive, and the representative’s recollection is weak evidence.

Correct conduct at the time would have been: complete the record of advice before or when finalising the recommendation and store it in the firm system immediately.

Exam trap: “The signed application is enough.” An application proves a transaction was concluded; it does not prove advice quality or the basis of the recommendation.

Scenario B — Verbal advice never written down

Facts: On a Teams call, a representative recommends switching a unit trust. The client agrees verbally. The switch is processed. No call note, no record of advice, no confirmation of risks discussed.

Analysis: Verbal channels are still financial services communications contemplated by the Codes. Section 3(2) expressly contemplates recording verbal and written communications. Digital convenience is not a record-keeping exemption.

  • Skill 2 — Store securely (and lawfully)
  • Security is a compliance control, not only an IT preference

“Safe from destruction” and confidentiality duties (GCOC section 3 themes) require more than a cardboard box under a desk:

  • Control Why it matters
  • Access control Only authorised staff should open client files; shared open drives invite leakage and tampering
  • Backup / dual media Server failure is not a defence for non-retrievability
  • Version integrity Final signed records should not be silently overwritten without audit trail

Confidentiality Records contain personal financial information; idle sharing on WhatsApp groups is a dual privacy and Code risk

Third-party storage Outsourcing storage is allowed in principle under FAIS/GCOC and FIC themes, but the provider/accountable institution remains responsible for availability and protection

Electronic records

Electronic storage is expressly contemplated. The practical test taught for RE5:

Can authorised persons access the record within operational deadlines?

Can the record be readily reduced to written or printed form for the Authority, Ombud, client or court process?

Is the electronic system included in business continuity and cybersecurity arrangements proportional to the firm’s risk?

Photos of handwritten notes on a personal phone that only the representative can unlock are a fragile system — not a robust firm procedure.

Retention vs storage location

Do not confuse “we use a cloud CRM” with “we meet five-year retention.” You still need:

  • Retention rules that prevent auto-deletion before the FAIS/GCOC/FIC clocks expire;
  • Exportability if the vendor relationship ends;

Mapping of which repository holds advice files , complaints , section 18 logs , register evidence , and FICA packs .

  • Skill 3 — Retrieve on lawful request
  • Who may require retrieval

Representatives must cooperate with retrieval requests from, among others:

  • Requester Typical purpose
  • Authority (FSCA) Inspection, investigation, licensing or enforcement enquiries
  • Compliance officer Monitoring under section 17; Reg 5 written reporting
  • Key individual / supervisor Oversight, supervision of representatives, remediation
  • Client Record of advice copy; recordings where direct-marketing rules apply; general transparency expectations
  • Ombud processes / legal processes Complaint determination and related proceedings (through firm procedure)

GCOC section 3(2) themes teach that providers must ensure records are available for inspection within the prescribed time when the Authority requests (commonly taught: within seven days ). Firm procedures may set tighter internal SLAs so that the CO can meet external deadlines.

Scenario C — Client requests a copy of the record of advice

Facts: A client emails: “Please send me the record of the advice you gave me last year about my endowment.” The representative is annoyed and replies that records are “internal only.”

Analysis:

Question-bank logic and Code practice treat the record of advice as something the client is entitled to receive as a summary of the basis of advice — not as a secret firm weapon.

Refusing without a lawful basis undermines transparency, damages complaint posture, and can escalate into a formal complaint.

Correct path: follow firm procedure, retrieve the stored record, provide the client with the record of advice content (and any other documents the firm’s policy and law require), and log the request and response.

Exam trap: “Records exist only so the FSP can defend itself; clients never see them.” Defence and client transparency are both legitimate purposes — and poor files achieve neither.

Scenario D — Inspection readiness

Facts: The CO announces that next week the Authority (or an intensive internal audit) will sample twenty advice files, ten complaint files, the representative register extract, and a sample of FICA onboarding packs. Several representatives plan to “update files over the weekend.”

Analysis:

Inspection readiness means files are complete before the notice, because they were built correctly at the time of service.

Weekend backdating of needs analyses or fabricating product comparisons is an integrity failure — often worse than an honest gap with a remediation plan.

Ready firms can retrieve within hours: register current; section 18 categories populated; client files indexed; FICA packs attached; complaint statuses visible.

Practical readiness checklist for a representative’s book of business:

Every advice case has a record of advice (or documented reason if pure intermediary service with no advice).

Disclosures and product documents are stored with the file.

Instructions and material calls are noted or recorded per firm policy.

Complaints touching your clients appear in the firm complaints system , not only in your inbox.

Your appointment and supervision status on the register matches reality.

FICA artefacts for your onboarded clients are complete in the approved system.

You can find any file without relying on a personal laptop that is offline.

  • Skill 4 — No destruction (or alteration) during the retention period
  • What you must not do

Prohibited practice Why it fails

Early destruction to “make space” or “hide a bad file” Breaches GCOC safe-from-destruction and section 18/FIC retention themes

  • Silent alteration of historical advice notes after a complaint Integrity breach; evidential contamination
  • Backdating templates as if they always existed Dishonesty; potential debarment pathway

Private deletion of emails or call recordings contrary to firm retention Obstructs CO/Authority; personal and firm risk

Refusing access to the CO or KI during monitoring Turns a conduct issue into an obstruction/integrity issue

When a genuine error is found (wrong product code typed, incomplete disclosure pack), the lawful path is usually supplement with a dated correction note or remediation , not rewrite history to pretend perfection.

Scenario E — “Delete it; the five years feel long enough”

Facts: A branch manager tells staff to purge all files older than three years to save cloud costs. Some products terminated only two years ago; some FICA relationships ended last year.

Analysis: A casual three-year purge is not aligned with the commonly taught five-year FAIS/GCOC floors, nor with FIC retention triggers. Representatives who participate in unlawful destruction expose themselves. Escalate to compliance/KI; do not execute a purge instruction that contradicts statutory retention.

Putting the four skills into a single workflow

Use this end-to-end loop for every material client interaction: Interact → Capture facts contemporaneously → File into firm system

  • → Secure storage + retention clock → Retrieve on request
  • → Remediate gaps honestly → Never destroy early
  • Stage Representative habit
  • Before the meeting Confirm appointment scope; open or refresh client file; know which disclosure packs apply
  • During the meeting Take structured notes; avoid undocumented “off the record” product promises

Immediately after Complete record of advice / instruction note; upload FICA docs; trigger any required second-level review

  • When something goes wrong Log complaint or incident; preserve the existing file; add dated updates
  • When asked for the file Retrieve via firm process quickly; do not edit first
  • How Task 5 links to other RE5 tasks
  • Task Link to records
  • Task 1 (framework / CO) CO monitors using your files; false information to a CO is serious
  • Task 2 (licence / offences) Record failures can escalate to firm enforcement and offence themes
  • Task 3 (KI) KIs oversee systems that make retrieval possible
  • Task 4 (GCOC) Advice, disclosure, complaints and custody all generate records
  • Task 6 (FIC) Identity and transaction records are parallel duties
  • Task 7 (Ombud) Ombud outcomes often turn on documentary trails
  • Task 8 (representatives) Register accuracy and supervision evidence are record themes
  • Exam focus — choose the option that preserves the trail

When RE5 offers four responses to a record scenario, prefer the option that:

  • Creates a contemporaneous, truthful record;
  • Uses firm systems rather than private side-channels;
  • Retrieves and shares lawfully with client/Authority/CO;
  • Refuses destruction or fabrication ;

Escalates retention or access conflicts to compliance/KI rather than improvising.

Reject options that treat records as optional admin, claim verbal advice needs no trail, deny clients any copy of advice records as a blanket rule, or invent post-complaint paperwork as if it were original.

If you can create cleanly, store securely, retrieve quickly and never destroy early, you have operationalised Task 5 — and you have protected the client, the FSP licence and your own fit-and-proper standing at the same time.