Optional cookies require your permission.Privacy & cookies

A screening result belongs to someone else. How do you correct it?

A shared name can produce a match between people with different dates of birth, roles, or addresses. Show the distinguishing facts before requesting a correction or sending fuller personal records.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (4)
Handwritten slips record names and dates in several different hands.
In this essay10 sections
  1. Establish what has happened.
  2. Separate contradiction from missing information.
  3. Build a comparison a second reviewer can follow.
  4. Distinguish the wrong person from the right person with an incomplete history.
  5. Send three different requests where necessary.
  6. Treat blocked property as a separate problem.
  7. Keep one factual chronology across the recipients.
  8. Keep the application moving without concealing the review.
  9. Preserve the decision without overstating it.
  10. The Bitcoin Lawyer take

Establish what has happened.

A reviewer asks about a sanctions entry, a public-office profile, or an article about somebody with your name. Before writing a defense of your character, establish the issue. Is this a candidate match awaiting review, a formal refusal, a payment restriction, or an inaccurate database profile? Those situations need different recipients and different next steps.

Ask for the source category, record reference, matched fields, and date of the check, to the extent the institution can disclose them. A vendor’s profile, a government designation, and a news report are separate records even when one screening result links all three. Keep the exact wording of the request and any application or payment deadline.

Do not assume a name-only result proves that you are designated. OFAC’s FAQ 5 directs organizations to examine the full entry and compare identifiers, not just the name. Its current guidance leaves the match determination with the organization and says OFAC does not confirm potential matches or false positives. This is US sanctions guidance, not a universal instruction for citizenship authorities.

Separate contradiction from missing information.

Make a side-by-side comparison of the applicant and the source record. Use the complete name, documented variants, birth details, relevant nationality and identity numbers, and any entity identifier. Lead with the strongest supported distinction. Similar occupations or a shared city may add context without resolving identity.

A conflicting date of birth and an absent date of birth are different findings. Mark the first as a documented inconsistency and the second as unavailable. Do not convert missing information into proof that the record concerns somebody else. Where the source gives a date range or several possible identifiers, compare against that whole entry rather than the most convenient field.

Use historical records where the alleged connection is historical. A current company extract may not answer who directed it during the reported event. A recent residence document may not establish where you lived then. Preserve the relevant official history, translations, and explanatory notes, while limiting disclosure of unrelated family, or financial information.

Build a comparison a second reviewer can follow.

A correction packet should allow somebody who has never met you to repeat the comparison. Put the challenged record reference at the top. Below it, identify each relevant field, what the record says, what your evidence says, and the document supporting that statement. Use page numbers where an exhibit contains several people. Avoid treating a biography written for this request as independent evidence of the facts it repeats.

Suppose, in a fictional example, a screening profile concerns a person born in 1974, while the applicant has a birth record showing 1988. The difference is worth highlighting. If the profile also gives an identification number, compare that separately. Where it gives no birthplace, write that the field is absent. Do not fill it with a guess or claim that an unknown birthplace conflicts with your own.

Names need particular care. Preserve the original script alongside the transliteration used in the application. Explain a documented marriage name or spelling change with its supporting record. Where two documents use different transliterations, identify that difference explicitly. A reviewer should not have to decide whether an unfamiliar spelling is another person, a clerical error or a routine rendering of the same name.

Keep the underlying documents intact. If the recipient agrees to a redacted reading copy, identify it as redacted and retain the original securely. A highlighted extract can help navigation, but it should not hide qualifications or surrounding text that changes its meaning. Before supplying a full identity document, confirm the recipient, purpose, and secure delivery method. A correction process should not create a second problem through unnecessary disclosure.

Distinguish the wrong person from the right person with an incomplete history.

Not every uncomfortable screening result is a false positive. A report may correctly identify the applicant but describe an old allegation without a later outcome. A public-office record may concern a genuine former role. Those are different questions from mistaken identity. The response should acknowledge the connection and explain the precise omission or error, rather than argue that the whole record belongs to somebody else.

For a historical dispute, establish the sequence using the records that actually exist: the reported allegation, the relevant proceeding, and its documented disposition. Read the disposition before summarizing it. A case ending without a merits determination should not be described as a finding that every allegation was false. Equally, an allegation should not silently become a conviction in the summary prepared for the next application.

A commercial provider may also retain a risk opinion after correcting an inaccurate fact. Ask what was corrected and what remains disputed. The ICO guidance distinguishes factual inaccuracies from recorded opinions and recognizes that an accurate history can include a previous mistake and its correction. Its guidance is under review following UK legislation, so the applicable rights and procedure should be checked when a real request is made.

The practical consequence is to make the requested remedy precise. Separating two people, correcting a birth date, and adding a subsequent outcome are three different changes. Identify which one the evidence supports. If the remaining dispute concerns the institution’s appetite for the activity, a factual correction alone may not change its commercial decision. Record that distinction instead of promising an account or application outcome.

Send three different requests where necessary.

The institution reviewing your application can assess its candidate match. The database controller may be able to separate conflated identities or correct an inaccurate profile. The keeper of the underlying record can address an error in that source. Ask each to decide the issue it actually controls; a request to one party does not establish that the others have updated their records.

For a correction request, identify the precise field, why it is inaccurate, the replacement supported by evidence and the relevant attachments. Where the UK GDPR applies, the ICO’s guidance describes rectification of inaccurate personal data and, depending on purpose, completion of incomplete data. That right has a defined legal scope and exceptions. It is not a worldwide right to remove accurate, inconvenient information.

Retain the request as sent, its delivery or acknowledgment, reference number, and response. If an institution resolves the identity issue while a vendor request remains open, describe those two statuses separately. “The bank closed its candidate match on this date” is more informative than “the database cleared me” when no database decision exists.

Treat blocked property as a separate problem.

An unresolved question in an application is not the same as property that has been blocked. If funds are restricted, preserve the notice, transaction reference, institution, and stated reason, and obtain sanctions advice for that actual restriction. Do not try to route around the review through another person, account, or payment rail.

OFAC FAQ 1196 distinguishes property blocked in error through mistaken identity from property correctly blocked whose status later changes. It describes the reporting organization’s procedures and an alternative Compliance Release process. That process is available to the organization that blocked the property; an affected customer should engage with that institution rather than treating the FAQ as personal permission to move the funds.

The correction file can support that work, but it does not decide whether there was a blockable interest, whether an authorization is required, or which reporting duties apply. Give the responsible institution and qualified advisor the complete facts. Keep technical payment support separate from the authority to release a restriction.

Keep one factual chronology across the recipients.

Several parallel requests create a version-control problem. Nominate one coordinator for the factual record and preserve each submitted version. If a date, spelling or relationship needs correction, record what changed, and which recipients need the update. Quietly replacing an attachment in one folder does not correct a statement already sent elsewhere.

Illustrative example: a commercial profile merges an applicant with a former director who shares a transliterated name. The applicant’s documents establish a different birth date, while historical company filings identify the other person’s role. The institution might decide those records resolve its match. A separate vendor request should still identify the merged profile and ask for its correction; the institution’s decision should not be represented as the vendor’s.

Keep the packet proportionate: an issue summary, the decisive identity comparison, primary exhibits, and the correspondence record. A large unrelated wallet archive will not resolve a birth-date collision. Agree a secure channel before sending identity documents, and ask which additional evidence is actually needed if the first comparison remains inconclusive.

Keep the application moving without concealing the review.

A pending correction and a pending citizenship application can have different deadlines. List both and identify the person responsible for communicating with each recipient. If a response date cannot be met, ask the relevant recipient about an extension or an accepted interim response. A deadline entered in your own calendar is a planning tool; it does not establish that the authority has extended anything.

An interim explanation can identify the disputed record, the evidence already available and the outstanding request, where the recipient permits that approach. Keep its language conditional. “A correction was requested” means the request exists. It does not mean the provider agrees, the record has changed, or the screening question has been resolved. Send any later decision through the proper application channel with its reference and date.

Repeatedly starting new applications can multiply versions of the same unresolved issue. Before doing so, establish what earlier declarations and refusals must be disclosed under the new application’s questions. Do not describe a still-open matter as settled merely because another advisor has taken over. Give the new coordinator the submitted account as well as the latest evidence so that discrepancies can be addressed openly.

Once the review ends, retain a compact record that can be understood later: the original concern, the decisive exhibits, the request, and the actual response. Restrict access to the sensitive documents and keep an index of what was sent to whom. The next institution may conduct a fresh review, but it should receive a coherent history rather than a claim of clearance detached from its evidence.

Preserve the decision without overstating it.

Ask for the outcome the recipient can provide, including its date and scope. A closed candidate match, a corrected profile, and a withdrawn official record are different results. If the matter remains pending, preserve that status and the next action. Do not turn an acknowledgment into approval because a separate project deadline is approaching.

OFAC does not issue certificates of non-inclusion or a safe list, as FAQ 469 expressly states. Be wary of any document sold as universal sanctions clearance. Keep prior institutional decisions as dated evidence of what that institution reviewed, and expect a later recipient to make its own assessment.

Before the next material application, update expired identity records, changed names, relevant company histories, and any later outcome. Preserve older versions so the progression is intelligible. The goal is to reduce avoidable ambiguity, not to remove accurate identities, relationships, or events from a lawful review.

The whole picture

The Bitcoin Lawyer take

Separate the mistake in the source from the decision an institution made using it. Retain each reply and describe the scope of the correction accurately if another reviewer raises the same name.

A second passport or a different payment method does not solve a mistaken-identity record. A precise comparison, the right recipient, and a documented outcome do.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “A screening result belongs to someone else. How do you correct it?” https://www.bitcoinlawyer.com/journal/correcting-a-screening-false-positive