What a Statement of Accuracy Actually Says

The Statement of Accuracy is the single page that turns a translation into a certified translation. Most of what UK receiving authorities rely on when they accept a translated document as evidence is contained on it: who translated the document, that the translation is complete, when it was produced, and how the caseworker can verify any of it if they need to. The wording of the Statement is less standardised than people expect, and matters less than the formatting. What matters is that a specific set of elements is present, unambiguous, and easy for a caseworker to locate under time pressure. Here is what a well-formed Statement of Accuracy carries, why each element is doing a job, and where the most common failures show up.

What certified means in the UK, and where the Statement fits

A certified translation in UK practice is an accurate rendering of a full source document accompanied by a signed declaration from the translator or provider confirming the translation is complete and accurate. That signed declaration is the Statement of Accuracy. It is not a formality tacked onto the end of the file. It is the mechanism by which the translation becomes certified at all. Strip the Statement off and what remains is a translation, not a certified translation, and UKVI, HM Courts and Tribunals Service, universities and any other UK authority receiving a translation will not treat it as evidence of the underlying foreign-language document.

The UK, like Ireland, does not operate a state register of sworn translators. Where continental systems in Spain, Poland, France or Germany hand a translator a state-conferred authority that carries its own registry number and seal, the UK does the same job through the Statement of Accuracy. Our sworn vs certified translation page has the country-by-country detail, but the practical upshot is straightforward: the credibility of a UK-issued certified translation rests on the Statement of Accuracy. On the fact of it being present, on its being formatted so a caseworker can find and verify it, and on the identity and contactability of the signatory. Everything a UK receiving authority needs in order to trust the translation lives on that page.

The five elements a well-formed Statement carries

Strip a well-formed Statement of Accuracy down to its load-bearing parts and there are five. First, an explicit accuracy claim: a sentence stating in plain terms that the translation is a true and complete rendering of the original document. Not implied, not folded into a cover letter, but stated in words on the same page as the translation itself. Second, the identity of the certifying translator or provider: for us, that is “Tatkowski Certified Translator” printed clearly, alongside our company registration where the receiving office wants it. Third, working contact details, so a caseworker with a query can actually reach us. Fourth, the date the translation was produced, in an unambiguous format. Fifth, a signature, wet or digital, that binds the identity in the second element to the accuracy claim in the first.

For UKVI applications specifically, those five elements map almost exactly onto the four requirements set out at Immigration Rules Para 39B: confirmation of accuracy, date, translator’s full name and signature, and contact details. We covered the Para 39B breakdown in more depth on UKVI certified translation, and it is worth reading that alongside this piece if you are assembling a visa file. What the five-element frame adds is a way of thinking about the Statement that works across every UK recipient, not just the Home Office: courts, universities, employers and private-sector bodies all look for the same underlying anatomy, even when they do not name it as such.

What a caseworker actually does with the Statement

Understanding what happens on the receiving side clarifies why the formatting discipline matters. A UKVI caseworker, a court clerk at HM Courts and Tribunals Service, a First-tier Tribunal Immigration and Asylum Chamber registrar or a university admissions officer is not reading the translation for literary quality. They are matching the facts against the rest of the application file, and they are checking that the Statement of Accuracy is present and complete so the translation itself can be treated as evidence.

The first check is presence. The Statement needs to be visible, ideally on a page of its own or in a clearly delineated block at the end of each translated document, rather than folded into running text. A caseworker under time pressure has seconds to locate it. The second check is the five elements. If any element is missing or ambiguous, the caseworker’s options are to reject the translation or to route a verification query to the translator’s contact details. Either outcome slows the application, and query-routed applications routinely lose weeks. The third check is coherence with the rest of the file: names in the translation get cross-referenced against passports and application forms, dates on translated certificates get cross-referenced against dates given elsewhere, and a translated document that contradicts itself or contradicts the wider file gets flagged. Our how we work page describes the workflow we run to head off all three failure modes before submission.

The common formatting failures we see

None of the failures we see are exotic. They repeat, and they cluster in a small number of predictable places. The most common is an accuracy claim that never actually states, in words, that the translation is complete and accurate: a cover paragraph implying certification without ever containing the certifying sentence. Caseworkers are trained to look for the claim, not infer it, and an implied claim reads as a missing one.

Illegible signatures are a close second. A scanned signature compressed to a smudge does not fulfil the signature requirement on its own, particularly if the printed name below it is also unclear. Both need to be present, both need to be legible, and together they need to identify the certifying party without ambiguity. Contact details that bounce when a caseworker tries them (an email routed to a closed inbox, a phone number nobody answers) are worse than absent contact details, because they look like an attempt to obstruct verification rather than an honest oversight. A Statement failing at contact-detail verification places the entire translation under suspicion even where every other element is correct.

Ambiguous dates draw more queries than most translators realise. A translation dated “March 2026” without a day, or dated in a format that could be read as DD/MM or MM/DD, forces the caseworker to guess. UK receiving authorities default to DD/MM/YYYY, but a translator working across markets can slip into US-style formats without noticing, and the resulting ambiguity is enough to generate a query on an otherwise clean file. Incomplete identity is the last common failure: a first name and initial with no company name, or a company name with no signatory, leaves the receiving authority uncertain who exactly stands behind the accuracy claim.

Statement of Accuracy vs Statement of Truth: two different documents

One clarification worth making before it causes confusion. A Statement of Accuracy is what certifies a translation. A Statement of Truth is a distinct court document governed by Civil Procedure Rules Part 22 and CPR 32.14, used to verify witness statements, statements of case and certain other filings in civil court proceedings. The two get conflated because the wording overlaps and both involve a signed declaration, but they do different jobs.

For a translation used in a UKVI visa application, a First-tier Tribunal Immigration and Asylum Chamber appeal, an HMCTS civil claim, or a Magistrates’ or Crown Court hearing, the Statement of Accuracy on the translation itself is the certifying mechanism. What CPR 32.14 adds in the court context is a separate Statement of Truth that a party to the proceedings signs to verify a document being relied on. That Statement of Truth may reference a translated exhibit, but it does not replace the need for the translation itself to carry its own Statement of Accuracy. Translations used purely for UKVI purposes under Para 39B need the Statement of Accuracy only; translations exhibited in court proceedings typically carry the Statement of Accuracy on the translation and are then referenced by a separate Statement of Truth in the wider filing. Confusing the two, or assuming a Statement of Truth in the case file removes the need for a Statement of Accuracy on each translation, is a recurring mistake in litigation bundles.

Digital versus wet signatures, and where apostille sits

Both digital and wet signatures satisfy the UK certification standard. UKVI accepts digital-signed Statements of Accuracy on PDF submissions without asking for a hard copy, HMCTS accepts them in filed evidence, and university admissions accept them for enrolment paperwork. Where a hard copy is needed we produce a wet-signed and stamped physical version alongside. The segment that still routinely asks for wet is private-sector recipients: some banks, some overseas conveyancers dealing with UK property transactions, and some employers used to older paper workflows. When that is the case we send both a digital-signed PDF and a wet-signed hard copy in the post, because it removes an entire class of query about signature type before it starts. Language-specific pages such as Polish translation and Ukrainian translation walk through the document types where wet signatures still come up most often, particularly civil documents from jurisdictions where receiving offices back home have not moved fully to digital.

Apostille sits on a separate track. The 1961 Hague Apostille Convention legalises the origin of a public document for use in another Convention country. It does not legalise the translation, and UKVI does not require apostille on translations submitted with a visa application. Where apostille does come in is on the underlying foreign public document, if the receiving country outside the UK asks for one on a UK-issued certificate before accepting it. In the UK, the FCDO Legalisation Office is the issuing body. Our apostille and legalisation page covers when that separate step is genuinely needed and when it is not, alongside the certified translation cost page for pricing. If you are assembling a Home Office bundle, the broader UKVI translation guide walks through the full sequence.

What we put on every Statement we issue

Every certified translation we issue carries the same Statement structure, without variation across document types. The accuracy sentence is present in explicit terms, confirming the translation is a true and complete rendering of the original document. The certifying identity is printed as “Tatkowski Certified Translator” with our company registration and UK trading address. Contact details include a working telephone number and an email address that reaches an actual monitored inbox, not a no-reply forwarder. The date is written in DD Month YYYY format to remove ambiguity. The signature appears both as a digital signature block and, on hard copies, as a wet signature over the printed name, with a stamp where the receiving office asks for one.

That standard is what a UKVI caseworker, a court clerk at HMCTS, a First-tier Tribunal Immigration and Asylum Chamber registrar or a university admissions officer sees when they open one of our translations. It is designed so the five elements can be verified in under a minute without hunting through the file. The formatting discipline is what turns an accurate translation into a certified translation that will actually be accepted. Send us the document you need translated and the Statement will be built to that standard from the first draft.