Study guide
Rules-Based Transaction Monitoring
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
Rules-Based Transaction Monitoring
Key Takeaways Explain This Topic AI
Transaction monitoring detects suspicious patterns after the fact using scenarios/rules with thresholds (e.g., structuring, rapid movement, high-risk geography).
U.S. CTR threshold is over $10,000 in cash in one business day; structuring to evade it is itself a federal crime regardless of source of funds.
Alerts are not SARs: alerts are reviewed, dispositioned, and only confirmed suspicion leads to a SAR (filed within 30 days of detection in the U.S.).
Rule design balances coverage and noise; poorly tuned rules cause alert backlogs and missed activity, both regulatory findings.
Last updated: June 2026
Rules-Based Transaction Monitoring
Transaction monitoring is the detective control that reviews completed activity for patterns indicative of money laundering, terrorist financing, or fraud. Rules-based (scenario-based) monitoring is the predominant approach: the institution codes scenarios with parameters and thresholds, and any activity breaching a threshold generates an alert for human review. It is reactive and pattern-focused, complementing the preventive, real-time payment screening covered earlier.
Common rule scenarios
Most programs run a library of scenarios mapped to known typologies:
- Scenario Typology detected Example parameter
- Structuring / smurfing Evading reporting thresholds Multiple cash deposits just under $10,000
- Rapid movement of funds Layering Funds in and out within 24–48 hours
- High-risk geography Placement / sanctions risk Wires to/from high-risk jurisdictions
- Velocity / volume change Activity inconsistent with profile Monthly turnover spikes 300% over expected
- Round-amount or pass-through Shell / funnel accounts Repeated round-number transfers
- Key U.S. thresholds the exam tests
Under the Bank Secrecy Act, a Currency Transaction Report (CTR) is required for cash transactions exceeding $10,000 in one business day (aggregated by the same person). Structuring — breaking transactions into amounts under $10,000 to avoid the CTR — is a separate federal crime under 31 U.S.C. §5324, and it is illegal even if the underlying funds are legitimate . A Suspicious Activity Report (SAR) must be filed within 30 calendar days of initial detection of facts that may constitute suspicious activity (up to 60 days if no suspect is identified).
The SAR filing threshold for many institutions is $5,000 in aggregate when a suspect can be identified.
Alerts are not SARs
The single most-tested concept here: a generated alert is not a SAR. The workflow is alert → review/investigate → disposition. Most alerts are false positives and are closed with documented rationale. Only when investigation confirms a reasonable basis to suspect illegal activity does the institution file a SAR. Filing a SAR for every alert (defensive filing) degrades the value of the data to law enforcement; closing alerts without documented rationale is a control failure.
Worked scenario
Monitoring flags a customer who made nine cash deposits of $9,500 across three branches over five business days — totaling $85,500 — with no apparent business reason. This is a textbook structuring pattern. The CAMS workflow: the alert is investigated, the analyst documents the pattern and the absence of a legitimate explanation, the institution files a SAR within 30 days, and critically the institution does not tip off the customer that a SAR was filed (tipping off is prohibited). No single deposit triggered a CTR, which is the point of structuring — monitoring catches the aggregate pattern that the CTR threshold alone misses.
Tuning and governance
Rules degrade over time as customer behavior and typologies evolve. Thresholds set too tightly create unmanageable alert backlogs (a frequent regulatory finding); set too loosely they miss activity. Rule changes require documented governance, and the program must be independently tested. Above-the-line/below-the-line testing (sampling alerts just above and below thresholds) is the standard tuning technique — covered in the next section on model risk.
Continuing-activity SARs and recordkeeping
Filing one SAR is rarely the end. When suspicious activity continues after an initial SAR, U.S. guidance expects institutions to review the relationship periodically — commonly every 90 days — and file a continuing-activity SAR if the conduct persists, capturing the aggregate of the prior period. Institutions must also retain SARs and supporting documentation for five years from the filing date, and must keep CTR records for five years as well. The supporting documentation is treated as part of the SAR and is subject to the same confidentiality and tipping-off protections.
Rules-based versus behavioral approaches
Pure rules-based monitoring has a known weakness: thresholds are static, so sophisticated launderers can transact just under them, and unusual behavior that does not breach any single rule can go undetected. This is why programs increasingly layer behavioral / anomaly-based monitoring and machine learning on top of rules — building a baseline of expected activity per customer and flagging deviations. The rules library still anchors regulatory expectations and explainability, while behavioral models widen coverage.
The exam frames this as complementary, not either/or: rules give defensible, transparent coverage of known typologies, and analytics extend detection to novel patterns, with both governed under model risk management.
Quality and effectiveness
A monitoring program is judged on effectiveness , not alert volume. Regulators examine whether scenarios map to the institution's actual risk profile, whether thresholds are tuned and tested, whether alerts are investigated within reasonable timeframes, and whether SAR decisions are sound and documented. Independent testing and quality assurance close the loop.
Common traps
Equating an alert with a SAR, or filing a SAR for every alert.
Closing alerts without documented rationale.
Ignoring structuring because no individual transaction broke the $10,000 CTR threshold.
Forgetting continuing-activity SAR reviews after the initial filing.
Tipping off the customer that activity was reported — a prohibited act.