Apexnode TechEnterprise Wealth Tech
Compliance

AML Compliance Software in South Africa: FICA, goAML Filing, Costs and Timelines

South Africa's FICA regime tells you what to report and to whom. It doesn't tell you which software to buy. This guide maps the RMCP and goAML filing to specific components, with indicative USD costs and a phased timeline.

By the Apexnode Tech editorial team · November 2026 · 10 min read

The FICA buying decision: what the software actually has to do

If you're an accountable institution under South Africa's Financial Intelligence Centre Act 38 of 2001 (FICA), you can't realistically avoid buying AML compliance software. Past a few hundred customers, manual compliance is close to unworkable. What you do decide is which components to buy, in what order, and how much to build around your core systems. Buying AML compliance software in South Africa goes wrong when an institution picks a global platform built for another regime and then finds it can't produce the reports or audit trail local supervisors expect.

Since the 2017 amendments, FICA has been risk-based. There's no fixed checklist. You document your own assessment of money laundering, terrorist financing and proliferation financing risk in a Risk Management and Compliance Programme (RMCP), then apply controls that match it. The 2022 general laws amendments went further: they brought crypto asset service providers into scope, tightened beneficial ownership requirements and widened the politically exposed person categories. South Africa has since exited the FATF grey list, but supervisors still press on effectiveness, and administrative penalties for a legal person can run to tens of millions of rand.

Advertisement

This guide is for banks, insurers, lenders, payment providers and fintechs, whether they operate locally or are entering South Africa from abroad. It covers general obligations, not legal advice. Have a South African compliance attorney or FICA specialist confirm how each requirement applies to your licence type.

Mapping FICA obligations to software components

Most FICA duties map to one of six components. One platform may supply several, but evaluate each separately. A vendor that's strong on screening is often weak on case management, and the reverse is common too.

FICA obligationSoftware componentWhat to check
Customer due diligence, including beneficial ownershipKYC/onboarding and identity verificationHome Affairs ID verification through an approved provider, CIPC company data, ownership-chain capture for companies and trusts
Domestic and foreign prominent influential persons, plus family members and close associatesPEP screeningWhether the vendor's data covers South African domestic categories, not just foreign PEPs
Targeted financial sanctionsSanctions screeningFIC's TFS list and UN Security Council lists updated daily, plus rescreening of the whole book when lists change
Ongoing due diligence and suspicious reportingTransaction monitoringRand-denominated rules, local typologies, scenario tuning
Cash threshold, terrorist property and, for some institutions, cross-border transfer reportsRegulatory reporting to goAMLFIC XML schema support, validation before submission
Record keeping, generally five yearsCase management and audit storeImmutable logs, retrieval by customer and by transaction

Whatever you buy must also handle data under the Protection of Personal Information Act (POPIA). Banks and insurers face Prudential Authority expectations on cloud use and offshoring too. If the vendor hosts in the EU or the US, you need a defensible basis for the cross-border transfer under POPIA's transfer provisions, and sometimes a notification to your supervisor. Get the vendor's position in writing before the commercial stage.

Build the RMCP first, then configure the system to it

The RMCP is the first document your supervisor reads. That's usually the Prudential Authority for banks and insurers, or the FSCA for many investment and crypto businesses. It must be approved by your board or senior management, and it must explain how you identify, assess, monitor and mitigate risk across customers, products, channels and geographies. Supervisors then test whether your systems do what the RMCP says.

So write the RMCP before you configure anything. A common failure runs the other way: the institution buys a monitoring tool, accepts the vendor's default scenarios and writes the RMCP afterward to describe whatever the tool happens to do. That gap is easy to see in an inspection. The RMCP should drive these settings:

  • Customer risk rating model: the factors and weights, which you should be able to change without paying for vendor professional services.
  • Due diligence tiers: simplified, standard and enhanced, each with its own document and verification rules.
  • Refresh cycles: for example, high-risk customers reviewed annually and low-risk customers every three to five years, with the system triggering the reviews.
  • Escalation and sign-off: which roles can approve high-risk relationships and prominent influential person onboarding, which need senior management approval.

When you shortlist, ask each vendor to run your draft RMCP's risk model in their product during the demo. A vendor that can't do it within a two-week proof of concept will probably struggle in production too.

goAML reporting: web forms versus XML integration

The FIC receives reports through goAML, the UNODC-developed platform used by many financial intelligence units around the world. Accountable institutions must register on goAML whether or not they expect to file. The main report types are suspicious and unusual transaction reports (STRs) and suspicious activity reports (SARs). There are also cash threshold reports (CTRs) for cash at or above the prescribed threshold, currently R50,000 (confirm the current figure with the FIC), terrorist property reports, and cross-border transfer reporting for certain institutions. STRs are currently due as soon as possible and no later than 15 business days after you become aware of the suspicion. CTR deadlines are much shorter.

There are two ways to file. Web-form entry is manual and fine for low volumes. XML batch upload means your system generates files in the FIC's goAML schema. As a rule of thumb, once you're filing more than roughly 30–50 reports a month, or any CTRs from a branch or agent network, manual entry starts producing errors and missed deadlines. You need XML.

What to demand from goAML reporting features

  • Support for the FIC's current schema version, plus a committed timeline for adopting updates.
  • Validation before upload, so rejected submissions are caught internally.
  • Automatic CTR aggregation across linked accounts and multiple transactions in a period, which supervisors check closely.
  • Storage of the FIC acknowledgement reference against the case record.

Many global vendors claim "goAML support" because the platform is used in many countries. But each FIU customizes its schema. Ask for a reference client already filing to the South African FIC.

Transaction monitoring in South Africa: rules, typologies and tuning

Transaction monitoring takes most of the budget and causes most of the regret. A tool that floods analysts with false positives is a liability: investigation backlogs show up in inspections and STR deadlines slip.

Monitoring for South Africa needs rules that reflect local typologies, not just generic scenarios. Typical ones include cash structuring just under the CTR threshold, rapid movement through mule accounts linked to fraud syndicates, cross-border flows to higher-risk regional corridors, wildlife trafficking and illicit mining proceeds, and misuse of trusts and shell companies. FIC guidance and its published typology reports are the right starting point for scenario design.

Rules-based or machine learning? For most institutions with fewer than about 500,000 customers, a well-tuned rules engine with risk-based thresholds is the better first deployment. It's easier to explain to an inspector, cheaper to validate and faster to go live. Add machine-learning alert scoring once you have 12–18 months of labelled alert outcomes. Vendors such as NICE Actimize, Oracle, SAS and FICO serve larger banks. ComplyAdvantage, Napier, Hawk and Feedzai are common picks for fintechs and mid-sized lenders. All sell internationally, but their local implementation partner support varies, so ask.

Plan for monthly threshold tuning in year one, and keep documented below-the-line testing as evidence for the supervisor.

Indicative costs for FICA compliance software

The ranges below are typical 2026 market figures in USD. They vary widely by contract, transaction volume, hosting model and exchange rate, and local resellers often price in rand. Confirm every figure with vendors.

ProfileScreening and KYCTransaction monitoring and goAML reportingImplementation (one-off)
Fintech or payment provider, under 100k customers$15k–$60k per year, often priced per check ($0.20–$1.50 per ID verification)$30k–$100k per year (SaaS)$20k–$80k
Mid-sized lender or insurer, 100k–1m customers$50k–$150k per year$100k–$350k per year$100k–$400k
Bank, over 1m customers$150k–$500k+ per year$400k–$1.5m+ per year, or a perpetual licence plus roughly 15–22% annual maintenance$500k–$3m+

Buyers most often underestimate these cost drivers:

  • Data integration: pulling clean transaction data from core banking, card and agent systems often costs more than the software.
  • List and data fees: premium PEP and adverse-media data from providers such as LSEG World-Check, Dow Jones or LexisNexis is often billed separately.
  • Analyst headcount: say a lender generates 2,000 alerts a month at 20 minutes each. That's roughly four full-time analysts. Cutting false positives by 30% is worth more than a 30% licence discount. (Hypothetical example.)
  • Local hosting: major hyperscalers operate South African cloud regions, but not every SaaS vendor deploys in them.

A realistic phased timeline

Vendors will quote three months. Plan for 9–15 months to reach full production at a mid-sized institution. Banks replacing legacy monitoring should allow 18–24 months.

PhaseTypical durationOutputs
1. Risk assessment and RMCP update6–10 weeksApproved RMCP, risk-rating model, requirements document
2. Vendor selection and proof of concept8–12 weeksTested risk model, POPIA and offshoring review, contract
3. Screening and KYC go-live8–12 weeksSanctions and PEP screening on new and existing customers, book rescreen
4. goAML reporting automation6–10 weeks (can run alongside phase 3)XML CTR and STR generation, validated test submissions
5. Transaction monitoring go-live12–20 weeksScenarios, thresholds, parallel run against the legacy process
6. Tuning and independent review3–6 months after go-liveTuning evidence, model validation, internal audit sign-off

Put sanctions screening first. Targeted financial sanctions obligations apply immediately and don't depend on a risk-based threshold, and screening is the fastest control to deploy.

Red flags and a decision rule for shortlisting

Drop a vendor, or push back hard, if you see any of these:

  • No reference client filing to the South African FIC through goAML XML.
  • PEP data that doesn't distinguish South African domestic prominent influential persons.
  • A risk-rating model that can't be changed without a change request and professional-services fees.
  • No clear answer on where data is stored and processed, or a refusal to accept POPIA-aligned contract terms.
  • Sanctions lists updated weekly rather than daily, or no way to trigger a rescreen of the full customer book.
  • Alert audit trails that analysts can edit after the fact.

The decision rule: shortlist no more than three vendors. Run a two-week proof of concept on six months of your own anonymized transaction data, configured to your draft RMCP. Choose the vendor with the lowest false-positive rate at an equal detection rate that can also file a validated goAML test submission. Licence price is the tiebreaker, not the starting point. Before you sign, have your compliance officer and an external FICA specialist review the configuration against the RMCP.

Questions buyers ask

Does a small fintech need dedicated AML compliance software to comply with FICA?

FICA doesn't name software, but it does require consistent customer due diligence, sanctions screening, ongoing monitoring and timely reporting. Doing that manually stops being realistic past a few hundred active customers. Most small fintechs start with SaaS screening and KYC tools and add monitoring as volumes grow.

Can we use a global AML platform we already run in other countries?

Often yes, but it needs South African configuration: a risk model matching your local RMCP, domestic PEP categories, the FIC's TFS list, CTR aggregation in rand, and goAML XML in the FIC's schema. Check POPIA cross-border transfer requirements and Prudential Authority offshoring expectations before you route South African data to another region.

How long do we have to file a suspicious transaction report on goAML?

STRs and SARs are currently due as soon as possible and no later than 15 business days after you become aware of the suspicion, unless the FIC approves otherwise. Cash threshold and terrorist property reports have much shorter deadlines. Confirm current deadlines and thresholds in FIC guidance.

What does the RMCP have to include, and does the software generate it?

The RMCP must document how you identify, assess, monitor, mitigate and manage money laundering, terrorist financing and proliferation financing risk, and your board or senior management must approve it. Software doesn't write it. The system should put its rules into practice and produce evidence that they work. Have a FICA specialist review the document.

Should we choose SaaS or on-premise for transaction monitoring in South Africa?

SaaS is usually faster and cheaper for fintechs, lenders and mid-sized insurers, provided the vendor can host locally or satisfies your offshoring and POPIA requirements. Large banks with complex core systems and strict data residency policies often still choose on-premise or private-cloud deployments. Decide on data location and integration effort, not licence price alone.

Written by the Apexnode Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.