The Verification Gap: Why Translated Summaries Misprice Cross-Border European Deals

In a cross-border deal, the risk is not that a number was translated. It is that nobody checked the translation against the original. A German footnote becomes a clean English sentence, an Italian working-capital note becomes a tidy summary, and the version that ends up pricing the deal is the one furthest from the source. The gap between the original document and the summary is where seven-figure mistakes live, and it is exactly the gap a busy buyer is least able to police.

Most cross-border buyers solve the easy half of this problem and skip the hard half. They get the documents translated, read the summary, and feel informed. The value is in the second step almost nobody takes: verifying the handful of numbers the decision rests on against the original-language line they came from.

Language access is the easy part

It is tempting to treat multilingual diligence as a translation problem. Get the German CIM read in German, the French contracts read in French, and the job feels done. But translation is the beginning, not the end. Once a figure is in English it still needs verifying against its source, and that is the step, under time pressure, that quietly disappears. A footnote gets paraphrased into confident English. A working-capital adjustment gets summarised in a way that is technically reasonable and subtly wrong. The summary reads clean. The error is invisible because the reader never returns to the original line.

Why cross-border deals make it worse

This is sharper in Europe than almost anywhere, because the deals are genuinely multilingual in a way many markets are not. A buyer might look at a German manufacturer one month and a French services business the next, each arriving in its own language, with its own accounting conventions and its own footnote culture. And the people one step removed from the documents, the investors and the investment committee, sit even further from the source language than the buyer does. They see the cleanest, most summarised, most translated version of all. The further you sit from the original document, the more confident and the less checkable the number in front of you becomes.

Which numbers actually deserve a second look

You cannot re-read every line of every data room in three languages, and trying to is its own failure: it burns the exclusivity window on figures that do not matter. The discipline is narrower. Verify the handful of numbers your decision actually rests on against the original-language document.

Figure	Why it moves the deal	Check it against
Customer concentration	Sets the risk discount on the multiple	The customer schedule, in the source language
Working-capital peg	Moves the price at closing	The original financial notes, not the summary
Revenue recognition	Changes whether earnings are real	The accounting policy note in its own language
Change-of-control terms	Can un-do the deal after close	The actual assignment clause in the contract

For those, the quote should stay in its original language, so you or someone you trust can check it. If a number cannot be traced back to a specific line, it is not a number yet. It is a question.

A worked example

Consider a manufacturer in a German-speaking country. The English summary of the financials, prepared by an adviser, described a customer concentration that looked acceptable. The original German footnote, read carefully, said something narrower and more alarming: one large customer relationship was contractually softer than the headline implied. The summary was not dishonest. It was a reasonable paraphrase that lost the single qualifier that mattered. A buyer who priced the deal on the English version would have underwritten a concentration risk they never saw, and the investment committee would have approved it without ever seeing the footnote. The reconciliation is what surfaces it.

How Deal OS closes the gap

This is the discipline behind the cited-brief approach in Deal OS. It turns a data room, including documents in other languages, into a brief where every claim traces back to the exact source line it came from, with the original-language passage preserved next to the English so the number can be checked rather than trusted. Where a summary and a source disagree, it flags the contradiction with both sides cited, rather than smoothing it into a clean sentence. You can see it run on a synthetic deal in the sample brief.

Pair this with the management meeting cross-check and the M&A due diligence checklist: the checklist tells you what to verify, the management meeting is where the spoken version drifts, and the verification gap is where the translated version drifts. All three are the same discipline. Treat every summary as a claim until it traces to a source.

Frequently asked questions

What is the verification gap in due diligence? It is the step that gets skipped after a document is translated: checking the English summary against the original-language source. The translating is done; the verifying is not, because the summary is faster to read than the source.

How do I verify a translated financial summary? Identify the few figures your decision rests on, find the specific line in the original-language document that supports each one, and keep the quote in its original language so it can be checked. Numbers that cannot be traced become diligence requests.

Why is cross-border due diligence riskier than single-language diligence? Because every deal arrives in a different language with different accounting conventions, usually without a bilingual analyst to check the translation, and the investors and IC sit even further from the source than the buyer does.

What is source-language citation? It is the practice of tracing each figure back to the original-language passage it came from and preserving that passage, rather than relying only on the translated summary, so the number stays checkable.

See what a cited, contradiction-flagging brief looks like on a sample deal at Deal OS.