FLAT LAW FIRM
Request a consultation

Corporate Legal Services

Bilingual Contract Review Checklist: 18 Points Before Signing

9 min readFLAT LAW FIRM
Ký kết tài liệu bằng bút máy, minh họa checklist rà soát hợp đồng song ngữ trước khi ký

Bilingual Contract Review Checklist: 18 Points to Check Before Signing

This bilingual contract review checklist is for FDI enterprises routinely signing Vietnamese–English (and Vietnamese–Chinese) contracts: bilingual contracts are the norm in cross-border deals, yet a single word diverging between the two versions can surface only when a dispute erupts — too late. The 18-point checklist below enables systematic pre-signing review — each point states what to check, why it matters, a quick checking method, and typical error signals.

Contents

1. Golden rules for bilingual contract review

  1. Review clause-by-clause in pairs, never skim the two versions separately. Place both versions side by side and check each corresponding clause — reading each version alone will never reveal where they diverge.
  2. The translation must reflect correct legal intent, not just grammar. "Right words, wrong meaning" is more dangerous than "clumsy translation": a smooth sentence that changes a clause's meaning can cost you your rights.
  3. Reviewers must understand both language and law. A linguistically skilled translator who misunderstands the legal substance of "indemnity" versus damages will mistranslate intent — so the final review round should involve a lawyer.

2. The 18-point checklist

Group A — Framework (1–5)

  • [ ] 1. Prevailing language clause: check whether the contract designates which language version governs when the two conflict. Why: without this clause, each side clings to one version in disputes, forcing arbitrators or courts to reinterpret from scratch — costly and unpredictable. How to check: search for "prevail"/priority language in both versions and confirm both designate the same governing version. Error signal: the two versions designate opposite versions, or the clause is missing entirely.
  • [ ] 2. Party information: full names, head-office addresses, tax codes, legal representatives and titles — absolutely matching in both versions. Why: wrong names or tax codes can affect contract validity and later enforcement. How to check: compare directly against each party's enterprise registration certificate/ERC; beware of abbreviated names. Error signal: the English version uses an unregistered abbreviation, or the addresses differ.
  • [ ] 3. Defined terms: every capitalized term must be defined once in the definitions section and used consistently throughout both versions. Why: the same concept translated differently in the two versions creates two different obligations. How to check: build a bilingual terminology table and search each term across the full text. Error signal: one Vietnamese word rendered as two different English words in different clauses.
  • [ ] 4. Clause structure: article/paragraph numbering must match between versions. Why: a translated version adding or dropping a sub-clause throws off every cross-reference that follows. How to check: place both tables of contents side by side and compare numbering from start to finish. Error signal: the translation merges two sub-clauses into one, or renumbers without updating references.
  • [ ] 5. Cross-references: every "as per Article X" must point to the correct article number in both versions. Why: a wrong reference applies the wrong clause — an error readers rarely catch because few follow each reference. How to check: follow each reference and verify the target article exists with matching content. Error signal: after renumbering in the translation, references still carry the old numbers.

Group B — Commercial content (6–10)

  • [ ] 6. Amounts: figures, currencies, amounts in words — absolutely matching. Why: this is the most common error with the most direct consequence: one wrong figure means a wrong payment obligation. How to check: read each figure aloud in both versions; watch thousand/decimal separator conventions (1,000 vs 1.000). Error signal: the Vietnamese version states "two billion VND" while the English states "two million USD" — completely wrong value.
  • [ ] 7. Dates and deadlines: signing date, effective date, deadlines, warranty periods — matching with one consistent format. Why: a shifted effective date changes the entire obligation schedule. How to check: build a bilingual timeline from both versions and compare; adopt a single date format throughout. Error signal: "05/06/2026" means 5 June in the Vietnamese version but may read as 6 May to an English reader.
  • [ ] 8. Scope of work / subject matter: technical descriptions, quantities — the translation must neither narrow nor expand. Why: changing scope through translation changes the contract's subject matter without one party knowing. How to check: compare each scope bullet; have both an engineer and a lawyer review. Error signal: the English version adds "approximately" before quantities while the Vietnamese states absolute figures.
  • [ ] 9. Price and payment: payment terms, late penalties, guarantees — equivalent in both versions. Why: differing payment mechanics trigger cash-flow disputes as soon as performance begins. How to check: draw the cash flow (who pays whom, when, how much, how) from each version and compare. Error signal: the Vietnamese says "payment within 30 days" while the English says "within 30 business days" — 30 days and 30 business days differ.
  • [ ] 10. Appendices and attachments: fully listed with matching numbering. Why: a missing or misnumbered appendix leaves part of the contract uncitable in disputes. How to check: count the physically attached appendices and compare each title and number across versions. Error signal: the translation renumbers appendices (Appendix A becomes Appendix 1) while the main text still cites "Appendix A".

Group C — Legal clauses (11–15)

  • [ ] 11. Governing law: law names and document numbers — accurate in both versions. Why: non-standard translations of law names confuse research and citation (e.g., "Luật Doanh nghiệp" has the official English rendering "Law on Enterprises"). How to check: use official English names where available; verify the cited instrument is still in force at signing. Error signal: citing a repealed or replaced instrument number.
  • [ ] 12. Dispute resolution: arbitration or court, which institution, where, language of proceedings — absolutely equivalent. Why: one wrong word can lose the arbitration option — e.g., the Vietnamese names "Vietnam International Arbitration Centre (VIAC)" while the English vaguely says "arbitration in Vietnam". How to check: break down each element — forum, seat, language, procedural law — and compare versions. Error signal: one version names the arbitral institution, the other says only "arbitration" generically. See the standard clause framework for international commercial contracts to draft this clause correctly from the start.
  • [ ] 13. Force majeure: covered events, notification procedures, legal consequences — equivalent. Why: a narrower definition in one version can strip that party of relief when an event occurs. How to check: compare the listed events in both versions; verify notice periods and forms match. Error signal: the Vietnamese lists "dịch bệnh" (epidemics) while the English has no "epidemic/pandemic".
  • [ ] 14. Indemnity: compensation mechanics, liability caps — the translation must capture the true nature. Why: common-law "indemnity" is not identical to "bồi thường thiệt hại" under Vietnam's Civil Code 2015; mechanical translation alters the liability regime. How to check: read the mechanics — when indemnity triggers, whether fault must be proven, the cap — rather than comparing words. Error signal: the English uses "indemnify and hold harmless" while the Vietnamese compresses it to "bồi thường" (compensate).
  • [ ] 15. Termination: termination events, notice periods, consequences — equivalent. Why: differing termination conditions mean one party holds a right the other never knew existed. How to check: build a bilingual comparison table: which events, how much notice, in what form, with what consequences. Error signal: the Vietnamese says "30 days' notice" while the English says "30-day prior written notice" — the "written" requirement exists in only one version.

Group D — Form and effectiveness (16–18)

  • [ ] 16. Signatures and seals: authorized signatures, seals (if required) on both versions. Why: a missing signature on one version invites disputes over whether that version is effective. How to check: inspect each original — signature, printed name, title, seal (if any). Error signal: only the Vietnamese version signed, the English left blank.
  • [ ] 17. Effective date and conditions: matching; state clearly if approval or notarization is required for effectiveness. Why: "effective upon signing" contradicts itself when the two versions bear different signing dates. How to check: compare the effectiveness clause in both versions; list any conditions precedent. Error signal: the Vietnamese says "kể từ ngày ký" (from the signing date) while the English says "upon execution by both parties" — whether signing includes sealing remains unclear.
  • [ ] 18. Number of originals: how many originals each party keeps and which languages each contains. Why: in an "originals" dispute, only one fully executed copy puts you at a disadvantage. How to check: count the actually executed originals against the clause. Error signal: the clause says "in quadruplicate" but only two originals exist.

3. The three most classic errors

  1. Mismatched amounts and dates — the most common error with the most direct consequences. Illustrative example: the Vietnamese version states a contract value of "two billion VND"; the English states "two billion VND (approximately USD 80,000)" — "approximately" turns an absolute figure into an estimate, enough for the counterparty to dispute at payment. See the scenario of a counterparty demanding a mid-contract price increase for how price disputes unfold.
  2. No prevailing language clause — in disputes each side clings to one version, forcing arbitrators or courts to reinterpret from scratch. Costs and timelines multiply versus a clause of a few lines. It is point 1 of this checklist, yet the most skipped when parties rush to sign.
  3. Mechanically translating "indemnity" as damages — distinct legal concepts; mistranslation alters the liability regime. Illustrative example: "indemnify and hold harmless against all losses" compressed into "compensate all losses" — the translation drops the duty to defend against third-party claims, which is the core of indemnity.

4. Frequently asked questions

Q: What is a prevailing language clause?

A: A clause designating which language version governs in case of conflict. Without it, interpreting the contract in disputes becomes very complex.

Q: What should bilingual contract review cover?

A: This bilingual contract review checklist covers 18 points: prevailing language, consistent terminology, matching figures/dates, correct cross-references, equivalent dispute resolution clauses, signatures and effectiveness.

Q: How to handle legally non-equivalent terms?

A: Define them clearly in the contract (defined terms) and keep them consistent throughout. For concepts without absolute equivalents (e.g., 'công chứng' vs 'notarization'), explain by definition rather than word-for-word translation.

Q: Which version is correct when figures or dates differ?

A: Fix them to match absolutely before signing — never leave 'which is correct' for a court to decide later. This is the most common bilingual contract error.

Q: Who should review a contract translation?

A: A lawyer fluent in both languages and the relevant legal systems — not just a translator, because many legal terms require understanding legal substance, not only language.

Q: Any extra notes for Vietnamese–Chinese bilingual contracts?

A: Beyond the general checklist, note the greater systemic legal differences (the two civil-law systems conceptualize differently), and have a Chinese lawyer co-review the Chinese version.

5. When to work with a lawyer

Work with a lawyer when: (1) drafting or reviewing high-value bilingual contracts — from the drafting stage, consult the standard clause framework for international commercial contracts to prevent errors at the source; (2) spotting version conflicts before signing; (3) disputes already arising from translation differences; or (4) building standard bilingual templates for the enterprise, especially in specialized fields such as EPC contracts and FIDIC or import-export contracts. For a real conflict case study, see T-396; for in-depth drafting, see T-389. FLAT Law Firm reviews and drafts Vietnamese–English–Chinese bilingual contracts — contact hotline 0988424851.

References

  • Civil Code 2015 (91/2015/QH13).
  • Content cross-checked at time of writing (28/9/2026); supplementary review 29/9/2026.

—