TL;DR: ERP. Excel. BI. Planning software. Four layers of technology. Still two weeks to build a board pack. The paradox of the over-tooled, under-informed finance function, and what it means for the CFO trying to lead strategically.
There is a conversation that happens in finance leadership teams with striking regularity. Someone notes that the function is better equipped than it has ever been. The ERP is modern and integrated. A BI tool is live and accessible to the whole business. A planning platform handles the budget. The team is capable and committed.
And the board pack still takes two weeks. The variance explanation still arrives in week three of the new month. The ad hoc question from the CEO still takes three days to answer properly.
McKinsey's CFO research found that sixty percent of finance leaders now cite strategic planning as a top priority, up from thirty-eight percent in 2023. The ambition is clearly there. The gap between that ambition and what the current workflow produces is the subject of this post.
More tools have not produced more understanding. The question is why, and what would actually change it.
The ERP Was Not Built for Understanding
The ERP is the foundation of the finance function, and rightly so. It records transactions, maintains the audit trail, produces the actuals, and enforces the controls that make financial reporting reliable. For what it was designed to do, it does it well.
What it was not designed to do is interpret. The ERP tells you what happened with precision. It does not tell you what it means. When revenue in a product line is fifteen percent below plan, the ERP confirms the number. The explanation of why, and the implication for what the business should do next, requires work that happens entirely outside the system.
This is not a criticism of ERP design. It is a description of the boundary the system was built to operate within. The problem arises when finance teams expect the ERP to be the source of understanding as well as the source of record. It was designed for the latter. The former requires something it was never architected to provide.
The Dashboard Made Data Prettier, Not Smarter
The BI tool or dashboard layer was supposed to be the insight layer. Real-time data, accessible to everyone, in a visual format that made patterns obvious. For a period in the early 2010s, the dashboard was positioned as the tool that would finally make finance genuinely real-time and self-service.
Gartner forecast that by 2026, more than seventy percent of finance organisations would move away from spreadsheets as their primary planning tool. The dashboard was part of that transition. And dashboards have delivered real value: report distribution that once required manual effort now happens automatically, and data that once required a finance analyst to surface is accessible to business leaders on demand.
But a dashboard is still a display system. It shows the current state of the data in a more accessible format. It does not build an argument from that data. It does not surface signals that have not been explicitly configured as alerts. It does not explain why the metric on screen moved or what the movement implies for the decision the business is trying to make.
The one hundred percent of FP&A professionals who still use spreadsheets at least quarterly according to AFP's 2025 research are not failing to adopt the BI tool. They are completing the analysis that the BI tool cannot do. The dashboard shows the picture. Excel builds the argument. Both are still required because the layer between the two, the reasoning layer, has not been built.
The Planning Tool Solved the Wrong Problem
The planning tool was the most significant finance technology investment of the 2010s for mid-market companies. Moving from sprawling Excel workbooks to a purpose-built planning platform genuinely improved the budgeting process. Consolidation that took days became automatic. Driver-based models that were fragile in Excel became structurally sound. Scenario modelling that required rebuilding from scratch became parameterised and repeatable.
These are real improvements. They solved a real problem. And Gartner's 2024 research still found that only fifteen percent of FP&A teams operate with a sustainable delivery model.
The planning tool improved the forecasting and budgeting process. It did not change the fundamental architecture of how finance relates to business decisions. Budgets are produced faster. Forecasts are updated more easily. The gap between a financial outcome and the business understanding it implies remains. The planning tool produces better projections. It does not produce better decisions, because producing decisions requires a layer of reasoning that sits above the projection.
The Excel Persistence Problem
The persistence of Excel in finance after thirty years of alternatives is the most telling evidence that the problem is structural rather than a matter of tool quality.
AFP's 2025 research found that one hundred percent of FP&A professionals use spreadsheets at least quarterly. The planning platform has been in place for years. The ERP is modern. Excel persists because every tool in the stack has a gap at its output boundary that only Excel, in the existing workflow, can fill.
The ERP produces data. Excel models it. The BI tool displays the model output. The planning tool structures the budget. Excel sits between all of them because it is the only tool in the stack designed to let a skilled analyst build an arbitrary argument from arbitrary data in real time.
That is not a failure of Excel. It is evidence that the analytical layer, the place where data becomes understanding, has not been replaced. Every other layer in the stack has evolved. The analytical layer is still a spreadsheet. And as long as that is true, the overhead of feeding Excel, reconciling its outputs, maintaining its formulas, and managing its versions will consume the majority of finance capacity that should be going to interpretation and direction.
Why the Investment Has Not Changed the Output
The cumulative picture is clear. Four layers of technology, each genuinely improved over the prior generation, and the strategic output of the finance function has not changed proportionally.
The reason is specific: none of the four layers was designed to reason. The ERP records. The dashboard displays. The planning tool projects. Excel models. None of them watches the business continuously, surfaces signals before they are asked about, carries context from one decision to the next, or connects a financial movement to the commercial question it implies.
Gartner's 2024 research identified the concept of capability diffusion as the model for high-performing FP&A functions: technology as the default channel for decision support, with in-person finance leadership reserved for the most complex and novel decisions. That model requires a layer of technology that provides genuine decision support, not just data, visualisation, or projection.
The four layers that most mid-market finance functions run on do not include that layer. They were not built for it. Investing more in any of the four existing layers produces improvements within each layer. It does not add the layer that is missing.
What the Missing Layer Actually Is
The layer that produces the strategic output the business needs from finance is not a better version of any existing tool. It is a reasoning layer: a system designed to watch actuals as they move, interpret what is driving the movement, and connect internal financial signals to the external market forces shaping them. Competitor pricing shifts, input cost indices, demand signals, and macro indicators are the context that explains why internal performance moves the way it does. This combination of internal and external intelligence is what Uptio refers to as Signals. It surfaces what matters before being asked, and carries context forward so that understanding compounds rather than resets.
This is what the phrase AI-native FP&A means when it is used precisely rather than as a marketing term. Not AI added to the existing stack as a feature. A layer designed from the ground up around the goal of turning financial signals into understanding that supports decisions.
When that layer exists, the board pack does not take two weeks because explanation is not assembled from scratch at month-end. The variance commentary does not arrive in week three because the variance was being interpreted in week two. The ad hoc question does not take three days because the data has been continuously watched and contextualised rather than sitting in a system waiting to be extracted.
The ERP investment was not wasted. It is the transactional foundation that every finance function needs and will continue to need. The dashboards and planning platforms that sit above it are the tools Uptio is built to replace over time, not to complement. What has been missing is not another layer on the stack. It is a fundamentally different kind of system: one that reasons over data rather than displaying or projecting it.
That is the gap. And in 2026, it is the gap that is closing.
Uptio connects to the ERP and transactional source systems, watches actuals and external market signals continuously, and produces the understanding the business needs from finance. Learn how Uptio works.