STR Report

When to Use

Draft or restructure a suspicious transaction report (STR) or suspicious activity report (SAR) narrative for AML compliance filing or internal MLRO review
Build the who / what / when / where / why suspicion story with clear chronology and aggregated transaction facts
Map red flags and typologies (structuring, layering, trade-based ML, etc.) to observable facts—not conclusions without evidence
Compile subject and customer identification fields, related parties, accounts, and product/channel context for filing templates
Produce a supporting documentation checklist and exhibit index aligned to the narrative
Run quality review (completeness, consistency, tone, PII handling) before submission to MLRO or regulator-facing systems
Compare jurisdiction-agnostic structure with high-level US (FinCEN SAR), EU, and goAML field concepts (not legal filing advice)
Distinguish STR/SAR from internal case notes, management summaries, or law enforcement referral packages
Escalate and hand off to MLRO/compliance with a structured fact pack and open questions