A Mistranslated Child's Name Delayed Immigration for Months

“Tatiana” or “Tetiana”? “Yevhen” or “Yevgeniy”? “Oleksiy” or “Olexiy”? One letter of difference - and your immigration application freezes for months. One family had their visa process delayed simply because their child’s name in the translated birth certificate didn’t match the name in the passport. Nobody was lying - the translator just used a different transliteration system than the one in the child’s passport.

This isn’t a rare case. As JK Translate reports, name errors are one of the most common reasons for delays and denials in immigration applications. And the most insidious part? Both spellings are technically correct - they just follow different transliteration standards. But the immigration officer isn’t required to understand the nuances of Cyrillic script. They see two different names - and hit the “Request for Evidence” button.

Let’s break down why a child’s name is the most vulnerable point in document translation, and how to protect yourself from months of delay.

Why a child’s name is the biggest problem¶

The logic is simple: an adult has a passport where their name is already transliterated into Latin script. The translator sees the passport and copies the spelling. Problem solved.

Now picture the situation with a child. A young child often doesn’t have a passport yet. Or they do, but the parents are simultaneously submitting a birth certificate where the parents’ names are written in Cyrillic - and the translator has to decide how to transliterate those names on their own. If they pick a different transliteration system than what’s in the parents’ passports - you end up with two different spellings of the same name in one document package.

As Immihelp explains, names on the birth certificate, passport, and all other documents must match completely. Any discrepancy - even a single letter - triggers a review.

And here’s what makes this situation especially painful:

• The child can’t fix their own documents - everything falls on the parents, who are already stressed about the immigration process
• The birth certificate is the primary document for visas, citizenship, and family reunification
• Ukrainian birth certificates list BOTH parents’ names - doubling the potential error points
• The patronymic (middle name based on father’s name) is a separate trap, because most countries don’t have this concept at all

5 transliteration systems - and none is “the only correct one”¶

Here’s the root of the problem. Ukraine has gone through several transliteration standards in the past 30 years, and each one produces a different spelling of the same name.

Cyrillic name	Passport (2010+)	Old passport	Via Russian	Via French (USSR)	Via Polish
Євген	Yevhen	Yevgen	Yevgeniy	Evgueni	Jewhen
Тетяна	Tetiana	Tetyana	Tatiana	Tatiana	Tetiana
Олексій	Oleksii	Oleksiy	Aleksey	Alexeï	Oleksij
Ганна	Hanna	Ganna	Anna	Anna	Hanna
Георгій	Heorhii	Georgiy	Georgiy	Gueorgui	Heorhij
Щербак	Shcherbak	Shcherbak	Shcherbak	Chtcherbak	Szczerbak

See the issue? Євген can be Yevhen, Yevgen, Yevgeniy, Evgueni, or Jewhen - and all five are technically correct because they follow different official standards used in different years. According to Cabinet of Ministers Resolution No. 55 from 2010, the current official standard is the 2010 passport transliteration. But older passports issued before 2010 use different rules.

As Wikipedia’s article on Romanization of Ukrainian explains, dozens of transliteration systems have been created over the years - via Russian, French, Polish, and German. Each produced unique spellings. And all of these variants currently exist in real documents belonging to real people.

Real cases: when one letter broke everything¶

Case 1: Months of delay from a child’s name in translation¶

As JK Translate reports, one family’s visa process was delayed for months due to a single error - the child’s name was recorded incorrectly in the translated birth certificate. USCIS compared the name in the translation with the name in the child’s passport - they didn’t match. Result: a Request for Evidence (RFE), new expenses for a retranslation, and months of waiting.

The cost of the aftermath? By their own estimates, fixing an error through an RFE costs between $1,500 and $5,000 - legal fees, new translation, postage, and most importantly, lost time.

Case 2: Mother is “Tetiana” in passport, “Tatiana” in translation¶

On the VisaJourney forum, here’s the situation described: the translated birth certificate listed the mother’s name as “Tatiana” (via Russian transliteration), while her passport showed “Tetiana” (per the 2010 Ukrainian passport standard). USCIS raised a red flag: “Who is this Tatiana? The passport says the mother is Tetiana. Are these the same person?”

A one-letter discrepancy - “a” instead of “e” - and the application was put on hold for review. The family had to submit additional documents and an explanation letter (affidavit) to prove that Tatiana and Tetiana are the same person.

Case 3: “Oleksiy” vs “Aleksey” - two completely different people?¶

On the immigration.com forum, an applicant describes a classic problem: the name on the marriage certificate (translated via Russian - “Aleksey”) doesn’t match the passport name (“Oleksiy” - per the Ukrainian system). The difference isn’t cosmetic - to someone who doesn’t speak Slavic languages, these look like two completely different names.

The result: the FBI name check gets repeated with the new name combination, which can add 60+ days of delay to the process. And if the applicant previously filed documents with one spelling and now files with another - that’s yet another layer of confusion in the system.

Case 4: Canadian visa rejected over name in translation¶

On the CanadaVisa forum, a case is described where a visa was rejected specifically because the name spelling in the passport didn’t match the translated document. IRCC requires translations to be word-for-word and match the original exactly - but names also need to match the passport. If the Cyrillic original has one spelling and the Latin passport has another - the translator is caught in a trap: an accurate translation from the original doesn’t match the passport.

Ukrainian letter traps: Є, Ї, Ґ, and others¶

Some letters in the Ukrainian alphabet are a genuine minefield for transliteration. Here are the most problematic ones.

Г vs Ґ¶

Ukrainian has two “g” sounds - Г (pronounced as a fricative “h”) and Ґ (pronounced as a plosive “g”). Under the current passport system: - Г → H (Григоренко → Hryhorenko) - Ґ → G (Ґалаґан → Galagan)

But in Soviet passports, Г was transliterated as “G” (via Russian, where Г = G). So Григоренко in old documents is Grigorenko, and in new ones - Hryhorenko. To an immigration officer, these are two different surnames.

Є¶

Є is transliterated as “Ye” at the beginning of a word and “ie” after a consonant. But in the Russian system, Е is often rendered simply as “E”. So: - Євген → Yevhen (Ukrainian system) or Evgeniy (via Russian) - Єлизавета → Yelyzaveta or Elizaveta

Ї¶

Ї → “Yi” in the Ukrainian system, but often gets lost when translating via Russian: - Їжак → Yizhak (Ukrainian) or Yezhak (via Russian)

І vs И¶

This is a classic. Ukrainian І = I, while И = Y. But in Russian, И = I. So: - Ірина → Iryna (Ukrainian) or Irina (via Russian) - Дмитро → Dmytro (Ukrainian) or Dmitriy (via Russian)

As ukrainiansintheuk.info explains, Soviet foreign passports transliterated names through French, which produced even more exotic variants: “Chtcherbak” instead of “Shcherbak,” “Gueorgui” instead of “Heorhii.”

The patronymic problem: an issue that doesn’t exist in most countries¶

Ukrainian birth certificates include not just a first name and surname, but also a patronymic (a name derived from the father’s first name). That’s standard in Ukraine, Russia, and a few other countries. But for the rest of the world, it’s a confusing third name element that doesn’t fit into any form.

Problems with patronymics in immigration documents:

Situation	Problem	Example
Form only has First Name and Last Name fields	Where does the patronymic go?	Oleksandr Petrovych Kovalenko - First: Oleksandr, Middle: Petrovych? Or First: Oleksandr Petrovych?
Passport has patronymic, form doesn’t	Discrepancy between documents	Passport: Oleksandr Petrovych Kovalenko. Form: Oleksandr Kovalenko
Child without a patronymic	Empty field looks suspicious	Certificate has the name but no patronymic (e.g., single mother)
Female vs male patronymic	Translator confuses endings	Petrivna (female) vs Petrovych (male) → Petrivna vs Petrovych

According to USCIS policy, when verifying identifying information, the officer checks all name variants across all documents. If one document has a patronymic and another doesn’t, it can trigger additional review.

Tip: when translating documents for countries that don’t use patronymics, list it as a middle name and make sure it’s translated identically across all documents in the package.

How the discrepancy happens: step-by-step anatomy of a mistake¶

Here’s the typical scenario that gets families into trouble.

Step 1. Mom Tetiana gets her passport in 2020. Under the 2010 standard, her name is transliterated as Tetiana.

Step 2. A child is born. The birth certificate lists the mother’s name in Cyrillic: Тетяна.

Step 3. The family applies for a visa. The translator receives the birth certificate and needs to transliterate the mother’s name. They don’t see the mother’s passport (or don’t think to cross-reference), and write Tatiana - because it “sounds more natural” and is how this name is more commonly spelled in English.

Step 4. In the document package: the mother’s passport says “Tetiana” while the translated certificate says “Tatiana.” The officer sees two different names - and hits “RFE.”

Step 5. The family receives a request for additional evidence. Now they need a new translation, an explanation letter (affidavit of name discrepancy), possibly a lawyer - and 3-6 months of waiting.

All because of one letter. “e” instead of “a.”

Affidavit of Name Discrepancy: when the mismatch already exists¶

If a discrepancy has already been found - don’t panic. There’s an official tool: the Affidavit of Name Discrepancy.

As LawBench explains, this document confirms that different spellings of a name refer to the same person. It should include:

1. The applicant’s full name - all spelling variants found across documents
2. Explanation of the reason for discrepancy - different transliteration systems, changed standards, translation via a third language
3. List of documents with different spellings - passport, birth certificate, translation
4. Oath statement: “I declare under penalty of perjury that the foregoing is true and correct”
5. Signature and date - notarization is recommended but not required for USCIS

For Canada, IRCC requires that an explanation be submitted alongside the translation, and the translation must be done by a certified translator (through ATIO, OTTIAQ, or STIBC).

For Germany, the situation is simpler - Ausländerbehörde typically accepts the translator’s explanation as a note within the translation, and a sworn translator (beeidigter Übersetzer) can add a comment about the reason for the discrepancy directly in the translation.

7 iron rules for translating names in immigration documents¶

These rules will save you from months of delay.

1. Always cross-reference with the passport¶

The golden rule: the name in the translation of ANY document must match the name in the passport. Letter for letter. Not “what sounds better,” not “what’s more correct” - but what’s written in the passport. USCIS, IRCC, and Ausländerbehörde all compare against the passport.

2. Ask the translator for all family passports¶

If you’re translating a child’s birth certificate - give the translator passports for BOTH parents. Not just the child’s. The certificate lists both parents’ names - and both must match their passports.

3. Don’t mix transliteration systems¶

If Mom’s passport says “Tetiana” - write “Tetiana” everywhere. Even if your gut tells you “Tatiana” sounds more natural in English. Consistency matters more than aesthetics.

4. Pay special attention to the patronymic¶

Decide in advance where to put the patronymic: as a middle name, as part of the first name, or on a separate line. And do it the same way across all documents. If the passport includes the patronymic - the translation must too. If the passport doesn’t have it - note it in the translation as “patronymic” with an explanation.

5. Check ALL names in the document¶

A birth certificate has at least three names: child, mother, father. A marriage certificate has two. A work reference has the employee’s name and the signatory’s. Each name is a potential error point. Check every single one.

6. Include a translator’s note¶

If the Cyrillic original spells a name differently than the passport (e.g., an old certificate with Soviet standards) - the translator should add a note: “Name transliterated as per passport No. XX dated YY” or “Original Cyrillic: Тетяна. Transliterated as Tetiana per current Ukrainian passport standard.”

7. Use a qualified translator¶

Seems obvious, but over 20% of delays in visa applications happen due to document errors. A translation by “a friend who knows English” is a direct path to an RFE. For USCIS, you need a certified translation with a Certificate of Accuracy. For Germany - a sworn translation. For Canada - a translation by a certified ATIO/OTTIAQ/STIBC translator.

On ChatsControl, AI translation goes through multiple rounds of review. But for immigration documents where name accuracy is critical - we recommend additionally ordering a certified translation from a certified specialist.

What to do if the mistake has already been made¶

Documents haven’t been submitted yet¶

Just order a new translation. Make sure the translator has passports for everyone whose name appears in the document. Compare every name in the translation against the passport. This is the cheapest and simplest option.

Documents submitted, no RFE yet¶

As Nolo explains, for most immigration forms you can submit an amendment letter with the correct translation. For DS-160 - open the saved application and fix it. The sooner you notify them, the fewer problems you’ll have.

You’ve received an RFE¶

You have 30-90 days to respond. As ASAP Translate recommends, structure your response like this: Cover Letter → Index of Exhibits → point-by-point explanations → new translations. Include an Affidavit of Name Discrepancy explaining the reason for the mismatch (different transliteration systems). Send it 10-14 days before the deadline to account for mail delays.

You’ve received a denial¶

This is the worst-case scenario. But even after a denial, you can re-file or appeal the decision. Consult an immigration lawyer - lawyer fees are lower than the losses from re-filing from scratch.

Name translation requirements by country¶

Country	Translator requirement	Names must match	What to do if there’s a discrepancy
USA (USCIS)	Certified translation + Certificate of Accuracy	Passport	Affidavit of Name Discrepancy
Canada (IRCC)	Certified translator ATIO/OTTIAQ/STIBC	Passport	Explanation letter + notarization
Germany	Sworn translator (beeidigter Übersetzer)	Aufenthaltstitel or passport	Translator’s note within the translation
UK	Certified translator	Passport or BRP	Explanation letter for UKVI
Australia	NAATI-certified translator	Passport	Statutory declaration

Pre-submission checklist: 8 name verification checkpoints for translated documents¶

Before you take your documents to the embassy - go through this list:

1. Every name in the translation matches the passport. Compare letter by letter - the child’s name, the mother’s, the father’s.

2. The patronymic is handled the same way across all documents. If you list it as a middle name - do it everywhere. If you don’t list it - don’t list it anywhere.

3. The mother’s surname is recorded correctly. Ukrainian certificates often list the mother’s maiden name - check that it matches what’s in the passport.

4. There’s no mixing of transliteration systems. If the passport uses the Ukrainian system (Tetiana, Oleksii, Hryhorii) - the translator shouldn’t switch to the Russian system (Tatiana, Aleksey, Grigoriy).

5. Special characters are handled correctly. Є → Ye/ie, Ї → Yi, Ґ → G, Г → H. If the passport uses a specific transliteration - stick with it.

6. The translation was done by a qualified translator. For USCIS, IRCC, Ausländerbehörde - each has its own qualification requirements.

7. There’s a translator’s note for any potential ambiguity. “Name transliterated as per Ukrainian passport standard” or “Cyrillic original: Тетяна Петрівна Коваленко.”

8. Passports for everyone whose name appears in the document were provided to the translator. Not just the applicant’s - everyone’s.

FAQ¶

Why does the name in my translation differ from my passport if the translator did it correctly?¶

Because there are multiple “correct” transliterations. The translator may have accurately transliterated the name using one standard (say, ISO 9), while the passport uses a different standard (the 2010 Ukrainian passport transliteration). Both are valid - but the immigration officer sees two different names. The fix: always cross-check the translation against the passport and require the translator to copy the spelling from the passport.

Can a name error actually cause a visa denial?¶

Yes, and it happens regularly. A mismatch between the name in the translation and the passport name triggers a Request for Evidence (RFE) at USCIS, delaying the case by 30-90 days minimum. In cases of repeated discrepancies or suspected fraud - it can lead to denial. For Canada, IRCC may deem the application incomplete and return the entire package.

What should I do with the patronymic when translating for countries that don’t have one?¶

The safest approach is to list the patronymic as a middle name. That’s a standard field on most immigration forms. If the passport includes the patronymic - the translation must too. If the form doesn’t have space for a middle name - list the patronymic in the Other Names Used field and add a note: “patronymic name as per Ukrainian naming convention.”

Do I need a new translation if I got a new passport with different transliteration?¶

Yes. If you received a new passport with a different name spelling (for example, after transliteration standards changed), all document translations supporting your immigration application need to be updated. An old translation with “Tatiana” won’t work if your new passport says “Tetiana.” It’s an extra expense, but far less than the delay caused by an RFE.

How do I verify that the translator transliterated the name correctly?¶

Compare every name in the translation against the corresponding passport. If someone listed in the document doesn’t have a passport - check against the official transliteration table from the Cabinet of Ministers of Ukraine. And make sure to tell the translator exactly which transliteration to use - don’t leave it to their discretion.