How Unilever rebuilt its planning architecture around xP&A

By 2019, Unilever was operating roughly 400 product categories across more than 190 countries, with regional finance teams producing forecasts largely independent of what commercial or supply chain teams were projecting. The mismatch was not a technology failure. The company had capable ERPERPA single integrated software backbone that runs core operations: finance, procurement, supply chain, HR and manufacturing on shared data.View full definition → infrastructure and a sophisticated FP&AFP&AThe finance function that builds budgets, forecasts and analysis to guide business decisions and connect strategy to numbers.View full definition → function. The problem was structural: each planning cycle produced internally coherent numbers that diverged sharply when compared across functions. Sales would commit to volume targets that supply planning had not modelled. Finance would build annual budgets from historical trends that bore little relation to what the commercial teams were negotiating with major retailers. The result was a persistent gap between plan and actual that absorbed significant management time every quarter.

This situation is not unusual for companies at Unilever's scale, but Unilever made it public through investor communications and internal reorganisation announcements, which makes it a useful case to examine rather than an anonymised composite.

What did Unilever change in its planning architecture?

The company's response, developed progressively between 2019 and 2023, had three distinct components.

The first was consolidating the data layer. Unilever invested in a unified data platform that pulled signals from trade spend systems, customer order data, and production scheduling into a single environment accessible by finance, sales operations, and supply chain planning teams simultaneously. This is the infrastructure precondition for xP&A: without a shared data model, extended planning is just another word for more meetings. The company worked with SAP (a vendor with a direct commercial interest in this architecture, worth noting when reading SAP's own case study materials on the topic) to build integrated planning modules, while also drawing on cloud-based data infrastructure through Google Cloud, announced in a partnership in 2019.

The second component was redesigning the planning cadence itself. Unilever moved away from an annual budget cycle supplemented by quarterly reforecasts toward a rolling 18-month planning horizon updated monthly at the category level. This change forced the organisation to treat forecasting as a continuous process rather than a periodic event. For the FP&A team, it meant shifting significant capacity from variance analysisvariance analysisVariance analysis compares actual financial results against budgeted or planned figures to quantify differences and explain why they occurred.View full definition → toward scenario modelling, because a rolling plan is only useful if the scenarios it contains are actually decision-relevant.

The third component, and the one that took longest, was changing who owned what in the planning process. Previously, each function submitted its numbers upward, and reconciliation happened at the CFO or COO level. Unilever created cross-functional planning teams at the category level, where a finance business partner, a demand planner, and a commercial lead worked from the same base data and jointly owned the category forecast. This distributed accountability rather than consolidating it at the top.

SAP IBP and Anaplan in Unilever's planning stack

Unilever's architecture drew on SAP Integrated Business Planning for supply chain scenarios and Anaplan for financial modelling. Both vendors have published their own accounts of this work, and both have a commercial interest in how it is described. The more reliable signals come from Unilever's own investor presentations and the operational metrics the company disclosed. Independent analysts at Gartner have noted, in research published prior to 2026, that companies achieving genuine xP&A integration consistently report that technology is the easier part: the harder work is process governance and incentive alignment across functions.

Results of Unilever's xP&A shift between 2021 and 2023

Unilever reported meaningful improvements in forecast accuracy at the category level between 2021 and 2023, though the company disclosed these in qualitative terms in earnings calls rather than publishing a precise percentage figure. Attributing forecast accuracy improvement solely to xP&A integration would overstate the case, because the same period included significant supply chain disruption from commodity price volatility and the post-pandemic demand normalisation.

What Unilever did disclose more concretely: a reduction in the number of planning systems used globally from over 60 to fewer than 20 by 2023, and a stated reduction in the time finance business partners spent on data consolidation (a figure cited internally as approximately 30 percent of planning time recovered, though this number comes from internal Unilever communications rather than audited reporting). The strategic planning team also became more involved in scenario work tied to portfolio decisions, which aligned with the company's public programme of divesting slower-growth categories during this period.

The clearest outcome is structural rather than numeric. Unilever's finance function changed its relationship with commercial and operational planning from a verification role (checking whether numbers added up after decisions were made) to an earlier position in the decision cycle.

What transfers to a smaller CFO team

The Unilever case carries concrete lessons for a CFO leading an xP&A integration, alongside genuine cautions about where the context differs.

The data infrastructure investment is non-negotiable, but it does not need to be uniform across the whole business. Unilever phased adoption by category and region, which limited disruption and allowed the organisation to learn from early implementations before scaling. A mid-size company with fewer legacy systems may actually move faster than a business of Unilever's complexity.

The planning cadence change is where most organisations underestimate the cultural resistance. Moving to rolling forecasts requires the business to accept that the approved annual budget is no longer the primary performance reference. That shift needs explicit CFO sponsorship and, critically, alignment with the CEO and commercial leadership before the first rolling cycle begins. Announcing the new cadence without that alignment produces a system where rolling forecasts coexist with the old budget as a shadow reference, which adds work without adding insight.

The cross-functional ownership model transfers well to almost any organisation, but the design details matter. Finance business partners embedded in cross-functional planning teams need clear authority to challenge commercial assumptions, not just report on them. Companies that create the team structure without adjusting the authority model find that finance reverts to a reporting function within the new format.

Where the Unilever context does not transfer: the company had the resources to run a multi-year technology migration while maintaining existing systems in parallel. Smaller organisations may need to sequence more aggressively, accepting that a lighter integrated tool deployed quickly will outperform a sophisticated architecture that takes three years to implement.

The core principle behind xP&A is straightforward: finance, sales, and operations planning produce better decisions when they share a data model and a planning rhythm, not just a reconciliation meeting. Unilever's path to that outcome took several years and required deliberate governance changes at every level. The companies that attempt xP&A as a technology project, without touching the process or the accountability structure, tend to arrive at better-connected silos rather than integrated planning.