Your notarized translation is useless. Delhi High Court wants one of six things.

When the Registry says no to your document

You have a signed contract. A balance sheet. A crucial email chain. Every word is in Hindi, or French, or Mandarin. You walk into the Delhi High Court Registry, file it, and the clerk pushes it back. No English translation? No entry. Your case stalls before a single argument is heard. That rejection costs you time, momentum, and sometimes the entire proceeding. Here's exactly what you need to do to make sure it never happens.

What the Registry actually checks

The Delhi High Court (Original Side) Rules, 2018, Chapter IV, Rule 5, is the gatekeeper. It says: no document in a language other than English shall be received by the Registry unless it is accompanied by an English translation. That sounds simple. But the rule doesn't stop there. It lists six specific ways that translation must be certified. Miss any one of them, and the document is dead on arrival.

Think of it as a checklist the Registry runs in its head. First: is the document in English? If yes, proceed. If no, next question: is there an English translation attached? If yes, next: how is that translation certified? If the certification doesn't match one of the six permitted modes, the document is rejected. No discretion. No "we'll accept it and fix it later." The Registry's job is to enforce the rule, not to bend it.

This isn't about the court being difficult. It's about judicial comprehension. A judge cannot decide a case based on a document they cannot read. The translation is not a formality—it is the bridge between the evidence and the decision. And the rule ensures that bridge is built properly, by someone whose word the court can trust.

Six ways to get your translation accepted

Here are the six certification routes, in order of practical usefulness. Pick the one that fits your situation.

1. Get all parties to agree. If the other side signs off on the translation, the Registry will accept it. This is the cleanest path—no advocate certification needed, no court translator required. But in adversarial litigation, agreement is rare. Use it when you can, but don't count on it.
2. Have your own advocate certify it. The advocate engaged in the case can certify the translation as true. This is the most common route. Your lawyer reads the original, compares it to the translation, and signs a certificate. The Registry trusts the advocate's professional word.
3. Have another advocate certify it, with your advocate's authentication. If your advocate doesn't want to personally certify—maybe they don't read the source language—another advocate can do the certification. But then your advocate must authenticate that certification. Two signatures, one document.
4. Use an official court translator. The Delhi High Court has its own panel of translators. If you go through them, the translation carries the court's own stamp. This is the gold standard, but it can take time and cost more.
5. Use a translator recognized by the Court, Central Government, or State Government. Many government bodies maintain lists of approved translators. If your translator is on one of those lists, the Registry will accept their work. Check the list before you hire.
6. Get a translator approved by the Registrar. If none of the above works, you can apply to the Registrar for a special appointment. The Registrar can approve a translator specifically for your document. This is the fallback option—use it when the other five are unavailable.

Each route has the same end result: a certified English translation that the Registry will accept. The difference is in who does the certifying and how much friction you face.

The Registrar's hidden power

Rule 5 also gives the Registrar a separate power: to order any party to produce and leave with the Registrar any document not in English that is in that party's possession, for the purpose of being officially translated. This is a discovery tool. If the other side has a key document in a foreign language and won't share a translation, you can ask the Registrar to compel them to hand it over for official translation. The Registrar then arranges the translation, and both sides get a certified copy.

This is useful when the document is in the opponent's control and they are using the language barrier to hide evidence. The rule turns their advantage into your opportunity.

What lawyers don't tell their corporate clients about translation

Here's the insider truth: most litigation delays from translation issues happen because the lawyer didn't plan for it. The client hands over a stack of documents in Hindi, or a contract in French, and the lawyer files them without checking the certification. The Registry rejects them. The lawyer then scrambles to get the translation done, losing a week or more. Meanwhile, the opposing counsel is already serving notice, filing replies, building momentum.

The fix is simple: before you file anything, ask your lawyer which certification route they will use. If they say "don't worry, we'll sort it out," that's a red flag. The answer should be specific: "I'll certify it myself under Route 2," or "We'll use a government-approved translator under Route 5." If they can't give you that answer, find a lawyer who can.

For in-house counsel and CFOs, this is a due diligence item. When you are sending documents to external counsel for litigation, include a note: "Please confirm the translation certification route for any non-English documents." It takes ten seconds and saves days of delay.

The one thing that changes everything

There is a common misconception that a notarized translation is enough. It is not. Notarization is not one of the six permitted modes. A notary public can certify that the translator appeared before them and swore to the accuracy of the translation, but that does not satisfy Rule 5. The Registry will reject it. You need one of the six specific certifications, not a notary stamp.

Another trap: assuming that a translation prepared for a different proceeding will work. If you had a contract translated for an arbitration in Singapore, and now you want to use the same translation in the Delhi High Court, you need to check the certification. Was it certified by an advocate engaged in the arbitration? If that advocate is not engaged in the current case, the certification may not carry over. You may need a fresh certification under Route 2 or 3.

THE PLAY: Before you file any non-English document, confirm the certification route with your advocate and get the certificate signed before the filing date—not after the Registry rejects it.

If you're in this spot: the three-step fix

Suppose you have already filed a document without a proper translation, and the Registry has rejected it. Here is what to do:

Step one: Identify which certification route you can use fastest. If your advocate reads the source language, Route 2 is the quickest. If not, find a government-approved translator (Route 5) or apply to the Registrar (Route 6).

Step two: Get the certification in writing. The certificate should state: "I, [name], advocate/translator, certify that the attached English translation is a true and accurate translation of the original [language] document." Sign and date it.

Step three: Re-file the document with the certified translation attached. The Registry will accept it if the certification matches one of the six routes.

That is the entire process. It is mechanical, not strategic. But missing it can cost you the case.

The bottom line

If you are dealing with a document not originally in English, your only job is to ensure it arrives at the Registry with a certified English translation that matches one of the six permitted modes. No shortcuts. No notarization. No "we'll fix it later." The rule is clear, the Registry enforces it, and the only person who suffers from non-compliance is you. Pick your certification route before you file, and you will never hear the words "document rejected" from the clerk.