AML Scenario Gap Finder
For whoever answers the examiner's question: which scenario covers this risk

Paste your AML scenarios. See which money-laundering risks no scenario covers.

AML Scenario Gap Finder reads your transaction monitoring scenario list as it stands in the inventory. Paste your transaction monitoring scenario list. Get every scenario placed against the money-laundering typology it detects and the obligation it answers, quoted and cited; the channels and products with no scenario for the typologies they carry; thresholds set above the reporting threshold; sanctions screening running in batch where a payment should be stopped before it leaves; duplicate scenarios to put to the model owner; and scenarios with no owner or no review inside 12 months.

What it reads. It reads the scenario list you paste, in your browser. Nothing is stored until you save.

What it does not. It does not read transactions and does not tune thresholds: it shows which risks and channels your scenarios reach, and which they do not.

Read your own scenario listEight scenarios free, no account. A published dictionary of 50 typologies and the obligation text load with the page; every placement runs in your browser.
Specimen: an invented community bank7 of the 45 typologies that apply to its 8 channels
TypologyCSHRDCACHWDMWINRTPP2PCOR
Cash structuring below the reporting threshold2not applicablenot applicablenot applicablenot applicablenot applicablenot applicablenot applicable
Rapid movement of fundsnot applicablenot applicableno scenario11no scenariono scenarionot applicable
Money mulesnot applicablenot applicableno scenarionot applicablenot applicable11not applicable
Sanctions name screeningnot applicablenot applicableno scenario11no scenariono scenariono scenario
High-risk jurisdictionsnot applicablenot applicablenot applicablenot applicable1not applicablenot applicableno scenario
Missing originator or beneficiary informationnot applicablenot applicablenot applicableno scenario1not applicablenot applicableno scenario
Correspondent and nested activitynot applicablenot applicablenot applicablenot applicablenot applicablenot applicablenot applicableno scenario

36 scenarios, 64 risks no scenario covers.

2coveredno scenario·not applicable

CSH Cash, branch and ATMRDC Remote deposit captureACH ACH and direct entryWDM Domestic wiresWIN International wiresRTP Real-time paymentsP2P Person-to-person paymentsCOR Correspondent accounts

46 of 110 sectors covered, 1 channel dark, 10 finding types. The full chart runs below the paste box.

Two colleagues at a conference table working through ring binders of printed files
Go into the exam knowing which risks your monitoring reaches and which it leaves open, with the rule behind every sector quoted and cited. It works from the scenario inventory you already keep, so there is no rule engine to license, no transaction file to hand over and no consultant's matrix to wait weeks for.
01

Paste the list as it comes out of the rule engine

One scenario per line: the name alone, or with any of id, threshold, lookback, frequency, channel, segment, last reviewed, owner, alerts and SARs. Each is placed on one of 50 published typologies in twelve groups: an id like STR-01 or HRG places it first, the wording second, and a scenario that matches nothing is marked unplaced and never guessed.

02

Read the coverage chart

Typology by channel, for the channels you tick as offered. A sector a scenario reaches is tinted with the count; a sector no scenario reaches is hatched; a sector where the typology does not apply is left blank. Every sector links to the typology page and the obligations behind it.

03

Take the exam pack to the model owner

Ten findings in fixed order, each with the scenarios it names, the obligation quoted from the Bank Secrecy Act, the FATF Recommendations, the Australian AML/CTF Act or the OFAC framework, and the question to put to the model owner.

One scenario per line: Scenario, or ID | Scenario | Threshold | Channel | Owner, or a CSV export with a header row. Tabs, pipes, commas or double spaces. A first line such as type: community bank | countries: US, AU | channels: cash, ACH, wires | segments: PEP | as at: 2026-09-24 sets the institution, the regimes, the channels you offer and the date.
Nothing is sent anywhere until you choose to save.
Countries (the regimes whose obligations are quoted)
Channels and products you offer (the columns of the chart)
Segments named for enhanced measures

Why a coverage chart and not a tuning engagement

Monitoring platforms sell a continuous layer to institutions that can buy one. The BSA officer at a community bank, a credit union or a payments company still answers the examiner from a spreadsheet of scenarios beside a vendor rule engine. Before anyone retunes a line, somebody has to show which typology each scenario reaches, on which channel, and where nothing does. That is the chart this builds, in your browser, from the list as it stands.

The dictionary is ours and published in full: every typology in twelve groups, the channels each one applies to, what each kind of institution usually runs and the obligations each regime attaches. It reads the scenario list only: no transaction, no alert, no customer record, and it passes no judgement on how well a scenario works.

AML scenario coverage: the questions examiners ask

What does AML Scenario Gap Finder do?

It reads your transaction monitoring scenario list as it stands and shows which money-laundering risks no scenario covers. Each scenario is placed against the typology it detects and the obligation it answers, quoted and cited. It also shows the channels and products with no scenario for the typologies they carry.

Does it read my transactions or tune my thresholds?

No. It does not read transactions and does not tune thresholds; it shows which risks and channels your scenarios reach, and which they do not. It reads the scenario list you paste, in your browser, and nothing is stored until you save.

What is a typology in this tool?

There are 50 published typologies in twelve groups, such as cash structuring below the reporting threshold, rapid movement of funds, money mules, sanctions name screening, high-risk jurisdictions, missing originator or beneficiary information, and correspondent and nested activity. Each scenario is placed on one of them, an id like STR-01 or HRG placing it first and the wording second. A scenario that matches nothing is marked unplaced and never guessed.

Which regimes does it quote?

It quotes the Bank Secrecy Act and its regulations (31 CFR Chapter X), the FATF 40 Recommendations and Recommendation 16 on payment transparency, the Australian Anti-Money Laundering and Counter-Terrorism Financing Act, and the OFAC framework for sanctions compliance commitments. The countries you tick decide whose obligations are quoted. Where the page names an obligation without stating its requirements, it says so and does not state them.

Can it be used by tranche 2 firms?

Yes. There is a separate tranche 2 tool for lawyers, conveyancers, accountants, real estate agencies, trust and company service providers and dealers to read their list of AML/CTF checks. The main chart is aimed at banks, credit unions, payments companies and remitters. Both read a pasted list in your browser.

What does it flag about thresholds?

It flags thresholds set above the reporting threshold, so a scenario that will not fire where the obligation expects it becomes visible. It does not tell you what to set the threshold to; that stays with the model owner. The finding states the obligation and the question to put to them.

What does it say about sanctions screening?

It flags sanctions screening running in batch where a payment should be stopped before it leaves. The obligation behind it is quoted from the regime you ticked, such as the OFAC framework. The finding is a question for the model owner, not a ruling.

Is it free?

Eight scenarios can be read free with no account. A published dictionary of 50 typologies and the obligation text load with the page, and every placement runs in your browser.

What does the coverage chart show?

The chart is typology by channel, for the channels you tick as offered. A sector a scenario reaches is tinted with the count, a sector no scenario reaches is hatched, and a sector where the typology does not apply is left blank. Every sector links to the typology page and the obligations behind it.

What does it flag about owners and review?

It brings back scenarios with no owner or no review inside 12 months. It also flags duplicate scenarios to put to the model owner. A finding names the scenarios it covers and the question to put to them.

What should I do with the output?

Take the exam pack to the model owner, since the ten findings run in fixed order and quote the obligation behind each. It is built from the scenario inventory you already keep, so there is no rule engine to license and no transaction file to hand over. It passes no judgement on how well a scenario works.

What do I need to paste?

One scenario per line: the name alone, or with any of id, threshold, lookback, frequency, channel, segment, last reviewed, owner, alerts and SARs. A CSV export with a header row works too. A first line such as type, countries, channels, segments and as at sets the institution, the regimes, the channels you offer and the date.

What this does, and what a spreadsheet, a consultant or an AI assistant does better

A spreadsheet is better for keeping the scenario inventory as the working record, with the columns, thresholds and notes your team maintains, and no dictionary is needed to read it. A compliance consultant or lawyer is better on whether a scenario is adequate for your institution's risk and on how a regulator would read it, and can advise on tuning the model itself. A general AI assistant is better for drafting the narrative that accompanies the scenarios or the response to an examiner's question. What this does that they do not is place each pasted scenario on a published typology, draw the typology-by-channel coverage chart, and return the risks and channels with no scenario, the thresholds above the reporting threshold and the duplicate or unreviewed rows, quoting the obligation behind each finding; it reads the scenario list and never the transactions, does not tune thresholds, and passes no judgement on how well a scenario works.

Primary source: FATF