FinCEN Just Made 314(b) a Fraud-Fighting Tool

Last updated: June 2026

Fraud rarely stays inside one institution's walls. The same scheme can touch multiple banks, payment processors, fintechs, and counterparties before any single institution has the full picture. FinCEN's June 2026 Section 314(b) update is aimed at that reality. It pushes financial institutions to use the fraud safe harbor as a practical information-sharing tool, not a last-resort exception, and to stop treating SAR confidentiality as a broader restriction than the law actually imposes.

That matters because the criminal networks behind pig butchering, romance scams, mule accounts, and crypto off-ramps already operate as networks. They know which accounts are active, which exchanges are receiving funds, and which victims have not yet realized what happened. They move that information in real time because coordination is how the money moves before anyone can stop it.

Financial institutions have their own coordination tool: Section 314(b), a voluntary safe harbor created to let institutions share information about possible money laundering or terrorist financing. But in practice, many programs have used it cautiously, slowly, or not at all. Some institutions are not registered. Others respond too late for the information to matter. Many limit fraud-related sharing because they are unsure where the SAR confidentiality line sits.

FinCEN's June 12, 2026 fact sheet addresses those hesitations directly. It confirms that fraud is within scope, clarifies what can be shared without revealing a SAR, and explicitly encourages real-time information sharing. For compliance teams dealing with fast-moving scams and mule networks, the message is straightforward: 314(b) was built for this kind of moment.

This article breaks down what changed, what institutions can share, where the SAR line sits, and what compliance teams should update now.

TL;DR

• FinCEN's June 2026 fact sheet confirms Section 314(b) covers fraud, not only money laundering. That includes pig butchering, romance scams, and mule account activity.

• Institutions can share transaction records, device data, IP addresses, and adverse media. They cannot share a SAR or reveal one exists, but the underlying facts a SAR is based on are not themselves protected.

• FinCEN now explicitly endorses real-time sharing, responding to industry findings that delayed sharing arrives too late to interrupt fast-moving fraud.

• Registration in FinCEN's Secure Information Sharing System must be renewed annually; an expired registration means no safe harbor, and processing takes two business days.

Can Section 314(b) be used for fraud?

The biggest practical change for most programs is the explicit treatment of fraud. Fraud is a predicate crime under 18 U.S.C. § 1956, and it's been a specified unlawful activity since the beginning. But plenty of compliance programs have been running 314(b) as an AML-only tool, hesitant to apply it to fraud cases because the connection wasn't explicit in prior guidance.

The June 2026 fact sheet is direct about it. The covered activities include "an array of fraudulent and other criminal activities, including fraud against individuals, organizations, or governments, computer fraud and abuse, and other crimes." Pig butchering proceeds, romance scam funds, mule account activity, and first-party fraud rings are all within scope. You can share information about attempts to engage in transactions as well, including money mule schemes. You do not need to have confirmed that proceeds are involved. You need a reasonable basis to believe the information relates to activity that may involve money laundering or terrorist financing, and you need to be sharing it for a permissible purpose.

That's not a high bar. It's a lower threshold than most programs have been operating against, and it covers the exact categories where speed decides whether information sharing interrupts the crime or merely documents it: authorized push payment fraud, pig butchering, and money mule movement.

What can institutions share under 314(b) without revealing a SAR?

The reason many institutions have been cautious with 314(b) is the SAR confidentiality concern: share too much and you've accidentally revealed that you filed, which is a BSA violation regardless of whether the safe harbor applies. That concern is real. The line, however, is narrower than most programs treat it.

The prohibition is specific: you cannot share a SAR, and you cannot share information that would reveal the existence of a SAR. What the fact sheet makes clear is that the underlying facts, transactions, and documents on which a SAR is based are not themselves SAR-protected. Transaction records, entity relationship data, typology characterization, monitoring alerts, adverse media, device data, IP addresses, and video surveillance footage can all be shared. There is no limitation on the type or medium of information under the safe harbor. What you cannot share is the SAR decision itself and anything that reveals it was made.

The practical distinction matters: an investigator who understands this can share aggressively. An investigator who doesn't know where the line is often shares nothing, which is the worst outcome for the program and for the victims on the other end of the crime.

One note from industry practice: describing activity as "unusual" or "questionable" and leading with the factual pattern is cleaner than using the word "suspicious," which in certain contexts implies a SAR decision has been made.

When collaboration under 314(b) identifies suspicious activity, the fact sheet specifically contemplates a joint SAR as the natural result. Institutions considering or having already filed a joint SAR may freely discuss it among themselves. That's the program working as intended: shared intelligence leading to a more complete filing that gives law enforcement an actual picture of the network rather than three separate partial views. Getting that right depends on AML monitoring that can surface the relationships behind an alert while staying explainable and examiner-ready, so the facts assembled for sharing are clean and the SAR narrative stays distinct.

Why real-time sharing is now the standard FinCEN expects

The other thing the June 2026 update does is push hard on speed. The guidance is explicitly intended to promote greater information sharing "including in real time." That phrasing is not decorative.

Consider what happens after a pig butchering victim sends the first wire. The funds hit a mule account at Bank A. Within hours, they move to Bank B, then Bank C, then out through a crypto exchange or mixing service. In October 2025, the Department of Justice announced the seizure of approximately $15 billion in Bitcoin tied to one such operation, the largest forfeiture action in DOJ history. The same coordinated action saw Treasury sanction Cambodia-based Prince Group and the DOJ indict its chairman, Chen Zhi (also known as Vincent), for directing forced-labor scam compounds and laundering billions in illicit proceeds. Huione Group, which served as laundering infrastructure for these networks, processed more than $4 billion in illicit funds between August 2021 and January 2025, according to U.S. Treasury reporting. These are industrial-scale operations with purpose-built infrastructure for moving money faster than compliance can respond. The same Prince Group network ran scam compounds managing tens of thousands of accounts with automation that legacy transaction monitoring rules were never built to match.

Pig butchering victims are not people who made a careless decision. They were targeted by organized criminal enterprises, many of them operating out of forced labor compounds in Southeast Asia where the workers running the scams were themselves trafficked. The grooming process runs for weeks or months. By the time the first wire is sent, the victim genuinely believes in the relationship or the investment. The bank receiving that wire has no way to know. But a bank that has seen these mule account patterns before, and shares that account profile and device data through 314(b) with the receiving institution before the transfer clears, has a chance to interrupt the chain. That depends on AML transaction monitoring that analyzes activity in milliseconds rather than overnight batches.

That is what the tool is for. A 314(b) request that arrives three weeks after the fact is documentation. It is not intervention. Industry research from Datos Insights identified response latency as a significant failure mode in existing 314(b) programs. FinCEN's explicit endorsement of real-time sharing is a direct response to that reality.

The question for compliance teams is no longer whether 314(b) can support fraud investigations. The question is whether their systems can support it fast enough.

How Oscilar helps operationalize real-time 314(b) sharing

Running 314(b) at the speed FinCEN is now describing requires case management infrastructure that was built for it. Most legacy systems weren't.

Oscilar's case management platform brings together transaction records, entity relationships, typology characterizations, adverse media, device intelligence, and monitoring alerts in a single structured case card. That matters for 314(b) specifically because the underlying facts, the shareable category, are already assembled and distinguishable from the SAR narrative, which is not. When a request comes in or needs to go out, the package is ready rather than scattered across systems.

Intelligent queuing routes incoming 314(b) requests by case type and severity, so they don't sit in a shared inbox waiting for someone to notice them. Prioritization models surface the highest-urgency matters first. For a program trying to operate at real-time speed, that infrastructure is the difference between a 314(b) program that functions and one that exists on paper.

When collaboration leads to a joint SAR, which the fact sheet specifically contemplates, Oscilar's AI-generated SAR narratives and automated evidence collection reduce the documentation burden of a multi-institution filing. The audit trail built into the system also supports the safe harbor documentation requirements: what was shared, with whom, when, and for what permissible purpose. It is the same unified approach MoneyGram adopted when it moved its fraud, AML, and compliance operations onto a single real-time platform to keep pace with cross-border threats.

Oscilar also tracks 314(b) requests and responses end to end, giving compliance teams visibility into where requests stand, how long they're taking, and what's outstanding. That tracking feeds dashboards that surface trends over time: which customer populations are generating requests, which geographies are showing up repeatedly, which typologies are driving activity across institutions. That's not just operational convenience. If you're seeing a consistent pattern in the requests you're receiving or sending, that pattern is telling you something about the threat environment your institution is operating in. The programs that get ahead of typologies are the ones reading that signal rather than just processing the queue.

What compliance teams should do now

Read the June 2026 fact sheet and compare it against your current internal 314(b) policy. If your policy is more restrictive than what the guidance authorizes, on fraud coverage, on the types of information that can be shared, or on response timeframes, update it.

Confirm your registration in FinCEN's Secure Information Sharing System is current. Registration must be renewed annually. An expired registration means no safe harbor, and processing takes two business days.

Train your investigators on where the SAR line actually sits. The fact sheet's clarity on what is and isn't protected belongs in your AML training curriculum, and teams modernizing AML monitoring more broadly can work from a practical framework for applying AI across AML operations while keeping it examiner-ready.

And build for speed. The 2026 update is FinCEN telling you that a program designed for formal legal correspondence is not the program they're describing. The threat shares information in real time. Your program should too.

FAQs: Section 314(b) information sharing

Does 314(b) cover fraud?

Yes. FinCEN's June 2026 fact sheet states explicitly that Section 314(b) covers an array of fraudulent and criminal activities, including fraud against individuals, organizations, and governments, computer fraud and abuse, and money mule schemes. Fraud has been a predicate offense for money laundering under 18 U.S.C. § 1956 since the program began in 2001; the 2026 update removes any doubt that institutions can apply the safe harbor to fraud cases such as pig butchering, romance scams, and first-party fraud rings.

Can institutions share transaction records under 314(b)?

Yes. Under the safe harbor, institutions can share transaction records, entity relationship data, monitoring alerts, adverse media, device data, IP addresses, and even video surveillance footage. The June 2026 fact sheet confirms there is no limitation on the type or medium of information shared, provided the sharing is for a permissible purpose and the institution has a reasonable basis to believe the information relates to possible money laundering or terrorist financing.

Can institutions discuss SARs under 314(b)?

Institutions cannot share a SAR itself or any information that would reveal a SAR exists. Doing so is a BSA violation regardless of the safe harbor. However, the underlying facts, transactions, and documents on which a SAR is based are not SAR-protected and can be shared. The June 2026 fact sheet also confirms that institutions considering or filing a joint SAR may freely discuss it among themselves.

Does 314(b) allow real-time information sharing?

Yes. FinCEN's June 2026 fact sheet explicitly encourages greater information sharing, including in real time. The guidance responds to industry findings, including Datos Insights research identifying response latency as a significant failure mode, that delayed sharing often arrives too late to interrupt fast-moving fraud and laundering chains.

How often does 314(b) registration need to be renewed?

Annually. Institutions must maintain a current registration in FinCEN's Secure Information Sharing System, and that registration must be renewed each year. Processing a registration takes two business days, and an expired registration means the safe harbor does not apply.

NEW GUIDE

Agents in AML: A Production Playbook from the Investigator's Seat

Get your copy

->

References

• FinCEN, Section 314(b) Fact Sheet (June 12, 2026)

• FinCEN, FinCEN Issues Guidance to Help Financial Institutions Eliminate Fraud Through Information Sharing (June 12, 2026)

• Datos Insights, Section 314(b) information sharing for financial crime prevention (2025)

• U.S. Department of Justice, Chairman of Prince Group indicted; record $15 billion forfeiture (October 14, 2025)

• U.S. Department of the Treasury, Prince Group TCO sanctions and Huione Group section 311 final rule (October 14, 2025)