AML screening false positives: why they happen and how to reduce them
An AML screening false positive is an alert generated by a sanctions, PEP, or adverse-media match that, on review, turns out not to be the customer at all. Traditional name-only screening generates around 99.5% false positives industry-wide, and for a Canadian reporting entity that noise is not a minor inconvenience, it is the single biggest driver of alert fatigue, missed real risk, and reviewer cost. This guide explains why false positives happen, what they cost a compliance program, and the concrete ways to bring the rate down without loosening controls.
A false positive in AML screening is an alert that names your customer but is not actually about them. It happens when a sanctions, PEP, or adverse-media match surfaces on the strength of a shared name, a similar spelling, or a coincidental data overlap, rather than a genuine identity match. For a Canadian reporting entity running sanctions and PEP screening as a mandatory control, the false-positive rate determines whether that control is sustainable at scale or whether it quietly buries a small number of real risks inside thousands of alerts nobody has time to review properly.
Why AML screening produces so many false positives
Four causes account for most of the noise a screening program generates.
- Homonyms. Common names appear on sanctions and PEP lists just as they appear in the general population, so a name-only match can flag hundreds of unrelated people who happen to share it.
- Transliteration and spelling variants. Names transliterated from non-Latin scripts routinely produce several accepted English spellings of the same listed person, and fuzzy matching tuned to catch all of them catches unrelated names too.
- Thin identifying data. A customer or list record with no date of birth, no address, and no secondary identifier forces the match to run on name alone, which is the least reliable signal available.
- Static, one-size thresholds. A single match sensitivity applied across an entire customer book ignores that some segments genuinely need tighter scrutiny and others are being flagged for no added protection.
The cost of unresolved false positives
A high false-positive rate is not just a workload problem. Reviewers facing thousands of low-value alerts develop alert fatigue, and fatigue is what causes a genuine match to get cleared on autopilot along with the noise around it. It also distorts examiner confidence: a compliance program that cannot explain why 99% of its alerts were false is harder to defend as risk-based and effective, which is the standard Bill C-12 set for every FINTRAC-regulated program. The team's real capacity, meanwhile, gets spent clearing duplicates instead of investigating the genuine edge cases that actually carry risk.
How entity resolution reduces false positives without dropping true matches
The fix is not to loosen matching, which trades false positives for missed true hits. It is to resolve identity more precisely before an alert ever reaches a reviewer. Agentic entity resolution scores identity coherence across candidate matches, collapsing near-duplicate hits caused by spelling variants, transliterations, and homonyms into a single scored identity, and is designed to cut false positives by up to 80% as a result. This works because it distinguishes a genuine, if imperfectly spelled, match from a coincidental homonym, rather than simply widening or narrowing a match-sensitivity dial. Every hit that survives resolution still carries a plain-language rationale, so the reduction in volume does not come at the cost of losing the explainability an examiner would expect.
Practical steps a compliance team can take today
- Enrich the data behind the match, not just the matching logic. A record with relationships, roles, and context gives resolution something real to work with; a bare name does not.
- Move from batch to continuous screening. Batch re-screening produces alert spikes every run; continuous monitoring spreads the same volume into a steady, prioritized queue.
- Apply risk-based thresholds, not one global setting. Tune sensitivity to the risk rating of the segment being screened, in line with the risk-based approach your risk assessment already sets out.
- Keep the rationale attached to every disposition. A cleared alert with no recorded reasoning is indistinguishable from one nobody actually reviewed.
How BriteBase approaches this problem
BriteBase runs sanctions, PEP, and adverse-media screening through one entity-resolution engine rather than three disconnected tools, so the same resolution logic that clears a sanctions duplicate also clears the equivalent noise in PEP and adverse-media matches. The detail on how each list type is handled is on the screening software page, and the product itself sits on the AML screening solution page.
FAQ
What causes most AML screening false positives?
Homonyms, transliteration and spelling variants, and thin identifying data behind the customer or list record. A common name alone can generate dozens of alerts, and a record with no date of birth or address forces matching to rely on name alone, which is the least reliable signal available.
How high is the industry false-positive rate?
Traditional name-only screening generates around 99.5% false positives industry-wide, meaning the large majority of alerts a manual review queue processes are noise rather than genuine risk.
Does reducing false positives mean loosening controls?
No. Loosening match thresholds trades false positives for missed true matches. Entity resolution instead scores identity coherence to distinguish a genuine, if imperfectly spelled, match from a coincidental homonym, so the reduction comes from precision rather than permissiveness.
How much can false positives realistically be reduced?
BriteBase is designed to cut false positives by up to 80% through agentic entity resolution, without dropping true risk, and while keeping a plain-language rationale attached to every hit that survives resolution.
Does batch or continuous screening produce more false positives?
Batch re-screening produces large alert spikes every time it runs, since an entire customer book is matched against updated lists all at once. Continuous monitoring applies resolution to each change as it happens, producing a steadier, more manageable queue instead of periodic floods.
Sources
Cut screening noise without losing coverage.
Book a demo and we will show you agentic entity resolution clearing false positives in real time, with a plain-language rationale on every hit that remains. No retainers. No hourly rates.
Book a demo