Study guide
14.2 Building an Audit Trail for Suspicious Activity Reviews
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
14.2 Building an Audit Trail for Suspicious Activity Reviews
Key Takeaways Explain This Topic AI
A good audit trail records the data reviewed, the sources used, the analysis, the decision, the rationale, the approver and the timestamps for each alert or case.
US banks must keep a copy of each SAR and its supporting documentation for five years from filing and provide them to FinCEN or law enforcement on request.
In October 2025, FinCEN and the federal banking agencies confirmed that the BSA does not require documenting a decision not to file a SAR, though many firms still record it.
Case notes should separate facts from inferences and conclusions, and SAR-related records need stricter access controls than ordinary case files.
Last updated: October 2026
CAFCA sub-topic 3.6 covers best practices in creating an audit trail , meaning documentation for all suspicious activity work. In compliance, a decision that is not documented cannot be shown to have been made properly. Examiners, internal auditors, partner banks and law enforcement all depend on the record.
Why the audit trail matters
Regulatory examinations sample closed alerts and filed SARs to test whether decisions were reasonable and timely.
Partner banks in BaaS programmes test the FinTech's closures as part of oversight.
Law enforcement may request the supporting documents behind a SAR.
Quality assurance and training need a record to review.
Continuity : when an investigator leaves, the next one must be able to pick up the case.
What to record for every alert and case
- Element Example content
- Identification Alert or case ID, scenario or rule triggered, date generated, assigned analyst
- Scope Accounts, customers and date range reviewed; linked alerts and cases
Data and sources Transaction extracts, KYC file, device and IP data, screening results, open-source items (with URL, date and capture), internal databases checked
Customer contact Date, channel and wording of any request for information, and the customer's response and documents
- Analysis Facts found; red flags present or absent; how the explanation was tested; typology considered
- Decision Close, monitor, escalate, restrict, exit, or refer for SAR/STR
- Rationale Why the evidence supports the decision
- Approvals Reviewer or approver name and role, and date
Follow-up Actions taken (holds, limits, exit), reminders, links to the SAR reference stored in the restricted repository
Qualities of good documentation
Contemporaneous : written at the time, not rebuilt weeks later.
Complete and specific : enough for a stranger to follow. Write "Reviewed 42 transactions, 1 March to 30 April; inflows from 17 unrelated P2P senders; 3 senders filed scam reports", not "reviewed, ok".
Objective : separate facts ("funds left within 20 minutes"), inferences ("consistent with pass-through") and conclusions ("suspicious; escalate"). Avoid speculation about personal characteristics.
Consistent : use templates and required fields so that quality does not depend on the individual.
Tamper-evident : case systems should log edits with user IDs and timestamps, and keep version history.
Access-controlled : SAR drafts, filings and any record that reveals a SAR need restricted permissions, because disclosure is a crime.
Retained : keep records for the legal period and make them retrievable (Chapter 18).
SAR records and decisions not to file
SARs and supporting documentation. US rules require keeping a copy of each SAR and its supporting documentation for five years from filing . Firms must give the supporting documentation to FinCEN or law enforcement on request, without a subpoena. Other regimes have similar retention rules.
Decisions not to file. In October 2025, FinCEN and the federal banking agencies issued FAQs confirming that the BSA does not require a firm to document a decision not to file a SAR. FinCEN had encouraged it, not required it. Most firms still record closure rationales, because internal policy, QA, partner contracts and other regulators expect them, and because they protect the firm when a decision is questioned later.
System-level audit trails
Beyond case notes, the platform should log:
Which rule or model version generated the alert, and the thresholds in force at the time.
Which sanctions list version was screened, and when.
Privileged actions , such as whitelist changes, overrides, manual releases and bulk closures, with user and approver.
Data feed completeness , meaning evidence that every transaction stream was ingested.
These logs show that the system worked, not only that analysts did their jobs.
Writing for the reader who comes later
Write every note for a reader who has no context: an examiner two years from now, a new analyst, or a prosecutor reading the supporting file. Use plain language and full dates, and define any internal codes. Name the documents relied on. Explain how the decision follows from the evidence, for example: "Payslip and employer contract match the inflows; the declared occupation is consistent; therefore no further action." When the evidence is mixed, say so and explain the weighing. A note that admits uncertainty and then justifies the decision is stronger than one that sounds confident but gives no reasons.
Realistic exam scenario
An examiner samples 60 closed alerts. Thirty-one say only "No suspicious activity – closed." There are no attachments and no record of what was reviewed. Even if the decisions were correct, the firm cannot show it. The examiner will likely cite inadequate documentation and may question whether the alerts were reviewed at all. The remedy is to mandate structured closure templates, retrain analysts, apply QA to closures, and look back at the poorly documented closures to confirm whether any need re-review.
Common exam traps
"Reviewed – OK" notes. These are not an audit trail.
Storing SAR files in a shared drive with broad access.
Back-dating notes to meet service levels. This is falsification and a serious breach.
Assuming no documentation is ever needed if no SAR is filed. The BSA may not require it, but policy, partners and good practice usually do.