Anti-money laundering tipping-off rules forbid anyone at a financial institution from telling the subject of a suspicious activity report, directly or indirectly, that a report was filed or is being considered. The prohibition sits at 31 U.S.C. § 5318(g)(2), and it is paired with a civil immunity at § 5318(g)(3) that protects the institution and its people from being sued for filing. Willful violations can bring a $250,000 fine and up to five years in prison; the safe harbor, by contrast, is broad and does not depend on whether a crime is ever proven.
What the Prohibition Covers
When a financial institution reports a suspicious transaction to a government agency, no one at that institution may notify the person involved that a report was made, or reveal any information that would expose the report’s existence.1Office of the Law Revision Counsel. 31 USC 5318 – Compliance, Exemptions, and Summons Authority The ban reaches further than handing over a copy of the SAR. Hints, verbal warnings, coded language, and anything else that would signal the filing to the subject are all covered. A compliance officer who tells a customer “we had to send something to the government about your account” has violated the statute as clearly as one who emails the report itself.
Current and former directors, officers, employees, agents, and contractors of the reporting institution are all bound. Leaving the job does not end the obligation. Government employees who learn about a SAR face a parallel prohibition against disclosing it to anyone involved in the transaction, except as needed to carry out their official duties.1Office of the Law Revision Counsel. 31 USC 5318 – Compliance, Exemptions, and Summons Authority
The list of institutions subject to the rule is wide. Banks, credit unions, money services businesses, casinos, securities broker-dealers, mutual funds, futures commission merchants, and certain insurance companies all operate under this regime. If an entity has a SAR obligation under the Bank Secrecy Act, the tipping-off prohibition travels with it.
The Employment Reference Exception
One narrow carve-out exists. A financial institution may include information from a SAR in a written employment reference provided to another financial institution under Section 18(w) of the Federal Deposit Insurance Act, or in a termination notice filed with the SEC or CFTC under self-regulatory organization rules. Even then, the reference cannot state that the information came from a SAR or that any report was filed.1Office of the Law Revision Counsel. 31 USC 5318 – Compliance, Exemptions, and Summons Authority This lets institutions warn each other about problem employees without exposing an underlying investigation.
Internal Sharing That Is Allowed
Confidentiality does not mean a SAR has to stay inside one department. FinCEN guidance permits a depository institution that filed a SAR to share the report, or information revealing its existence, with its head office or controlling company for enterprise-wide risk management and compliance oversight.2Financial Crimes Enforcement Network. Sharing Suspicious Activity Reports by Depository Institutions with Certain U.S. Affiliates A depository institution may also share a SAR with a domestic affiliate, provided that affiliate is itself subject to a SAR regulation.
The limits are firm. An affiliate that receives a SAR cannot pass it along to its own affiliates, even if those entities also have SAR obligations. Foreign branches of U.S. banks are treated as foreign banks under the BSA and are excluded from this sharing framework.2Financial Crimes Enforcement Network. Sharing Suspicious Activity Reports by Depository Institutions with Certain U.S. Affiliates And one restriction cuts across every form of internal sharing: no one may share a SAR further if there is any reason to believe it could reach a person involved in the suspicious activity. Institutions sharing SAR information with affiliates must also maintain internal controls, policies, and procedures to ensure that affiliates keep the information confidential.
Information Sharing Between Institutions Under 314(b)
Section 314(b) of the USA PATRIOT Act created a separate, voluntary channel for financial institutions to share information with each other about suspected money laundering or terrorist financing. Institutions that register with FinCEN’s Secure Information Sharing System gain safe harbor protection for the information they exchange.3Financial Crimes Enforcement Network. Section 314(b) Fact Sheet
The threshold for sharing is low. An institution does not need conclusive proof of a crime or evidence tying activity to a particular unlawful act. A reasonable basis to believe the information relates to possible money laundering or terrorist activity is enough. There are no restrictions on the medium, either. IP addresses, video surveillance footage, and verbal communications all qualify.3Financial Crimes Enforcement Network. Section 314(b) Fact Sheet
Before sharing, an institution must confirm that the other party is also a registered 314(b) participant by checking the real-time participant list through FinCEN’s system. Registrations are processed within two business days. Shared information may only be used to identify and report suspicious activity, to decide whether to maintain an account or complete a transaction, and to meet AML compliance obligations.
One rule ties 314(b) back to the tipping-off prohibition. Institutions sharing information under this program still cannot share the SAR itself or anything that would reveal a SAR exists. They can share the underlying facts and suspicions that might lead to a SAR, but the report stays confidential.3Financial Crimes Enforcement Network. Section 314(b) Fact Sheet The one exception is that institutions considering or filing a joint SAR may discuss that specific report among themselves.
Penalties for Tipping Off
Consequences split into civil and criminal tracks, driven mostly by whether the violation was willful.
Civil Penalties
Under 31 U.S.C. § 5321, a willful violation of the BSA or its regulations exposes the institution, and any partner, director, officer, or employee responsible, to a civil penalty of up to the greater of the transaction amount involved (capped at $100,000) or $25,000 per violation.4Office of the Law Revision Counsel. 31 USC 5321 – Civil Penalties These are base statutory amounts. FinCEN applies an annual inflation adjustment under the Federal Civil Penalties Inflation Adjustment Act, which pushes effective maximums somewhat higher. For 2026, the Office of Management and Budget canceled the annual adjustment because the government shutdown prevented the Bureau of Labor Statistics from producing the October 2025 CPI-U data needed for the calculation, so 2025 penalty levels remain in effect.
Negligent violations draw far less. The cap is $500 per violation, or up to $50,000 for a pattern of negligent conduct.4Office of the Law Revision Counsel. 31 USC 5321 – Civil Penalties The gap is substantial. A compliance officer who inadvertently mentions a filing in a meeting that reaches the wrong person faces a very different exposure than one who deliberately warns a customer.
Criminal Penalties
A willful violation carries a fine of up to $250,000, imprisonment for up to five years, or both. If the tipping-off occurs alongside another federal law violation, or is part of a pattern of illegal activity involving more than $100,000 in a 12-month period, the maximum fine doubles to $500,000 and the maximum sentence doubles to 10 years.5Office of the Law Revision Counsel. 31 USC 5322 – Criminal Penalties In practice, the enhanced penalties frequently apply, because a person who tips off a target is often tied to the underlying scheme.
The Safe Harbor for Filers
The counterpart to the tipping-off prohibition is a sweeping civil immunity. Under 31 U.S.C. § 5318(g)(3)(A), a financial institution that discloses a possible legal violation to a government agency, voluntarily or as required by regulation, cannot be held liable to any person under federal or state law, or under any contract or arbitration agreement, for making the disclosure or for failing to notify the subject.1Office of the Law Revision Counsel. 31 USC 5318 – Compliance, Exemptions, and Summons Authority The protection covers the institution and every director, officer, employee, and agent involved in the reporting decision.
The practical effect is significant. Without the safe harbor, a bank that flagged a high-net-worth customer’s transactions could face defamation claims, breach-of-contract suits, or tortious interference actions. The statute removes that entire category of risk. Congress wanted institutions to err on the side of reporting rather than stay silent out of litigation fear.
No Good-Faith Requirement in the Text
The text of § 5318(g)(3)(A) does not condition immunity on the reporter’s good faith or subjective intent.6Office of the Law Revision Counsel. 31 US Code 5318 – Compliance, Exemptions, and Summons Authority Immunity attaches to the act of disclosure. That is a broader shield than safe harbors in some other regulatory contexts, which explicitly require good faith. A report filed purely as personal harassment or competitive sabotage, with no connection to suspected financial crime, would arguably fall outside the statute, which protects a “disclosure of any possible violation of law.” Within the ordinary SAR process, though, the immunity holds whether or not a subsequent investigation finds wrongdoing.
Voluntary and Mandatory Reports Both Qualify
The safe harbor applies to both mandatory SAR filings and voluntary disclosures. A bank that spots something odd and files even where no specific regulation required it receives the same protection as one meeting a mandatory obligation. If a later investigation reveals no crime, the institution and its employees remain shielded from civil claims arising from the disclosure.1Office of the Law Revision Counsel. 31 USC 5318 – Compliance, Exemptions, and Summons Authority
SAR Confidentiality in Litigation
SARs carry legal protection that goes beyond ordinary confidential business records. Under 31 CFR § 1020.320(e), a SAR and any information that would reveal its existence are confidential and cannot be disclosed except through specific authorized channels.7eCFR. 31 CFR 1020.320 – Reports by Banks of Suspicious Transactions Courts have treated this as an absolute evidentiary privilege. If a party in civil litigation subpoenas a bank’s SAR records, the bank must refuse production.
The regulation sets out the response. The bank should decline to produce the SAR, cite 31 CFR § 1020.320 and 31 U.S.C. § 5318(g)(2)(A)(i), and notify FinCEN of the request and the bank’s response.8Financial Crimes Enforcement Network. Disclosure Prohibited The notification step is easy to overlook during active litigation, but skipping it defeats part of the regulatory design.
There is a key distinction between the SAR itself and the underlying facts. The transactions, documents, and records that prompted the SAR are not privileged simply because a SAR was filed about them. Bank statements, wire transfer records, and account opening documents remain subject to normal discovery. What the institution cannot disclose is the report, its contents, the fact that it was filed, or any internal work product that would reveal its existence.9Federal Register. Confidentiality of Suspicious Activity Reports If SARs themselves were discoverable, sophisticated criminals could use civil litigation to learn exactly what tripped the detection systems and restructure around it.