Excel in Due Diligence: Where Spreadsheets Break Down on Complex Engagements
Excel is the dominant tool in Transaction Services. Virtually every QoE analysis, NWC assessment, and net debt bridge is built, reviewed, and delivered in a spreadsheet. For simple engagements with a single entity, limited periods, and clean data, Excel is perfectly adequate.
The problems emerge on complex engagements where the volume of data, the number of entities, and the analytical requirements exceed what spreadsheets handle well. These are precisely the engagements where margins are already under pressure, and operational inefficiency has the largest financial impact.
Where Excel Works
Excel excels at tasks that match its core strengths:
- Ad hoc analysis: Quick calculations, pivot tables, and exploratory data analysis
- Presentation: Formatted tables and charts for client deliverables
- Flexibility: Custom formulas and structures for unique analytical requirements
- Familiarity: Every analyst knows how to use it, reducing training overhead
For a single-entity QoE engagement with 12 months of data and 200 GL accounts, Excel is efficient. The data fits in a manageable number of rows. Formulas are traceable. The file size stays reasonable.
Where Excel Breaks Down
Data Volume
A multi-entity target with five entities, 36 months of monthly data, and 500 GL accounts per entity generates 90,000 data rows before any disaggregation. Add sub-ledger detail for revenue, working capital, or cost analysis, and the row count reaches hundreds of thousands.
Excel handles this volume poorly. Files become slow. Formulas take minutes to calculate. The risk of corruption increases. Analysts waste time waiting for spreadsheets to respond rather than doing analysis.
Version Control
On a deal engagement, multiple team members work on the analysis simultaneously. The manager builds the QoE framework. Two analysts populate the data. A senior analyst works on adjustments. The partner reviews and requests changes.
Excel has no native version control. Teams rely on file naming conventions (Model_v3_final_FINAL_reviewed.xlsx) and shared drives. When two people edit the same file, changes conflict. When someone overwrites a file accidentally, work is lost. When the partner asks what changed between versions, nobody can answer quickly.
Audit Trail
Every number in a due diligence deliverable should trace back to its source. In Excel, this traceability depends on disciplined formula construction and documentation by individual analysts. There is no systematic enforcement.
Common audit trail failures in Excel-based diligence include:
- Hard-coded numbers with no link to source data
- Formulas that reference deleted or moved cells, producing errors
- Adjustments entered as manual overrides without documentation
- Inconsistent calculation approaches across workstream tabs
These issues are manageable on small engagements but become systemic on complex ones. Partners and managers spend disproportionate time in review tracing numbers back to their sources. This directly erodes margins and delays delivery. For more on this challenge, see audit trail discipline in due diligence.
Data Integrity
Excel does not validate data on input. An analyst importing a trial balance can accidentally paste data into the wrong column, miss a period, or introduce a duplicate. These errors propagate through the analysis and may not be caught until the review stage, triggering rework.
On a multi-entity engagement, the risk compounds. If Entity A's data is imported correctly but Entity B's is not, the consolidated analysis is wrong even though most of the underlying work is accurate.
Reusability
When a deal completes, the Excel workbook captures the final analysis but not the process that produced it. The mapping logic, validation rules, and analytical approaches embedded in formulas are difficult to extract and reuse on the next engagement.
This means each new deal starts from scratch (or from a template that captures structure but not knowledge). The team's institutional expertise remains locked in individuals' heads rather than being captured systematically.
The Real Cost
The inefficiencies of Excel-based due diligence are often invisible because they are distributed across the engagement. An extra 30 minutes here for data reformatting, an extra hour there for version reconciliation, an additional review cycle because hard-coded numbers could not be traced.
On a single engagement, these add up to 15 to 25 percent of total hours. At a typical team size and blended rate, that represents 20,000 to 50,000 EUR of margin erosion per deal.
Across a practice running 40 to 60 engagements per year, the cumulative impact is material.
Moving Beyond Spreadsheets
The solution is not to eliminate Excel but to remove it from the tasks where it performs worst. Data ingestion, account mapping, validation, and version control are process-oriented tasks better handled by purpose-built tools. Analysis, judgment, and presentation remain Excel's strengths.
Teams that separate the data engineering from the analytical work consistently achieve better margins, faster delivery, and higher quality. The spreadsheet remains the analyst's workspace for the work that requires human judgment. The data preparation that feeds it becomes a standardized, repeatable process.
This division of labor is not about technology preference. It is about allocating the team's most expensive resource, analyst time, to the tasks that generate the most value.