Platform · 04

Matched on who they are, not on what they typed.

Screening a raw registration string against a sanctions list produces false positives at a rate that trains reviewers to click through them. Normalise first, tier the result, and the queue becomes readable.

Dailylist refresh
TieredPEP results
On changere-screening

Three lists, three behaviours

They are not interchangeable

Sanctions

Behaviour
refusal
Refresh
daily

A match is a stop

A confirmed sanctions match ends the registration. There is no threshold at which an operator may proceed, so the platform does not offer one.

Consolidated lists, refreshed daily
Fuzzy matching on normalised identity, then confirmation
The matched list and entry are recorded against the check

PEP

Behaviour
review
Output
tier

A match is a risk tier

Political exposure is not wrongdoing. It raises the standard of diligence, which is a different instruction to a reviewer than 'refuse'.

Tiered by proximity, so a distant relative is not treated as the office-holder
The tier is returned; what it triggers is your policy
Re-tiered when the underlying role changes, not only at onboarding

Adverse media

Behaviour
context
Output
flags

A match is context

Returned as flags with sources, never as a verdict. Media is the weakest of the three signals and the platform treats it that way.

Sourced and dated, so a reviewer can judge the item rather than the label
Never sufficient alone to produce a fail
Excluded from the automatic decision unless your policy opts it in