90% of SARs Are Noise: Why Your Suspicious Activity Report Gets Ignored
FinCEN receives 3+ million SARs annually. Most get 8 seconds of attention. The problem isn't volume—it's defensive filing. Here's what regulators actually want to see.
90% of SARs Are Noise: Why Your Suspicious Activity Report Gets Ignored
Published: May 28, 2026
Category: AML / Compliance
Reading Time: 4 minutes
The 2 AM Report
You stayed up until 2 AM writing that Suspicious Activity Report.
The regulator scanned it for 8 seconds. Then moved on.
This isn't because you don't care. It's because most SARs were never designed to be read.
The Numbers Don't Lie
FinCEN receives over 3 million SARs annually. FATF has repeatedly criticized member countries for low-quality STRs/SARs in mutual evaluations.
The problem isn't volume. The problem is signal-to-noise ratio.
What is "Defensive Filing"?
Banks are afraid of fines. So they file at the first hint of risk. Not because they genuinely suspect crime—but because "not filing = not doing your job."
The result:
- 30% of SARs are one-line templates
- 50% lack transaction pathway descriptions
- 70% include no recommended follow-up actions
This creates a paradox: the more SARs you file, the less any single SAR matters.
What Do Regulators Actually Want?
Not: "This person transferred money."
But:
1. Why is it suspicious?
What specific behavior, pattern, or typology triggered the alert? Generic descriptions like "unusual activity" are worthless.
2. How did the money move?
Not raw transaction logs—a narrative of the pathway. Source → intermediate accounts → destination. Timing, velocity, sequencing.
3. Who is connected?
Counterparties, beneficial owners, related entities, shell companies. The network matters more than the individual.
4. When did the pattern emerge?
Timing analysis. Is this new behavior? Escalating? Tied to a specific event or jurisdiction?
5. What next?
Continue monitoring? Close the account? Deep-dive investigation? Without a recommendation, the SAR dies in the inbox.
A Good SAR Checklist
A SAR that gets read—and acted upon—includes:
- [ ] Specific amounts, timestamps, and counterparties
- [ ] Transaction pathway narrative (not just raw data)
- [ ] Risk assessment (why this person/transaction is high-risk)
- [ ] Recommended follow-up (monitor/close/dive deeper)
- [ ] Supporting documents (KYC records, adverse media, related parties)
The Core Principle
A SAR isn't "safe" just because you filed it.
A SAR is valuable when it helps law enforcement catch criminals.
If your regulator can't understand it, act on it, or follow up on it—it's noise. And in a system drowning in noise, the signal gets lost.
The Fix
The compliance industry needs to shift from defensive filing to intelligence-led reporting.
- Fewer SARs, but higher quality
- Narrative-driven, not template-driven
- Actionable, not archival
This isn't just about writing better reports. It's about building systems that surface genuine risk instead of manufacturing compliance theater.
Related Reading: FinCEN SAR Guidance
Tags: #AML #SAR #Compliance #FinancialCrime #FinCEN #FATF #RiskManagement #RegTech
UWAY Compliance Team
UWAY Innovation Limited is a Hong Kong-based compliance technology partner specializing in KYC, KYB, and AML infrastructure for Web3 and fintech firms.