Fraud and money laundering rarely stay inside the walls of a single institution. A scam that drains one account often resurfaces at another bank within days, and the compliance team that caught it the first time is sometimes the only one that knows what to look for. Section 314(b) of the USA PATRIOT Act gives financial institutions a voluntary way to close that gap by sharing information about suspected illicit activity, protected by a legal safe harbor.
On June 12th, 2026, the Financial Crimes Enforcement Network (FinCEN) issued an updated Section 314(b) Fact Sheet clarifying how the safe harbor works, confirming that it extends to fraud, and encouraging real-time sharing between institutions. This article covers what Section 314(b) permits, how it differs from Section 314(a), what changed in the June 2026 update, and how to register.
Key Highlights
- Section 314(b) of the USA PATRIOT Act creates a voluntary safe harbor that protects financial institutions from civil liability when they share information about suspected money laundering, terrorist financing, or fraud.
- FinCEN’s June 12th, 2026 update confirmed that fraud qualifies as a specified unlawful activity (SUA) under 18 U.S.C. § 1956, extending the safe harbor to scams, mule networks, and other fraud typologies.
- Participation requires registration through FinCEN’s Financial Institutions (FI) Portal, and registration must be renewed annually to keep the safe harbor active.
- Institutions may share information verbally, in writing, or electronically, including in real time as activity is occurring.
- A financial institution cannot disclose a Suspicious Activity Report (SAR) itself or confirm one exists, though the underlying facts that led to a SAR can be shared.
- Unlike Section 314(a), which requires financial institutions to respond to mandatory law enforcement search requests, participation in 314(b) is entirely voluntary.
What Section 314(b) Allows Financial Institutions to Share
Section 314(b) permits two or more registered financial institutions, or an association of financial institutions, to share information about individuals, entities, or transactions they suspect may involve money laundering, terrorist financing, or fraud. Sharing is not limited to a specific customer or account relationship, and a registered institution can share with another registered institution even if the receiving institution has no existing relationship with the individual involved.
An institution does not need to identify specific fraud proceeds being laundered before it shares information. A reasonable suspicion is enough, which matters for fast-moving typologies like pig butchering scams and mule account activity, where waiting for conclusive proof means the money is already gone. Institutions typically exchange transaction records, device and IP data, and adverse media, feeding directly into the kind of automated transaction monitoring programs compliance teams already use to flag suspicious patterns.
314(b) vs. 314(a): Two Different Tools
Section 314(b) is often confused with its counterpart, Section 314(a), but the two work in opposite directions. Section 314(a) is mandatory: FinCEN transmits information requests from law enforcement, and institutions must search their records and respond within the required window. Section 314(b) is voluntary: it lets institutions share information directly with one another without a government request driving the exchange. For a closer look at the mandatory side of the program, see our guide to FinCEN 314(a) compliance.
What Changed in FinCEN’s June 2026 Update
The June 2026 Fact Sheet replaced FinCEN’s December 2020 guidance and made two notable changes. First, it confirmed that fraud offenses fall within the safe harbor’s scope, aligning 314(b) with the Treasury’s broader fraud-prevention priorities set out in two March 2026 executive orders on cybercrime and predatory schemes. Second, it explicitly endorsed real-time information sharing, removing ambiguity about whether the safe harbor was limited to formal, delayed correspondence. The full Section 314(b) Fact Sheet is available from FinCEN, and the FDIC’s related notice outlines what the update means for supervised institutions.
Registering for the 314(b) Program and Staying Compliant
To rely on the safe harbor, an institution must register through FinCEN’s FI Portal, verify that any counterpart it shares information with is also registered, and renew that registration annually. An expired registration means no safe harbor protection. Institutions must also maintain procedures to safeguard shared information and use it only for permissible purposes, such as investigating suspicious activity or deciding whether to file a SAR. Documenting how shared information factors into an investigation is easier when alerts, case notes, and evidence live in one case management system rather than scattered across emails and spreadsheets.
Turning Information Sharing Into a Stronger Compliance Program
Section 314(b) will not replace a strong internal AML and fraud program, but it extends visibility beyond what any single institution can see on its own. As FinCEN pushes institutions toward faster, broader information sharing, compliance teams that pair 314(b) participation with disciplined internal monitoring and clear case documentation are better positioned to catch mule activity and cross-institution scams before losses compound. Alessa’s AML compliance software helps teams connect that shared intelligence to their existing monitoring and reporting workflows.
