What if the match is not against an OFAC list?
First, you should contact a lawyer specializing in sanctions law as quickly as possible. Actions must be strategically planned: from gathering documents and preparing a delisting petition to communicating with OFAC. A legal analysis of the reasons for inclusion should be conducted, and a defense strategy should be developed, which includes requesting clarifications from OFAC (Request for Information) and, if necessary, submitting a petition for delisting (Delisting Petition). It is also important to cease all operations that could violate the sanctions regime to avoid additional sanctions or criminal liability.
Not every screening alert is an OFAC hit. Sanctions screening software typically checks names against several different watchlists simultaneously, and each list has its own legal basis, its own administering agency, and its own required response. Treating every alert as an OFAC match — and automatically freezing funds or filing an OFAC report — is itself a compliance error that can create unnecessary friction with legitimate customers and partners.
FBI Most Wanted
A match against the FBI Most Wanted list reflects a domestic criminal law enforcement matter, not a sanctions designation. There is no OFAC blocking obligation. The appropriate response is to escalate internally per your institution’s AML/BSA policy and, where a genuine match is confirmed, coordinate with law enforcement rather than treasury compliance.
INTERPOL Red Notice
A Red Notice is a request for international law enforcement cooperation regarding an individual wanted for prosecution or to serve a sentence — it is not a U.S. sanctions designation and does not, by itself, trigger an OFAC blocking requirement. Red Notices can also be contested or politically motivated; institutions should apply enhanced due diligence rather than automatic account restrictions. For clients affected by a Red Notice itself, see our Interpol representation services.
BIS Entity List
The Entity List is maintained by the Commerce Department’s Bureau of Industry and Security under the Export Administration Regulations (EAR) — a separate legal framework from OFAC’s Treasury-administered sanctions. A match restricts specific export, re-export, and transfer activities involving the listed party rather than triggering a blocking/freezing obligation. See our export controls guide for how EAR restrictions differ from OFAC sanctions.
Department of State Sanctions
Certain sanctions programs — including some terrorism-related and foreign terrorist organization (FTO) designations — are administered by the State Department rather than OFAC, under separate statutory authority. A match here should be routed to the agency identified in the alert, following your institution’s escalation matrix for State Department programs specifically.
FinCEN 314(a)
A 314(a) match is an information request, not a sanctions or blocking list. Financial institutions receiving a 314(a) match are required to search their records for the specified individual or entity and report back to FinCEN within the timeframe specified in the request — typically without freezing the account or notifying the subject. Confusing a 314(a) hit with an OFAC match can lead to improper account restrictions. See our FinCEN compliance services for more on 314(a) obligations.
EU/OFSI Lists
EU sanctions lists and the UK’s OFSI Consolidated List operate under entirely separate legal regimes from OFAC — a person delisted in one jurisdiction may remain designated in another, and vice versa. A match here requires analysis under EU or UK law specifically, not U.S. sanctions law. Businesses with EU or UK nexus should treat this as a distinct compliance question — see our EU Sanctions Lawyer and UK Sanctions Lawyer (OFSI) pages.
Which of the following is the response you should take if a hit is against a list other than an OFAC list?
If the match is against a list other than an OFAC sanctions list, follow your institution’s compliance procedures and contact the agency responsible for that list if necessary. Do not automatically report every non-OFAC hit to OFAC — misrouting a non-OFAC match as an OFAC report can trigger the wrong regulatory process, delay resolution, and, in some cases, disclose account information to the wrong authority.
