A logistics firm based in Amsterdam begins a routine wire transfer. Its bank's screening system flags the company as a match for an entry on OFAC's SDN List (OFAC's list of Specially Designated Nationals and blocked persons). The firm has never operated in any sanctioned territory. Its name resembles that of a blocked entity. Every transaction freezes. The damage – frozen accounts, cancelled shipments, supplier disputes – begins immediately, before anyone has verified whether the match is real.
Mistaken-identity removals under OFAC are the administrative mechanism by which a non-designated party obtains formal confirmation from OFAC that it is not the blocked person named on the SDN List. The governing authority is the Office of Foreign Assets Control, acting under the International Emergency Economic Powers Act (IEEPA) and related statutory authorities. Resolution typically turns on submitting documentary evidence that distinguishes the claimant from the listed party – and, as of early 2026, the process remains one of the most time-sensitive in OFAC's administrative practice.
This briefing explains how the mistaken-identity removal process works, how it differs from a formal delisting, what the cross-regime picture looks like for businesses operating across multiple jurisdictions, and when a business should treat a false-positive screening hit as a compliance emergency requiring counsel.
What is the legal and administrative basis for OFAC's mistaken-identity process?
OFAC administers US economic sanctions under a range of presidential executive orders issued primarily under IEEPA, as well as under the Trading with the Enemy Act (TWEA) and programme-specific statutory authorities. When a party appears on the SDN List, US persons are prohibited from dealing with that party, and its assets subject to US jurisdiction are blocked. The list-maintenance function – including corrections and removals – sits entirely within OFAC's discretion as the administering agency.
A mistaken-identity removal is not a designation challenge. It does not require a party to prove that the original designation was legally defective. Instead, it proceeds on the narrower factual claim that the claimant is a different person from the individual or entity that OFAC intended to designate. The distinction matters. It limits the evidentiary scope considerably and, in our experience, makes resolution faster when the factual distinction is clear.
OFAC's authority to maintain and correct the SDN List flows from the same statutory foundations that authorise the underlying sanctions programmes. Where OFAC accepts that a party was never the intended target, it issues formal guidance – sometimes described as a "name-removal" or an "administrative correction" – and notifies the relevant financial institutions. The correction is prospective; it does not automatically reverse actions taken by third parties during the period of the false positive.
The position above covers the standard case. Your facts – the degree of name similarity, the jurisdictions involved, the nature of the transactions that have been blocked – change the speed and difficulty of the process materially.
To discuss a mistaken-identity matter at its earliest stage, contact Calder & Vance at info@caldervance.com.
How does a mistaken-identity removal differ from an OFAC delisting?
The core distinction is whether the claimant was ever the intended target of a designation. A delisting – formally, a petition for reconsideration of a designation – argues that the designated party should no longer be listed, whether because the legal basis was unsound, the evidentiary record has changed, or the party has come into compliance with the underlying programme's requirements. A mistaken-identity removal argues something different: that the claimant and the listed person are two separate parties who share identifying characteristics that triggered an erroneous association.
This distinction shapes the entire proceeding. A delisting typically requires engagement with the substantive basis for the designation and may involve classified information OFAC holds. A mistaken-identity removal avoids that layer entirely. The claimant does not need to address why the listed person was designated. The claimant needs only to establish, through documentary evidence, that its own identifying details – legal name, registered address, ownership structure, date of formation, national registration numbers, and similar markers – are materially different from those of the SDN-listed party.
In practice, the evidentiary package for a mistaken-identity removal is shorter but must be precise. Vague submissions asserting general dissimilarity rarely move quickly through OFAC's review. Specific, organised, cross-referenced documentation – certificates of incorporation, corporate registry extracts, tax identification records, beneficial-ownership charts – is what OFAC's reviewers need to act. We regularly advise clients on assembling this evidence in a form that minimises back-and-forth with the agency.
What triggers a mistaken-identity situation, and what does it look like in practice?
The most common trigger is a screening hit at a financial institution, a payment processor, or a trade counterparty's compliance department. Automated screening tools match against name variants, transliterations, date-of-birth fields, and address data. When a legitimate business shares a name – or even a phonetically similar name – with an SDN-listed party, the screen flags the match as a potential positive. The institution's compliance team, acting under its own regulatory obligations, then restricts the relationship pending clarification.
A secondary trigger arises in trade and logistics: a shipment is held at a port or bonded warehouse after a cargo screening system identifies a shipper, consignee, or notify party as a potential SDN match. The commercial cost accumulates quickly. Demurrage, storage charges, and customer penalties begin while the verification process runs its course.
A third pattern involves individual persons – executives, beneficial owners, or directors – whose names match SDN entries for individuals, often with similar nationalities or birth years. The individual finds that bank accounts are frozen, card payments are declined, and counterparties refuse to transact. The impact is personal as well as commercial.
In a recent matter, a mid-sized manufacturing business in South-East Asia found that a US correspondent bank had frozen an export-related payment because the company's trading name was nearly identical to an SDN-listed entity in a different sector and jurisdiction. We prepared the documentary package distinguishing the two entities, submitted it to OFAC with a request for administrative guidance, and the matter was resolved without the need to open a formal licensing proceeding. The lesson: preparation quality determines resolution speed.
What evidence does OFAC require – and how is the cross-regime picture different?
OFAC's mistaken-identity process is evidence-driven. There is no prescribed form; submissions are made by letter or through OFAC's online portal. The substantive requirement is to place before OFAC enough factual material to allow its reviewers to distinguish, with confidence, the claimant from the SDN entry.
The standard evidence set includes: certified copies of incorporation documents (with the precise legal name as registered); current beneficial-ownership information with a visual chart showing the ownership chain; any national registration or tax identification numbers that differ from those associated with the SDN entry; evidence of the principal place of business and its history; and, where the confusion arises from a name similarity, a clear side-by-side comparison demonstrating the divergence in identifiers. If the SDN entry carries specific identifiers – dates of birth, passport numbers, vessel IMO numbers, registration numbers – the submission should address each one directly.
The cross-regime comparison here is instructive. Under OFSI in the United Kingdom, a party in an analogous position – a business or individual falsely matched against the UK Consolidated List – would submit a formal request to OFSI for confirmation that it is not the designated person. OFSI's process is governed by the Sanctions and Anti-Money Laundering Act (SAMLA) and OFSI's published guidance. The UK process shares the evidence-first logic but operates on a different timeline and involves different notification routes to the financial institutions involved.
Under EU sanctions, governed by the relevant Council Regulation, the ownership and control (the UK and EU test for whether a non-listed entity is caught through a listed person) question adds a layer absent in OFAC cases: a non-listed entity may be treated as if listed if a designated person exercises control over it, even below a majority-ownership threshold. That means an EU-established business in a mistaken-identity situation may face both a "same party" question and an "owned or controlled" question simultaneously. Our practice regularly advises businesses navigating both layers at once.
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 to discuss a matter already in motion.
What are the key risk flags – and when should a business treat this as urgent?
Not every screening hit is a mistaken-identity case. The first risk flag is failing to make that determination quickly. A hit that turns out to involve genuine ownership or control connections to a designated person requires a different response entirely – one that may involve assessing whether a licence is required, reporting obligations have been triggered, or an apparent violation has occurred. Treating a genuine SDN-ownership hit as a simple name-confusion error and sending an evidence package is a significant mistake.
The second risk flag is the false assurance that "we are obviously different." Obvious factual differences do not automatically resolve a mistaken-identity case if the submission is poorly structured, incomplete, or directed to the wrong OFAC team. OFAC receives a high volume of inquiries. Submissions that are clear, well-referenced, and organised around OFAC's own verification criteria move faster.
Third: secondary-sanctions exposure. A company whose transactions are being blocked by a US financial institution because of an SDN screen hit may also face questions from counterparties in the EU, the UK, or other jurisdictions where screening is conducted in parallel. A resolution with OFAC does not automatically clear the party with every other institution or regime. Coordinating the communications – and ensuring that the OFAC guidance letter is shared with every institution that has imposed a restriction – is a practical step that is often overlooked.
Fourth: the statute of limitations is not the primary urgency driver here, but commercial harm is. Every day that a freeze persists is a day of commercial loss. Businesses sometimes delay instructing counsel because they assume OFAC will correct the position automatically once the agency is notified. That assumption is not reliable. OFAC acts on submissions it receives; it does not proactively search for cases where screening has produced a false positive.
A common myth worth addressing directly: many businesses assume that simply contacting their bank with an explanation is enough to resolve a mistaken-identity freeze. It is not. The bank's compliance team cannot override the screening result on the basis of a customer's self-certification. The authoritative resolution must come from OFAC itself – typically in the form of a written communication that the bank can document in its compliance file. Until that communication exists, the bank has no safe basis to release frozen funds or resume the relationship.
How does the process interact with OFAC's licensing and enforcement functions?
A mistaken-identity removal is an administrative correction, not a licence. The distinction matters in two directions. First, during the period before OFAC issues its clarification, a non-designated party whose assets are frozen does not hold a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) authorising any dealings. The party cannot transact. It cannot agree with a financial institution to conduct business "pending resolution." Any transaction while the screen hit is unresolved – even with the intention of resolving it – risks triggering the reporting and disclosure obligations that apply to blocked property.
Second, if the mistaken-identity submission does not succeed – for example, because OFAC determines that the claimant is in fact related to or associated with the SDN-listed party in a way not initially apparent – the matter may shift to a formal licensing or enforcement context. This is another reason why the initial submission must be factually accurate and complete. A submission that overstates the claimant's distance from the listed party, or that omits relevant ownership information, can create a worse evidentiary position than no submission at all.
Where there is genuine uncertainty about whether a relationship to a designated person exists, the correct course before submitting a mistaken-identity package is to conduct a thorough internal ownership-and-control review. Counsel can assist in structuring that review and in deciding whether to proceed with a mistaken-identity submission or an alternative route – such as a specific-licence application or, where justified, a voluntary self-disclosure (VSD, disclosure to a regulator of a potential violation before enforcement action begins).
For businesses in the financial sector, there is an additional layer. A US financial institution that has blocked property or a transaction because of an SDN screen hit has its own OFAC reporting obligations. Those obligations run on the institution's own timeline, independent of the screened party's submission to OFAC. A non-designated party that wants to resolve its position quickly should understand that the institution's compliance team is operating under its own constraints and timelines – and that coordinated, well-documented outreach to both OFAC and the institution is more effective than sequential approaches.
Practical steps once a mistaken-identity situation arises
The first step is verification: confirm whether the screening hit is a true false positive or a case involving a genuine OFAC nexus. Run the SDN entry against every identifier available for the claimant – legal name in every script where the name has a transliterated form, all registration numbers, addresses, dates, and any associated persons named in the SDN entry.
The second step is documentation: gather the evidence package before submitting anything to OFAC. A piecemeal submission – initial letter followed by follow-up responses to requests for information – takes longer to resolve than a complete, well-organised initial submission that anticipates OFAC's questions. The package should address every identifier in the SDN entry directly.
Third: notify affected counterparties. Financial institutions that have frozen funds or blocked transactions should receive a concurrent communication explaining the basis of the mistaken-identity claim and confirming that a submission to OFAC is being made. This does not unlock the freeze, but it creates a documented record and allows the institution's compliance team to place the file in the correct queue.
Fourth: assess parallel-regime exposure. If the claimant conducts business in the EU, the UK, or other jurisdictions with active screening obligations, the SDN hit may have triggered responses in those regimes as well. Coordinate the resolution across regimes, not just with OFAC. Our practice covers both the OFAC side and the parallel UK OFSI and EU Council-regulation picture, which allows us to manage the cross-border resolution in a single engagement.
Fifth: preserve records. All communications with OFAC, with financial institutions, and internal records documenting the discovery and response to the screen hit should be retained. Record-keeping obligations under the relevant sanctions programmes require that related records be kept for a defined period, and a thorough file also supports any subsequent commercial claims arising from the freeze period.
Related practices
- Delisting evidence packages – Australia – building and submitting the evidence package for autonomous sanctions delisting under the applicable Australian regime.
- Mistaken-identity removals under OFAC (part 3) – advanced considerations including complex ownership chains and multi-regime coordination.
- Mistaken-identity removals under OFSI – the UK financial-sanctions parallel: SAMLA, OFSI's process, and divergences from the OFAC route.