Study guide
16.2 Writing Effective SAR and STR Narratives
ACAMS Certified AML FinTech Compliance Associate CAFCA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CAFCA Exam Overview and Study Strategy
1.1 CAFCA Exam Format, Official Domains, and Study Strategy
2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities
2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures
3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter
3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules
4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance
4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes
5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection
5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting
6 Chapter 6: Domain 1: Bank Partners and Internal Threats
6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse
7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD
7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types
8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data
8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics
9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags
9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies
10 Chapter 10: Domain 3: Payment Screening
10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls
11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags
11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization
12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics
12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens
13 Chapter 13: Domain 3: Monitoring Crypto Transactions
13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions
14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI
14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information
15 Chapter 15: Domain 4: Investigations and Customer Communication
15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps
16 Chapter 16: Domain 4: SARs and STRs
16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives
17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners
17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms
18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies
18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing
16.2 Writing Effective SAR and STR Narratives
Key Takeaways Explain This Topic AI
FinCEN's 2003 narrative guidance asks filers to cover who, what, when, where, why and how in a clear, complete and chronological narrative.
A strong narrative opens with a summary of the suspicious activity, gives the facts chronologically, and closes with the actions the institution took.
Narratives should include identifiers such as account numbers, amounts, dates, counterparties, IP addresses, device data and blockchain transaction hashes where relevant.
UK filers use NCA glossary codes such as XXS99XX to flag a request for a defence against money laundering.
Last updated: October 2026
CAFCA sub-topic 4.4 includes best practices for writing SARs and STRs. Analysts at the FIU and in law enforcement read thousands of reports. A clear narrative gets used, while a vague one gets ignored. In the US, FinCEN's guidance on preparing a complete and sufficient SAR narrative (2003) remains the standard reference.
The five Ws and how
Question What to include
Who is conducting the activity? Subjects' names, dates of birth, addresses, identification numbers, account numbers, occupation or business, relationship to the institution; counterparties and their banks or VASPs
- What happened? Instruments and methods (P2P, ACH, wire, card, crypto); products used
- When did it occur? Start and end dates; dates of key transactions; the date of initial detection
- Where did it happen? Branches or channels, countries, IP locations, receiving institutions, wallet addresses
Why is it suspicious? The red flags, how the activity departs from the expected profile, the typology it fits, and the customer's explanation and why it did not resolve the concern
How was it done? The mechanics: how funds entered, moved and left; the links between accounts; device or login patterns
A three-part structure
Introduction : one paragraph summarising the suspicious activity, the subjects, the total amount, the period, why it is suspicious, and any prior related SARs (by reference number). Include advisory key terms , such as FIN-2023-PIGBUTCHERING, in field 2 and the narrative where FinCEN requests them.
Body : a chronological account of the activity and the investigation. Cover the flow of funds, counterparties, patterns and amounts, technical indicators (IPs, device IDs, transaction hashes, wallet addresses), RFIs and responses, and open-source findings that support the suspicion.
Conclusion : the actions taken or planned (account restricted or closed, law enforcement contacted, funds frozen), whether supporting documentation is available, and a contact point.
FinCEN's electronic SAR accepts a single CSV attachment for tabular transaction data. The narrative must still explain the activity, so do not write only "see attachment".
- Before and after
- Weak : "Customer had unusual activity. Many transfers in and out. Possible money laundering. Account closed."
Strong : "Between 2 and 9 June 2026, Jane Doe (DOB 1 Feb 2004; account 1234) received 23 P2P credits totalling US$16,480 from 19 unrelated individuals in four states. Within an average of 18 minutes of each credit, she sent the funds by push-to-card to two cards issued to third parties, leaving a closing balance of US$12. Three senders filed scam complaints describing a fake rental listing. The device used to log in (device ID ABC…) was also used on accounts 5678 and 9012, which were opened in other names during the same week. When asked about the payments, Ms Doe said she was 'helping a friend with rent collection' but could not name the friend or provide any documents. The pattern is consistent with a funnel account receiving scam proceeds. The account was restricted on 10 June and will be closed. Supporting documentation is available on request."
Style rules
Be concise but complete. Include every fact a reader needs and nothing irrelevant.
Use plain language. Spell out internal codes and abbreviations, and do not name systems the reader will not recognise.
Be objective. Describe behaviour and facts. Avoid speculation and loaded language, and never refer to protected characteristics unless they are directly relevant (for example, elder exploitation).
Be precise. Give exact amounts, dates and identifiers, consistent with the structured fields of the form.
Explain the conclusion. Say clearly why the facts are suspicious. Do not assume the reader will infer it.
Do not copy and paste templates that do not fit the case.
Jurisdiction notes
United Kingdom : the NCA publishes guidance on SAR quality and glossary codes that help it route reports. For example, XXS99XX marks a request for a defence against money laundering. A DAML request must clearly describe the criminal property, the proposed transaction and the reasons for suspicion.
Other FIUs : many use structured goAML forms with a free-text section. The same five-Ws discipline applies.
Realistic exam scenario
A reviewer returns a draft SAR because it lists 60 transactions in a table but never explains what links them or why they are suspicious. The analyst should add an introduction summarising the scheme and a body that explains the funnel pattern, the counterparties and the evidence. The conclusion should note the restriction placed on the account, and the transaction table should be kept as supporting material.
Common exam traps
"See attached" narratives.
Omitting why the activity is suspicious , leaving only a list of transactions.
Including irrelevant personal details or speculation.
Leaving out advisory key terms that FinCEN has requested.