Certified Translation of IP Documents for Nepal: A Workflow That Survives the DOI
IP documents filed in Nepal must be in Nepali. A practical certified translation workflow for foreign applications, POAs and corporate papers at the DOI.
The Department of Industry examines applications filed in Nepali. Every foreign document in the set — the Power of Attorney, the home-country registration, the priority paper, the corporate extract — needs a certified Nepali translation attached, and the translation is examined with the same care as the original.
Most translation failures are not linguistic. They are consistency failures: the company name spelled differently across the POA, the translation and the application form.
In short
Documents filed at Nepal's Department of Industry go in Nepali, so every foreign-language document in an IP filing needs a certified Nepali translation. The workflow that survives examination: lock the source documents first (legalised, names consistent), translate through a translator who understands IP terminology, certify the translation, and check the translated names and dates against the application before filing. Translation errors cost examination cycles — a misspelled applicant name in a translated POA is one of the quietest ways to lose months.
Which IP documents need certified translation
The rule is simple: if the DOI has to read it, it has to be in Nepali — or travel with a certified Nepali version. In practice that reaches further than foreign applicants expect.
- Power of Attorney — legalised abroad, then translated; the applicant and agent names must match the application exactly
- Home or base registrations — the certified copy supporting a foreign filing, translated so the examiner can read the goods and the mark's status
- Priority documents — where Paris Convention priority is claimed (6 months for trademarks and designs, 12 months for patents)
- Assignment deeds and licence agreements — for recordals, where the transferred rights must be legible in Nepali
- Corporate documents — extracts and board resolutions supporting signatory authority
The translation set at a glance
The table is the checklist to hand any translator: for each document, the fields that must survive translation character-for-character, and the failure that shows up most often in examination queries.
| Document | Must match exactly | Common failure |
|---|---|---|
| Power of Attorney | Applicant and agent names, company spelling, signatory capacity | Name rendered differently than in the application |
| Home registration certificate | Mark, owner, classes, goods wording, dates | Goods list paraphrased instead of translated |
| Priority document | Filing number, office, date | Calendar confusion between BS and foreign dates |
| Assignment or licence | Party names, marks, scope of rights | Scope wording broader or narrower than the original |
| Corporate extract | Company name, registration number, legal form | Legal-form terms rendered inconsistently |
The translation workflow, step by step
The sequence matters because errors made early propagate into everything downstream.
Finalise and legalise the source documents first
Never translate a draft. The POA is notarised and legalised through the consular chain — Nepal is outside the Apostille Convention, so the route is notarisation, home-country authentication, then Nepalese mission legalisation, typically 2–6 weeks. Translate the final, signed, stamped version.
Lock the names before translating
Agree the Nepali rendering of the company name, the agent name and the address with the local agent before translation begins. The transliteration used in the translation must match the application form character for character — this single decision prevents most rework.
Translate with IP awareness
The translator needs IP vocabulary — the goods wording in a registration certificate, the classes, the term dates. A consumer translator who renders a Class 30 certificate's goods list loosely creates ambiguity the examiner then queries.
Certify and cross-check
The translation is certified — typically by the translator and, where the DOI or the document's later use requires, notarised. Before filing, a second reader compares translated names, numbers and dates against the original and the application form. Dates deserve special care: certificates often carry Bikram Sambat dates alongside foreign-language dates, and mixing calendar systems is a classic error.
The direction that surprises Nepali filers
Translation runs both ways. Nepali businesses filing abroad face the mirror problem — US, EU, UK and Indian offices want English documents, and Nepali corporate papers, POAs and certificates need certified English versions for foreign filings. The same discipline applies in reverse: lock the transliteration of the company name, translate final documents only, and keep the source and translation consistent across the whole foreign docket.
Keep one master transliteration table for the company — the Nepali name, the English name, and the agreed variants — and attach it to every translation job. It costs a page and saves the consistency argument at some future office.
What translation failures actually cost
A translation defect is rarely fatal; it is slow. The DOI issues written queries, the query cycle runs in weeks, and each round pushes the examination and publication timeline out — an unopposed application already takes roughly 12–18 months, and a name mismatch in a POA can add a full round trip. In recordals, a defective translation can mean the register still shows the old particulars after the fee is paid.
The honest cost comparison: a careful translation pass is hours of professional time. A corrected filing cycle is months. Every practitioner in Kathmandu has a story that ends with "the translation was rushed."
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.