Suspicious Transaction Reports Under FICA: Is Suspicion Alone Enough to Trigger the Obligation?

A client deposits a large sum in cash and instructs a representative to invest it immediately. Asked about the source of funds, the client gives an explanation that the representative finds implausible — but cannot disprove. No unlawful activity has been confirmed. No evidence exists beyond the representative's unease and the transaction's unusual structure.

The representative hesitates. Filing a formal report with the Financial Intelligence Centre feels like a serious step — an accusation. Without proof, is there really an obligation?

Under the Financial Intelligence Centre Act 38 of 2001, the answer is unambiguous. Proof is not the standard. Suspicion is.

The Suspicious Transaction Report Obligation

Under FICA Section 29(1), the obligation to file a Suspicious Transaction Report (STR) with the Financial Intelligence Centre is triggered by suspicion alone — proof of the underlying unlawful activity is not required. A representative who "knows or ought reasonably to have known or suspected" that a transaction involves the proceeds of unlawful activities must file the report. Failure to do so — even through negligence — constitutes a criminal offence under Section 52(2).

The Legislative Framework

Section 29(1): The Suspicion Standard

Section 29(1) of FICA sets out the obligation:

"A person who carries on a business or is in charge of or manages a business or who is employed by a business and who knows or ought reasonably to have known or suspected that — (a) the business has received or is about to receive the proceeds of unlawful activities; (b) a transaction or series of transactions to which the business is a party has no apparent business or lawful purpose... must, within the prescribed period after the knowledge was acquired or the suspicion arose, report to the Centre the grounds for the knowledge or suspicion and the prescribed particulars concerning the transaction."

The trigger is the formation of a suspicion — not its confirmation. The provision does not require the representative to investigate until the suspicion can be substantiated. It requires the representative to report as soon as the suspicion arises. "Knowledge was acquired or the suspicion arose" marks the start of the prescribed period, not the conclusion of any internal enquiry.

Section 52(2): Negligent Failure Also an Offence

Section 52(2) extends the obligation beyond deliberate non-reporting:

"Any person referred to in section 29(1) or (2) who reasonably ought to have known or suspected that any of the facts referred to in section 29(1)(a), (b) or (c)... exists, and who negligently fails to report the prescribed information... to the Centre, is guilty of an offence."

This provision closes a gap that would otherwise allow a representative to avoid liability by suppressing a suspicion or simply choosing not to notice suspicious indicators. If a reasonable person in the representative's position would have formed a suspicion, the failure to report is a criminal offence — even without proof that the representative deliberately ignored the warning signs. The obligation is an affirmative duty of vigilance, not merely a requirement to act on suspicions already formed.

The 15-Day Prescribed Period

The "prescribed period" referenced in Section 29(1) is defined in Regulation 24(3) of the Money Laundering and Terrorist Financing Control Regulations: 15 days from the date the representative became aware of the facts giving rise to the obligation.

The clock starts when the suspicion arises — not when the underlying transaction completes, not when the client confirms or denies the source of funds, and not when any internal investigation concludes. A representative who defers filing pending confirmation of the source of funds may find the 15-day period has elapsed before confirmation could have been obtained.

Section 33: The Transaction May Continue

A common misconception is that filing an STR requires the representative to halt or refuse the transaction. Section 33 of FICA states the opposite:

"An accountable institution, reporting institution or person required to make a report to the Centre in terms of section 28 or 29, may continue with and carry out the transaction in respect of which the report is required to be made unless the Centre directs the accountable institution, reporting institution or person in terms of section 34 not to proceed with the transaction."

The transaction may continue after the STR is filed. Only a specific direction from the FIC under Section 34 can halt it. This design is deliberate: suspending or refusing every flagged transaction would signal to the subject that a report has been filed — a disclosure that Section 29(3) expressly prohibits.

Section 29(3): The Tipping-Off Prohibition

Once a report has been filed — or must be filed — Section 29(3) prohibits the representative from disclosing that fact to any person, including the subject of the report. It is a criminal offence to inform the client that an STR has been submitted, even in response to a direct question. The only permissible disclosures are to the FIC itself, in compliance with a court order, or to an attorney for the purpose of obtaining legal advice.

The tipping-off prohibition and the permission to continue the transaction operate together. The representative files the report and proceeds as normal — maintaining the appearance of an ordinary transaction while the FIC determines whether intervention under Section 34 is warranted.

Where Representatives Go Wrong

Waiting for confirmation. The most common error is treating the STR as an accusation rather than an investigative referral. A criminal charge requires proof beyond reasonable doubt. An STR requires only suspicion. The report is information provided to an authority that is equipped to investigate — it is not a finding of guilt and it is not a formal allegation. Representatives who wait for confirmation before filing conflate the two standards and risk allowing the 15-day period to expire.

Believing that refusal is the correct response. A representative who refuses to execute a suspicious transaction, citing the suspicion as the reason, has effectively tipped off the client without filing any report. Section 33 permits the transaction to continue after an STR is filed precisely to avoid this outcome. Refusing the transaction without filing may itself constitute a breach — the representative has acted on the suspicion without fulfilling the reporting obligation that the suspicion triggers.

Misapplying the general duty of transparency. After filing an STR, a client asks the representative directly whether a report was made. The representative — who has a general FAIS obligation to be transparent with clients — is tempted to confirm the report. Section 29(3) overrides the general transparency obligation in this specific context. The representative must decline to confirm or deny that any report has been filed.

How This Works in Practice

The implausible explanation

A client instructs an adviser to invest R450,000 in cash. When asked about the source of the funds, the client states they were accumulated from freelance work. The amounts and timing are inconsistent with the client's known income profile. The adviser cannot prove the explanation is false, and the client declines to provide documentation.

The adviser must file an STR within 15 days of forming the suspicion. The inability to disprove the explanation is irrelevant — the suspicion has arisen, the obligation has been triggered, and the prescribed period has begun. The adviser may accept the investment instruction and proceed with processing while simultaneously filing the report.

The direct question after filing

Two weeks after filing an STR, the client contacts the adviser: "My bank has flagged unusual activity on my account. Did your office report me?" The adviser has a long-standing relationship with the client and wishes to be transparent.

The adviser must not confirm or deny that any report was filed. Disclosing the existence of the STR — even to the subject of the report, even in response to a direct question — is a criminal offence under Section 29(3). The adviser should decline to comment on any regulatory reports or compliance processes.

Practical Implications

For representatives — the STR obligation requires you to form a view, not to investigate until the view is confirmed. If a transaction's features are consistent with money laundering or unlawful activity, and you cannot identify a plausible legitimate explanation, the obligation to file arises at that point. The 15-business-day period begins then. Document the date on which the suspicion arose; the deadline calculation depends on it. Once the report is filed, continue the transaction as normal unless the FIC directs otherwise.

For compliance officers — Regulation 24(3)'s exclusion of weekends and public holidays is a precision point worth embedding in compliance calendars. Where an STR obligation arises close to a public holiday period, the effective filing deadline extends — but "extends" here means more calendar days, not additional working time. Ensure representatives understand that the prescribed period measures business days from the date of awareness, and that deferring awareness is not a compliant strategy.

For exam candidates — RE5 scenario questions on STRs typically test three things: the standard of trigger (suspicion, not proof), the filing period (15 business days from awareness, not from the transaction date), and the tipping-off prohibition (no disclosure to the subject, regardless of the relationship). In any scenario where a representative knows something is unusual but lacks confirmation, the correct regulatory response is to file — not to investigate further, not to refuse the transaction, and not to alert the client.