An exporter's finance team discovers that a payment has been blocked by its bank. The reason given is a flag against the counterparty on a BIS restricted-party list. The goods have already shipped. The letter of credit is on hold. Every hour of inaction compounds the commercial and legal exposure.
Frozen-account management under the Export Administration Regulations ("EAR") – the US export-control rules administered by the Bureau of Industry and Security ("BIS") – requires a defined sequence of steps: identify the legal basis for the freeze, preserve all documentation, report to the appropriate authority where required, assess licensing options, and decide on an orderly resolution strategy. The process differs meaningfully from financial-sanctions freezes under OFAC, and understanding that distinction is the first practical step.
This guide walks through the procedure step by step, identifies the points where exporters most commonly go wrong, and explains when to involve export-control counsel. It also compares the BIS / EAR position with the approach under the UK and EU regimes, so that businesses with cross-border exposure can manage the full picture from the outset.
Step 1: Identify the legal basis for the account restriction
Before any other action, a business must establish which authority and which list triggered the restriction – because the answer determines everything that follows. A BIS-driven restriction typically arises because the counterparty, end-user, or consignee appears on the Entity List, the Denied Persons List ("DPL"), or the Unverified List ("UVL"); or because the goods in question carry an Export Control Classification Number ("ECCN") that requires a licence for the destination, end-use, or end-user in question, and no licence was obtained.
This step is not formality. A freeze arising from a DPL entry carries a prohibition that differs in scope from one arising from an Entity List placement. An ECCN-based hold may be resolved through a licence exception or a formal licence application; a DPL-based hold cannot be resolved by licence at all – the denial order is an absolute prohibition during its term. Conflating the two wastes time and exposes the firm to further violations.
In our experience, firms that arrive at this stage without having separated the BIS / EAR question from a simultaneous OFAC financial-sanctions question create significant downstream confusion. A counterparty can appear on both an OFAC list and a BIS list at the same time. The remedies under each regime are distinct. Map each freeze to its legal authority before moving to resolution.
Step 2: Preserve documentation and freeze all affected records
Once the legal basis is identified, the business must immediately preserve all records relating to the transaction, the counterparty, the goods, and the screening process that preceded the shipment. This preservation obligation exists independently of any formal reporting requirement and is the foundation of every subsequent step – including any voluntary self-disclosure or licensing application.
What must be preserved? At minimum: the export licence or the licence-exception basis relied upon at the time of shipment; all end-use documentation including end-use certificates and shipper's export declarations; the screening records that existed at the time the order was accepted; all communications with the counterparty and the freight forwarder; and the bank's written explanation for the hold.
Record-keeping obligations under the EAR extend for a defined period from the date of export or the date of the relevant transaction. The applicable period is not universal – it depends on the category of record – so counsel should confirm the precise requirement for each document class. What is clear is that early destruction, even inadvertent destruction, of relevant records is treated as a separate aggravating factor in any subsequent enforcement proceeding. Do not issue a routine document-retention hold notice and assume that is sufficient; verify that the litigation and investigation hold has actually been applied to all relevant systems.
Step 3: Assess reporting and voluntary self-disclosure obligations
A voluntary self-disclosure ("VSD") to BIS is not universally required, but it is a significant mitigant if a violation has occurred. BIS's published enforcement guidance treats a timely, complete, and accurate VSD as a major mitigating factor in civil penalty calculations. The decision whether to disclose is one of the most consequential a business faces in this situation, and it should be made with export-control counsel.
The core question is whether the facts reveal an apparent violation of the EAR – for instance, exporting an ECCN-controlled item without a required licence, or continuing a transaction with a party after their Entity List placement. If the answer is yes, or if it is unclear, the VSD option must be evaluated promptly. A delay in disclosure can convert a mitigating factor into an aggravating one. In our cross-border practice, we advise clients to complete an initial scope assessment within a defined internal window so that the VSD decision is made deliberately, not by default.
The reporting position under other regimes diverges sharply here. Under OFSI's enforcement guidance, a mandatory reporting obligation arises where a financial institution knows or suspects that it holds funds belonging to a designated person; the reporting obligation is triggered by knowledge or suspicion, not by a formal finding. Under EU sanctions regulations, reporting requirements arise for financial institutions and others who hold funds of designated persons. A business with simultaneous exposure under BIS / EAR, OFSI, and EU regulations must manage three separate reporting tracks, potentially with different deadlines. This is a point at which multi-regime counsel adds material value.
Step 4: Evaluate the licensing and exception options
Where the restriction arises from an ECCN-based licence requirement rather than an absolute prohibition, the business has a path: apply for a formal BIS licence, or identify a licence exception that covers the transaction. This step requires a precise classification of the goods and a careful review of the end-user, end-use, and destination against the applicable controls.
Licence exceptions under the EAR are transaction-specific and depend on conditions that must be met at the time of export. They cannot cure a completed shipment that went forward without a required licence; they speak to prospective activity. For an ongoing relationship where the hold is on a payment for goods already exported, the more relevant analysis is whether a formal licence application can address the continued financial relationship while the broader export relationship is reviewed.
BIS licence applications are decided against a general policy framework that considers the transaction, the end-user, and the destination. Policy is not published as an absolute rule for every combination – a licensing officer assesses the specific facts. Timelines for a decision are not fixed by statute and vary with the sensitivity of the item, the end-use, and the destination. In our experience, a well-prepared application with a complete technical annex and a clear end-use statement moves faster than an application that requires the agency to ask follow-up questions.
Is there a licence exception that might apply in your case? The answer requires a classification review first. Without a confirmed ECCN and a precise statement of the end-use, the exception analysis cannot proceed reliably. We regularly advise businesses that have proceeded on an incorrect EAR99 assumption – that is, that the goods are not controlled – only to find on proper review that an ECCN applies and a licence was required.
Step 5: Structure an orderly resolution and manage the counterparty relationship
Once the legal analysis is complete and the disclosure decision has been made, the business must resolve the frozen account in a manner that is consistent with its EAR obligations and does not create new violations. This step has a commercial dimension – unwinding a credit facility or a supply arrangement with a flagged counterparty – and a legal dimension: ensuring that the unwinding itself does not constitute a prohibited transaction.
Where the counterparty is on the Denied Persons List, any continued dealing is prohibited for the duration of the denial order. There is no licensing path. The business must cease the relationship and, where funds are held, seek specific BIS guidance on the mechanics of returning or handling the frozen balance. This is the scenario that generates the most significant commercial loss, and it is the one where early identification of the list entry would have prevented the problem entirely.
Where the counterparty is on the Entity List but a licence is available in principle, the business may apply for a licence to complete specific transactions, including settlement of the frozen account. The application must describe precisely what is being authorised, and the business should not assume that a pending application permits the transaction to proceed – it does not, unless a specific authorisation to that effect has been granted.
A micro-scenario illustrates the point. In a recent matter, a trading house in the Asia-Pacific region discovered that a buyer had been added to the Entity List after a contract was signed but before shipment. The goods carried an ECCN that required a licence for that destination and end-user. We advised the client to halt the shipment, preserve all records, conduct an immediate scope review, and file a formal licence application covering both the outstanding shipment and the settlement of the partial payment already made. The application was prepared with full end-use documentation. The matter concluded without penalty, though no outcome can be guaranteed in any individual case.
How does the BIS / EAR approach compare with OFSI and EU sanctions regimes?
The BIS / EAR regime is an export-control regime, not a financial-sanctions regime in the primary sense. That distinction carries practical consequences for frozen-account management that are frequently misunderstood by compliance teams trained on OFAC and OFSI.
Under OFAC financial sanctions, a freeze applies to property in which a blocked person has any interest, however minor. The trigger is the designation on the SDN List or the operation of the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked). The property is blocked; it cannot be moved, paid, or returned without an OFAC licence.
Under OFSI and the EU's financial-sanctions regulations, a similar freeze mechanism applies to funds and economic resources belonging to, owned by, or controlled by a designated person. The UK and EU tests extend explicitly to control – not only ownership – meaning that a non-listed entity that is controlled by a designated person is caught even if the listed person owns less than a controlling stake in the narrow percentage sense. Both OFSI and the EU have a reporting obligation for financial institutions that is separate from the licensing track.
BIS's restricted-party lists operate differently. The Entity List imposes a licence requirement for exports, re-exports, and in-country transfers involving the listed entity. It does not automatically freeze all property of that entity in the way that OFAC and OFSI designations do. The financial hold that a business experiences is typically the bank's own reaction to a compliance flag – the bank applies enhanced due diligence or blocks the payment pending a review. The underlying legal question is whether the EAR required a licence for the underlying transaction, not whether the counterparty's funds are "blocked" in the OFAC sense.
This difference matters when a business is advising its board on exposure. Under OFAC or OFSI, a failure to freeze blocked funds is itself a violation. Under the EAR, the violation is the unlicensed export or transfer; the subsequent financial hold is a consequence, not an independent legal trigger. Conflating these two theories of liability leads to incorrect assessments of both the legal risk and the resolution route. Where does your analysis start – with the goods, or with the money?
Risk flags and when to involve export-control counsel
Several fact patterns consistently produce the most severe outcomes and should be treated as automatic triggers for specialist review, not internal triage. Each flag listed here reflects a pattern we regularly advise on.
- DPL or Entity List entry discovered after shipment: this is the highest-risk scenario. The BIS enforcement division treats post-shipment knowledge as an aggravated position if the business continues dealing or fails to disclose promptly.
- Incorrect EAR99 classification: a shipment processed as EAR99 (not subject to ECCN-based controls) that is subsequently found to carry a classified ECCN is a completed unlicensed export. The scope assessment must be conducted by someone with classification competence.
- Concurrent OFAC and BIS flags: a counterparty on both an OFAC list and a BIS list creates overlapping obligations with different resolution tracks. Handling them in sequence rather than in parallel wastes time and may allow the OFAC reporting window to close while BIS matters are being addressed.
- Forwarding a payment through a jurisdiction with independent controls: a payment routed through a correspondent bank in a jurisdiction that applies its own export-related financial restrictions may trigger separate reporting obligations under that jurisdiction's national instrument.
- The counterparty disputes the list entry: where the counterparty believes it has been listed in error or that the name match is a false positive, the business must not simply accept that representation without independent verification. The legal exposure rests with the exporter, not the counterparty.
Involve export-control counsel immediately where any of these flags is present. The VSD window and the licensing window both run from the point at which a violation is identified or should have been identified. Delay is almost never beneficial.
Related practices
- Frozen-account management under BIS / EAR – service page – full-service support from scope review through licence application and resolution.
- Frozen-account management under BIS / EAR: advanced guide – deeper treatment of classification, exception analysis, and multi-regime interaction.
- Frozen-account management under the Canadian regime – managing holds under Canada's autonomous sanctions and export controls.
The position above addresses the standard case. Your specific facts – the goods, the counterparty's list status, the route, and the jurisdictions in play – change the analysis materially. Contact Calder & Vance at info@caldervance.com for an initial assessment of your exposure under the EAR.