What CFOs Need Before Approving an S/4HANA Migration

What is the CFO actually approving?

Do not approve an SAP S/4HANA migration because 2027 is close or because the technical team says the system is ready. Approve it only when finance can see the chosen transition path, the cost range, the unresolved assumptions, the test evidence, and the named owners who will carry the risk after go-live.

This decision comes after the company has built its SAP ECC migration business case. The CFO is deciding whether that case is ready to enter funded execution, not whether S/4HANA is attractive in principle.

The path must be explicit. SAP's Getting Started With SAP S/4HANA 2025, version 2.0 dated 25 February 2026, identifies three typical paths from SAP Business Suite: system conversion, selective data transition, and new implementation. Each produces a different data scope, testing burden, cutover plan, and cost exposure. “Move to S/4HANA” is therefore not an approvable scope.

Time matters, but it does not replace evidence. SAP's 4 February 2020 maintenance announcement states that Business Suite 7 core applications receive mainstream maintenance through the end of 2027. Optional extended maintenance runs through the end of 2030 at a premium of two percentage points on the maintenance basis. SAP also committed to maintaining at least one S/4HANA release through 2040. Appcentric's ECC support guide explains the timing question; it is not proof that a specific project is ready.

Key takeaways

• A deadline can set the decision window. It cannot prove the plan.
• A technical readiness report is one input, not final approval evidence.
• Every open item needs an owner, a review date, and a stated financial or operational effect.
• Approval should release a defined stage of funding against measurable conditions.

Which evidence should finance require before saying yes?

Require dated technical and business evidence. In its 2026 Getting Started With SAP S/4HANA 2025 guide, SAP describes Readiness Check: “This tool analyzes your SAP ERP 6.0 system and highlights important aspects of the conversion to SAP S/4HANA, such as identification of relevant simplification items, high-level custom code analysis, add-on compatibility, sizing, and more.” It also says to run Simplification Item and custom-code checks before conversion.

The phrase “and more” is where weak approvals hide. A green technical report does not prove that the close will tie out, invoice data will remain usable, a warehouse can keep shipping, or the company has enough nonproduction capacity for realistic testing.

Use this pre-approval evidence register. It is an Appcentric editorial checklist, not an SAP-prescribed template.

For programs considering Appcentric's RISE with SAP service, SAP said in an April 2024 methodology article that its approach drew on thousands of RISE customers over three years. It also described added onboarding and quality checks for first-time RISE subscribers after 1 April 2024. That supports staged checks for RISE programs. It does not make SAP or a systems integrator the owner of finance acceptance.

What should stop approval?

Stop when a missing item could change the cost, delivery date, control design, or ability to operate after cutover. Do not let a red item become green because the team renamed it an assumption.

A conditional approval can be sound when the condition is narrow, measurable, funded, and due before the affected work starts. “Custom-code disposition signed by the application owner before build begins” is a condition. “Resolve custom code during the project” is an admission that scope and cost are not known.

Finance should withhold approval when any of these is true:

• the selected transition path is still being debated;
• the cost case excludes data cleansing, regression testing, temporary environments, business backfill, or cutover support;
• a material add-on, interface, tax process, or reporting output has no owner and no test case;
• finance has not approved the opening-balance and transaction-reconciliation method;
• the cutover plan has no tested fallback point or workable manual procedure; or
• the approval pack uses vendor status colors without the underlying dated evidence.

Commercial uncertainty deserves the same treatment. A proposal must state what is included, which volumes or environments drive price, how change requests are controlled, and which costs remain with the customer. Use Appcentric's SAP pricing guide to identify commercial variables, then require the proposal to convert each applicable variable into a documented assumption.

Do not ask for certainty that no project can provide. Ask for bounded exposure. The approval pack should show a base cost, identified contingencies, the decisions that can still change the amount, and the last point at which management can stop without committing the next stage of spend. The fact to end on is not a green dashboard. It is the largest unresolved exposure, who owns it, and when that person must decide.

What do CFOs ask before approving an S/4HANA migration?

The CFO should not be treated as the sole legal approver by default. Section 22 of the Philippine Revised Corporation Code places corporate powers, business conduct, and control of corporate property with the board unless the Code provides otherwise. Whether this project needs board, executive-committee, CFO, procurement, or other approval depends on the company's bylaws, authority matrix, board resolutions, and contract rules.

The approval record should therefore name the decision owner, required concurrences, delegated limit, approved amount, stage being released, conditions, and expiry date. That record matters in week eleven, when an exception becomes a change request and nobody remembers what “approved” included.

Does SAP Readiness Check prove that the project is ready?

No. It identifies technical conversion considerations such as simplification items, custom code, add-on compatibility, and sizing. Finance still needs evidence for cost, data reconciliation, process acceptance, tax controls, cutover continuity, and ownership. Treat the report as an input to the register, not the approval itself.

Should the 2027 maintenance date force an immediate approval?

No. It should force a dated decision. SAP's maintenance policy gives the company planning facts, including optional extended maintenance through 2030. Management must compare the cost and exposure of waiting against the risk of starting with an incomplete scope. A compressed, unready project is not a safer answer.

Who should own finance reconciliation?

The controller or named finance process owner should approve the method and acceptance threshold, while the data team executes the loads and produces evidence. The sign-off should cover opening balances, transaction populations, key reports, and unresolved differences. “Data migrated successfully” is not a finance acceptance criterion.

Can the CFO approve while issues remain open?

Yes, if none of the issues invalidates the selected path or approved cost and each condition has an owner, due date, funding, and stop rule. Conditions must be cleared before the affected work begins. An issue without a decision date is deferred exposure, not a controlled exception.

What should happen immediately after approval?

The program office should freeze the approved baseline, issue the decision record, fund only the authorized stage, and place every condition in the delivery plan. Finance should schedule the next evidence review before more spend becomes irreversible. The signed register becomes the reference when scope, price, or timing changes.