Part of the Finance systems at end of life series.
SAP plans to continue mainstream maintenance for Business Objects Financial Consolidation (BFC) until the end of 2030, with the stated intention of migrating existing customers to SAP S/4HANA for Group Reporting. That gives BFC groups a longer runway than BPC groups - and that extra time is both an asset and a trap.
What has SAP actually said about BFC maintenance?
SAP has confirmed mainstream maintenance for BFC through the end of 2030. That is a specific, published commitment: groups running BFC can expect vendor support, patches and regulatory updates until that date. Beyond 2030, SAP's stated direction is migration to S/4HANA for Group Reporting. SAP has not, to date, published an equivalent commitment to extended maintenance beyond 2030 for BFC in the way it has done for some other legacy products. The practical read: 2030 is a hard horizon, not a soft one.
How does the BFC position differ from BPC?
The BFC position differs from the BPC position in one material respect: the maintenance end date. SAP's mainstream maintenance for BPC ended earlier, leaving BPC groups with a shorter decision window. BFC groups have more runway by comparison. The destination SAP intends for both populations is the same - S/4HANA for Group Reporting - but BFC groups have more time to approach that journey deliberately rather than reactively. That difference in timeline is real. What groups do with it is a strategy question, not a technical one.
Why is a long runway also a risk?
A long maintenance runway can produce a false sense of stability. If 2030 feels distant, the natural organisational response is to defer the decision - to treat the platform question as next year's problem, then the year after that. The risk is structural: the longer a decision is deferred, the shorter the remaining runway becomes, and the narrower the realistic set of options. Groups that start evaluating in 2028 are not conducting a strategic selection; they are managing a crisis. Under time pressure, the path of least resistance is to accept whatever the incumbent vendor offers. That may be the right answer. It may not be. The problem is that there is no longer enough time to find out.
What does the decision window actually look like?
Work backwards from 2030. A consolidation platform replacement - requirements definition, vendor selection, implementation, parallel running, go-live, stabilisation - typically consumes more time than finance leaders expect when they first scope it. Groups that begin the process in earnest in 2026 or 2027 are in a reasonable position. Groups that begin in 2029 are not selecting a platform; they are accepting one. The window for a genuine, unhurried evaluation is now, not later. The 2030 date makes this feel comfortable. That comfort is the risk.
How should a group finance function use the remaining runway?
The right use of a long runway is to make the decision well, not to avoid making it. That means three things. First, understand where your current BFC implementation actually sits on the maturity scale - what is genuinely being used, what workarounds exist, where the process pain is. Second, articulate what a replacement needs to deliver for your group specifically: legal entity volume, multi-GAAP requirements, intercompany complexity, CSRD obligations on the finance-owned cut. Third, build an internal business case with a costed gap - not a vendor-supplied ROI estimate, but a bottom-up view of what the status quo is costing and what the move is worth. That business case is what protects a group from being sold to rather than served.
What is the connection to AI and ESG in consolidation?
The platform decision does not exist in isolation. Groups evaluating their consolidation function in 2025 and 2026 are doing so in the context of two frontier shifts: AI-embedded finance automation and finance-led ESG reporting under CSRD. A group that treats its BFC replacement as a like-for-like swap - same process, newer software - may find it has made the migration without capturing the value. The consolidation platform a group selects in this window will likely be the one that either enables or constrains its AI-embedded and CSRD ambitions for the decade that follows. That is a stronger argument for engaging now than the 2030 deadline alone.
What should a group CFO do next?
The immediate action is not to issue an RFP. It is to produce an honest internal picture of where the finance function stands today - across consolidation, close, planning and reporting - and what the gap to best practice is worth in pounds. That picture does two things: it frames the platform decision in business value terms rather than IT replacement terms, and it ensures the board conversation, when it happens, is grounded in numbers rather than vendor narratives. The Finance Value Score Maturity Matrix exists precisely for this purpose - to turn a hunch about finance maturity into a board-ready view of value at stake. BFC groups have enough time to do this properly. The question is whether they will.
Common questions
When does SAP end mainstream maintenance for Business Objects Financial Consolidation?
SAP plans to continue mainstream maintenance for BFC until the end of 2030. Beyond that date, SAP's stated intention is to migrate existing BFC customers to SAP S/4HANA for Group Reporting. Groups should treat 2030 as a hard horizon when planning their consolidation platform strategy.
Is the SAP BFC end-of-life date the same as BPC?
No. SAP's mainstream maintenance for BPC ended earlier than BFC, leaving BPC groups with a shorter decision window. Both populations are directed toward S/4HANA for Group Reporting as the intended destination, but BFC groups have more time to conduct a deliberate evaluation.
What is the risk of waiting until 2029 to start a BFC migration?
A group that begins its consolidation platform evaluation in 2029 no longer has time for a genuine competitive selection. Under time pressure, the practical outcome is accepting whatever the incumbent vendor offers. Starting the evaluation in 2025 or 2026 preserves optionality and allows a properly scoped business case to be built.
Does the BFC migration decision affect a group's AI and ESG consolidation ambitions?
Yes. The platform selected during this window will likely determine whether a group can embed AI automation and meet finance-led CSRD obligations - including ESG data consolidation - for the following decade. Treating the migration as a like-for-like swap risks missing that value entirely.
What is the right first step for a group CFO facing the BFC end-of-life decision?
The right first step is an internal assessment of where the finance function sits today - across consolidation, close, planning and reporting - and a costed view of the gap to best practice. This produces a board-ready business case grounded in pounds rather than vendor claims, which is the foundation for any credible platform decision.