False positives are the biggest operational cost in sanctions screening.
Learn why sanctions screening false positives happen and how better matching, context fields, evidence records, and review workflows can reduce manual workload.
Why false positives happen
Common names
Many sanctioned individuals have highly common names (e.g., 'John Smith' or 'Mohamed Ali'). Without context, every matching name flags.
Transliteration variations
Names translated from Cyrillic, Arabic, or Han scripts to Latin characters have multiple valid spellings.
Missing context
Screening a name without a Date of Birth or Country prevents the system from ruling out obvious mismatches.
Weak matching thresholds
Legacy systems relying on simple Levenshtein distance or soundex algorithms produce too much noise on short names.
Stale list data
Using outdated sanctions lists means you might flag entities that have been delisted or cleared by regulators.
Partial name overlap
A person whose middle name matches a sanctioned entity's surname might trigger a flag in naive systems.
How to reduce false positives
Provide Date of Birth
DOB adds important disambiguation evidence. A date-of-birth, country, or identifier conflict is evidence for identity assessment. It must not silently clear or confirm a candidate.
Provide Nationality or Country
Including country of residence or registration adds context for identity assessment. Its materiality depends on the screening engine and candidate evidence.
Use Entity Identifiers
Whenever possible, screen using national IDs, passport numbers, or LEIs, which provide definitive matches.
Specify Entity Type
Always declare if you are screening a 'person' or an 'entity' to prevent companies from matching with individuals.
Leverage Source Evidence
Use a system that provides per-field confidence breakdowns so your team can quickly understand why a match occurred.
Implement Human Review
Use policy to prioritize candidates for review. An analyst disposition, not a low score alone, establishes that a candidate is a false positive.
How Verifex helps manage noise
We design our screening infrastructure to help you confidently reduce false positives while maintaining strict regulatory compliance.
candidate and identity assessment
Verifex preserves candidate and identity evidence so your team can assess ambiguous results without silently discarding a candidate.
Context-aware scoring
Advanced context-aware matching and scoring signals weigh the statistical probability of a match based on field rarity and data quality.
Common-name guardrails
Built-in caps prevent highly common names from achieving critical risk scores without corroborating context.
Evidence Capsules
Every match provides transparent, per-field confidence contributions so reviewers can inspect the reasoning.
Frequently Asked Questions
What is a false positive in sanctions screening?
A false positive occurs when the screening system flags an individual or entity as a potential sanctions match, but upon review, they are found to be a different person or entity with a similar name.
What is an acceptable false positive rate?
There is no single industry-standard figure — published false-positive rates in sanctions screening vary widely by data quality, matching configuration, list scope and how an alert is defined. 'Acceptable' depends on your risk appetite, the quality of your customer data, and your regulatory environment. Rather than target a headline percentage, measure your own rate consistently and watch whether disposition stays fast, consistent and reviewable; a persistently high rate is a signal to tune matching or improve data collection, not a number to chase down at the expense of recall.
How do context fields reduce false positives?
Context fields such as date of birth and country provide evidence for identity assessment. A date-of-birth, country, or identifier conflict is evidence for identity assessment. It must not silently clear or confirm a candidate.
What happens when a false positive is flagged?
The transaction or onboarding is typically paused while a compliance analyst manually reviews the alert. They inspect evidence, confirm the mismatch, mark it as a false positive in the audit log, and release the block.
Explore the full platform
Sanctions API
Global sanctions screening with structured confidence.
Matching Methodology
How our engine calculates match confidence.
Evidence Capsule
Append-only, hashed audit records for every screen.
Continuous Monitoring
Watch entities and get alerts on list changes.
Stop drowning in false positives.
Upgrade to an intelligent screening API that understands context and provides clear evidence.