Debarring a representative under FAIS section 14: the order of events, and the file
A representative leaves under a cloud. Section 14 of the FAIS Act tells a brokerage what to do, in what order, and inside which deadlines to notify the FSCA.
FIMA is in force and NAMFISA is watching conduct. How a Namibian brokerage prepares: licences, debit orders and WhatsApp records that stand up to review.
Namibian brokers have talked about FIMA for years; now the talking is over. The Financial Institutions and Markets Act (Act 2 of 2021) came into force in May 2026 after repeated postponements, replacing the Long-term and Short-term Insurance Acts of 1998 that governed the industry for a generation. For a brokerage in Windhoek, Walvis Bay or Oshakati, the question is no longer when FIMA arrives but whether your daily practice — including the WhatsApp conversations where most client contact actually happens — would stand up to a NAMFISA inspection under the new regime.
This article sets out what changes in practical terms, what to do about data protection in a country that does not yet have a data-protection law, and how to turn WhatsApp from a compliance blind spot into your best evidence file. The market fundamentals are on the Namibia country page.
FIMA consolidates the supervision of non-banking financial institutions — insurers, intermediaries, retirement funds, medical aid funds and more — under a modernised framework, with NAMFISA as the supervisor. The detail arrives through subordinate standards and regulations rather than the Act alone, so the exact requirements applying to your licence category should always be checked against NAMFISA's current publications. But the direction is unambiguous, and it rhymes with what South African brokers went through under FAIS:
The sensible posture for 2026 is not to wait for every standard to be litigated, but to run the brokerage now in a way that any conduct supervisor would recognise as controlled. South African neighbours offer a preview of what that looks like in practice — the disciplines in our guide to FAIS record-keeping on WhatsApp translate almost directly.
Namibia currently has no data-protection act in force. A Data Protection Bill has been in preparation for years, but until it is enacted there is no Namibian equivalent of POPIA or GDPR, and no data-protection authority. That is not a licence to be careless, for three reasons. First, a law is coming, and retrofitting consent onto years of harvested contact lists is far harder than collecting it properly from the start. Second, many Namibian brokerages deal with South African insurers and group structures, dragging POPIA-grade expectations across the border contractually. Third, FIMA's fair-treatment logic already frowns on spamming clients or leaking their information, whatever the data statute says.
The pragmatic minimum: record a WhatsApp opt-in before marketing messages, separate servicing from promotion, keep client documents out of personal handsets, and honour every opt-out on first request. When the Namibian law lands, you will be compliant on day one instead of starting a remediation project.
Namibia's payment reality shapes retention. The Namibia dollar is pegged one-to-one to the South African rand within the Common Monetary Area, salaries cluster at month-end, and recurring premiums ride on debit orders. When a debit order fails — insufficient funds in the last days of the month, a changed account, a disputed deduction — the policy starts the slide towards lapse, and the broker usually finds out late.
WhatsApp shortens that loop. A same-day message when the deduction fails, a friendly note before the retry, and a confirmation once the premium is collected keep small failures from becoming cancelled cover — and each message doubles as a record that the client was informed. The timing logic (payday, retries, public holidays) is covered in depth in our guide to premium reminder timing in Southern Africa.
Here is the gap in most brokerages: the regulator-facing files are tidy, but the actual client relationship lives in staff members' personal WhatsApp. Under a conduct regime that is an unowned risk. The fix maps obligation to evidence:
| Supervisory expectation | What the WhatsApp record must show | How to organise it |
|---|---|---|
| Advice and disclosure | What was recommended, what was disclosed, in which words | All client chats on a brokerage number, not personal phones |
| Client instructions | Who asked for what, and when | Threads linked to the client record, searchable by name and policy |
| Premium collection | Reminders sent, failures notified, arrangements agreed | Automated reminder and failed-collection messages, logged per client |
| Complaints handling | Date received, steps taken, outcome communicated | Escalation out of the chat into a tracked process, with the thread attached |
| Accountability | Which staff member said what | Named users in a shared inbox, with an audit trail |
This is precisely the shape of ORIS: one brokerage WhatsApp number, a shared inbox where every conversation sits next to the client's policies, campaigns run from Meta-approved templates, audit logs of who did what, and a CSV export when you need to hand records to an auditor or supervisor. The point is not software for its own sake — it is that under FIMA, "it is somewhere on someone's phone" stops being an acceptable answer.
No — like most financial-sector laws, FIMA is channel-neutral. It regulates the conduct: licensing, fair treatment, disclosure, records. If advice and instructions flow through WhatsApp, then WhatsApp threads are business records, and the brokerage must be able to retrieve and produce them like any other file.
Licence categories and proportionality are set out in NAMFISA's standards, and smaller intermediaries carry lighter reporting than insurers. But the core expectations — fit-and-proper people, honest disclosure, retrievable records, handled complaints — apply to every licensee. Small firms actually benefit most from automating reminders and records, because nobody has spare hands for admin.
Legally there is no Namibian data-protection statute to stop you yet, but it is still a bad idea. WhatsApp blocks numbers that get reported as spam, a Data Protection Bill is in the pipeline, and cross-border insurer relationships often impose POPIA-style duties by contract. Collect opt-ins now and you never have to clean up later.
Three moves, in order: confirm your licence category and the standards applying to it on NAMFISA's site; move client conversations from personal phones onto one brokerage WhatsApp number with named users; and set up automatic premium reminders and failed-debit-order alerts so collection problems surface the day they happen, with a written trace.
FIMA's transition arrangements deal with existing registrants, but do not assume everything is automatic — verify your status, the people registered under it, and any re-licensing steps directly with NAMFISA. Transitional windows have deadlines, and missing one is an avoidable way to interrupt your ability to earn commission.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
A representative leaves under a cloud. Section 14 of the FAIS Act tells a brokerage what to do, in what order, and inside which deadlines to notify the FSCA.
What the FAIS General Code of Conduct requires of an FSP advising clients on WhatsApp: the five-year rule, electronic records, FSCA inspections and the Ombud.
NIC licensing, the Data Protection Act 2012 and MTN MoMo: how Ghanaian insurance brokers run compliant WhatsApp conversations and collect premiums.