OFAC's issuance of General Licenses Y and Z, along with new Iranian network designations, underscores a regulatory pattern you can't ignore: wind-down periods aren't optional pauses in sanctions enforcement. They're structured exit ramps with hard deadlines and specific limitations. Yet, compliance teams often mishandle these windows, turning what should be an orderly disengagement into a scramble or inadvertent violations.
Why These Mistakes Keep Happening
Wind-down general licenses sit in a gray area of sanctions compliance. They're neither full authorizations nor complete prohibitions. Your team gets notified that a counterparty is now on the Specially Designated Nationals and Blocked Persons List (SDN List), and simultaneously, OFAC issues a general license giving you 30 days to exit. The pressure is immediate: legal wants clarity, treasury needs payment instructions, and operations is asking about tomorrow's shipment.
This time pressure leads to predictable errors. Teams either interpret the licenses too cautiously, leaving money on the table, or too permissively, exceeding the license scope. Both approaches result in compliance costs and regulatory exposure.
Mistake 1: Treating Wind-Down Periods as Full Authorization
Why it happens: Your sanctions analyst sees that General License Y authorizes "transactions ordinarily incident and necessary to the wind down" and assumes this means business as usual until August 9, 2026.
Real consequence: Your institution processes a payment for new services contracted after the designation date, thinking it's covered by the wind-down license. OFAC's stance is clear: wind-down licenses cover pre-existing obligations, not new business. This misstep could lead to a potential violation, requiring voluntary self-disclosure, internal investigation costs, and possible civil penalties.
The fix: Implement a designation-date cutoff in your sanctions screening workflow. GL Y and GL Z authorize completing transactions that existed before Smart Global Limited and the Shamkhani network entities were designated. Any contract signed or service initiated after July 10 or July 14, 2026, respectively, is outside the license scope. Your payment processing system should flag and hold any transaction with a newly designated party until a sanctions officer confirms it relates to a pre-designation obligation. Document this determination for each approved payment.
Mistake 2: Missing the Blocked Account Requirement
Why it happens: Your team focuses on the wind-down deadline but overlooks the payment mechanics in the general license. Payments get processed through normal channels because "it's authorized anyway."
Real consequence: GL Y and GL Z require that payments to blocked persons be deposited into blocked, interest-bearing accounts in the United States. Wiring funds directly to Smart Global Limited's account in Saint Kitts and Nevis or settling a shipping invoice to a Shamkhani-controlled entity's UAE account violates the license terms, even if the transaction was otherwise permissible. OFAC doesn't see this as a technical error; you've failed to freeze assets as required under the International Emergency Economic Powers Act.
The fix: Establish a blocked account protocol before you need it. Your compliance team should maintain relationships with correspondent banks that can open blocked accounts on short notice. When a wind-down payment is approved, route it to a blocked account in the payee's name at a US financial institution, not to the designated party's existing foreign accounts. Include the OFAC designation citation and general license number in the account opening documentation. This isn't a workaround; it's the compliance mechanism that makes wind-down payments legal.
Mistake 3: Assuming the License Covers All Related Parties
Why it happens: Smart Global Limited appears on multiple transaction records alongside other entities in Ansari's network. Your team assumes that if the general license authorizes Smart Global transactions, it must cover the broader network.
Real consequence: GL Y explicitly states it doesn't extend to transactions involving other blocked persons unless separately authorized. Approving a payment that involves both Smart Global Limited and another Ansari-controlled entity not named in the general license exceeds the authorization. The fact that both entities serve the same beneficial owner is irrelevant to OFAC's licensing structure.
The fix: Screen every party to the transaction, not just the primary counterparty. If your wind-down payment involves intermediaries, benefits additional parties, or involves entities with shared ownership, each one requires separate sanctions clearance. You can't rely on GL Y to cover Ansari himself or other network entities. If the transaction involves multiple designated parties, you need either additional general licenses or a specific license application to OFAC. Build this multi-party screening into your wind-down approval checklist, and don't approve partial exits that leave you exposed to unlicensed parties.
Mistake 4: Ignoring the Scope Limitations in Maritime Licenses
Why it happens: GL Z authorizes certain vessel-related activities, and your operations team interprets this as permission to continue normal shipping operations through September 12, 2026.
Real consequence: GL Z covers specific categories: financial transaction wind-down, safe vessel operations (docking, anchoring, departure), crew welfare, emergency repairs, environmental protection, and delivery of cargo loaded on or before July 14, 2026. It doesn't authorize new cargo loading, extended charter arrangements, or routine maintenance beyond emergency repairs. Loading new containers onto a designated vessel in August 2026, citing GL Z as authority, exceeds the license scope. The authorization protects safety and environmental concerns; it doesn't preserve commercial shipping operations.
The fix: Create activity-specific authorization checklists for maritime general licenses. Before approving any vessel service, confirm it falls within one of the enumerated categories in GL Z. "Ordinarily incident and necessary to wind down" doesn't mean "anything we normally do with ships." It means completing financial obligations from before the designation, ensuring the vessel can safely leave port, protecting crew health, preventing environmental damage, and delivering cargo already loaded. If the activity doesn't fit these categories, it requires a specific license regardless of the wind-down period.
Mistake 5: Letting the Deadline Expire Without Documentation
Why it happens: Your team completes all wind-down transactions by August 9, 2026, and considers the matter closed. No one creates a wind-down completion record or confirms that all blocked funds have been properly reported.
Real consequence: Three months later, OFAC conducts a targeted review of your institution's handling of the Ansari designations. You can't produce contemporaneous documentation showing which transactions were processed under GL Y, why each qualified for wind-down treatment, or how you ensured compliance with the blocked account requirement. Without this audit trail, OFAC can't verify your good-faith compliance, and you can't defend against allegations that some payments exceeded the license scope. The absence of documentation transforms defensible judgment calls into apparent violations.
The fix: Treat wind-down periods as compliance events that require formal closeout procedures. Before the general license expires, compile a wind-down summary that lists every transaction processed under the authority, the pre-designation obligation it satisfied, the blocked account where funds were deposited, and the date of completion. Include copies of the underlying contracts or invoices that demonstrate the obligation existed before the designation date. File this summary with your sanctions compliance records and notify your OFAC point of contact that wind-down activities have concluded. This documentation protects you in future examinations and demonstrates the control environment OFAC expects from sophisticated institutions.
Prevention Checklist
Incorporate these steps into your sanctions compliance procedures before the next designation wave:
Immediate response (Day 0-1):
- Freeze all transactions involving newly designated parties
- Identify which general licenses, if any, accompany the designations
- Pull transaction records for the past 12 months to identify pre-existing obligations
- Notify business units of the designation and wind-down timeline
Wind-down execution (Days 2-29):
- Verify each proposed transaction relates to a pre-designation obligation
- Confirm the transaction category falls within the general license scope
- Route payments to blocked accounts at US financial institutions, not to the designated party's foreign accounts
- Screen all transaction parties, not just the primary counterparty
- Document the legal basis for each approved transaction in writing
Closeout procedures (Final day before expiration):
- Compile a complete list of wind-down transactions with supporting documentation
- Confirm all blocked accounts have been reported to OFAC
- Create a wind-down completion summary for compliance records
- Brief senior management on any remaining exposure or unresolved obligations
Wind-down general licenses reflect OFAC's recognition that sanctions designations disrupt legitimate commerce. But that recognition comes with precise conditions and hard deadlines. Your compliance program should treat these windows as structured procedures and build the documentation standards that prove you stayed within the lines.
