Can a Client Waive Their Rights Under the General Code of Conduct?

A client is in a hurry. They have done their research, they know what they want, and they do not want to sit through a Needs Analysis. They offer to sign a document confirming they waive that right. The representative, wanting to be responsive, considers whether accepting a client-initiated waiver is permissible. After all, no one pressured the client. The waiver was entirely the client's idea.

Under Section 21 of the General Code of Conduct for Authorised Financial Services Providers and Representatives, this reasoning reaches the wrong answer. The representative cannot accept the waiver. The waiver itself is null and void. The Needs Analysis obligation remains intact.

The Rule

Section 21 of the General Code of Conduct for Authorised Financial Services Providers and Representatives (Board Notice 80 of 2003, Part XIII — Waiver of Rights) states:

No provider may request or induce in any manner a client to waive any right or benefit conferred on the client by or in terms of any provision of this Code, or recognise, accept or act on any such waiver by the client, and any such waiver is null and void.

This is the entirety of Part XIII of the Code — one provision, one sentence, no exceptions. The provision operates in two directions: it prohibits the provider from seeking a waiver (request, induce), and it prohibits the provider from acting on a waiver that the client produces independently (recognise, accept, act on). The phrase "any such waiver by the client" is not an exception to the prohibition — it is part of it. Any such waiver is null and void regardless of its form or how it came about.

What Section 21 Actually Prohibits

Section 21 contains a prohibition that operates in two directions simultaneously, and understanding both directions is what the RE5 examination tests.

The Provider May Not Initiate a Waiver

The first direction is intuitive. A provider may not request a client to waive any right or benefit conferred by the Code. A provider may not induce such a waiver. The word "induce" has specific significance: it covers any conduct designed to bring about a waiver, including commercial incentives. An FSP that offers a client a premium discount in exchange for signing a waiver of their right to claim damages for gross negligence has induced a waiver. Section 21 prohibits the offer as much as the outcome.

The Provider May Not Act on a Client-Initiated Waiver

The second direction is the one that examination questions exploit. Section 21 does not stop at prohibiting the provider from requesting or inducing waivers. It also prohibits the provider from "recognising, accepting, or acting on any such waiver by the client."

The phrase "by the client" is not an exception. It is part of the prohibition. If a client arrives at the office with a formal written waiver prepared by their own attorney, signed, and commissioned by a Commissioner of Oaths — the provider still cannot act on it. The initiative belonged to the client, the formality was impeccable, and the provider did nothing to encourage it. Under Section 21, none of that matters.

Any Such Waiver is Null and Void

The third element of Section 21 is the consequence: any such waiver is null and void. This means it has no legal effect. A representative who acts on a client's waiver does not acquire any protection from having done so. If the client later claims their rights under the Code, the representative cannot point to the signed waiver as a defence. The document is a legal nullity regardless of what it says, who signed it, or whether both parties agreed to it at the time.

The breadth of the provision is also significant. Section 21 covers "any right or benefit conferred on the client by or in terms of any provision of this Code." This includes the Needs Analysis obligation under Section 8(1), disclosure obligations under Section 7, the record of advice requirement under Section 9, and every other client protection in the Code. A client cannot waive any of them.

Where Representatives Go Wrong

The most persistent mistake is treating the client's spontaneous initiative as the distinguishing factor — reasoning that if the provider did not request or induce the waiver, it must be permissible to act on it.

This reading is understandable. It matches the general legal instinct that consent freely given is consent that counts, and that protections designed to prevent pressure cannot be meant to override a genuinely autonomous choice. But Section 21 is not primarily about preventing pressure. It is about maintaining minimum consumer protection standards as non-negotiable floors. The client's autonomy to choose a financial product is preserved; the client's ability to surrender the protections that attach to the transaction is not.

A useful comparison is Section 3(3) of the Code, which covers confidentiality. Under Section 3(3), a provider may not disclose confidential client information unless the client has given written consent. There, consent matters. The legislature knew how to write a consent carve-out. The fact that Section 21 contains no equivalent — that it provides no exception for client-initiated waivers — is a deliberate drafting choice, not an oversight. Where the GCOC wanted consent to release a provider from an obligation, it said so. Section 21 says nothing of the sort.

The examination exploits this gap. Wrong answer options on this topic are systematically constructed around the "client-initiated" theory: the waiver is valid "where the client independently initiated the waiver without provider inducement," or valid "provided a Commissioner of Oaths countersigned it," or binding "if the Key Individual formally ratified it in writing." Every one of these options imports a formality or condition that Section 21 does not recognise. The correct answer is always simpler: the waiver is null and void.

General Code of Conduct Waiver Scenarios

The impatient client

A client has reviewed the product independently and tells the representative they do not want a Needs Analysis or disclosure document. They offer to sign a written acknowledgment that they waive both. The representative, confident that no pressure was applied and that the client has genuine experience, agrees to proceed on the waiver's terms.

The representative has violated Section 21. The obligations under Sections 7 and 8(1) of the Code — disclosure and Needs Analysis — remain intact. The fact that the representative did not request or induce the waiver is irrelevant. Acting on it triggers the prohibition.

The premium discount

An FSP, trying to close a transaction efficiently, offers a client a 10% reduction in premium if the client signs a document waiving any right to claim damages under the FAIS General Code of Conduct. The client, satisfied with the arrangement, signs.

The FSP has induced the waiver — the premium discount is the inducement. The waiver is null and void. The client retains all rights under the Code. If the FSP is later found liable for negligent advice, it cannot rely on the signed document to limit the client's claim.

The formally executed waiver

A client approaches the FSP with a document prepared by their personal attorney. The document is signed, commissioned by a Commissioner of Oaths, and states that the client voluntarily and irrevocably waives all rights and benefits conferred by the General Code of Conduct. The FSP's compliance officer, noting the formality, confirms the client acted independently and approves acting on the waiver.

The compliance officer's approval is without legal foundation. Section 21 renders the document null and void. The formality of execution — the attorney, the signature, the Commissioner of Oaths — has no bearing on Section 21. No approval mechanism, no level of formality, and no proof of independent client initiative validates a waiver of GCOC rights.

Practical Implications

For representatives:

When a client offers to waive a GCOC obligation — the Needs Analysis, disclosures, the record of advice — the representative must decline. There is no analysis to perform and no competing consideration to weigh. The representative should note the client's preference in the file and proceed with the full obligation regardless.

For FSPs and compliance officers:

An FSP that builds commercial arrangements around client waivers — discounts for waived obligations, streamlined processes contingent on waiver signatures — has incorporated a Section 21 violation into its business model. Any waiver document in the FSP's standard contract should be reviewed against this provision.

For exam candidates:

When you see an RE5 question involving a client who offers to waive a GCOC right, the question is testing one specific point: whether the client-initiated nature of the waiver changes the answer. It does not. The answer is always: the representative cannot accept or act on the waiver, and the waiver is null and void under Section 21.

If the question adds formality — "the client had the document prepared by an attorney," "the waiver was countersigned," "the Key Individual approved it" — these details are designed to make the wrong answer more plausible. The formality is legally irrelevant.

Key Takeaways

• Section 21 of the General Code of Conduct prohibits providers from requesting, inducing, accepting, or acting on any waiver of client rights — regardless of who initiated the waiver.
• A client-initiated waiver is not permissible. Section 21 explicitly covers "any such waiver by the client."
• Any such waiver is null and void — no formal execution, no third-party approval, and no proof of client autonomy changes this outcome.
• The prohibition covers every right and benefit conferred by the Code, including the Needs Analysis (Section 8), disclosures (Section 7), and record of advice (Section 9).
• The contrast with Section 3(3) — where client consent does lift the confidentiality obligation — confirms that the absence of a consent exception in Section 21 is deliberate.