A contract is a machine made of words. Translating one means keeping every part connected — the defined terms to their definitions, the cross-references to their clauses, the language of obligation to obligation and not to intention. We render binding agreements so the translated document imposes exactly what the original imposes.
When you need contract translation
You need a contract translated when parties negotiate, sign, or enforce across a language boundary — a supply or distribution agreement, an employment contract, a lease, a share purchase, a license, an NDA, a memorandum of understanding. Also when a signed agreement must be produced to a court, a registry, a tax authority, or a counterparty's counsel.
A translation for negotiation or internal review needs no certification. One going to a court, a registry, or a government office generally does — certified, or sworn in jurisdictions that require it. The guide by receiving authority sets out which.
Where contract translations fail
- Defined terms come loose from their definitions. An agreement that defines Territory, Confidential Information or Change of Control in clause 1 then uses each term forty times over. Every one of those instances must carry the defined sense and the identical rendering — not a synonym chosen for variety. A translator reaching for elegant variation has quietly created two terms where the contract has one, and a dispute where there was none.
- Obligation, futurity and permission collapse into each other. Shall, will, may and must are not stylistic alternatives: they are the difference between a duty, an expectation, a right and a condition. Languages divide this ground differently — the German hat zu against wird, the Italian subjunctive of obligation, the Turkish -meli — and getting it wrong changes what a party owes.
- Cross-references break. A contract navigates by number: as set out in Clause 8.2(b), subject to Schedule 3, save as provided in Article 14. Numbering, lettering and the internal pointers are preserved exactly, because a translated agreement whose references no longer resolve is a document nobody can read against its original.
- Legal systems do not map onto one another. Common-law consideration has no equivalent in civil-law systems, which require causa or nothing at all; trust, estoppel and tort have no clean counterparts either. Rendering such a term by its nearest cognate produces a sentence that reads well and means something the original never said. Where no equivalent exists, we render the function and note the term, rather than pretending to a correspondence that is not there.
- Boilerplate is not filler. Governing law, jurisdiction, severability, entire-agreement and force-majeure clauses are the parts most often skimmed and the parts most often litigated. They are translated with the same attention as the commercial terms, because that is where the argument goes when something breaks.
Which text prevails
Most cross-border agreements name one language as authoritative. A clause near the end records that the agreement is executed in two languages and that, in the event of discrepancy between them, one governs. That single sentence decides what the other text is for, and it should be settled before a word is translated rather than after.
Three arrangements are common, and they are not equally demanding.
| Arrangement | What the translation is | What it requires |
|---|---|---|
| The original governs | For information and negotiation. The signed text remains the source. | Accuracy throughout, and a clear note wherever the source is ambiguous. |
| The translation governs | The operative agreement, usually because it will be filed or enforced where that language is official. | Terminology fixed before drafting begins, and a full read of the rendered text as a contract in its own right. |
| Both are equally authentic | Two operative texts, executed together. | The most exacting of the three. Any divergence becomes a matter of construction rather than correction, so the two are read line against line before signature. |
Tell us which applies when you send the file. A translation that will be signed as an authentic text is not the same job as one that sits beside the original for reference, and we would rather know at the outset than learn it when the document is already in front of a notary.
We do not advise on which arrangement to adopt. That is a question for the counsel drafting the agreement, and it turns on where enforcement is likely and under which law. What we can tell you is what each one asks of the translation.
Licensing, royalty and distribution agreements
A licensing agreement grants the use of something without parting with it — a trademark, a patent, a piece of software, a format, a name. Everything of value in the document sits in the precise boundary between what the licensee may do and what the licensor keeps, and that boundary is drawn in language that has to survive translation intact.
Where the care goes
- The scope of the grant. Exclusive, sole and non-exclusive are three different things, and the middle one — where the licensor may still use the right itself but may license nobody else — has no settled term in several of our languages. It is rendered by its effect, not by a word that half-fits.
- Field of use and territory. Both are usually defined terms doing narrow work, and both are where a licensee later argues the grant was wider than the licensor intended.
- Royalty mechanics. Net sales definitions, permitted deductions, minimum guarantees, audit rights and reporting periods are arithmetic expressed in prose. A misplaced qualifier changes the sum owed.
- Sublicensing, assignment and change of control. Who else may come to hold the right, and on whose consent.
- Improvements and grant-back. What happens to what the licensee builds on top of the licensed material — a provision that is short, easily flattened in translation, and expensive when it is.
- Term, termination and survival. Sell-off periods, return or destruction of materials, and which obligations outlive the agreement.
Franchise, distribution and agency agreements are built from the same machinery and are handled the same way.
A note on the word license. This page concerns licensing agreements: contracts made between parties. It does not concern a license in the other sense — a driver's license, a professional practice license, a business or import permit, a firearms certificate. Those are issued by an authority rather than agreed between parties, and they are translated as certificates.
If that is what you have, certified translation is the page you want, and document types lists what we handle.
What we do not promise
We do not promise that a translated contract will be enforceable in another jurisdiction, and we do not give legal advice. Enforceability turns on local law, on the choice-of-law and jurisdiction clauses, and on counsel who know the forum. Our work is to give you and your lawyers a rendering that says exactly what the original says — so that the legal question is about the agreement, not about the translation.
We do not silently improve a contract. If a clause is ambiguous, internally inconsistent, or refers to a schedule that is not there, we translate it as it stands and tell you what we found. An agreement tidied in translation no longer matches the one the parties signed.
And we do not run contracts through a machine. A model produces fluent legal-sounding English with no sense of what is load-bearing — which is precisely the failure that does not announce itself.
How pricing works
Certified translation of an agreement is priced at €22.50 per page, confirmed at checkout before any charge. Volume discounts apply automatically from three pages onward, rising to 25% at seven or more — which is where most agreements land once schedules and annexes are counted. Uncertified translation for negotiation or internal review is priced per word.
Where a court or registry requires sworn translation or an apostille, we will tell you before you order.
How to prepare your file
- Send the complete agreement — schedules, annexes, exhibits, amendments, side letters and signature pages. A schedule omitted is a defined term left undefined.
- Say what the translation is for: negotiation, execution, a court filing, a regulatory submission. It determines whether certification is needed and how the rendering is pitched.
- Tell us whether the translation will be signed. If it is to be executed as an authentic text, or as one of two equally authentic texts, say so — it changes how the work is done.
- Send any glossary, prior translation, or house terminology you want followed. If your organization has rendered a term a particular way before, we will keep to it.
- Tell us the governing law and the parties' jurisdictions. A contract under English law translated for a German counterparty is a different problem from a German-law contract translated for an English one.
Frequently asked questions
What is the difference between contract translation and certified translation?
They answer different questions. Contract translation is about the rendering — whether the translated agreement imposes what the original imposes. Certification is about the attestation — a signed statement that the translation is complete and accurate, which an office can rely on. For a court filing or a registry submission you generally need both: the work done properly, and a statement standing behind it.
Which language version of a bilingual contract governs?
Whichever the agreement says governs. Most cross-border contracts carry a prevailing-language clause naming one text as authoritative; where both are executed as equally authentic, any divergence becomes a matter of construction rather than correction. Tell us which arrangement applies before we begin, because a translation that will be signed as an authentic text is a different job from one that sits beside the original for reference.
Do you translate licensing agreements?
Yes — trademark, patent, software, format and franchise licensing, together with distribution and agency agreements. The care goes into the scope of the grant, the field of use and territory, the royalty mechanics and audit rights, and what survives termination. Note that a licensing agreement is a contract between parties; a driver's license or a professional practice license is a document issued by an authority, and is translated as a certificate instead.
Do you translate all types of contracts?
Yes — commercial and supply agreements, employment contracts, leases and tenancies, share and asset purchases, licensing agreements, distribution and agency agreements, NDAs, memoranda of understanding, powers of attorney, and settlement agreements, in any direction between our ten languages.
Can a translated contract be used in court?
Courts generally require a certified translation, and many European courts require a sworn one made by a translator registered with them. Some filings need notarization or an apostille as well. Tell us the forum and we will say which applies rather than leaving you to find out at the registry.
Can you keep our existing terminology?
Yes, and we would rather you send it. If your organization has a glossary, an earlier translation of a related agreement, or simply a preferred rendering for a recurring term, it is followed throughout. Consistency across a set of related contracts is worth more than any individual choice of word.
The contract we sent has an error in it. Will you correct it?
No — we will tell you about it. A missing schedule, a cross-reference pointing at a clause that does not exist, a defined term used before it is defined: we flag each one and translate the document as it stands. The corrected version has to be the parties' own, agreed between them. A translation that quietly repaired a signed agreement would be worthless to anyone relying on it.
Related document guides
Ready when your agreement is.
Not sure whether your filing needs certification or a sworn translator? Send us the requirement and we will tell you, before you order. salve@enlatin.net