Sanctions Screening and OFAC Compliance
How firms check counterparties, clients, and trade instructions against government sanctions lists before money moves, and why a hit on the wrong list can freeze a transaction — or trigger criminal liability — in seconds.
Prerequisites: KYC and Customer Due Diligence
Before a bank or asset manager wires money, opens an account, or settles a trade, it has to answer a narrow but consequential question: is anyone in this transaction on a government sanctions list? In the US, the Office of Foreign Assets Control (OFAC) maintains the Specially Designated Nationals (SDN) list — individuals, companies, vessels, and countries that US persons are barred from dealing with. Similar lists exist from the UN, the EU, and the UK's OFSI. Getting this wrong isn't a paperwork slip; it can mean facilitating money laundering, terrorist financing, or transactions with a sanctioned government, and OFAC enforces strict liability — a violation counts even if the firm didn't know who it was really dealing with.
What screening actually checks
Sanctions screening runs names — of clients, counterparties, beneficial owners, and even instruction text in wire payments — through automated matching software against the current sanctions lists, before an account opens or a transaction settles. The matching is fuzzy on purpose: sanctioned parties routinely operate under name variants, transliterations, or shell companies, so software flags anything close to a listed name rather than requiring an exact match. That fuzziness is also the operational headache — common names like "Mohammed Ali" or "John Smith" generate a flood of false positives that a human analyst has to clear one by one, comparing date of birth, address, and other identifiers against the real listed entity before releasing the transaction.
A hit that can't be quickly cleared as a false positive gets escalated: the transaction is held, the compliance team investigates, and if the match is confirmed, the funds are typically blocked (frozen, not returned) or the transaction rejected, and OFAC must be notified within a set window. A frequent-trading desk with global counterparties will screen thousands of names a day; the whole system is only useful if the false-positive rate stays low enough that genuine matches don't get lost in the noise.
What this means in practice
For a quant fund trading globally, sanctions screening shows up at onboarding (screening every new counterparty and their beneficial owners), at the prime broker (which screens the fund itself and its investors), and at payment processing, where every outgoing wire gets checked before it leaves the building. Trading a name that later gets added to a sanctions list, or discovering a counterparty is a shell for a sanctioned entity, can force an unwind at a bad price and trigger regulatory reporting regardless of intent.
Sanctions screening matches every party in a transaction against government-maintained lists like OFAC's SDN list before money moves, and because OFAC liability is strict — intent doesn't matter — firms err heavily toward blocking ambiguous matches rather than risking a violation.
A common misconception is that sanctions and AML screening are the same control. AML screening looks for suspicious patterns of behavior (structuring, layering) that require judgment to spot; sanctions screening is a binary name match against a specific list, and a true hit must be blocked immediately — there's no "watch and see" option the way there often is with an AML red flag.
Further reading
- OFAC, Economic Sanctions Enforcement Guidelines (31 CFR Part 501, App. A)