Complaints Management Rules for Financial Services Providers in South Africa

For Financial Services Providers, complaints management is not merely an administrative function. It is a core regulatory obligation and an important part of treating customers fairly. A poorly handled complaint can lead to regulatory scrutiny, reputational harm, Ombud exposure and evidence of broader governance weaknesses within the business.

In South Africa, complaints handling by FSPs is governed primarily by the FAIS framework and related conduct standards. Firms are expected to have proper complaints systems, fair procedures and clear internal accountability. For fintech businesses, brokerages, advisers and other regulated intermediaries, complaints management should be built into the compliance framework from the start.

Why complaints management matters

A complaint is often the first warning sign that something in the business is not working properly. It may reveal disclosure failures, unsuitable advice, representative misconduct, operational errors or poor record-keeping. Regulators therefore treat complaints data as a useful indicator of conduct risk.

A proper complaints management system helps an FSP to:

• resolve disputes fairly and promptly

• identify recurring operational or compliance failures

• reduce Ombud referrals and litigation risk

• protect client relationships

• demonstrate sound governance to the regulator

In practice, an FSP that mishandles complaints may create more legal exposure through the response than through the original issue.

What counts as a complaint?

Not every customer query is a regulatory complaint. In the FAIS environment, the focus is usually on complaints alleging that the FSP or its representatives caused a client loss, inconvenience or prejudice through the rendering of a financial service or a failure to render it properly.

This may include complaints relating to:

• unsuitable advice

• misrepresentation

• disclosure failures

• delays in processing instructions

• administrative errors

• unauthorised transactions

• policy or product misunderstandings

• representative conduct

• poor service connected to a financial product or service

FSPs should define complaints carefully in their internal policy so that staff know which matters trigger the formal complaints process.

The need for a complaints management framework

Every FSP should have a documented complaints management framework that is appropriate to the size and complexity of its business. This is not something that should sit on a shelf unused. It should be implemented in practice and understood by staff, representatives and management.

A proper framework usually covers:

• how complaints are received and recorded

• who is responsible for handling them

• escalation procedures

• timeframes for acknowledgement and response

• investigation steps

• decision-making authority

• communication with the complainant

• record-keeping

• root cause analysis

• reporting to management and compliance

The framework should also distinguish between ordinary service complaints, serious conduct issues and matters that may require legal or compliance escalation.

Accessibility and fairness

An FSP’s complaints process should be easy for clients to access and use. If the process is hidden, overly technical or difficult to navigate, that can undermine fairness and create regulatory risk.

Clients should be told clearly:

• how to lodge a complaint

• what information should be provided

• where the complaint must be sent

• what the internal process is

• how long the matter is likely to take

• what further remedies are available if the complaint is not resolved

The process should not impose unreasonable barriers. Complaints should be handled objectively and with proper regard to the client’s rights, not simply treated as a defensive exercise.

Timely acknowledgement and response

One of the most important rules in complaints management is that complaints must be dealt with promptly. Delays frustrate customers and often make regulatory outcomes worse.

When a complaint is received, the FSP should:

• acknowledge receipt promptly

• assess whether it falls within the formal complaints framework

• investigate the relevant facts

• gather documents and input from the relevant representative or business unit

• provide a substantive response within a reasonable period

• explain the outcome clearly

If more time is needed, the complainant should be updated rather than left without communication. Silence is one of the quickest ways to escalate a complaint into an Ombud matter.

Proper investigation of complaints

An FSP should investigate complaints properly before reaching a conclusion. A superficial response based only on the first version of events is risky, especially where advice, disclosure or representative conduct is in issue.

A proper investigation may require consideration of:

• mandates and application forms

• records of advice

• call recordings

• emails and messages

• product disclosures

• transaction records

• policy wording or investment documentation

• internal notes

• the representative’s account of events

Where the complaint suggests misconduct, the FSP should also consider whether the matter raises broader regulatory, disciplinary or debarment issues.

Communication with complainants

Responses to complainants should be clear, professional and reasoned. A complaint outcome letter should generally explain:

• the issue raised

• the facts considered

• the FSP’s findings

• whether the complaint is upheld, rejected or partially upheld

• any remedial steps or redress offered

• any further rights available to the complainant

Poorly drafted responses can create unnecessary legal risk. An aggressive or dismissive tone often drives complainants to escalate the matter further. Equally, admissions should be considered carefully and, where necessary, with legal input.

Record-keeping and complaint registers

A formal complaint should always be recorded properly. FSPs should maintain a complaints register that allows the business to identify patterns and monitor outcomes.

The register should usually capture matters such as:

• the date the complaint was received

• the complainant’s details

• the product or service involved

• the representative or business unit concerned

• the nature of the complaint

• steps taken to investigate

• the outcome

• the date of resolution

• whether the complaint was escalated externally

Good record-keeping is essential. If an Ombud complaint or FSCA query later arises, the FSP must be able to show how the matter was handled and why.

Complaints data as a governance tool

Complaints should not only be resolved individually. They should also be analysed collectively. Repeated complaints about the same product, representative or process may indicate a systemic issue that requires intervention.

For that reason, complaints reporting should be escalated to appropriate governance structures within the FSP. Management should review trends such as:

• repeat complaint categories

• complaints against particular representatives

• delays in resolution

• product-specific risks

• complaints resulting in compensation

• matters referred to the Ombud

• complaints revealing training gaps or disclosure failures

This kind of analysis can help an FSP identify problems early before they develop into enforcement issues.

Representatives and complaints risk

Many complaints arise from the conduct of representatives. This makes oversight particularly important. An FSP cannot assume that complaints against representatives are isolated HR issues. They may reveal failures in supervision, onboarding, disclosure controls or product governance.

Where a complaint reveals possible misconduct, the FSP may need to consider:

• enhanced supervision

• retraining

• disciplinary steps

• client remediation

• reporting implications

• debarment issues in serious cases

The response should be proportionate but structured. Complaints handling and representative oversight should work together.

Complaints and Ombud exposure

If a complaint is not resolved internally, it may be referred to the relevant Ombud process. That creates additional legal and reputational exposure for the FSP.

An FSP’s internal complaint file often becomes highly important once a matter reaches external dispute resolution. Weak internal records, contradictory explanations or poor client communication can damage the FSP’s position later.

This is why complaints should be managed as if they may eventually be scrutinised by an external decision-maker.

Common mistakes FSPs make

Many FSPs create avoidable risk in the way they handle complaints. Common mistakes include:

• having a policy that staff do not actually follow

• failing to distinguish complaints from ordinary queries

• not acknowledging complaints promptly

• allowing representatives to respond informally without oversight

• keeping poor records

• using defensive or unclear response letters

• failing to escalate serious matters to compliance or legal teams

• not analysing complaint trends

• treating repeated complaints as isolated incidents

These issues are particularly common in fast-growing financial services and fintech businesses.

Complaints management in fintech businesses

Fintech platforms often assume that complaints rules apply mainly to traditional advisers and brokerages. That is a mistake. If a fintech business is acting within the FAIS environment or providing regulated financial services, it also needs a proper complaints framework.

This is especially important where the business uses:

• digital onboarding journeys

• automated product recommendations

• app-based support channels

• outsourced call centres

• embedded finance products

• online distribution models

In these businesses, complaints may arise quickly and at scale. The internal framework must therefore be operational, not merely theoretical.

How legal advisors can help

Complaints management is both a compliance and risk-management function. Legal advisors can assist FSPs by:

• drafting or reviewing complaints policies

• aligning the framework with the FAIS regulatory model

• advising on difficult or high-risk complaints

• improving complaint response letters

• assessing representative misconduct implications

• supporting Ombud-facing strategy

• identifying wider governance or conduct issues exposed by complaints trends

This is particularly valuable for businesses preparing for FSCA scrutiny, licensing applications or growth into new product lines.

Conclusion

Complaints management is a critical part of regulatory compliance for Financial Services Providers in South Africa. A sound complaints framework helps FSPs resolve customer concerns fairly, identify systemic problems and reduce legal and regulatory risk.

For FSPs, the issue is not simply whether complaints are received. The real question is whether the business has the systems, oversight and judgment to deal with them properly.

Barter McKellar advises FSPs, fintech platforms and regulated intermediaries on FAIS compliance, complaints management, representative risk and broader regulatory governance in South Africa.