Only 18% of organisations can run planning scenarios in under one day — a practical marker of FP&A agility (Source: FP&A Trends, Agile FP&A / scenario turnaround data). The remaining majority spend the bulk of their time on manual data gathering, reconciliation, and formatting reports that arrive too late to influence decisions.
Meanwhile, 58% of CFOs have increased their focus on FP&A capabilities since last year, according to PwC. The investment is growing. The returns are not.
The gap between intent and outcome is not a people problem or a technology problem. It is an architectural failure.
The Five Structural Failures
1. Data Unreliability at the Foundation
The 2025 AFP FP&A Benchmarking Survey identifies data quality as the single greatest obstacle to FP&A effectiveness. Sixty-one percent of respondents cite a lack of data reliability as their primary challenge, while 60% report inaccessible data as a critical barrier.
When the foundation is unreliable, everything built on top of it — forecasts, scenarios, variance analyses — inherits that unreliability. Yet most organisations attempt to solve this by adding new tools on top of fragmented data, rather than investing in the underlying data architecture.
The fix begins with a data governance programme that establishes consistent definitions, validated sources, and clear ownership. Before investing in advanced analytics or AI, ensure the planning data is trustworthy.
2. Spreadsheet Dependency
Despite decades of enterprise software development, spreadsheets remain the dominant planning tool. The AFP Benchmarking Survey found that 96% of FP&A professionals use spreadsheets for planning, and 93% use them for reporting on a daily or weekly basis.
Spreadsheets are flexible. They are also unauditable, error-prone, and incapable of supporting the real-time, multi-dimensional analysis that modern enterprises require. A single formula error in a consolidated planning model can cascade through every downstream output without detection.
The Empyrean 2025 Bank Risk and Performance Survey confirms this: 52% of financial institutions still depend on spreadsheets for core reporting — a dependency that inhibits rapid response to volatile markets and regulatory changes.
This is not a call to eliminate spreadsheets overnight. It is a call to recognise that a planning architecture built primarily on spreadsheets has a structural ceiling that no amount of skilled analysts can overcome.
3. Siloed Planning Across Functions
FP&A cannot plan in isolation. Sales maintains its own forecast. Operations tracks capacity constraints independently. HR manages headcount plans in a separate system. Finance consolidates a budget that reconciles with none of them.
While 74% of institutions report collaborating with shared assumptions between asset-liability management and financial planning, only one in three have the tools and processes to fully integrate cross-functional planning. The result is a budget that reflects political negotiation rather than strategic reality.
Integrated business planning — where operational, commercial, and financial plans converge around shared assumptions and a single version of the truth — remains the goal. Few organisations have achieved it. Those that have report significantly faster planning cycles and more accurate forecasts.
4. Scenario Planning That Cannot Keep Pace
Only 18% of organisations can run planning scenarios in under one day. Nearly half take longer or cannot run scenarios at all.
In an environment where interest rates, supply chains, and geopolitical conditions shift monthly, a planning function that requires weeks to model a new scenario is not a planning function. It is a reporting function with aspirations.
Effective scenario planning requires three elements: a flexible data model that supports rapid reconfiguration, pre-defined scenario frameworks that bracket the range of plausible outcomes, and decision protocols that specify what actions each scenario triggers.
5. Reporting Instead of Decision Support
The most fundamental failure is one of purpose. Most FP&A functions are designed to produce reports. Reports describe what happened. They rarely prescribe what to do.
When the primary output of the planning function is a monthly variance report that arrives two weeks after month-end, the function is not supporting decisions — it is documenting history. By the time leadership reviews the analysis, the window for corrective action has closed.
The shift from reporting to decision support requires reorienting the entire planning architecture around the decisions it must enable. What capital allocation choices does the board face this quarter? What operational trade-offs do business unit leaders navigate this week? The planning process should flow backward from these decision points.
Rebuilding the Framework
The path from a reporting-oriented FP&A function to a decision-support function requires three structural shifts:
**From data collection to data governance.** Invest in the reliability and accessibility of planning data before investing in the tools that consume it. Establish a shared semantic layer with consistent definitions across functions.
**From periodic cycles to continuous planning.** Replace the annual budgeting marathon with a rolling forecast process that updates assumptions monthly and reallocates resources quarterly. The goal is not a perfect annual plan — it is a planning capability that adapts faster than the environment changes.
**From variance analysis to forward-looking intelligence.** Supplement backward-looking performance reports with leading indicators, scenario analyses, and decision-trigger frameworks that enable proactive management.
These are not incremental improvements. They represent a fundamental redesign of how the finance function creates value for the enterprise. The 18% of FP&A teams that have made this transition are not working harder. They are working on a different architecture.