Why These Mistakes Keep Happening
Your SAR narrative isn't just paperwork. It's the document explaining to law enforcement why you flagged a transaction. When you file a SAR, you're building a case file that investigators will use months or years later.
Most SAR narrative problems stem from three pressures: volume targets that prioritize speed over clarity, siloed teams that don't understand how law enforcement uses the reports, and compliance officers who've never seen what happens after they click "submit." Your narrative quality reflects whether you understand that a SAR is a communication tool, not a regulatory receipt.
The stakes are high. Incomplete narratives force investigators to request follow-up information, delaying action. Inaccurate subject details send law enforcement down false leads. Disorganized narratives make pattern analysis nearly impossible when investigators pull multiple SARs to build a money laundering case.
Mistake 1: Writing "See Attachment" Instead of a Narrative
Why it happens: You've compiled transaction logs, wire transfer details, and account analytics in a spreadsheet. It's comprehensive. Why duplicate that work in prose?
The consequence: SAR filing systems accept attachments as supplemental documentation, not as substitutes for the narrative section. When you write "see attachment" in the narrative field, you're forcing the investigator to reverse-engineer your suspicion from raw data. They don't know which transactions matter most, what pattern you identified, or why this activity crossed your threshold. The attachment becomes useless without context.
The fix: Use the narrative to guide the reader through the attachment. Write: "Between March and June, the account received 47 incoming wires totaling $890,000 from 12 different countries (see Attachment A for full wire detail). All funds were withdrawn in cash within 48 hours of deposit, structured in amounts below $10,000. No business rationale was provided despite three customer outreach attempts documented in Attachment B."
The attachment provides evidence. Your narrative provides the argument.
Mistake 2: Committing to Remedial Actions You Don't Track
Why it happens: You want to show regulators you're taking the account seriously. Writing "we will close this account within 30 days" or "this customer will be added to enhanced monitoring" feels proactive.
The consequence: These statements create enforceable commitments. Auditors, examiners, and prosecutors will follow up. If you stated you'd close the account and it's still active six months later, you've documented your own compliance failure. If you committed to 90-day reviews and your system shows no follow-up, you've handed regulators evidence of inadequate controls.
The fix: Only document actions you've already completed or that are automatically triggered by your system. Write "account closed on [date]" or "customer added to enhanced due diligence queue with automated 30-day review alerts" instead of future commitments. If you mention planned actions, assign ownership immediately, before you file, and build verification into your SAR quality control process.
Mistake 3: Omitting Subject Information You Actually Have
Why it happens: You're uncertain about data accuracy, worried about including information that might be wrong, or you don't realize how critical complete subject details are to investigative work.
The consequence: Law enforcement uses SAR data to link activity across institutions, identify networks, and build prosecution-ready cases. When you file a SAR without the subject's date of birth, business registration number, or known aliases, you've made it nearly impossible for investigators to connect your report to others. Incomplete subject information doesn't just weaken your SAR, it isolates it.
The fix: Include all known subject information at the time of filing. If you have a business name, include it. If you have multiple addresses on file, list them all. If the customer provided a tax ID that you later questioned, include it with a note: "Customer provided TIN XXX; verification pending." Uncertainty about one data point doesn't justify omitting it. Law enforcement can cross-reference questionable information; they can't work with information you never provided.
Mistake 4: Treating the Narrative as a Transaction Log
Why it happens: You're focused on accuracy and completeness, so you list every transaction chronologically without explaining why the pattern is suspicious.
The consequence: A narrative that reads like a ledger forces the investigator to do your analysis. They see 50 transactions but don't know which ones matter. They see amounts and dates but don't understand the typology you identified. The SAR narrative section is marked "critical" on the form because it's the only place where you explain your reasoning.
The fix: Lead with your suspicion, then use transactions as evidence. Structure your narrative: "This account exhibits structuring behavior consistent with Bank Secrecy Act evasion. Over 90 days, the customer made 23 cash deposits, each between $7,500 and $9,800, avoiding the $10,000 Currency Transaction Report threshold. Total deposits: $201,000. Customer stated business is consulting, but deposits occurred at branches across three states with no explanation for geographic distribution."
You're not just reporting what happened. You're explaining why it matters.
Mistake 5: Filing Without Cross-Checking Your Own Earlier SARs
Why it happens: Your case management system doesn't automatically surface prior SARs on the same subject, or analysts treat each suspicious activity as an isolated event.
The consequence: You file a SAR describing suspicious wire activity without mentioning that you filed three SARs on the same customer last year for cash structuring. Law enforcement pulls your latest SAR and has no context for the escalating pattern. You've fragmented a case that should be presented as continuing suspicious activity.
The fix: Before you finalize any SAR narrative, search your system for prior filings on the same subject. If you find earlier SARs, reference them: "This is the fourth SAR filed on this account. Previous SARs (filed [dates]) documented cash structuring and suspicious wire activity. Current activity represents continued pattern with increased transaction velocity." This continuity transforms individual reports into a case file that shows progression and persistence.
Prevention Checklist
Before you file your next SAR:
- Narrative explains not just what happened, but why you found it suspicious
- All available subject information included (name, DOB, TIN, address, business registration)
- Attachments are referenced specifically in the narrative, not used as substitutes
- Any remedial actions mentioned are already completed or automatically tracked
- Prior SARs on the same subject have been reviewed and referenced if relevant
- Narrative is organized by suspicion type, not just transaction chronology
- Someone other than the original analyst has reviewed for clarity and completeness
- Specific transaction details support the suspicion you identified (amounts, dates, patterns)
- You've avoided subjective conclusions without supporting facts
- The narrative would make sense to an investigator reading it six months from now with no other context
Your SAR quality directly determines whether law enforcement can act. Write every narrative assuming it will be the pivotal document in a prosecution, because it might be.
