Study guide
Supporting Functions and Risk Partners
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
Supporting Functions and Risk Partners
Key Takeaways Explain This Topic AI
AFC programs depend on partner functions: legal, human resources, information technology and data, fraud, operations, and procurement/vendor management.
Internal audit (third line) provides independent assurance and must remain separate from the controls it tests.
Outsourced and third-party arrangements (KYC utilities, screening vendors) do not transfer regulatory responsibility, which stays with the institution.
CAMS scenarios test which partner owns a dependency and whether oversight of outsourced work is adequate.
Last updated: June 2026
The Program Does Not Operate Alone
CAMS tests the reality that an anti-financial-crime (AFC) program depends on partner functions across the institution. A monitoring rule is only as good as the data that feeds it; a SAR is only as defensible as the legal review behind it. Knowing which risk partner owns each dependency is frequently examined.
Key Supporting Functions
Partner function Contribution to the AFC program Example dependency
Legal Interpret obligations, manage privilege, advise on production requests Whether a disclosure is lawful or constitutes tipping-off
Information technology / data Provide complete, accurate, timely data to monitoring and screening A data feed gap means alerts are never generated
Human resources Screen and train staff, manage conduct cases, support whistleblowing Pre-employment screening for sensitive AFC roles
Fraud Share intelligence; fraud and money laundering often overlap A mule account flagged by fraud is also an AML concern
Operations Execute holds, freezes, account closures Timely execution of a sanctions freeze
Procurement / vendor management Govern third-party screening and KYC utilities Oversight of an outsourced alert-review provider
Internal Audit As Independent Assurance
Internal audit (the third line of defense) is a partner but a deliberately independent one. It tests whether the risk assessment, monitoring, screening, and reporting actually work, and reports findings to the board or audit committee. To preserve independence, audit must never have designed or operated the controls it reviews, a point CAMS contrasts against quality assurance, which sits inside the second line and tests case quality day to day.
Outsourcing And Third-Party Reliance
Institutions increasingly use external KYC utilities, screening vendors, and managed-service providers. The governing CAMS principle is unambiguous: regulatory responsibility cannot be outsourced. The institution remains accountable for the work even when a vendor performs it. That requires:
Due diligence on the vendor before engagement.
A contract with clear scope, service levels, audit rights, and data-protection terms.
Ongoing oversight: sampling the vendor's output, monitoring service levels, and periodic reassessment.
A documented exit and contingency plan.
Reliance on a third party for customer due diligence is permitted in many regimes only when the institution can obtain the underlying records promptly and the relied-upon party is itself adequately regulated.
Worked Scenario
A bank outsources alert triage to a vendor and the vendor clears a batch of alerts without documenting rationale. An examiner cites the bank, not the vendor. The failure is inadequate oversight: no sampling, no quality checks, no audit rights exercised. The remediation is enhanced vendor oversight and re-review of the cleared alerts, because accountability never left the bank.
Common Traps
Believing a vendor contract transfers regulatory liability.
Letting internal audit operate a control and then audit it.
Ignoring data-quality dependencies and blaming the monitoring system for missed alerts that were really a data-feed gap.
The exam-ready instinct: identify the owning partner, confirm oversight exists, and remember responsibility stays in-house.
Distinguishing Quality Assurance From Internal Audit
A frequently tested nuance is the difference between quality assurance (QA), quality control (QC), and internal audit. QC and QA sit inside the second line: QC checks work as it is produced (for example, a reviewer confirming an analyst documented an alert disposition correctly), while QA samples completed work to measure consistency and feed back improvements. Internal audit is the third line and provides independent, periodic assurance to the board that the whole control framework, including the QA function itself, is effective.
Because QA is part of the function it tests, it can never substitute for audit, and audit can never run QA without losing independence. When a scenario describes a team that both performs investigations and certifies their quality to the board, the exam wants you to flag the missing independent third-line assurance.
Sharing Intelligence Across The Fraud And AML Divide
Fraud and money laundering increasingly converge, and CAMS expects the program to treat fraud teams as genuine risk partners rather than a separate silo. A mule account identified by fraud is also an AML concern, scam proceeds become laundering flows, and the same customer data can surface both. The leading practice is a shared intelligence channel, common watchlists where lawful, and joint typologies, sometimes formalized as a financial-crime unit that combines fraud, AML, and sanctions. The constraint is data protection and privilege: information sharing must respect legal limits, which is exactly why legal is a standing risk partner.
The exam-correct instinct is to break down silos for detection while respecting the legal boundaries that legal and compliance jointly police, and to remember that wherever a function is outsourced or shared, the institution still owns the regulatory outcome.
Governing The Vendor Relationship Over Time
Vendor oversight is not a one-time procurement event; it is a lifecycle the exam expects you to manage. Before engagement, the institution conducts due diligence on the vendor's competence, financial stability, security, and its own financial-crime controls. At contracting, it secures clear scope, measurable service levels, audit and inspection rights, data-protection and confidentiality terms, sub-contracting limits, and a defined exit. During the relationship, it monitors performance against the service levels, samples the vendor's output for quality, reassesses the vendor's risk periodically, and reviews any incidents.
Concentration risk matters too: relying on a single screening or KYC-utility vendor for a critical control creates a single point of failure, so contingency and exit planning are part of prudent governance. The recurring exam lesson is that the contract is necessary but never sufficient; it is the ongoing, evidenced oversight that discharges the institution's duty. When a scenario shows a vendor failing, look first for the missing oversight activity, the unexercised audit right, the absent sampling, the unmonitored service level, because that gap, not the vendor's error alone, is what an examiner will cite against the institution.