Farsi (Persian) Legal Translation in Dubai
Persian is the language of one of Dubai's oldest trading communities, and Farsi documents arrive here carrying a legal system, a calendar and a notarial tradition of their own. This page explains how Iranian commercial records, civil-registry booklets and registered deeds become usable before UAE authorities — and why the paperwork route for an Iranian document starts in Tehran, not in Dubai.
- Farsi to Arabic and Farsi to English for UAE authorities
- Shenasnameh booklets treated as full civil records, not single certificates
- Solar Hijri dates converted and checked against the Gregorian calendar
- Trade paperwork aligned with the Iranian legalisation chain
- Dubai-based, UAE-wide service
- Arabic & English
- Clear guidance on every document
- Direct request, no middlemen
A trade corridor that runs on paper
The commercial relationship between Iran and the UAE is one of the largest in the region. Figures published by the Iranian customs administration and carried in Iranian media describe non-oil trade measured in billions of dollars in each direction, with the UAE ranking among Iran's top trading partners for both imports and exports. Behind every consignment in that flow sits a file of paper: invoices, packing lists, certificates of origin, corporate registrations and powers of attorney — much of it written in Persian, dated in a calendar most UAE officials do not read, and stamped by authorities whose seals mean nothing here until a chain of certifications explains them.
The community behind that trade is long established. The Iranian Business Council in Dubai, an Iranian business body active in the emirate for more than three decades, describes its purpose as building commercial networks between Iranian businesspeople and promoting trade and economic ties across the UAE. Families, holding structures and trading houses in this community accumulate documents on both sides of the Gulf — an Iranian marriage record here, a Dubai licence there — and sooner or later those documents have to cross, in one direction or the other, through translation.
What makes Persian legal work genuinely different is not vocabulary. It is that Iranian documents come out of institutions with no exact UAE counterpart: notarial registry offices that register deeds rather than merely witnessing signatures, a civil-status booklet that follows a person through life rather than a stack of separate certificates, an Official Gazette that publishes corporate facts, and a calendar whose year begins at the March equinox. A translator who renders the words but misses the institutions produces a text that reads fluently and misleads quietly.
On this page we separate three things carefully: general background about how Iranian documents work, official requirements published by named authorities in Iran, the UAE and elsewhere, and our own working method at MANJAZ. Where a rule comes from an authority we say which one. Where practice varies or nothing official has been published, we say that too — because on this route, the honest answer is sometimes the only accurate one.
The route an Iranian document travels
Official translation inside Iran
A motarjem-e rasmi — an official translator licensed by the Iranian Judiciary — translates the document, commonly into English for international use. This happens first, inside Iran, because the translator's seal is the thing the next authority certifies.
Iranian Ministry of Justice
The Iranian Ministry of Justice legalises the official translator's seal and signature, confirming the translation was produced by a translator on the Judiciary's register.
Iranian Ministry of Foreign Affairs
The Iranian Ministry of Foreign Affairs adds its own stamp over the Ministry of Justice legalisation. Foreign embassies in Tehran only recognise documents that carry this stamp.
UAE Embassy in Tehran
Because neither Iran nor the UAE is a party to the Hague Apostille Convention, the document needs consular legalisation by the UAE mission in Iran. Each authority in the chain certifies only the seal of the one before it, which is why the order cannot be rearranged.
MOFA attestation in the UAE
The UAE Ministry of Foreign Affairs attests the embassy stamp. MOFA's published rules: the document must be original, must not be laminated, and must be in Arabic or English or accompanied by a legally certified translation. The attestation certifies signatures and seals — never the content.
Arabic legal translation in the UAE
For mainland courts, notaries and most government filings, an Arabic version is produced against the fully stamped document by a legal translator approved by the UAE Ministry of Justice. The official UAE portal states that court documents must be in Arabic or translated by such a translator.
Why the Iranian route translates before it legalises
Most European documents travel the other way round: the original is legalised first, and a translation is attached later, wherever the document lands. The Iranian system reverses this. Government guidance published by the Netherlands for documents from Iran states it plainly: documents in Persian must be translated into English in Iran by a sworn translator, then approved by the Iranian Ministry of Justice, then the Iranian Ministry of Foreign Affairs, then the destination embassy in Tehran. The Belgian Embassy in Tehran publishes the same fixed order.
The same guidance goes further: even a document that was not issued by Iran but is held by an Iranian family — a foreign birth certificate, for example — is expected to be translated and legalised in Iran. The logic is structural. The Iranian Ministry of Justice legalises the seal of a Judiciary-licensed translator; a translation made anywhere else carries no seal that ministry recognises, so it simply has nothing to stamp.
For anyone planning a Dubai filing, this has two practical consequences. First, if your original is still in Iran, the translation step belongs there, inside the chain — flying the document out untranslated usually means flying it back. Second, the English produced in Tehran is rarely the end of the story: once the document reaches the UAE and clears MOFA attestation, mainland courts and notaries still work in Arabic, and that Arabic version is produced here, against the fully stamped file.
Want this checked for your own document?
The Iranian instruments, called by their names
- Shenasnameh (شناسنامه)
- The booklet-format identity and birth record issued by Iran's National Organization for Civil Registration. It records marriage, divorce, children and death across its pages — a life record, not a single certificate.
- Karte melli (کارت ملی)
- The Iranian national identity card. It does not replace the shenasnameh; UAE-bound files routinely need both, and the national ID number links the two.
- Daftar-e asnad-e rasmi (دفتر اسناد رسمی)
- The official notarial registry office where property deeds, powers of attorney and contracts are registered. Registration is what gives the deed its official character.
- Sardaftar (سردفتر)
- The head notary who runs a notarial registry office. The signature and seal behind a registered Iranian deed are ultimately the sardaftar's.
- Sanad-e rasmi (سند رسمی)
- A deed registered at a notarial registry office, carrying stronger evidential weight than an unregistered private paper, the sanad-e adi. A translation that flattens both into "document" erases a distinction Iranian law considers decisive.
- Vekalat-nameh (وکالتنامه)
- A power of attorney, typically executed and registered at a daftar-e asnad-e rasmi. UAE notaries and registries read powers narrowly, so the scope clauses must be rendered word by word, not summarised.
- Sanad-e ezdevaj / aghd-nameh (سند ازدواج / عقدنامه)
- The Iranian marriage document. Its mahriyeh clause — the dower — is a substantive financial term that must be translated precisely, because it can be litigated.
- Talaq-nameh (طلاقنامه)
- The Iranian divorce document, read together with the divorce entry in the shenasnameh. Personal-status files usually need both to tell one consistent story.
- Rooznameh-ye rasmi (روزنامه رسمی)
- The Official Gazette of Iran, where company registrations and amendments are published. A gazette notice is frequently the underlying evidence behind an Iranian corporate document — including who may sign.
- Motarjem-e rasmi (مترجم رسمی)
- An official translator licensed by the Judiciary of Iran. Their seal is what the Iranian Ministry of Justice legalises — the anchor of the whole outbound chain.
Reading a shenasnameh as a record, not a certificate
Documentation published by the Immigration and Refugee Board of Canada describes the shenasnameh in detail: it is issued by Iran's National Organization for Civil Registration, under the Ministry of Interior, and it contains the holder's name, parents' details and birth information — but also marital status, with dedicated pages for recording marriage, divorce and death. Children are listed by national identity code rather than by name. The newer, passport-like format adds watermarked paper, printed photographs, national ID numbers, barcodes and punched security codes; older booklets remain valid indefinitely, with replacement encouraged rather than mandated.
Every one of those design facts becomes a translation decision. Because the booklet records events over a lifetime, the receiving authority usually needs the entries — the marriage on one page, the divorce annotation, the children's ID codes — not just the bio page. Because children appear as codes, the translation must reproduce those codes exactly and resist the temptation to substitute names from other documents. Because old and new formats circulate side by side, the translation should identify which format it is working from. And because the booklet has no expiry, the version of events it shows is only as current as its last entry — which is precisely what an immigration officer or a court is checking.
Our own practice at MANJAZ is therefore to quote and translate the booklet as a booklet: every written page, every marginal entry, and a note where entry pages are blank, so the Arabic or English reader can see not only what the record says but what it does not. A first-page-only translation looks cheaper until the file bounces and the legalisation clock restarts.
Solar Hijri dates: why the offset is not fixed
Iran's official calendar is the Solar Hijri calendar. Its year begins at the March equinox, determined astronomically for the Tehran meridian — which means the boundary between one year and the next is set by observation, not by a fixed formula. Converting a Solar Hijri year to a Gregorian one requires adding either six hundred twenty-one or six hundred twenty-two, depending on whether the Iranian year in question had already begun at the date concerned. Leap years likewise follow the equinox, not an arithmetic cycle.
The practical consequence: any single Solar Hijri year straddles two Gregorian years, roughly March to March. The year 1398, to take a common example from marriage documents, began in March of 2019 and ended in March of 2020 — so a date written as 1398 cannot be converted honestly without reading the month and day beside it. A converter that applies one fixed offset to everything will be right for part of the year and quietly wrong for the rest.
A second trap sits beside the first. The Gulf uses the lunar Hijri calendar for Islamic dates, and the two systems share the word Hijri while producing completely different Gregorian results. An Iranian civil date is solar; treating it as lunar shifts a document by decades. When we prepare a Farsi file, dates are converted entry by entry, cross-checked for internal logic — a birth in Esfand falls in late winter, a contract signed in Tir belongs to summer — and, where it helps the receiving authority, shown in both calendars so the reviewer never has to trust our arithmetic blind.
The twelve Solar Hijri months
| Month | Persian script | Days | Position in the year |
|---|---|---|---|
| Farvardin | فروردین | Thirty-one | First month; begins at the March equinox (Nowruz) |
| Ordibehesht | اردیبهشت | Thirty-one | Second month, mid-spring |
| Khordad | خرداد | Thirty-one | Third month, late spring |
| Tir | تیر | Thirty-one | Fourth month, early summer |
| Mordad | مرداد | Thirty-one | Fifth month, midsummer |
| Shahrivar | شهریور | Thirty-one | Sixth month, late summer |
| Mehr | مهر | Thirty | Seventh month, start of autumn |
| Aban | آبان | Thirty | Eighth month, mid-autumn |
| Azar | آذر | Thirty | Ninth month, late autumn |
| Dey | دی | Thirty | Tenth month, start of winter |
| Bahman | بهمن | Thirty | Eleventh month, midwinter |
| Esfand | اسفند | Twenty-nine; thirty in leap years | Twelfth month; the leap day follows the equinox observation |
Working to a Dubai deadline while the original is still in Tehran? Send us photos of every page and we will map the route before you commit to anything.
Start your requestCommercial paper on the Iran-UAE corridor
Trade files have their own geography inside the UAE system. Commercial invoices and certificates of origin are not attested through the ordinary MOFA route at all: the ministry processes them through eDAS, a separate electronic attestation system that companies access with their trade licence and UAE Pass. Corporate instruments — registration records, articles of association, board authorities — travel the classic chain instead, and for an Iranian company that means the full Tehran sequence before the file ever reaches a UAE counter.
Iranian corporate files carry a peculiarity worth planning for: the Official Gazette. Company formation, changes of directors and changes of signing authority in Iran are published in the rooznameh-ye rasmi, and the gazette notice is frequently the document a bank or licensing officer actually needs in order to see who may bind the company. A registration certificate without its gazette notices is often half a file. We translate the notices together with the corporate documents they support, keeping company names, registration numbers and signatory titles consistent across every page — because a reviewer who sees three renderings of one company name reads them as three companies.
Language gates matter early in commercial work. MOFA's published requirement is that a document issued outside the UAE be in Arabic or English, or accompanied by a legally certified translation — so a Farsi-only instrument needs its certified translation before it can even enter the attestation stage, which in the Iranian pattern is exactly what the Tehran chain produces. Then, at the far end, the destination decides the final language: the official UAE portal states that documents before the courts must be in Arabic or translated into Arabic by a legal translator approved by the Ministry of Justice. Between those two fixed points, nothing in the chain ever checks translation accuracy: every stamp certifies a signature or a seal, and the words remain the translator's responsibility alone.
One more UAE-side fact protects trade files from a common false economy: according to MOFA, an attestation does not expire. The underlying document may still age out — a receiving authority can insist on a recent gazette notice or a current registration — but the stamps themselves do not lapse. Building a small library of attested, translated corporate documents is therefore a rational investment for an Iranian trading house that files in the UAE repeatedly, rather than rebuilding the chain for every transaction.
Have a question about your case?
Files we see on this route
An Iranian trading company is opening a presence in Dubai
What is usually neededRegistration documents, articles and the supporting Official Gazette notices translated inside Iran by a Judiciary-licensed translator, legalised by the Iranian Ministry of Justice and Ministry of Foreign Affairs, then the UAE Embassy in Tehran, then MOFA attestation in the UAE — and finally an Arabic version for the licensing authority, produced against the fully stamped file.
A family residency file rests on a shenasnameh and a marriage document
What is usually neededThe whole booklet translated — entries included — with the aghd-nameh and its mahriyeh clause rendered precisely, Solar Hijri dates converted with the equinox rule, and every name transliterated to match the passport. The official UAE portal requires foreign personal documents to be attested and translated into Arabic by an authorised translator, with the translation certified.
A vekalat-nameh from a daftarkhaneh must act in Dubai
What is usually neededThe registered deed goes through the full Tehran chain, then UAE-side attestation, then Arabic translation. The scope-of-authority clauses are the heart of the work: UAE notaries and registries read powers narrowly, so what the sardaftar recorded must appear in Arabic exactly — neither widened nor summarised.
An Iranian court judgment is needed as evidence in a UAE dispute
What is usually neededThe judgment and its enforcement papers follow the legalisation chain, and the target language follows the forum: Arabic for onshore courts, per the official portal rule, or English where the matter sits in the DIFC. Party names, case numbers and Solar Hijri hearing dates must line up with the rest of the evidence bundle.
An importer needs Iranian-origin paperwork to clear and to reconcile
What is usually neededInvoices and certificates of origin route through eDAS on the UAE side, while supporting Farsi documents — contracts, packing lists, bank confirmations — are translated so the whole file tells one consistent story to customs, banks and auditors, with amounts, dates and party names matching across languages.
Where Iranian files go wrong
The mistakeConverting Solar Hijri years with one fixed offset applied to every date.
The fixRead the month and day first. The Iranian year begins at the March equinox, so the correct offset depends on whether that year had begun — convert entry by entry and sanity-check each result.
The mistakeTreating a Solar Hijri date as a lunar Hijri date because both say Hijri.
The fixIranian civil dates are solar; Gulf Islamic dates are lunar. The two systems drift apart by decades over a lifetime, so the calendar must be identified before anything is converted.
The mistakeTranslating only the bio page of a shenasnameh to save cost.
The fixThe booklet records marriage, divorce, children and death, and those entries are usually what the authority is checking. Translate the record, not the cover.
The mistakeCommissioning a translation of an Iranian original outside Iran, then looking for someone to legalise it.
The fixThe chain expects the translation inside Iran, by a Judiciary-licensed translator, before the ministries stamp. A translation made outside that chain carries no seal the Iranian authorities will certify.
The mistakeUnstapling, unsealing or rescanning a legalised package to tidy it up.
The fixLegalising authorities treat the bound, sealed set as one instrument. Keep it physically intact; if a working copy is needed, ask before anything is separated.
The mistakeLetting each document spell the family name its own way in Latin script.
The fixFix one spelling — the passport's — and hold every translation to it: shenasnameh, marriage document, corporate papers, visa records. Transliteration drift reads as an identity mismatch.
The mistakeLaminating a certificate to protect it before attestation.
The fixMOFA states laminated documents cannot be attested and will be rejected — the stamps need the paper. Protect originals in a sleeve, never under heat-sealed plastic.
Destination decides the language
Dubai Courts and mainland authorities
- Proceedings run in Arabic; the official portal requires court documents in Arabic or translated by a legal translator approved by the Ministry of Justice.
- Notary work — powers of attorney, declarations, company memoranda — is executed in Arabic before court or licensed notary offices.
- Personal-status files need the foreign document attested and its Arabic translation certified, per the official portal.
- For an Iranian file this means the Tehran English translation is a bridge, and the Arabic produced in the UAE is the operative text.
DIFC
- An English-language common-law jurisdiction: the DIFC Courts' rules state that proceedings are conducted in English and filings are made in English.
- A Farsi contract or judgment for a DIFC matter therefore needs certified English, not Arabic — confirm with the registry before commissioning.
- The exception folds back: a DIFC judgment served elsewhere in the UAE needs an Arabic translation lodged within a two-day window under the courts' rules, and the English text prevails if versions conflict.
- Ask where the document is going before asking what language it is in — the answer sets the whole workflow.
One question on this route has no cleanly published answer: whether a given UAE authority will work from the English translation legalised in Tehran, or will require a fresh Arabic translation produced in the UAE — or both. MOFA's attestation rules accept a document in Arabic or English or with a legally certified translation, while the court rule requires Arabic by a translator approved by the Ministry of Justice; how the two interact for any specific counter is not published anywhere official we can cite. Our practice is to treat the Tehran English as the entry ticket and to confirm the final-language requirement with the receiving authority before commissioning the Arabic.
Practice also differs between emirates. Abu Dhabi's judicial authorities issued a circular exempting bank statements and invoices that consist solely of numerical data from mandatory certified Arabic translation in Abu Dhabi courts; no equivalent has been published for the other emirates, so nothing on this page should be read as if that relaxation travels. None of this is legal advice — it is the map as officially published, with the blank spots marked honestly. Always confirm with the authority that will receive your file.
Directions we work in
- Persian → ArabicMainland courts, notary work and personal-status files — the operative language of onshore UAE.
- Persian → EnglishDIFC matters, banks, auditors and internal review — where the forum works in English.
- Arabic → PersianUAE judgments, notices and contracts heading to Iranian counterparties and authorities.
- English → PersianAgreements and correspondence prepared in Dubai for review by a Tehran head office.
What to send us for a Farsi file
- Every page of the shenasnameh, including entry pages — even the blank ones, so the record is complete.
- The passport photo page of every person named, so transliteration is fixed to one spelling.
- The stamped package exactly as it came back from the last authority — bound, sealed and unopened.
- The name of the receiving authority and the emirate or jurisdiction, so the target language is right first time.
- For corporate files: the Official Gazette notices alongside the registration documents they support.
- For a vekalat-nameh: the full scope clause as registered, never a summary of it.
- Both dates where the document shows them — Solar Hijri and Gregorian — so conversions can be verified rather than assumed.
- Any earlier translations of the same documents, so wording stays consistent across your history with each authority.
Every stamp in the chain certifies a signature. Not one of them certifies a word. The words are the translator's alone — which is why the translator is the one choice you actually control.
Not sure which route applies to your document?
Persian legal translation: questions we actually get
Plan for the whole booklet. The shenasnameh records marriage, divorce, children and death on its inner pages, and those entries are usually the very thing a residency officer or court wants to see. A translation that stops at the bio page invites a request for the rest — after the file has already been queued. Where entry pages are blank, the translation should say so, because the absence of an entry is itself information.
It is the correct beginning, not the end. Those stamps carry the document through the UAE Embassy in Tehran and MOFA attestation here, because MOFA accepts documents in Arabic or English or with a legally certified translation. But the official portal requires Arabic for court documents, produced by a legal translator approved by the Ministry of Justice — so for mainland courts, notaries and most government filings an Arabic version is still produced in the UAE, against your fully stamped file. Whether a specific authority will also work directly from the Tehran English is exactly the point we recommend confirming with that authority first.
On its own, 1398 spans two Gregorian years: it began at the March equinox of 2019 and ended in March of 2020. The only honest conversion reads the Solar Hijri month and day beside the year — a date in Farvardin 1398 falls in spring of 2019, while a date in Esfand 1398 falls at the end of winter heading into 2020. This is why we convert date by date rather than applying a single offset to the whole document.
Usually because somewhere along the line a Solar Hijri date was converted carelessly — with a fixed offset, or as if it were a lunar date. The discrepancy then propagates: the passport shows one Gregorian birthday, the translated shenasnameh another, and the mismatch surfaces at the worst moment, inside a government system. The repair is to reconvert from the original Persian entries using the equinox rule and align every document to the passport, flagging any residual difference openly rather than hoping no one notices.
We plan each file around the certified version the receiving authority needs, and we tell you before work starts how your document will be handled and which translator will certify it. What matters legally is that the certifying translator holds the right language authorisation for the pair being certified — a point worth asking any provider, because a licence in the UAE is scoped to named languages rather than covering all of them by default.
The UAE Ministry of Justice registers legal translators by language, and its own services directory includes a separate request to add a language to an existing registration. The licence is therefore scoped: an authorisation for one pair does not extend to another. When Farsi is the source language, ask specifically which language authorisation the certifying translator holds — it is a fair question and a professional provider will answer it plainly.
Yes — a vekalat-nameh registered at a daftar-e asnad-e rasmi is one of the most consequential documents on this route. It needs the full Tehran chain first, then UAE-side attestation, then translation into the language the receiving authority requires. The craft is in the scope clauses: what the sardaftar registered must appear in the target language exactly, because a UAE notary or registry will act on the words in front of it and nothing else. We also match the principal's and attorney's names to their passports, so the power is exercised by the same person on paper as in the system.
No — and you could not get one if you tried. Iran is not a party to the Hague Apostille Convention, and neither is the UAE, so no Iranian office issues apostilles and no UAE office treats one as sufficient. The route is consular legalisation: the Judiciary-licensed translation and ministry stamps in Iran, the UAE Embassy in Tehran, and MOFA attestation in the UAE. Treat any offer of an Iranian apostille as a description of that chain under the wrong name — or as a reason to ask more questions.
We will not quote a number, because no honest one exists without seeing where your document stands. The chain crosses several authorities in two countries, the Iranian steps happen in Iran on Iranian schedules, and no one in Dubai can compress them. What we can do is map your specific document against the sequence, tell you which steps remain, and make sure nothing is done out of order — because the expensive delays on this route come from redone steps, not slow ones. If a deadline exists, start the chain before anything else in your plan.
It can. Persian names take several defensible Latin spellings, and UAE systems compare records literally: MOFA lists mismatched application data among its rejection grounds, and immigration or court records that disagree with the passport invite scrutiny at best. The remedy is procedural, not linguistic — pick the passport spelling as the single standard, hold every translation to it, and where an old document already circulates with a different spelling, have the translation note the equivalence explicitly so the reviewer sees one person, not two.
Yes — bank statements, financial statements and audit reports are regular parts of Iran-UAE corporate files, for licensing, banking relationships and disputes. Two notes from the official record: figures alone do not always exempt a document from translation, and the one published relaxation — Abu Dhabi's treatment of purely numerical bank statements in its courts — applies in Abu Dhabi, not everywhere. So the language plan for financial evidence follows the emirate and the forum, and we confirm it before starting rather than assuming.
Farsi and Persian are the same language; Farsi is simply its native name as used in Iran. Dari is the variety used in Afghanistan, and Tajik is written in Cyrillic. They share a script and most vocabulary, but official terminology, calendar and date formats and document layouts differ, so the translator should know which country issued the document. Tell us its origin when you send it.
Official references
- HCCH — Status table of the Apostille Convention
- UAE Ministry of Foreign Affairs — Attestation of Official Documents
- UAE Government Portal — Civil cases (court language rule)
- Government of the Netherlands — Legalisation of documents from Iran
- Embassy of Belgium in Tehran — Legalisation of documents
- UAE Ministry of Justice — Translators services directory
This page is general information about translation services, not legal advice. Requirements are set by the authority receiving your document and can change — always confirm with the receiving authority or ask us to check for your specific case.
Ready to translate your document?
Send the document and we confirm the exact certification the receiving authority expects.


