| Wrong target script | Cyrillic and the traditional vertical script are both in play. Deliver the wrong one and the document is unusable for its purpose. | We establish the required script up front and set the whole document in it — Cyrillic or traditional. |
| Mongolian treated as Russian | Mongolian Cyrillic adds Өө and Үү. Handled as Russian, these sounds vanish and names are misspelled. | The full Mongolian alphabet is used, so every sound and name is correct. |
| Vowel harmony broken in suffixes | Case suffixes must match the stem's vowels. A mismatched suffix is ungrammatical and marks a text as non-native. | Suffixes are chosen in harmony with the stem, so grammar reads as native. |
| Patronymic filed as a surname | Mongolian names carry a father-based element, not a European family name. Treated as a surname, the record no longer matches the passport. | The patronymic is kept in its role and matched to the ID, so the name is accepted without a query. |
| Transliteration inconsistent with the passport | Cyrillic names can be romanised several ways. Varied across documents, a name diverges from the ID. | One consistent transliteration is fixed and matched to the passport across all documents. |
| Case suffixes “translated” as prepositions | Mongolian marks relations with suffixes, not prepositions. Rebuilt as prepositions, the structure reads foreign and can blur meaning. | We write from the agglutinative structure, with suffixes in their correct roles. |
| Soviet-era terms & Russian loanwords | Older documents carry Soviet terminology and Russian loanwords. Rendered literally, they mislead in a modern context. | Historical terms are recognised and rendered by their real meaning for today's reader. |