Section 314(b): What It Requires and Who It Applies To

What is Section 314(b)?

Section 314(b) of the USA PATRIOT Act (Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act), signed into law on October 26, 2001, is a voluntary program that lets financial institutions share information about suspected money laundering and terrorist financing directly with each other. FinCEN published the implementing rule in November 2002 (67 Fed. Reg. 60579), with the program taking effect in December of that year.

The program exists because of a structural problem that predates 9/11. Privacy laws, including the Right to Financial Privacy Act and the Gramm-Leach-Bliley Act, blocked institutions from sharing customer information across organizations. A criminal who spread transactions across five banks could evade detection at each one. No single institution had the full picture, and the law didn't allow them to build one together.

Section 314(b) addresses this by creating a statutory safe harbor. When an institution shares information in good faith under an active 314(b) notice, it's protected from civil liability under those privacy statutes. There's no FinCEN intermediary. Two participating institutions can contact each other directly, share what they've found, and jointly assess a suspect's activity across the system.

What it doesn't do is replace the Bank Secrecy Act reporting framework. Filing a suspicious activity report remains a separate obligation. Section 314(b) runs alongside SAR filing. It gives investigators a channel to gather more information before, during, or after a SAR decision; it doesn't substitute for one.

Who does Section 314(b) apply to?

Any financial institution with a qualifying BSA/AML program can participate. There's no asset-size threshold. A $300 million community bank and a $3 trillion global custodian face identical eligibility criteria. What matters is whether the institution maintains a compliant BSA/AML program under the Bank Secrecy Act.

The following entity types are eligible:

• Insured depository institutions (national banks, state-chartered banks, savings associations, federal and state-chartered credit unions)
• Broker-dealers registered with the SEC under the Securities Exchange Act of 1934
• Mutual funds subject to a FinCEN AML program requirement
• Futures commission merchants and introducing brokers subject to CFTC oversight
• Money services businesses registered with FinCEN (see MSB Registration for program requirements)
• Insurance companies subject to a FinCEN AML rule
• Casinos and card clubs with BSA obligations
• Loan and finance companies subject to BSA requirements

Participation is voluntary, but zero activity doesn't go unnoticed. Examiners at the OCC, FDIC, Federal Reserve, and NCUA increasingly flag institutions with high-risk customer bases that show no 314(b) usage as having program gaps.

Jurisdictionally, the program is domestic. Foreign branches of US institutions may participate if they're covered by the same AML program as the US parent, per FinCEN's 2009 guidance (FIN-2009-G002). A foreign bank without a US presence cannot participate directly.

One practical point worth stating plainly: participation requires an active annual notice on file with FinCEN. If that notice lapses, every subsequent 314(b) exchange loses its safe harbor protection, even if the institution otherwise runs a fully compliant AML program.

What does Section 314(b) require?

Once an institution decides to participate, six core obligations apply.

1. File an annual notice with FinCEN. Before any information exchange, the institution must register through FinCEN's 314(b) participation system. The notice includes basic identifying information, a designated contact, and a certification that the institution maintains a qualifying AML program. It must be renewed each year. Missing the renewal is the single most common compliance failure.

2. Maintain a qualifying AML program. Participation is contingent on having a BSA-compliant AML program with four core elements: written internal controls, independent testing, a designated BSA officer, and ongoing staff training.

3. Limit sharing to ML/TF suspicions. Information shared under Section 314(b) must relate specifically to suspected money laundering or terrorist financing. The program doesn't cover general fraud, credit risk data, or any other customer information. Institutions that use the 314(b) channel for off-scope purposes lose safe harbor protection for those exchanges.

4. Verify counterparty participation before each exchange. Before sharing, the initiating institution must confirm that the receiving institution has a current, valid 314(b) notice registered with FinCEN. FinCEN maintains a searchable participant directory for exactly this purpose. Assuming ongoing participation without checking is a known failure point.

5. Keep received information confidential. Institutions receiving information under 314(b) must treat it as confidential. It cannot be disclosed to the subject of the inquiry without following strict protocols, and it cannot be re-shared outside the 314(b) framework.

6. Act in good faith. The liability safe harbor applies only to good-faith disclosures. Sharing information for improper purposes, sharing outside the ML/TF scope, or sharing with a non-participant voids the protection for that specific transaction.

There's no mandated minimum volume of 314(b) activity. In practice, institutions with high-risk customers, MSB relationships, or significant cash-intensive business that show zero 314(b) requests face scrutiny. FinCEN's FAQs on Section 314(b) are worth reviewing for specific edge cases on scope and eligible counterparties.

What evidence do regulators expect?

On exam day, supervisors aren't checking whether a 314(b) notice is on file. They're testing whether the program is operationally real. Here's what they look for:

• Current annual notice. A valid, unexpired 314(b) notice registered with FinCEN. Examiners verify directly against FinCEN's participant list.
• Written policies and procedures. The AML compliance manual should describe the full lifecycle of a 314(b) request: who can initiate, how counterparty participation is verified, how received information is handled, and how results feed into SAR decisions.
• Training records. Investigators, relationship managers, and BSA officers should have documented 314(b) training refreshed at least annually.
• Request logs. A log of all 314(b) requests sent and received, including date, counterparty institution, subject of inquiry, and outcome. There's no mandated format, but the absence of any log is treated as evidence of a non-functioning program.
• Counterparty verification records. Documented proof that before each exchange, the institution confirmed the counterparty's current participation status via FinCEN's list.
• Integration with SAR workflow. Examiners want to see 314(b) results tied directly to SAR decisions. If an institution investigates a high-risk customer and never checks whether another institution holds relevant information on the same subject, that's a procedural gap. The two processes need to connect.
• Escalation procedures. Documentation showing how 314(b) results that reveal significant suspicious activity are escalated within the compliance function and whether they triggered enhanced due diligence reviews.

The broader expectation is proportionality. Institutions with simple retail portfolios face less scrutiny over low 314(b) volume. Institutions with complex commercial books, MSB customers, or correspondent banking relationships will not.

Common failure modes

The failure patterns seen across exams and enforcement actions are consistent.

• Lapsed annual notices. The most frequent finding. An institution participates for a year or two, the renewal falls off the compliance calendar, and subsequent exchanges occur without valid safe harbor protection. One missed renewal exposes all subsequent sharing to civil liability.
• Scope creep. Teams that treat 314(b) as a general information-sharing tool start using it for fraud or credit risk cases. These exchanges fall outside the ML/TF scope and lose safe harbor protection.
• No counterparty verification. Institutions assume that because a counterpart participated last year, it's still participating now. FinCEN's participant list changes. Sharing with a lapsed participant is treated identically to sharing outside the program.
• Disconnected investigations. Investigators complete SAR reviews without checking whether a 314(b) request to another institution could have added material information. This is a systemic process failure, not an individual oversight. It shows up repeatedly in exam findings for institutions with complex commercial customers.
• Missing documentation. No request logs, no records tying 314(b) activity to case files, no evidence that counterparties were verified before exchanges. Examiners treat absent records as direct evidence of program failure, not just administrative sloppiness.
• Passive participation. Filing the annual notice but never making a request. For institutions with high-risk customers, this signals that 314(b) is a compliance checkbox rather than a working investigative tool.

FinCEN's May 2020 advisory on COVID-19-related financial crime (FIN-2020-A002) specifically called on financial institutions to use 314(b) actively when investigating pandemic-related fraud schemes tied to money laundering activity. That advisory made clear that passive participation alone doesn't meet FinCEN's expectations.

Penalties for non-compliance

Section 314(b) doesn't carry its own standalone penalty provision. Failures surface as components of broader BSA/AML enforcement actions under 31 U.S.C. § 5321 and § 5322.

Civil penalties under the BSA reach $25,000 per violation per day for non-willful violations. Willful violations carry up to $100,000 per day or twice the amount of the underlying transaction, whichever is greater. Criminal violations can result in fines up to $250,000 and prison terms up to five years, rising to ten years when connected to other federal financial crimes.

Enforcement comes from the institution's primary federal regulator (OCC, FDIC, Federal Reserve, or NCUA), often in coordination with FinCEN. The DOJ Criminal Division handles criminal referrals.

Standalone enforcement for 314(b) weaknesses alone is rare. The more common pattern is 314(b) failures appearing within comprehensive BSA/AML consent orders and assessments. FinCEN's $390 million assessment against Capital One in January 2021, published on FinCEN's enforcement page, cited a sustained failure to investigate suspicious customers and inadequate use of available information-sharing tools. The related DOJ action resulted in a $290 million criminal penalty and a guilty plea.

The Anti-Money Laundering Act of 2020 expanded FinCEN's penalty authority. Regulators can now scale penalties to the benefit an institution gained from non-compliance, rather than applying only a flat per-day rate. For institutions that processed high volumes of suspicious transactions without adequate investigation, that calculation can produce substantially larger figures than the statutory per-day formula alone.

Related regulations and frameworks

Section 314(b) sits within the broader BSA/AML architecture. The Bank Secrecy Act is the parent statute; 314(b) is a voluntary mechanism within it that extends what institutions can do after they identify suspicious activity.

Its closest counterpart is Section 314(a), the mandatory program where FinCEN sends institutions searchable lists of named subjects suspected of terrorism or money laundering, and institutions must respond within 14 days. The two provisions work in opposite directions. Section 314(a) flows from FinCEN to institutions; Section 314(b) flows between institutions.

The FinCEN CDD Rule governs the customer due diligence baseline every institution must maintain. Strong CDD records are often exactly what gets exchanged in a 314(b) sharing event. CDD and 314(b) are complementary: one builds the file, the other lets institutions share it when suspicion warrants.

At the international level, FATF Recommendation 20 requires all countries to mandate STR filing with their national financial intelligence unit. Section 314(b) goes a step further by creating a domestic institution-to-institution channel that FATF's framework doesn't directly address. FATF focuses on institution-to-FIU flows; 314(b) fills the horizontal information gap between institutions that FATF leaves open.

The AMLA 2020 directly strengthened 314(b) by requiring FinCEN to evaluate the program's effectiveness and by expanding the conditions under which SAR-related information can be shared with foreign subsidiaries of US financial institutions. The BIS's 2018 working paper on information barriers in cross-border financial crime (BIS Working Paper 730) identified voluntary information-sharing programs as significantly underused in most jurisdictions. The US 314(b) model remains one of the few operational examples at scale.

How FluxForce supports Section 314(b) compliance

FluxForce's AI agents automate the investigative steps that feed into 314(b) activity. Nova Sentinel monitors transaction patterns continuously and flags subjects that warrant a 314(b) inquiry before a human investigator would catch the signal. Aiden Flux manages the documentation trail. Every sharing request, counterparty verification, and outcome is logged against the underlying case file automatically. The platform's regulatory compliance automation capabilities track annual notice renewal dates and generate alerts when participation is at risk of lapsing. To see how this works in practice, book a demo.