Part of the Finance systems at end of life series.
SAP BPC 10.1 for Microsoft reached the end of mainstream maintenance in June 2026. SAP BPC 10.1 for SAP NetWeaver has mainstream maintenance until 31 December 2027, with optional extended maintenance available until 31 December 2030. SAP has published no like-for-like successor: it directs consolidation work to SAP S/4HANA for Group Reporting and new planning work to SAP Analytics Cloud. That is the totality of what SAP has formally stated. Everything else - urgency, timing, sequencing - is an inference, and the quality of that inference matters considerably to a group CFO.
What exactly has SAP published about BPC end of life?
SAP has published two distinct maintenance timelines depending on which platform your BPC installation runs on. BPC 10.1 for Microsoft lost mainstream maintenance in June 2026. BPC 10.1 for NetWeaver retains mainstream maintenance until 31 December 2027; customers who require it can purchase extended maintenance through to 31 December 2030. These are the dates SAP has formally committed to. Mainstream maintenance means SAP continues to release legal, regulatory, and security patches as standard. Extended maintenance typically carries an additional licence fee and a narrower scope of support. Groups still on the Microsoft variant are already in the grey zone; those on NetWeaver have a defined runway, but a shrinking one.
What does SAP offer as a replacement?
SAP offers no single replacement for BPC - that is the first thing a group finance team needs to understand clearly. Consolidation is directed to SAP S/4HANA for Group Reporting; planning and budgeting is directed to SAP Analytics Cloud. One product is being retired into two destinations, each sitting in a different part of SAP's portfolio and, potentially, on a different commercial and implementation track. Whether those two destinations are right for a given group is a separate question entirely - the point here is structural. The replacement map is a fork, not a migration.
Why does a maintenance date matter for a finance function that is still running?
A product running beyond mainstream maintenance continues to function - the lights do not go out on 1 January 2028. What changes is the risk profile. Without mainstream maintenance, SAP will not proactively deliver regulatory updates, and any patches become a negotiated, fee-bearing conversation. For a group finance function, the practical concern is statutory and regulatory: CSRD disclosure requirements, IFRS amendments, and local GAAP changes continue regardless of what SAP is willing to patch. A consolidation tool that falls behind on regulatory currency is a material risk to the integrity of group reporting, not merely an IT inconvenience. That is why the maintenance timeline is a finance-owned decision, not one that can be safely delegated to IT procurement.
Is this a consolidation decision or a planning decision - or both?
It is both, and that is precisely why it is harder than a conventional end-of-life migration. Groups that use BPC for statutory consolidation and group reporting face one decision: where does the legal-entity close, intercompany elimination, and group pack production move to? Groups that also use BPC for planning and budgeting face a second, largely independent decision: where does the planning model go, and how does it connect to actuals? These two decisions have different owners, different timelines, different data architecture implications, and - critically - different business cases. Conflating them produces a programme that is twice as complex and half as governable. The discipline is to separate them explicitly at the outset, assign a sponsor to each, and resist the vendor temptation to bundle them into a single transformation.
What is the actual decision a group CFO needs to make?
The actual decision is not which system to buy next - that comes later. The decision a group CFO needs to make first is whether the organisation is moving because the deadline compels it, or because the current state of the Maturity Matrix in consolidation and planning justifies a deliberate upgrade. A group running group close at a Manual or Standard maturity level will not get to Integrated or Automated simply by changing platform; the process discipline has to move first, or the new system inherits the old dysfunction. A group that is already Integrated and wants to reach Automated or AI-embedded has a coherent business case: the platform change is in service of a capability ambition, and the value at stake - the costed gap between where the function is today and a level-5 AI-embedded close - can be put in front of a board in pounds. That is the difference between a reactive migration and a finance transformation with a defensible number attached.
What should a group finance team do now?
Three things, in order. First, establish which BPC variant you are running and confirm the precise maintenance status - Microsoft or NetWeaver, and whether extended maintenance has been contracted. Second, separate the consolidation question from the planning question formally: different workstream, different sponsor, different business case. Third, assess current maturity before specifying a destination. The Finance Value Score Maturity Matrix covers both Group month-end close and Planning & budgeting as distinct rows; rating each area from 1 (Manual) to 5 (AI-embedded) produces the factual baseline from which a costed business case - value at stake in pounds - can be built. A maintenance deadline is a useful forcing mechanism. It is not, by itself, a strategy.
Common questions
When does SAP BPC 10.1 reach end of mainstream maintenance?
SAP BPC 10.1 for Microsoft reached the end of mainstream maintenance in June 2026. SAP BPC 10.1 for SAP NetWeaver has mainstream maintenance until 31 December 2027. Optional extended maintenance for the NetWeaver version is available until 31 December 2030.
What is SAP's stated successor to BPC?
SAP has published no single like-for-like successor to BPC. SAP directs consolidation and group reporting requirements to SAP S/4HANA for Group Reporting and new planning work to SAP Analytics Cloud. One product is effectively replaced by two separate destinations in SAP's portfolio.
Does a BPC end-of-maintenance date mean the software stops working?
No - the software continues to function after mainstream maintenance ends. What changes is SAP's obligation to deliver regulatory, legal, and security patches as standard. For group finance teams, the primary risk is that the consolidation tool may fall behind on statutory and regulatory updates, which is a material reporting risk.
Should a group consolidation migration and a planning migration be managed together?
They are two separate decisions with different owners, timelines, and business cases, and treating them as a single programme typically increases complexity and reduces governance clarity. The consolidation decision concerns the statutory close, intercompany eliminations, and group reporting; the planning decision concerns budgeting models and their connection to actuals. Separating them explicitly at the outset is the disciplined approach.
What is the right starting point before choosing a BPC replacement?
The right starting point is an honest maturity assessment of the current finance function - specifically of group close and planning - before specifying a destination platform. Without knowing whether the function currently operates at Manual, Standard, Integrated, Automated, or AI-embedded maturity, there is no basis for a defensible business case, and the risk is that a new platform inherits existing process dysfunction.