A freight forwarder's name matches a listed individual by one letter. An automated screening system flags the transaction. The bank freezes the account. The business cannot pay staff or suppliers. The problem is not a sanctions violation – it is a data error. But under OFAC's rules, the practical effect is identical until the record is corrected.
Mistaken-identity removals under OFAC address a specific failure mode: a person or entity whose name, date of birth, or identifying details are sufficiently similar to a listed party that automated and manual screening produces false positives that block legitimate activity. OFAC administers a defined administrative procedure under IEEPA and related authority to remove erroneous matches from the SDN List (OFAC's list of Specially Designated Nationals and blocked persons) and to issue corrected identifying information. Resolution typically requires a structured submission supported by identity documentation, and the timeline depends on the clarity of the evidentiary record.
This briefing explains the governing authority, the applicable test, the submission procedure, how the UK and EU handle comparable situations, and the practical steps a business or individual should take as of early 2026.
Who administers mistaken-identity removals, and what is the legal basis?
OFAC administers the SDN List and holds exclusive authority to add, amend, or remove entries under the powers delegated to it through IEEPA, the Trading with the Enemy Act, and programme-specific executive orders. The SDN List is the primary consolidated publication of individuals and entities subject to US economic sanctions. Errors and near-matches on that list are corrected through OFAC's own administrative process, not through the courts in the first instance.
The mechanism rests on two distinct situations. First, the listed person themselves believes their entry contains erroneous or outdated identifying information – wrong date of birth, wrong nationality, wrong address. Second, an entirely different person is being wrongly identified as the listed party by screeners. The second situation – mistaken identity – is the focus of this briefing. In both situations, the pathway runs through OFAC's Office of Global Targeting and the agency's correspondence procedures.
Understanding this distinction matters. A challenge to the decision to list someone is a designation challenge, a separate and more demanding procedure. A mistaken-identity removal does not contest the underlying designation. It asserts only that the applicant is a different person from the listed individual and that the identifying markers used by screeners should be corrected to prevent continued confusion. That is a narrower – and often faster – argument to make.
What does OFAC prohibit, and why does a false positive create real harm?
OFAC prohibits US persons and, in secondary-sanctions contexts, certain non-US persons from engaging in any transaction with a listed party or with an entity that falls within the 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked). The prohibition is strict-liability in its basic structure: the intent of the counterparty is not the threshold question. A match triggers a block obligation, and the blocking party must file a report with OFAC within a short statutory window.
For the person wrongly identified, the consequences are severe and compound quickly. Banks decline account relationships. Payment processors reject transactions. Correspondent banks route around the institution. Employment references generate adverse screening results. Cargo is detained. In our experience, businesses in trading, logistics, and financial services face the most acute operational disruption, because multiple counterparties independently reach the same blocking decision on the same data. Does your current compliance programme have a defined escalation path for customers who allege a false positive? Many do not.
The harm is not limited to the named individual. A business whose beneficial owner shares a name with a listed party can find its transactions blocked even where the owner is a different person with different national identity documentation. Screeners working under a strict-liability regime have limited incentive to resolve ambiguity in the customer's favour. That is why a formal submission to OFAC, rather than bilateral negotiation with the blocking bank, is typically the right first step.
The position above covers the standard case. Your facts – the degree of name similarity, the volume of affected counterparties, the jurisdiction of the blocking institution – change both the urgency and the submission strategy.
For an assessment of your exposure and an early view on whether a mistaken-identity submission is the right route, contact Calder & Vance at info@caldervance.com.
How does the mistaken-identity removal procedure work in practice?
OFAC's procedure for correcting mistaken identity requires the affected person to submit a structured request that establishes three things: that they are a real and identifiable person, that their identifying details are materially different from those of the listed individual, and that the similarity of names or other data is the source of the screening errors they have encountered.
The submission package typically contains the following elements:
- A covering letter or memorandum setting out the factual basis for the claim in plain terms, addressed to OFAC and identifying the listed person by their SDN entry
- Government-issued identity documents – passport, national identity card, or equivalent – showing the applicant's full legal name, date of birth, nationality, and photograph
- Evidence of the screening errors themselves: written notifications from banks or counterparties stating that a transaction was declined or blocked due to a sanctions hit
- Additional differentiating data where available: registered business records, utility documents, professional licences, or any documentary evidence that distinguishes the applicant's profile from the listed party's known identifiers
- A declaration, signed by the applicant or their authorised representative, confirming the accuracy of the submission
OFAC reviews the submission against the SDN entry. If satisfied, it can take several steps: add additional identifiers to the listed person's entry (such as a "not to be confused with" notation), publish updated guidance on its website, or in some cases issue a letter confirming that the applicant is not the listed party. It does not remove the listed party unless the underlying designation is vacated. The remedy is clarification and differentiation, not deletion of the listing itself.
Timing is not governed by a published deadline in most cases. OFAC handles submissions according to its internal workload and the completeness of the submission. Incomplete packages stall. In our experience, the most common cause of delay is a submission that describes the problem clearly but fails to present documentary proof in a form OFAC can process – translated documents, certified copies, and a clear cross-reference between the applicant's identifiers and the SDN entry markers all matter.
How does the UK OFSI process compare, and what does the EU offer?
The UK and EU systems do not use the US "mistaken-identity removal" label, but both face the same operational problem and have developed comparable, if structurally different, responses. Any business with cross-border exposure to more than one sanctions regime will need to address the issue under each relevant authority, because a successful US submission does not automatically resolve problems arising under UK or EU screening.
Under OFSI, an individual or business suffering screening errors caused by name similarity to a UK-listed party can write to OFSI explaining the position and requesting clarification. OFSI may issue a letter confirming that the person is not subject to UK financial sanctions, which can then be presented to affected UK financial institutions. The legal basis is OFSI's administration of the financial-sanctions regime under the Sanctions and Anti-Money Laundering Act ("SAMLA"). OFSI does not publish a dedicated mistaken-identity procedure, but its licensing and correspondence functions can accommodate the request. Timelines under OFSI tend to be shorter than under OFAC in straightforward cases, but the process is less formalised.
Under the EU, the Council regulation establishing each sanctions programme is the relevant legal instrument. The EU Consolidated List is the publication administered by the European External Action Service. An individual suffering from name-match errors attributable to an EU-listed person can request clarification from the relevant competent authority in the EU member state where the blocking is occurring. There is no single EU-level mistaken-identity procedure; member states implement the consolidated list through national competent authorities, and those authorities vary in their responsiveness. The EU General Court is available for annulment actions in true designation-challenge situations, but that route is disproportionate for a mistaken-identity case.
The practical implication: where a client operates across the US, UK, and EU simultaneously – and is being blocked by institutions in all three jurisdictions – parallel submissions to OFAC, OFSI, and the relevant EU competent authority are the correct approach. Sequencing matters. The OFAC submission often generates the most useful documentary output, because OFAC's published SDN entry is the source document screeners in all three regimes tend to reference.
What are the principal risk flags that require early escalation to counsel?
Not every screening error requires immediate counsel involvement, but several fact patterns raise the stakes and alter the strategy considerably.
Multiple institutions blocking simultaneously. When more than one bank or payment processor has blocked the same client on the same SDN match, a bilateral resolution with any single institution is unlikely to produce a durable fix. A formal OFAC submission is the only mechanism that addresses the underlying data problem.
The corporate counterparty is the listed individual's namesake and operates in the same sector or geography. That combination means automated and analyst-driven screening will independently and repeatedly reach the same (erroneous) conclusion. Clearing the record requires more than a covering letter.
The listed individual operates under aliases that partially overlap with the applicant's known trade names. OFAC SDN entries typically list aliases, and a match on an alias is treated by screeners as seriously as a match on the primary name. The submission must address all matching identifiers in the entry, not only the primary name.
A public enforcement filing or press release has identified the listed party in a way that increases the reputational dimension of the confusion. Even after OFAC clarifies the position, third parties who have seen the coverage may continue to apply caution. Counsel can advise on the appropriate steps to address the downstream reputational effect.
The applicant is a regulated financial institution itself, and the name match is triggering adverse correspondent banking decisions. That situation involves both the mistaken-identity question and the de-risking dynamic that can close banking relationships on a prospective basis independent of any specific transaction. In our practice, we regularly advise institutions in this position, and the resolution requires engagement with the correspondent banks as well as with OFAC.
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential assessment.
A common misconception: can a bank resolve this without going to OFAC?
A persistent belief among compliance teams is that providing the blocking bank with identity documentation is sufficient to resolve a mistaken-identity problem. This is the most common myth in this area. It is understandable – banks are the immediate point of friction – but it misunderstands how the blocking obligation operates.
A bank that has determined a match with an SDN entry is operating under a strict obligation. It cannot voluntarily release blocked funds or resume a relationship simply because the customer has presented a passport. The bank would need to be satisfied that there is genuinely no match with the listed party. In practice, that means the bank needs either an authoritative clarification from OFAC itself or a clear and verifiable difference in the identifying data that makes a match impossible. Customer-supplied documents, standing alone, rarely meet that bar – not because the bank doubts the customer, but because the bank's compliance function faces its own regulatory risk.
The right strategy is to address both layers simultaneously: give the bank whatever documents clearly distinguish the applicant, and at the same time submit to OFAC so that the authoritative record is updated. The OFAC submission is the mechanism that changes the root cause. The bank submission is a parallel communication to manage the immediate relationship. Neither replaces the other.
We regularly advise on both dimensions in parallel, and in our experience the coordinated approach resolves the matter more quickly than sequential escalation.
When should a mistaken-identity removal be escalated to a full designation challenge?
A mistaken-identity removal and a designation challenge are fundamentally different procedures directed at different facts. The former asserts that the applicant is not the listed person. The latter asserts that the listed person should not have been designated, or that the legal basis for the listing no longer exists. The two can, however, overlap when the identity of the listed person is itself uncertain or contested.
Escalation from a mistaken-identity submission to a designation challenge becomes appropriate in two scenarios. First, where OFAC's review of the mistaken-identity submission produces a determination that the applicant may in fact be the listed party – or where the identifying data is genuinely ambiguous and OFAC declines to issue a differentiation letter. In that situation, the applicant needs to confront the underlying designation directly, which is a separate and more resource-intensive process.
Second, where the applicant believes that the listing itself is based on information that confused their identity with the true target at the designation stage – in other words, that the original decision to list was itself a product of the same data error. In that case, the administrative record matters and the designation challenge route, which includes a petition to OFAC's Office of Global Targeting, is the appropriate mechanism.
The distinction also has a cross-regime dimension. An EU designation challenge proceeds before the EU General Court as an annulment action. A UK designation challenge proceeds before the High Court by way of judicial review. These are adversarial proceedings governed by different procedural rules and timelines. They are not the same as the administrative processes OFAC offers, and success in one jurisdiction does not automatically produce relief in another.
Practitioners advising on OFAC matters note that the threshold for a successful mistaken-identity submission is lower than for a designation challenge – the burden of proof is on distinguishing identity, not on rebutting a policy determination. That lower threshold is the reason a mistaken-identity submission should always be considered first, before committing to the more demanding designation-challenge route.
Related practices
- Delisting evidence packages for Australia – building the evidentiary record for Australian sanctions delisting submissions
- Mistaken-identity removals under OFAC: further analysis – extended practitioner commentary on contested and cross-regime cases