A technology exporter has a shipment in transit when the buyer's account is frozen following an Entity List addition. The goods are mid-journey. Payment instructions are blocked. The exporter's bank refuses to process clearing. What happens next, and who is responsible for what?
Frozen-account management under the Export Administration Regulations (the EAR, administered by the Bureau of Industry and Security, BIS) involves a defined sequence: identify which control applies, confirm whether a licence exception is available, halt or quarantine the affected transaction, and engage BIS directly when no exception covers the position. The EAR does not block funds in the way that OFAC sanctions do – but it does prohibit certain exports, re-exports, and transfers in country, and a frozen payment stream is often the symptom of an underlying export-control restriction that must be resolved before any funds move.
This guide walks through each procedural stage, identifies the points where businesses most often go wrong, and explains how the BIS / EAR position interacts with OFAC, the UK's ECJU, and the EU dual-use regime.
Step 1 – Identify the operative restriction and the classification of the item
The first action in any frozen-account situation under the EAR is to confirm which restriction has triggered the freeze and whether it attaches to the item, the party, or the transaction itself. Under the EAR, restrictions arise through three distinct mechanisms: the Commerce Control List (CCL, the tiered list of controlled items identified by Export Control Classification Number, or ECCN) – which specifies which items require a licence to which destinations; the Entity List (a list of foreign parties against whom a licence requirement applies for all EAR-controlled items); and the Denied Persons List (DPL, a list of parties subject to a denial order, prohibiting virtually all EAR transactions). A payment freeze may result from any one of these, or from an interaction between them.
Confirming the ECCN of the goods is the starting point. If an item is designated EAR99 – the residual category for items subject to the EAR but not listed on the CCL – it carries no inherent licence requirement unless a party-based restriction applies. If the item carries an ECCN with licence requirements for the destination or end-use in question, those requirements govern independently of any party-based control. In our experience, businesses often assume that a party-based freeze releases once a party is removed from a list; in fact, if the item itself requires a licence to that destination, the licence requirement persists regardless of party status.
Verify both dimensions before taking any further step. A single incorrect classification at this stage causes every subsequent decision to be wrong.
Step 2 – Screen the parties against the Entity List, the Denied Persons List, and the SDN List
Once the item classification is confirmed, screen all parties to the transaction – buyer, consignee, freight forwarder, end-user, and any intermediate broker – against the current Entity List, the DPL, and OFAC's Specially Designated Nationals and Blocked Persons List (the SDN List). These are maintained by different agencies and carry different legal consequences. BIS administers the Entity List and the DPL under IEEPA and the Export Control Reform Act; OFAC administers the SDN List under a range of authorities including IEEPA. The two regimes interact but are not coextensive.
A party may appear on the Entity List but not on the SDN List, or vice versa. An Entity List designation requires a BIS licence for exports of EAR-controlled items to that party; an SDN designation blocks all property and interests in property under OFAC's authority, including funds. When a party appears on both lists, both sets of obligations apply simultaneously, and the stricter prohibition governs. This is the point at which many compliance teams encounter genuine uncertainty. Does the OFAC block supersede the BIS licensing pathway? No – they are parallel and must each be addressed independently.
In a recent matter, a trading house received a payment-refusal notice from its correspondent bank. The bank had flagged the consignee as a listed entity. On review, the consignee appeared on the Entity List but not the SDN List. The operative restriction was a BIS licence requirement, not an OFAC asset freeze. The path forward was a BIS licence application, not an OFAC specific-licence application. The distinction reduced the response timeline significantly.
Step 3 – Determine whether a licence exception covers the position
Under the EAR, a licence exception is a standing authorisation that permits a defined category of transactions without a separate application to BIS – provided all the conditions of the exception are met. This is the analogue of a general licence under OFAC. Before preparing any formal licence application, confirm whether an applicable licence exception is available for the item, the destination, the party, and the end-use.
Several exceptions are relevant in frozen-account situations. The License Exception STA (Strategic Trade Authorisation) permits certain exports of controlled items to governments and nationals of low-risk destinations. The License Exception TMP covers temporary exports and certain returns. The License Exception RPL authorises replacement parts. None of these exceptions is available when the consignee is on the Entity List or the DPL – party-based restrictions are not waived by general exceptions unless BIS has specifically noted otherwise in the Entity List entry. Read the Entity List entry itself. Some entries include a specific footnote authorising a defined transaction type even for that listed party; others provide a total bar. The entry controls.
What is the consequence of relying on an exception that does not apply? Proceeding without a required licence is an EAR violation. The transaction becomes an unlicensed export. That fact does not change because the exporter genuinely believed an exception covered it. Good faith is a mitigating factor in enforcement proceedings, but it does not constitute a defence to the underlying violation. Verify the exception eligibility in writing before proceeding.
Step 4 – Quarantine the transaction and preserve records
When no licence exception covers the position and a formal BIS licence application is required, the transaction must be quarantined. Quarantine means stopping the physical movement of goods and all associated financial transfers. It is not sufficient to halt only the payment; the goods themselves must not continue in transit to the named consignee without a valid authorisation.
Record-keeping begins at this stage. The EAR requires exporters to retain records of all transactions – including the classification, the screening, the licence application, any correspondence with BIS, and the ultimate disposition of the goods – for a defined period. Verify the current record-keeping period against the applicable regime before relying on any specific figure. In our cross-border practice, we advise clients to treat record-keeping as an active compliance obligation, not an administrative afterthought. A well-maintained contemporaneous record is often the difference between a matter that closes with a warning and one that proceeds to a formal penalty process.
Quarantine also requires internal escalation. The compliance function should notify senior management and, where appropriate, legal counsel at the point of quarantine, not after a decision has been made about how to proceed. Early escalation preserves options.
Step 5 – Prepare and submit the BIS licence application
Where no exception applies, a licence application to BIS through the Simplified Network Application Re-engineered platform (SNAP-R) is the formal route to authorise the transaction. The application requires, among other elements: the classification of the item (ECCN or EAR99 confirmation); the parties to the transaction with their full legal names and addresses; the end-use and end-user; and a statement of the grounds for approval.
The processing timeline for a BIS licence application is not fixed in the EAR itself. In our experience, routine applications for commercial items to allied destinations resolve within a few weeks of submission; applications involving advanced technology, listed parties, or sensitive end-uses take materially longer. BIS may issue a request for additional information (RFI), which pauses the clock. Plan for this. A transaction that requires funds to move by a contractual deadline should have the licence application submitted as early as possible, with the counterparty informed of the regulatory constraint. Do not present a BIS RFI to a counterparty as an unexplained delay.
The cross-border angle matters here. A UK exporter re-exporting US-origin goods is subject to BIS extraterritorial jurisdiction under the EAR's re-export provisions. That exporter cannot rely on ECJU (the UK's export-licensing authority) to resolve a BIS licence requirement. The two licensing systems are independent. A valid ECJU licence does not substitute for a BIS licence where US jurisdiction attaches. This is one of the most consistent sources of error we encounter in cross-border trade matters.
Step 6 – Voluntary self-disclosure where a violation has already occurred
If review of the transaction reveals that goods were exported, re-exported, or transferred without a required licence – or that a payment moved under the cover of an exception that did not in fact apply – a voluntary self-disclosure (VSD) to BIS should be considered without delay. A VSD is a formal submission to BIS's Office of Export Enforcement disclosing the apparent violation, the parties involved, and the steps taken to prevent recurrence.
BIS's enforcement policy, as stated in its public guidelines, treats a timely and complete VSD as a significant mitigating factor when calculating any penalty. It does not guarantee a particular outcome. The absence of a VSD when a violation is later independently discovered by BIS is itself treated as an aggravating factor. The decision whether to submit a VSD and its timing and scope has legal consequences. Counsel should be involved in that decision before any submission is made.
The position is broadly analogous under OFAC for sanctions-related violations and under OFSI in the United Kingdom for financial-sanctions breaches. Each regime maintains its own VSD process, with its own timelines and procedural requirements. A business that has triggered obligations under both BIS and OFAC – for example, where an export-control violation also involves a blocked party – must file separately with each authority. A BIS VSD does not satisfy the OFAC obligation, and vice versa.
The position above covers the standard procedural path. Your facts – the goods, the route, the parties, the specific list entries in play, and any prior dealings with the same counterparty – change the analysis at every step.
For a confidential review of your position, contact Calder & Vance at info@caldervance.com.
Risk flags in frozen-account management under the EAR
Several recurring patterns produce enforcement exposure in EAR frozen-account situations, and recognising them early significantly reduces risk.
Incorrect or absent ECCN classification. Proceeding on the assumption that goods are EAR99 without a formal classification review is a common error. Items that appear commercial – certain electronics, sensor components, chemical precursors – may carry specific ECCNs with licence requirements that are not apparent from a product description alone. A classification review is not optional once a transaction is flagged.
Incomplete party screening. Screening only the direct buyer while overlooking intermediate freight forwarders, customs agents, or named end-users is a consistent gap. The EAR prohibits exports to listed parties at any point in the distribution chain, not only to the primary purchaser. The screening obligation extends to the end-user and to any party with a decision-making role over the final disposition of the goods.
Conflating BIS and OFAC obligations. Obtaining a BIS licence does not resolve an OFAC asset-blocking obligation. These are parallel regimes with different authorities, different lists, and different licensing procedures. A business that satisfies one without addressing the other remains in violation of the unsatisfied regime.
Over-reliance on automated screening tools. Screening platforms vary in their coverage and update frequency. A party may be added to the Entity List and the screening system may not yet reflect the update. Manual verification against the live BIS and OFAC databases is a necessary check, particularly for transactions in higher-risk sectors or destinations. Are your screening tools being tested and updated at a frequency that matches the pace of list changes?
Failing to assess extraterritorial reach. European, Asian, and other non-US exporters regularly underestimate the reach of BIS jurisdiction over items incorporating US-origin content or US-origin technology. The de minimis and foreign direct product rules extend EAR jurisdiction to foreign-produced items in defined circumstances. A UK, EU, or Singapore exporter dealing in items with US-origin components is not outside BIS jurisdiction merely because the transaction is conducted in a non-US currency or routed through a non-US bank.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time.
For a confidential discussion of a flagged transaction or a potential violation, contact us at info@caldervance.com.
Cross-regime comparison: how BIS / EAR frozen-account management compares with OFAC, OFSI, and the EU
A cross-border business managing a frozen-account situation often faces more than one regime simultaneously. Understanding where the regimes align and where they diverge is essential to building a coherent response.
Under OFAC, the operative concept is asset blocking: property of a blocked person is frozen, and any dealing with it – including releasing a payment or shipping goods – requires an OFAC specific licence or the cover of an applicable general licence. The BIS / EAR regime does not operate on an asset-blocking model. The EAR controls the act of export, re-export, or transfer in country. A payment associated with an EAR-controlled transaction may be frozen not because the funds are blocked property but because the counterparty bank has declined to process a payment pending confirmation that the underlying transaction is licensed. These are legally distinct situations requiring different remedies.
OFSI in the United Kingdom administers financial-sanctions regulations under the Sanctions and Anti-Money Laundering Act (SAMLA). The OFSI licensing process and the BIS SNAP-R process are independent. Where a transaction involves UK financial institutions or UK-incorporated entities, and also involves US-origin goods subject to the EAR, both OFSI and BIS may have jurisdiction. The licensing process under OFSI applies to financial-sanctions restrictions; ECJU licensing applies to UK export-control restrictions. Neither substitutes for BIS.
The EU dual-use regime, governed by the applicable Council Regulation, similarly operates on an export-authorisation model rather than an asset-blocking model. The EU's control list and the EAR's CCL are broadly aligned in structure through the Wassenaar Arrangement framework, but the lists are not identical. An item may require a licence under the EAR to a given destination but not under the EU regime, or the converse. Do not assume alignment. Verify against each applicable regime's list separately.
Canada's export-control regime, administered by Global Affairs Canada, similarly operates independently of the EAR. A Canadian exporter of US-origin goods must comply with both Canadian rules and BIS jurisdiction. The SECO regime in Switzerland applies Swiss export-control obligations to Swiss exporters independently of EAR reach, though items subject to the EAR passing through Swiss hands may also engage Swiss controls. In our cross-border practice, we regularly advise on matters where three or four regimes apply to a single transaction, each with its own list, its own licensing authority, and its own enforcement posture.
Related practices
- BIS / EAR licensing service – direct instruction and management of BIS licence applications and account release
- Frozen-account management under Canada's regime – parallel guide to the GAC process and comparison with BIS / EAR
- Canada frozen-account management: advanced considerations – deeper analysis of Canadian controls, re-export, and US nexus