A cross-border payment firm flags a transaction. Its screening system has matched a customer's name against the SDN List (OFAC's list of Specially Designated Nationals and blocked persons). The customer is not the designated individual. The names are similar; the date of birth is different; the nationality is different. Yet the account is frozen, the payment is held, and the customer is demanding answers. This is a mistaken-identity situation – and the routes for resolving it under OFAC and under the EU differ in ways that most businesses do not map until the problem is already live.
Mistaken-identity removal under OFAC is a distinct administrative procedure, separate from a delisting petition, governed by rules under IEEPA. The EU operates a parallel but structurally different process under the relevant Council regulations. As of February 2026, the procedural gap between these two regimes – in timelines, evidence standards, and the scope of what the authority will reconsider – is the primary source of delay and error for cross-border businesses managing a live hit.
This analysis maps the divergence criterion by criterion, identifies the risk flags that practitioners see most often, and sets out when external counsel changes the outcome.
What is a mistaken-identity removal, and why does it differ from delisting?
A mistaken-identity removal is a request to an authority to confirm that a screened party is not the same person as the designated individual who shares their name – and to unblock transactions or relationships on that basis. It is not a delisting petition, which challenges whether the designation itself was lawful or justified. The distinction is critical and frequently misunderstood.
Under OFAC, a business or individual can submit an OFAC reconsideration request (informally called an "unblocking" or "mistaken identity" submission) asking OFAC to confirm that the screened party is not the SDN. OFAC has a separate mechanism for this: it does not require the screened party to argue the merits of the underlying designation, only to demonstrate that identity does not match. The consequence is different too. A successful mistaken-identity resolution under OFAC does not remove anyone from the SDN List. It produces a letter or a general licence-type confirmation that the specific party is not the person listed. The SDN entry remains intact.
The EU process is governed by the relevant Council regulation and administrative practice of the relevant Council working group. The EU also distinguishes between a delisting request – asking the Council to revoke or modify a designation – and an "affected-person" clarification, where an individual or entity demonstrates that they are not the named designee. In practice, however, EU member states and EU-regulated institutions approach these two routes less consistently than OFAC does. In our experience, the EU path to a mistaken-identity resolution involves more procedural uncertainty precisely because the EU lacks a single administrative gateway equivalent to OFAC's dedicated enquiry process.
Why does this matter for a business? Because the wrong route adds weeks of delay. Filing a full delisting petition when a mistaken-identity submission would suffice exhausts resources and gives the authority a harder question to answer. Filing a short identity clarification when the facts actually require a full merits challenge wastes the submission window.
How does OFAC handle mistaken-identity removals?
OFAC administers mistaken-identity requests through its Office of Global Targeting and, for licensing matters, through its Licensing Division. A party submitting a mistaken-identity request to OFAC must provide documentary evidence that distinguishes them from the SDN entry: full legal name, date and place of birth, nationality, identification documents, address history, and any other identifiers that demonstrate the divergence.
OFAC's matching criteria under IEEPA-based programmes require that a blocking action be supported by a reasonable match against an SDN entry. Where a financial institution or other regulated person has blocked property believing it to be associated with an SDN, and the true owner can demonstrate they are not that SDN, OFAC can issue guidance – and in appropriate cases a specific licence authorising unblocking – on that basis. The burden is on the party seeking the removal to produce evidence sufficient to satisfy OFAC that the match was erroneous.
Timelines are not fixed by statute in the way some applicants expect. OFAC processes vary by the complexity of the evidence and the programme involved. In our practice, well-documented mistaken-identity submissions tend to receive a substantive response faster than a contested delisting petition, but the process can still take several weeks. There is no published processing-time guarantee. Businesses that plan around an assumption of days rather than weeks regularly encounter difficulty.
One practical point that practitioners note: OFAC's response to a mistaken-identity submission may be a specific licence (authorising the release of blocked funds or property), or a letter confirming non-match, or a request for additional information. Each response type has a different implication for the regulated institution holding the blocked property. The institution needs clear written direction before it acts – a verbal confirmation from an OFAC officer is not sufficient basis for unblocking.
How does the EU handle mistaken-identity removals?
The EU does not operate a single centralised mistaken-identity gateway equivalent to OFAC's process. Under the relevant Council regulation, EU member states are competent authorities for administering the regulation within their territory. This means that a business seeking clarification that a screened party is not the EU-designated person must, in the first instance, approach the competent authority of the member state in which it is established or in which the relevant transaction is occurring.
Member state competent authorities vary in their resources, their speed, and their approach to evidence. Some have dedicated sanctions teams with established procedures for identity-clarification requests. Others handle these enquiries through general financial-intelligence or export-licensing structures, and the response time and procedural rigour vary accordingly. This fragmentation is the single biggest structural difference between the EU and OFAC processes.
At the EU level, the Council's working group on sanctions (RELEX) manages the underlying designations. An individual or entity that believes they have been listed in error – or that they are being treated as listed in error because of a name match with a designated person – can ultimately seek a review by the Council. If the Council declines, the EU General Court is available for an annulment action under the relevant treaty provisions. But that is the long route and is appropriate when the designation itself is disputed, not merely when a name collision has occurred.
For pure mistaken-identity situations – where the screened party can demonstrate beyond reasonable argument that they are not the designated person – the practical route is a well-documented submission to the relevant member state competent authority. The submission should address every identifier in the EU consolidated list entry: name and any aliases, date and place of birth, nationality, address, identification document numbers, and any associated-entity or associated-vessel information. The more systematically the submission addresses each data point in the list entry, the faster the competent authority can confirm a non-match.
Where do the regimes diverge most sharply?
Four divergence points define the practical difference between the OFAC and EU paths.
First, the single-authority versus multi-authority structure. OFAC is the single US authority for the SDN List. A submission goes to one place; one authority responds; one written confirmation resolves the matter across all US-regulated persons. The EU has no equivalent. A confirmation from one member state competent authority does not automatically bind institutions in other member states. A business with relationships in multiple EU jurisdictions may need separate clarifications in each, or may need to seek guidance from the Council's RELEX working group to produce an instrument with cross-member-state effect.
Second, the evidentiary threshold and documentary standard. OFAC's mistaken-identity process is well-established and practitioners have a reasonably clear sense of what a complete submission looks like. The EU competent authority process is less codified. Some member states have published guidance; others have not. In our cross-border practice, the most common cause of delay in an EU mistaken-identity matter is an incomplete first submission that does not address all identifiers systematically.
Third, the interaction with blocking obligations. Under OFAC, a financial institution that has blocked property pending a mistaken-identity determination has a specific legal obligation to maintain the block until it receives a written authorisation to release. Under the EU regime, the obligation to freeze is equally firm, but the mechanism for releasing the freeze is managed through the competent authority or, in some cases, through a derogation (licence). The procedural route for release is not always as clearly prescribed as the OFAC unblocking-licence mechanism, and institutions sometimes act on informal guidance, creating compliance risk of their own.
Fourth, the appeal route when the clarification is refused. Under OFAC, a refusal to confirm a non-match or issue an unblocking specific licence is subject to an administrative review, and ultimately to challenge in US federal court under the applicable administrative-law standard. Under the EU, a refusal at the member state level can be challenged before the relevant national court; a refusal at the Council level can be challenged by annulment action before the EU General Court, with appeal to the Court of Justice. The EU judicial route is longer and more expensive, but the EU General Court has a developed body of case law on the evidentiary standard for designation and for identity.
For a business operating across both regimes simultaneously, these four divergences mean that a single mistaken-identity event can require parallel submissions to OFAC and to one or more EU competent authorities, with different evidentiary packages, different response timelines, and different release mechanisms. Co-ordinating those two tracks is where specialist cross-border counsel adds the most immediate practical value.
What risk flags do practitioners see most often?
Mistaken-identity situations produce recurring failure patterns. Recognising them early reduces the cost and delay of resolution.
Screening-tool over-reliance. A screening tool that flags a name match and auto-freezes without presenting the identifier comparison to a human reviewer creates the conditions for a mistaken-identity block to persist far longer than necessary. The tool's job is to surface the potential match; the compliance officer's job is to assess the identifiers. Programmes that skip that human layer regularly generate protracted mistaken-identity cases.
Partial identifier packages are the second failure mode. A submission to OFAC or to an EU competent authority that provides only a name and a passport number, without addressing nationality, date of birth, address history, and the specific identifiers listed in the designation entry, will almost certainly draw a request for further information. That request adds weeks. We regularly advise clients to treat the designation-list entry as a checklist: every data point in the entry should be addressed in the submission, either confirming a difference or explaining why a particular identifier is unavailable.
Confusing the process with a delisting. A business that has screened a counterparty who is genuinely not the designated person does not need to challenge the designation on its merits. It needs to demonstrate identity divergence. Framing the submission as a merits challenge – arguing that the designation is unjustified – invites the authority to engage with that question, slows the process, and sometimes produces a response that addresses the wrong issue entirely.
Failure to manage the institution holding the block. The screened party's legal problem is not the only problem in the room. The institution holding the blocked funds or frozen account has its own obligations and its own compliance risk. If that institution is not kept informed of the submission, its timeline, and the expected form of the response, it will often take its own independent legal advice – sometimes leading to conflicting positions on what documentation is required to release the funds. Co-ordinating the submission and the institution's compliance response from the outset is faster and cheaper than resolving the conflict afterwards.
Secondary-sanctions exposure in multi-regime situations. Where the screened party's name appears on both the SDN List and an EU consolidated list entry – not because they are a single designation duplicated across regimes, but because two different regimes happen to list a person with a similar name – resolving the OFAC track does not resolve the EU track. Cross-regime overlap is a real source of confusion, and a resolution letter from OFAC carries no weight before an EU competent authority.
What should a cross-border business do when a mistaken-identity hit occurs?
The first action is not to submit anything. It is to assess the hit carefully.
Compare every identifier available for the screened party against the designation entry: name and aliases, date of birth, nationality, identification documents, known addresses, associated entities, and any other identifiers in the list entry. The comparison is the submission. If the identifiers clearly diverge across multiple data points, the submission should document that divergence comprehensively and without argument on the merits of the designation.
Second, identify which regimes are in play. A payment running through a US correspondent bank creates US sanctions exposure regardless of where the parties are established. An EU-regulated institution faces EU obligations regardless of where the transaction originates. If both OFAC and the EU are relevant, prepare parallel submissions. The submissions should not be identical: the OFAC submission follows OFAC's established process; the EU submission should be structured to address the specific member state competent authority's requirements.
Third, maintain the block or freeze until written authorisation to release is obtained. Acting on informal indications – a phone call from an OFAC officer, an email from a member state contact that does not constitute a formal decision – creates compliance risk for the institution and potentially for the party that requested early release. The cost of waiting for a formal written response is almost always lower than the cost of defending a premature release.
Fourth, document everything. Record the date and nature of the hit, the identifiers comparison, the date of submission, and all communications with the authority. Good documentation accelerates the authority's review and, if the matter is later challenged, provides the evidentiary foundation for any appeal.
Consider whether counsel is needed early. In straightforward cases with clear identifier divergence, a well-structured submission by an experienced in-house compliance team can resolve the matter. Where the identifier divergence is ambiguous, where the situation involves both OFAC and EU tracks, where the institution is seeking legal assurance before releasing significant value, or where the authority has already requested additional information, external counsel with direct experience in this process materially improves both the speed and quality of the outcome.
Is there a myth that one regime is simply easier than the other?
There is. A widely held view in in-house compliance circles holds that OFAC mistaken-identity submissions are slower and more bureaucratic than EU processes, because OFAC is a single US federal agency with a large caseload. The reverse is often true in practice.
OFAC's single-authority structure and its established process for mistaken-identity submissions – with a clear procedure, a defined evidence standard, and a written output that resolves the matter across all US-regulated persons – frequently produces resolution faster and more predictably than the EU's fragmented multi-authority model. The EU's multi-member-state architecture means that a business with pan-European relationships may need to manage several separate competent authority processes simultaneously, each with its own timeline and its own evidential preferences.
The myth of EU speed derives partly from the fact that some EU competent authorities with dedicated, well-resourced sanctions teams do process straightforward mistaken-identity clarifications quickly. But experience is uneven across member states, and the absence of a centralised EU gateway means there is no mechanism to ensure consistency. In our cross-border practice, the total elapsed time to achieve full resolution – across all affected institutions and jurisdictions – is typically longer for multi-EU-jurisdiction situations than for single-programme OFAC matters of comparable complexity.
The practical implication: do not plan your resolution timeline based on assumptions about which regime will be faster. Assess the specific member state or states involved, the OFAC programme in question, the complexity of the identifier divergence, and the volume of the blocked property. Plan for the slower track; work the faster one in parallel.
The position above covers the standard case. Your facts – the counterparty's specific identifiers, the regimes in play, the institutions holding the block, and the value involved – change the analysis materially. For a confidential review of a live mistaken-identity situation, contact Calder & Vance at info@caldervance.com.
Related practices
- Delisting evidence package – Australia – building the evidentiary foundation for a formal delisting request under the Australian autonomous-sanctions regime
- Mistaken-identity removals: OFSI vs Australia – how the UK and Australian regimes compare on process, evidence, and timelines
- Mistaken-identity removals: OFSI vs Australia (continued) – further analysis of divergence between OFSI and Australian competent-authority processes