A freight forwarder receives a shipment-refusal from a US carrier. The stated reason: the consignee appears on the BIS Entity List. The forwarder's client insists it is a different company – same name, different country, no connection to the listed entity. The export is stalled. The client faces reputational damage and a broken supply chain. How does this get resolved, and how quickly?
Mistaken-identity removals – the process of demonstrating that a screened party is not the listed person or entity – differ materially between the US Bureau of Industry and Security regime under the Export Administration Regulations and the EU sanctions removal mechanisms. Under BIS and the EAR (the Export Administration Regulations, the primary US export-control instrument administered by the Commerce Department's Bureau of Industry and Security), a business bears the burden of establishing the distinction with supporting documentation submitted to BIS directly. Under EU Council regulations, the mechanism turns on a formal annulment action or an administrative correction request, and the procedural route depends on whether the listing is a UN-derived designation or an autonomous EU measure.
This analysis maps those two regimes against each other, identifies where the procedural paths diverge, and sets out the risk flags that cross-border businesses consistently miss when a mistaken-identity issue arises in an export-control or sanctions context.
What is a mistaken-identity removal, and why does it arise?
A mistaken-identity removal is the administrative or legal process by which a party demonstrates that it is not the specific person or entity named on a restricted-party list, and thereby secures removal of the erroneous match from the operative screening result. It is distinct from a delisting petition – which challenges the substantive grounds for a designation – because the party seeking relief does not contest the legitimacy of the listing itself; it contests only the identification.
Mistaken-identity issues arise for several structural reasons. Screening tools rely on name-matching algorithms. Common corporate names, transliteration variants, and shared addresses across unrelated entities all generate false positives. In our cross-border practice, we regularly advise businesses where the listed entity and the legitimate counterparty share a name, a jurisdiction of incorporation, or an ownership structure that superficially resembles the listed profile. The practical consequence is immediate: a carrier, bank, or platform applies a transaction block before any human review occurs.
The problem is compounded when the business operates across both the US and the EU. A name that appears on the BIS Entity List may not appear on the EU Consolidated List, or vice versa. A match on one list does not produce a match on the other, yet both lists are fed into a single screening system. The result is an error that looks bilateral but has a unilateral source – and the remedy differs depending on which regime is in play.
As of early 2026, the volume of entries on major restricted-party lists continues to grow as new designations and export-control additions are made at pace. The probability of a false-positive match increases proportionately. Businesses that have not stress-tested their screening logic against their actual counterparty base are operating with a structural blind spot.
How does BIS handle a mistaken-identity removal under the EAR?
Under the EAR, a mistaken-identity removal from the BIS Entity List begins with a written request to the End-User Review Committee – the interagency body that administers the Entity List – supported by documentation establishing that the screened party and the listed entity are distinct persons. The burden rests on the requesting party, and BIS does not operate a fixed statutory timetable for resolving the request once submitted.
The documentation package is the critical instrument. BIS expects evidence that addresses each of the identifying characteristics used in the original listing: the legal name, any aliases, the country of incorporation or operation, the address, and any ownership or control linkages cited in the listing notice. A submission that addresses name similarity alone, without engaging the address, jurisdiction, and operational profile, will be treated as incomplete.
In our experience, businesses underestimate how granular BIS expects this evidence to be. A certificate of incorporation showing a different registered address is necessary but rarely sufficient. Corporate registry extracts, commercial registration documents in the relevant language with certified translations, ownership charts verified against official sources, and operational evidence – such as a distinct product line, a separate client base, and a different founding history – all contribute to a record that distinguishes the parties clearly.
There is a secondary route: under the EAR, exporters may also approach BIS through the commodity classification and advisory-opinion process to confirm that a specific transaction does not involve the listed entity. This does not remove the Entity List entry, but it can unblock an individual shipment while the removal request is processed. The two processes run in parallel, and using them together is often the most practical response to a commercial deadline. What does a business do, though, when the same counterparty also triggers a match under EU rules?
How does the EU approach the same problem?
Under EU Council regulations, the procedural path for a mistaken-identity issue depends on the origin of the listing. Where the EU listing derives from a UN Security Council designation, the competent authority is not the EU itself but the UN Sanctions Committee, and the EU's role is to implement the UN list rather than to maintain an independent record. In those cases, a mistaken-identity correction must begin at the UN level, through the Focal Point mechanism or the relevant Committee.
Where the listing is an autonomous EU measure – adopted by the Council on its own authority under the applicable Council Decision and Regulation – the remedies are different. An affected party that is not itself the designated person has two routes. The first is an administrative approach to the competent national authority of the EU member state in which it operates, presenting evidence of the distinction. Member states have varying practices on how they handle such submissions, and the outcome is not always a formal EU-level correction.
The second route is a direct action before the EU General Court under the relevant treaty provisions on annulment. This route is principally available to designated parties, but an affected non-listed party that suffers direct consequences from an erroneous identification may have standing in certain circumstances. In practice, the General Court route is slow and expensive relative to the commercial urgency of unblocking a transaction. The more common EU-level response is a practical clarification from the competent national authority combined with direct communication to the screening operator.
EU autonomous listings carry an obligation on the Council to provide reasons, and the statement of reasons is the document against which a mistaken-identity argument is tested. If the reasons identify the entity by reference to a specific address, registration number, or ownership structure, and those details do not match the screened party, the distinction can often be established on the face of the official record. That is a procedural advantage that the BIS Entity List process does not always replicate, because Entity List entries vary in the level of identifying detail they include.
Where do the two regimes diverge most sharply?
The most significant divergence between BIS and the EU on mistaken-identity removals is the availability of a formal, structured administrative correction mechanism with defined procedural steps. BIS operates a functional process through the End-User Review Committee, but it is not bound by a statutory deadline, and the process does not carry an independent right of appeal if the Committee declines to remove the entry. The EU administrative route is similarly informal at the national level, and the General Court route – though structured – is slow.
The second divergence is the role of identification detail in the listing. EU autonomous Council regulations are required to include a statement of reasons, and those reasons typically carry enough identifying detail to allow a distinct party to distinguish itself on the face of the official record. BIS Entity List entries vary considerably in their specificity. Some entries carry detailed addresses and registration particulars; others carry only a name and a country. Where the entry is sparse, the burden of proof on the removing party is correspondingly heavier, because there is less official text against which to test the distinction.
Third, the extraterritorial reach of the two regimes creates asymmetric risk. BIS controls apply to US-origin goods, software, and technology wherever they travel, and to all transactions involving items on the Commerce Control List regardless of the exporter's nationality if the items are of US origin. A mistaken-identity issue that stalls a shipment under the EAR may therefore affect exporters in multiple jurisdictions simultaneously. The EU regime's territorial scope is different: it applies to EU-nexus transactions, and a mistaken-identity issue arising under EU rules does not automatically create a BIS problem, or vice versa.
For a business operating in both the US and the EU, this asymmetry means that resolving the BIS issue and the EU issue are parallel exercises requiring parallel processes – and they are not always aligned in pace or outcome. We regularly advise clients who have resolved the BIS matter but find the EU match still active, or who have obtained an EU national authority clarification that carries no weight in a US export-compliance review.
What are the risk flags businesses consistently miss?
The most common error in a mistaken-identity matter is treating the issue as a screening-system problem rather than a legal one. A screening alert is a trigger, not a conclusion. The legal analysis of whether a specific transaction is prohibited requires human review of the actual listing, its identifying particulars, and the facts of the specific counterparty. Businesses that resolve the alert by adjusting the screening threshold or suppressing the match without a documented legal analysis expose themselves to enforcement risk if the counterparty later turns out to be the listed entity.
The second risk flag is inadequate documentation at the point of the initial transaction. When a business concludes that a match is a false positive and proceeds with the shipment, the contemporaneous documentation of that conclusion is the compliance record. If BIS or the relevant EU authority later questions the decision, the record of the analysis – who reviewed it, what evidence was considered, what the conclusion was, and when it was made – is what stands between the business and a finding of a compliance failure. In our experience, that contemporaneous record is absent in a significant proportion of the cases that come to us after the fact.
Third: do not assume that a negative determination by one regime is accepted by another. A BIS advisory opinion or a positive result from the End-User Review Committee does not bind OFAC, EU authorities, or any other regime. Each list is maintained independently, and a finding of non-identity under one regime must be obtained separately under each regime in play. Cross-regime reliance is a systematic error that creates gaps in compliance coverage.
Fourth: the timeline pressure of a commercial transaction can push businesses into informal workarounds that create greater legal exposure than the original match. Rerouting a shipment through an intermediate country, substituting a different legal entity as the consignee, or characterising the goods differently to avoid a flagged classification – each of these creates serious legal risk under the EAR and the relevant EU rules, irrespective of whether the original match was a false positive. The remedy for a mistaken-identity issue is a formal resolution, not a transactional workaround.
How should a cross-border business structure its response?
A structured response to a mistaken-identity alert begins with a legal hold: suspend the transaction, do not destroy records, and do not communicate informally with the counterparty about the nature of the match until the legal position is clear. That initial step preserves options and prevents inadvertent disclosure of potentially sensitive compliance information.
The second step is a factual investigation. Pull the listing in full from the official source – the BIS Entity List as published in the Federal Register and maintained on the BIS website, or the EU Consolidated List as maintained by the European External Action Service. Compare the listing's identifying particulars, field by field, against the verified corporate data of the screened counterparty. This comparison is the foundation of the mistaken-identity argument and must be documented.
The third step is to identify the remedy route. Under BIS: prepare the End-User Review Committee submission. Under the EU: determine whether the listing is UN-derived or autonomous, and select the administrative or judicial route accordingly. Where both regimes are in play, the processes should be initiated in parallel, not sequentially.
The fourth step is to manage the commercial relationship. The counterparty will need to know that the transaction is under review and that a formal process is under way. Communicating that a mistaken-identity process has been initiated – without disclosing the details of the legal analysis – is usually acceptable. Do not represent to the counterparty that the match is definitely erroneous until the formal process confirms it.
In a recent matter, a manufacturing business in an EU member state faced a transaction block because its distributor in a third country shared a name with an entity on the BIS Entity List. We mapped the listing's identifying particulars against the distributor's verified corporate registry records, assembled a documentation package addressing name, address, incorporation history, and ownership structure, and submitted the package to BIS while simultaneously preparing a statement of distinction for the EU competent authority. The commercial transaction was unblocked within a defined review window, with a documented compliance record in place.
The position above covers the structured case. Your facts – the specific listing, the level of identifying detail, the regime in play, and the commercial deadline – change the analysis materially and may require a different approach.
For a confidential assessment of a mistaken-identity issue under the BIS, EU, or any other regime, contact Calder & Vance at info@caldervance.com.
When should counsel be involved?
Counsel should be involved before the first substantive communication with BIS or the relevant EU authority. Submissions to the End-User Review Committee and requests to EU competent authorities are part of the official record of the matter. A submission that is incomplete, factually imprecise, or legally misconstrued can narrow the options available in a later challenge. Early involvement of qualified export-control counsel is not a luxury; it is a structural safeguard.
There is a common misconception in this area. Many businesses believe that a mistaken-identity issue is a minor administrative matter that can be handled internally without specialist input – that it is, essentially, a paperwork problem. That characterisation is incorrect. The End-User Review Committee submission is a regulatory filing. The EU administrative process produces a record that can be used in subsequent legal proceedings. And the decision to proceed with a transaction on the basis of an unresolved match, even a match that the business believes is a false positive, carries enforcement risk that is real and not theoretical.
Specialist counsel brings three things that internal teams typically lack: direct experience of what the reviewing authority expects to see, the capacity to assess whether the documented distinction is legally sufficient under the applicable standard, and the ability to engage the authority directly if the initial submission is questioned. Where the commercial deadline is short, that experience difference can be the factor that determines whether the transaction closes.
If a transaction has already been flagged, or a filing is under review, an early assessment can preserve options that narrow with time. Contact us at info@caldervance.com.
Related practices
- Delisting evidence package – Australia regime – building a structured evidentiary record for autonomous Australian sanction removal requests.
- Mistaken-identity removals: BIS / EAR vs EU – extended analysis – deeper treatment of the procedural comparison and multi-regime coordination.
- Mistaken-identity removals: OFAC vs BIS / EAR – how the OFAC and BIS approaches to false-positive identification differ in practice.