Compliance

FICA Compliance & Your IT Systems: A Guide for SA Accounting Firms

PDSThe PDS Team·2026-06-02·8 min read
A stylised financial data motif in plum and charcoal representing accounting compliance

South Africa left the FATF grey list, but FIC inspection pressure on accounting firms went up, not down. Here’s why FICA compliance now lives in your IT systems, and what an inspection actually tests.

Most accounting firms still file FICA in the same mental drawer as their annual returns: paperwork, done once, forgotten until next year. That mental model is now the single most expensive mistake a practice can make. The Financial Intelligence Centre Act treats your firm as an Accountable Institution, which means the regulator can register you, inspect you, and fine you, and increasingly what it inspects is not a binder of forms but the systems behind them.

This isn’t the checklist. If you want the full obligation-by-obligation breakdown, our FICA compliance checklist for accounting firms covers that in detail. What follows is the part that gets skipped: why your IT systems have quietly become your FICA control, and what that means for a practice in Gqeberha, East London or Mthatha that doesn’t have an in-house compliance team.

TL;DR: Accountants are Accountable Institutions under FICA, so the FIC can inspect you. Between April 2024 and April 2025 it issued penalties from R20,000 to R7.8 million, mostly off the back of inspections (Masthead, 2025). Compliance now depends on IT: five-year record retention, secure client due-diligence storage, and goAML reporting your systems must actually support.

Are accounting firms really "accountable institutions" under FICA?

Yes, and there’s no opt-out. Accountants and accounting firms are listed Accountable Institutions, which puts a full set of anti-money-laundering duties on the practice: a Risk Management and Compliance Programme (RMCP), client due diligence, transaction monitoring, and reporting to the FIC. The regulator confirmed the scale of the regime in its 2024/25 reporting year: 55,262 registered institutions submitted more than 13.5 million regulatory reports, and the FIC conducted 556 inspections into medium-to-high-risk institutions (Baker McKenzie, 2025).

Two 2025 deadlines made this concrete. The FIC required accountable institutions to submit their RMCPs by 12 March 2025, with non-submission itself an act of non-compliance. And Guidance Note 7A took effect on 13 February 2025, tightening what an RMCP must actually contain (MIE, 2025). The era of "we have a policy document somewhere" is closing.

Here’s the part that catches firms out: more than half of the administrative sanctions the FIC published in the past year were simply for not submitting the Risk and Compliance Return, with legal practitioners and estate agents making up most of those cases (Masthead, 2025). Accounting firms sit in exactly the same category of risk. Most penalties don’t follow a dramatic money-laundering scandal: they follow an administrative miss that a half-decent system would have flagged.

What does getting FICA wrong actually cost a firm?

The statutory ceiling is steep: administrative penalties reach R10 million for a natural person and R50 million for a legal person, alongside criminal exposure (FIC). But the real-world numbers tell the more useful story. Between April 2024 and April 2025 the FIC handed down penalties ranging from R20,000 to R7.8 million, the bulk of them off the back of inspection findings (Masthead, 2025).

The shift in enforcement appetite is best captured by one number. In August 2024 Sasfin Bank was hit with a penalty of R209 million, on its own roughly equal to the total of all such penalties over the previous six years combined (Baker McKenzie, 2025). Smaller firms won’t see nine-figure fines, but the message behind them is aimed at everyone: the FIC is willing to act, and willing to publish.

For an accounting practice the financial penalty is rarely the worst of it. FICA non-compliance also exposes you to SAICA and IRBA disciplinary action, which can reach the right to practise, and the FIC publishes non-compliance, so reputation is on the table too. In a profession built on trust with the kind of clients who notice these things, that’s the cost that lingers.

How long must accounting firms keep FICA records, and where?

FICA requires records to be kept for at least five years: from the date a business relationship ends, from the date a single once-off transaction concludes, or from the date a regulatory report is submitted to the FIC. That sounds simple until you ask the practical question: where are those records, and can you actually produce them in a usable form five years later?

This is where the obligation quietly becomes an IT problem. Five-year retention isn’t a sticky note; it’s a document-management policy that has to enforce itself, prevent premature deletion, and survive a laptop dying, a staff member leaving, or a ransomware incident. It means backups that are tested, not just scheduled. It means an audit trail showing who accessed a client’s due-diligence file and when. None of that lives in a filing cabinet: it lives in systems someone has to set up and maintain.

The firms that fail an inspection here usually aren’t negligent. They simply trusted that "the files are on the server" was the same as compliant retention. It isn’t. A server with no enforced retention policy, no tested restore, and no access log is a five-year obligation held together by hope.

What IT systems do client due diligence and goAML reporting actually need?

FICA is technology-neutral: it doesn’t name a product. But its obligations are only satisfiable with the right plumbing. Client due diligence needs a secure onboarding system that captures and stores identity documents, screens for Politically Exposed Persons and sanctions, and establishes beneficial ownership for entity clients. Those records then need encrypted, access-controlled storage tied to the client file, with retention enforced automatically.

Suspicious and cash transaction reporting adds another system requirement. Reports go to the FIC through its goAML platform, and your staff have to be able to spot a suspicious pattern, document it internally without alerting the client (the "tipping off" prohibition is strict), and file the report promptly. Cash transactions above R24,999.99 trigger mandatory reporting on their own. A practice that handles this through ad-hoc emails and a shared spreadsheet is one staff change away from a gap.

This is the work we build into FICA-compliant IT for finance and accounting practices: onboarding and record-keeping that enforces retention, access controls and logs that stand up to an inspection, and reporting workflows that don’t fall apart when the person who "knew how it worked" goes on leave.

Why your RMCP is only as strong as the systems that enforce it

An RMCP is a document that describes how your firm manages money-laundering risk. The uncomfortable truth is that the FIC doesn’t inspect intentions: it inspects evidence. When an inspector asks to see five years of due-diligence records, an access log, or proof that a suspicious transaction was reported, a beautifully written RMCP that your systems don’t actually enforce is worse than useless. It documents, in your own words, the gap between what you said you’d do and what your IT lets you do.

That’s the connection most firms miss: the RMCP and the IT system are the same control, viewed from two angles. The policy is the promise; the systems are whether you can keep it. This is also why the cheapest, most reactive IT setup is a false economy for a regulated firm: a break-fix arrangement where someone only shows up when something breaks has no one accountable for retention policy, access logs or backup testing between emergencies. We’ve written separately on why a break-fix IT model fails a FICA inspection; for an Accountable Institution, the difference isn’t convenience, it’s compliance.

It’s the same systems question that data-protection law puts to your legal-sector neighbours. If you also act for, or alongside, law firms, our pillar on POPIA for Eastern Cape law firms walks through the equivalent problem from the privacy side: different Act, identical lesson about systems.

A practical first step for Eastern Cape accounting firms

South Africa was removed from the FATF grey list on 24 October 2025, after clearing all 22 of its action items (SAICA, 2025). It would be a mistake to read that as the pressure coming off. The delisting happened because enforcement intensified, and the FIC has signalled it intends to keep supervision tight: the grey-list exit raised the floor, it didn’t remove it.

The sensible first move isn’t a six-month overhaul. It’s a focused gap assessment: can you produce five years of due-diligence records on demand, do your access logs exist and survive, and is your goAML reporting workflow real or improvised? Most Eastern Cape practices don’t have an in-house IT team, and FICA never assumed they would: what it assumes is that someone is accountable for the systems. That’s the model we built Pandora Data Services around: a named analyst who knows your practice across Gqeberha and the wider Eastern Cape, not a ticket queue.

Frequently asked questions

Are accountants accountable institutions under FICA?

Yes. Accountants and accounting firms are listed Accountable Institutions under FICA, which means they must maintain an RMCP, perform client due diligence, report suspicious and cash transactions to the FIC, and retain records, all enforceable by inspection and penalty (FIC).

How long must accounting firms keep FICA records?

At least five years, measured from the end of the business relationship, the conclusion of a once-off transaction, or the submission of a regulatory report. Records must be reproducible in a usable form, which in practice means your document-management and backup systems have to enforce the retention period and protect against premature deletion.

Does FICA require specific IT systems?

FICA is technology-neutral, so it doesn’t mandate a particular product. But its obligations (secure due-diligence storage, audit logs, automatic retention, and goAML reporting) can only be met with systems built for them. A firm relying on shared drives and email will usually have gaps an inspection finds.

What actually happens in a FIC inspection?

The FIC reviews evidence that you’re meeting your obligations: your RMCP, due-diligence records, access logs, and reporting history. It carried out 556 inspections into medium-to-high-risk institutions in 2024/25, and the penalties that followed ranged from R20,000 to R7.8 million (Masthead, 2025).

The bottom line for accounting practices

FICA stopped being a once-a-year form and became a question about your systems. The regulator is active, the penalties are real, and the things it inspects (retention, due-diligence storage, reporting, access control) are all things your IT either does or doesn’t. For an Eastern Cape practice without a compliance department, the gap is rarely budget; it’s having someone accountable who knows your setup well enough to close it.

If you’d like a clear read on where your firm actually stands against FICA, book a FICA IT assessment or message us on WhatsApp. You’ll speak to the analyst who’d handle your account, not a script. This article is a guide, not legal advice; for a formal interpretation, consult a FICA compliance specialist.

Let’s talk about your IT needs.

Connect with a principal architect to discuss your firm’s technology, security, and compliance — in the context of the Eastern Cape’s regulatory landscape.

No obligation. A response from a principal analyst, usually within one business day.