AML & Financial Crime

Suspicious Activity Reporting (SAR/STR): When to File and How

The Suspicious Activity Report is the regulated firm's formal channel for reporting suspected money laundering or terrorist financing to its national Financial Intelligence Unit. This guide explains what triggers the filing obligation, how the no-tipping-off rule works, and how filing mechanics differ across major FIUs including STRO Singapore, FinCEN, the NCA, and others.

Published: May 2026 Category: AML & Financial Crime Read time: ~10 minutes
Quick Answer
A Suspicious Activity Report (SAR) — known as a Suspicious Transaction Report (STR) in Singapore and several other jurisdictions — is the formal disclosure a regulated firm makes to its national Financial Intelligence Unit when it knows, suspects, or has reasonable grounds to suspect that funds are the proceeds of crime or are connected to terrorism financing. The filing obligation is mandatory: failure to file when grounds for suspicion exist is a criminal offence in most jurisdictions. SARs are filed with the relevant FIU — STRO (Singapore), FinCEN (US), the NCA (UK), FIU-IND (India), AUSTRAC (Australia), TRACFIN (France), and equivalent bodies in every other FATF jurisdiction. The no-tipping-off rule prohibits the firm from informing the customer (or anyone outside a defined need-to-know circle) that a SAR has been or will be filed. Filing must be prompt — most jurisdictions require filing within days of forming suspicion, with separate procedures for transactions requiring an active consent decision.

SAR filing sits at the apex of the AML programme. Customer due diligence, risk rating, and transaction monitoring all exist primarily to surface activity that should be reported. A programme that does everything else well but fails at the SAR step has produced a great deal of operational documentation and contributed nothing to the financial crime intelligence picture.

Regulators have been increasingly direct about this. SAR filing rates that diverge sharply from peers, SAR quality that consistently scores poorly with the FIU, and SAR-decision documentation that does not explain the firm's reasoning are all flags supervisors specifically look for. Getting SAR filing right — both the decision to file and the substance of what is filed — is one of the highest-stakes operational disciplines in compliance.

What Triggers a Filing Obligation

The legal threshold for filing varies subtly between jurisdictions but converges on a similar concept: the firm must file when it knows, suspects, or has reasonable grounds for suspicion that funds or activity relate to money laundering, terrorism financing, or specified predicate offences.

Knowledge is the highest standard — the firm has actual knowledge of the unlawful origin or purpose of funds. Rare in practice; when present, filing is unambiguous.

Suspicion is a lower threshold and the most common in practice — the firm has more than a vague unease but less than confirmed proof. The standard test is whether the suspicion is genuine and rational, not whether it is provable.

Reasonable grounds for suspicion is lower still and is the threshold most jurisdictions actually apply. The test is objective: would a reasonable person in the firm's position, with the same information, have suspected ML/TF? If yes, the obligation arises whether or not the firm itself subjectively suspected.

Importantly, the firm is not required to be certain — it is required to report suspicion. Refusing to file because the firm cannot prove the underlying offence is a misunderstanding of the standard. The FIU's role is to investigate; the firm's role is to escalate suspicion.

The Internal SAR Process

A SAR is the output of a regulated firm's internal process for evaluating and escalating suspicion. The process must be documented, must be available to every employee with relevant knowledge, and must lead to a defined decision-maker — typically the MLRO.

1

Internal Disclosure

Any employee who forms suspicion must escalate it internally to the MLRO (or to the firm's designated disclosure officer). The escalation channel must be confidential, accessible, and explicitly protected against retaliation. Frontline staff, relationship managers, operations staff, and compliance analysts may all be the originator of an internal disclosure.

2

MLRO Review

The MLRO evaluates the disclosure against the legal threshold. The review considers the underlying activity, the customer's profile and history, any explanations the firm has obtained, and the broader context. The MLRO's analysis is documented in a structured case file — what was considered, what was concluded, what additional information was sought, and the rationale for the final decision.

3

Decision and Filing (or Not)

If the MLRO concludes the legal threshold is met, the SAR is filed with the relevant FIU. If the MLRO concludes it is not met, the case is closed with documented rationale. Either decision must be reviewable — a regulator examining the file two years later must be able to follow the reasoning. "Not filed" decisions are scrutinised as carefully as filed ones.

4

Post-Filing Actions

Filing a SAR does not automatically require exiting the relationship. The firm must consider whether to continue, restrict, or exit, balancing the suspicion against the no-tipping-off rule and any consent or no-consent indication from the FIU. In some jurisdictions and circumstances, the firm must request consent from the FIU before continuing the activity that triggered the SAR.

The No-Tipping-Off Rule

Every major AML regime prohibits the regulated firm from disclosing to the customer that a SAR has been filed, will be filed, or is under consideration. This is the no-tipping-off rule, and it is a criminal offence to breach it.

The rule is broader than "don't tell the customer." It extends to anyone outside the defined need-to-know circle within the firm and outside law-enforcement and FIU channels. Tipping off can happen through subtle cues: a relationship manager closing an account too abruptly, a customer-service representative declining to answer routine questions, a sudden change in tone of communications. Compliance training must address the practical operational behaviours that can breach the rule, not just the principle.

Where a SAR is filed but the relationship continues, special care is required. The firm must be able to communicate normally with the customer, decline transactions where required, and respond to enquiries — without giving any indication that suspicion has been formed or reported. This is one of the operationally hardest aspects of SAR handling and requires careful coordination between the MLRO, the relationship manager, and frontline staff.

Account Closure After SAR
Many firms instinctively close accounts after filing a SAR. This may itself constitute tipping off if the closure timing or rationale signals suspicion. Best practice is to make the closure decision on grounds independent of the SAR — risk appetite, business viability, customer behaviour — and to document those independent grounds. Some firms maintain accounts post-SAR specifically to avoid the tipping-off concern, on the basis that the FIU can investigate more effectively while the activity continues.

Filing Mechanics by Jurisdiction

Every FATF jurisdiction has a designated FIU, and every FIU has a defined filing portal, format, and timeline. A firm operating cross-border must understand the filing requirements of each jurisdiction it operates in.

The filing requirements at the major FIUs:

  • Singapore — STRO (Suspicious Transaction Reporting Office): STRs filed via the SONAR online portal; structured form fields; expectation of prompt filing measured in days from formation of suspicion.
  • United States — FinCEN: SARs filed via the BSA E-Filing System; deadline 30 days from initial detection (60 days if no suspect identified).
  • United Kingdom — NCA UK Financial Intelligence Unit: SARs filed via the SAR Online portal; separate Defence Against Money Laundering (DAML) regime for transactions requiring consent; the DAML decision is time-bound (notice + moratorium periods).
  • European Union: Each member state operates its own FIU (TRACFIN in France, FIU-Netherlands, etc.); filing standards align under the EU AMLD; cross-border information sharing through the FIU.NET network.
  • Australia — AUSTRAC: SMRs (Suspicious Matter Reports) filed via the AUSTRAC Online system; prompt filing required.
  • Hong Kong — JFIU: STRs filed via the JFIU's e-reporting system; immediate filing required where suspicion is formed.

Writing a SAR That Is Actually Useful

The substance of the SAR — what is actually written in the narrative — determines whether the FIU can act on it. FIUs receive enormous volumes of SARs annually; poorly-written narratives that fail to communicate the suspicion clearly result in reports that effectively disappear into the queue.

A useful SAR narrative does five things: identifies the customer and relevant accounts; describes the specific activity that triggered the suspicion (dates, amounts, counterparties, transaction types); explains why the activity is suspicious in context (compared to the customer's expected behaviour, declared business, or known typologies); documents what the firm has done in response (further investigation, customer contact, monitoring intensification); and identifies any specific assistance the FIU could provide.

FIUs publish guidance on SAR quality and most run feedback programmes for filers. Reviewing the FIU's published guidance and incorporating it into the firm's internal SAR template materially improves filing quality.

From Alert to SAR Without the Friction

One Constellation's compliance portal connects transaction monitoring alerts directly into MLRO case workflows, structured SAR drafting, and audit-ready filing records — for STRO, FinCEN, NCA, AUSTRAC, and other major FIUs.

← Transaction Monitoring CDD Guide → All Articles
Scroll to Top