Study guide

Documentation and Evidence Quality

CAMS Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CAMS Orientation and Exam Facts

Current CAMS Exam Format Eligibility Credits and ACAMS Membership Package Pricing and Study Materials Pearson VUE Scheduling Window Passing Score and Result Reporting Exam Non-Disclosure and Practice Ethics

2 Chapter 2: Financial Crime Risks and Methods

AML, CFT, Sanctions, Fraud, ABC, and Tax Evasion Financial Systems and AFC Consequences Predicate Crimes and Financial Crime Exposure Sector, Product, Customer, Jurisdiction, and Channel Risk Banking Products and High-Risk Sectors Politically Exposed Persons and High-Risk Customers

3 Chapter 3: High-Risk Sectors and Structures

MSBs, PSPs, and E-commerce Platforms Insurance Product Risk VASPs, Cryptoassets, and Related Products Gaming, Gambling, and Real Estate Gatekeepers, Trusts, and Company Service Providers Accountants and Other High-Risk Structures

4 Chapter 4: Global AFC Frameworks

FATF Role and Recommendations United Nations Sanctions Regimes Regulators, Law Enforcement, and FIUs Public Sector, Private Sector, and NGO Objectives Cross-Border Cooperation Authority Reports, Trends, and Typologies

5 Chapter 5: Governance Regulations and Information Sharing

Risk-Based Regulatory Expectations Regulatory Examinations and Enforcement Public-Private Partnerships Information Sharing Mechanisms De-Risking and Financial Inclusion RFIs, Tipping Off, and Customer Communication

6 Chapter 6: AFC Compliance Program Design

Effective Program Pillars Three Lines of Defense and MLRO Role Risk Appetite Statement Enterprise Risk Assessment Risk-Based Controls Policies Standards and Procedures

7 Chapter 7: Program Governance and Operating Model

Horizon Scanning and Regulatory Guidance Governance Committees and Terms of Reference AFC Team Structure and Responsibilities Front Office Interaction Supporting Functions and Risk Partners Training, Awareness, and Staff Risk Culture

8 Chapter 8: Customer Lifecycle Controls

Control Tools Across the Customer Lifecycle Data Quality, Integrity, Access, and Taxonomy Customer Experience and Friction Digital Onboarding and Electronic KYC (e-KYC) External Data Sources and Beneficial Ownership Customer Screening and Sanctions Lists

9 Chapter 9: Ongoing Controls and Monitoring

Periodic Refresh and Perpetual KYC Adverse Media Screening Batch Screening and Fuzzy Logic Transaction and Payment Screening Rules-Based Transaction Monitoring Model Risk Management and Tuning

10 Chapter 10: Investigations and Case Support

Investigation Triggers and Case Triage Open Source Tools and Investigator Support Escalation and Suspicious Activity Decisions Documentation and Evidence Quality Law Enforcement and FIU Requests Post-Investigation Feedback Loops

11 Chapter 11: Technology and Emerging AFC Practice

AI and Machine Learning in AFC Controls Blockchain Transaction Screening Automation to Support Investigators Scenario Coverage and Threshold Setting Data Privacy, Cybersecurity, and Other Risk Functions Technology Governance for AFC Tools

12 Chapter 12: Final CAMS Review and Exam Day

Domain-Weighted Study Allocation Simulator Practice Without Actual Exam Claims Pearson VUE Identification and Test Rules Time Management and Guessing Strategy Retake Extension and Appeal Boundaries Recertification and Ongoing Membership

Documentation and Evidence Quality

Key Takeaways Explain This Topic AI

The SAR narrative is the heart of the report — it must answer who, what, when, where, why, and how in clear, factual language.

Good documentation is contemporaneous, objective, source-cited, and free of speculation or conclusions of law.

Supporting documentation must be retained for 5 years and provided to FinCEN or law enforcement on request — but not attached to the SAR itself.

Poor narratives (vague, jargon-heavy, missing dollar amounts or dates) are a leading cause of low-value SAR filings.

Last updated: June 2026

Why Documentation Quality Matters

A Suspicious Activity Report (SAR) is only as valuable as the facts and narrative behind it. The Financial Crimes Enforcement Network (FinCEN) and law-enforcement analysts read thousands of filings; a vague report buries the signal. The CAMS exam treats evidence quality and the SAR narrative as core investigator skills, because a defensible file protects the institution and a clear narrative makes the report actionable.

The SAR Narrative: Five W's and How

The narrative is the heart of the SAR. It should be written in plain English and answer the classic questions:

  • Element What to capture
  • Who Subjects, account holders, beneficial owners, counterparties
  • What The suspicious activity and why it is suspicious
  • When Specific dates and the time span of the activity
  • Where Branches, jurisdictions, accounts, instruments involved
  • Why The articulable basis for suspicion (typology, deviation from profile)
  • How The mechanics — cash, wires, structuring, third parties

Always quantify : state exact dollar amounts, transaction counts, and date ranges. "Customer made nine cash deposits totaling $84,600 between March 3 and March 7 across three branches" is far stronger than "customer made several large deposits recently."

Hallmarks of High-Quality Evidence

Contemporaneous. Record findings as the work is done; memory and reconstruction weaken reliability.

Objective and factual. Describe what was observed; avoid speculation, emotion, or legal conclusions such as "the customer is a money launderer." State facts that support suspicion.

Source-cited. Note where each fact came from — internal system, registry, court record, adverse media — with retrieval dates.

Complete and self-contained. A reader with no prior context should understand the case from the narrative alone.

Free of unexplained jargon and acronyms. Spell terms out; analysts outside the institution must follow it.

Worked Example: Weak vs. Strong

Weak: "Customer's activity looked off and seemed like laundering, so we filed." This states a legal conclusion, gives no amounts, dates, or mechanism, and is not actionable.

Strong: "Between 03/03/2026 and 03/07/2026, the customer deposited cash in nine transactions totaling $84,600 at three branches, each between $9,200 and $9,800 — amounts consistently below the $10,000 CTR threshold. Stated occupation (part-time tutor) does not support this volume. No legitimate source of funds was provided. Activity is consistent with structuring." This is factual, quantified, sourced, and immediately useful.

Retention and the Supporting File

The institution must retain the SAR and all supporting documentation for five years from the filing date and make it available to FinCEN or law enforcement upon request . A key exam point: do not attach supporting documents to the SAR ; reference them in the narrative and hold them in the case file. Supporting documentation includes transaction records, account-opening files, internal memos, and the investigator's notes.

Structuring the Narrative

FinCEN guidance favors a logical narrative structure. A reliable template:

Introduction — who is filing, what type of activity, the total amount, and the date range.

Body — a chronological account of the activity with specific transactions, amounts, dates, and parties.

Conclusion — why the activity is suspicious (the typology and the deviation from expected profile) and any action taken.

Write in the past tense, third person, and active voice. Define every entity on first mention and avoid internal codes the reader cannot decode.

Documenting the No-File Decision

The exam stresses that closing a case without filing also requires documentation. A clear, contemporaneous rationale — "the large deposit was a documented inheritance supported by a probate record" — protects the institution if the activity is later questioned. Undocumented closures are an audit and examination red flag, because they suggest decisions were not risk-based.

A Quality Checklist

Before a SAR leaves the queue, an investigator should confirm:

Every dollar amount, date, and transaction count is specific and accurate .

The narrative names all subjects and counterparties and their roles.

The basis for suspicion is stated as fact, not as a legal conclusion.

Sources for external facts are identified.

The narrative is self-contained and readable by an outside analyst.

Acronyms are spelled out on first use.

Supporting documents are retained, not attached .

Why Quality Drives Value

Law enforcement prioritizes actionable filings. A 2019-era FinCEN advisory theme that the exam echoes is that vague, formulaic SARs waste analyst time and obscure genuine threats. A precise narrative — quantified, sourced, and typology-aware — increases the chance the report supports an investigation or asset seizure. Quality documentation is therefore not bureaucratic overhead; it is the deliverable that gives the entire investigation its public-protection value, and it is the single artifact an examiner reviews to judge whether the program's investigations are effective.

Common Traps

Conclusions instead of facts. Write what supports suspicion, not a verdict.

Omitting amounts and dates. Numbers make a narrative actionable.

Attaching files to the SAR. Keep them in the case file; provide on request.

Backdating or editing notes. Documentation must be contemporaneous and tamper-evident to remain credible in an examination or court.