Name Matching Across Documents: Accents, Maiden Names

Name matching means comparing the name written on one document with the name on another document or record and deciding whether they refer to the same person. Exact string equality is the wrong test. "José García-Lopez" on a passport, "JOSE GARCIA LOPEZ" on a bank statement and "Garcia, Jose" on a pay stub are one person, while "Jon Smith" and "John Smith" with different dates of birth may not be. A usable rule normalizes the name, compares the parts that matter, and sends the rest to a person with a defined next step.

This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of October 2026 and cover the United States unless stated otherwise. Rules differ by state and by institution type. Consult a qualified professional for your situation.

What does name matching compare, and why not use exact equality?

Name matching compares the last name, first and middle names and a second anchor field (usually date of birth) between two documents, after removing differences that carry no identity information. Exact equality fails on harmless differences and still passes a different person who happens to share a string, so it is both too strict and too loose.

For banks, the Customer Identification Program rule requires a written program with risk-based procedures that let the bank form a reasonable belief that it knows each customer's true identity, using the customer's name, date of birth, address and identification number (31 CFR 1020.220). The rule lets an institution specify when it uses documents, non-documentary methods or both. Property managers, staffing firms and lenders outside the Bank Secrecy Act framework face the same practical problem: the license, the pay stub and the bank statement were each typed by a different party.

This article sits inside our wider document verification guide. For the other comparisons in a file (address, income, bank details), see cross-document verification checks.

Which name differences are common, and what does the reviewer do?

Seven kinds of difference explain most name mismatches in applicant files. Each has a source field, a comparison field, a verdict and a next step.

The point of the table is the three verdict classes. Cosmetic differences are accepted automatically with the normalization rule logged. Explainable differences need one more document. Unexplained differences stop the file.

How should accents and diacritics be handled?

Strip accents and fold case before comparing, but keep the original spelling for the record. A name written "Müller" can legitimately appear as "Mueller" or "Muller," and "Åsa" as "Asa" or "Aasa," depending on who typed it and which system stored it. Many U.S. systems store only unaccented ASCII, so an accent on a passport and none on a pay stub is the normal case, not a red flag.

Passports add a second layer. The machine-readable zone at the bottom of a passport is limited to the letters A to Z and the filler character "<," so accented letters cannot appear there and each issuing state converts them by its own convention under ICAO Doc 9303. The visual zone can show the accent; the machine line cannot. A difference between the printed name and the machine line is therefore expected for accented names and is not a sign of tampering.

Practical rules:

1. Compare on a folded form (lower case, no accents, no punctuation) but display both forms to the reviewer.
2. Treat "ü / ue / u" and "å / aa / a" as equivalent in the comparison.
3. When the printed name and the machine line disagree on more than diacritics, flag it.

How do maiden names and name changes show up?

A maiden-name mismatch looks like a different last name with the same first name and date of birth. In the United States a person may change name through marriage, divorce or a court order, and the State Department's page on changing or correcting a passport lists a marriage certificate, divorce decree or court order as the documents that support a passport name change. Nothing forces a person to update every document at once, so a file can legitimately contain an older bank statement in one last name and a new license in another.

Handle it in four steps:

1. Confirm the first name and date of birth match across the two documents.
2. Ask for the document that links the names: a certified marriage certificate, divorce decree or court order.
3. Check that the linking document names both last names and that its date falls between the two documents' issue dates.
4. Record the link, so the next reviewer does not ask again.

A name-change document proves the link between two names; it does not by itself prove that the person presenting it is the person named. Keep identity verification and name linking as separate steps. Many U.S. applicants also hold documents issued by different bodies (a state license, a federal passport, an employer pay stub), and each body may have updated at a different date.

What about compound names and several last names?

Compound first names and multiple last names are compared as sets of parts, not as one string. "Mary-Ann," "Mary Ann" and "Maryann" should resolve to the same first name; "Smith-Jones," "Smith Jones" and "Jones" (when a person uses only one half) need a rule.

The safe rule is: every part present on the narrower document must appear on the fuller one, and the last-name part must match. "Jones" against "Smith-Jones" passes the first test; "Smith" against "Smith-Jones" passes too. Both are accepted only when date of birth also matches, and both are logged as partial matches. Prefix particles ("Van," "De," "O'," "Mc") are a frequent trap: "McDonald" and "Mc Donald" are the same, and "Van der Berg" may be filed under V or B in a payroll system. Suffixes such as "Jr." and "III" should be stripped for comparison but kept in the record, since they separate a father from a son who may share an address.

How do you handle transliteration from other alphabets?

Transliteration differences are matched against the passport machine-readable line, which acts as the agreed Latin spelling for that person. Names written in Arabic, Cyrillic, Chinese or other scripts have no single Latin form, so "Mohammed," "Muhammad" and "Mohamad" can all be correct renderings.

The reviewer's question is not "which spelling is right?" but "does this spelling connect to the identity document?" If the passport machine line reads MUHAMMAD and the pay stub reads Mohammed, with the same date of birth, accept and log. If the bank account is held under a third spelling, ask the applicant for a bank letter or a statement re-issued with the passport spelling. Only fuzzy matching (edit-distance or phonetic scoring) should be used to propose a match, never to approve one alone.

What about sanctions screening?

Sanctions screening is a separate name check against a list, not a way to confirm that two documents belong to the same person. OFAC's own Sanctions List Search tool returns exact matches or, when widened, fuzzy results; OFAC's published FAQ describes the fuzzy logic as applying to the name field. The consequence for a file reviewer is simple: a clean screening result says no list entry scored as a match for that spelling, and it does not say the name on the license matches the name on the pay stub. Run the document comparison first, then screen the confirmed name and its known variants under your own compliance program.

What do users ask about name mismatches?

People who handle onboarding files and people who are asked to prove their name tend to raise the same questions. These two come up most.

"My pay stub has my married name but my passport has my maiden name. Will the check fail?" It will raise a flag, not fail by itself. Provide the marriage certificate, or update the passport using the process on the State Department's name-change page. Reviewers then record the link and move on.

"The bank spells my name without the accent. Is that a problem?" No. Accents are removed by many systems, and a good comparison folds them. The date of birth and last-name parts are what count.

Another frequent question is how much fuzziness is acceptable. Our answer: none for date of birth, some for first names, and a documented rule for last names.

Where can names be checked against a register?

A register check confirms a name against an authoritative record, which is different from comparing two documents the applicant supplied. For companies, each state keeps its own business registry, typically run by the Secretary of State, which lists entity name, status and registered agent. For individuals there is usually no open public register, so the license or passport and a government-issued linking document are the anchors.

A register lookup shows that a person or company with that name exists on that date; it does not show that the document in your hands is genuine. Use it as an additional source and state in the file which source answered which question.

Setting thresholds your team can apply

Write the rule down. A short policy removes the situation where two reviewers decide the same pair differently:

• Always required: date of birth equal, last-name part equal after normalization.
• Allowed with logging: missing middle names, hyphens, accents, order swaps, suffix differences, one transliteration variant.
• Needs a linking document: any last name that differs, any first name that differs by more than a transliteration variant.
• Must escalate: no link possible, or the account holder is a different person.

Collect only the name fields you need and keep identifiers such as Social Security numbers out of the comparison unless the check requires them; the FTC's guidance on protecting personal information is a sound baseline, and state privacy laws may add duties.

Automating the comparison

A validation tool should extract the name fields from each document, normalize them and show the result field by field with the reason for each difference. CheckFile compares fields, dates and register data across a file and flags differences for review; it does not certify that any document is authentic. To see how this fits a bank or KYC onboarding file, look at our KYC and banking solution, check pricing or read how we handle data in security.

Frequently Asked Questions

What is name matching on documents?

It is the comparison of a person's name across several documents or records, after normalizing accents, case, punctuation and order. The result is a verdict (cosmetic, explainable or unexplained) with a defined next step.

Should "John" and "Jon" be treated as the same name?

Only when the last name and date of birth match and your policy allows a one-letter first-name variant. Log the rule applied so the decision can be reviewed later.

What document proves a change from maiden to married name?

A certified marriage certificate is the usual link, or a court order for a legal name change. A divorce decree can link a name returned to the earlier last name.

Is fuzzy matching enough to approve a file?

No. Fuzzy scoring is useful to suggest that two names may match, but approval should rest on stated rules and, where a last name differs, on a linking document.

Does a name match prove the document is genuine?

No. It shows that two documents agree on a name. A forged document that copies the same name would match, so register or issuer checks remain a separate control.