How FIC Directive 10 Turns Group Footprint Data Into a Monitoring Coverage Question

Transaction Monitoring  ·  October 2026  ·  South Africa

Directive 10 is a registration rule, not a monitoring rule. Its value for risk leaders is that it forces a group to state where it operates, which is the list a monitoring map should reconcile to.

FIC Directive 10 reads like an administrative rule, and in one sense it is. Directive 10 of 2026 specifies the geographic location particulars that must accompany an accountable institution’s registration with the Financial Intelligence Centre under section 43B of the Financial Intelligence Centre Act, 2001 (FICA). It was signed by the FIC Director on 31 July 2026 and took effect on publication in the Government Gazette.

The Directive does not mention transaction monitoring. The FIC’s stated purpose is to help it and supervisory bodies understand group structures and apply risk-based supervision of group-wide compliance. That purpose is the link for a risk leader. A group that must tell the supervisor where it operates should be able to show that its monitoring covers those places.

This article sets out what the Directive requires, what the FIC has said about scope, and a reconciliation that connects the registered footprint to monitoring coverage.

FIC Directive 10 visual showing the reconciliation from registered group footprint through a list of locations and a monitoring coverage map to reconciliation and updates within 90 days

The registered footprint and the monitoring coverage map should agree, and a change to either should trigger a check of the other.

Quick answer

Directive 10 of 2026, signed by the FIC Director on 31 July 2026, requires specified accountable institutions to give the FIC the locations of their head office, branches and subsidiaries, with contact details for the compliance function at each. Institutions already registered have 90 days from commencement to update and 90 days to update after any later change. It applies to legal practitioners, certain trust and company service providers, estate agents, gambling institutions, credit providers other than banks, Postbank, high-value goods dealers, the South African Mint and crypto asset service providers.

What Directive 10 requires

An accountable institution with operations in more than one geographic location must give, when it registers, the name, licence number and registration number where applicable, the business address and the contact details of the person carrying out the compliance function under section 42A(2)(b) of FICA, for its head office, each branch, each subsidiary’s head office and each subsidiary’s branches, in South Africa and abroad. Institutions already registered when the Directive commenced must update their registration within 90 days of commencement, and must update again within 90 days after any change. Failure to comply is non-compliance that can attract an administrative sanction under FICA.

The Directive applies to the accountable institutions in items 1, 2, 3, 9, 11 (excluding banks, mutual banks and co-operative bank credit providers), 14, 20, 21 and 22 of Schedule 1 to FICA. Moonstone’s report of the final Directive maps these to legal practitioners, certain trust and company service providers, estate agents, gambling institutions, credit providers other than banks, Postbank, high-value goods dealers, the South African Mint and crypto asset service providers. The draft had covered every Schedule 1 institution, and the FIC has indicated that a further directive may follow for the financial institutions sector.

Location typeParticulars requiredCompliance contact
Head office Name, licence and registration numbers, business address Person carrying out the compliance function
Branches in and outside South Africa As for head office, for each branch Person responsible for the branch’s particulars
Subsidiary head offices As for head office, for each subsidiary Compliance contact for the subsidiary
Subsidiary branches As for head office, for each branch of each subsidiary Compliance contact for the branch

What counts as a branch

The Directive defines a branch as a physical office, not a separate legal entity or accountable institution, located away from the head office, where business is conducted for the institution and products and services are provided to clients. In its consultation feedback, as reported by Moonstone, the FIC said this means premises where Schedule 1 products and services are provided directly and in person to clients. It said the Directive does not reach data centres, ATMs, remote-working locations or virtual platforms. A business that operates mainly through a virtual platform must still give its head office, and where it uses third-party agents to engage clients, the agents’ branches must be listed.

The FIC also said the Directive does not require branches or subsidiaries to register as separate accountable institutions.

In scope

Physical premises where Schedule 1 services are provided in person.

Out of scope

Data centres, ATMs, remote-working locations and virtual platforms.

Virtual businesses

Give the head office; list third-party agents’ branches.

No separate registration

Branches and subsidiaries are not registered as separate institutions.

Why the footprint list is not the monitoring perimeter

The two lists answer different questions. The registered footprint says where the institution provides services in person. Monitoring coverage says which customers, products and channels generate alerts and who reviews them. A virtual product sold nationally may have no branch to list yet carry most of the transaction risk, and a branch may be listed that handles few transactions.

The reconciliation is therefore a check, not a rule: for each listed location and the head office, can the group show which monitoring rules, case queue and named reviewer cover its customers and products, and for each monitored product, can it show where it is delivered from?

Footprint itemMonitoring questionEvidence to hold
Head office Which team owns monitoring policy and rule changes for the group? Named owner and approval records
Each branch Which alerts arise from branch-originated activity, and who reviews them? Case queue assignment by origin
Each subsidiary Does the subsidiary run the group’s rules or its own, and who approves differences? Rule-set comparison and sign-off
Virtual channels and agents Which product and channel risks sit outside any listed branch? Channel-level coverage map

Dates and the next update

The Directive took effect on publication in Government Gazette No. 55097 of 31 July 2026, as reported by Moonstone. On a count of 90 days from 31 July 2026, the first update window runs to 29 October 2026. That date is calculated; each institution should confirm it against its own reading of the commencement date. After that, any change to the particulars must be updated within 90 days.

The FIC has said further guidance will explain how the information must be submitted, and that submissions will go through a dedicated category on its registration and reporting platform that does not affect existing reporting.

1

31 July 2026

Directive 10 signed; effective on Gazette publication.

2

29 October 2026

End of the first 90-day update window, on a calculated count.

3

After a change

Particulars updated within 90 days of the change.

4

Possible later step

FIC has indicated a further directive may follow for financial institutions.

Four checks for risk leaders

The Directive is an obligation about registration. These four checks use it to test something it does not require.

List what you registered

Keep the filed list of locations and contacts as the reference footprint.

Map monitoring to each location

Show the rules, queue and reviewer that cover each listed location and each virtual channel.

Trigger a check on change

A new branch, subsidiary or agent should prompt a monitoring coverage review as well as a registration update.

Name the contact

Make sure the compliance contact filed for each location can describe its monitoring.

How Nexiant supports group coverage mapping

FraudShield, Nexiant’s specialist transaction-monitoring brand, is built around real-time detection, configurable rule logic and case-management workflows. For group coverage mapping, the useful tests of any monitoring capability are whether alerts can be traced to the location or channel they came from, whether rule sets can be compared across subsidiaries, and whether changes to configuration are recorded. Nexiant brings these questions together across compliance, fraud and monitoring as a design discipline, not as a claim about one integrated system.


Frequently Asked Questions

Directive 10 of 2026 specifies, under section 43B of FICA, the geographic location particulars that must accompany an accountable institution’s registration with the FIC: its head office, branches, each subsidiary’s head office and the subsidiaries’ branches, in South Africa and abroad.
It applies to the accountable institutions in items 1, 2, 3, 9, 11 (excluding banks, mutual banks and co-operative bank credit providers), 14, 20, 21 and 22 of Schedule 1 to FICA. The FIC has indicated a further directive may follow for the financial institutions sector.
Institutions registered at commencement must update within 90 days of commencement, and must update again within 90 days after any change to the particulars. The Directive took effect on Gazette publication on 31 July 2026, so a count of 90 days ends on 29 October 2026.
No. The Directive concerns registration particulars. The FIC’s stated purpose is to help it and supervisory bodies understand group structures and apply risk-based supervision of group-wide compliance.
Failure to comply with any provision is non-compliance and is subject to an administrative sanction under FICA, read with sections 61A and 45C.

Check that monitoring coverage matches your footprint

Speak with a Nexiant expert about mapping monitoring coverage across branches, subsidiaries and virtual channels, or explore FraudShield’s case-management and rule-configuration capability.

Speak with an expert

This article was accurate at the time of publication in October 2026 and is intended for general informational purposes only. It does not constitute legal, regulatory or compliance advice. Organisations should seek qualified professional guidance in relation to their specific obligations.