Modernizing Finance Before, During, Or After The SAP S/4HANA Move

The most common reason SAP Finance teams give for postponing a planning and consolidation upgrade is also the least examined: “We will do it after SAP S/4HANA.” The logic sounds prudent. Why build on a landscape that is about to change? Yet the SAP S/4HANA program itself has become the reason many Finance organizations are running on aging tools with no roadmap.

OneStream’s announcements at Splash 2026 in Orlando, alongside SAPinsider’s 2026 research, suggest that the sequencing question deserves a fresh look from CIOs, enterprise architects, and the Finance leaders waiting on them.

The Wait Is Longer Than Programs Admit

SAPinsider’s ERP Migration and Transformation 2026 benchmark found that 55% of organizations have deployed SAP S/4HANA or SAP S/4HANA Cloud, but only 34% have fully switched daily operations to it. A further 35% intend to switch before the end of 2026, which will strain partner and internal capacity. The gap between deployed and fully live is where Finance teams spend months, sometimes years, reconciling across two ERPs.

Additionally, SAPinsider’s Office of the SAP CFO research found that 54% of SAP finance organizations have migrated core Finance to SAP S/4HANA, yet only 17% describe their Finance systems as fully integrated. Some 42% still need more than eight days to close. At the same time, 92% rate real-time analysis and reporting as critical and 71% use driver-based planning.

What Splash 2026 Changed

During Splash 2026, OneStream’s technical keynote centered on a new cube engine, described as drop-in compatible with existing models with no migration project required. Early results show 2x to 4x improvements across calculation, consolidation, translation, and load to cube, with one real-world consolidation cut from over 90 minutes to 28 minutes on the same model, data, and rules. Data unit guidance rose tenfold, from two million to 20 million rows, and the engine now operates natively at daily granularity with no performance penalty.

A second announcement made at Splash 2026 matters more for the sequencing debate. A new Line Item Modeling engine lets Finance plan at the level where decisions happen, from hiring a role to launching a project, with SensibleAI Forecast generating line-level predictions and Operational Data Chat letting leaders query operational data in plain language. On that framework, OneStream introduced three prepackaged solutions: Workforce Planning; Fixed Term Planning for projects, contracts, leases, and subscriptions; and Duration-Based Contract Planning that captures the true start and end of activities rather than averages. Customers including Asurion and Emmi have replaced fragmented workforce planning tools with the platform.

IDC’s Heather Herbst framed the trend behind the release, noting that within just a few years, 50% of CFOs will take on Chief Operating Officer roles, applying rigorous financial discipline to operations. Finance leaders taking on that scope cannot wait for an ERP cutover to gain visibility into workforce cost, contract duration, or project spend.

Reframing “Wait for Sap S/4HANA”

Pras Chatterjee, who led SAP EPM product marketing before joining OneStream, argues in his analysis of SAP BPC’s end of maintenance that planning is mission-critical, and delaying improvements leaves the CFO’s office exposed to poor forecasting and lost agility. His point is that OneStream can be deployed before or in parallel with an SAP S/4HANA migration, providing validation and real-time insight during the ERP deployment itself.

That reframes the objection. Instead of a dependency on the ERP timeline, the planning and consolidation layer becomes an instrument for managing it. OneStream integrates across SAP ECC, SAP S/4HANA, SAP Datasphere, and SAP BW through BAPIs, function modules, IDoc exchange, and drill-through to transaction detail. During migration, Finance can validate migrated balances against legacy data, keep a single source of truth while entities move in waves, and continue closing without a parallel spreadsheet economy. When the ERP program slips, planning and reporting keep running.

The cost argument reinforces the case. SAPinsider’s Technology Leaders’ Strategic Agenda for 2026 found that 70% of technology leaders rank operational efficiency and cost reduction as their top priority, and 63% expect pressure to reduce IT and SAP-related costs this year. A consolidation that runs in 28 minutes rather than 96 minutes, and a planning process that replaces static assumptions with actual durations, are efficiency gains available now, not after go-live.

What This Means For SAPinsiders

Decouple the EPM decision from the ERP go-live date. CIOs should treat planning and consolidation as landscape-agnostic infrastructure. Deploying it before or alongside SAP S/4HANA gives the program a validation layer and gives Finance continuity through every migration wave.

Use the migration period to model operational drivers, not just a chart of accounts. With 71% of SAP Finance teams already using driver-based planning, enterprise architects should evaluate whether workforce, contract, and project planning can move to a single platform during the ERP program rather than after it.

Set performance baselines that survive the cutover. Finance leaders should record current consolidation times, close duration, and data load times, then hold both the ERP and EPM programs to improvement targets. SAPinsider’s finding that 42% of teams still close in more than eight days is the benchmark to beat.