Quick summary: Settle one question before ordering: does the contract say which language version governs? If it does, your translation is a working document rather than the operative agreement, and that changes how it should be used. Beyond that, the things that make a translated contract usable are defined terms rendered consistently, clause numbering preserved exactly, and every annexure included — because cross-references are how a contract is read.
Commercial contract translation is ordered for two quite different reasons, and confusing them causes real problems.
To understand an agreement you are considering, performing under, or in dispute about.
As a record — for a lodgement, an audit, a due diligence process or a court.
The translation work is the same. What differs is how carefully version control has to be handled afterwards.
First: which version governs?
Most cross-border contracts contain a clause stating which language version prevails in the event of inconsistency. Find it before you order.
If the contract nominates a governing version
Your translation is a reading aid, not the agreement. Every substantive question — obligations, liability, termination — is answered by the governing version, and any divergence in the translation is resolved in the governing version's favour.
That is not a reason to skip the translation. It is a reason to label it clearly, so nobody in your organisation later negotiates from the wrong document.
If it does not, or you are creating a bilingual version
Then the drafting question becomes live, and it is a legal one. Whether to execute a bilingual agreement, and how to word the prevailing-language clause, is a matter for a lawyer before signature rather than a translator after it.
Defined terms have to be consistent
A contract is a closed system. Terms are defined once and then used with that exact meaning throughout, and the whole structure depends on the reader being able to see that a word is the defined term rather than an ordinary word.
A translation must therefore pick one rendering for each defined term and use it everywhere — including in the annexures, which are frequently translated last and are where consistency most often slips.
This is why it matters that a single translator, or a coordinated team working from a shared glossary, handles the whole instrument. Splitting a contract across providers to save time is how a document ends up defining "the Goods" three different ways.
If you have existing translated agreements with the same counterparty, supply them. Continuity of terminology across a commercial relationship is worth a great deal.
Numbering and cross-references are structural
Clause numbering is not formatting. It is how the document refers to itself.
A translation preserves the numbering and hierarchy exactly, so that clause 8.3.2 is clause 8.3.2 in both versions and every cross-reference still lands. Renumbering to suit a different convention would break the document.
The same applies to schedules, annexures and exhibits: their labels are part of the reference system.
Send the whole instrument
The most common omission in contract orders, and the most damaging:
- the main agreement
- every schedule, annexure, exhibit and appendix
- any side letters referenced by the contract
- variations, amendments and extensions agreed since execution
- the execution pages, with signatures, dates, company seals and witness details
An agreement translated without its schedules refers repeatedly to commercial terms nobody can read. And an agreement translated without its variations describes an arrangement that no longer applies.
Entity names, and consistency across a bundle
Party names are legal identifiers. They are rendered as registered rather than translated, and the legal form stays as it is — a GmbH is not converted into a Pty Ltd, because they are different creatures under different laws.
Where the contract sits in a bundle alongside company registration documents, financial statements or tax records, every one of those will name the same entities. Order them together and supply the entity name spellings, so the bundle is internally consistent.
Figures, currencies and dates
Amounts stay in the original currency and formatting, with no conversion. Where a figure appears in both words and numerals and they differ, both are rendered — that discrepancy is a real and potentially significant feature of the document.
Dates are rendered as written rather than converted to Australian convention, and payment periods, notice periods and deadlines are reproduced as stated rather than recalculated.
Confidentiality
Commercial contracts carry pricing, margins, customer lists and sometimes trade secrets.
Use a proper upload rather than email, ask about retention and deletion before sending, and send only the documents actually required. Where an agreement contains a confidentiality clause restricting disclosure, check what it permits before providing the document to a third party for translation — that is a question worth two minutes of a lawyer's time.
Where these come up
Commercial contracts are translated for business and investment applications, sponsorship matters where a business relationship must be evidenced, procurement and due diligence, and litigation. They also appear in personal matters where a self-employed person is evidencing their business, alongside the document set covered in our guide to certified translation for a partner visa.
Before you order
Find the prevailing-language clause. Gather the complete instrument including every annexure and variation. Supply a glossary or prior translations if you have them, and fix the entity name spellings.
Home Affairs publishes its document and translation requirements and NAATI its practitioner identification guidance; both are updated over time. You can upload a full contract set to LodgeHQ Translate for a fixed-price quote across the instrument. Nothing here is legal advice.