End-to-End AML Review Overview

An end-to-end AML/KYC review moves from intake to evidence-backed disposition. The sequence below keeps scope, sources, decisions and escalation in order.

1. Start the case #

Collect the basic case context:

customer or counterparty name;
individual / legal entity / legal arrangement / wallet / vessel / other;
requested product, service, transaction or relationship;
countries/geographies involved;
expected volume, value, frequency and purpose;
who requested the review;
deadline and business context.

2. Identify the subject #

Individual#

Collect and verify:

full legal name;
date of birth;
nationality or residence indicators where available;
ID document or reliable identity evidence;
address or contact information where required by policy;
occupation, employer, business activity or source of income where relevant.

Legal entity#

Collect and verify:

legal name;
registration number;
legal form;
registered address;
business activity;
directors / managers / authorised signatories;
ownership structure;
beneficial owners;
group structure where relevant.

3. Understand purpose and expected activity #

Ask:

Why does the customer need this relationship or transaction?
What is the expected activity?
Does the activity fit the customer profile?
Is there a clear economic or lawful purpose?
Does the activity involve higher-risk sectors, countries, products or delivery channels?

4. Run core screening #

At minimum, screen:

customer / counterparty;
beneficial owners;
directors / managers / signatories;
known connected parties;
payers and beneficiaries;
vessels, wallets, banks or other relevant objects where applicable.

Screening categories:

sanctions / TFS;
PEP;
adverse media;
geographic exposure;
sector or activity risk;
ownership/control complexity.

5. Review results #

For each hit or red flag, classify:

No match → document why cleared.
Possible match → collect more identifiers and review.
True match → escalate immediately.
Risk indicator → consider EDD or monitoring.
Suspicion indicator → escalate to MLRO / compliance owner.

6. Assign initial risk #

Use risk factors:

customer type;
beneficial ownership transparency;
geography;
product/service;
transaction pattern;
delivery channel;
PEP exposure;
sanctions exposure;
adverse media;
source of funds / source of wealth;
business activity and sector.

7. Decide CDD or EDD #

Apply standard CDD when the customer is understandable, risk is normal and no unresolved red flags exist.

Apply EDD when there is higher risk, such as:

PEP exposure;
high-risk geography;
complex or opaque ownership;
unusual transaction activity;
adverse media;
sanctions proximity;
unexplained wealth or funds;
high-risk sector;
crypto/VASP exposure;
trade-based money laundering indicators.

8. Collect additional evidence where needed #

EDD evidence may include:

source of funds documents;
source of wealth explanation and supporting evidence;
ownership chart;
corporate registry documents;
transaction documents;
invoices, contracts, shipment documents or proof of service;
independent media or database evidence;
blockchain tracing evidence for crypto cases;
management approval record where required by policy.

9. Make a documented recommendation #

Recommendation options:

Proceed — no material unresolved risk.
Proceed with monitoring — risk exists but is understood and controlled.
Request more information — evidence is insufficient.
EDD required — higher-risk case needs deeper review.
Escalate to MLRO — suspicion, serious red flag or unresolved high-risk issue.
Reject / exit — risk is outside appetite or cannot be mitigated.

10. Build the evidence pack #

Evidence pack should contain:

case summary;
subject identifiers;
documents reviewed;
screening screenshots or logs;
source links;
red flags found;
red flags cleared;
risk rating rationale;
decision matrix used;
recommendation;
escalation memo if applicable.

11. Final output format #

AML Review Result

Subject:
Purpose:
Risk rating:
Checks completed:
Key findings:
Red flags:
Cleared alerts:
Outstanding issues:
Evidence collected:
Decision:
Recommended next action:
Source basis:
Prepared by:
Date:

12. Golden rule #

The analyst does not need to prove crime. The analyst needs to identify whether the facts create risk, unresolved concern or suspicion requiring escalation under the AML process.

13. Optional KYB/EDD step: digital infrastructure exposure #

For corporate customers and counterparties with meaningful online presence, the analyst may add a Digital Jurisdiction Exposure check.

The check reviews public DNS and email infrastructure records to identify visible providers, email relays, DNS dependencies and jurisdictional references. The result should support the KYB/EDD narrative, not replace standard sanctions, PEP, UBO, adverse media or source-of-funds checks.

Related article: Digital Jurisdiction Exposure

14. Practical verification controls #

A complete AML review should not rely only on documents or declarations supplied by the subject. The analyst or reviewer should:

1. list declared facts in a declared-data inventory;

2. decide which facts require independent source verification;

3. record exact source checks and search inputs;

4. capture evidence during the review;

5. log mismatches and missing information separately;

6. map findings to risk factors and escalation triggers;

7. prepare a review-ready case file rather than an unsupported narrative.