On October 5, 2026, the U.S. Department of the Treasury's Office of Foreign Assets Control (OFAC) published an Iran-related alert to foreign financial institutions conducting business with Iran, alongside an amended FAQ 156 and a batch of deletions from the Specially Designated Nationals (SDN) List. The alert formalizes OFAC's expectations of non-U.S. banks whose U.S. dollar correspondent or trade-finance activity touches Iran-adjacent payments.
Foreign banks with USD correspondent banking and Iran-linked transaction exposure must immediately update SDN screening to reflect the October 5, 2026 delistings and the amended FAQ 156, and assess institutional exposure to Iran-related transactions, or face civil penalties under the International Emergency Economic Powers Act (IEEPA) and 31 CFR Part 501, blocked transactions, and loss of USD correspondent access. OFAC sanctions operate on a strict-liability basis, with penalties materially reduced for voluntary self-disclosure.
What did OFAC change on October 5, 2026?
The release on OFAC's recent-actions page bundles three distinct items, and compliance teams should not treat them as one. The headline is the alert "Notice to Foreign Financial Institutions Conducting Business with Iran", a formal OFAC warning to non-U.S. banks about Iran sanctions risk in their correspondent and trade-finance flows. The second item is an amended Iran-related FAQ 156, which updates OFAC's published guidance on how the Iran sanctions program applies. The third is a set of SDN List deletions, not new designations.
The delisted entries are tagged under the IRAQ2 and SDNT programs, not Iran: IRAQ2 covers former Iraqi regime officials and entities from the pre-2003 sanctions, such as former ministers and Real Estate Bank officials, while SDNT covers Colombia narcotics-trafficking designees. They are operational bookkeeping, but they still require a screening refresh, so that cleared transactions no longer false-match parties OFAC has removed and any funds blocked solely on a now-delisted party can be released through the OFAC unblocking process.
| October 5, 2026 action | What it is | What compliance must do |
|---|---|---|
| Iran alert to foreign FIs | Formal OFAC warning to non-U.S. banks on Iran sanctions risk | Assess institutional Iran exposure across correspondent and trade-finance flows |
| Amended FAQ 156 | Updated OFAC guidance on the Iran sanctions program | Update screening logic, training and internal guidance |
| SDN List deletions (IRAQ2, SDNT) | Removals of old Iraq and Colombia-narcotics entries | Refresh screening lists; clear false matches; review blocked funds |
Which foreign banks are exposed to the Iran alert?
The alert is addressed explicitly to foreign financial institutions, and the exposure turns on U.S. dollar clearing. Any transaction that touches the U.S. financial system or a U.S. person implicates OFAC jurisdiction, which is why a non-U.S. bank processing an Iran-adjacent cross-border payment through a U.S. correspondent remains in scope. The directly exposed actors are foreign banks with USD correspondent banking and Iran-linked transaction exposure, sanctions and AML compliance teams at non-U.S. financial institutions, correspondent banks routing Iran-adjacent cross-border payments, and trade-finance banks handling Iran-related payments.
The 50 Percent Rule compounds the exposure: any entity 50 percent or more owned in the aggregate by blocked persons is itself blocked even if not separately listed, so screening logic must aggregate ownership, not just match names. Banks whose respondent relationships include institutions in jurisdictions with active Iran trade corridors face the highest residual risk.
What must compliance teams do, and how quickly?
The action is immediate. SDN list changes are effective on publication, and the alert is a live warning, so there is no forward compliance date to plan against. Sanctions and AML teams at exposed non-U.S. banks should treat the screening update and the exposure assessment as same-day work, not a scheduled quarterly task.
- Pull the October 5, 2026 SDN List update and refresh all screening engines, transaction screening, customer onboarding and correspondent-banking due diligence, so delisted IRAQ2 and SDNT parties no longer match.
- Read the amended FAQ 156 against your current Iran sanctions interpretation and update screening logic, internal guidance and front-line training wherever the guidance has shifted.
- Assess institutional exposure to Iran-related transactions across correspondent and trade-finance flows, prioritizing respondents and customers in jurisdictions with active Iran trade corridors.
- Review any funds or transactions previously blocked solely on the basis of a now-delisted party, and prepare OFAC unblocking requests where appropriate.
- Brief relationship managers in trade finance and correspondent banking on the alert's expectations before they handle the next Iran-adjacent payment.
What happens if a bank misses the screening update?
OFAC enforcement operates on a strict-liability basis: civil penalties attach without proof of intent, which is why a stale screening list is itself the violation, not just an operational gap. Penalties accrue under IEEPA (50 U.S.C. 1701-1706) and the Reporting, Procedures and Penalties Regulations at 31 CFR Part 501, with mitigation available for voluntary self-disclosure under 31 CFR Part 501, Appendix A.
Beyond the fine, the commercial threat for a foreign bank is loss of USD correspondent access. A single Iran-sanctions violation can lead a U.S. correspondent to terminate the relationship, cutting the bank off from dollar clearing. Blocked transactions remain frozen until OFAC authorizes unblocking, and a pattern of Iran-adjacent exposures that the alert warned about compounds both the penalty and the correspondent-risk consequence.
Next steps: confirm your screening vendor has ingested the October 5 SDN update, run a lookback against the delisted parties, document the FAQ 156 review against your internal guidance, and brief your correspondent-banking and trade-finance desks. Obsidian tracks OFAC actions per jurisdiction as they publish, so your team sees the next alert without rebuilding the watch.
