HOLDco

Mismatched numbers across a data room don't have to mean fraud — but they can still kill a deal. This episode breaks down cross-document reconciliation: why it must be deliberate, how to build a master map, and where the gaps that cost buyers real money actually hide.

Show Notes

A data room full of organized, permissioned documents is not the same thing as a data room full of consistent ones. This episode of HoldCo tackles the discipline that separates clean closings from late-stage surprises: cross-document reconciliation — the systematic process of identifying every place where figures, definitions, or contractual terms appear in more than one document and confirming they actually agree.

The episode walks through a practical, step-by-step framework for running reconciliation deliberately rather than hoping it emerges as a byproduct of careful reading. Key topics include:

  • Why mismatches are structural, not suspicious: Auditors, management teams, and bankers each produce numbers for different purposes using different definitions — and none of them are wrong in their own context.
  • Building a master reconciliation map before reading begins: Identifying every metric likely to appear across multiple documents — revenue, EBITDA, headcount, ARR, debt, working capital, and key contract terms — and turning that list into a live matrix the whole team populates in real time. Tools that support cross-document reconciliation can flag these inconsistencies automatically and accelerate the process.
  • A worked revenue example: How the same fiscal year can yield three different revenue figures — each defensible — and why the buyer's real question is which figure underpins the purchase price versus which figure is warranted in the SPA.
  • Chasing add-backs to their source: Why every EBITDA add-back in the model must be traced to the exact line item in the management or statutory accounts — and how mismatches in classification quietly distort the margin you underwrote.
  • Contract summaries versus underlying agreements: Legal schedule abstractions introduce error; the reconciliation discipline is to personally verify every material contract above a defined threshold, and document the rationale for relying on summaries below it. AI document intelligence can surface relevant clauses across large contract sets far faster than manual review.
  • Process mechanics that prevent workstream silos: Assigning row-level ownership on the reconciliation map, reviewing it as a standing agenda item, and ensuring the financial and legal teams are working from the same numbers before the IC memo is drafted.

The episode closes with a reminder that the data room is not a single source of truth — it is a conversation between documents that were never designed to agree. The teams that treat inconsistency as information, rather than noise, are the ones who reach closing with confidence. For a deeper look at how structured diligence workflows support this kind of rigour, agentic due diligence is worth exploring. If this episode prompted questions about deal structure more broadly, the previous episode, Capital Structure: The Hidden Lever That Makes or Breaks a Deal, covers the financial architecture decisions that shape what you are actually buying.

VDR

What is HOLDco?

Dynamic holding company podcast, covering varying topics on M&A, marketing, software engineering and deal strategies. We discuss topics and provide details of our various holdings at HOLD.co.