The client’s problem
Manpreet’s request was a single line, typed quickly and with one word misspelled: translate my birth certificate from Punjabi to English for immigration to New Zealand. One page. A photograph of the certificate attached. The service selected was immigration document translation, the receiving authority recorded as Immigration New Zealand, notarisation ticked on, and the purpose recorded as “Residency/Citizenship”.
Three things in that record needed settling before any translating happened, and none of them was the Punjabi.
Why it was harder than it looked
The first thing was that the certificate was already partly in English.
Birth certificates issued in Punjab under India’s births and deaths registration framework are routinely bilingual. The form is printed with field labels in Punjabi and often in English too, and the entries may be filled in Gurmukhi, in English, or in a mixture, depending on the registering office, the year and the clerk. A great many of these documents arrive looking as though they have already done the translator’s job.
They have not, and the reason is specific. On a bilingual certificate the English layer is frequently incomplete – labels in English but entries in Gurmukhi, or some entries transliterated and others not – and where both layers are filled in, they sometimes disagree. A name may be rendered one way in Gurmukhi and spelled another way in the English field. A place name may appear in two forms. The pre-printed English label may describe a field that the Punjabi entry has been used to record something slightly different in.
A client looking at that document sees English on the page and reasonably concludes that an official reader will be able to read it. An official reader looking at the same document sees a form they cannot fully parse, with gaps where the entries are in a script they do not read, and in some cases two different answers to the same question. What they need is a complete English rendering of everything on the page, produced by someone who can read both layers and who will say plainly where the two do not match – rather than a document that half-speaks their language and leaves the other half to be guessed at.
That last point is the one that earns the fee. Where a bilingual certificate’s two layers disagree, the translator’s job is not to pick the better-looking version. It is to render both and make the discrepancy visible, so that the reader can deal with it. Quietly adopting the English spelling because it looks tidier conceals a fact the authority is entitled to see, and conceals it in a document whose entire purpose is to be relied upon.
The second thing was the purpose field, which offered “Residency/Citizenship” as a single choice. Those are two different applications, to two different agencies, with two different sets of requirements. Residence is Immigration New Zealand. Citizenship is the Department of Internal Affairs. A client selecting a field that bundles them has not told us which one they are doing, and the client’s own message said “immigration”, which pointed to residence – so that is what we worked to, having confirmed it rather than assumed it. Preparing a document to the wrong agency’s standard is a common and entirely avoidable cost. (We saw the mirror image of this on a Russian-language certificate going to the Department of Internal Affairs, where the question was the language of the document rather than the agency reading it.)
The third thing was the notarisation tick, and this is where we saved the client money.
Immigration New Zealand’s requirement for a translated document is about the translation’s quality and the translator’s independence. It wants a complete and accurate English translation, produced by someone competent to do it, who is not the applicant and not a member of the applicant’s family, and who identifies themselves. That independence rule is the heart of it, and it is more specific than many people realise: a translation produced by a cousin who speaks excellent English fails, not because the English is poor but because the translator is inside the family. This is the single most common reason an otherwise good translation is rejected on an immigration file.
Notarisation is a different service entirely. A notary public attests to the execution of a document or the identity of a signatory; a notary does not verify the accuracy of a translation and is not qualified to, unless they happen also to read the source language. On an INZ residence file, for a certified translation of a civil-status document, the notarial layer adds cost and turnaround and answers a question nobody has asked. The tick on the form was almost certainly a precaution rather than a requirement someone had communicated.
Fourth, there was the question of what the certificate’s own issue date says. Where an Indian birth certificate was registered long after the birth it records, that is visible on the face of the document, and a reader will see it. It is not our place to comment on it in the translation, but it is very much our place to make sure the issue date and the registration date are both rendered clearly and distinctly, because a translation that blurs them removes information the authority uses.
How we approached it
We read the whole document first, both layers, and built one picture of it: which fields were pre-printed in which language, which entries were in Gurmukhi, which were in English, where the two overlapped and whether they agreed. That reading produced the specification for the job, and it produced one query worth raising with the client before starting.
We confirmed with the client which application the document was for, so that the work was done to Immigration New Zealand’s requirements rather than to a guess.
We told the client that notarisation was not required for this and recommended removing it. It is worth saying why we volunteer that rather than simply taking the order: a client who pays for a notarial layer they did not need, on a file that would have succeeded without it, does not come back. The advice costs us a line item and buys the relationship.
Then the translation. Every field on the certificate, in both languages, rendered into English: the pre-printed labels, the entries, the registering authority, the registration number, the registration date and the date of issue as separate facts, the signature block, and the seal. Where the Gurmukhi entry and the English entry for the same field differed, both were rendered and the difference flagged in a translator’s note rather than resolved silently.
On the name, the rule is the one we apply to every identity document: the spelling in the client’s passport governs in the body of the translation, with the Gurmukhi form shown as it appears. Punjabi names carry a further wrinkle, in that the components English readers treat as surnames do not always function that way in the source record, and older certificates sometimes have no surname field at all. Where the certificate’s structure does not match the structure of the name on the passport, we render the certificate as it is and let the passport spelling sit alongside it, rather than reorganising a person’s name to make two documents look tidier than they are.
Anything not legible in the photograph was marked as illegible. Dates were given with the month as a word.
The certification was issued in the form INZ expects: a signed statement that this is a true and complete translation of the document supplied, with the translator’s name, the date and contact details, and – because this is the part that matters on an immigration file – identifying the translator as independent of the applicant.
What we delivered
One certified English translation of the bilingual Punjabi birth certificate, covering every field in both languages, with the registering authority, registration number, registration date and date of issue rendered as distinct facts, any disagreement between the English and Gurmukhi layers flagged rather than smoothed over, the client’s name matched to the passport spelling with the Gurmukhi form shown, illegible elements marked, and a certification statement in the form Immigration New Zealand requires, from a translator independent of the applicant.
Delivered inside the deadline, prepared for the right agency, and with the notarisation the client had ticked removed from the order before it was charged for.
The result
The translation went into the residence file complete and on time, with nothing queried. The client’s file carried a document the case officer could read in full, in which the two language layers of the original were both visible and any difference between them was on the face of the translation rather than buried in it.
The decision on a residence application belongs to Immigration New Zealand, and this piece makes no claim about it. What we could control was that nothing in the translated paperwork gave anyone a reason to come back and ask.
What a reader in the same position should know
If your certificate already has English on it, send it to us anyway. Bilingual Indian certificates are the most common source of false confidence in this field. The English layer is often incomplete, and where it is complete it sometimes contradicts the Punjabi. An authority needs one complete English document, not a partly readable one.
Do not let a family member translate it, however good their English. Immigration New Zealand wants a translator who is independent of you, and a relative fails that test regardless of competence. This is the most frequent avoidable reason a translation is sent back.
Work out whether you are applying for residence or for citizenship, because they go to different agencies. If a form offers you both in one option, say which one you mean in the message box.
And do not buy notarisation unless someone has specifically asked you for it. For a certified translation of a civil-status document on an immigration file, it is normally unnecessary. Ask us first and we will tell you.
You can read about this work on our Punjabi to English translation, certified birth certificate translation and translations for Immigration New Zealand pages. If your application is for a visa rather than residence, our visa document translation page covers that, and if you are in fact applying for citizenship, see translating documents for a citizenship application. Our notarised translation page explains what notarisation actually does, and our translation FAQs answer the rest. When you are ready, order a certified translation.
Guides written and reviewed by our certified translators and editors — the team behind 25,000+ accepted translations for INZ, DIA, NZQA and NZ Courts since 2013.