Last updated: June 2026
This is the most common quiet panic on a visa file: you've collected birth certificate, marriage certificate, passport, bank statements, and the name on each one isn't quite the same. Mohammed on the birth certificate, Muhammad on the passport, Mohamed on the marriage certificate. The fear is that UKVI will read the file as belonging to three different people. The reality is that caseworkers see this pattern every working day, and a clean translator's note fixes most of it without anyone needing an affidavit or a corrected document.
Names in Arabic, Cyrillic, Devanagari, Chinese and other non-Latin scripts have no single 'correct' Latin spelling. Different officials, in different decades, using different transliteration conventions, produce different Latin renderings of the same name. The mismatch is normal, not a sign that anything is wrong.
The underlying issue is that transliteration isn't translation, and there's no universal standard.
An Arabic name like محمد can be Latinised as Mohammed, Muhammad, Mohamed, Mahomet, Mohammad and several other variants. Each spelling is a phonetic approximation, and which one ends up on a document depends on the official who issued it. A Pakistani passport office in 1985 used different conventions from a Saudi civil registry in 2010 from a Dubai immigration counter in 2022.
The same applies to Russian and Ukrainian names (Yuri vs Yury vs Iurii, Aleksey vs Alexey vs Alexei), Chinese names (Wang Xiaoming under pinyin vs Wong Siu Ming under Cantonese Wade-Giles), Indian names (Krishnan vs Krishnan vs Krishna with different parental affix conventions across states), and Tamil names (where the parental initial can appear before or after the personal name).
In other words: the variation is structural, not a mistake. Trying to 'correct' the documents into a single spelling is usually impossible because each was issued by a different authority on a different date, and each authority's record is the binding one for documents it issued.
UKVI caseworkers are trained to expect transliteration variation across documents from non-Latin-script countries. The file passes when the translation includes a translator's note explicitly stating that the variant spellings refer to the same person, and when the documents otherwise reconcile (dates, parents, places).
UKVI's published guidance on document verification acknowledges name-spelling variation as a normal feature of files from many countries. Caseworkers don't expect a Saudi passport spelling to match a Saudi birth certificate spelling, especially when the documents are decades apart.
What they look for instead is supporting consistency. The birth certificate's date of birth matches the passport's. The parents' names on the birth certificate match the parents' names on the marriage certificate. The address history reconciles. The pattern of evidence supports a single applicant identity, even if the Latin spelling of the name on each document is slightly different.
The translator's note is the procedural bridge. It sits at the end of the certified translation and reads something like: 'The applicant's name appears as MOHAMMED on the Arabic birth certificate and as MUHAMMAD on the UK passport. Both are valid transliterations of the same Arabic name (محمد).' Caseworkers accept this routinely. What's not acceptable is a translation that silently picks a spelling and doesn't flag the variation; that puts the caseworker in the position of comparing names with no explanation and having to RFI for one.
A translator's note solves transliteration variants (different Latin spellings of the same non-Latin name) and minor spelling errors (single-letter typos). It does not solve substantive name changes (marriage, court-ordered change, religious conversion), for which the underlying name-change document needs to be translated as well.
The clean cases the note handles by itself:
Transliteration variants of the same underlying name. Mohammed/Muhammad. Yuri/Yury. Krishna/Krishnan. The note explains the variants and confirms the underlying name is the same; UKVI accepts it.
Official typos and OCR errors. An older Indian birth certificate prints 'Ramesh Kumar' as 'Rmaesh Kumar' due to a registrar's typo. The note flags the typo as a transcription error in the source, not a different person; the supporting evidence (parents, date) confirms identity.
Different script systems for the same person. A Hong Kong applicant with a Cantonese-Wade-Giles passport name (Wong Siu Ming) and a mainland-Chinese-pinyin birth certificate (Wang Xiaoming) — same Chinese characters, different Latin systems. The note presents the Chinese characters and confirms both Latin renderings are the same name.
The cases where the note isn't enough:
Substantive name change after marriage. The applicant's birth name is Anna Volkova, her UK marriage certificate names her as Anna Smith. UKVI expects the marriage certificate to appear in the file as the bridging document, not just a translator's note explaining the change.
Court-ordered name change. A deed poll, gazette notification or court order issued by the home country needs to appear as a translated document, with the certified translation covering the order text in full.
Religious conversion changing the legal name. The certificate of conversion issued by the relevant authority needs to be in the file as a translated document.
Gender transition. The legal-recognition certificate from the home country, if any, needs to be in the file as a translated document.
Ask the translator to add a consolidated identity note at the end of each affected document's translation, listing every variant spelling that appears across the file and confirming they refer to the same person. If the file is already submitted and the variants weren't flagged, expect an RFI and reply with the consolidated note as the response.
The cheapest path is to surface the variants before the file is submitted.
When the translator quotes for the work, send all the documents at once and explicitly tell them which spellings appear where. The translator then prepares each certified translation with a closing note that reads, in effect: 'Note on identity. The applicant's name appears in this file as follows: Mohammed on the birth certificate, Muhammad on the passport, Mohamed on the marriage certificate. All three are valid Latin transliterations of the same Arabic name محمد and refer to the same individual.' That note appears on every certificate's translation, signed by the translator under the statement of accuracy.
When the file has already been submitted and an RFI lands asking 'Please clarify the variation in name spelling between documents A and B', the right response is the same note prepared retrospectively. The translator issues a brief addendum certificate listing the variants and confirming identity. Cost: usually £20–£40 per document covered. Turnaround: same business day. UKVI accepts it as a curative response.
What doesn't help: submitting an affidavit from the applicant declaring 'I am the same person'. That's a self-declaration with no independent linguistic weight. The translator's note is independent because the translator is a third party certifying the transliteration variation, not the applicant asserting their own identity.
Not on its own. UKVI caseworkers see transliteration variants every day, especially on files from Arabic, Cyrillic, Devanagari and Chinese-script countries. The fix is a translator's note flagging the variants as transliterations of the same name.
Usually not necessary. An affidavit is a self-declaration; a translator's note is independent third-party certification, and that's what UKVI actually wants. Save the affidavit for substantive identity issues, not transliteration variants.
Both passports are valid government-issued identity documents. The translator's note explains the variation as a transliteration difference between the two issuing authorities, supported by the matching date of birth and place of birth on both passports.
Sometimes, but it's slow and rarely necessary. Civil-registry corrections in most countries take weeks or months and require a specific reason. The translator's note is the faster, cheaper route for transliteration variants.
The marriage certificate itself is the bridging document and needs to be in the file as a certified translation. A translator's note alone is not enough for a substantive name change; the certificate (or court order, or deed poll) is the underlying evidence.
Not strictly, but referencing ISO 9 for Cyrillic, Hanyu Pinyin for Chinese, or the country's official transliteration convention for Arabic adds weight. UKVI accepts the note either way; a citation makes it look more thoroughly considered.
UKVI-accepted certified translations from £12.99 per page. Statement of accuracy included. 24-hour delivery.