OFAC FAQ (Current) # 48 - Blocking and Rejecting Transactions

Date issued: Jan. 30 2015

Last substantive commentary amendment:
Apr. 02 2024

TURBOFAC Commentary (266 words)

Notes:

1) Consult the enforcement action module of the Research System to search for enforcement actions dealing specifically with diligence failures occurring subsequent to having initially received a "match," "hit" or other similar flag.

2) This FAQ is most notable for use of the term “reasonably close match,” in a context which appears to map onto OFAC’s standards for determining when one has a “reason to know” of facts giving rise to a potential violation. See generally General Note on the Terms "Knowingly," "Should Have Known" And "Reason to Know" In the Primary Sanctions, Secondary Sanctions and Derivative Designation Contexts (System Ed. Note). In other words, where one encounters a “reasonably close match.” There is an expectation to do further diligence. When the match is not “reasonably close,” there is no expectation to interdict and investigate (assuming no other sanctions-implicating facts other than the name).

3) The FAQ is also notable for the suggestion that that, unless a U.S. person holding property is sure that there is a blockable interest in property, the property should not actually be blocked until the factual question concerning the blockable interest has been resolved (in consultation with OFAC or otherwise). (“Unless you have an exact match or are otherwise privy to information indicating that the hit is a sanctions target, it is recommended that you do not actually block a transaction without discussing the matter with OFAC.”) This is further evidence that the blocked property reporting requirements operate such that the 10-day block begins once the determination has been made that there is a blockable interest in property.