Fictional parties with declared sectors and permitted HS-code scopes, plus routes and IMO numbers.
Trade-based money launderingTrade finance and TBML
Trade finance and TBML
test scenarios.
Generate fictional companies, banks, invoices, shipments, structured letters of credit and financing draws. Twelve case types plant over- and under-invoicing, business mismatches, duplicate financing and unexplained routing next to ordinary trade and explained exceptions, and the answer key gives the expected action for each.
Runs in your browser. Free plan, no account needed.
From the sample answer key
- case_key
- over_invoicing
- expected_action
- alert
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.
Goods, grades, quantities, prices, routes, transshipments and credit terms that tie together.
Supplied reference prices and fictional vessel/port restrictions the cases are measured against.
Expected action and evidence references for each case and payment.
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_trade_alerts · first rows
| case_key | expected_action | reason |
|---|---|---|
| over_invoicing | alert | Standard-grade goods are invoiced at 3.5 times the supplied fixture reference price without supporting explanation. |
| under_invoicing | alert | Standard-grade goods are invoiced at 20% of the supplied fixture reference price without supporting explanation. |
| business_mismatch | alert | A food retailer imports industrial measuring instruments outside its supplied declared business scope. |
| duplicate_financing | alert | Two full-value financing draws claim the same invoice, bill of lading and shipment without an installment agreement. |
| unexplained_routing | alert | An unnecessary distant transshipment port is added without a supplied commercial explanation. |
| listed_vessel | alert | The vessel IMO matches an active fictional screening restriction. |
| listed_port | alert | The discharge port matches an active fictional screening restriction. |
| dual_use_review | review | The supplied goods-risk register requests end-use review for this specific instrument specification. An HS code alone does not establish an export-control restriction. |
| ordinary_trade | no_alert | A shipment fits the business scope, fixture price, ordinary route and supplied screening records. |
| explained_price | no_alert | The higher invoice price exactly matches the supplied premium-grade reference and supporting certificate. |
| installments | no_alert | Two agreed 40%/60% draws finance one invoice; their total is the invoice value. |
| explained_routing | no_alert | A supplied port-closure notice explains the otherwise unusual transshipment route. |
Sample files
Small enough for the Free plan. Answer-key files are marked; keep them away from the system under test.
- invoices.csvInvoices · 1.5 KB
- shipments.csvShipments · 1.4 KB
- letters_of_credit.csvLetters of credit · 2.3 KB · Structured fixtures, not SWIFT MT700
- trade_payments.csvFinancing draws · 1.2 KB
- reference_prices.csvReference prices · 929 B
- expected_trade_alerts.csvExpected actions · 3.5 KB · Answer key: alert, review or no alert
Built for a repeatable test.
Test pricing rules
Over- and under-invoicing are measured against supplied reference prices, with a premium-grade control that should not alert.
Test document consistency
Business-scope mismatches, duplicate draws and routing exceptions need invoices, shipments and credits read together.
Balance alerts with controls
Ordinary trade, explained routing and documented installments check that rules do not over-alert.
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.
Where do the case types come from?
The broad indicator categories are informed by public FATF/Egmont trade-based money-laundering risk indicators and HMRC guidance on common techniques. The specific cases are synthetic benchmarks.
Are the letters of credit SWIFT messages?
No. They are structured fixture records with the fields needed for the cases, not SWIFT MT700 instruments.
Are the vessels and ports real?
Ports and vessels are fictional or illustrative, and restrictions are fictional test entries. Nothing here asserts that a real vessel, port or company is sanctioned.
How many cases can I generate?
The default pack has 24 cases. In the workspace choose case types, copies (up to 1,000 per case), currency and identity countries.
Other scenarios.
Generate your own.
Change the seed, volume and scenarios in the browser. Nothing is uploaded.