A trading house with operations across three continents receives notice that one of its US-registered subsidiaries has had accounts frozen under an export-control action linked to BIS / EAR enforcement. The affected subsidiary holds operating capital and is party to several active supply agreements. The compliance team has forty-eight hours before the next scheduled wire transfer. What happens next, and who decides?
Frozen-account management under the Export Administration Regulations (the EAR – the US Commerce Department's primary export-control instrument, administered by BIS, the Bureau of Industry and Security) is a distinct discipline that sits at the intersection of licensing, enforcement, and day-to-day treasury operations. It is not simply a screening problem. It requires a structured legal response: scope the order, identify what assets are caught, determine whether any authorisation permits continued access, and engage BIS within the available window. As of June 2026, the EAR does not impose a single universal notification deadline for all situations, but the window for preserving options is short and the consequences of inaction are significant.
This case comment walks through a representative frozen-account matter: the situation that triggered the freeze, the legal questions that arose under the EAR, the cross-border complications that required analysis under both OFAC and UK OFSI rules, and the route the business took to restore operational access. The account is anonymised; no identifying details are carried.
The situation: what triggered the freeze
The freeze was triggered when the US subsidiary was placed on a restricted-party list administered by BIS following a referral by a third-party compliance programme. The entity was not itself the subject of an export-control violation finding, but it shared a beneficial-ownership chain with a company that appeared on the Entity List (BIS's list of persons subject to specific licence requirements for all items subject to the EAR). Under the EAR's ownership-and-control analysis, the US subsidiary's accounts were swept into the restriction pending clarification.
The first question the business had to answer was definitional: was this an EAR measure, an OFAC measure, or both? The answer mattered because the response route, the authorising agency, and the available licensing pathway are different for each. In our experience, this is where many businesses lose time. They assume that because accounts are frozen, OFAC must be the authority. That assumption is wrong when the originating action is an export-control matter routed through BIS.
The originating order in this case was a BIS administrative measure. OFAC had not separately designated any entity in the ownership chain. That distinction defined everything that followed – the applicable instrument, the licensing authority, and the form of any authorisation to restore access.
What the EAR requires: the legal basis for the freeze
The EAR, administered under the authority of the Export Control Reform Act and IEEPA, gives BIS broad authority to impose licence requirements on persons and entities whose conduct raises proliferation or diversion concerns. An Entity List placement does not mean a criminal finding. It means that BIS has determined that there is sufficient reason to believe the listed person poses an export-control risk, and that all items subject to the EAR therefore require a licence before being exported, re-exported, or transferred in-country to that person.
The knock-on effect on financial accounts arises because many financial institutions and payment processors treat an Entity List placement in the same enforcement register as an OFAC SDN listing. That conflation is understandable from a risk-management perspective. It is not always legally accurate. An entity on the Entity List is not automatically a Specially Designated National (SDN – a person whose property is blocked under OFAC regulations). The two lists have different legal bases, different consequences, and different resolution routes.
What, then, authorises a financial institution to release funds when the underlying restriction is an EAR measure rather than an OFAC block? The answer lies in the nature of the authorisation the regulated party holds or can obtain. Under the EAR, a specific licence (a case-by-case authorisation issued by BIS permitting a defined transaction or class of transactions) can authorise the relevant activity. A licence exception (a standing authorisation that permits a defined category of activity without a specific application) may also apply, depending on the goods, technology, or activity in question – but licence exceptions under the EAR are narrower when an Entity List placement is in force.
How was the cross-border picture complicated by OFSI and EU rules?
The trading house's parent was incorporated in the United Kingdom and had operating accounts in an EU member state. This introduced two additional regimes: OFSI (the UK's Office of Financial Sanctions Implementation) and the relevant EU Council financial-sanctions framework. Even though the originating restriction was a US BIS action, UK and EU financial institutions with correspondent relationships to the affected accounts faced their own compliance obligations.
Under OFSI's licensing regime, a UK financial institution holding funds related to a person subject to a UK financial-sanctions measure must obtain a specific licence before releasing those funds. But in this matter, no UK designation was in force. The UK financial institution's concern was therefore not a formal OFSI freeze but a voluntary hold imposed as a precaution pending clarification of the US position. That is a different situation, and it called for a different response: not a licence application to OFSI, but a legal opinion letter explaining the US-law position and confirming that no UK financial-sanctions measure applied.
We regularly advise on exactly this junction. The cross-border misread – treating a BIS enforcement measure as an automatic OFSI or EU freeze – delays resolution and increases cost. In our experience, a clear written analysis of each regime's applicability, delivered early, is the most effective tool for unblocking precautionary holds imposed by financial institutions acting under their own compliance programmes.
The EU picture was similar. No EU designation applied. The EU financial institution's hold was precautionary. Again, the resolution route was documentary rather than regulatory: a regime-by-regime analysis confirming the absence of a concurrent EU measure, combined with a request that the institution clarify its internal compliance basis for the hold.
The authorisation route: applying to BIS for a specific licence
With the jurisdictional picture clear, the primary response was a specific-licence application to BIS through the Simplified Network Application Process Redesign (SNAP-R) system. The application set out the nature of the accounts, the ownership and control chain, the absence of an OFAC designation, the operational need for access, and the compliance measures the business had put in place to address the original Entity List concern.
BIS licence applications are reviewed against the statutory export-control criteria under the EAR. The processing timeline for a specific-licence application varies by complexity and the nature of the commodity, technology, or activity in question. There is no universal processing deadline in the EAR analogous to OFSI's guidance timelines. In our practice, well-prepared applications with complete documentation and a clear statement of need tend to receive a response more quickly than applications submitted in stages or without a coherent narrative.
The application in this matter was accompanied by a detailed cover letter explaining the background, the ownership structure, the regulatory history, and the steps taken to mitigate the concern that had led to the Entity List placement. The letter also addressed the distinction between the BIS measure and the OFAC regime – anticipating a question that BIS reviewers commonly raise where a financial account is involved.
Parallel to the licence application, the business engaged local counsel in the relevant jurisdiction to begin a formal review of the Entity List placement itself, with a view to a potential delisting petition. Delisting from the Entity List is a distinct process from licensing. A licence authorises a specific transaction or category of transactions; it does not remove the underlying placement. For a business that expects to have an ongoing US export-controlled supply chain, delisting is the more durable solution.
Risk flags and what the business should have done earlier
Every frozen-account matter under the EAR that we have worked through reveals the same cluster of avoidable vulnerabilities. The business in this case was not exceptional in having them; it was typical.
The first risk flag was ownership-chain opacity. The beneficial-ownership link between the US subsidiary and the Entity List company was not surfaced by the business's own screening programme. It appeared only when a counterparty's due-diligence process flagged it. A properly configured screening programme should screen not only direct counterparties but the full ownership chain to a meaningful depth – and it should re-screen periodically, not only at onboarding.
The second flag was the absence of a pre-planned response protocol for export-control account restrictions. The business had an OFAC response protocol. It did not have an EAR protocol. Those are different instruments. When the BIS action came in, the compliance team initially directed it to the OFAC response stream, which introduced delay and sent the matter to the wrong internal owners.
The third flag was the treasury team's exposure. Operating capital was concentrated in accounts held by the affected subsidiary. A more resilient treasury structure would have maintained access to funds through entities not in the same ownership chain as the restricted party. This is a structural point, not a compliance point, but it is one that counsel regularly raises in post-matter reviews.
Have you tested your own screening programme against a layered ownership scenario? Does your compliance team know the difference between an EAR freeze and an OFAC block, and does that distinction affect who handles the matter internally?
The lesson: what similar businesses should take from this matter
The core lesson is that frozen-account management under the EAR is a structured legal task, not a treasury problem. Its resolution depends on identifying the correct authorising regime, building the correct application, and managing the financial institutions in parallel. Treating it as a bank-to-bank matter, or as an OFAC problem by default, slows resolution and can cause the business to pursue the wrong authorisation route entirely.
A myth that circulates in compliance teams is that Entity List placements are only relevant if you are an exporter. That is wrong. The EAR's ownership-and-control analysis can sweep in US-registered financial accounts and domestic transactions that have no direct export dimension, because the restriction attaches to the listed person and to items and transactions subject to the EAR, not only to cross-border shipments. If your US subsidiary, your US financial account, or your US-person employees are connected to an Entity List company, your domestic operations can be affected.
The second lesson is jurisdictional clarity. Cross-border businesses almost always operate in more than one regime. The resolution of a BIS matter does not automatically resolve a concurrent OFSI or EU question, even where no separate designation exists. Managing the financial institutions in those jurisdictions requires parallel engagement, and the message to each institution needs to be calibrated to the legal position under that institution's applicable regime – not a single generic communication.
In our cross-border practice, the matters that resolve most efficiently are those where the client contacts us at the point of the freeze, not after several internal escalation rounds have consumed the available response window. Early engagement preserves options. It allows counsel to scope the matter correctly, identify the authorisation route, prepare the application, and manage the financial institutions before precautionary holds harden into formal compliance restrictions that require their own resolution process.
Related practices
- Frozen-account management under the EAR – service page covering the full scope of BIS licensing and account-restoration work
- Frozen-account management: a cross-border matter – related case comment on multi-regime account restrictions
- General-licence eligibility: an Australia matter – case comment on licensing authorisations in a comparable non-US regime