Operation Economic Outcast: Five Sectors, Three Compliance Decisions
Primary lensTrade policy
Sub-topicPolicy monitoring
Evidence base15 records used
Use casePolicy monitoring
The five sectors are not a five-sector blocked list
Operation Economic Outcast did not turn aviation, digital assets, gold, shipping, and technology into five blocked industries. Treasury added those sectors to the grounds it may use for future determinations, while separately naming nearly 60 entities, individuals, and vessels and suspending five authorizations until further notice. For compliance teams, those are different events: one changes who is blocked today, another widens future designation or correspondent-account sanctions exposure, and a third creates two licensing clocks, one for wind-down only and one for wind-down or maintenance.
The package creates three different compliance states
Compliance teams need to sort the August 24 package into three separate decisions.
Legal state
What changed
Immediate file
Blocked now
OFAC named nearly 60 entities, individuals, and vessels under several authorities.
Screen the published names and identifiers, plus entities directly or indirectly owned 50 percent or more in the aggregate by one or more blocked persons under OFAC's ownership rule.
Designation risk
Treasury may now designate a person for operating in one of the five sectors; for knowingly engaging, on or after January 10, 2020, in a significant transaction for the sale, supply, or transfer to or from Iran of significant goods or services used in connection with one of those sectors; for supporting a person blocked under E.O. 13902; or for ownership, control, or agency ties to such a blocked person. Sector contact alone does not make the person blocked.
Record the counterparty's role, ownership, transaction facts, and evidence of significance. Use "blocked" only when a designation, status rule, or ownership rule supports it.
Authorized wind-down or maintenance
OFAC suspended five Iran authorizations, issued General License BB for a short wind-down, and issued LNR-specific General License AA for stated wind-down and maintenance activity.
Identify the authorization, permitted activity, conditions, and applicable September 8 or October 23 deadline.
A screening match, a possible designation theory, and a license decision belong in separate fields. A company may pause a transaction because of unresolved risk, but that internal hold should not be recorded as an OFAC block.
Sector exposure still requires a person and conduct
The relevant theory depends on the party's role under E.O. 13902. A carrier may raise an operating-in-the-sector question; a vendor may raise a goods-or-services question; and a bank may be reviewed for the transaction it facilitated. Each conclusion requires its own evidence.
Section 1(a)(ii) supplies one route: Treasury may determine that a person knowingly engaged, on or after January 10, 2020, in a significant transaction for the sale, supply, or transfer to or from Iran of significant goods or services used in connection with a listed sector. Section 2 does not itself impose blocking sanctions. It authorizes Treasury, after determining that a foreign financial institution knowingly conducted or facilitated a qualifying significant financial transaction on or after January 10, 2020, to prohibit the opening, or prohibit or impose strict conditions on the maintaining, of a U.S. correspondent or payable-through account for that institution.
For the narrower question whether goods or services used in connection with a sector are significant, FAQ 833 says Treasury may consider the totality of the facts and circumstances. The factors can include value, frequency, commercial purpose, management awareness, patterns of conduct, blocked-person involvement, the effect on the order's objectives, and deceptive practices. The FAQ does not separately define the significant transaction element in section 1(a)(ii) or the significant financial transaction element in section 2.
Two order-level exceptions also belong in the file. E.O. 13902 does not apply to a person for conducting or facilitating a transaction for the provision, including any sale, of agricultural commodities, food, medicine, or medical devices to Iran. It also does not prohibit transactions for the conduct of official United Nations business by UN employees, grantees, or contractors. Those exceptions do not independently authorize conduct prohibited by the Iran regulations or another sanctions authority.
The five labels do not yet supply five definitions
The new determination names the sectors but does not define them. That leaves a real boundary problem around terms such as technology and digital asset.
OFAC handled earlier E.O. 13902 sectors with more detail. FAQ 831 defines construction, mining, manufacturing, textiles, and finance. FAQ 832 describes goods and services used in connection with those sectors. As of August 24, those pages do not provide equivalent definitions for the five new sectors.
A sanctions team should not fill that gap with a NAICS code, a marketing description, or a country-of-incorporation rule and call the legal question closed. The working record should state the proposed sector classification, the facts supporting it, and the definition still awaited from OFAC. A technology service used by an Iranian airline may raise more than one theory, but multiple plausible theories are not the same as a published determination.
The same discipline applies to Treasury's statement that countries will receive defined timelines to close identified Iran-related activity. The public package reviewed for this analysis does not list those countries, the activity identified for each one, or the deadlines. A direct request from Treasury to a foreign government could affect a company's risk assessment. The public announcement, however, gives private companies no country list or deadline to implement.
September 8 is a licensing deadline, not the sector effective date
The sector determination took effect on August 24. September 8 belongs to a different part of the package.
OFAC's suspension notice suspended three regulatory authorizations and Iran General Licenses F and G until further notice. The affected activities concern certain third-country educational activity, noncommercial personal remittances, conferences, sports exchanges, and academic exchanges. General License BB allows transactions ordinarily incident and necessary to wind down activity previously authorized by one or more of those five provisions through 12:01 a.m. EDT on September 8.
The license is not permission to start a new underlying activity. The file has to show the prior authorization and why the closing step is ordinarily incident and necessary to wind-down. If a payment goes to a blocked person, GL BB requires it to be placed in a blocked interest-bearing account in the United States in accordance with the Iran regulations. Other prohibitions remain in place unless separately authorized.
As of August 24, the eCFR still showed the pre-suspension text dated August 20. A rules engine fed only from the codified text could therefore continue approving activity that OFAC had already placed into wind-down. Until eCFR catches up, the August 24 suspension notice supplies the operative change.
There is also no single deadline for every August 24 authorization. General License AA authorizes transactions otherwise prohibited by E.O. 13902 that are ordinarily incident and necessary either to wind down a transaction or to maintain operations, contracts, or other agreements in effect as of August 24 involving La Nivernaise De Raffinage SAS, or an entity it owns directly or indirectly 50 percent or more, through 12:01 a.m. EDT on October 23. GL AA does not authorize transactions involving any other person blocked under E.O. 13902, or any other transaction prohibited by that order, unless separately authorized. Importing the September 8 date into that file would be as wrong as importing October 23 into the suspended-license file.
Why this is new: one matrix, not one ban
Build the review around individual counterparties and transactions, not a list labeled "five banned sectors."
Use this header as the working file:
Counterparty and activity
Screen timestamp and list version
Ownership result
E.O. 13902 route
Sector and conduct evidence
Current legal status
Prior authorization
Wind-down authority and deadline
Operational disposition
Owner and reopen trigger
[Name and transaction]
[Time and list]
[Direct and aggregate ownership]
[Operator, transaction, support, ownership/control/agency, or FFI]
[Facts and source]
[Legal classification]
[Provision or license]
[Authority, cutoff, conditions]
[Release, hold, wind down, or block]
[Owner, date, trigger]
Attach the screening evidence, ownership record, governing authority, and dated approval to each row.
Keep legal status separate from the company's operational decision. The status field should say: blocked now under an identified authority, status rule, or ownership rule; authorized wind-down or maintenance under a stated license; designation or correspondent-account sanctions exposure only; or no current blocking basis found after screening the applicable sanctions lists, ownership chain, Government of Iran or Iranian-financial-institution status, and relevant authorities. Record E.O. 13902 designation risk and section 2 correspondent-account risk separately. The disposition field should record what the company will do: block, wind down, hold for further review, or proceed with controls. If company policy is stricter than the legal result, say so directly.
First, rescreen active counterparties, vessels, financial intermediaries, and ownership chains with Iran, sector, payment, or routing exposure against the August 24 SDN List update, including third-country parties. Preserve the list version and time of the check.
Second, inventory activity that may connect to aviation, digital assets, gold, shipping, or technology in Iran. Separate operating in a sector from supplying goods or services to it and from financing a transaction. Send ambiguous sector classifications to the named decision owner rather than converting them into automatic blocks.
Third, find every open transaction that relied on 31 CFR 560.544, 560.550, 560.554, Iran GL F, or Iran GL G. For any proposed closing step, document the former authorization, the wind-down necessity, the payment route, and the September 8 cutoff. Keep GL AA wind-down or maintenance transactions in a separate October 23 queue.
Fourth, record foreign-government outreach as monitoring evidence until an operative public instrument or a direct legal obligation reaches the company. Do not invent a country list from Treasury's general statement.
Benchmarks to watch
Reopen the matrix when OFAC publishes a rule or definition, adds a designation, changes a license, or establishes a relevant enforcement record. Each event could alter the sector classification, a counterparty's status, or the deadline governing a transaction.
Enforcement actions will also show how Treasury applies "operating in," "significant goods or services," and facilitation to the five new sectors.
Caveats
Private government outreach may exist even though the public package supplies no country-by-country schedule. OFAC may also designate a person without prior notice, so a company can impose a stricter hold while an issue is unresolved. The record should identify that as a policy decision, not as a current blocking determination.
For U.S. persons, the existing Iran regulations still apply. For now, the operational instruction is narrower than the campaign language: screen the named parties and their ownership chains, document the relevant conduct, and place each authorization on its own deadline.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.