Parallel columns in one DOCX: the Russian side for the bank and customs, the English side for your foreign partner. Both texts are equally binding.
You do not order the English version separately — it is built together with the Russian one
Details of both parties, subject of the deal, delivery and payment terms. Goods can be described in English yourself, or left to the built-in translation.
By card online. Right after payment the system assembles the document with both columns.
Opens in Word, LibreOffice and Google Docs. The columns are laid out as a table, so editing one side does not break the other.
The set of clauses changes with the type: goods come with a specification, services with an acceptance act
Bringing products into Russia. The Russian column goes to the bank and customs, the English one to the supplier.
Shipping products out of Russia. The buyer needs the English column, the bank the Russian one.
A foreign contractor: development, consulting, engineering. An acceptance act instead of a specification.
A Russian contractor and a foreign client. Acceptance act and rights to the result of the work.
Translating a Russian contract and drafting a bilingual one are different tasks with different results
Every clause appears in both columns under the same number
Which text prevails, what happens if they diverge, and what the bank expects
Fill in the form, pay online and download right away. 2 990 ₽ for a document with its specification; the file is yours to edit.
A bilingual contract is a single document in which the Russian and English texts run side by side, clause against clause. It is not a translation attached to a contract — it is one signed document with two columns, and both of them are equally binding. In Russian foreign trade this is the usual form: the Russian side is needed by the bank and customs, the English side by the counterparty.
Two separate files mean two documents that can drift apart: someone edits the price in one and forgets the other. When the texts sit in one table, an edit is visible immediately, and the clause numbering is shared. It also removes the question of which version was signed — there is only one document.
HS codes, Incoterms terms, SWIFT and IBAN, and the amount in figures stay as they are in both columns: they are international notation, and translating them would create a discrepancy. Company names of the Russian party are transliterated the way they appear in payment documents, not translated word by word.
When a contract is registered with an authorised bank, the bank works with the Russian column: it is what the deal amount, the payment deadlines and the parties are read from. A document written only in English is normally returned for a Russian version to be added — which is precisely the step the bilingual format removes.
The usual route to a bilingual contract is to write the Russian text, send it to a translator and then merge the two versions into one table. The mistake appears at the last step: clauses shift, some paragraphs are left without a pair. In the builder there is no merging step at all — the document is assembled in pairs from the start, clause against clause, with the same numbering in both columns.
EN
RU