What Home Office Actually Checks on a Translation

Every non-English or non-Welsh document in a UK visa application needs a certified translation, and the requirement is narrower than most applicants expect. UKVI is not grading the translation’s prose. Under Immigration Rules Para 39B, a caseworker is checking for four specific elements, and the overwhelming majority of translation-related refusals or delays we see trace back to one of those four being missing, not to the quality of the translation itself. Here is what Para 39B actually requires, and the patterns behind the translations that get flagged.

The four elements Para 39B requires

Para 39B sets out a short, specific list. A certified translation submitted to UKVI must include:

1. Confirmation it is an accurate and complete translation of the original document, stated explicitly rather than implied.
2. The date the translation was produced.
3. The translator’s full name and signature.
4. The translator’s contact details, so the translation can be verified if a caseworker has a question.

That is the entire standard. There is no requirement for notarisation, no requirement for a court stamp, and no requirement for the translator to hold a specific professional accreditation, though most reputable providers do hold one. A signed Statement of Accuracy carrying all four elements is, on paper, sufficient for every visa route UKVI processes. Where applicants run into trouble is not usually the translation itself; it is one of the four elements missing or presented ambiguously enough that a caseworker cannot immediately confirm it is there. We cover the requirement in more depth on our UKVI certified translation page.

The patterns behind rejected or queried translations

After reviewing enough of these files, the failure modes repeat. None of them are exotic.

Missing or vague accuracy confirmation. A translation that reads naturally but never actually states, in words, that it is a complete and accurate translation of the original. Caseworkers are trained to look for the statement, not infer it from the fact that a translation exists.

No date, or a date that does not match the document being submitted. This shows up most often when an old translation gets reused for a new application months or years later. If the translation itself is not dated to reflect when it was produced, or the date looks inconsistent with the rest of the application timeline, it draws a query.

A name with no matching signature, or a signature with no printed name to match it against. Both need to be present and legible. A scanned signature that is illegible, with no typed name alongside it, functions the same as a missing signature for a caseworker trying to verify the translator’s identity.

Contact details that do not actually work. An email address or phone number on the Statement of Accuracy that bounces or goes unanswered when a caseworker tries to verify something is worse than no contact details at all, because it looks like an attempt to obstruct verification rather than an oversight.

Partial translation of a multi-page or multi-stamp document. Translating the data fields of a certificate but skipping a stamp, an annotation, or a second page that carries relevant content. UKVI wants the complete document rendered, not a summary of the parts that look important.

Mismatched document identification. Where an application includes several translated documents and it is not immediately clear which translation corresponds to which original, particularly common with bundles of financial or employment evidence. Clear labelling that ties each translation to its source document removes an entire category of query before it starts.

None of these require better translation. They require the Statement of Accuracy to be complete, legible, verifiable and clearly attached to the right document. We build our translations to satisfy all four Para 39B elements as standard, and if UKVI raises a formatting query attributable to our work, we revise and reissue at no extra charge.

What Home Office does not need

It is worth being explicit about what UKVI does not ask for, because applicants routinely spend time and money on steps Para 39B never required. Notarisation is not required; a notary verifying the translator’s identity adds nothing UKVI’s own rules ask for. Apostille on the translation itself is not required either, though an apostille on the underlying foreign public document (a birth or marriage certificate, for example) is a separate matter that some receiving countries or specific UKVI routes may require independently of the translation. Sworn translation, in the continental European sense of a state-registered translator with an official seal, is not a UK concept and UKVI does not ask foreign documents to be translated by one; a UK certified translation meeting all four Para 39B elements covers the same ground.

Confusing these requirements with each other is common and costly. Booking a notary appointment because a form says “certified copy,” when the applicant actually needed a certified translation, adds days to a timeline that is often already tight. See our certified translation page for the broader UK standard, or if the underlying document also needs legalising, apostille and legalisation covers when that separate step is genuinely needed.

Which visa routes this affects most

Every route that requires supporting evidence in a language other than English or Welsh runs into Para 39B, but the volume concentrates in a few categories. Spouse and partner visa applications carry the highest document count per case, typically a marriage certificate plus supporting relationship evidence, and any inconsistency across those documents gets noticed because a caseworker is actively cross-checking names and dates between them. Skilled Worker applications bring in academic and employment documents where partial translation of stamped or annotated pages is a repeat issue. Student visa and ILR applications add financial evidence, where mismatched document identification across a bundle of bank statements or payslips is the most common query. Our spouse visa translation page has route-specific detail if that is the application you are working on.

What a caseworker actually does with the translation

It helps to understand the mechanics on the other side of the submission. A caseworker processing a visa application is not reading every translated document for literary quality; they are matching facts against the rest of the file. A name on a translated birth certificate gets checked against the name on the passport application. A date on a translated marriage certificate gets checked against dates given elsewhere in the relationship evidence. A translated bank statement gets checked against the financial requirement threshold for the specific route. The translation’s job is to make those facts legible and unambiguous, not to read smoothly as English prose, though a competent translation manages both.

This is why formatting discipline matters more than people expect. A caseworker under time pressure, working through a large caseload, is more likely to raise a query on a translation that makes them hunt for information than one that presents it clearly, even where both translations are equally accurate. Clear labelling, a visible Statement of Accuracy, and a layout that mirrors the original document’s structure all reduce the caseworker’s cognitive load, and a lower cognitive load translates directly into fewer queries.

Preparing a bundle a caseworker will not need to query

For applications involving several translated documents, a few habits consistently reduce query rates:

Translate documents in the same order they appear in the application form’s evidence list. A caseworker working through a checklist should be able to find the corresponding translation without hunting through the bundle.

Keep the Statement of Accuracy visually distinct on every translation. A short, clearly formatted statement block at the end of each translated document, rather than folded into a paragraph of running text, is easier to locate and verify at a glance.

Flag any discrepancy the applicant already knows about, rather than hoping it goes unnoticed. If a name is spelled two different ways across two genuine source documents, or a date format differs between an older and newer certificate, a one-line translator’s note explaining the discrepancy heads off a query that would otherwise cost weeks.

Submit translations as searchable text where the platform allows it, not as a scanned image of a printed translation. A searchable document is faster for a caseworker to cross-reference against the rest of the file, and it avoids the risk of an illegible scan being queried purely on legibility grounds.

None of this changes what Para 39B requires. It changes how quickly and cleanly a caseworker can confirm that the requirement has been met, which is the difference between an application that moves and one that sits in a query queue.

Getting it right the first time

The translation quality itself is rarely the problem. What separates a translation that sails through from one that draws a query is whether the Statement of Accuracy is complete, whether the date and signature are unambiguous, whether the contact details actually work if someone tries them, and whether every translated document is clearly tied to the original it belongs to. Build those four things into every submission and there is very little left for a caseworker to query. If you are assembling a visa application now and want a translation built to the Para 39B standard from the first draft rather than after a query comes back, send us the documents and we will quote a fixed price within fifteen minutes.