OFAC Sanctions Afghanistan
A Dubai-based logistics firm processed payment for an Afghan freight forwarder in January 2026. OFAC screening flagged the recipient as a Taliban-linked entity under Executive Order 13224. The transaction was blocked, triggering a mandatory filing requirement within 10 business days—miss that window and you’re looking at a separate violation stacked on top of the original penalty, potentially exceeding $377,700 per violation.
What Legal Exposure Do U.S. Persons Face Under Current Afghanistan Sanctions?
Unlicensed transactions with designated persons trigger both criminal and civil liability. Civil penalties reach the greater of $356,579 per violation or twice the transaction value under the International Emergency Economic Powers Act (IEEPA). Criminal violations: fines up to $1 million and up to 20 years imprisonment for willful breaches under 50 U.S.C. § 1705.
The Taliban received SDGT designation under Executive Order 13224 on July 2, 1999, reimposed following their August 2021 return to power. The Haqqani Network carries dual designation—SDGT under E.O. 13224 (September 2012) and FTO under INA § 219. Both trigger automatic asset freezes and transaction prohibitions for all U.S. persons: individuals, corporations, branches, and foreign subsidiaries that are 50% or more U.S.-owned.
OFAC enforces strict liability. Intent doesn’t matter for civil penalties; reckless disregard or negligent failure to screen suffices. The 2023 OFAC Enforcement Guidelines do offer some relief for voluntary self-disclosure, remedial steps, and effective compliance programs—but only if you catch the violation yourself. OFAC discovers it during an exam? No voluntary disclosure credit, period.
When a transaction involves a blocked person, you must freeze property and file a report within 10 business days via OFAC’s online system. Failure to block or file constitutes separate violations with independent penalties. For Afghanistan deals, that blocking obligation covers funds, goods in transit, and accounts receivable if the counterparty is on the SDN List or owned 50%+ by someone blocked.
OFAC Sanctions Afghanistan
Our team specialises in cases with an international element. We review applicable treaties, assess risks, and prepare an action plan.
Contact a lawyer →OFAC Afghanistan Sanctions vs. Comprehensive Country Embargoes: What’s the Difference?
| Sanctions Type | Afghanistan (Targeted) | Iran/Cuba (Comprehensive) | Compliance Requirement |
|---|---|---|---|
| Geographic scope | No country-wide prohibition; transactions allowed with non-blocked Afghan persons | Nearly all transactions prohibited regardless of counterparty | Screen counterparty + verify ownership structure |
| SDN List screening | Mandatory for all transactions; must screen individuals, entities, and 50% ownership | Mandatory; additional sectoral lists apply | Daily list updates; document all screening |
| General Licenses | GL 14-20 authorize humanitarian aid, legal services, basic needs support (31 CFR 594/597) | Limited carve-outs for food, medicine; most require Specific License | Verify GL applicability; maintain compliance records |
| Specific License applications | Available for commercial transactions if no blocked person involvement | Rarely granted; policy presumption of denial | 30-60 day processing; detailed justification required |
| Civil penalty range | $356,579 per violation or 2× transaction value | $356,579 per violation or 2× transaction value | Same statutory maximum; settlement rates vary by program |
Afghanistan’s targeted sanctions create far more compliance friction than comprehensive embargoes. Under comprehensive sanctions, you avoid nearly all transactions with a sanctioned country. Afghanistan requires you to pick and choose: lawful business is possible, but only after confirming no Taliban, Haqqani, or other SDN involvement. That means granular counterparty due diligence and ownership verification on every deal.
General Licenses 14 through 20 (31 CFR parts 594 and 597) authorize specific Afghanistan activities without individual license applications. GL 20 permits humanitarian assistance and activities supporting basic human needs, including transactions with Taliban-controlled Afghan government entities when necessary to deliver aid. Legal services, telecommunications, and personal remittances under $400 per month also qualify.
Specific License applications demand detailed transaction descriptions, end-use certifications, and policy justifications. OFAC evaluates them under a presumption of denial for Taliban-related transactions unless humanitarian grounds or critical policy objectives apply. Expect 30-60 days for processing; OFAC may request more documents or deny without explanation.
How to Screen Transactions Against the OFAC SDN List for Afghanistan
OFAC publishes the Specially Designated Nationals (SDN) List daily at 8:00 AM EST in PDF, XML, and CSV formats. It includes Taliban officials, Haqqani commanders, Afghan government ministers, and associated entities designated under E.O. 13224. Afghanistan entries carry program codes SDGT, SDNTK (Specially Designated Narcotics Traffickers), and AFGHAN for individuals subject to Afghanistan-specific sanctions under prior United Nations Security Council resolutions.
Before executing any transaction, match customer names, business counterparties, and beneficial owners against the SDN List. OFAC’s Sanctions List Search tool offers a web interface with adjustable confidence thresholds—from exact matches (100% confidence) to approximate string matching for name variations and transliterations common in Afghan names.
Best-practice workflows break down like this:
- Initial customer screening. Run name-based search at account opening or contract execution; document search parameters and results.
- Ownership verification. Identify beneficial owners holding 25%+ equity; screen each owner independently. The 50% threshold triggers blocking regardless of SDN status.
- Ongoing monitoring. Re-screen quarterly at minimum or use automated sanctions update services—OFAC adds designations without notice.
- False positive resolution. Investigate matches flagged by screening tools: cross-check address, date of birth, nationality, and aliases in the SDN entry; document reasons for clearing or escalating.
The Consolidated Sanctions List combines SDN entries with non-SDN program-specific lists: the Foreign Sanctions Evaders List, Sectoral Sanctions Identifications List, and Non-SDN Menu-Based Sanctions List. Afghanistan transactions require screening against the full Consolidated List, not just the SDN List, to catch sectoral restrictions and indirect entity controls.
XML and CSV formats enable automated batch screening for high-volume institutions. Financial institutions typically embed OFAC screening into payment processing systems, blocking transactions automatically when matches exceed confidence thresholds. Compliance officers then manually review borderline cases and false positives before clearing payments.
What Are OFAC’s Comprehensive Sanctions Programs, and How Does Afghanistan Compare?
OFAC administers comprehensive sanctions programs against five countries plus three Ukrainian regions. As of January 2026:
- Cuba operates under comprehensive embargo (Cuban Assets Control Regulations, 31 CFR part 515)
- Iran faces comprehensive sanctions (Iranian Transactions and Sanctions Regulations, 31 CFR part 560)
- North Korea operates under comprehensive sanctions (North Korea Sanctions Regulations, 31 CFR part 510)
- Syria operates under comprehensive sanctions (Syrian Sanctions Regulations, 31 CFR part 542)
- Crimea, Donetsk, and Luhansk regions of Ukraine face comprehensive sanctions (Ukraine-Related Sanctions Regulations, 31 CFR part 589)
Afghanistan is not on OFAC’s comprehensive sanctions list. Instead, targeted sanctions under the Global Terrorism Sanctions Regulations (31 CFR part 594) and Foreign Terrorist Organizations Sanctions Regulations (31 CFR part 597) block specific individuals and entities rather than imposing geographic trade embargoes.
Comprehensive sanctions prohibit nearly all transactions with sanctioned countries and require Specific Licenses for lawful business. Afghanistan operates differently. Transactions with non-blocked Afghan persons don’t need individual licenses—provided your screening confirms no Taliban, Haqqani Network, or other SDN involvement. This distinction shapes your entire compliance footprint.
General License 20 (31 CFR parts 594 and 597) opens doors that stay closed elsewhere. It authorizes humanitarian assistance, personal remittances, and transactions meeting basic human needs. You get broader pathways here than in comprehensively sanctioned countries, where humanitarian carve-outs demand far stricter licensing.
Building a Sustainable Afghanistan Sanctions Compliance Program
Effective OFAC compliance requires more than a checklist. You need documented policies, trained personnel, and third-party verification systems that go beyond list screening. OFAC’s Framework for Compliance Commitments (May 2019) identifies five essential components: management commitment, risk assessment, internal controls, testing and audit, and training.
Management commitment starts at the board level. Senior leadership must allocate real resources, designate a compliance officer with direct board access, and establish written policies addressing Afghanistan-specific risks. Your board should review program effectiveness at least annually and formally document resolutions authorizing Afghanistan operations—this documentation matters if regulators audit you later.
Risk assessment forces you to identify where exposure actually lives. Which transaction types create heightened OFAC risk? Correspondent banking for Afghan financial institutions tops the list. Supply chain relationships with Afghan government contractors rank high. Humanitarian aid delivery requiring Taliban ministry coordination creates its own complications. Update your risk assessment whenever OFAC issues new designations or modifies General Licenses—which happens more often than you’d expect.
Internal controls translate risk into action. Afghanistan compliance typically requires:
- Pre-transaction SDN screening with documented match/no-match determinations
- Payment monitoring catching indirect evasion attempts—shell companies obscuring Taliban ownership, for instance
- Vendor due diligence that actually verifies beneficial ownership and sanctions compliance certifications
- Escalation protocols forcing management review before any questionable transaction executes
Testing and audit prove your controls work. Independent auditors or internal teams should test screening accuracy, license documentation, and recordkeeping at least annually. Audit findings require management-approved remediation plans with real deadlines.
Training ensures your staff actually understands what they’re doing. Coverage should include SDN List screening procedures, General License applicability, blocked property reporting deadlines, and red flags signaling potential evasion. Annual refreshers keep people current as new designations and regulatory changes roll out.
Record retention under 31 CFR § 501.901 mandates preserving screening documentation, license applications, and compliance records for five years minimum. Electronic systems should capture screening parameters, match results, and reviewer decisions—you’ll need this detail if audits come.
FAQ
What are the current OFAC sanctions on Afghanistan?
There is no comprehensive, country-wide U.S. embargo on Afghanistan. OFAC’s Afghanistan-related program is targeted: the Taliban were first sanctioned in 2001 under E.O. 13224, which created a national emergency, but that emergency was terminated in 2002 under E.O. 13268. Today, the Taliban are designated as a Specially Designated Global Terrorist (SDGT) under E.O. 13224, and the Haqqani Network is designated as both an SDGT under E.O. 13224 and a Foreign Terrorist Organization under the Immigration and Nationality Act. Importantly, these designations do not prohibit U.S. persons from exporting or reexporting goods or services to Afghanistan, as long as the transaction doesn’t involve a sanctioned party or blocked property. Separately, E.O. 14064 (2022) carved out certain exceptions for property of Da Afghanistan Bank. To keep humanitarian channels open, OFAC has issued seven Afghanistan-related General Licenses (14 through 20) under the Global Terrorism Sanctions Regulations and the Foreign Terrorist Organizations Sanctions Regulations, authorizing transactions ordinarily necessary for humanitarian assistance and support of the Afghan people.
Where can I download the OFAC SDN List?
The SDN List is published daily at 8:00 AM EST on OFAC’s website in PDF, XML, and CSV formats — see our screening workflow above for how to use it.
What is the latest update to Afghanistan-related sanctions?
Based on the most recent search results (through mid-August 2026), OFAC’s Afghanistan-specific framework hasn’t changed structurally — the program remains anchored in the SDGT/FTO designations of the Taliban and Haqqani Network, the Da Afghanistan Bank carve-out under E.O. 14064, and GLs 14–20 for humanitarian flows. OFAC’s broader “Recent Actions” feed shows ongoing terrorism- and Iran-related designation updates through August 2026, but no Afghanistan-specific SDN action has surfaced in current results. Note that allied programs have moved more recently: on 11 March 2026, the UK’s Foreign, Commonwealth and Development Office updated 22 entries on the UK Sanctions List for the Afghanistan regime, and the UN’s Taliban sanctions committee updated entries for several individuals in April 2026. If you need the definitive, current OFAC position, I’d check OFAC’s Recent Actions page directly, since designations there can change day to day.
