Guided product tour
Adjudicate a sanctions screening hit
Six steps, no account, nothing to install. Each step is its own page, so you can send a colleague a link to the part that matters and it will open exactly there.
Every name, list and identifier in this walkthrough is invented. SAMPLE SUBJECT 001 is not a person, SPECIMEN SANCTIONS LIST is not a real list, and none of these panels is a screenshot — they are drawn with the same components the application is built from.
Where a true match goes instead
And if the evidence had confirmed the match?
A confirmed match does not close. It opens a case that carries the screening evidence with it, gathers the customer, ownership and transaction context around the same subject, and — where the facts support it — becomes a report to the NFIU with the validation evidence of the submission retained alongside it.
Escalation path
Sample data- Confirmed matchThe hit stays open and is escalated rather than closed. The screening evidence travels with it.
- Case opened on the subjectCustomer profile, ownership, identity evidence and transaction context gather around one subject rather than one alert.
- Investigation and reviewNotes, linked evidence and an approval path appropriate to the decision being made.
- Report to the NFIUWhere the facts support it: generated from controlled mappings, validated before submission, with the validation evidence retained.
Why it matters. The screening hit, the case and the filed report are one chain of custody over a single subject, not three systems that have to be reconciled by hand.
Start the tour again or read how screening is built in the platform documentation.
After the tour
The same walkthrough, against your own list configuration
A specialist runs this on the lists your policy puts in scope, at the threshold your committee approved, with the customer types you actually onboard.