Reporting AML Failures Without Disclosing a SAR: What the Transactions and Decisions Can Show

SAR confidentiality and whistleblower evidence can coexist: an insider’s account can explain transactions and control failures without disclosing the report or revealing that one exists. You may know which alerts went unreviewed, what testing found and why management kept the same settings. Those decisions can be the story.

Can a Bank Whistleblower Use Underlying Transaction Records?

Underlying transaction records can provide whistleblower evidence about an anti-money laundering failure. The bank’s suspicious activity reporting rule distinguishes the facts, transactions and documents behind suspicious activity from the suspicious activity report itself. The question for an insider is what you personally know, what you lawfully hold and where the rest of the evidence sits.

A payment record describes money moving. Customer information describes the business the bank expected to see. Monitoring settings and testing results can explain why the activity never reached an investigator. Together, those records may connect the transaction to a decision inside the institution.

Are SAR Filings Confidential?

Yes. SAR confidentiality protects the suspicious activity report and information that would reveal its existence.

An insider may recognize a monitoring failure through the settings, the test results or management’s response to a warning. We can begin with the work you performed, the decisions you witnessed and the evidence locations you know.

Confidentiality and effective oversight belong together. The Wharton Initiative on Financial Policy and Regulation’s 2024 paper, Anti-Money Laundering: Opportunities for Improvement, examined a leak of Financial Crimes Enforcement Network documents and identified both weaknesses in safeguarding confidential information and substantial bank compliance failures. The paper treats protecting confidential information as essential to the system’s integrity. A useful whistleblower account brings the control failure into focus while respecting the protected report.

Reporting AML Failures Without Disclosing a Suspicious Activity Report

To report AML failures without disclosing a suspicious activity report, the useful starting point is the underlying conduct: what happened, who made the decision, what warning reached them and what followed. A monitoring system’s history can make that account concrete.

Bank of America’s Alerts Aged Out Before Investigation

Bank of America admitted anti-money laundering program and reporting failures in its October 2026 consent order. The Financial Crimes Enforcement Network assessed a $1,200,000,000 civil penalty.

Its Event Processor grouped customer alerts and ordinarily required 20 points before an investigation began. Alerts older than 13 months stopped contributing to the score.

Testing found high SAR yields among activity below the investigation threshold. Yet the bank kept the threshold until December 2023. The order also describes resource concerns and suppression rules that lacked adequate testing.

The bank had evidence that its filter was missing activity worth reporting. The filter stayed. For someone who works in monitoring, the relevant history includes the setting actually used, the test that challenged it, who received the result and the decision that followed.

The same order described online auto auction customers whose periodic reviews omitted negotiable instruments despite heavy use of them. Internal escalation did not produce adequate changes to customer risk profiles or ongoing monitoring. Here the issue was what the bank’s review left out and what happened when the concern reached people inside it.

Those are different failures with different evidence. One concerns the rule controlling which alerts became investigations. Another concerns customer activity left out of a review. An insider who knows the system or the customer can explain the difference.

What Proof Do You Need as a Whistleblower?

Useful whistleblower evidence connects transactions, controls and decisions. Your firsthand knowledge, your analysis, what others told you and records you lawfully hold make different contributions. Knowing where investigators can obtain an additional record can also matter.

Payments and Customer Records Connect the Activity

Account records, payment messages and customer due diligence connect money moving through the institution to the customer and the business it claimed to conduct. The useful comparison is between expected activity and what actually happened: the counterparties, currencies, amounts and timing.

An onboarding employee may know what the customer said the account was for. A payments employee may understand the transfers. A reviewer may know why a concern was escalated. Each can explain a different part of the same activity.

Monitoring and Testing Explain What Reached Review

The version of a monitoring scenario actually deployed matters. So do excluded transaction categories, risk overrides, validation results and the thresholds controlling review. A written policy can describe a control that the live system did not deliver.

Staffing and Escalation Explain the Response

Budget decisions, audit findings and management escalations can connect a known weakness to the people responsible for fixing it. An alert queue has a staffing story as well as a software story.

The Financial Crimes Enforcement Network’s consent order concerning USAA Federal Savings Bank described understaffed alert review and inadequate identification and reporting of suspicious transactions. For an employee familiar with that kind of failure, review capacity and the response to internal warnings can explain why activity stayed unresolved.

Exchange Records Connect the Transfer to the Customer

At a crypto exchange, a public transaction hash can show a transfer while the customer credited for it appears in the exchange’s internal ledger. Wallet control, customer information, screening decisions and escalation history supply different parts of the account. The person who understands those connections can explain much more than a blockchain trace alone.

The Financial Crimes Enforcement Network’s Bittrex consent order addressed anti-money laundering program and suspicious activity reporting failures at a virtual currency exchange and hosted-wallet business. The technology changed where the records sat. The institution still had decisions about identifying customers, monitoring activity and reporting suspicion.

Why a Report Count Does Not Explain the Failure

The number of reports an institution files cannot explain what its monitoring missed. The Wharton paper distinguishes increased reporting from evidence that the system works better:

That uncertainty is where an insider’s account adds something a filing total cannot. A test result may show what the threshold missed. An audit finding may identify a category the system excluded. A management instruction may explain why the setting stayed in use.

The paper also discusses conflicting incentives inside financial institutions: compliance staff may see their work as supporting law enforcement while others treat it as an expense to minimize. The budget, warning and response make that tension specific to a business. They show what happened behind the policy.

A SAR and a Whistleblower Tip Serve Different Purposes

A suspicious activity report is the institution’s account of suspicious activity. A whistleblower tip supplies information about a possible violation, including failures in the institution’s own controls or reporting. An award claim is a separate part of the whistleblower program.

Information learned through anti-money laundering or compliance work can matter. The statute includes information learned and reported as part of a whistleblower’s job duties, as the Financial Crimes Enforcement Network explains in the statutory background to its April 2026 proposed rule.

The agency describes awards totaling 10% to 30% of the money collected in qualifying enforcement actions imposing more than $1 million in penalties, shared among eligible whistleblowers, but FinCEN says award processing and payment will begin only after final regulations.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. We connect the conduct you know to the appropriate whistleblower case and the evidence it needs.

When the Evidence Raises Questions

Questions about SAR confidentiality, privilege, anonymity or your own role in the conduct belong in a conversation with our whistleblower experts and anti-money laundering whistleblower counsel. We work through them with you alongside the facts of the case.

Our starting point is your knowledge of the failure.

The Decision Behind the Missed Activity

If you know why alerts went unreviewed or a failed control stayed in place, speak with our whistleblower experts about the decisions you witnessed. We build the case with you around the transactions, testing and management response, and bring in anti-money laundering whistleblower lawyers who understand both the control failure and SAR confidentiality. From the first conversation through the case, we stay at your side to build your strongest anti-money laundering whistleblower case.