Most finance teams believe SAP gives them a complete view of their CapEx. They have project reports, they have visibility into budgets, actuals, and commitments. On paper, it looks like everything needed to forecast capital spend is already in place.

And for many finance teams, that assumption feels reasonable. SAP is the system of record for capital projects. It underpins financial control, supports reporting, and provides the foundation for project portfolio management. With the right reports, dashboards, and analytics, it should also provide clear project portfolio visibility across the organization.

But that confidence starts to break down when a different question is asked.

Not “what have we spent?”
But “what are we actually going to spend?”

When CFOs and treasury teams need to understand future cash outflows, the answers are far less clear. Because while SAP is highly effective at reporting what has been incurred, it does not provide a reliable view of what will actually be paid, in cash terms, and when.

This isn’t a reporting gap. It’s a structural limitation in how SAP captures and represents project data. In this blog, we’ll break down exactly why SAP falls short and what’s actually required to produce a reliable CapEx cashflow forecast.

A CapEx Cashflow Forecast Requires more than SAP Data

A reliable CapEx cashflow forecast cannot be built from a single system. It requires combining multiple layers of capital activity across the lifecycle.

A true view of future capital spend must include:

• planned projects that have not yet entered SAP
• approved projects that have not started
• in-flight projects currently being executed
• carry-forward projects from prior periods
• future pipeline demand that is not yet committed

This is the reality of capital budgeting. Decisions are not made on projects that already exist in SAP. They are made on a portfolio of investments at different levels of maturity, each with different levels of certainty, timing, and financial impact.

And this is where the gap begins. SAP only contains a subset of this picture, primarily projects that have already been approved, structured, and committed for execution.

SAP starts at execution. CapEx forecasting starts long before that.

Why SAP Falls Short on CapEx Cashflow Forecasting

1. If It’s not in SAP yet, It’s Not in Your Cashflow Forecast

SAP can only report on what exists within it. If a project has not been created, approved, and structured in SAP, it does not appear in any report, forecast, or projection.

But that’s not how capital decisions are made.

Early-stage demand and pipeline activity sit outside SAP, in spreadsheets, approval workflows, and disconnected planning tools. This is where projects are evaluated, prioritized, and refined before they ever reach execution.

This is the gap between budgeting vs planning. Planning happens before SAP. Budgeting and execution happen within it.

The result is that your “forecast” is built on a partial dataset, one that excludes a significant portion of future capital spend. What appears to be a complete forecast is missing most of the pipeline that will ultimately drive cash outflows.

2.  SAP Tracks Cost, Not Cash Timing

SAP is highly effective at capturing financial activity. But what it captures is not what treasury needs. Project reporting in SAP is built around:

• actuals
• commitments
• accrual-based accounting

This supports financial control and external reporting. But it does not provide a reliable view of cash. CapEx decisions depend on something different:

• when cash will be paid
• how payments are structured
• how funding requirements evolve over time

This is the difference between an incurred cost and a cash outflow.

A Capital Expenditure Budget may show when costs are expected to be recognized. But it does not show when money will leave the business. And in practice, those two timelines rarely align.

• Milestone-based contracts create uneven payment profiles
• Deposits shift cash forward ahead of delivery
• Delayed invoicing pushes payments into later periods
• Payment terms may extend to the following quarter
• Lease structures distribute cash over time

The result is a consistent mismatch between what is reported and what is paid. Cash flow is not the same as incurred cost, and SAP is not designed to bridge that gap.

3.  Your Cashflow Forecast Stops Where SAP Starts

SAP provides a clear view of what has been committed and what is currently being executed. But capital spend does not follow a fixed path; projects are delayed, timelines shift, funding is reallocated and priorities change.

A reliable cashflow forecast must account for:

• projects being rescheduled
• budgets being rephased across years
• investment decisions being deferred or accelerated

SAP reflects the current state of execution, but not how that state will evolve. This is the challenge in capital investment budgeting. Forecasting is not just about what exists today, it is about how the portfolio will change tomorrow. And that movement, across time, priorities, and funding, sits outside SAP.

4. Forcing Cashflow Forecasting into SAP Creates More Noise, Not Accuracy

Recognizing these gaps, SAP teams often try to solve the problem within SAP itself. They:

• create projects earlier than necessary
• push planning activities into SAP structures
• attempt to model future demand within execution frameworks

On the surface, this appears to bring everything into a single system. In practice, it creates new problems:

• master data becomes bloated with speculative or inactive projects
• forecasts require constant rework as priorities shift
• planning loses flexibility and becomes constrained by rigid structures

Instead of improving accuracy, this approach introduces noise. Trying to turn SAP into a planning system creates more problems than it solves.

The Problem Isn’t SAP, It’s Where Cashflow Data Exists

At this point, the issue is often framed as a limitation of SAP, but that misses the real problem.

SAP is designed to manage and control project execution. It performs that role extremely well. The challenge is not what SAP does, but what a complete cashflow forecast actually requires.

A reliable CapEx cashflow forecast does not come from a single stage of the lifecycle. It requires connecting multiple layers of capital activity that exist in different places:

• planning activity before projects are approved
• the approval pipeline as investments are evaluated and prioritized
• execution data within SAP once projects are underway
• financial perspectives that reflect both incurred cost and cash movement

Each of these components is valid and exists for a reason. But they do not naturally sit within the same system, which is where the breakdown occurs.

The challenge is not reporting on any one of these stages. It is connecting them into a single, continuous view of future cash outflows.

Until that connection exists no system, including SAP, can produce a reliable CapEx cashflow forecast.

The Real Cashflow Forecast Is Still Built Outside SAP

The gap between SAP data and a reliable cashflow forecast is not solved within the system. It is managed outside it.

Finance and project teams extract actuals and commitments from SAP, combine them with planning data held in spreadsheets or approval workflows, and manually consolidate the results into a single view of expected spend. Over time, this becomes the de facto approach to capital planning because it is the only way to bring all the required inputs together.

This approach provides flexibility and allows teams to incorporate pipeline activity that does not yet exist in SAP, but it also introduces a level of fragility that is difficult to control. The process relies heavily on manual intervention, which introduces:

• version control issues as multiple files circulate across teams
• lagging data that quickly becomes outdated
• limited auditability, making it difficult to trace how forecasts were built
• a lack of real-time visibility across the portfolio

What emerges is not a system but a process, one that can produce a forecast, but not a reliable one.

The Solution: A Capital Planning Layer Integrated with SAP

The issue is not that SAP needs to be replaced, it’s that it needs to be complemented. Rather than forcing planning into SAP, the more effective approach is to connect planning to it, allowing each system to operate within its intended role while contributing to a single, integrated view of capital spend.

This is where a solution like Stratex Online fits. It becomes the system of record for planning activities, including:

• project plans
• forecasts
• portfolio-level decisions

SAP remains the system of record for execution, managing:

• actuals
• commitments
• project delivery

The value of this approach is not in replacing one system with another, but in connecting them.

By bringing together planning and execution data in a structured way, it becomes possible to:

• combine planned, approved, and in-flight projects into a single forecast
• maintain both accrual and cashflow perspectives across the portfolio
• integrate SAP actuals and commitments without manual consolidation

The result is a consolidated view of capital spend that reflects both what is expected to be incurred and what will actually be paid.

Cashflow Visibility Is Now a Capital Constraint

The impact of this gap is no longer confined to reporting accuracy. It directly affects how capital is allocated, funded, and managed across the business.

For finance teams, an incomplete view of cashflow introduces risk into capital allocation decisions. Investment choices may align on paper, but without a clear understanding of when cash will be required, that alignment can quickly break down against financial reporting and funding constraints.

For treasury, the challenge is more immediate. Funding requirements depend on timing, not just totals. Without a reliable view of when cash will leave the business, liquidity planning becomes reactive rather than controlled, and short-term decisions begin to replace structured forecasting.

At an executive level, the implications extend further. Confidence in portfolio decisions depends on the ability to see how capital will be deployed over time, not just which projects have been approved. Without that visibility, the ability to reallocate capital dynamically is constrained, and strategic flexibility is reduced.

This is why the distinction between cost and cash has become more critical. In a high-interest rate environment, the timing of capital spend carries a direct financial impact. Delays, accelerations, and mismatches between forecast and reality are no longer absorbed easily; they affect funding costs, liquidity, and ultimately the viability of investment decisions.

Cash timing is no longer a detail within the forecast; it is a constraint that shapes it.

SAP Is Not the Problem, But It’s Also Not the Answer

SAP remains essential to capital project execution. It provides the financial control, structure, and discipline required to manage projects once they are approved and underway.

But that is not the same as forecasting.

A reliable CapEx cashflow forecast requires a view that extends beyond execution, one that captures investment activity before it reaches SAP and connects it seamlessly to what happens within it.

Forecasting does not start with committed projects. It starts with planning, prioritization, and decisions that shape how capital will be deployed over time. Without that context, any forecast built from SAP data alone will remain incomplete.

Organizations that get this right do not try to force SAP to do more than it was designed for. They recognize its role and build around it.

They introduce a capital planning layer that connects early-stage planning, portfolio decisions, and SAP execution into a single, continuous view of capital spend.

SAP remains the system of record for delivery. But the forecast, the one that reflects what will actually be spent, comes from the system that connects everything before and beyond it.