An insurer declines a claim for non-disclosure. What section 53 obliges it to prove, what your inception file must show, and the claims clocks that start next.
The repudiation letter is usually two paragraphs long. The insurer declines the claim because information was not disclosed when the policy was taken out — a previous loss, a modification, business use of the vehicle, a health condition — and states that, had it known, it would have underwritten differently. The client forwards it to the brokerage with three words attached: but I told you.
Whether that sentence is true, and whether anything in your file can show it, decides everything that follows. Non-disclosure is not a technicality an insurer may reach for at will: South African law sets a test, the insurer carries the onus on it, and the broker sits in the middle of the only conversation capable of satisfying or defeating it. This is what the statute actually requires, where the disclosure record is really made, and what has to happen once a claim has been declined.
Section 53 of the Short-term Insurance Act 53 of 1998 is one of the conduct provisions deliberately left standing when the Insurance Act 18 of 2017 stripped the prudential ones out. It says that a policy shall not be invalidated, the insurer's obligation shall not be excluded or limited, and the policyholder's obligations shall not be increased on account of a representation that is untrue or a failure to disclose information — whether or not the disclosure was warranted to be true — unless the representation or non-disclosure is such as to be likely to have materially affected the assessment of the risk under the policy at the time of its issue or at the time of any renewal or variation of it. Section 59 of the Long-term Insurance Act 52 of 1998 does the same work on the life side.
Two things in that sentence do most of the arguing.
Materially is defined objectively. Section 53(1)(b) says a representation or non-disclosure is material if a reasonable, prudent person would consider that the particular information should have been correctly disclosed to the insurer so that the insurer could form its own view as to the effect of that information on the assessment of the relevant risk. That is not the same as asking what this insurer says it would have done, and it is not a question about whether your client meant to hide anything. It is a notional-person test, and the case law on how our courts apply it is summarised well in De Rebus. The practical consequence for a brokerage is that arguments about the client's state of mind rarely rescue a claim; arguments about what was in fact said to the insurer sometimes do.
The duty does not stop at inception. The section expressly reaches the time of any renewal or variation. A vehicle that acquires a tracker, an alarm that is removed, a home that becomes a workshop, a driver added, a sum insured raised — each of these is a moment at which risk is reassessed, and each is a moment where a WhatsApp thread either contains the disclosure or does not.
Most brokerages think of disclosure as an inception event and file it accordingly. Insurers do not, and neither does the statute.
| Moment | What the insurer will later ask for | What has to be in your file |
|---|---|---|
| Inception | The proposal answers and who supplied them | The client's own words on the material questions, plus what you told them about the consequences of getting them wrong |
| Renewal | Whether the client was asked to confirm that nothing had changed | A dated request to confirm or update, and the client's reply — silence is not a reply |
| Mid-term variation | What changed, when you knew, and when the insurer was told | The message that raised it, the endorsement request and the insurer's confirmation |
The middle row is where brokerages lose. A renewal invitation forwarded with please confirm all still correct and no follow-up produces no record at all. A short, specific question — has anyone new started driving the vehicle, has the business added a second premises, has anyone on the funeral policy been diagnosed with anything since we last spoke — produces one, whichever way the client answers.
The General Code of Conduct is explicit. Section 7(1)(d) requires a provider to fully inform a client, in relation to the completion or submission of any transaction requirement, that all material facts must be accurately and properly disclosed and that the accuracy and completeness of all answers, statements or other information provided by or on behalf of the client are the client's own responsibility; that if the provider completes or submits a transaction requirement on the client's behalf, the client should be satisfied as to the accuracy and completeness of the details; of the possible consequences of misrepresentation or non-disclosure of a material fact or the inclusion of incorrect information; and that the client must on request be supplied with a copy of any transaction requirement. Section 7(1)(c)(vii) separately requires concise details of special terms, exclusions of liability, waiting periods, loadings, penalties, excesses and circumstances in which benefits will not be provided.
Read subparagraph (ii) against how a brokerage actually works on WhatsApp. The client sends a forty-second voice note. A member of the team listens to it and types the answers into the insurer's portal. That is the provider completing a transaction requirement on the client's behalf, and the Code says the client should be satisfied as to the accuracy and completeness of what was entered. Sending the completed answers back into the thread and asking the client to confirm them takes ninety seconds and converts a repudiation argument into a document. It is the same discipline that underpins a defensible record of advice when the sale happened on WhatsApp.
The Policyholder Protection Rules (Short-term Insurance), 2017 govern what the insurer must now do, and a broker who knows rule 17 is worth considerably more to the client than one who forwards the letter with condolences.
Those ninety days are the client's real remedy and they are routinely wasted. Representations are not an appeal letter; they are the opportunity to put the disclosure record in front of the insurer. If your thread shows the question asked, the answer given and the confirmation sent, that is what goes in. If the matter then becomes a complaint rather than a claim dispute, the routing question is separate and worth getting right — we covered it in the guide to which ombud a declined-claim complaint belongs to.
None of this is a software problem, but software decides whether the record exists. In ORIS the WhatsApp conversation sits against the customer record rather than in one adviser's handset, so a disclosure made in a thread two renewals ago is still retrievable when a claim is declined — including after the representative who took it has left. Renewal and policy-anniversary reminders run off lifecycle triggers rather than a diary somebody stopped updating, so the specific renewal question actually goes out. Audit logs show who sent what and when, and the book exports to CSV when a compliance officer or an ombud wants to look across the file. What the platform will not do is decide which facts were material, or write your representations to the insurer. Those are judgements, and the reasonable, prudent person is the one they will be measured against.
It depends on the capacity in which your brokerage was acting, and it is exactly the point on which files are won and lost. As an independent intermediary you generally act for the client, so telling you is not automatically telling the insurer — but where you hold a binder or a mandate to accept the information, the position can differ. Either way, the evidence that a fact was communicated to your office is what makes the argument possible at all, which is why the thread matters more than the recollection.
That is governed by the policy wording read against section 53. The section limits the insurer's ability to invalidate the policy, exclude or limit its obligation, or increase the policyholder's obligations, and it does so only where the non-disclosure was likely to have materially affected the risk assessment. Ask the insurer to state precisely which remedy it is exercising and on what basis, and put that in the representations if the answer is thin.
The materiality test is not limited to the questions on the proposal form, so silence about something a reasonable, prudent person would regard as relevant can still bite. In practice, though, insurers rely far more easily on an incorrect answer to a question they did ask. Asking the insurer's actual questions, in the client's own words, closes most of that gap.
The Rules frame the period as not less than ninety days after the date of receipt of the notice, and the notice itself has to spell the period out. Where a client forwards a letter weeks after it landed, establish the receipt date early and record it, because the internal escalation route and the ombud time limits both depend on it.
Work to the record-keeping obligations that apply to your FSP and treat the disclosure thread as part of the client file, not as chat. A claim on a life or funeral policy can surface a decade after inception, and a policy varied at each renewal has a disclosure history rather than a single record. Our guide to FAIS record-keeping for WhatsApp covers the retention and retrieval side.
Shared WhatsApp inbox, client records, follow-ups and opportunities for the whole brokerage. 15-minute demo.
Loss of supply, a surge on restoration and a grid collapse are three different events on a South African policy. What a broker checks before answering a client.
A motor policy pays for the car. The Road Accident Fund pays for the person. The two clocks, the RAF 4 form, and the line a brokerage must not cross.
When a storm puts a month of claims into two days, a brokerage needs triage, document packs and a communication cadence. A practical plan for short-term brokers.
