A multinational's counterparty has just been removed from the SDN List (OFAC's list of Specially Designated Nationals and blocked persons). Accounts are unfrozen on paper. Goods that were held at a port may be moving again. But the counterparty's export licences were revoked when it appeared on the Entity List (BIS's list of parties subject to heightened export-control restrictions). The delisting resolved one set of prohibitions. A separate, parallel system still controls what can be shipped to that party, under what conditions, and who bears the administrative burden of proving the release is complete. Post-delisting release of assets under OFAC versus BIS / EAR is not a single clearance event. It is two distinct legal processes, governed by different authorities, operating on different timetables, and carrying different residual risks.
As of February 2026, post-delisting release of assets under OFAC operates through a statutory unblocking mechanism triggered automatically when a name is removed from the SDN List, though administrative steps and specific-licence requests may still be required. The BIS / EAR process is structurally different: removal from the Entity List lifts the licence requirement imposed by that listing, but underlying Export Control Classification Number (ECCN – a product-specific code on the Commerce Control List that determines what authorisation is needed) controls remain, and any revoked licence is not automatically reinstated. Neither system synchronises with the other, and where both applied to the same party, both must be worked through in sequence.
This analysis maps the two processes side by side, identifies the points of divergence that create residual exposure, and sets out what a cross-border business should do before it treats the release as complete.
What legal authority governs post-delisting asset release under OFAC?
Post-delisting release under OFAC is governed by IEEPA – the International Emergency Economic Powers Act – and the specific thematic sanctions regulations issued under it. OFAC administers the process. When a designation is revoked, the legal prohibition on dealing with the blocked person lapses as of the effective date of removal. However, the property that was blocked while the designation was in force does not simply flow back to its owner without further action.
Blocked property held by a US person (any individual or entity subject to US jurisdiction, including foreign branches of US firms) must be released or transferred. In practice, a financial institution holding blocked funds will require written confirmation of the removal and, in many cases, a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) to effect the actual transfer – particularly where the funds were blocked for a significant period and the account structure has changed. OFAC has issued guidance on unblocking procedures, and institutions routinely submit licence requests even post-delisting to obtain certainty before moving value.
The governing principle is that the unblocking is effective as of the OFAC removal date, but the mechanics of transfer remain subject to institutional compliance requirements and, where any doubt exists about the nature of the property or the identity of the beneficial owner, a licence request is the prudent course. In our experience, financial institutions are slow to move without that written comfort. The removal date and the practical release date are almost never the same day.
The position above covers the standard case. Your facts – the counterparty, the assets involved, the institutions holding them, and the secondary regimes in play – change the analysis materially. For an assessment of your post-delisting exposure, contact Calder & Vance at info@caldervance.com.
How does BIS / EAR handle the release of export privileges after removal from the Entity List?
Under the EAR – the Export Administration Regulations administered by the Bureau of Industry and Security (BIS) – removal from the Entity List lifts the specific elevated licence requirements that the listing itself imposed, but it does not restore a clean export-privileges slate. The EAR distinction matters: the Entity List is an additional control layer, not the entirety of EAR jurisdiction over a party.
When a party was listed on the Entity List, BIS typically imposed a licence requirement for all items subject to the EAR destined for that party, often with a policy of denial. Removal ends that layer. What remains are the underlying ECCN-based controls applicable to the goods themselves. A shipment that required a licence before listing still requires one after delisting if the ECCN and end-use controls call for it. The delisting changes the party-specific layer; it does not change the commodity-level layer.
More significant is the question of revoked licences. Where BIS revoked an existing export licence upon listing, removal from the Entity List does not automatically reinstate that licence. The exporter must apply for a new licence and BIS will review it on its current merits, taking into account any changes in the end user's circumstances since the original licence was granted. That review can take a significant period. Exporters who plan operations on the assumption that prior authorisation revives at delisting face a real gap in their programme.
There is also the question of Validated End-User (VEU) authorisation status, which some parties in high-technology sectors relied upon before designation. VEU status does not survive listing and is not reinstated at delisting; a fresh application is required. In our experience, post-delisting clients are often surprised by the length of that re-authorisation pipeline.
Where do the regimes diverge on post-delisting release of assets?
The two regimes diverge at four structural points, and each divergence creates a distinct category of residual risk for a business that has relied on a single counterparty throughout a supply chain or financing arrangement.
First: automaticity. OFAC's unblocking is legally automatic on the effective date of removal – the prohibition lapses by operation of law. BIS has no equivalent automatic restoration. The Entity List removal is published in the Federal Register, but nothing in the EAR restores prior authorisations or removes the underlying ECCN controls. A business that treats Entity List removal as full clearance has misread the regime.
Second: the asset-versus-privilege distinction. OFAC's post-delisting process is primarily about releasing blocked property – funds, accounts, goods held in escrow. BIS's post-delisting process is primarily about restoring export privileges – the right to receive shipments of controlled goods. These are categorically different things. A company whose cash was frozen under OFAC and whose component supply was cut off under the EAR faces two separate recovery paths with no procedural overlap.
Third: the institutional intermediary's role. Under OFAC, financial institutions are central to the release. They hold the blocked funds and must act to transfer them. Under the EAR, the exporter or re-exporter is the regulated party and bears the compliance burden at the point of shipment. The post-delisting process under each regime thus runs through a different set of actors, and coordinating them requires deliberate project management.
Fourth: residual compliance obligations. Under OFAC, once blocked property is properly released under a specific licence or confirmed unblocking, the OFAC risk to that transaction is discharged. Under the EAR, ongoing shipments to the formerly-listed party remain subject to the full EAR compliance cycle – ECCN classification, end-use screening, destination control statements, and record-keeping. Post-delisting does not reduce the EAR compliance burden on future transactions to zero.
If a transaction has already been flagged, or an export licence application has been refused, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential review.
Which regime is stricter on post-delisting release of assets?
Strictness is a function of what the regime is controlling. On the narrow question of releasing blocked assets, OFAC is more demanding in the sense that it requires a formal unblocking step – written confirmation, and often a licence request from the holding institution – before value can move. BIS has no analogous asset-holding mechanism: the EAR does not freeze property.
On the broader question of restoring a normal commercial relationship with the formerly-listed party, the EAR is more demanding. Nothing in the OFAC regime governs future shipments of goods once the person is removed from the SDN List. The EAR, by contrast, continues to apply to every subsequent shipment of any item with an ECCN that carries a licence requirement for the relevant destination or end use. The party may be off the list, but the goods remain classified, and the classification does not care about the counterparty's current SDN status.
For a business that both held blocked funds under OFAC and maintained an export relationship under the EAR, the combined answer is that OFAC is strict at the moment of release, and the EAR is strict on an ongoing basis thereafter. That sequence – a sharp OFAC compliance event followed by a continuing EAR compliance programme – is the correct mental model for managing post-delisting operations with a formerly-listed party.
The cross-border dimension adds a further layer. A UK or EU counterparty of the delisted party may find that OFSI's ownership and control test (which, unlike OFAC's mechanical ownership rule, extends to effective control) or the EU Council regulation's equivalent test retained a prohibition even after the OFAC SDN removal. The applicable UK thematic sanctions regulations and the relevant EU Council regulation may not delist the same party on the same date, or at all. In our practice, the gap between OFAC removal and EU or UK removal can run to months, sometimes longer. Assuming parallelism across regimes is one of the costliest errors we see at the post-delisting stage.
What does the cross-border picture look like for a business with UK or EU exposure?
Post-delisting under OFAC carries no automatic effect in the UK or EU regimes. OFSI administers UK financial sanctions under the Sanctions and Anti-Money Laundering Act, and an OFAC removal triggers no automatic OFSI review. A UK person holding assets subject to an OFSI financial-sanctions obligation must continue to comply with that obligation until OFSI's own list is updated or a specific licence from OFSI is obtained.
The EU position is the same in principle. The EU Council designates and de-lists separately from OFAC. An EU operator holding funds pursuant to an EU Council regulation asset freeze cannot release them on the basis of an OFAC SDN removal alone. The applicable Council regulation remains in force as to that party until the Council acts.
There is also the question of what practitioners call the stricter-prohibition principle – where two regimes overlap, the stricter prohibition governs the transaction for the party subject to both. A US exporter with a UK subsidiary is subject to both US and UK rules. If the UK rules still prohibit the transaction after OFAC delisting, the US parent cannot simply proceed on the basis of the OFAC clearance. The UK prohibition binds the subsidiary, and the group's consolidated risk exposure must be assessed accordingly.
For businesses with operations across multiple jurisdictions, the practical implication is that post-delisting project management must proceed regime by regime. A single removal from one list creates one clearance for one set of obligations. It does not constitute a global release. This is a point where involving experienced cross-border counsel early saves significant subsequent cost.
What risk flags should a business monitor in the post-delisting period?
Post-delisting risk does not disappear at the moment of removal. Several categories of residual exposure regularly materialise in the weeks and months after a counterparty is removed from the SDN List or the Entity List.
The first risk flag is the re-designation window. A party removed from the SDN List may be re-designated if OFAC determines that the basis for designation has recurred or that new grounds exist. In our experience, businesses that rapidly resume full transactional relationships immediately after delisting – before the operational picture has stabilised – have had to manage a second freeze event. A monitored re-entry phase, rather than an immediate return to full volume, is the more defensible position.
The second risk flag is the ownership chain at removal. The delisting resolves the prohibition as to the named party. It does not resolve the position as to other parties in the ownership chain that may themselves be listed. If the delisted company has a majority shareholder that remains on the SDN List, the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked, in the aggregate across all blocked holders) continues to apply to the delisted company. The entity-level removal does not sever that chain until the parent-level issue is resolved.
The third risk flag under the EAR is the end-use and end-user change between the original licence and any post-delisting application. BIS will assess the new application against current facts, which may include changes in the formerly-listed party's ownership, its customers, or its sector activities during the listing period. An application that would have been approved before designation may face a different outcome if the underlying risk profile has changed.
The fourth risk flag is record-keeping continuity. Under the EAR, export records must be maintained for a defined period. Under OFAC, records relating to blocked property and its subsequent release must also be preserved. A business that has changed systems, personnel, or counterparty relationships during the listing period faces a records-management risk at post-delisting. A gaps analysis before resuming transactions is the minimum prudent step.
A common myth: delisting means the relationship is clean
The most persistent misconception we encounter is this: that a counterparty's removal from the SDN List or the Entity List means that the commercial relationship is unrestricted and that prior compliance deficits are wiped. Neither is true.
Delisting ends the specific prohibition tied to that designation. It does not end the EAR's application to the goods. It does not end the UK or EU sanctions regime's application if those regimes have not separately delisted the same party. It does not cure any violation of the prohibition that occurred while the party was listed – those are historical positions and may separately require a VSD (voluntary self-disclosure to a regulator) assessment. And it does not restore any collateral contractual position, such as force-majeure notices that were served during the sanctions period, without independent legal review.
Post-delisting is not a clean slate. It is the start of a structured re-entry process that requires the same analytical rigour as the original onboarding. In our practice, clients who treat it as anything less regularly find themselves managing a secondary compliance event six to twelve months later.
Related practices
- Delisting evidence package – Australia – building the evidentiary record for DFAT removal proceedings
- Post-delisting asset release – OFAC vs BIS / EAR (extended analysis) – extended cross-regime analysis of the post-delisting sequence
- Post-delisting asset release – OFAC vs EU compared – how the EU Council regulation and OFAC unblocking diverge in practice