Document Translation for Latvia

Translating into English instead of Latvian is the costliest mistake

The commonest problem we see in files sent from Türkiye to Latvia is not technical but a matter of assumption: the document is translated into English first, on the belief that everyone in Riga speaks English. Latvia’s rules on the state language, however, require a document submitted to a public body in a foreign language to be accompanied by its counterpart in the state language. That the official can read English does not lift the requirement; the file is refused on the ground that it is “not in the state language”, and you pay for the translation twice. English can count as sufficient in some academic processes, university applications among them, but on the residence, civil registry and employment side the expectation of Latvian is the rule.

So the first question ought to be not “into which language” but “to which institution”. The same diploma may be wanted in English for a letter of admission and in Latvian for a residence application. Having both versions prepared together works out cheaper than paying a second time later on; seeing the per-page cost of preparing in two languages at the outset makes the job easier.

How will your name be written in the translation?

Latvian adapts foreign proper names to its own grammar: a grammatical ending is added to the forename and surname, and the spelling may shift to follow Latvian pronunciation. The result is this: the surname on your passport and the surname in the Latvian text do not look identical letter for letter. An official who does not know this may say “these documents belong to different people”, or conversely may find the text defective because the adapted form has not been used.

The practical answer is to keep the original Latin-script spelling from the passport in brackets alongside the adapted form. In family files this matters more still: where the marriage certificate, the birth certificate and the diploma show the same person under three different spellings, it is not one document that comes into question but the whole set. That is why we ask you to include a scan of the identity page of your passport when you send in your request.

The document set for your purpose

What notarisation confirms, and what it does not

In a notarised translation the notary confirms not the accuracy of the text but the identity and signature of the person who made the translation. The distinction matters in practice: an error of content will not be sent back by the notary, it will be sent back by the institution. Two different forms of notarisation are also muddled together – confirming that a copy of the document conforms to the original is not the same thing as confirming the translation. Sending a certification of the translation when the institution has asked for a “certified copy”, or the other way round, leaves the file incomplete.

Sequence, and a realistic timetable

• Obtain the original from the body that issued it; do not start from a photocopy.
• Have the certification annotation added before the translation – the annotation is part of the text and has to be translated too.
• Have the translation done into the right target language, and match the spelling of the name to the passport.
• If the institution asks for it, add the notarisation last of all.

The translation is usually the shortest step in the process; what stretches the timetable is obtaining the original and completing the chain of certification. With bulky files such as course descriptions the page count bears directly on the time, so sending the file in one piece rather than splitting it is both quicker and more consistent. Upload your documents and let us first settle together which layer you actually need; there is no sense in paying for certification you will not use.

Digital document or paper document?

Because a good part of Latvian public services runs electronically, applicants are used to uploading documents straight as PDFs. The verification links carried on electronic documents produced in Türkiye, however, work only on Turkish systems; the official at the other end cannot open the link and confirm that the document is genuine. The upshot is that a technically flawless printout comes back marked “source could not be verified”. A document being digital does not of itself make it valid internationally.

The right course is to obtain the wet-signed or sealed physical counterpart of the electronic document and to build the chain of certification on that copy. The translation must rest on the same copy, because the text of the translation states expressly which document it was translated from; that line and the paper in your hand have to agree. Once two different copies are in circulation, the question of which one is valid locks the file up.

With documents bearing a QR code or a barcode there is one more detail: those areas count as part of the text and cannot be disregarded in the translation. Having the verification code, the document number and the name of the issuing unit visible in the translation helps the official match the document to its source and heads off a needless exchange of queries.

• Do you have the physical original of the document, or only a printout?
• Was the certification annotation obtained before the translation, and on the right copy?
• Does the spelling of the name on the passport match the spelling in the translation?
• Does the institution want Latvian or English – and do you have that confirmed in writing?
• Will you be using the same document for another institution later on?

The account below summarises typical practice; each consulate applies its own current guidance. For the conditions in force, consult the institution’s current list of papers.