Sanctions screening in practice: matching, alerts and when to re-check

Exact matching misses most of the risk

Watchlists are compiled from many sources, in many scripts, and your own customer data arrives in a different form again. The same person can appear as several different strings.

• Transliteration — an Arabic, Russian, Chinese or Urdu name written into Latin letters has more than one accepted spelling.
• Name order — given name and family name reversed or combined differently across documents.
• Patronymics, multi-part surnames, hyphenation, and maiden or married names.
• Diacritics dropped in one system and present in another.
• Legal-form noise in company names — 'Holdings', 'HoldCo', 'L.L.C.', and '&' versus 'and'.
• Ordinary typing errors in your own records.

A tool that only returns exact matches will therefore look quiet and be wrong. Look for phonetic, proximity and cultural matching, and for thresholds you can tune as your alert queue tells you what is working.

A hit is a question, not an answer

Screening produces an alert. What separates a real match from a coincidence is the identifiers you hold alongside the name.

• For individuals: date of birth, nationality, passport or ID number, and address history.
• For entities: country and date of incorporation, registration number, and known aliases or former names.
• Context: the role the party plays in the relationship, and the jurisdictions it operates in.

If you cannot compare those, you cannot resolve an alert properly. That is usually a data-collection problem in onboarding, not a problem with the screening tool.

Document the dismissal, not just the hit

For every alert you close, keep enough to explain it later:

• What the alert was, and which list and version produced it.
• Which identifiers you compared, and where they agreed or differed.
• Who made the decision, and when.
• What would reopen it — a new identifier, a change of address, a new listing.

Deleting an alert destroys the evidence that you looked. The written decision is what makes a false positive defensible.

A clean check has an expiry date

Lists are updated continuously, ownership and control links change, and a customer can become politically exposed after onboarding. Screening once at onboarding answers a question about a moment that has already passed.

Ongoing screening re-checks your live customer base as lists change. It is what catches the customer who was clean yesterday.

Screening and transaction monitoring are different controls

• Screening asks whether a party you are dealing with appears on a sanctions, PEP, enforcement or adverse-media record.
• Transaction monitoring asks whether activity looks unusual for that customer — amounts just under thresholds, unexpected corridors, a sudden change in volume.

A customer can pass screening and still be laundering. Transaction monitoring catches patterns that no list contains. ComplianceSuite covers screening, transaction monitoring and case management together, and we keep the two controls on separate pages so you can scope each one properly.

A workflow that survives an inspection

1. 1Screen at onboarding, before the relationship starts, and again before high-risk transactions.
2. 2Route alerts to a named reviewer who has the identifiers needed to resolve them.
3. 3Resolve on evidence, and write down the reasoning.
4. 4Re-screen the live customer base whenever lists change.
5. 5Keep the full trail — list version, alert, decision, decision-maker, date.