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.
| Typology | CSH | RDC | ACH | WDM | WIN | RTP | P2P | COR |
|---|---|---|---|---|---|---|---|---|
| Cash structuring below the reporting threshold | 2 | not applicable | not applicable | not applicable | not applicable | not applicable | not applicable | not applicable |
| Rapid movement of funds | not applicable | not applicable | no scenario | 1 | 1 | no scenario | no scenario | not applicable |
| Money mules | not applicable | not applicable | no scenario | not applicable | not applicable | 1 | 1 | not applicable |
| Sanctions name screening | not applicable | not applicable | no scenario | 1 | 1 | no scenario | no scenario | no scenario |
| High-risk jurisdictions | not applicable | not applicable | not applicable | not applicable | 1 | not applicable | not applicable | no scenario |
| Missing originator or beneficiary information | not applicable | not applicable | not applicable | no scenario | 1 | not applicable | not applicable | no scenario |
| Correspondent and nested activity | not applicable | not applicable | not applicable | not applicable | not applicable | not applicable | not applicable | no scenario |
36 scenarios, 64 risks no scenario covers.
Tinted: covered, with the count. Hatched: no scenario, each one a risk. Dot: not applicable. 46 of 110 sectors covered, 1 channel dark, 10 finding types. The full chart runs below the paste box.
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.
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.
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.
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.