Fictional people, companies, banks, vessels and test locations, with aliases and programme markers.
Sanctions screeningSanctions screening
Sanctions screening
test data.
Test name and payment screening against a fictional watchlist. ScenarioLoom plants matches in names, bank BICs, cities, vessel IMO numbers and free-text remittance, using aliases, typos, word-order swaps and Chinese-character, pinyin and Cantonese variants, plus near misses that should not hit.
Runs in your browser. Free plan, no account needed.
From the sample answer key
- field
- debtor_name
- variant
- alias
- expected_hit
- true
Generated fixture · seed scenarioloom-sample
What you getInputs and answers,
Inputs and answers,
kept apart.
Source records go to the system you are testing. The answer key stays with you, so you can compare results afterwards.
Ordinary payments plus planted hits and near-miss controls across debtor, creditor, agent BIC, city, remittance and vessel fields.
For every payment: the field and XML path, list entry, variant type, expected hit and the values compared.
SDN XML, SDN/ADD/ALT CSV and ISO 20022 pacs.008 messages, generated from the same records.
A sample, generated by ScenarioLoom.
Seed scenarioloom-sample, anchor date 2026-11-01. Open the setup to change the volume, scenarios or format; the same settings always reproduce these files.
expected_matches · first rows
| payment_id | field | variant | expected_hit | list_value | payment_value |
|---|---|---|---|---|---|
| P000001 | debtor_name | alias | true | Lee & Lewis 002 | Lee-&-Lewis-002 |
| P000003 | creditor_name | alias | true | Prime Capital 012 | Prime-Capital-012 |
| P000004 | intermediary_agent_bic | exact | true | OLAMBR40XXX | OLAMBR40XXX |
| P000005 | creditor_city | near_miss | false | Testport 025 | Testport 025son |
| P000006 | creditor_name | exact | true | Lee & Lewis 002 | Lee & Lewis 002 |
| P000011 | creditor_agent_bic | exact | true | KTEWHK80XXX | KTEWHK80XXX |
| P000013 | debtor_agent_bic | near_miss | false | OLAMBR40XXX | ZKSTBR40XXX |
| P000018 | intermediary_agent_bic | near_miss | false | MJLZFR20XXX | TLOGFR80XXX |
Sample files
Small enough for the Free plan. Answer-key files are marked; keep them away from the system under test.
- fictional-sdn.xmlWatchlist (SDN XML) · 19.2 KB · Follows OFAC’s published SDN XML schema; every entry is fictional
- payments-pacs008.xmlPayments (pacs.008 XML) · 74.2 KB · Input for your screening system
- payments.csvPayments (CSV) · 18.3 KB
- expected_matches.csvExpected matches · 8.0 KB · Answer key: field, list entry, variant and expected hit
Built for a repeatable test.
Check fuzzy matching
See which variants your engine catches: aliases, adjacent-letter typos, spacing, initials, accents and transliterations.
Count false positives
Near-miss controls are deliberately different identities, so hits on them show where matching is too loose.
Test every payment field
Hits are placed in agent BICs, intermediary BICs, cities and remittance text, not only party names.
Scope. These are fictional, seeded test fixtures. Expected outcomes define a synthetic benchmark, not a legal or compliance determination about any real party, and they are not a substitute for practitioner review. Use them in isolated test environments.
Common questions.
Does it use the real OFAC, UN, EU or UK lists?
No. The watchlist is entirely fictional and no live lists are fetched, so you can share fixtures without handling real designations. The exports follow the published OFAC file formats so your loaders can ingest them.
What does the answer key say?
Each payment has one planned case: the field and XML path where the value appears, the list entry it relates to, the variant type, whether a hit is expected, and the list and payment values.
Are the BICs and IMO numbers real?
They are synthetic. BICs use a test marker in the eighth position, and vessel IMO numbers have valid check digits. Synthetic identifiers can coincide with real ones, so keep fixtures in test systems.
Can I change the volume and fields?
Yes. In the workspace choose the watchlist size, payments, hits, controls, currency, the fields that may carry hits and the variant types.
Other scenarios.
Generate your own.
Change the seed, volume and scenarios in the browser. Nothing is uploaded.