Study guide

AI and Machine Learning in AFC Controls

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

AI and Machine Learning in AFC Controls

Key Takeaways Explain This Topic AI

Supervised models learn from labeled SAR/non-SAR outcomes; unsupervised models flag anomalies without labels, useful for novel typologies.

Machine-learning monitoring reduces false positives but cannot replace the human investigator's judgment or the legal duty to file a SAR.

Explainability is mandatory: regulators expect that any ML alert can be reconstructed and justified to an examiner.

Biased or unrepresentative training data can systematically under-detect risk in certain customer segments, creating fair-lending and AML exposure.

Last updated: June 2026

How AI and Machine Learning Fit AML Programs

Artificial Intelligence (AI) is the broad field of systems that perform tasks normally requiring human reasoning; Machine Learning (ML) is the subset where models learn patterns from data rather than from hand-coded rules. In anti-financial-crime (AFC) programs, ML is applied chiefly to transaction monitoring , customer risk rating , alert triage , and sanctions name-matching . The CAMS exam treats these tools as enhancements to a risk-based program, never as substitutes for the legal obligations of the financial institution.

Knowing the vocabulary matters because the exam tests judgment about the tool , not the mathematics behind it.

Traditional monitoring uses rules ("flag any cash deposit over USD 10,000"). Rules are transparent and easy to defend to an examiner, but rigid: they miss novel patterns and generate large volumes of false positives because they cannot weigh context. ML supplements rules by learning subtle correlations across many features at once, such as combining transaction velocity, counterparty risk, geography, and deviation from a customer's own baseline into a single risk score.

The exam point is balance: ML should augment a rules-based system, layering risk scoring on top of clear regulatory triggers, not silently replace the auditable rules an institution must still be able to explain. Many institutions therefore run ML alongside rules so that mandatory thresholds (like the Currency Transaction Report trigger) remain hard-coded and transparent.

Supervised vs. unsupervised learning

Type What it learns from AML use case Key limitation

Supervised Labeled outcomes (e.g., past alerts that became SARs vs. those closed) Predict which alerts are likely productive; alert scoring Only as good as past labels; misses typologies never previously detected

Unsupervised Unlabeled data; clusters and outliers Anomaly detection; surfacing novel or emerging typologies High false positives; needs human interpretation of clusters

Reinforcement / hybrid Feedback signals over time Tuning thresholds, optimizing review queues Hard to validate and explain to regulators

A frequent exam distinction: supervised models cannot detect a money-laundering method that has never appeared in the training data , because there is no labeled example to learn from. Unsupervised anomaly detection is the better choice for surfacing novel behavior.

Explainability, Bias, and Model Risk

Regulators in the United States (under the interagency Supervisory Guidance on Model Risk Management, SR 11-7 ) and elsewhere expect institutions to validate models and to explain individual outputs. A "black box" that flags a customer without a reconstructable reason is a compliance failure: an examiner must be able to ask why an alert fired and receive a defensible answer. This is why explainable AI (XAI) and documented feature logic are stressed. An institution that cannot articulate which features drove an alert cannot defend either its decision to file or its decision to close, and cannot prove it is not discriminating.

Bias is a recurring trap. Models learn whatever the training data contains, including the historical preferences and blind spots of the humans who labeled it. If training data over-represents one customer segment among historical SARs, the model can systematically over-flag that segment (creating fair-treatment and reputational risk) or under-flag another (creating detection gaps that let real laundering through). Both outcomes are AML problems and potential fair-lending or consumer-protection problems at the same time. Mitigation includes representative training data, fairness testing across segments, and human review of edge cases.

A further limitation is concept drift : criminal behavior evolves, so a model trained on last year's typologies degrades over time. This is why ongoing performance monitoring, not just an initial validation, is required.

Worked scenario

A bank deploys an unsupervised model that clusters customers. One small cluster shows rapid pass-through of funds, with deposits matched by near-immediate wires to high-risk jurisdictions. The model assigns no "label" but isolates the cluster as anomalous. The correct AFC response is not to auto-close or auto-file. It is to route the cluster to an investigator, who reviews KYC, transaction purpose, and source of funds, then decides whether a Suspicious Activity Report (SAR) is warranted. The model prioritizes work; the human decides and documents .

If the investigator finds a legitimate explanation (for example, a treasury function with a documented business purpose), the alert is closed with a recorded rationale rather than escalated reflexively.

Key exam reminders for ML in AFC:

A model output is an input to investigation , never an automatic SAR or automatic account closure.

Models must be validated before deployment and revalidated periodically and after material change or observed drift.

The institution remains fully liable for ML decisions; "the algorithm did it" is not a defense to a regulator.

Document the model's purpose, data, limitations, and override logic so examiners can reconstruct any output.

Test for bias across customer segments; an under-detecting model is a hidden AML gap.

The best answer on the CAMS exam usually preserves human judgment, documentation, and proportionality rather than maximal automation. AI augments the analyst; it does not assume the institution's legal responsibilities.

A final practical note on deployment. Many institutions adopt ML in a phased way: they run it in parallel (champion/challenger) against the existing rules for a period, comparing what each detects before relying on the model in production. This protects against a model that looks impressive in testing but under-detects in the real population, and it builds the documented evidence regulators expect before a new monitoring approach goes live.

The lesson the exam reinforces is sequence and proof: validate, run in parallel, document the comparison, obtain governance approval, and only then rely on the model, with ongoing monitoring for drift afterward. Skipping straight to full reliance on an unproven model, however sophisticated, is the wrong answer.