TL;DR: The modern finance stack was built to record and display. It was never built to reason. Here is the gap that sits between every dashboard and every decision, and why adding another tool to the stack does not close it.
Most mid-market finance functions run on a stack that looks something like this. An ERP for transaction processing and actuals. Excel for modelling and analysis. A BI or dashboard tool for visualisation. Possibly a dedicated planning tool for budgeting and forecasting. Four categories of technology, often representing significant investment, implemented over several years.
And yet the question that arrives most frequently from the business, the one that generates the most work and the most pressure on the finance team, is one that none of these tools answer directly. Why did this happen? What does it mean? What should we do about it?
That is not a technology gap in the conventional sense. It is a design gap. Every tool in the stack was built for a specific and well-defined purpose. The ERP was built to record. The BI tool was built to display. The planning software was built to project. None of them were built to reason.
According to McKinsey's research on the finance function of the future, CFOs should be spending the majority of their time advising the business and shaping decisions. The current stack was not designed to support that role. It was designed to support the role finance played a generation ago.
What the ERP Actually Does
The ERP is the foundation of the finance function, and it deserves to be. It records every transaction with accuracy, maintains the audit trail, enforces controls, and produces the actuals that everything else in the finance function is built on. NetSuite, SAP, Oracle, Microsoft Dynamics: these are mature, reliable, essential systems.
What they are not designed to do is interpret. An ERP records that revenue in a particular product line was fifteen percent below plan last month. It does not explain why. It records that a cost category ran three percent above budget across five consecutive months. It does not flag that the aggregate trend is material even though no individual month crossed the variance threshold. It produces the data. The human produces the understanding.
This is not a criticism of ERP design. It is a description of what ERPs were built for and what they do well. The problem arises when finance teams expect interpretation from a system that was architected around record-keeping. The ERP will never close the gap between what happened and what the business should do next, because that was never its job.
What the BI Tool Actually Does
The dashboard or BI layer is a genuine improvement on raw ERP data. Visualisation makes patterns more accessible. Drill-down capability allows analysis that would take hours in a flat export to happen in minutes. Automated report distribution means the business can access financial data without waiting for finance to produce it.
Gartner forecast that by 2026, more than seventy percent of finance organisations would move away from spreadsheets as their primary planning tool. The BI tool was supposed to be part of that transition. And for many teams, dashboards have genuinely reduced the manual reporting burden.
But a dashboard is still a display system. It shows the data in a more accessible format. It does not build the argument from that data. When the CFO looks at a dashboard showing margin compression in Q3, the dashboard confirms that the compression is happening. It does not isolate the driver, assess whether it is a trend or an anomaly, connect it to a commercial decision, or frame the trade-off the business now faces.
A hundred percent of FP&A professionals still use spreadsheets at least quarterly according to AFP's 2025 research. The persistence of Excel alongside BI tools is not a failure of adoption. It is evidence that the BI layer does not complete the analysis that finance needs to do. The model still gets built in Excel because the BI tool shows the picture and Excel builds the argument.
What the Planning Tool Actually Does
Dedicated FP&A and planning platforms represent the most recent layer in the finance stack evolution. Tools in this category, whether Anaplan, Adaptive, Pigment, or others, are designed to make budgeting and forecasting faster, more integrated, and more collaborative than Excel-based processes allow.
They deliver on those promises in meaningful ways. Budget cycles that took twelve weeks in Excel can be compressed. Scenario modelling that required rebuilding a model from scratch can be parameterised and run on demand. Driver-based planning that was theoretically possible in Excel but practically fragile becomes structurally sound.
And yet Gartner's research published in 2024 found that only fifteen percent of FP&A leaders operate with a sustainable delivery model. That figure reflects the state of the market after a decade of planning tool adoption. Teams are better equipped than they were. The shape of the problem has not fundamentally changed.
The planning tool, like every other layer in the stack, optimises a step. It makes budgeting faster. It makes scenario modelling more accessible. It does not change the fundamental architecture: data flows in, assumptions are applied, outputs flow out. The connection between those outputs and the decisions the business is trying to make still requires a human to build, every cycle, from scratch.
The Gap That No Layer Fills
Taken together, the traditional finance stack does the following reliably well. It records what happened with accuracy and auditability. It stores and surfaces that data in accessible formats. It allows assumptions to be applied to produce forward projections. It automates steps that were previously manual.
What it does not do is maintain continuous awareness of what is happening in the business as it happens, surface signals before they are asked about, carry context from one decision to the next, or connect a financial movement to the commercial question it implies.
That is not a gap in any individual tool. It is a gap in the architecture of the stack as a whole. The stack was designed around a periodic, output-oriented model of finance. Data arrives at fixed intervals. Analysis is performed. Outputs are produced. The cycle resets. This model was appropriate for a business environment where the speed of decisions matched the speed of reporting.
McKinsey's CFO survey found that sixty percent of finance leaders now cite strategic planning as a top priority, up from thirty-eight percent in 2023. That ambition requires a finance function that can operate continuously, not cyclically. The current stack was not built for that operating rhythm, and adding another tool to it does not change its fundamental architecture.
What Sits Between the Stack and the Decision
The layer that is missing from the traditional finance stack is not another tool that optimises a step. It is a reasoning layer: a system designed not to record, display, or project, but to interpret. To watch actuals as they move and build context around the movement. To ingest external market signals alongside internal data: competitor pricing, demand indicators, input cost trends, and macro signals that explain why internal performance is moving by reference to what is shifting in the environment. This combination of internal actuals and external intelligence is what Uptio refers to as Signals. To surface what matters before being asked. To carry understanding forward from one cycle to the next rather than resetting with each report.
This is what the phrase decision layer means in practice. Not an add-on to the existing stack. A replacement for the tools whose core purpose was always projection and display rather than reasoning. Uptio connects to the ERP and the transactional source systems where financial reality is recorded. The planning and BI tools that finance teams currently use to manage budgets and visualise data are the systems Uptio is designed to make redundant over time, not to sit alongside.
When the sales director asks why margin is soft, the decision layer does not start the seven-step process of extracting, reconciling, modelling, and presenting. It has been watching the relevant signals since they started moving. The context is already built. The drivers are already isolated. Finance reviews and advises rather than assembles and reports.
The stack was built to make finance reliable. A decision layer makes finance relevant in real time. Those are not the same thing, and the gap between them is precisely where the CFO's strategic role either gets created or gets crowded out by the weight of the workflow.
The Right Way to Think About This
The ERP investment was not wasted. It is the transactional foundation and it stays. What changes is everything built above it: the dashboards, the planning platforms, and the Excel models that have served as the reasoning and projection layer. Those tools were always an approximation of what finance needed. Uptio is what finance actually needs: a system that connects to source data, reasons over it continuously, and surfaces understanding rather than formatted outputs.
Uptio is the decision layer that connects to the ERP and transactional source systems, interprets actuals continuously, and produces the understanding the business needs from finance. Learn how Uptio works.