The standard M&A due diligence checklist is a request list. It tells a buyer's counsel what to ask the seller for: three years of audited financials, a schedule of material contracts, employment agreements for key personnel, IP ownership documentation, pending litigation disclosures, tax returns, and so on. The checklist is about coverage — making sure you've asked for everything.
What the checklist doesn't cover is verification: once the documents arrive in the data room, do they actually support the financial representations the seller has made? A seller can respond to every item on the checklist with real documents that are nonetheless inconsistent with the purchase price model. Checklist completion is not the same as diligence completion.
The four types of discrepancies that verification finds
1. Amount mismatches
The most common finding in document-level verification is an amount mismatch: a ledger line item that doesn't match its supporting document. This happens for several reasons. The ledger might record a net amount while the invoice shows gross. The ledger entry might include an accrual that the invoice doesn't reflect. Or the amounts are simply wrong — either in the ledger or in the document — and no one caught it during the seller's preparation.
Amount mismatches under $10,000 are often written off as immaterial. The problem is that systematic amount mismatches in the same category — say, all transportation expenses are consistently 3% lower in the ledger than in the underlying invoices — can indicate a pattern of misclassification that has material EBITDA implications.
2. Date inconsistencies
Date inconsistencies are subtler but often more significant. An invoice dated December 28th that appears in the January ledger might represent legitimate accrual timing. Or it might represent a revenue recognition decision that isn't consistently applied across periods. The same pattern appearing in multiple documents around fiscal year-end is a flag worth escalating.
3. Missing supporting documents
Some of the most important findings from document verification aren't about what's in the documents — they're about what isn't there. A ledger line item that can't be traced to any supporting document in the data room is either an undisclosed transaction, a mis-filed document, or a fabricated entry. The seller's response to a missing-document request tells you a lot about their diligence preparation quality.
In a typical mid-market deal, systematic document verification finds missing supporting documents for 3–8% of ledger line items. Most resolve to mis-filed documents in the VDR. About 10% of gaps represent transactions that require further explanation.
4. Counterparty name variation
Vendor and customer names in a financial ledger are rarely entered consistently. 'Accenture LLP,' 'Accenture Federal Services,' and 'ACN Consulting' might all refer to the same entity — or they might not. Document verification against invoices and contracts surfaces cases where vendor name variation masks concentration risk: a company that appears to have 40 vendors might have 12 when you normalize for naming inconsistency.
Where standard checklists stop short
The standard due diligence checklist operates at the document level: was this category of document provided? Document verification operates at the transaction level: does this specific entry in the financial statements have verifiable support? These are different questions, and most deal teams conflate them because answering the second question at scale is genuinely hard.
- —Checklist: 'Were three years of audited financials provided?' — Verification: 'Do the ledger entries in those financials match the supporting documents in the room?'
- —Checklist: 'Were material vendor contracts provided?' — Verification: 'Are the contracted rates consistent with the amounts on the corresponding invoices?'
- —Checklist: 'Were customer revenue schedules provided?' — Verification: 'Do the revenue figures in the schedule match the invoices and bank deposits in the room?'
Building verification into the checklist process
The practical challenge is that verification at scale requires either a lot of analyst time or a systematic extraction and matching approach. For deals where the data room contains fewer than 100 documents, manual verification is manageable. For deals with 300+ documents and ledgers with thousands of rows, manual verification is where things break down.
Automated reconciliation changes the economics. When extraction and matching run in minutes rather than days, it becomes feasible to run verification passes throughout the diligence process — not just at the end. That means discrepancies surface earlier, when sellers can still respond during the live diligence period, rather than post-LOI when the leverage dynamic has shifted.
What a complete diligence process looks like
A complete diligence process runs both checklist completion and document verification in parallel. The checklist tracks what's been received. Verification tracks whether what's been received actually supports the representations. The output is a two-dimensional view: documents received vs. documents verified — and the gap between them is where the most material findings live.
If you're only running a checklist without verification, you know you have the documents. You don't know what they say — or whether they agree with each other.