Sanctions Screening Effectiveness
A sanctions screening effectiveness assessment tests whether systems and staff surface relevant potential matches, explain why alerts were raised or dismissed, and respond safely when rules or lists change. It focuses on a defined regime, data set, channel and decision process.
Test coverage and the information being screened
A useful review starts with the firm's exposure and screening policy: which customers, connected parties, transactions or other data are in scope, against which current lists and restrictions, and how often screening runs. It can examine whether list updates and data feeds are complete and timely, and whether names and relevant ownership or control information arrive in a form the system can use.
FCA findings published in May 2026 described gaps involving outdated lists, incomplete data coverage, name transformations, long or non-Latin names, and inadequate oversight of vendor configuration. A defined test set can help reveal such blind spots. Depending on scope, cases might include exact matches, spelling variants, multiple name elements, titles, and records changed after a list update. Testing should use appropriately governed data and retain evidence of what was tested and what happened.
Balance missed matches and alert burden
Matching thresholds involve trade-offs. A more sensitive setting may produce more alerts for analysts to resolve; a less sensitive one can miss relevant variations. Sanctions screening effectiveness work can examine how thresholds and rules perform against representative scenarios, whether false positives have consistent reasons, and whether potential matches are wrongly discounted. Alert outcomes should be supported by evidence that another reviewer can understand.
An initial discussion can review the list entry and customer or payment data used, the matching logic, analyst rationale, escalation path and final disposition. Changes to lists, data feeds, name handling, configuration or thresholds call for clear ownership, approval, testing and records. Firms also need to understand what happens if a feed or screening service is delayed or unavailable.
Define a practical review scope
A first conversation can clarify the jurisdiction, sanctions regimes, screening use case and concern to resolve. Relevant inputs might include policies, data and list-feed descriptions, configuration decisions, test cases, alert quality samples and change records. The intended decision could be to identify test gaps, unclear exclusions or threshold questions for the firm's accountable teams; review depth and any written output would be agreed beforehand.
OFSI guidance explains that the effect of a match depends on the specific sanctions and facts, and directs readers to current legislation. The assessment focuses on screening evidence and process; the firm retains its legal decisions and reporting duties.
Common questions
Does a screening assessment clear a potential sanctions match?
No. It can examine the system, evidence and decision process. Whether a restriction applies depends on current law and the specific facts, and must be determined by the responsible firm with appropriate legal support where needed.
How should a firm test its screening thresholds?
Use representative, controlled scenarios to assess both missed variations and the volume and quality of alerts. Record the rationale for thresholds, test outcomes, approvals and changes so accountable reviewers can understand the trade-offs.