One Page, Two Words, and an Employment Pass File That Could Not Be Queried
Published on October 20, 2026
Case study – certified and notarised Malay to English translation of a Malaysian death certificate, ordered for an Employment Pass application. Details anonymised; the client is referred to by first name only, and nothing identifying the person named on the certificate appears anywhere in this account.
Noor’s enquiry reached us early on a Wednesday morning, and it was about as short as an enquiry gets. One page. Malay into English. Certified translation, with notarisation ticked. In the box where the form invites a customer to explain what they need, she had written two words: Death certificate. In the box asking what the translation is for, she had chosen Employment Pass application.
That is the whole brief. A single-page Malaysian death certificate, in Malay, that had to come out in English and go into an immigration file. There was a phone scan attached, made that morning – the file name still carried the scanner app and the date. Nothing else: no covering note, no checklist, no explanation of how a civil-registration document had come to sit inside an employment application.
We did not ask. A death certificate is never the customer’s own document, and the reason a family needs one translated is rarely a conversation a translation company has any business opening. What we needed from Noor was narrower and more useful: who was going to read this, in what pack, alongside which other documents, and under what name spellings. Everything that made this job interesting came out of those four questions.
A short brief is not a simple job
Short briefs are the ones we slow down for. When a customer writes three paragraphs about their situation, the risk is reading too much into it. When a customer writes two words, the risk is the opposite: assuming the obvious reading is the right one and producing a technically perfect translation that is wrong for the file it is going into.
Here is what the two words did not tell us. A Malaysian death certificate – the sijil kematian issued through the national registration system – is not one document. Depending on when and where it was registered, it can be a modern computer-printed certificate with a serial number and a bilingual header, an older typed register extract, or a form with handwritten entries, district stamps and an officer’s signature running across the lower third. The fields are the same in substance but they are not in the same places, the Malay wording is not identical, and the older the certificate, the more of it is rubber stamps rather than print.
The two words also did not tell us what standard of certification the receiving side wanted. The form captured that as a contradiction, which is the single most common thing we fix before a job starts. The field that asks which authority’s certification standard applies had been set to Not Applicable. The notarisation box, immediately below it, was switched on. In plain terms: Noor wanted a notarised translation but had not named anyone who had asked her for one.
And the form’s own document-type dropdown had no option for what she was holding. She had selected Other – even though she had arrived at us from our death certificate translation services page and then gone to the quote form, where that document family simply was not on the list. We mention it because it is worth knowing as a reader: when an intake form makes you choose “Other”, write the document name in the message box, exactly as Noor did. Those two words were the only reason we knew what was in the PDF before we opened it.
The three things we had to get right
Once we had the scan open and Noor on a short call, the job resolved into three problems, none of them about vocabulary.
Malay names do not behave like the names an English form expects
This is the part that quietly sinks immigration files, and it has nothing to do with translation quality. Most Malaysian names in Malay civil records are patronymic: a given name, then bin or binti, then the father’s name. There is no surname in the sense an English-language form means by “family name” or “last name”. A certificate may also carry a name in a slightly different form from the one on a passport – a spelling variant, an extra given name, an initial, an older romanisation of the same Arabic-derived name.
When a document like this goes into a pack with a passport, an employment contract and other civil-registration papers, a reader who does not read Malay compares strings. If the certificate renders a name one way and the passport renders it another, the reader cannot tell whether they are looking at a variant spelling or at two different people – and the file comes back with a query. So before translating a single field, we asked Noor for the passport spelling of every name that appears in both places, and we matched the translation to the identity documents in the pack rather than inventing a tidy English version of a Malay name. Where a spelling genuinely differed on the certificate, we rendered it exactly as the certificate had it and flagged the variance in the translator’s note, which is the honest way round: a translator may not silently correct a source document, but we can tell the reader why two spellings describe one person.
The same discipline applies to place names, administrative districts, the registration district and the issuing office – these stay as proper nouns, not translated into approximations. It is the first thing we check on any Malay to English translation of a civil-registration document, and it matters just as much on a birth certificate translation or a marriage certificate translation that has to sit in the same file as this one.
A certificate is mostly not text
Open a Malaysian death certificate and count how much of the page is running prose. Very little. It is a grid of labelled fields, a serial number, one or more official stamps, an authorising signature, and sometimes a reverse-side endorsement. Some of those fields hold information that is nobody’s business outside the family, and we neither discuss nor characterise their contents here.
A complete certified translation has to account for every mark on the page, including the ones that are not words. Stamps get rendered as described elements – what they are, where they sit, whether they are legible. Signatures are described, never reproduced or “translated”. An illegible stamp is reported as illegible rather than guessed at. Blank fields are shown as blank, because a reader needs to know the field existed and was left empty, not have it quietly disappear. And the layout is kept recognisable, so the person checking the English can hold it beside the Malay original and find the same field in the same place.
Noor’s scan was a phone scan, which is normal and perfectly workable, but it had the usual phone-scan problems: one edge slightly cropped, a stamp partly washed out by the flash, and a fold line running through a field. We asked for one reshoot of the lower third in daylight rather than guessing at the stamp. That cost about twenty minutes and removed the only genuine ambiguity in the document.
Certified, notarised, or both – decided on evidence, not on a hunch
Back to the contradiction in the form. Noor had asked for notarisation without naming a body that required it, and the honest first move was to find out whether she needed it at all. Certified and notarised are not two grades of the same product; they answer different questions. A certified translation is the translator’s signed statement that the English is a complete and accurate rendering of the Malay. Notarisation adds a Commissioner for Oaths or Notary Public, who witnesses and endorses that statement – they do not re-check the language, and they are not vouching for the translation’s accuracy. We set this out in full in our guide to the difference between certified and notarised translation in Malaysia, and it is the single most useful thing a first-time applicant can read before ordering.
For submissions to Jabatan Imigresen Malaysia, a properly certified translation is generally what is accepted; notarisation is more usually asked for by courts, by some overseas legal and immigration proceedings, and in inheritance and probate matters. So we told Noor plainly that she might be buying a layer she did not need, and we asked her to check with whoever had given her the document list.
She came back and asked for it anyway. Her reasoning was sound and we agreed with it: the pack was being handled through an employer, she could not get a definitive answer on the certification standard that week, and a notarised translation satisfies a request for a certified one, while the reverse is not true. When a deadline is fixed and the requirement is vague, buying the stronger endorsement once is cheaper than discovering you need it later. That is the judgement call this job turned on, and it is worth remembering if you are ever in Noor’s position with a checklist you cannot verify.
How we ran it
- Resolved the brief. One call: who reads it, what else is in the pack, which name spellings govern, and whether anyone had actually asked for notarisation.
- Fixed the source. Requested one reshoot of the stamp area so nothing on the page had to be guessed at.
- Built a name and place key from the identity documents in the pack, so every proper noun in the English would match what the reader would see elsewhere in the file.
- Translated the full page into English by a Malay-language translator working in this document family – every field, every label, blanks shown as blanks, stamps and signatures described, layout mirrored.
- Independent check against the reshot original, field by field, with particular attention to dates, the serial number and the registration details, where a single transposed digit is the kind of error that gets a file returned.
- Issued the certificate of accuracy – translator’s statement, language pair, date, signature and company stamp – and attached a short translator’s note explaining the name-spelling variance in neutral terms.
- Took the certified set to a Commissioner for Oaths for endorsement, and delivered the notarised translation with the original scan attached, in the order a reader would want to leaf through it.
The whole thing moved inside the same working day, which is the normal shape of a one-page civil-registration job when the source is legible and the questions get answered early. The two places a job like this loses a day are both avoidable: an unreadable stamp nobody queried, and a certification standard nobody confirmed.
How it turned out
The translation went in complete and on time, inside the deadline Noor had, certified and notarised exactly as she had asked. The seals and the Commissioner’s endorsement were in place, the name spellings matched the identity documents in the pack, and the English page could be laid beside the Malay original and read field for field.
Nothing on the translation was queried. Noor confirmed the document had done its job in the file and that no one had come back asking for a different form of certification or a re-translation. The outcome of the Employment Pass application itself sits with the Immigration Department of Malaysia, as it always does, and is not ours to report – what we can say is that the translation was not the part anyone had to ask about, which on a document like this is exactly the point.
What this one taught us to say earlier
Two things from Noor’s job we now raise on the first call rather than the second.
The first is pack consistency. A certificate that is accurate in isolation can still break a file, because immigration readers compare documents against each other rather than against the original language. Any civil-registration document joining a pack needs its proper nouns reconciled with the identity documents already in it, and any genuine mismatch explained in the translator’s note instead of smoothed away. That is a translation-management problem as much as a language one, and it is why we ask what else is in the file before we start – the same reason it comes up constantly in legal translation work where several documents land on one desk together.
The second is that an unverifiable checklist is a legitimate reason to over-certify. We will always tell you when we think you are buying more than you need – but when the requirement cannot be confirmed before the deadline, the stronger endorsement is the cheaper mistake. Noor made that call herself, with the facts in front of her, and it was the right one.
If you are holding a Malay death certificate and a document list you cannot fully decode, send us the scan and tell us what the pack is for. Two words in the message box is enough to start – Noor’s were. You can upload your document for a certified translation quote and we will tell you which level of certification your submission actually calls for before you pay for one.
Related case studies
About Malaysia Translators
Malaysia Translators
