Excel: Universal Tool, Impossible CAPEX Governance
Excel is the most widely deployed corporate finance tool in the world. Its flexibility makes it a first-resort solution for any management challenge, including investment tracking. But that same flexibility is its main limitation for CAPEX governance in a multi-site group.
In a multi-entity environment, Excel-based CAPEX management systematically relies on the same compromises: each site builds its own file, with its own coding logic, its own columns, its own statuses. Group consolidation becomes a translation exercise rather than an aggregation one.
In a group of 8 sites, monthly CAPEX consolidation takes an average of 2 to 3 days of controlling work — for a result that is already partially obsolete at the time of presentation.
The 5 Structural Limitations of Excel in CAPEX Governance
1. No native decision traceability. Excel records data, not processes. Who approved this project? When? On which version of the business case? This information is outside the file by definition.
2. Commitments precede payments by 6 to 18 months. Excel does not distinguish between a decided project and one merely considered. The real commitment — the firm decision — is invisible until the first disbursement.
3. Multi-version consolidation is a permanent source of error. CAPEX_2024_v7_FINAL_real.xlsx: every finance organisation knows this file name. Version management in a shared environment is unmanageable beyond 3 or 4 contributors.
4. Business cases are not comparable. Without a mandated template, each site director argues in their own way. The investment committee arbitrates on form as much as substance.
5. Audit trail is impossible to reconstruct. In the event of a statutory audit or internal review, finding who approved what, in which file version, takes several days — when it is even possible.
At What Threshold Does Excel Become a Risk?
The question is not 'Is Excel good or bad?' but 'At what level of complexity does Excel generate more risks than it resolves?' Finance organisation observations suggest three critical thresholds.
- Beyond 3 contributing entities, consolidation becomes a systemic error risk.
- Beyond 15 to 20 simultaneous projects, tracking statuses and versions exceeds what a file can reasonably handle.
- Once the annual CAPEX budget exceeds €5M, the lack of commitment traceability constitutes a measurable financial risk.
Beyond these thresholds, overruns are no longer accidents but structural inevitabilities.
What Multi-Site Groups Need in 2025
The needs of multi-site group finance departments converge on four requirements that Excel cannot structurally satisfy.
- A single repository, shared in real time across all entities, with no version management.
- Configurable approval workflows aligned with the group's financial delegation matrix.
- Commitment capture at the decision date — not the disbursement date.
- Automated group consolidated reporting, available on demand for the executive committee.
These four needs define exactly the scope of a dedicated CAPEX governance solution. Not to replace the ERP, but to occupy the decision-making layer that precedes the ERP.
The Transition: Moving from Excel to a Dedicated Tool Without Disruption
The main fear of finance teams when migrating from Excel is disruption of the existing process. This fear is legitimate — and it largely determines project success.
The recommended approach is progressive migration: CAPEXIA is first deployed in parallel with Excel on a limited scope (one or two pilot entities, one budget cycle). Teams validate the process, adopt the tool, and the full switch occurs in the following cycle. Full deployment takes 4 to 6 weeks.
The goal is not to remove Excel from the finance IS — it is to restore its natural role as an ad hoc analysis tool, by freeing CAPEX management from a dependency that generates structural risks.