
SAR Filing Narrative Compiler
Generate FinCEN-compliant SAR narratives from investigation documentation
What You Can Do
This skill converts complex investigation findings, transaction data, and suspicious activity documentation into precise, fact-based SAR narratives that clearly establish nexus to money laundering, terrorist financing, or predicate crimes. You input raw investigation notes and transaction patterns, and Claude generates compliant narratives structured for regulatory review, eliminating speculation and ensuring investigative integrity while satisfying FinCEN requirements.
Features
organizes investigation findings into chronological, fact-based storylines with clear nexus to predicate offenses
creates legally precise connections between observed activity and potential money laundering or terrorist financing indicators
structures structuring, round-tripping, layering, and beneficial ownership evasion patterns into coherent narratives
ensures narratives align with FinCEN Form 111 requirements and examination standards
synthesizes complex, multi-account or multi-party patterns into unified, understandable narratives
documents investigation timelines and explains delays with regulatory transparency
incorporates OFAC, sanctions, and international transaction context into narratives
structures narratives to withstand compliance review and external audit scrutiny
Example Output
Input: Transaction notes showing $50K deposits in round amounts over 2 weeks to shell company account, followed by immediate wire transfers to known high-risk jurisdiction, with beneficial owner identity unclear despite requests.
Generated Narrative Output:
Between [DATE] and [DATE], Customer [NAME]/Account [#] received five deposits totaling $50,000 in round amounts ($10,000 each) originating from multiple third-party sources. Deposits were structured at or below $10,000 thresholds. Within 24 hours of each deposit, funds were transferred via wire to [JURISDICTION] to entity [BENEFICIARY], which refused beneficial ownership documentation despite institution requests on [DATES]. Analysis indicates potential structuring to evade reporting thresholds combined with rapid movement to high-risk jurisdiction consistent with money laundering layering phase. Institution has no legitimate business rationale for structured deposits and rapid cross-border movement pattern.
Input: Investigation notes on individual opening accounts under multiple aliases with conflicting documentation and small deposits followed by large withdrawals.
Generated Narrative Output:
Between [DATE] and [DATE], institution identified customer [NAME] operating under aliases [ALIAS 1], [ALIAS 2] opening four separate deposit accounts within 10 days using inconsistent identification documents. Discrepancies identified in [SPECIFIC DOCUMENT DETAILS]. Each account received small deposits ($500–$2,000) from consistent third-party source over [PERIOD], followed by large cash withdrawals ($8,000–$12,000 per withdrawal) over [PERIOD]. Pattern is consistent with potential money laundering placement and integration phases. Account activity ceased after [DATE]. No legitimate business explanation provided.
What's Included
- SKILL.md instruction file with FinCEN compliance guidelines and narrative structure requirements:
- SAR narrative template: pre-structured format for organizing investigation facts with nexus language placeholders
- Red flag documentation checklist: structured list of suspicious indicators (structuring, round-tripping, layering, beneficial ownership evasion) with narrative examples
- FinCEN Form 111 requirement alignment guide: cross-reference of narrative elements to specific Form 111 fields and regulatory expectations
- Examination-ready narrative examples: 3–4 sample narratives for different violation types (structuring, sanctions evasion, shell company abuse) demonstrating compliant formatting
Who It's For
- BSA/AML Officers — create and revise SAR narratives meeting regulatory requirements
- Compliance Managers — review and approve narratives before FinCEN submission
- Bank Examiners — evaluate narrative quality and compliance during regulatory examinations
- Risk Management Teams — document suspicious activity findings with regulatory precision
- Fraud Investigators — structure investigation notes into formal reporting documentation
Best For
- Initial SAR narrative compilation from investigation notes and transaction analysis
- Narrative revision for compliance review findings or external audit feedback
- Complex multi-transaction pattern documentation with multiple accounts or parties
- Structuring and layering pattern documentation requiring precise nexus language
- Cross-border transaction narratives requiring OFAC and sanctions context
- Delayed SAR justification with timeline documentation
- Beneficial ownership evasion and shell company red flag documentation




