A migration agent in Parramatta opens a rejection email at four o'clock on a Friday afternoon. The translation reads cleanly. The names match the passport. The dates line up. The mistake sits three lines from the bottom, where a small council stamp on the back of a Pakistani birth certificate was left untranslated. The whole partner visa file now waits another six weeks for a fresh submission. Stories like this play out every week across Sydney, Melbourne, and Brisbane. The reasons rarely change.
What counts as a migration translation mistake? Anything on the translated page that gives a Department of Home Affairs delegate a reason to set the file aside. That includes missing elements, formatting choices that break the parallel layout, credential gaps, and inconsistent handling of names, dates, or stamps. The bar sits lower than most applicants expect.
Where the mistakes cluster
| Category | Share of our reject pile | Typical authority response |
|---|---|---|
| Formatting and layout | About 28 percent | Request for resubmission |
| Certifier credentials | About 22 percent | Outright rejection |
| Source document handling | About 19 percent | Request for original |
| Name and date handling | About 18 percent | Request for further information |
| Stamp and seal handling | About 13 percent | Request for revised translation |
The ten mistakes that derail migration files
01. Translating a photocopy instead of the certified original
Applicants often scan a faded photocopy and send that across. The translator works from what they receive, so the translated page carries every blur and missing edge of the source. Home Affairs delegates want to see the translation matched to a clear certified copy or the original itself. Send a high resolution scan of the issued document, not a scan of a scan.
02. Leaving the issuing authority stamp untranslated
Every official stamp on the source must appear in the translated page, either in a bracketed transcription or as a labelled translation block. Skipping a council stamp, a registrar's mark, or a Ministry of Foreign Affairs verification is the single most common reason a migration translation comes back. The fix is small but rigid. If you want a translator who handles the stamp panel correctly, our naati translation services page sets out the standard format we use for migration files.
03. Latinising names without matching the passport spelling
A Vietnamese applicant whose birth certificate reads Nguyễn Thị Hồng Vân might appear in the passport as Van Thi Hong Nguyen. The translation must mirror the passport spelling and order, with the source script preserved alongside. A mismatch between the translated name and the biodata page triggers an immediate request for further information.
04. Converting dates to Australian format without flagging the original
A date written 05/04/1992 in a European source might mean the fifth of April. The same digits on an American source mean the fourth of May. Quietly converting to the Australian DDMMYYYY layout without showing the original arrangement leaves the delegate guessing. Show both, label the source format, and let the reviewer confirm.
05. Skipping the back of the document
Police certificates from Pakistan, India, the Philippines, and Vietnam often carry verification stamps, watermarks, or registrar signatures on the reverse. Many applicants send only the front page to the translator. The translated file then arrives at Home Affairs missing half the source content, and the delegate cannot verify the document as complete. Our passport and identity document translation page explains the dual side workflow we run for every migration submission.
06. Using a translator without a current NAATI certification number
A lapsed credential is treated the same as no credential. Home Affairs checks the practitioner number against the live NAATI directory during processing. If the number does not return an active result, the translation is set aside. Always confirm the certification cycle before you commission the work.
07. Missing the statement of accuracy block
A migration translation needs a signed declaration from the translator confirming accuracy, the language pair, the direction of translation, the practitioner number, and the date. A page without this block reads as a working draft, not a certified document. The full requirements for the statement and stamp panel sit on the NAATI certification page, which sets out the credential framework Australian authorities check against.
08. Mishandling religious or calendar dates
Afghan tazkiras carry Hijri dates. Nepali birth certificates run on the Vikram Samvat calendar. Thai documents use the Buddhist Era. A translator who converts these to Gregorian without showing the original calendar leaves the source unverifiable. Show the original, show the Gregorian equivalent, and label both clearly. A simple bracketed conversion saves the file.
09. Loose handling of parents' names on birth certificates
Birth certificates often list parents under different transliterations than the ones used in passports or marriage records. The translator who reconciles these without flagging the variation creates a paper trail that does not match across the file. The cleanest fix is to translate exactly what the source shows and add a translator's note when a spelling variation appears. Our piece on why Australia's translation rules stay stricter than Europe's sets out why Australian delegates inspect these details more closely than many European authorities.
10. Submitting an AI assisted translation to Home Affairs
Machine output looks fluent and lands on the desk as a finished page. It carries no NAATI credential, no signed statement, and no accountable practitioner. Home Affairs guidance on translated documents sits on the Department of Home Affairs translation requirements page, which is the source delegates work from. A file built on machine output rarely survives a first read.
What each mistake actually costs
| Mistake | What the applicant loses | Typical rework path |
|---|---|---|
| Photocopy source | Two to four weeks | Resubmit with original |
| Untranslated stamp | Three to six weeks | Fresh translation of full page |
| Name mismatch | Four to eight weeks | Request for further information cycle |
| Lapsed NAATI number | Six weeks or more | Full retranslation by current practitioner |
| Missing statement of accuracy | Two to three weeks | Reissued certification panel |
| Machine generated output | Risk of refusal | Full retranslation, possible appeal |
A small share of these files end in refusal rather than a request for more information. Most cycle back through requests for documents, which still cost the applicant six to ten weeks at the worst point of a visa timeline. Public Department of Home Affairs reporting on processing times shows that document related requests are a leading cause of file pauses across partner, parent, and skilled visa streams.
What a clean migration file looks like
A delegate opening a clean file sees the translated page laid out in parallel to the source. Every stamp, seal, signature, and handwritten note appears either transcribed or labelled. Names match the passport. Dates show both calendars when relevant. The statement of accuracy sits at the foot of the page with a current NAATI number, the practitioner's signature, the language pair, and the date of certification. Both sides of the source are present. Nothing on the page invites a second question.
Quick answers
Can I translate my own migration documents?
No. Australian authorities require a translation prepared by a NAATI certified practitioner. A self translation, even from a fluent bilingual applicant, will not satisfy the credential requirement.
Does Home Affairs accept translations done overseas?
Overseas translations are accepted only when the translator is approved for the relevant language in their country and the translation carries the translator's full credentials, contact details, and certification. NAATI work prepared inside Australia is the safer route for most migration files.
What happens if the translator's NAATI number has lapsed?
The translation is treated as uncertified. Home Affairs checks the practitioner number against the live NAATI directory, and a lapsed result returns the file for a fresh translation by a currently certified practitioner.
Do I need to translate the stamp on the back?
Yes. Every stamp, seal, signature, and handwritten note on either side of the source must appear in the translated page. Missing a back of page stamp is the single most common reason a migration translation file comes back from Home Affairs.
Lodge the file with the right translation the first time
A migration translation that survives a first read shows the source completely, mirrors the passport on names, handles calendars cleanly, and carries a current NAATI credential at the foot of the page. Upload your source documents through the AcudocX platform to commission a translation prepared in line with Department of Home Affairs requirements, at fixed pricing of $44.95 for a Self Service Extract Translation, $59.95 for an Extract Translation, and $79.95 for a Full Translation.
This article was prepared by a NAATI certified translator working with our team, based on experience handling certified translations for official use in Australia.