Lesson 08 of 25
Using the Enterprise-Wide AML Risk Assessment to Scope
4 min read · CAMS-Audit
Learn how the institution's AML risk assessment drives audit scope, and why the auditor both uses it and tests it. Keep inherent, control, and residual risk straight, and spot unsupported ratings.
The risk assessment drives the scope
- Enterprise-wide AML risk assessment = the program's risk map
- Audit scope should track that map
- Cover where the institution says its risk is highest
- And probe whether that map is even accurate
The single most important input to audit scope is the institution's enterprise-wide AML risk assessment. Think of it as the program's official risk map: it identifies where money-laundering and terrorist-financing risk concentrates across products, customers, geographies, and channels. A risk-based audit plan should track that map closely, directing coverage to where the institution itself says its risk is highest.
But here's the auditor's double duty. You use the risk assessment to scope, and you also test whether the risk assessment is accurate. If the map is wrong, every plan built on it inherits the error.
The FFIEC manual treats the risk assessment as the foundation of the whole program for exactly this reason.
Inherent risk vs. residual risk
- Inherent — risk before controls
- Residual — risk after controls do their work
- Controls reduce inherent risk toward residual
- Audit tests whether that reduction is real
Two terms anchor risk-assessment work, and the exam separates them carefully. Inherent risk is the risk that exists before any controls, the raw exposure from doing the business at all. Residual risk is what remains after the controls operate.
The controls are what move you from inherent down to residual. So a correspondent-banking line might carry high inherent risk, but strong controls could bring residual risk to moderate. The auditor's job is to test whether that claimed reduction is real, whether the controls the institution credits actually exist and actually work.
If residual risk is rated low but the controls behind it are weak, the residual rating is unsupported, and that's a finding.
What a defensible risk assessment includes
- All relevant risk categories and lines of business
- A clear, documented methodology
- Quantitative and qualitative inputs
- Refreshed for new products, geographies, and events
When you scope from a risk assessment, you first judge whether it's defensible. A sound one covers all relevant risk categories and lines of business, with nothing material quietly excluded. It uses a clear, documented methodology so the ratings can be reproduced rather than asserted.
It blends quantitative inputs, like transaction volumes and high-risk customer counts, with qualitative judgment about emerging threats. And it's refreshed when the business changes, a new product, a new geography, an acquisition, a regulatory shift, or a significant incident. A risk assessment that hasn't been updated in three years while the business transformed is stale, and a stale risk assessment misdirects both the program and your audit.
When the map and the audit disagree
- Audit may find risk the assessment understated
- Raise it: the risk assessment itself is deficient
- Don't just shrug and follow the stated scope
- Feed real findings back into the next risk assessment
Sometimes fieldwork reveals risk the assessment understated, a high-risk customer segment growing fast that the map still rates low, or a product whose monitoring coverage is thin. When that happens, the auditor doesn't just quietly stay within the originally scoped area. The mismatch is itself a finding: the enterprise risk assessment is deficient, because it failed to capture a risk the audit could plainly see.
And the relationship runs both ways. Real audit findings should feed back into the next risk assessment, sharpening the map for everyone. The exam likes scenarios where the right move is to challenge the risk assessment rather than treat it as gospel.
Risk categories the assessment must capture
- Products and services — cash, wires, trade, correspondent
- Customer types — PEPs, MSBs, cash-intensive businesses
- Geographies — high-risk jurisdictions and exposure
- Delivery channels — non-face-to-face, digital, third parties
To scope from a risk assessment, you need to know the categories a complete one must capture, because a gap in any category is unassessed risk. The standard lenses are products and services, with cash, wire transfers, trade finance, and correspondent banking carrying higher inherent risk; customer types, where politically exposed persons, money services businesses, and cash-intensive businesses raise the profile; geographies, including exposure to high-risk jurisdictions and cross-border flows; and delivery channels, where non-face-to-face onboarding, digital channels, and reliance on third parties add risk. The FFIEC manual frames the risk assessment around these kinds of categories.
When you audit or scope from a risk assessment, run down this list and ask whether each is genuinely covered. A risk assessment that thoroughly analyzes products but ignores the delivery channels through which those products are sold has a hole, and that hole becomes a blind spot in everything built on top of it.
Recap and next
- The enterprise risk assessment scopes the audit
- But audit also tests whether that assessment is accurate
- Inherent minus working controls equals residual
- Next — building the scope statement and objectives
Recapping: the enterprise-wide AML risk assessment is the primary driver of audit scope, but the auditor both uses it and tests it, because a flawed risk map misdirects everything built on it. Keep inherent risk, the controls, and residual risk straight, and remember that an unsupported residual rating is a finding. And make sure the assessment captures every risk category, products, customers, geographies, and channels, because a gap in any one is unassessed, uncontrolled risk.
In the next lecture, we turn that risk picture into a concrete engagement: the scope statement, the objectives, the resourcing, and how risk appetite shapes those choices. Test yourself on risk-assessment auditing first.
Sources
- FFIEC BSA/AML Examination Manual — BSA/AML Risk Assessment
- FATF Recommendation 1 — risk-based approach
- Basel Committee, Sound management of risks related to money laundering and financing of terrorism
Test your knowledge
A few CAMS-Audit questions on this material — pick an answer to see the explanation.
Q1. An auditor interviews the alert-review team leader, who asserts that all alerts are investigated thoroughly. The auditor records this and concludes the control is operating effectively. What is the MOST significant flaw?
Q2. After completing fieldwork, an auditor has a clear mental recollection of every test she performed and every conclusion she reached, but her workpapers are incomplete. What is the problem?
Q3. An auditor uses statistical sampling on 300 CDD files and finds a 4% exception rate. She concludes the overall population has a material deficiency and recommends remediation. Management argues the exceptions are isolated. Whose framing is more defensible, and why?
Q4. An auditor re-runs a sanctions-screening rule using the same name list and transaction data the system processed and compares the output to what the system actually produced. Which testing technique does this represent?
Ready to practice?
Put this lesson to work on real CAMS-Audit questions.
Drill the full CAMS-Audit bank →