Excel remains part of the architecture
AFP’s discussion of its 2025 benchmarking survey reports that 85% of respondents used spreadsheets alongside EPM tools. That is evidence of coexistence in the reported sample, rather than a universal adoption rate or proof that every architecture works well. [source]
Excel is not the problem. Uncontrolled planning architecture is.
Evaluate the recurring process, contributor model and required controls alongside the workbook itself.
Three useful architecture states
Keep Excel
- Few model owners
- Limited recurring process
- Manageable dependencies
- Small scenario burden
- Manual work is proportionate
Strengthen the architecture
- Repeated planning cycles
- Growing collaboration
- Several linked models
- More versions and scenarios
- Repeated data preparation
- Key-person dependency
Evaluate governed planning
- Many entities and contributors
- Continuous forecasting
- Complex model dependencies
- Formal workflow and approvals
- Permissions, lineage and audit trail
- Automated integrations needed
Editorial diagnostic framework. These are cumulative indicators, not numerical thresholds or a software recommendation.
Hybrid is a legitimate choice
A governed model can coexist with spreadsheet exploration, one-off analysis or a familiar planning interface. The useful boundary is which calculations, data definitions and controls are authoritative.
Datarails describes preserving Excel models with centralized FP&A data and workflows; Jedox documents a shared model with an Excel interface and Add-in. These examples show different approaches to coexistence, without establishing a preferred product. [source] [source]
For any hybrid design, test import and write-back rules, scenario identity, calculation ownership, version control and how source changes reach downstream outputs.
Two more ways to retain Excel
Loyos bi: model and report handoffs
The Helpcenter documents an Excel plan-input workbook; release notes also establish dynamic formula calculation in FMS. Agree which logic remains in Excel and which runs in the service. [source] [source]
Read the Loyos bi research profileAllevo: Excel as a SAP frontend
KERN documents Junan as an Excel frontend for its SAP extension, with bidirectional exchange. This raises a different governance question: how are SAP objects, calculation responsibilities and released plan values controlled? [source]
Read the KERN Allevo research profileCommon validation questions: Where do the rules calculate? Where are approved values stored? Who can change a formula or scenario? How does a downstream report identify the released version?
A neutral robustness check
- Inventory the models, recurring transfers and financial outputs.
- Identify hidden assumptions, external links and duplicated logic.
- Establish who can change inputs, formulas and released versions.
- Measure the effort required to reconcile and rerun a scenario.
- Check traceability, handover and key-person dependence.
- Choose the smallest architecture change that addresses the observed constraints.
Sources & research notes
The guide builds on the supplied Deep Research Report and the supplementary Loyos bi / Allevo research reviewed on 11 October 2026. The references below identify this page’s evidence. Vendor documentation establishes a stated capability; implementation fit and outcomes require separate validation. Editorial frameworks and illustrations are identified in the text.
- AFP: Why Aren’t FP&A Teams Using the EPM Tools They Bought? ↗Professional association; 2025 benchmarking discussion · 5 May 2025 · Reviewed 11 October 2026
- Datarails: Excel-native FP&A ↗Official vendor documentation · Publication/update date not stated · Reviewed 11 October 2026
- Jedox: Financial Planning & Analysis ↗Official vendor documentation · Publication/update date not stated · Reviewed 11 October 2026
- Loyos bi: June 2026 release notes ↗Official release notes · June 2026 · Reviewed 11 October 2026Formula calculation for dynamic-planning type M.4 is documented. This is evidence of calculation logic, not a complete specification of an industrial planning engine.
- KERN: The technology behind Allevo ↗Official vendor documentation · Publication/update date not stated · Reviewed 11 October 2026ABAP architecture, Junan Excel and Koodai browser frontends, bidirectional exchange, permissions and web infrastructure.
Help improve this research.
Send the claim, product or release, a dated source and the correction you propose.