On September 10, 2026, the U.S. Treasury's Office of Foreign Assets Control (OFAC) released a three-part Iran package under Operation Economic Outcast: an immediate hardening of its Iran-specific licensing policy to a presumption of denial, 19 new Specially Designated Nationals (SDN) additions across the counter-terrorism and Iran programs, and a $1,427,230 enforcement settlement against an individual who advised an Iranian software company. The change is effective immediately, and every component reaches compliance teams with Iran exposure or a USD-clearing nexus.
The analytical core is the licensing shift. OFAC's Iran-related specific licensing policy has been modified so that Iran-specific license applications are now considered with a presumption of denial, except as required by law or in narrow circumstances such as risk to life, limb, or environmental safety. For any organization holding or planning an Iran-specific license, the burden has inverted: a grant is now the exception, not the baseline expectation.
What changed in OFAC's Iran licensing policy?
The amendment concerns specific licenses, the case-by-case authorizations OFAC issues for otherwise prohibited transactions, not the standing general licenses in 31 CFR Chapter V. Before September 10, 2026, an Iran-specific license application was adjudicated on its merits; the policy now starts from denial and grants only where law compels or where life, limb, or environmental safety is at stake.
Compliance teams with an active Iran-license strategy should treat the change as a live portfolio risk. Pending applications may face denial where the old posture would have allowed negotiation, and any reliance on a forthcoming specific license for Iran-related activity should be re-underwritten against the new presumption. OFAC encourages affected parties to subscribe to its Recent Actions feed for further updates.
Who must screen the 19 new SDN designations, and what about the 50 Percent Rule?
OFAC added 19 SDN entries: 14 individuals and 5 entities. Sixteen are designated under the SDGT counter-terrorism program (Executive Order 13224, as amended by Executive Order 13886), and three under the Iran program (Executive Order 13902). The additions cluster around three nodes: Kata'ib Hizballah and broader Hizballah networks in Iraq and Lebanon, the Zaher El Dine facilitation network, and the Dubai-based Shams and Bahr Trading Company, an "other monetary intermediation" firm designated under IRAN-EO13902.
| Program tag | Authority | Designees added | Secondary sanctions |
|---|---|---|---|
| SDGT | EO 13224, amended by EO 13886 | 16 (12 individuals, 4 entities) | Yes, section 1(b) |
| IRAN-EO13902 | EO 13902 | 3 (2 individuals, 1 entity) | Per program authorities |
Screening is not optional and not forgiving. OFAC operates under strict liability: civil penalties attach without proof of intent, and every listed entry must be run against counterparty, beneficial-ownership and transaction-screening systems immediately. The 50 Percent Rule compounds the reach: any entity 50 percent or more owned, in the aggregate, by one or more blocked persons is itself blocked even if it never appears on the SDN List. The two Dubai-based individuals and the Shams and Bahr exchange are the signal to trace ownership chains through the United Arab Emirates, Iraq and Lebanon, not just the named parties.
For foreign persons, the secondary-sanctions exposure under section 1(b) of EO 13224, as amended by EO 13886, means material support to any of the SDGT designees can trigger designation even absent a U.S. nexus. USD clearing remains the other hook: any transaction touching the U.S. financial system or a U.S. person brings the conduct into OFAC jurisdiction.
What does the $1,427,230 settlement signal for Iran compliance?
Alongside the policy and designations, OFAC announced that an individual agreed to pay $1,427,230 to settle potential civil liability for providing management consulting and advisory services to one of Iran's leading software solutions companies, receiving Iranian-origin dividends into U.S. bank accounts, and acquiring real property in Iran. The full enforcement release sets out the facts.
| Element | Detail |
|---|---|
| Settlement | $1,427,230 |
| Conduct | Consulting and advisory services to an Iranian software company; Iranian-origin dividends to U.S. bank accounts; real property in Iran |
| Determination | Egregious; not voluntarily self-disclosed |
| Partner agency | FBI, Los Angeles Field Office, Orange County Resident Agency |
Two features matter for practitioners. First, the matter was deemed egregious and was not voluntarily self-disclosed; voluntary self-disclosure can materially reduce a penalty under 31 CFR Part 501, Appendix A, and its absence here is part of why the settlement reads as a deterrence signal. Second, the conduct is services and dividends, not goods: advising an Iranian company and routing Iranian-origin proceeds through U.S. accounts was enough. Compliance programs that focus sanctions screening on shipments and counterparties but not on professional-services revenue, dividend flows, or foreign real-asset holdings should close that gap.
Continuous, per-jurisdiction real-time monitoring surfaces an SDN addition or a licensing-policy shift the moment OFAC publishes it, so a team screens against today's list, not yesterday's.
Subscribe to the free newsletter
What should compliance teams do next?
Three immediate steps: re-baseline any pending or planned Iran-specific license application against the presumption of denial; push the 19 new SDN entries, their aliases and identifiers into screening systems today, then trace 50 Percent Rule exposure through ownership chains, especially the United Arab Emirates, Iraq and Lebanon; and brief sanctions, treasury operations and front-office teams that services revenue, Iranian-origin dividends to U.S. accounts, and Iranian real property are now an enforced enforcement pattern, not a theoretical one.
