CasePilot

AML business-wide risk assessment template, with worked entries

A business-wide risk assessment should explain where an institution is exposed, what its controls actually do and what remains uncertain. This copyable structure is a working aid, not a regulator-approved form.

What this template is — and is not

I use a business-wide assessment to connect the institution’s products, customers, channels and geographies to financial-crime exposure. It is different from a customer risk score, which assesses one relationship, and from a new-product assessment, which tests a proposed change before launch. The wider method is covered in How to write a risk assessment; this page focuses on the fields and the reasoning that make the document usable.

The exact categories and review triggers depend on the institution, its applicable jurisdiction and its policies. The FFIEC’s US examination manual describes a bank-specific assessment across products, services, customers and geographic locations, and says there is no required single format. That is useful reference material for a US bank, not a universal legal template.

Copyable structure

Template fields

  1. Scope and assessment period: entity, business lines, jurisdictions, date range and exclusions.
  2. Business inventory: products, services, customer types, delivery channels, payment corridors and third parties.
  3. Risk statement: what feature creates the exposure, how it could be exploited and what consequence could follow.
  4. Supporting exposure data: volumes, customer mix, geography, transaction patterns and known limitations of the data.
  5. Inherent risk and reasoning: exposure before relying on controls, with the evidence and assumptions stated.
  6. Controls: the preventive and detective measures mapped to each exposure.
  7. Control-effectiveness evidence: testing, quality assurance, alert outcomes, training records or other evidence; separate designed controls from tested controls.
  8. Residual risk and reasoning: what remains after the evidenced controls, including uncertainty.
  9. Owner and action: accountable owner, action, due date and dependency.
  10. Approval and review triggers: approver, decision date and events that require an update.

Worked illustrative entries

The figures below are invented to show the shape of an entry. They are not CasePilot statistics or a benchmark.

FieldIllustrative entry
Scope and periodExample payment institution; card acquiring and domestic transfers; 1 January–30 June 2026; Poland and Germany operations.
Exposure dataIllustrative six-month volume: 1.2 million transfers; 8,400 merchant customers; 11% cross-border. Data excludes disputed-card records for April, so that limitation remains open.
Risk statementRapid merchant onboarding and cross-border settlement could be used to move funds through a newly created business before ownership and expected activity are properly understood, creating money-laundering and fraud exposure.
Inherent riskHigh for the onboarding and settlement combination because the speed and cross-border element increase exposure. This is a reasoned illustrative judgement, not a prescribed rating.
Controls and evidenceOwnership verification, sanctions screening, transaction monitoring and enhanced review for selected merchants. Evidence: a sample QA review and current monitoring-test results; a missing April dispute extract means effectiveness is not fully evidenced.
Residual riskMedium-high, with uncertainty retained until the missing extract is reconciled and the next QA sample tests the cross-border segment.
Owner and actionHead of Financial Crime; reconcile the extract, document the impact and retest the segment; due 31 August 2026.
Approval and triggerApproved by the designated risk committee on 15 July 2026 in this example; revisit after a material product, customer, geography or channel change.

How to reason through each field

Start with what the business actually does, not a generic list copied from another firm. A card acquirer, a remittance provider and a wealth manager may all use the word “customer”, but their exposure is not interchangeable. Record the population and data source before assigning a rating.

Keep inherent risk separate from control effectiveness. “We screen sanctions” describes a control. It does not prove the control is complete, timely or effective. The evidence column should tell a reviewer what was tested, when, on what sample and with what limitations. An empty field is more honest than unsupported assurance.

Residual risk is not a mathematical answer that appears automatically after subtracting controls. It is the remaining exposure and uncertainty that decision-makers accept, mitigate or escalate under their own governance. If the evidence is incomplete, write that down rather than silently choosing a lower rating.

Common category mistakes

Sources and boundaries

For a US bank, the FFIEC BSA/AML Risk Assessment guidance describes bank-specific risk categories and explains why management chooses the format. Its examination procedures look for identification, analysis and updating when the risk profile changes. The FATF Recommendations provide an international standard, but local implementation and supervisory expectations still govern the institution’s duties.

CasePilot is a practice environment for judgement. It is not a certification, legal advice or a production risk-assessment system.

What matters: A useful assessment lets another person see the exposure, the evidence, the control limitations and the decision that follows.

Practise the work, not the theory

CasePilot puts you in the analyst’s seat with authored cases and decisions to defend.

Open CasePilot