A contract translation is different from other business document translation because the translated words create obligations. A catalog entry that is loosely translated produces a wrong order. A contract clause that is loosely translated produces a different deal — one side believes it agreed to one thing, the other side believes it agreed to another, and both can point at a signed document to prove it.
What follows stays on ground that is specific to contracts: which language version governs, how defined terms and obligation wording must hold, how commercial figures and execution details cross over, how drafts and amendments stay aligned during negotiation, and how to check the result before signing. The general ground — how translation work runs, what to hand over before it starts, machine translation, and what moves a quotation — is covered in business document translation in China, and is not repeated here.
Which Version Governs?
Bilingual contracts are common in China business because each side needs to read the deal in its own language. The two versions sit side by side, and the question that matters most is rarely asked until there is a disagreement: if the versions differ, which one prevails?
The governing version clause decides. Most bilingual contracts name one version as governing, and when the versions conflict, the governing version is the one that counts. Check that this clause exists, that it names the version you expect, and that the clause itself says the same thing in both languages. A governing clause that is itself mistranslated decides nothing — it only adds a second disagreement about the first one.
In practice, the Chinese version often governs. In dealings with Chinese counterparties, the Chinese version is frequently the one treated as controlling, especially where the contract will be performed or enforced in China. This is a tendency, not a rule. Only the clause settles it, and only the clause as written in the version that governs settles it. Confirm the governing version in writing before signing, and never assume it from habit or from what happened on a previous deal.
Where there is no governing clause, a difference between versions becomes an ambiguity with no agreed answer. Each side argues for the version that favors it, and the argument is about the contract itself rather than about performance. That is the most expensive kind of disagreement to have, because it must be resolved before anything else can be. If the draft you receive has no governing clause, raise it before translation starts, not after signing.
What belongs in the contract itself — the clauses, protections, and payment terms worth including — is a separate question. See what to put in a China sourcing contract for that side of the work.
Defined Terms: One Term, One Meaning
Contracts define their own vocabulary. A word given a specific meaning in the definitions section carries that meaning everywhere it appears, in every clause, schedule, and appendix. The translator's job is to keep each defined term identical — same rendering, same capitalization — from the first page to the last.
Drift is the failure mode. A contract that calls the counterparty "Supplier" in the definitions and "Vendor" in the delivery schedule has, on paper, two different parties. A product term rendered two ways across a technical schedule reads as two different products. Neither error looks serious in isolation. Both become serious the moment someone relies on the document to argue what was agreed.
Three disciplines prevent drift. First, the translator works from a defined-terms list taken from the contract itself, not from general vocabulary — the contract's meaning wins over the dictionary's. Second, cross-references travel with the terms: a reference to Section 3.2 or Exhibit A must point at the same numbered place in the translation as in the source, after any renumbering is accounted for. Third, schedules and appendices get the same treatment as the main body. The parts of a contract that get translated loosely are rarely the main clauses. They are the attachments, where the commercial detail lives.
If the source uses a term inconsistently, the translator should ask rather than choose. Guessing at a defined term is not a small liberty. It rewrites the definition.
Obligation and Condition Language
Contract language is deliberately precise about who owes what, by when, and under what conditions. Small shifts in this wording change the deal itself, which is why obligation and condition language gets its own check rather than being left to general accuracy.
The modal verbs carry the weight. Must, shall, and may are not interchangeable, and neither are will and should in a contract setting. A "shall" rendered as "may" turns an obligation into an option. A "may" rendered as "shall" turns an option into an obligation. The translator must preserve the force of each, clause by clause, and flag any place where the source language leaves the force genuinely unclear instead of resolving it silently.
Conditions matter as much as obligations. Words like "subject to," "provided that," and "unless" set the circumstances under which an obligation applies at all. A dropped condition does not read as a translation error after signing. It reads as an unconditional commitment. The same applies to time language: "within 30 days," "no later than," and "on or before" set different deadlines, and a deadline rendered loosely is a deadline missed or a deadline invented.
Remedy language needs the same care. Caps on liability, liquidated damages, indemnity wording, and cure periods all set numbers and thresholds that decide what a breach costs. The translator's task is to carry those numbers and conditions across exactly, including where a threshold appears in more than one clause. Where the same threshold is stated twice and the two statements differ after translation, the contract contradicts itself — and the contradiction will be found by the side it favors, at the worst time.
Commercial Terms and Figures
The commercial schedules of a contract — prices, quantities, delivery, and payment — are where translation errors turn into money fastest. These sections deserve a check of their own, separate from the legal clauses, because the failure mode is different: not a wrong obligation, but a wrong number.
Amounts must match in words and in figures. Contracts commonly state key amounts both ways, and both forms must agree with the source exactly. A single shifted figure in a unit price, a total, or a payment milestone is a commercial dispute waiting for a trigger, and it will surface at the invoice, not at the signing.
Currency, delivery terms, and payment mechanics must cross over intact. The currency of each amount, the delivery terms the parties agreed (such as Incoterms, where used), and the payment method and schedule — installments, milestones, or payment against documents — all need to read identically in both versions. A payment term that names the right amount in the wrong currency is not a near miss. It is a different payment.
Quantities carry their own risks. Tolerances — the plus-or-minus range allowed on a quantity — must be preserved exactly, as must units of measure. A tolerance of five percent rendered as a fixed quantity, or a unit rendered in the wrong system, changes what must be delivered. Delivery schedules need the same treatment: dates, ports or places, and partial-shipment permissions must match the source clause by clause, because a schedule that reads correctly in one version and differently in the other is two schedules.
Execution: Signatures, Seals, and Counterparts
An otherwise accurate translation with a missing execution detail is an incomplete document. Execution — how the contract is signed and made effective — must come across completely and in the right places.
Signature blocks, dates, and the names and titles of the signatories must be carried over in full. Where the parties require company seals or chops, the requirement must appear in the translation exactly as in the source, including which party's seal is required and where it goes. A contract that is signed but not sealed where a seal was required, or sealed by the wrong entity, can fail at the point where it matters most: when someone tries to rely on it.
Counterparts need attention too. Where a contract is signed in counterparts — each party signing a separate copy, with all copies together forming one agreement — the translation must preserve that mechanism and state it the same way in both versions. Dates matter here as well: the effective date, the signing date, and any date from which obligations run are three different things, and confusing them shifts the whole timeline of the deal.
Where the contract will be submitted to an authority, certified handling may be required, and the requirement differs by body and by document type. Confirm it with the receiving authority before submitting, since a private agreement between two businesses and a filing with an authority are different uses with different requirements.
Translating Drafts and Redlines During Negotiation
Contracts are rarely translated once, from a finished text. More often, drafts move back and forth during negotiation, each round marked up, and translation has to keep pace without losing track of what changed, in which language, and when.
Version control is the discipline that makes this work. Number and date every round, in both languages, and keep a record of which round is current. The translator works on the current round only, and every round that goes out for comment in one language must be matched by the same round in the other. A negotiation where the English draft is on round four and the Chinese draft is still on round two is not a negotiation. It is two negotiations, and the parties will discover that at signing.
Redlines — the tracked changes each side makes — need translating as changes, not as fresh text. The translator must show what changed against the previous agreed round, so each side can see exactly what it is accepting. Accepting a clean copy without the change history means accepting wording nobody has compared against what was agreed before. Where a change is made directly in one language version only, it must be carried into the other version and marked as a change in the same round, before the round goes back. A change that exists in one version and not the other is a difference between versions waiting to be discovered.
For interpretation support during the negotiation that produces the contract, see the China translation services hub, which covers both spoken and written language support for China business.
Amendments and Side Letters
A contract is rarely signed once and never touched again. Amendments, side letters, and appendices change the deal after signing, and each one needs the same treatment as the original: translation, checking against the governing version, and alignment between languages.
The risk is the untranslated amendment. A price change, a specification change, or a deadline extension agreed in one language and never carried into the other quietly undoes the accuracy of the original translation. The parties then hold two versions of the deal that differ, and the difference is discovered when performance under one version does not match expectations under the other. Every amendment must be translated in full, checked against the governing version, and attached to the same contract file as the original, so the complete deal exists in both languages.
Effective dates and superseded clauses need the same care as in the original. An amendment takes effect on its own date, which may differ from the signing date, and clauses it replaces must be marked as superseded in both versions. A clause that is marked superseded in one version and left standing in the other creates two contracts where there should be one. Side letters — separate documents that change or clarify the main agreement — follow the same rule: translate them, check them, and file them with the agreement they modify, in both languages.
How to Check Before Signing
Checking a translated contract is not re-translating it. It is a targeted protocol over the places where errors change the deal, run on the exact version that will be signed — not on an earlier draft.
Work clause by clause against the source, in this order. First, the governing version clause: it names the version you agreed, in both languages, and nothing else in the document contradicts it. Second, defined terms: each appears identically every time, with the same capitalization, matching the definitions section. Third, obligation and condition language: must, shall, and may carry their force, conditions and deadlines read as in the source, and remedy thresholds match wherever they appear. Fourth, figures: every amount, quantity, date, and tolerance matches the source in words and in figures. Fifth, execution: signature blocks, dates, seals or chops where required, and counterparts are complete and in the right places.
Two methods add assurance where the stakes justify them. Back-translation — translating the translation back into the source language for comparison — surfaces drift that a single-direction check misses, particularly in defined terms and obligation language. A second reader, working independently from the first translator, catches what familiarity hides. Neither replaces the clause-by-clause pass. Both strengthen it.
Finally, compare the version you sign against the version you checked. Last-minute swaps — a page replaced, a schedule reissued, a clause reworded after checking — are how checked contracts become unchecked ones. If anything changed after the check, check the changed part again. Then have counsel review the translated contract before signing. Translation accuracy and legal advice are different jobs: the translator ensures the wording matches the source, and counsel ensures the terms protect your position, including the governing law and dispute clauses. This guide is about translation, not legal advice.
Key Takeaways
- The governing version clause decides which language version prevails. Confirm it in writing before signing, and never assume it.
- Defined terms must stay identical — same rendering, same capitalization — in every clause, schedule, and appendix.
- Obligation and condition language carries the deal: must, shall, and may are not interchangeable, and a dropped condition is an unconditional commitment.
- Commercial figures must match in words and in figures: amounts, currency, delivery terms, tolerances, and schedules, clause by clause.
- Execution details complete the document: signature blocks, dates, seals or chops where required, and counterparts, all in the right places.
- Amendments, side letters, and negotiation redlines need the same translation and checking as the original, in the same round, or the versions drift apart.
Frequently Asked Questions
Q: What happens if the two language versions differ?
A: It depends on the governing version clause. When the clause names one version as governing, that version generally prevails on a conflict. If there is no clause, the difference becomes an ambiguity that can turn into a dispute about the contract itself. Check the clause before signing, and have counsel review anything that changes the balance of the deal.
Q: Who should translate the contract — our translator or the counterparty's?
A: Have your own translator handle the version you will rely on. A counterparty-provided translation may be accurate, but it was prepared for the other side's interests, and you have no way to verify it without your own check. If the counterparty provides a version, have it independently checked against the governing version before signing.
Q: Should the translation be attached to the signed contract?
A: Yes, where both versions form the agreement. Attach the translation to the signed contract, identify each version by language, date, and version number, and state which version governs. An unattached translation that floats separately from the signed set is easy to lose, replace, or dispute.
Q: What if the counterparty amends only one language version?
A: Treat it as an incomplete amendment. The change must be carried into the other version, checked against the governing version, and marked as a change in the same round, before anyone relies on it. An amendment that exists in one version only creates two versions of the deal, and the difference will surface when performance is measured against the wrong one.
Q: Do I need a lawyer to review the translated contract?
A: Translation accuracy and legal advice are different jobs. The translator ensures the wording matches the source. Counsel ensures the terms protect your position, including governing law and dispute clauses. Have counsel review the translated contract before signing.
Q: What if we discover a difference after signing?
A: Preserve both versions exactly as signed, note the difference in writing, and seek counsel promptly. Do not re-translate or amend one version unilaterally, since that can change the evidence of what was agreed. How the difference is resolved depends on the governing version clause and the governing law, which is why counsel should lead from this point.
Arrange Contract Translation in China
If you need a contract translated for China — a sales contract, distribution agreement, or confidentiality agreement — start by outlining what you have and what the translation will be used for.
Share the document type, language pair, approximate length, deadline, and intended use. These details determine the right translator, the checking level, and the format you get back. Send them and we will confirm the scope and quote for the job.
For broader local assistance alongside translation, see our China Local Support & Errand Service.
For assistance coordinating your requirements in China, contact China Biz Agent with your documents and deadline. The appropriate arrangement will depend on the document type, volume, and how the translation will be used.