SAP IBP was meant to put an end to spreadsheet driven planning.
It promised cloud based workflows, cross functional alignment, scenario modeling, and tighter integration with your SAP environment. On paper, it checked every box.
Yet many organizations find themselves asking the same frustrating question.
Why is my team still exporting data to Excel every week?
Despite the investment, training, and long implementation cycles, planning often feels no more agile or intuitive than before. In many cases, business users create workarounds just to keep decisions moving. Planning continues outside the system while IBP quietly runs in the background.
This is not uncommon. And it is not a failure of your team.
It is a signal that something deeper is missing.
Let’s explore why this happens, what it is costing your organization, and how leaders can address it.
When planners return to Excel, it is rarely because they prefer spreadsheets.
It is because the system does not support how decisions actually get made.
Common frustrations we hear include:
In response, planners do what they have always done. They export the data and work offline where they can think freely.
According to Gartner, 74 percent of supply chain professionals still rely on spreadsheets for core planning processes even after implementing enterprise planning tools.
At first glance, this can sound like a technology failure. In reality, it points to something more nuanced.
Most planning software does not fail because it lacks functionality. It struggles because it was not designed to support how decisions are actually made day to day.
When planning tools function primarily as data repositories or reporting systems, teams still need somewhere to test assumptions, explore options, and understand tradeoffs. That work naturally falls back to Excel.
IBP may exist in the system landscape, but spreadsheets often become the environment where decisions are shaped.
This is exactly where advanced planning and scheduling tools play a critical role.
When planning platforms are designed to support real time scenarios, constraint based logic, and cross functional decision making, they eliminate the need for offline analysis. Planners stay in the system because it enables thinking, not just reporting.
The issue is not that planning technology does not work. It is that not all planning technology is built to enable decision making at the speed and complexity modern supply chains require.
When Excel becomes the true planning environment, risk quietly builds.
Spreadsheets create:
Over time, planning becomes slower rather than faster. Meetings focus on whose numbers are right instead of what actions should be taken.
This fragmentation has real financial impact. McKinsey reports that organizations operating with disconnected or manual planning environments experience significantly higher working capital levels and more frequent supply and demand mismatches.
The challenge is not visibility alone. It is decision confidence.
When leaders do not trust the plan, execution suffers.
When planners default to Excel, it is often described as a change management problem.
In reality, it is usually a design problem.
Planning systems must support the way planners think and work. That includes the ability to:
SAP IBP is powerful, but it is built around structured data models and predefined workflows. That rigidity can make it difficult for business users to respond quickly when conditions change.
As a result, planners turn to tools that give them speed and flexibility, even if those tools introduce risk.
Excel remains familiar not because it is ideal, but because it allows people to think.
The answer is not to replace your ERP or discard your existing investment.
The better question is this.
What role should IBP play, and what capabilities are still missing?
Modern planning environments are designed to complement ERP systems rather than compete with them. They focus on enabling decisions, not just managing data.
A stronger planning experience typically includes:
When planning systems are intuitive and responsive, the need for shadow spreadsheets disappears naturally.
Planners stay in the system because it helps them do their jobs better.
If your organization is still planning in Excel after implementing SAP IBP, it is not a failure.
It is feedback.
It signals that the planning environment is not delivering the agility, usability, or decision support your business now expects.
No amount of training will turn a rigid system into a flexible one. And no amount of customization will change how people naturally think through decisions.
At Scott Sheldon, we help organizations preserve the value of their SAP environment while strengthening the planning capabilities needed to support growth, volatility, and faster decision making.
If your planners are still living in spreadsheets, it may be time to rethink how planning is enabled.
Because when planning happens outside the system, the system is not truly working.
Sources
Gartner, The 2023 Supply Chain Technology User Survey
McKinsey, Risk, Resilience, and Rebalancing in Global Supply Chains, 2023
