By SanctionsAI team · Updated 2026-08-09

How to handle false positive sanctions alerts

False positives account for 90%+ of sanctions screening alerts. A structured workflow ensures you dismiss them correctly.

Alert disposition workflow

Alert typeReview deadlineDisposition criteria
Exact SDN matchImmediate (block)Treat as true positive until proven otherwise
Name similarity1 hourCompare DOB, address, nationality, ID
Fuzzy match4 hoursCompare all identifying fields
Jurisdiction flag24 hoursVerify route and counterparty location

False positive criteria

Document WHY the alert does not match: different DOB, different nationality, different address, different occupation, entity type mismatch.

Tuning to reduce false positives

Calibrate fuzzy match thresholds, build exclusion lists for common names, add secondary identifiers, segment by risk tier.

Never auto-dismiss: Every alert must be reviewed by a human. Auto-dismissal is a top OFAC enforcement finding.

Screen your agent's next payment

Check any wallet, name, or entity against OFAC, EU, UN sanctions lists in real time.

Free wallet checker

Frequently Asked Questions

What is the false positive rate?
Initial: 90%+. With tuning: 5-10%.
Can I auto-dismiss false positives?
No. Every alert must be reviewed and documented by a human.
How do I reduce false positives?
Calibrate thresholds, add secondary identifiers, build exclusion lists, segment by risk.
How long must I keep alert records?
At least 5 years per OFAC and FinCEN requirements.

← Back to how-to · SanctionsAI