Skip to main content
Promotional banner ad for the Penetration Testing Report Kit
AML/CFT Risk Assessment Audit Checklist for Internal AuditRegulatory Obligations Management
5 min readFor Internal Auditors

AML/CFT Risk Assessment Audit Checklist for Internal Audit

By Regulatory CouncilPublished

Is your institution's AML/CFT program still based on last year's business model? Recent enforcement actions have highlighted weaknesses across programs, from initial risk assessments to final remediation. These weaknesses can cascade: poor customer due diligence skews risk ratings, inaccurate ratings disrupt monitoring, and monitoring gaps undermine suspicious activity reporting.

This checklist helps your team test whether your risk assessment is dynamic, reflecting current business activities, and whether it connects to the necessary controls. Each item includes a done/not-done state and a description of what effective practice looks like.

Prerequisites

Before starting fieldwork, gather:

  • The current AML/CFT risk assessment and its approval history
  • Inventories of products, services, customers, channels, and geographies
  • Customer risk rating methodology and a sample of customer files
  • Alert, investigation, and SAR volumes by segment for at least the last review cycle
  • The independent testing scope and last report
  • The open findings log, including closed items from prior exams and audits
  • Any consent orders or institution-specific requirements that set review schedules

Separate institution-specific orders from general guidance. The FFIEC manual doesn't require continuous or fixed periodic updates of the BSA/AML risk assessment, but events like new products, customer types, or mergers can necessitate updates. Track the status of FinCEN's April 2026 proposed AML/CFT program rule and test whether your current triggers would meet its prompt-update requirement.

Checklist

1. The assessment covers the full risk universe. ☐ Done ☐ Not done
Ensure it addresses products, services, customers, transaction types, geographies, business lines, affiliates, and shared services. Regulators have specified this scope in corrective requirements.
Effective practice: Every product and business line in the current inventory maps to a risk conclusion, and terrorist financing exposure is addressed alongside money laundering, scaled to the institution.

2. The assessment describes today's institution. ☐ Done ☐ Not done
Compare the documented risk profile to actual business activities. Approval isn't the test. Check if transaction volumes align with assigned risks, if alerts concentrate in a lower-risk segment, and if customer activity changes without a rating update.
Effective practice: Differences between stated risk and observed activity are documented, investigated, and resolved by adjusting the risk conclusion, controls, or both.

3. Reassessment triggers are defined and used. ☐ Done ☐ Not done
Look for written triggers beyond the annual calendar: new products, geographic expansion, M&A or charter changes, shifts in customer mix, regulatory updates, advisories, and enforcement activity.
Effective practice: A documented process determines if a change materially affects risk, and you can show at least one trigger event that produced a decision, even if the decision was "no update needed."

4. CDD outcomes support the assigned risk rating. ☐ Done ☐ Not done
Sample customer files. Test whether the collected information, including beneficial ownership, supports the rating. Regulators found weaknesses across customer identification, beneficial ownership, ongoing and enhanced due diligence, customer risk ratings, and correspondent relationships.
Effective practice: File contents justify the rating, and higher-risk relationships receive enhanced due diligence that tracks changes in activity.

5. Risk ratings move when behavior moves. ☐ Done ☐ Not done
Trace a sample of customers whose activity changed materially. Did the rating and monitoring coverage change accordingly?
Effective practice: Rating changes are triggered by activity, documented, and visible to the monitoring function.

6. Significant risks map to monitoring controls. ☐ Done ☐ Not done
Perform a control objective mapping from each significant risk in the assessment to the scenarios, rules, thresholds, and coverage that address it. Regulators have cited weaknesses in scenarios, thresholds, data and system performance, alert backlogs, and documentation.
Effective practice: No significant risk lacks a monitoring control, and scenarios have been validated and tested, not just deployed.

7. Monitoring results feed back into the assessment. ☐ Done ☐ Not done
Check whether alert and SAR history is used to challenge risk assumptions. Concentrations by product, customer type, location, channel, or typology may signal changes.
Effective practice: A recurring review compares alert and SAR patterns to the assessment, and the minutes show assumptions being changed or reaffirmed with evidence.

8. Alert investigations and SAR filings are timely and documented. ☐ Done ☐ Not done
Review backlog aging, investigation documentation, and filing timeliness. Findings have shown management receiving reports of missed SAR filings over several years.
Effective practice: Backlogs are measured, escalated, and cleared within defined thresholds, and management reports surface late or missed filings immediately.

9. Staffing and expertise follow risk. ☐ Done ☐ Not done
Where higher-risk customers, activity, products, or geographies grew, did AML/CFT resources grow too? At smaller institutions, check if the BSA Officer has competing duties.
Effective practice: Management can explain why current resources remain appropriate, and training reflects the institution's actual risks.

10. Independent testing is scoped to risk. ☐ Done ☐ Not done
Test if the independent testing scope targets higher-risk areas and can detect weaknesses there. An October 2026 action linked ineffective independent testing to the failure to detect and remediate AML deficiencies on time.
Effective practice: Testing scope derives from the current risk assessment, and prior testing has found real issues rather than none.

11. The board and senior management receive meaningful reporting. ☐ Done ☐ Not done
Review governance reports for emerging risks, program performance, significant weaknesses, remediation status, and resource needs.
Effective practice: Reports drive decisions, and minutes show challenge, not mere acknowledgment.

12. Remediation fixes root cause and is validated. ☐ Done ☐ Not done
For each significant closed finding, separate evidence that the action was implemented from evidence that it works. Check for repeat findings.
Effective practice: Closure requires root cause identification, correction, effectiveness testing, and a decision on whether the issue changes risk elsewhere.

Common Mistakes

  • Treating approval as accuracy. A board-approved assessment can still describe a business you no longer run.
  • Auditing CDD for completeness only. A complete file can still produce the wrong rating.
  • Reading monitoring as a one-way street. If alert and SAR data never reach the risk assessment owner, the loop is open.
  • Accepting implementation as remediation. Closing on "action completed" without testing effectiveness is how findings return.
  • Assuming scale excuses gaps. The questions are the same at every size: do you understand your risk, do controls address it, and can you show they work?

Next Steps

Score the checklist, then rank not-done items by how many downstream controls they affect. Items 2, 4, and 7 usually carry the widest impact because they set the inputs for everything else. Share the results with the BSA Officer and the audit committee, and set a re-test date tied to remediation validation rather than the next annual cycle. Finally, add the FinCEN proposal to your regulatory change tracker and test your current triggers against its prompt-update expectation now, before it becomes final.

Promotional banner for the CUI buildout guide

You Might Also Like