Independent legal information. This website is not affiliated with LSEG, World-Check, Refinitiv, LexisNexis or any screening provider. Eligibility, remedies and outcomes depend on law and evidence.
False matches and mistaken identity
An individual may share a transliterated surname, nationality or company association with a person in a screening profile. Additional identifiers, dates, addresses or verified employment records may separate the two. The bank’s own alert decision may need review independently of the database entry.
Investigating the relevant identifiers
We would compare the available identifiers, source chronology and relationships, prepare a factual disambiguation pack and determine whether the request belongs with the screening provider, the financial institution or both.
Identity evidence to test a disputed match
| Document or record | Why it may help |
|---|---|
| Identity and date-of-birth documents | Establishes the relevant dates and identities |
| Alternate spellings and transliterations | Tests what the decision-maker actually recorded |
| Corporate registry extracts | Supports an objective factual comparison |
| Screenshots or letters describing the match | Shows a later event or possible consequence |
Why a bank alert is not proof of a vendor error
A screening hit is not proof that the person is listed in the database; some false positives occur only in the bank’s matching layer.
Common sources of mistaken identity
- Similar surnames across different alphabets and transliteration systems.
- Missing birth dates or incomplete nationality information.
- Company names that resemble unrelated entities.
- Historical addresses or occupations no longer associated with the client.
A useful dispute presents the matching field, counter-evidence, and specific correction requested in a short comparison table.
Two different decisions may need attention
A screening data provider can review the accuracy of its own record. A bank or regulated institution makes a separate decision about its customer relationship. The first outcome does not automatically determine the second.
False positive can describe two different errors
A bank's screening software may flag a potential name match that its analysts should resolve manually. Separately, a data provider may have an inaccurate profile that actually merges two identities. These are not the same allegation. A false-positive alert can be closed by a customer after review even if the underlying database record remains correct.
Distinguish the match before choosing a remedy
| Scenario | What may be wrong | Correct starting point |
|---|---|---|
| Same name, different birth date | Customer matched to someone else | Bank compliance review with disambiguating evidence |
| Similar transliterated names | Alias matching rule produced a candidate | Confirm identifiers and original-language spelling |
| Incorrect alias in the database | Provider associates wrong name with an entry | Provider profile correction request |
| One person's allegations attributed to another | Mixed profiles or mistaken reporting | Documentary identity comparison plus source correction |
| True historical record about the client | Not a false positive merely because adverse | Assess accuracy, context and separate legal rights |
A defensible disambiguation pack
The goal is to give an analyst enough information to distinguish identities without over-disclosing personal information. Useful evidence may include a minimal birth-date comparison, citizenship, role chronology, public registries and a signed explanation of the mismatch. Sensitive identifiers should be redacted when possible and sent only through verified secure channels.
A chronological matrix is especially useful where individuals share a name but live in different jurisdictions or held different offices at the date in question. A dated, independent record is typically stronger than a general assertion that "this is not me."
Why the bank should be engaged directly
A consumer cannot always inspect the screening interface used by a bank. The bank may also withhold parts of its investigation where disclosure would conflict with law. The case can still focus on the objective identifiers available to the institution, asking for appropriate human review and providing relevant documents. Avoid implying that a lawyer can directly alter the bank's internal screening-alert status without the institution's participation.
Frequently asked questions
Can a bank clear a false positive without deleting a profile?
Often the issue is a match-resolution decision rather than an inaccurate underlying profile.
Should I send my passport through a public form?
No. Arrange a secure verified process first.
What does a discounted hit mean?
In screening workflows it can describe an alert discounted after review; it does not necessarily show that the underlying provider record was false.
Does a matching name prove identity?
No. Names should be evaluated with available dates, places, aliases and other identifiers.
Can the bank keep an alert record after resolving it?
Its internal recordkeeping depends on law and policies; closing a false-positive alert need not erase the audit trail.
Related reading
Primary sources and verification
Discuss your situation
Please describe the jurisdiction, the decision-maker, what happened and whether you have received a written screening record or bank notice. Do not upload highly sensitive personal or financial data into an unverified form.