Study guide
Policies Standards and Procedures
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
Policies Standards and Procedures
Key Takeaways Explain This Topic AI
Policies state principles (what and why), standards set measurable requirements, and procedures give step-by-step how-to instructions.
Documents must be board- or senior-management-approved, version-controlled, and reviewed on a defined cycle.
Governance committees (e.g., a financial-crime committee) provide oversight and a documented escalation path.
Record-keeping rules — generally five years under FATF — and SAR/STR confidentiality must be reflected in procedures.
Last updated: June 2026
Policies, Standards, and Procedures
An AFC program lives or dies on its documentation . Examiners and the third line test programs against written policies, standards, and procedures (PSPs) — and a program is only as good as its ability to show that what it does matches what it says . CAMS routinely tests the hierarchy among these documents and the controls that keep them current.
The document hierarchy
The three layers descend from principle to action, and candidates often blur them.
Document Answers Approved by Example
Policy What and why (principles, commitments) Board / senior management "We comply with all applicable AML laws and file SARs as required."
Standard What measurable requirement Senior management / committee "PEPs require EDD and annual review."
Procedure How, step by step Process owner / line management "To screen a new customer: 1) run sanctions list, 2) record result, 3) escalate any hit within 24 hours."
A policy that contains keystroke-level instructions, or a procedure that sets strategy, is mis-leveled. A CAMS distractor may swap these — for example, expecting the board to approve every procedural step (it approves the policy; owners maintain procedures).
Approval, version control, and review cycle
Every PSP must be:
Approved at the right level (policies by the board or a board committee).
Version-controlled with dates, owners, and a change history.
Reviewed on a defined cycle (commonly annually) and updated for regulatory change or new typologies.
An out-of-date procedure that still references a repealed rule is an audit finding. "Policy exists but staff cannot locate or follow it" is also a failure — accessibility and training are part of the control.
Governance committees and escalation
PSPs must define who decides and how issues escalate . A financial-crime / AML committee typically provides oversight, reviews metrics and key risk indicators, approves standards, and receives escalations the MLRO cannot resolve at the line level. The escalation path should be explicit so that a difficult onboarding or a contested alert reaches the right authority and is documented.
Record-keeping and reporting embedded in procedures
Procedures operationalize legal duties. Under FATF standards (and most national regimes, including the US BSA and EU directives), institutions must retain CDD and transaction records for at least five years . Suspicious-activity reporting procedures must reflect filing deadlines (US SARs within 30 days , extendable to 60 with no identified suspect) and tipping-off confidentiality. A scenario describing a bank that discards onboarding records after two years is testing the five-year retention rule.
Scenario workflow
For a documentation scenario, ask:
Is the document correctly leveled (policy vs. standard vs. procedure)?
Was it approved at the right authority and is it current ?
Does the escalation path / committee handle the issue, or is someone acting outside governance?
Do the procedures honor record-keeping (five-year) and reporting/confidentiality rules?
The best answer aligns the document to its proper level, keeps approval and version control intact, routes hard calls through the governance committee, and preserves required records. Watch the trap where an institution "has a policy" but no procedure to execute it — a stated commitment without an operational step is not an effective control.
Worked example
During an exam, a regulator asks how the bank screens new customers against sanctions lists. Staff produce a one-line policy statement ("we comply with all sanctions obligations") but no procedure describing which lists, how often screening runs, who reviews hits, and the escalation timeline. The policy exists; the operational control does not. The exam-preferred remediation is to build a documented, version-controlled procedure with named owners and clear escalation SLAs, train staff on it, and have the AML committee approve the supporting standard. "Has a policy but no procedure" is a recurring finding pattern.
Mapping documents to obligations
Procedures are where abstract legal duties become daily steps. Each major obligation should trace to a written procedure.
- Obligation Procedure must specify
- Customer identification (CIP) Which IDs, verification method, beneficial-owner collection at 25%
- Sanctions screening Lists used, frequency, hit-review and escalation steps
- Suspicious-activity reporting Internal report route, MLRO decision, 30-day filing, tipping-off ban
- Record retention Five-year minimum for CDD and transaction records
- Training Role-based content, frequency, attendance tracking
Governance ties it together: the financial-crime committee approves standards, reviews key risk indicators, and is the documented destination for escalations the line cannot resolve. A robust program can demonstrate the full chain — board-approved policy, management-approved standards, owner-maintained procedures, evidence of training, and an audit trail showing the documents are current and followed.
When a scenario shows a procedure citing a repealed rule, records destroyed early, or escalation handled informally by an individual outside the committee, the defect is documentary control, and the correct answer restores proper leveling, approval, version control, and retention rather than treating the lapse as harmless.
Why documentation drives examinations
Regulators and the third line cannot watch every transaction, so they test the system : do the written PSPs describe an adequate program, and does evidence show staff follow them? This is why "show me the procedure" and "show me the version history" are standard examination requests. Two failure modes recur on the exam. First, the gap between policy and practice — a strong policy that the front line never operationalizes. Second, the stale document — a procedure that survived a regulatory change unrevised. Both are control deficiencies even if no laundering occurred, because the program cannot demonstrate it would catch wrongdoing.
A practical discipline ties it together: every PSP carries an owner , an approval date and authority , a next-review date , and a change log . New typologies (for example, a virtual-asset laundering method) or new sanctions programs should trigger an out-of-cycle update. Training reinforces the procedures so staff actually execute them, and the AML committee receives metrics confirming the cycle runs.
The section's unifying rule: keep documents correctly leveled, current, approved, accessible, and supported by retained records — a stated commitment without an executable, evidenced procedure behind it is not an effective control, no matter how well it reads.