Almost every certified translation produced in this country is built on the same unspoken assumption: a foreign document goes in, English comes out, and a British authority reads it. Then an enquiry arrives that removes English from the equation altogether. This one asked us for a Ukrainian and Russian to Romanian notarised translation, produced in the United Kingdom, legalised here, and presented to a Romanian authority for legal and court use. No English source. No English target. No UK reader at the end of it. Just a UK notary, a UK apostille, and two Cyrillic documents that had to become one coherent Romanian file.
It came to us from a language-services partner rather than a member of the public — an interpreting agency placing the written work on behalf of its own client. That changed the tone of the job as much as the language pair did.
Representative note: this account is anonymised. The agency and its client are not identified, no names, dates, document numbers or places are given, and the name-spelling examples used further down are generic illustrations of a known problem, not details from this file.
The enquiry: two documents, one page, and a certification box that did not fit
The form told us this much. Country: United Kingdom. Service required: certified translation. Notarisation: yes. Document type: birth certificate. Purpose: legal and court use. Languages: Ukrainian to Romanian. Paper length: one. Nothing uploaded. The agency had arrived on our UK document legalisation page and come back to it before enquiring, which told us legalisation was already on their mind rather than something we would have to introduce.
Then the free-text message, which is where the real job always lives:
“I Have two documents for Legalisation 1 – Passport from Ukrainian to Romanian 2 – Birth Certificate 1page from Russian to Romanian”
Read the dropdowns and you have one language pair and one document. Read the sentence and you have two of each. We quote from the sentence, every time.
Two source languages, not one
The form recorded Ukrainian to Romanian. The message said the passport is Ukrainian and the birth certificate is Russian. That combination is completely ordinary and we see it often: a civil-registry document issued in the Soviet era, or in a Russian-speaking jurisdiction, is in Russian, while the same person’s modern travel document is Ukrainian. Nobody has made a mistake. The enquiry form simply has one source-language field and the job has two.
Operationally that is not a small correction. Two source languages means two qualified translators working in two different pairs — Ukrainian into Romanian, and Russian into Romanian — because a translator certifying a Ukrainian passport should not be certifying a Russian-language certificate on the strength of “it’s close enough”. The two languages are related, not interchangeable, and a certification statement is a personal professional declaration, not a convenience.
And it creates the one genuinely hard problem in the whole file.
One person, two Cyrillics, and only one acceptable Romanian spelling
If a receiving authority is given two documents about one human being, the human being has to be the same in both. That sounds trivial until you notice that the name on these two documents is being brought out of Cyrillic twice, by two different routes, from two different source spellings, into a third language with conventions of its own.
Ukrainian and Russian romanise the same name differently. The standard illustrations are the obvious ones: Volodymyr against Vladimir, Serhii against Sergey, Oleksandr against Aleksandr, Mykhailo against Mikhail. Patronymics and surname endings diverge too. Left to run independently, two conscientious translators can produce two perfectly defensible Romanian spellings of one name — and a Romanian official looking at a passport translation and a birth certificate translation will see two people, or at best one person with a documentation problem.
Romanian adds its own layer, because it has established habits for rendering Cyrillic names and its own diacritics. So the decision is not “which transliteration standard is correct” in the abstract. It is: which single Romanian spelling of this name will appear on both translations, in the certification wording, and in anything the notary writes?
That has to be settled before either translator begins. The passport’s own romanised spelling is the natural anchor, because it is the spelling the person actually travels and identifies under, and it is the one a Romanian official is most likely to be able to match against something else. The older Russian-language certificate would then be translated with that spelling carried across, with the certificate’s own source form recorded in a translator’s note rather than silently overwritten — so the authority can see exactly how the two documents relate instead of having to guess. That note is the difference between a file that answers a question and a file that raises one.
This is the real engineering in a job like this, and it has to happen first. Retrofitting a name across two certified documents after they have been signed, notarised and apostilled means doing the chain again.
A passport data page is not a certificate — what translating one actually involves
The second document type brought its own questions. A passport data page is mostly structured furniture: field labels, an issuing authority code, a document number, dates of issue and expiry, a place of birth, and the machine-readable zone at the foot of the page, which uses ICAO transliteration — a third romanisation that often matches neither the Ukrainian national form nor the Russian one.
A proper certified translation of a passport renders the fields, identifies and accounts for the machine-readable zone rather than quietly deleting it, describes the stamps, photograph and signature panel as present, and transcribes every identifier exactly as printed. Identifiers are never tidied, never reformatted, never re-spaced to look neater. A document number is a string, not a style choice, and an official checking it against a register is matching characters.
There was also a question worth asking before quoting at all: did the receiving body want a translation of the passport, or a notarised copy of it? Those are different products with different fees and different chains. Plenty of authorities asking for “the passport” want a notary-certified true copy of the data page, sometimes with a translation attached and sometimes not. Quoting for a translation when a certified copy was wanted, or the reverse, is a wasted step the client pays for. We asked.
“Home Office (UKVI)” was the wrong box, and it mattered
The certification field on the enquiry recorded Home Office (UKVI). It should not have, and this is not a pedantic point.
Nobody at UKVI will ever see this file. The documents are being legalised for use by a Romanian body, for legal and court purposes, in Romania. Had we taken the dropdown at face value, we would have produced a UK-facing certified translation into English with a UKVI-style certification statement — the wrong target language, the wrong certification wording, the wrong authority named, and no notarisation or apostille in sight. It would have been competent work and completely useless, and it would have been discovered at the Romanian end, by someone else’s client, after the deadline.
We see this field misread constantly, because applicants and even busy agency coordinators treat it as “the certification box” and pick the most official-sounding option in it. The field means who is going to read this. If the answer is a foreign ministry, a foreign court, a foreign registry or a foreign notary, UKVI is not the answer. If you would like the longer version of why the certification wording changes with the reader, our guide on choosing between certified and notarised translation walks through it.
The chain, in the only order that works — and what the FCDO can and cannot touch
For a translation produced in the UK to carry weight with a Romanian authority, the usual shape is: the translator’s certification, then a UK notary public’s act attesting the translator’s signature and identity, then an FCDO apostille on the notarial certificate. Both the United Kingdom and Romania are Contracting Parties to the Hague Apostille Convention of 1961, so an apostille is generally sufficient and full consular legalisation at the Romanian Embassy is usually unnecessary. Requirements do differ by document and by receiving body, and they change, so confirm your own route with the Romanian authority that will receive the file before you commit to it.
One constraint governs everything, and it surprises people: the UK legalisation service apostilles UK documents and the signatures of UK public officials. It cannot apostille a Ukrainian passport or a Russian-language birth certificate, because those were not issued here. The apostille attaches to the notarial act produced in the UK, not to the foreign originals. If the Romanian authority also wants the underlying foreign documents authenticated in their own right, that has to be done in the country that issued them — which is why one of our first questions was whether anything had already been apostilled at origin. Discovering that late is what turns a straightforward file into a month’s delay.
The sting in the tail: the notary’s certificate and the apostille are in English
Here is the part that catches out providers who have only ever worked into English. The translator’s certification, the notary’s attestation and the apostille are themselves documents — and in a UK chain they are drafted in English. So a file that contains no English at the start can finish with three English instruments stapled to the back of it.
Romanian practice for a translation between two foreign languages generally expects the certification wording, and the certification of the translator’s signature, to appear in the target language as well. Which means the translation step can have to happen twice: once for the source documents, and once for the authentications attached afterwards. You cannot translate the notarial certificate before it exists, and you cannot apostille a document that is still going to be altered, so the sequence has to be decided consciously rather than discovered.
We set it out honestly for the agency as a choice rather than a fact, because the right answer depends entirely on what the receiving body accepts:
- Certification wording drafted bilingually from the outset, in Romanian alongside English, so the translator’s statement already reads in the target language before the notary signs.
- Notarise and apostille first, then add a short certified Romanian translation of the notarial certificate and the apostille as a final annexe — attached, never inserted into the sealed set.
- If the authority insists on a translator authorised by the Romanian Ministry of Justice, or on certification by a Romanian notary or consular post, say so now — because then the sensible plan is a notarised copy set produced and legalised here, with the translation itself performed under the Romanian system. A Romanian diplomatic mission or consular post can certify a translator’s signature, which is a legitimate alternative route to a UK notarial chain.
One footnote that genuinely matters for anyone comparing routes: the EU rules on multilingual standard forms, which let certain civil-status documents travel between member states without translation, operate between EU member states. A document legalised in the United Kingdom does not travel on them. Post-Brexit, the apostille route is the route.
Nothing was uploaded, so the documents had to be identified by asking
No file came with the enquiry, which meant the instrument identification was a conversation rather than an inspection. Four questions did most of the work.
Which Ukrainian passport — the internal ID card or the international travel document? They are different documents with different fields, and “passport” is used for both. Which generation of Russian-language birth certificate — a Soviet-era booklet, a post-Soviet certificate, a re-issue or a duplicate? The layout, the issuing-body wording and the endorsements differ, and a duplicate or re-issue carries annotations that have to be rendered rather than ignored. How many sides actually carry content, given that the form said one page and reverse-side stamps are routinely forgotten? And had anything already been apostilled in the country of origin?
None of that is bureaucratic throat-clearing. Each answer changes the page count, the certification wording or the chain, and a quote issued before the answers arrive is a guess dressed as a price.
Working for a language-services partner, not a worried applicant
A member of the public wants reassurance. An agency wants a file it can stand behind in front of its own client, and it needs different things from us.
It needs a quotable breakdown it can mark up — translation per document and language pair, notarial attestation, apostille, any annexe translation of the authentications, and courier, listed as separate lines so the markup is clean and nothing is hidden inside a single number. It needs certification wording its client can rely on, with a clear statement of who certifies what: the translator certifies the accuracy of the translation, the notary attests the signature and identity of the translator and not the content of the documents, and the apostille authenticates the notary’s seal and nothing beyond it. Collapsing those three into “legalised” is how files get rejected.
It also needs confidentiality that survives a second hop, because the data belongs to the agency’s client rather than to the agency, and it needs to know we will not approach that client directly. And it needs us to behave like a supplier: answer in writing, flag the UKVI contradiction rather than silently working around it, and put the sequencing decision in front of the coordinator so it can be taken to the end client as a question. Professional readers do not need to be managed. They need to be told the truth early. Our sworn translation and embassy translation work runs on exactly that basis.
What the scope covered
Two documents and two language pairs, not one. The Romanian spelling of the name to be fixed and recorded in writing before translation begins, and applied identically across both documents, the certification wording and the notarial paperwork, with the differing source spelling carried in a translator’s note. A full rendering of the passport data page with the machine-readable zone identified and accounted for and every identifier transcribed exactly as printed. A complete notarised birth certificate translation covering every side that carries content, including seals, stamps and marginal annotations described rather than omitted. Certification wording naming the actual destination and purpose — legal and court use in Romania — with no reference to UKVI anywhere. A UK notary public’s attestation, an FCDO apostille on the notarial certificate, and a written sequencing recommendation for the Romanian translation of the authentications, subject to confirmation with the receiving body. And one itemised price breakdown the agency could quote onward without rewriting it.
Where the enquiry stood
Nothing had been translated at the enquiry stage — no document had been uploaded, so there was nothing yet to translate. The scope was ready once the agency confirmed which passport and which generation of birth certificate its client held, which authority in Romania would receive the file, and how that authority wanted the authentications handled. Until those answers arrive, a price would only have been a guess.
The decision we are proudest of is the unglamorous one. We stopped, asked which language each document was actually in, and told the agency the certification dropdown contradicted the job before we quoted. Ten minutes of questions meant nobody quoted for an English-language UKVI-style translation that no one on this file would ever have needed.
If you are in the same position, settle these before anyone translates a word
Confirm the language of each document individually rather than the language of the bundle, because a passport and a civil-registry certificate issued decades apart are frequently in different languages. Confirm who the reader is and in which country, and ignore any UK-authority option in a dropdown if the file is leaving the country. Decide the one target-language spelling of the name, in writing, before translation starts. Ask the receiving body whether it will accept a foreign certified translation with an apostille at all, or whether it requires a translator authorised in its own jurisdiction. Ask whether it wants the authentications translated too, and get the sequencing agreed. And count the sides, not the sheets.
Questions the agency asked us on this job
Can a UK provider certify a translation between two foreign languages, with no English involved?
Yes. A certification statement is a declaration by a qualified translator that the translation is a complete and accurate rendering of the document in front of them, and it does not require English to be one of the two languages. What changes is the wording, the language the wording is drafted in, and what the receiving authority will accept — which is why the destination matters more than the source.
Does Romania need full consular legalisation, or is an apostille enough?
Both the UK and Romania are parties to the Hague Apostille Convention, so an apostille on the UK notarial act is generally sufficient and embassy legalisation is usually unnecessary. Individual bodies and individual document types can still ask for more, so confirm with the authority that will receive your file rather than relying on the general position.
Can the FCDO apostille my Ukrainian passport or my Russian birth certificate?
No. The UK service legalises documents issued in the UK and the signatures of UK public officials. A foreign original has to be authenticated in the country that issued it. In a UK chain, the apostille goes on the notary’s certificate, and that is what gives the translation its standing abroad.
Why does the name have to be decided in advance?
Because the same Cyrillic name romanises differently out of Ukrainian and out of Russian, and a third language has conventions of its own. If two translators choose independently, one person arrives at the authority looking like two. Fixing the spelling first is cheaper than redoing a notarised and apostilled set.
Will the notary’s certificate and the apostille need translating as well?
Often, yes, because they are written in English. Practice for translations between two foreign languages generally expects the certification to read in the target language too. Plan for it: either draft the certification bilingually from the start, or add a certified translation of the authentications as an annexe afterwards.
Do you work with translation and interpreting agencies placing work for their own clients?
Regularly. Trade clients get an itemised breakdown they can mark up, certification wording that states plainly who certifies what, no direct contact with their client, and a straight answer when the brief contradicts itself.
Placing a two-language file for Romania?
Tell us what each document is, what language each one is actually in, and which authority in which country is going to read it. We will tell you which chain it needs, in which order, and where the translation has to happen twice — before anyone starts typing. Start with our legalisation service page, see our notarised translation of court documents for legal and court files, or send us the details and we will scope it properly.