Client details are withheld; no name, number, date or place appears here. This account describes a scoping conversation. At the point it ends, nothing had been translated, notarised or submitted – the client was asking what the job would involve before sending the document, which is exactly the right order to do it in.
The enquiry that arrives at the end of a years-long process
Most translation enquiries arrive at the beginning of something. This one arrived at the end.
The message came in just after noon, Singapore time, through our ICA notarised translation page, and the first clause did the work of a paragraph: the client had just been granted Singapore citizenship, and had been asked to submit a Malay-language form obtained from the Malaysian mission in Singapore to ICA’s e-Service portal. Two pages. They wanted to know the cost, and whether notarisation and Singapore Academy of Law authentication were needed. And then the sentence that tells you who you are dealing with: once it is confirmed, I will send the document over.
No attachment of the form. A screenshot of a browser window, which is the sort of thing people send when they are trying to show you what they are looking at rather than what they are holding. And a question asked before buying anything.
We want to say something about that, because it is unfashionable advice in a business that profits from urgency. Asking first was the correct decision and it probably saved the client money. A great many people in this position buy the full stack – translation, notarisation, authentication – on the assumption that more layers mean more safety, and then discover that one of the layers does nothing for their particular submission. The client’s instinct to establish the requirement before committing is the instinct we would want every applicant to have.
What kind of document this is, and why that changes the question
The form in question belongs to a class that almost nothing else in our work resembles: a document a person obtains from the mission of the country they are leaving, to satisfy the country they are joining.
A first precision, since it recurs constantly and the client’s own message contained it. Malaysia’s mission in Singapore is a High Commission, not an embassy. Commonwealth countries exchange High Commissions with one another rather than embassies, and the head of mission is a High Commissioner. Nothing turns on it for the price of a translation, but it turns on quite a lot when a form, a portal field or a counter clerk asks you to name the issuing body – and getting it wrong in a submission is the sort of small wrongness that invites a second look at everything else.
A second precision, and this one we hold to firmly. The form code the client used is the designation they were given and the one used at the counter. We do not assert a statutory mapping for a form code we have not verified against a current published register. We learned that discipline the hard way on another Malaysian form earlier this month: a code that everyone in the market treats as official turned out not to appear in the issuing department’s current form list at all, and anyone who had written an authoritative-sounding sentence about it would have written a wrong one. So in our file note, and in this account, the code is recorded as the client’s designation. What matters for the translation is not the code. It is what the sheet actually says.
Which brings us to the real point. A renunciation-type instrument is not a civil-registry extract. A birth certificate records a fact that happened. An instrument of this kind is a declaration: a person stating something, in prescribed terms, with legal effect. And operative language has to survive translation intact.
Why a declaration is harder to translate than a certificate
Here is the difference, stated as plainly as we can.
When you translate a birth certificate, the question is whether you have reproduced the register faithfully. Every stamp, every endorsement, every marginal note, every field label. The reader is checking facts against other documents, and your job is fidelity.
When you translate a declaration, fidelity is necessary but not sufficient, because the document does not merely record something – it does something. It renounces, it declares, it undertakes. Malay legal drafting has its own register for that, and an English rendering that reads naturally can quietly demote a performative statement into a descriptive one. “I hereby renounce” and “this document is about renouncing” are not the same sentence, and only one of them is a translation.
So on a document of this class our practice is specific. The operative clauses are rendered with their force preserved and their structure visible – numbered where the original is numbered, in the original order, with no consolidation of clauses for readability. The prescribed wording stays prescribed-sounding. The declaration’s own apparatus – the attestation, the witness or officer block, the mission’s seal, the date panel, any reference number field, whether filled or blank – is accounted for in full, with seals and stamps described in bracketed translator’s notes giving their text and position. A blank field is translated as a blank field, labelled and empty. Quietly omitting an empty box is how a two-page form becomes a one-and-a-half-page form that no longer matches the original the officer is holding beside it.
And the names. Malaysian names carry patronymics – bin, binti, a/l, a/p – and Malay orthography has shifted across the decades, so a name can appear one way on a document issued years ago and differently on one issued last week. On a file where the whole point is that one legal identity is being reconciled with another, the names have to be fixed in writing before a word is translated, applied identically, and any divergence between source documents recorded in a note rather than silently harmonised. Silent harmonisation is the single most dangerous thing a translator can do to an immigration file, and it is most tempting precisely where it is most dangerous.
The answer to the question the client actually asked
Now the substance. The client asked whether they needed notarisation and SAL authentication. The honest answer has three parts, and the first part corrects something widely believed.
ICA does not require notarisation as a blanket rule. ICA asks for official translations of documents not in English, and its published guidance names the routes it accepts: a translation provided by the embassy or high commission of the issuing country or place; a translation produced by a notary public, in Singapore or in the issuing country or place; or a privately produced translation that is then verified – either attested by that embassy or high commission, or notarised by a notary public in Singapore or in the issuing country or place.
Read that list properly and the shape of it becomes clear. Notarisation is the verification step attaching to the third route. It is not a universal demand bolted onto every translation. Anyone who tells you ICA mandates notarisation and that a plain certified translation will be bounced is overstating it, and we are not willing to overstate it in order to sell a notarial act.
ICA also says, expressly, that it does not endorse any private translation company or entity. That sentence should end a certain kind of marketing claim permanently. No provider in Singapore – this one included – is ICA-approved, ICA-appointed or on an ICA list. There is no list.
What notarisation does add, where it is used, is worth being precise about. A notarial act confirms a signature, the signer’s authority and their capacity. It does not attest the accuracy of a translation. The Notary Public is not reading the Malay and is not checking whether a renunciation clause has been rendered with its force intact. The accuracy of the translation rests entirely on the translator’s own certificate of accuracy and the translator’s competence, which is exactly why the choice of translator matters more, not less, when a notarial layer is involved. Our comparison of certified versus notarised translation in Singapore sets the distinction out at length, and it is the single most useful thing a first-time applicant can read.
And SAL authentication: no, not for this submission. The Singapore Academy of Law authenticates the signatures of Notaries Public appointed in Singapore, and since 16 September 2021 it does so by affixing an apostille to the back of the notarial certificate. SAL does not review document content and does not assess translation quality. That layer exists for documents travelling out of Singapore to a foreign authority. A form being uploaded to a Singapore government portal, by a person living in Singapore, for a Singapore process, is not going anywhere. Adding an apostille to it buys nothing. Our SAL notarised translation page explains when that layer genuinely is the right one – and this was not one of those times.
So the answer we gave was: a certified translation to the proper standard is the floor; notarisation by a Singapore Notary Public is available and sits squarely inside what ICA says it accepts, if you want the verification layer; SAL authentication adds nothing here; and before you buy anything, check the portal’s own instruction for the specific item it is asking you to upload, because the authority’s own list governs and ours does not.
The one thing we could not answer, and said so
There is a limit to what anyone outside the process can tell you, and pretending otherwise is the industry’s besetting sin.
An e-Service portal asking for a particular document at a particular stage may carry its own instruction about the form in which it wants it: a scan or an original, a particular file format, a certified translation produced in a particular way, or a specific combination of the English and the Malay in one file. We cannot see the client’s portal screen, and the screenshot they sent showed a browser window rather than the instruction text.
So we asked for two things before quoting: the form itself, and the portal’s own wording for the item being requested. Not because we were being difficult, but because those two pieces of paper between them answer every remaining question, and guessing at either of them is how a client ends up paying for a layer they did not need or missing one they did.
We also told the client, in writing, that if the Malaysian High Commission itself can issue or endorse an English version of the form, that is one of ICA’s named routes and may be simpler and cheaper than anything we would do. We say that to clients fairly often and it costs us work. It is still the right thing to say, because a client who discovers later that the mission would have done it is a client who will remember who did not tell them.
What we actually did
- Read the purpose out of the client’s own words. The form fields said embassy certification and legal or court use. The client said citizenship, with a portal upload at the end of it. There is no court and no embassy step in this job; we noted the discrepancy so nobody downstream routed it to one.
- Named the issuing body correctly. A High Commission, not an embassy – and said so, because the submission will ask the client to name it.
- Declined to assert a statutory mapping for the form code. Recorded as the client’s designation pending verification against a current published register. The sheet governs, not the code.
- Classified the document by what it does, not what it is called. A declaration with operative effect, not a registry extract – which sets the whole translation approach.
- Answered the authentication question honestly, including the part against our own interest. ICA’s three routes stated accurately; notarisation offered and explained rather than asserted as mandatory; SAL ruled out for a domestic submission; the mission’s own English version raised as a possible cheaper route.
- Asked for the two documents that decide everything. The form itself, and the portal’s own wording for the item requested. Neither had been sent.
- Set out the names discipline before any work. Patronymics and orthography reconciled in writing across every document in the client’s set, divergences noted rather than harmonised.
- Quoted on scope rather than on hope. Two pages at the stated length, with the notarial layer priced separately and clearly marked optional, so the client could see exactly what each layer cost and decide for themselves.
- Explained the legibility check. Documents issued at a mission counter are often photographed rather than scanned; we check that every entry, seal and endorsement is readable before committing to a deadline. The reasoning is in our note on using a scanned copy for notarised translation.
- Left the decision with the client. No work was started at the scoping stage, and the file stayed open awaiting the form.
Where the file stood at scoping
This is a scoping story and we will not dress it as anything else. At the point the scoping conversation closed, nothing had been translated, nothing had been notarised, no apostille had been sought and nothing had been submitted to any portal. What the client had was an answer: what each layer does, which one their submission actually needs, which one it does not, what it would cost, and which two documents they needed to send for the quote to become final.
That is a smaller deliverable than a notarised bundle. On a day when somebody has just become a citizen and has one form standing between them and the end of a long process, it is also the thing they most needed.
Questions people ask at this exact point in the process
Does ICA require my translation to be notarised?
Not as a blanket rule, and anyone telling you otherwise is overstating it. ICA accepts a translation from the embassy or high commission of the issuing country; a translation by a notary public, in Singapore or in the issuing country; or a private translation subsequently attested by that mission or notarised by a notary public. Notarisation is the verification step on that third route. Check the instruction attached to the specific item you are being asked to upload.
Is any translation company ICA-approved?
No. ICA states expressly that it does not endorse any private translation company or entity. If a provider claims to be ICA-approved or on an ICA panel, that claim is not true of anybody.
Do I need SAL authentication or an apostille on top?
Not for something you are uploading to a Singapore government portal. SAL authenticates the signatures of Singapore Notaries Public, by apostille affixed to the back of the notarial certificate, and that step exists for documents being sent to a foreign authority. It adds nothing to a domestic submission.
Could the High Commission translate it for me instead?
Possibly, and it is worth asking before you pay anyone else. A translation provided by the mission of the issuing country is one of the routes ICA names. If the mission will issue or endorse an English version, that may be both simpler and cheaper.
Why do you need the portal’s wording as well as the document?
Because the portal’s instruction decides the form of what you submit – scan or original, file format, how the translation must be produced, whether the English and the source language travel as one file. We can translate without it. We cannot tell you that what we produce is what the portal wants without it.
I have been granted citizenship already. Why is translation still coming up?
Because the steps that follow an approval have their own documentary requirements, and those documents frequently come from the country a person is leaving rather than the one they are joining – in a language the receiving portal does not read. It is a stage people rarely budget for, which is why the question usually arrives, as this one did, at the very end.
Can a blank field just be left out of the translation?
No. A blank field is translated as a labelled, empty field. Omitting it makes the English page a different shape from the original, and an officer comparing the two will notice the discrepancy before they notice anything else.
Will the Notary Public check my Malay has been translated correctly?
No. This is the most persistent misunderstanding in the field. The Notary confirms a signature, the signer’s authority and their capacity. Translation accuracy is certified by the translator, in the translator’s own certificate of accuracy. Choose your translator on that basis.
If you are at the same stage
Send the form and the portal’s own wording for what it is asking you to upload, and say in your own words what stage you are at. Those three things together let us tell you not only the price but whether you need the layers you were about to buy.
Our immigration documents notarised translation page covers how a mixed set of civil, declaratory and supporting papers is assembled into one bundle, and our legal affidavits and declarations page covers documents whose language is operative rather than descriptive – the class this form belongs to. If your set also includes civil-registry records, start at birth certificate notarised translation. If you are earlier in the journey than this client, our note on notarised translation for a Singapore PR application is the right starting point. Our FAQs answer most of the certification questions people arrive with. When you are ready, upload through our hire translators page – and ask the question before you buy the layer. This client did, and it was the right call.
