What is an acceptable false positive rate?

What a false positive means in sanctions screening and how to think about an acceptable rate.

TL;DR

TL;DR: A false positive is a legitimate counterparty flagged as a sanctions match. There is no single universally acceptable rate: the goal is to minimize false positives while never letting a true match through. No industry-standard figure is documented here.

What a false positive actually is

In sanctions screening, a false positive occurs when a clean name or address matches a list entry by coincidence: a common name, a shared string, or a transliteration difference. The cost is friction: a legitimate payment is paused for review, and a real customer waits. The opposite failure, a false negative, means a blocked party passes the check, which carries penalties starting at $356,000 per violation.

Why there is no magic number

An acceptable rate depends on volume, data quality, and tolerance for friction. A high-volume payment processor and a small NFT drop have very different thresholds. Because OFAC is a strict liability regime, the bias should favor catching true matches over squeezing the false positive rate to zero. Any precise industry average is not documented.

How to drive false positives down without missing hits

The practical levers are a current, well-structured list and a check that resolves entities, not just raw strings. agentmail screens against 19,218 SDN names and 947 OFAC-listed crypto wallets across 16 jurisdictions, synced hourly, returning clean (ALLOW) or flagged (BLOCK) in under 100 ms. Keeping the list fresh and the match logic conservative is the reliable way to keep false positives low and true positives caught.