OFAC Screening Alert Fatigue
The operational problem of too many false positive alerts overwhelming compliance teams, leading to real matches being missed.
TL;DR
TL;DR: Alert fatigue happens when a screening tool produces so many false positive alerts that reviewers stop giving each one real attention, and genuine matches slip through. Tuning thresholds and scoring the results reduce the noise.
How fatigue builds
Every flagged name must be reviewed by a person before a payment can proceed. If the tool flags common names and harmless lookalikes at a high rate, reviewers spend their day clearing false positives. Over time they begin to assume every alert is noise, move faster, and pay less attention, which is exactly when a real match gets cleared by mistake.
Why it is a compliance problem
Fatigue converts a screening system from a control into a rubber stamp. The alerts are still generated, but the review that is supposed to catch true positives no longer works reliably. Under OFAC's strict liability standard, intent is not required, so a missed true positive is still a violation with civil penalties starting at $356,000.
Controls
- Raise the match threshold so only stronger candidates are flagged for review.
- Use a risk score to rank alerts so reviewers focus on the highest risk first.
- Separate wallets and accounts from name matches so the queue is only what matters.
A tool with a risk_score capability, such as sanctionsai.dev, helps teams prioritize instead of processing a flat, undifferentiated queue.