Introduction

Where standard AML training runs out

Most AML training programmes were built for a world of names, accounts, and correspondent banking relationships. That training isn't wrong, the underlying skill, recognising a pattern inconsistent with a stated profile, still applies. But a genuinely crypto-touching case exposes gaps that standard training simply doesn't cover, and an analyst who's never had those gaps named tends to discover them under pressure, mid-investigation, rather than beforehand.

This part names the gaps directly.
Gap 01

Fiat training assumes a bank in the middle

Traditional AML training is built around the assumption that value moves through regulated intermediaries, banks, payment processors, each capable of holding, delaying, or refusing a transaction. Part 4 already covered the structural consequence of this assumption breaking down in crypto: a firm often can't simply decline an incoming on-chain transaction the way a bank can decline to open an account. An analyst trained purely on "when in doubt, block the transaction" hits a genuine procedural wall the first time they're looking at value that's already landed in a wallet the firm controls, with no equivalent "return to sender" option available.

Gap 02

Identity and ownership don't map the way KYC training assumes

Standard KYC training teaches verifying who a customer is. Crypto adds a second, separate question standard training rarely addresses with any depth: whose wallet is this, actually. A customer can pass every identity check and still control multiple wallets under different guises, or conversely, a wallet address alone tells you nothing about who controls it without additional attribution work, clustering, exchange deposit tagging, or off-chain intelligence. An analyst trained to think "identity verified, case closed" misses that wallet-level attribution is a distinct, ongoing task, not something settled once at onboarding.

Gap 03

"Clean history" means something different on-chain

In fiat AML, a clean transaction history over time is genuinely reassuring. On-chain, a wallet's history can look clean simply because the tooling in use doesn't have visibility into activity on other chains, or because funds arrived via a bridge or mixer that severed the traceable link to their origin, not because the funds are actually clean. An analyst applying fiat intuition, "nothing's flagged, therefore it's fine", is applying a standard that doesn't transfer.

Gap 04

The pace is faster than the review cycle

A suspicious fiat transaction typically allows some window for review before it settles irreversibly. On-chain finality is often near-immediate. This changes what "acting quickly" actually means in practice, and it's a big part of why OFSI specifically flagged retrospective discovery, catching a sanctioned transaction only after better analytics tools became available, as a recurring, reportable failure pattern among UK crypto firms, covered in Part 4. Standard training rarely prepares an analyst for a case where the review window has already closed before the review even starts.

Gap 05

Standard training doesn't teach you to read a wallet graph

This is the most concrete, learnable skill gap, and arguably the easiest one to actually close. Reading a cluster of connected wallets, spotting a peel chain, recognising a tightly-knit group of addresses trading only with each other, none of this is covered in a typical AML certification course, and all of it is a genuinely learnable, practical skill once someone's shown what to look for. Part 3 of this series covered the underlying typologies directly.

Closing

Closing this gap deliberately, not by accident

None of the five gaps above get closed by reading about them once. They get closed by working through cases that force the decision the way a real one would, which is the entire premise behind Scenario Lab's KYC and Sanctions Investigation module: building an actual ownership tree, screening entities in sequence, and making a disposition call against a case that's specifically designed to test whether a clean surface result gets treated as the end of the analysis or the start of it. If any of the five gaps above sound familiar from your own experience, that's a reasonable place to test the actual skill, not just read another paragraph about it.

Put it into practice
Test the five gaps in Scenario Lab's KYC and Sanctions Investigation module
Free, no login. Build an ownership tree, screen entities in sequence, and make a real disposition call.
Open Scenario Lab →
This closes Part 5 of the series
Part 6 goes deeper into the specific mechanics of where wallet screening logic itself tends to break down, address clustering, mixing, and cross-chain visibility gaps.
Quick Reference
The training gap between AML certification and a real crypto case, cheat sheet summary Summary card listing five gaps between standard AML training and crypto-touching casework, plus a pointer to Scenario Lab's KYC and Sanctions Investigation module, for the Crypto Guide Part 5 guide. The Training Gap, At A Glance FIVE GAPS — CHEAT SHEET THE FIVE TRAINING GAPS 1 No bank in the middle to block it 2 Identity verified ≠ wallet control 3 "Clean" history isn't always clean 4 Finality outruns the review cycle 5 Wallet graphs aren't taught CLOSE THE GAP DELIBERATELY Scenario Lab's KYC and Sanctions Investigation module is built to test exactly these five gaps: build an ownership tree, screen in sequence, and make a real disposition call. A summary aid, not a substitute for the full guide or professional advice. fincrimeradar.org