If this is your first time here, take a look at our FAQ page and get a sense of our unique scope of coverage by perusing the Research System interface.
Also, please note that this website is not yet fully functional on mobile browsers. We recommend adjusting your mobile browser settings to view the site in Desktop Mode.
If this is your first time here, take a look at our FAQ page and get a sense of our unique scope of coverage by perusing the Research System interface.
Ed. Note: if you’re new to TURBOFAC, please take note that the text string filtration function generally shouldn’t be used for terms such as “ordinarily resident,” “causing” or “new debt”. For research on the meaning of words and phrases such as those, i.e. terms central to the key legal issues in sanctions law that appear on a cross-programmatic basis, you’re typically better off locating and checking the appropriate box in the “Key Legal Issues” search category, which will limit the results to those that have been manually assessed as being relevant for the interpretation of the terms at issue.
Try typing your search term (“ordinarily resident,” “new debt,” or something else) in the “Find a Search Filter” box at the top of the page, and the corresponding “Key Legal Issues” check box will pop up instantly, if one exists. Once you check the box (e.g. “new debt,” with ~55 results), you can always use the text string filtration function to further refine your search (e.g. by typing “invoice” and narrowing the ~55 results to ~10).
Note in addition that the same applies to text string searches such as “14071” (if you’re looking for items related to EO 14071). By typing “14071” in the “Find a Search Filter” field up top, you will be able to instantly narrow the results down to items manually assessed as relating to EO 14071. Ditto terms such as “515.204” or “Iran General License G” (try the “Discrete Legal Provision” search category).
Please contact [email protected] or [email protected] with any questions on search results and efficiency.
Please click "Apply Text String Filters" again after clicking the "Close" button immediately below.
1) Prior to the 2013 issue of EO 13599 (blocking all property and interests in property of the Government of Iran), Irasco was not a blocked party. Nevertheless, the sanctions in place at the time were such that the Government of Iran and all entities owned or controlled by the Government of Iran were ineligible to receive services from the U.S (560.410(b)). The Italian company "caused" an export of financial services to Italy, but where OFAC also considers that export of financial services to have reached Iran given that "the benefit of services performed anywhere in the world on behalf of the Government of Iran is presumed to be received in Iran" (560.410(b)). OFAC considers money transfers for the direct or indirect benefit of an Iranian entity, including the GOI, to fall within the scope of 560.204/560.410.
"The term Government of Iran includes (a) The state and the Government of Iran, as well as any political subdivision, agency, or instrumentality thereof; (b) Any entity owned or controlled directly or indirectly by the foregoing." This is an example of an "indirect" export of services to Iran.
Legally speaking, then, the theory of liability is unusually convoluted as Intesa Sanpaolo "caused" a U.S. person to indirectly export a financial service "to Iran," by causing a transfer to an entity in Italy owned by the GOI.
2) Intesa Sanpaolo was fined nearly $240m by New York regulators for, among other issues, sanctions violations not addressed by OFAC. Many of the violations cited, however, appear to have been likely permissible pursuant to the then-in-force U-turn general license for Iran.
See https://www.acfcs.org/news/323529/New-York-regulator-penalizes-Italian-bank-nearly-240-million-on-alert-failures-cavalier-attitude.htm
3) Diligence expectations related to dealings with entities that are blocked for being "controlled" by the Government of Iran:
It is prohibited for U.S. persons to export services to Iran where they have a "reason to know" about the destination of such services. Having a "reason to know" about a specific fact or circumstance is, in turn, interpreted to turn on the question of whether a person subject to sanctions prohibitions did or did not meet OFAC's due diligence expectations, given the facts and circumstances. See 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). When this case is read in conjunction with Intesa Sanpaolo S.p.A. (2013) (penalizing an Italian bank for routing USD payments through the U.S. for an entity meeting the definition of "Government of Iran"), one has a better sense of where the line is for having a "reason to know" that a given entity meets the definition of "Government of Iran." In Intesa Sanpaolo, OFAC fined a non-U.S. bank for having "failed to identify [a private Italian entity called] Irasco as meeting the definition of the GOI" in a situation where OFAC considered that the bank should have known about the GOI connection. In that case, the red flags identified by OFAC were the ostensibly private Italian entity’s "ownership and line of business as an exporter of goods to Iran, and its financial and commercial associations with Iranian state-owned financial institutions, companies, and projects."
In United States v. Alavi Found., in contrast, there was a situation where U.S. person entities had been operating in the United States for about 13 years before the U.S. government determined that they were indirectly "controlled" by the Government of Iran. In that case, the entities and persons linked to the GOI had gone to great lengths to conceal the fact that they were operating on behalf of the Iranian Government. Given that no publicly announced enforcement actions were issued in connection with that case, and that hundreds of U.S. person entities, including banks and commercial tenants, had technically "exported services" to Iran by dealing with the GOI-controlled U.S. person entities, it is probably safe to assume that OFAC did not consider any U.S. person counterparty to transactions with the GOI-controlled U.S. entities to have had a "reason to know" about such GOI control. It is possible that OFAC had issued cautionary letters and/or findings of violations in connection with such dealings, but there were no actual penalties issued.