A bank delays a wire transfer after a sanctions-screening alert on a founder's name. The founder insists they are not sanctioned, while a supplier asks whether the company can still receive payment. The same transliterated name appears in an OFAC search result, but the date of birth, registration details, or geography may point to another person. The immediate problem is not a media headline. It is getting the right evidence to the institution that must decide whether the alert is a true match, a false positive, or a different sanctions issue.
A useful response starts by separating a potential name match from an actual designation, a transaction rejection, and property already blocked under sanctions rules. Those are not interchangeable. OFAC's published guidance directs screening organizations to compare identifying facts and apply their own risk-based procedures. A company's communications team can organize the record and prevent contradictory claims; the bank's compliance function and qualified counsel make the applicable legal and transactional determinations.
Find out what triggered the bank review
Ask the bank, through its established compliance channel, what kind of request it is able to identify: a sanctions-screening name alert, an ownership or geographic exposure question, a blocked-funds event, a rejected transaction, or a broader internal risk review. Do not assume that every vendor alert is an OFAC hit. Screening systems may combine OFAC lists with other U.S. government lists, commercial databases, and internal controls. OFAC FAQ 5 expressly distinguishes alerts involving its sanctions programs from matches against sources maintained by other agencies.
Record the affected legal entity, the requested transaction, the date the issue arose, the bank's case reference if provided, and the exact documentation requested. If different affiliates or individuals are involved, maintain distinct records. An account application placed on hold is not necessarily an OFAC blocking action, and a bank's business-risk decision may remain separate from its sanctions analysis. The precise status determines who can resolve it and which representations are appropriate.
A name similarity score is not a sanctions decision
OFAC's Sanctions List Search uses fuzzy name matching, including character and phonetic techniques, so it can return similar names that are not the same person. FAQ 246 explains that fuzzy logic applies to the name field, not every identifier. The score is a search aid, not a government-issued probability of guilt or a clearance certificate. OFAC does not prescribe one universal matching threshold because institutions must assess risk within their own controls.
The review should compare the complete official list entry, not a cropped search screenshot. For an individual, relevant discriminators can include full legal names, aliases and original script, date and place of birth, nationality, passport or identification numbers, and addresses. For a company, the corresponding evidence may include incorporation records, business identifiers, ownership, registration jurisdiction, and operating history. A shared surname, transliteration, or address alone does not prove identity.
Not every mismatch disposes of an alert. An exact name combined with matching birth information or corporate identifiers requires more careful review than a loose phonetic resemblance. Ownership or control questions may also arise even when the screened company itself does not appear by name. OFAC's FAQ 5 warns that some entities may be blocked by operation of law, including under its 50 Percent Rule. A name-clearing narrative cannot replace an ownership analysis.
Build a bank-ready identity and source packet
A credible packet should make it easy for a reviewer to reproduce the comparison without exposing unnecessary personal information. Begin with the precise name or entity that triggered screening, identify the candidate OFAC entry, and show which independent documents support each material difference. Verify that dates, spellings, legal entities, and ownership statements are consistent across the packet. Maintain the full originals securely and provide redacted copies only as appropriate to the bank's requested channel.
- Identity sheet: legal name, former names, aliases, original-language spelling, birth details or corporate registration data, and the documents that establish each fact.
- Candidate-list comparison: list name, program and unique entry identifier where available; each relevant identifier in the official entry; and verified agreements or differences.
- Corporate context: formation extract, legal entity identifiers, current ownership chain and dated changes if the transaction involves a company.
- Transaction context: payment purpose, counterparties, contract or invoice reference, and the specific person or company conducting the transaction.
- Evidence index: issuer, issue date, country, language, translation status, source URL or retrieval date, and the person responsible for verification.
- Open issues and contact: unresolved similarities, documents still requested, the bank's case reference, and one authorized point of contact.
A one-page comparison table can be more useful than a lengthy public-relations narrative. It should distinguish verified facts from client assertions and hypotheses. Where the bank requires certified translations or more identity proof, treat those as evidence requirements rather than an invitation to speculate. For politically exposed founders or complex cross-border structures, reconcile public records with corporate documents before sending the packet; inconsistencies can prolong a review.
Choose the correct route for a false positive or blocked property
Screening alert with no confirmed blocking action
Provide the requested identity and transaction information directly to the screening institution and ask it to apply its existing sanctions-review process. OFAC FAQ 5 places the verification or disqualification decision with organizations following their compliance procedures. Avoid language claiming that OFAC has personally cleared the customer or certified the transaction. Under FAQ 469, OFAC does not issue certificates of non-inclusion or maintain a public safe list for people who are not listed.
Property blocked and reported because of mistaken identity
Escalate immediately through the institution's sanctions team and qualified counsel. OFAC FAQ 1196 describes mechanisms when property was blocked and reported because of mistaken identity, typographical error, or a similar error. The blocking institution may be able to unblock and file the appropriate report, or it may seek an administrative Compliance Release. That process is available to the organization that blocked the property, not to an unrelated communications adviser acting on the customer's behalf. The institution must determine the proper route and preserve required records.
Actual sanctions exposure rather than mistaken identity
Do not relabel an actual designation, a blocked ownership interest, or a prohibited transaction as a false positive. A listed person considering administrative reconsideration follows the separate petition process under 31 CFR 501.807. A true blocking case may instead implicate a license or other sanctions procedure, depending on the facts. These are counsel-led matters. The role of a communications adviser is to align verified explanations and stakeholder timing with the applicable legal posture, not to decide eligibility for release or removal.
Control what other stakeholders are told
The bank may request detailed confidential identifiers; a supplier or investor ordinarily needs a much narrower operational statement. Use a fact matrix with audiences, permitted disclosures, approval owners, and update triggers. Tell counterparties what is confirmed about payment or delivery timing and who owns the next update. Do not circulate passports, bank correspondence, possible SDN matches, or untested allegations to a broad distribution list.
A suitable holding position can be factual without predicting the bank's outcome: 'The financial institution is reviewing a sanctions-screening question. We have provided identifying records for its assessment and will communicate any confirmed operational change through our designated contact.' That is an illustrative formulation, not a statement that any specific client has been cleared. Adapt it to the actual record and counsel-approved disclosure restrictions.
Treat public-search results and adverse media as a parallel evidence problem. An erroneous database profile may be reused by suppliers, lenders, recruiters, or newsrooms after one bank resolves its internal alert. Document which source is wrong, whether the problem is mistaken identity, mistranslation, stale ownership, or incomplete procedural context, and what correction the source owner permits. A legitimate underlying report should not be characterized as fabricated merely because it is commercially inconvenient.
Run the review with a clear decision log
Name a case owner and maintain a chronology of the bank's requests, submitted evidence, source-list checks, decisions, and permitted stakeholder statements. Track the exact date and version of each sanctions-list check. Create escalation triggers for newly discovered identifier matches, requests involving blocked property, contradictory ownership data, legal notices, or a payment deadline that may affect contracted delivery. Do not treat silence from a bank as a finding that a potential match was false.
Before closing the matter internally, ask whether the bank has communicated the status of its own review, whether any actual blocking or rejection reporting remains open, whether another institution needs a separate submission, and whether public profiles need documented correction. Keep a record of the evidence used to reach internal conclusions. OFAC's FAQ 5 explicitly emphasizes complete, accurate investigation records for screening organizations; a disciplined client-side source index helps reduce conflicting follow-up submissions.
Where reputation diligence supports the compliance decision
For an executive, founder, family office, or foreign company, the practical deliverable is not a promise that a regulator or bank will reverse a decision. It is a verified identity record, an intelligible comparison to the screening hit, and controlled explanations that do not outrun the evidence. SIC Group USA's Executive & HNWI Reputation Due Diligence service addresses source-backed adverse media, cross-border digital records, and lawful correction planning. Where a real designation or blocked-property issue is confirmed, its OFAC Delisting & Reconsideration Support capability coordinates stakeholder communications alongside qualified sanctions counsel. The relevant services are at https://sic-group.us/services/reputation-engineering and https://sic-group.us/ofac-delisting-reconsideration-support.
Sources
U.S. Department of the Treasury, OFAC: FAQ 5: Assessing OFAC Name Matches - https://ofac.treasury.gov/faqs/5
U.S. Department of the Treasury, OFAC: FAQ 246: How Does Sanctions List Search Work? - https://ofac.treasury.gov/faqs/246
U.S. Department of the Treasury, OFAC: FAQ 1196: Property Blocked in Error Due to Mistaken Identity - https://ofac.treasury.gov/faqs/1196
U.S. Department of the Treasury, OFAC: FAQ 469: Certificates of Non-Inclusion and Safe Lists - https://ofac.treasury.gov/faqs/469
