How to Translate a Business Proposal or Quotation for an International Client

A proposal is one of the few documents where a translation mistake costs you money on the day you send it. Get a sentence wrong in a company brochure and you look careless. Get a payment term wrong in a quotation and you have either given away margin or handed the buyer a reason to walk. When you translate a business proposal you are translating a commercial offer, and the parts that decide the deal are usually the parts nobody proofreads: the price table, the validity date, the delivery clause, the two lines under the signature block.

We see these documents constantly from companies that have no translation department. Someone in sales runs the file through a free tool, the output reads perfectly well, and five weeks later there is an argument about what "within 30 days" was counting from. This is a guide to the parts that break and to a review pass you can run even when nobody on your team reads the target language.

What breaks when you translate a business proposal

A proposal is two documents wearing one cover. The front half is persuasion: who you are, why the buyer should care, what problem you solve. The back half is a contract in waiting: scope, exclusions, prices, payment schedule, delivery, warranty, validity. Translation tools treat both halves identically, which is where the trouble starts. Fluent, confident output across a page of commercial terms is exactly what a non-speaker cannot audit.

The single most common failure we run into is a delivery clause that shifts its starting point. A German machinery quotation read Lieferzeit 8 Wochen ab Auftragsbestätigung — eight weeks from order confirmation. The English version came back as "delivery within 8 weeks of payment." Both sentences are grammatical. One of them moves the clock by however long the buyer takes to pay, and the supplier found out when the buyer invoked it.

The second failure zone is the price table. Tables get mangled more often than paragraphs, because the text inside a cell is short, contextless, and sometimes not text at all. A number typed as a string in one cell and stored as a number in the next behaves differently the moment a tool touches the file.

The third is quieter. Proposal language carries a register, and register does not survive a generic translation. A direct, confident English pitch can land as brusque in Japanese or as oddly informal in German. That does not lose you a contract on its own, but it does make the sender look like they did not care enough to check. Buyers notice.

Separate the binding parts from the persuasive parts

Before you send anything anywhere, split the document into two zones and give them different quality bars. It takes ten minutes and it changes what you do next.

Zone one is anything a lawyer would read: scope of work, deliverables, explicit exclusions, unit prices, totals, taxes, payment schedule, penalties, warranty period, liability cap, governing law, and the validity date of the offer. Zone two is everything else: the cover letter, the company background, the case study, the closing paragraph about looking forward to working together.

Zone one needs to be accurate, not elegant. It should be checked line by line against the source, and if the contract value is large enough to matter to your year, it should be read by a person who knows both the language and the commercial terms. Zone two needs to read naturally to a buyer in that market, which is a different skill and a lower risk.

This split also tells you where to spend money. CSA Research's long-running "Can't Read, Won't Buy" survey found that most buyers prefer information in their own language and a substantial share will not buy from content in another language at all. That research covers consumers rather than B2B procurement teams, and a technical buyer who reads good English is a different animal from a retail shopper. Still, the direction holds: sending a proposal in the buyer's language moves the conversation forward, and the cheapest way to fund that is to stop paying human-review rates for the parts of the document that are pure marketing filler. If you want the arithmetic on what those choices cost, we broke the numbers down in our guide to document translation pricing.

Prices, currencies and dates need their own pass

Numbers are the part of a proposal that a reviewer can verify without speaking a word of the target language, and they are also the part that goes wrong most often.

Decimal and thousands separators flip between locales. Written in German or Spanish convention, 1.500,00 means one thousand five hundred. Read with English conventions, the same string looks like one and a half. We have watched an Excel price list come back from a free tool with the separators normalized to the target locale in some cells and left alone in others, which is worse than either option, because the file now looks internally consistent to nobody and plausible to everybody.

Currency deserves an explicit decision rather than a default. Are you quoting in your currency or theirs? If theirs, at what rate and valid until when? A quotation in euros that says nothing about exchange rate exposure is a quotation you will renegotiate. The symbol placement also moves: 1 500,00 € in French, €1,500.00 in English.

Dates are the cheapest trap of all. 03/04/2026 is two different days depending on where the reader sits. In the validity line of an offer, that ambiguity is worth real money. Write the month as a word in both versions and the problem disappears.

Two things should not be translated. Incoterms are standardized three-letter codes published by the ICC, and EXW, FCA, DAP and CIF stay in Latin characters in every language, sometimes with a plain-language gloss beside them. Product codes, SKUs and model numbers stay untouched too. Tools translate both when nobody tells them otherwise.

Write down twenty terms before you translate anything

A glossary sounds like an agency ritual. For a proposal it is twenty minutes of work that prevents the most embarrassing category of error, which is the same concept translated three different ways in one document.

Start with the words that name your commercial reality. What you call a quotation matters: Spanish gives you presupuesto, cotización and oferta, and the one that sounds normal in Madrid can sound off in Mexico City. The same applies to the difference between an estimate, which is indicative, and a quotation, which binds you. If your source document uses those two words precisely, the translation has to keep them apart, and a generic engine will happily merge them.

Then add your product and service names, your unit of sale (per licence, per seat, per tonne, per shipment), your payment terms, the legal form of your company, and any job titles that appear in the signature block. If the client has sent you documents before, mine them. Their terminology beats yours, and matching it signals that you read what they sent.

Finally, build a short do-not-translate list: brand names, product lines, software names, internal project codenames, and anything a reader will search for online.

If you do not want to assemble this by hand, our free glossary generator will pull a bilingual term list out of a document you paste in, and you can prune it down to the twenty entries that carry commercial weight.

Keep the file editable and keep the tables intact

Work from the original file, not from a printout of it. A proposal that starts life as a DOCX and gets flattened to PDF for sending should be translated from the DOCX. Translating the PDF means reconstructing the layout afterwards, and reconstruction is where price tables lose rows.

Three places hide text that reviewers forget to scope. Headers and footers carry the offer reference number and the confidentiality line. Footnotes carry the conditions attached to a price. Text boxes and grouped shapes in a slide deck carry whatever the designer put there instead of a proper text frame. All three are frequently skipped, and a proposal with an untranslated footer looks unfinished in a way that is hard to explain to the buyer.

Then there is length. Translations out of English into German, Spanish, French or Portuguese typically run 15 to 30 percent longer. In flowing text that just means an extra page. In a price table with fixed column widths, or on a slide where the box was already tight, it means wrapped cells, shrunken fonts, and a description column that pushes the total off the visible area. Budget an hour for layout repair on any proposal with a real table in it, and check the table on screen at the size the client will actually open it.

One more practical point: send the editable file, not only the PDF, when the buyer's procurement team will paste your terms into their own template. It saves a round trip and it keeps your wording intact rather than retyped.

How to review a translated quotation when you don't speak the language

You can catch most of the expensive errors without reading the target language at all. The checks below are mechanical on purpose.

Put the two versions side by side and compare every number in sequence: unit prices, quantities, line totals, subtotal, tax, grand total, payment percentages, the validity period, the warranty duration, the delivery lead time. Then recompute the totals in the translated file. If a separator flipped, the arithmetic stops working, and that is your alarm.

Next, check that dates match and that any date written as digits in the source is written with a month name in both files. Scan for leftover source-language text, which usually survives inside tables, image captions and footers. Confirm that product codes and Incoterms are unchanged. Count the pages and the table rows.

After that, you need one human who reads the target language. Not necessarily a translator. Your distributor, your agent in that market, a colleague in the regional office, or the buyer's own contact if the relationship is friendly enough. Ask them to read exactly two things: the first page and the commercial terms page. That is a fifteen-minute favour, not a project.

A tool that returns a QA report with a quality rating helps here, because it gives a non-speaker something to point at when deciding whether a document needs more review. We wrote a longer piece on checking translation quality when nobody on your team speaks the language. The honest limit: these checks catch mechanical and terminological errors reliably. They do not tell you whether the pitch persuades anyone. For that you still need a reader in the market.

A sequence you can run on the next quotation

Here is the order we would use on a proposal going out this week.

1. Open the original DOCX, XLSX or PPTX rather than the PDF.
2. Mark the binding zone: scope, exclusions, prices, payment, delivery, warranty, liability, validity.
3. Write a twenty-line glossary plus a do-not-translate list covering product names, codes and Incoterms.
4. Decide the currency, the rate and the validity date before translation, not after.
5. Rewrite every digit-only date as a date with a month name in the source file.
6. Translate, then run the number-by-number comparison and recompute the totals.
7. Fix the table and slide layout for text expansion.
8. Send the first page and the terms page to one reader in the target market.

If you would rather not stitch this together from several tools, SnapIntel handles the middle of it: you upload the DOCX, XLSX or PPTX, review the glossary and the translation instructions before anything runs, and get back the same file type plus a QA report and a quality rating you can use as the input to step 8. There is a one-time trial of 5,000 words over seven days with no card required, which is roughly a proposal and a price list, so you can test the sequence on a real document before deciding anything. You can read more at snapintel.io.

The single change worth making first, if you only make one: move the commercial terms out of the "translate the whole file" bucket and give them a separate review. That one page is where the money is, and it is short enough that checking it properly costs almost nothing.