Contract translation pitfalls: when a translated contract isn't the same contract
Why "the English version controls" matters, the legal force of translated copies, and how to handle multi-language contracts without creating two different obligations.
Translation is interpretation
Every translation is an act of interpretation. A 50-page English contract translated into Mandarin or Spanish or German will not say exactly the same thing in the target language — legal terms of art don't have one-to-one translations, and idiomatic constructions ('best efforts', 'reasonable endeavours', 'good faith') carry different weight in different legal traditions. That gap is where disputes are born.
The controlling-language clause
The single most important clause in a multi-language contract is the controlling-language clause: "This Agreement is executed in English and [Language]. In case of conflict, the English version controls." Without it, courts in each jurisdiction will apply their own canons of construction and you can end up with two contracts that say different things.
When you can't make English control
Some jurisdictions require local-language contracts as a matter of public policy. France's Toubon Law requires French for consumer contracts. Quebec requires French. China requires Chinese for contracts to be enforceable in Chinese courts. In those cases, you draft in two languages, accept that the local language controls in local courts, and add an arbitration clause to keep disputes in a neutral, English-speaking forum.
Mistranslation of legal terms of art
'Best efforts' translates differently in every legal system — and means different things even within English-speaking jurisdictions. 'Liquidated damages' has no real equivalent in many civil-law systems. 'Indemnify' has cleaner equivalents in French ('indemniser') and Spanish ('indemnizar') but blurry ones in Japanese. A contract that uses common-law terms of art and is then translated into a civil-law language can lose its teeth in translation.
Numbers and dates
The trivial-looking traps: numeric conventions (3,141.59 vs. 3.141,59), date formats (3/4/2026 means March 4 in the US and April 3 in India), currency symbols ($ might mean USD, CAD, AUD, SGD, HKD, or MXN). Always spell out currencies in full ('US Dollars (USD)') and use unambiguous date formats ('3 March 2026' or ISO '2026-03-03').
Quality control on a translation
Use a translation provider that (a) uses qualified legal translators (not generic translators), (b) provides a back-translation by a second translator to spot errors, and (c) employs a local lawyer for a brief review of legal terms. The added cost is a fraction of a single litigated mistranslation.
AI translation, with caveats
Large language models translate basic legal text increasingly well — but they still hallucinate legal terms and miss subtle differences in legal tradition. Use AI translation for first-pass drafts and internal comprehension; never use it as the final signing version of a contract.
How to handle a multi-language redline
When a contract is being negotiated in two languages simultaneously, agree at the start: (1) which language the negotiating versions are in, (2) when the other language gets updated (after each clean round, not every redline), (3) who is responsible for keeping them in sync, and (4) one final QA pass before signing. Without those agreements, you end up signing two slightly different contracts.
Stop reading contracts. Start understanding them.
Upload any PDF or DOCX and get a plain-English summary, risk score, and negotiation suggestions in under 60 seconds.
Try ContractScan AI free