The conventional wisdom says more is better. File liberally. When in doubt, file. Your institution's SAR count demonstrates vigilance to examiners, and you can't be faulted for over-reporting. Better to flood the Financial Intelligence Unit with marginal reports than miss the one transaction that matters.
This approach has become orthodoxy in AML compliance. It's also counterproductive.
Why We Disagree
The "file everything suspicious" mindset confuses compliance activity with compliance effectiveness. Your SAR volume doesn't measure your program's quality. It measures your uncertainty.
Here's what happens when you treat SARs as defensive documentation: You bury law enforcement in noise. Analysts at your Financial Intelligence Unit (FIU) spend their time triaging hundreds of reports describing routine structuring, obvious typology matches, and behavior that twelve other institutions already flagged. The marginal SAR you filed to cover yourself sits in a queue behind 6,000 others, many describing the same customer's activity at different banks.
Your compliance team burns hours documenting low-conviction suspicions. You're writing narratives for transactions you don't actually believe warrant investigation. You're checking a box, not supporting law enforcement.
And you're training your monitoring system to cry wolf. When your alert-to-SAR conversion rate sits at 85%, your team stops evaluating alerts critically. They stop asking whether the activity genuinely indicates potential money laundering or terrorist financing. They just document and file.
The Evidence
Law enforcement has access to SARs from every institution. That's the point. A single customer's suspicious pattern should generate one or two well-documented reports from the institutions that observed the most relevant activity, not fifteen redundant filings describing the same wire transfers from slightly different vantage points.
The FIU doesn't need you to report every transaction that trips a threshold. They need context. They need your analysis of why this customer's behavior deviates from their established pattern. They need the details you observed that might connect to a larger investigation.
Consider what makes a SAR valuable to law enforcement: specific customer knowledge, transaction details that reveal intent, behavioral changes that suggest external pressure, relationships between parties that aren't obvious from account records alone. You can provide this information because you interact directly with customers and transactions. That's your unique position.
A report that says "customer made nine deposits of $9,500 over three weeks" tells law enforcement nothing they can't derive from Currency Transaction Report (CTR) data. A report that says "customer historically deposited $30,000-$40,000 monthly via single check from employer; switched abruptly to cash deposits just under $10,000; when branch staff asked about the change, customer became evasive and moved to ATM deposits" gives investigators something to work with.
Your narrative quality matters more than your filing frequency. Law enforcement needs information that helps them build cases for prosecution, not volume metrics that demonstrate your compliance department's productivity.
What to Do Instead
Start with your alert disposition process. If you're filing SARs on 70% or 80% of your alerts, your monitoring system is tuned incorrectly. You're either generating too many alerts or you're not investigating them properly. Fix the root cause.
Train your investigators to ask: "Does this activity indicate potential money laundering or terrorist financing?" Not: "Could an examiner question why we didn't file?" Those are different questions with different answers.
Document your analysis even when you don't file. If you investigated an alert and determined the activity has a legitimate explanation, write that down. Examiners want to see your reasoning, not just your SAR count. A well-documented decision not to file demonstrates stronger compliance judgment than a defensive filing.
Improve your narrative quality. Stop using template language. Describe what you observed, what you know about the customer, why the activity deviates from their pattern, and what you couldn't verify or explain. Give investigators the context they need.
Coordinate with your peers when you identify shared customers. If you know another institution already filed a comprehensive SAR on the same activity, your redundant report doesn't add value. Focus your resources on documenting what you uniquely observed.
Measure effectiveness, not volume. Track how often your SARs contribute to investigations. Request feedback from your FIU. Ask which reports provided useful information and which ones duplicated existing intelligence. Adjust your program based on outcomes, not activity counts.
When the Conventional Wisdom Is Right
File liberally when you're genuinely uncertain. If you've investigated an alert, documented your analysis, and still can't determine whether the activity has a legitimate explanation, file the SAR. That's appropriate escalation.
File immediately when you observe clear indicators of money laundering or terrorist financing. Don't wait to gather more evidence. Don't try to investigate beyond your role. Report what you know and let law enforcement take over.
File even when you suspect another institution already reported the same activity, if your observations add meaningful context. You might have customer information or transaction details that other institutions don't. The FIU can connect those pieces.
And yes, file when examiner guidance or regulatory expectations clearly indicate that your institution should report specific activity types. Your program operates within a regulatory framework. Just don't confuse regulatory compliance with investigative value.
The goal isn't fewer SARs. It's better SARs. Reports that actually help law enforcement investigate financial crime, not reports that protect you from examination criticism. Your FIU doesn't need more volume. They need more signal.
