OFAC Screening Caveats

Important limitations of sanctions screening: no tool catches everything, screening is not a legal opinion, and strict liability still applies.

TL;DR

TL;DR: Screening has real limits: no automated tool catches every possible match, a screening result is not a legal opinion, and strict liability still applies. Screening reduces risk, it does not remove the obligation to comply.

No tool catches everything

Screening compares a counterparty against the SDN List and other data. It can miss a match when list data is stale, when a name is transliterated differently, or when a wallet address is new. A clean result is a strong signal, not a guarantee. Organizations should treat screening as one control among several, alongside policies, training, and human review of edge cases.

Screening is not legal advice

A screening tool reports whether a counterparty matches a list. It does not interpret the law, decide whether a specific transaction is lawful, or issue a license. Questions about whether a given activity is permitted should go to qualified counsel, not to a software result.

Strict liability still applies

Even with screening in place, OFAC liability remains strict: intent is not required, and penalties start at $356,000 per violation. Screening reduces the chance of a violation by catching matches before money moves, but it does not create a safe harbor that excuses failures elsewhere in the process.

Practical takeaway

Use screening on every transaction, keep the data current, fail closed on errors, and document results. sanctionsai.dev syncs its list data hourly and screens 19,218 SDN names and 947 OFAC-listed crypto wallets, which narrows, but never fully closes, the gap these caveats describe.