Study guide
15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps
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
15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps
Key Takeaways Explain This Topic AI
Confirmation bias is the tendency to seek and interpret evidence that confirms an existing belief while overlooking evidence against it.
Analysis of competing hypotheses, set out in Richards Heuer's 1999 book Psychology of Intelligence Analysis, tests evidence against several explanations at once.
Automation bias is over-reliance on a tool's score or alert, such as accepting a low risk score without examining the activity.
Investigation notes should separate facts, inferences and conclusions, so that a reviewer can test each step.
Last updated: October 2026
CAFCA sub-topic 4.3 covers analytical principles in an investigation , with confirmation bias as the named example. Investigators make judgements under uncertainty, time pressure and incomplete information. Bias leads to two kinds of failure. Some suspicious activity is wrongly closed. Some innocent customers are wrongly reported or exited. The exam tests whether you can recognise bias and apply structured methods.
Common biases in AML and fraud work
Bias What it looks like in an investigation Countermeasure
Confirmation bias Deciding early that the customer is a mule, then reading every transaction as proof and ignoring the payslips List evidence against the working theory; test alternative hypotheses
Anchoring Over-weighting the first fact seen, such as the alert's title or a high risk score Review the full file before forming a view; reassess after each new item
Availability bias "Last week's case was a scam, so this one is too", because recent cases come to mind easily Use the evidence for this case and refer to base rates
Automation bias Accepting a vendor "low risk" score or an auto-closure suggestion without looking Treat scores as inputs, not conclusions; sample auto-closures
Affinity or halo bias A polished corporate website or a senior job title lowers scrutiny Apply the same tests to every customer
Stereotyping Treating nationality, religion or ethnicity as evidence of crime Base conclusions on behaviour and facts; follow fair-treatment rules
Overconfidence Closing on a "gut feeling" with little evidence recorded Require stated evidence for every conclusion
Hindsight bias In QA, judging an earlier analyst as if later facts had been known at the time Review decisions against what was knowable then
Groupthink The team accepts the first view voiced in a case meeting Assign a devil's advocate; collect independent views first
Sunk cost Continuing an unproductive investigation because so much time has gone into it Set review points; close or escalate on the evidence
Core analytical principles
Objectivity : let the evidence lead. The goal is the truth, not a SAR or a closure.
Separate fact, inference and conclusion. For example: Fact : 14 inbound transfers from unrelated senders in 48 hours. Inference : consistent with funnel activity. Conclusion : suspicious, escalate.
Generate alternative hypotheses. For a burst of P2P inflows, consider (a) legitimate group payments, (b) a mule account, (c) the customer being a scam victim, and (d) account takeover.
Seek disconfirming evidence. What would we expect to see if the legitimate explanation were true? Look for it.
Weigh the reliability of sources , giving more weight to independent and authoritative sources (Chapter 8).
Be proportionate and timely. Gather enough evidence to decide reasonably within the deadlines. Certainty is not the standard.
Document the reasoning so that a reviewer can follow and challenge it.
Analysis of competing hypotheses (ACH)
Richards Heuer's Psychology of Intelligence Analysis (1999) popularised ACH . List the hypotheses across the top and the evidence down the side. Mark whether each item is consistent or inconsistent with each hypothesis. The hypothesis with the least inconsistent evidence is usually the strongest, even if another has more consistent items.
- Evidence H1: legitimate group refunds H2: mule account H3: customer is a scam victim
- 14 senders, no common link Inconsistent Consistent Neutral
- Funds forwarded within 20 minutes to a crypto exchange Inconsistent Consistent Consistent
- Several senders reported scams Inconsistent Consistent Neutral
- Customer says a "job" told them to forward funds Neutral Consistent (unwitting mule) Consistent
- Device shared with two other accounts Inconsistent Consistent Inconsistent
Here H1 has the most inconsistent evidence. H2, an unwitting mule, fits best. That affects how the firm treats the customer, possibly as a vulnerable person who has been exploited, and what goes into the SAR narrative.
Safeguards built into the process
Templates that require alternative explanations and supporting and contradicting evidence.
Peer review or four-eyes for escalations and for closures of high-risk cases.
QA calibration sessions where analysts compare decisions on the same cases.
Training on bias, with real (anonymised) examples.
Realistic exam scenario
An analyst sees an alert titled "Possible terrorist financing – high-risk country". The customer's nationality matches the country, and the analyst begins drafting a SAR. A reviewer notes that the transfers are monthly payments of US$200 to a family member, consistent with the declared purpose and income, with no adverse information. The analyst anchored on the alert title and stereotyped by nationality. The right approach is to assess the actual activity and evidence. That points to closure with a documented rationale, unless other red flags emerge.
Common exam traps
Equating a high risk score with suspicion. A score prompts a review; it is not evidence.
Ignoring evidence that contradicts the working theory.
Using nationality or ethnicity as evidence.
Hindsight bias in QA.