A US software company licensed its platform to a French buyer. The contract was drafted in English under New York law and translated into French for the buyer’s legal review. The English version contained a standard consideration clause: “In consideration of the mutual covenants herein, the parties agree...” The French translator rendered “consideration” as “contrepartie,” which is the ordinary French word for counterpart or exchange. Under French civil law, the binding element in a contract is not consideration but “cause” — the reason each party enters the agreement, which must be lawful and determined. “Contrepartie” doesn’t capture the legal meaning of either concept. When a dispute arose over whether the French buyer was obligated to make payments during a service outage, the French court analyzed the translated clause under the cause doctrine rather than the consideration doctrine, and reached a different conclusion than a New York court would have reached under the identical English text. The settlement cost the US licensor $6.4 million.
This is the fundamental problem of cross-border contract translation: common law and civil law systems don’t share the same conceptual architecture. They have structural differences that go deeper than terminology, and no amount of linguistic precision can bridge a gap that exists at the level of legal philosophy.
Common law builds from cases. Precedent accumulates into doctrine. Concepts like consideration, fiduciary duty, and indemnification have been shaped by centuries of judicial decisions, and their meanings include the accumulated weight of that case law. When you translate “consideration,” you’re not translating a word. You’re translating a concept that includes everything from Currie v Misa (1875) to the Restatement (Second) of Contracts. Civil law builds from codes. The French Civil Code, the German Bürgerliches Gesetzbuch, the Chinese Civil Code — these are comprehensive legislative frameworks where doctrine is prescribed from the top down rather than emerging from individual decisions. Concepts like cause, bonne foi, and Gewährleistung have meanings defined by statute and scholarly commentary, not by accumulated precedent.
The consequence: when a contract concept born in one legal tradition is translated into the language of another tradition, there may be no target concept that carries the same legal payload. Consideration has no civil law equivalent. Cause has no common law equivalent. The translator’s job is not to find the closest word — it’s to make visible the conceptual gap and ensure the parties understand what they’re actually agreeing to.
The consideration/cause problem is the most consequential example, but there are others that produce real commercial damage. Indemnification: a standard US contract provision where one party agrees to compensate the other for specified losses. In German law, the concept of Freistellung (release from liability) operates differently — it’s structured as a claim against the indemnifying party to prevent the indemnified party from being held liable in the first place, rather than a right to reimbursement after a loss has occurred. A translated indemnification clause that uses Freistellung without acknowledging this structural difference may create obligations that neither party intended.
Force majeure: in common law jurisdictions, force majeure is a contractual creation. It means whatever the contract says it means, because common law has no general doctrine of force majeure. In civil law jurisdictions, force majeure is a statutory concept. Article 1218 of the French Civil Code defines it as an event that is external to the parties, unpredictable, and irresistible. A force majeure clause translated from English to French may be read as supplementing the statutory definition, or it may be read as contradicting it, depending on how the translation handles the relationship between contractual and statutory provisions. If the English clause defines force majeure more narrowly than Article 1218, the French reader may assume the clause overrides the statute — which is not necessarily correct under French law.
Governing law and jurisdiction clauses create their own translation traps. A clause specifying “New York law” as governing law and “New York courts” as exclusive jurisdiction is straightforward in English. Translated into German, “Governing Law” becomes “anwendbares Recht,” which is accurate, and “jurisdiction” becomes “Gerichtsstand,” which is also accurate. But under German law, a choice-of-court clause may be interpreted differently depending on whether it’s classified as a Gerichtsstandsvereinbarung (jurisdiction agreement) or a Schiedsvereinbarung (arbitration agreement), and the translation of “courts” as “Gerichte” rather than “Schiedsgericht” may trigger different procedural rules than the English original intended. A German company I worked with assumed a “New York courts” clause meant they could resolve disputes in German courts applying New York law, because under German procedural law, jurisdiction and applicable law are independent concepts. The English clause intended exclusive jurisdiction in New York. The translation didn’t make the exclusivity clear enough under German interpretive principles.
The practical approach to cross-border contract translation involves three layers. First: legal concept mapping before translation begins. Identify every term in the source contract that has a legal meaning specific to its legal system, and determine whether a corresponding concept exists in the target system. Where there’s no equivalent, flag it. Second: structural adaptation, not just linguistic translation. If the source contract is structured around common law concepts (representations and warranties, indemnification, limitation of liability caps) and the target jurisdiction is civil law, the contract structure may need to be adjusted to reflect the target system’s doctrinal framework. Third: translator’s notes or comparative annotations for terms where the conceptual gap is significant. A footnote explaining that “consideration” has no civil law equivalent and that the parties intend the contract to be binding under the cause doctrine of the governing law is worth more than a translation that pretends the gap doesn’t exist.
The cost of getting this wrong is asymmetric. If the translation works, the contract functions as intended. If it doesn’t, the resulting dispute is expensive and the outcome is unpredictable, because courts in different legal systems will interpret the same translated text differently. The $6.4M consideration/cause settlement I mentioned at the start — that was a company that treated cross-border contract translation as a language task and discovered too late that the language was the least of their problems.
Artlangs Translation provides cross-border contract translation across 230+ language pairs: legal concept mapping between common law and civil law systems, structural adaptation for jurisdiction-specific doctrinal frameworks, translator’s annotations for non-equivalent concepts, and governing law and jurisdiction clause verification. Because bridging legal systems requires more than bridging languages.
