A mid-sized technology exporter receives notice that a minority shareholder in its joint-venture partner has appeared on BIS's Entity List (the list of foreign persons subject to licence requirements under the Export Administration Regulations, known as the EAR). The transaction team asks the obvious question: can we continue shipping, or must the relationship end? That question, left unanswered for even a few weeks, carries real exposure. As of January 2026, BIS enforcement posture remains active, and the EAR's extraterritorial reach means that a shipment from a third country can still trigger US jurisdiction if it contains items subject to the EAR.
Divesting a sanctioned interest under the BIS / EAR involves mapping the controlled items in the relationship, identifying the precise export-control classification and licence requirements, conducting a structured wind-down of controlled transfers, and closing the commercial relationship in a sequence that satisfies BIS record-keeping and, where applicable, voluntary self-disclosure obligations. The EAR is administered by BIS, the Bureau of Industry and Security within the US Department of Commerce, under authority derived from the Export Control Reform Act. Unlike a purely financial-sanctions wind-down under OFAC, the BIS / EAR divestment focuses on the ongoing transfer of technology, software, and hardware – not only the ownership or money flow.
This guide walks through each phase of that process: from the initial classification review, through the licence assessment and deal suspension, to the final wind-down and record closure, with a cross-regime comparison at each stage for businesses that also face OFAC, OFSI, or EU obligations on the same facts.
Step 1 – Understand what the EAR controls and why it differs from financial-sanctions rules
The EAR controls the export, re-export, and in-country transfer of commercial and dual-use items – physical goods, software, and technology – that appear on the Commerce Control List (CCL), as well as some items that fall outside the CCL but remain subject to the EAR's general requirements. BIS administers the regime; the Entity List, the Denied Persons List, and the Military End-User List are its primary screening tools. A designation on any of those lists may require a licence for items that would otherwise move freely, or it may trigger a policy of denial for all licence applications involving that party.
This matters for a divestment because the EAR's logic is transactional, not status-based. OFAC's financial-sanctions rules block property and prohibit transactions because of who the counterparty is. The EAR imposes licence requirements because of what is being transferred and to whom. That distinction drives the entire divestment sequence. A business can, in theory, hold an equity interest in a company on the Entity List without a per se violation – but every subsequent controlled transfer to that company will require a licence, and BIS's licensing policy for Entity List parties is typically one of presumption of denial. In our experience, conflating the two regimes at the outset leads firms to address the wrong risk first, often clearing the financial exposure while leaving live EAR violations on the table.
The EAR also has a long extraterritorial arm. Items that contain more than a de minimis proportion of US-controlled content, and foreign-made products of certain US technology, remain subject to the EAR wherever they are in the world. For a cross-border joint venture, this means the divestment analysis cannot stop at the US border. Is the foreign subsidiary re-exporting US-origin components to the listed entity? That transfer carries EAR exposure even if no US person is directly involved.
Step 2 – Map the controlled items and classify each relationship
Before any commercial decision is taken, every item, technology, and software being transferred in the relationship must be classified against the CCL, and every party in the chain must be screened against BIS's restricted-party lists, OFAC's SDN List (the list of Specially Designated Nationals and blocked persons), and, for UK-nexus transactions, OFSI's Consolidated List. This is not a one-off check; it is a point-in-time inventory with a cut-off date that becomes the baseline for the wind-down plan.
The classification step turns on the item's Export Control Classification Number (ECCN), which assigns each item to a category on the CCL based on its technical parameters. Items not assigned an ECCN typically carry the designation EAR99 – meaning they are subject to the EAR but not to CCL-specific controls, and therefore generally exportable without a licence to non-embargoed destinations and non-listed parties. Where the relationship involves EAR99 items only and the counterparty appears solely on a list that does not cover EAR99 items, the export-control picture looks different from a case where controlled technology is involved. Both scenarios require verification; assumptions are how violations begin.
The mapping exercise should produce a written inventory with four columns: the item or technology, its ECCN or EAR99 designation, the licence exception available if any, and the status of the counterparty or end-user under each applicable list. That document becomes the foundation for every subsequent step. It also becomes the disclosure file if a voluntary self-disclosure becomes necessary.
Cross-regime note: if the same counterparty is on both the Entity List and OFAC's SDN List, the divestment must satisfy both regimes simultaneously. The stricter prohibition governs each element. We regularly advise on cases where the BIS wind-down is technically complete but the OFAC property block has not been addressed – leaving the client in a position where the equity interest itself is frozen.
Step 3 – Assess licence requirements and whether a specific licence is needed to wind down
Not every divestment step is prohibited; some are required to produce a clean exit, and BIS has historically recognised that a well-structured wind-down may itself require a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) where controlled technology is involved. The question is whether a licence exception covers the winding-down transfers, or whether a specific licence application must precede each transfer.
Common licence exceptions – such as those covering technology for fundamental research, items controlled only for anti-terrorism reasons, or items destined to close allies of the United States – may not be available where the counterparty is on the Entity List, because Entity List entries often expressly exclude those exceptions. That exclusion must be checked on the face of the Entity List entry itself, as individual entries specify which exceptions remain available and which are removed. Where exceptions are excluded, every controlled transfer during the wind-down period requires either a specific licence or a cessation of transfers.
A cessation-first approach – stopping all controlled transfers immediately and then structuring the equity exit – is often the lower-risk path for smaller relationships. It accepts commercial disruption in exchange for regulatory clarity. For larger joint ventures where an abrupt halt would itself cause harm, a specific licence application to BIS may be warranted, explaining the wind-down purpose and requesting a time-limited authorisation to make only those transfers necessary to complete the exit. BIS has the discretion to grant such applications. There is no statutory guarantee; the licence-review process takes the time it takes, and a well-documented application supported by a clear wind-down plan fares better than a bare request.
How does the BIS / EAR divestment process compare to OFAC and OFSI wind-downs?
The BIS / EAR wind-down is operationally distinct from an OFAC-driven divestment in three significant ways. First, the trigger: OFAC designations block property automatically on the moment of listing, requiring immediate asset freeze and report to OFAC. BIS designations impose licence requirements prospectively; property is not automatically frozen. Second, the timeline: OFAC imposes a reporting obligation on US persons who hold blocked property – that window is short and its non-observance is itself a violation. BIS does not impose an equivalent automatic reporting deadline on discovering that a counterparty has been listed, though a voluntary self-disclosure (VSD) of prior unlicensed transfers is strongly advisable before a wind-down begins and becomes material to BIS's enforcement calculus.
Third, the divestment mechanism itself: under OFAC, a specific licence authorising the divestment of a blocked equity interest may be needed, and the process runs through OFAC's licensing office. Under the EAR, the equity holding per se is not blocked, but every technology and software transfer during the remaining commercial relationship requires an assessed licence position. The exit documentation – the share-purchase agreement, the technology hand-back, the IP licence termination – each need an EAR screen before execution.
Under OFSI (the UK Office of Financial Sanctions Implementation) and the comparable EU regime, the ownership-and-control test adds a further layer. OFSI and EU rules apply not only where a listed person owns 50 percent or more of an entity but also where a listed person otherwise controls it – a broader test than OFAC's mechanical ownership threshold. Where the joint venture has a UK or EU dimension, the divestment plan must address all three regimes. The strictest obligation applicable to each element of the unwind governs that element. Failing to map the EU and UK position while conducting a BIS-focused exit is a pattern we see repeatedly in cross-border deal teams.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, the jurisdiction of the joint venture vehicle – change the analysis significantly. For an early assessment of your BIS / EAR exposure, contact Calder & Vance at info@caldervance.com.
Step 4 – Structure the commercial exit and document every transfer
Once the licence position is clear, the commercial exit – the actual divestment of the equity interest or the termination of the supply relationship – must be structured in a sequence that keeps every transfer within the authorised position. This is where divestments most frequently go wrong: the commercial team moves faster than the compliance analysis, and controlled technology transfers continue into the wind-down period without a current licence assessment.
The practical structure for a controlled exit has four elements. First, a transfer moratorium: all transfers of items with ECCNs subject to licence requirements cease or are held under the licence exception or specific licence identified in Step 3. Second, a technology return or destruction protocol: controlled technology shared with the counterparty – drawings, source code, technical data – is either returned or certified destroyed, with written confirmation from the counterparty. Third, a commercial-agreement termination sequence that follows the licence position rather than preceding it. And fourth, a written record of each step, timestamped and file-referenced, to support both internal audit and a VSD if one becomes necessary.
Record-keeping under the EAR requires that export and re-export records be retained for five years from the date of the transaction. That obligation survives the end of the commercial relationship. The wind-down documentation – licence assessments, correspondence with BIS, transfer records, technology-return certificates – should all be filed within that system from the start. In a subsequent investigation, the existence of a contemporaneous, structured record is a significant mitigation factor.
In a recent matter, a European manufacturing group discovered mid-divestment that its subsidiary had been transferring controlled software updates to the joint-venture partner for several quarters after the partner's parent appeared on a BIS list. We classified each transfer, identified the applicable licence requirements, structured a VSD to BIS covering the prior unlicensed transfers, and managed BIS's follow-up queries. The matter concluded without a formal enforcement action. No outcome of that kind can be promised; what a timely and well-documented VSD does is place the firm in the most favourable procedural position before any enforcement discretion is exercised.
Step 5 – Consider voluntary self-disclosure and manage the BIS follow-up
A VSD to BIS is not legally compelled in every divestment, but it is, in our experience, the right decision in most cases where prior unlicensed transfers have occurred. BIS's published enforcement guidance identifies a VSD as a significant mitigating factor; the absence of one where a disclosure was warranted is correspondingly an aggravating factor. The VSD process involves an initial notification to BIS's Office of Export Enforcement, followed by a full written disclosure within a specified period. That disclosure must be accurate and complete; a VSD that omits material transfers is worse than no VSD.
The VSD submission should include: the identity of the items transferred by ECCN, the dates and values of the transfers, the identity of the counterparty (described in terms of the list entry, not embellished), the reason the transfers were not identified earlier, and the corrective actions taken or in progress. It should be accompanied by the classified transfer inventory prepared in Step 2 and the wind-down record prepared in Step 4. The quality of that documentation directly affects BIS's assessment of the firm's compliance culture.
BIS may respond with a request for additional information, a no-action letter, a warning letter, or, in more serious cases, a referral to formal enforcement proceedings. The range of outcomes reflects the breadth of BIS's enforcement discretion and the weight given to the self-disclosure, the prior compliance record, and the nature of the items transferred. We advise clients not to treat the VSD as a guarantee of any particular outcome, but rather as the beginning of a managed engagement with the regulator.
If a transaction has already been flagged, or a prior transfer has been identified as unlicensed, an early review preserves options that narrow with delay. Contact Calder & Vance at info@caldervance.com to discuss your position.
Risk flags and common mistakes in BIS / EAR divestments
Several patterns recur in BIS divestments that fail or attract enforcement attention.
The first is treating the EAR as a financial-sanctions problem. Businesses with strong OFAC compliance programmes sometimes apply OFAC's property-freeze logic to an EAR listing. The two regimes operate on different triggers and require different responses. Conflating them means the wrong controls are applied in the wrong sequence.
The second is a delayed classification. Firms sometimes begin commercial wind-down negotiations before completing the item classification. A contract termination that involves a transfer of controlled technology – including a technology hand-back – is itself a transfer that requires a licence assessment. Executing it without one is an unlicensed export, regardless of the wind-down purpose.
The third is incomplete screening. An Entity List entry may list only one legal entity in a corporate group. Unless the full ownership chain is screened, transfers to subsidiaries or affiliates of the listed entity may continue unchecked. BIS's rules on related parties and procurement agents extend the reach of a listing beyond the named entity in some cases. Verify the scope of each entry on its own terms.
The fourth is failing to address the cross-regime picture. A clean BIS wind-down that leaves an unresolved OFAC position is not a completed divestment. Where both regimes apply, the exit plan must close both. The same is true for UK and EU obligations where there is a nexus to those jurisdictions.
The fifth – and perhaps the one we see most often underestimated – is the record-keeping gap. The five-year retention obligation under the EAR means that records from a transaction completed today must be retrievable in 2031. Firms that do not have a document retention system aligned to export-control timelines routinely find that key records are missing precisely when BIS asks for them.
Related practices
- Correspondent banking and de-risking under OFAC – managing OFAC exposure in financial-institution relationships and cross-border payment flows.
- Divesting a sanctioned interest under the Canadian regime – step-by-step guide to the GAC framework and cross-border coordination.
- Divesting a sanctioned interest: cross-border guide – multi-regime overview covering OFAC, OFSI, EU, and additional regimes simultaneously.