Executive Clarity · CFO & Finance

Financing the Transformation: What the Move to Cloud ERP Does to Your P&L, Balance Sheet and Budget Logic

By Andreas BORN

Published

How a move to SAP Cloud ERP hits the P&L, balance sheet and budget: subscription vs licence, expense vs capitalisation, and what a CFO settles first.

The question

When an organisation moves from a perpetually licensed, on-premises SAP landscape to Cloud ERP, the technology conversation usually dominates. The finance conversation deserves equal weight, because the move quietly rewires three things at once: how the spend is contracted (licence plus maintenance becomes subscription), how it is accounted for (capitalisation logic changes fundamentally), and how it should be financed and budgeted (a multi-year operating commitment replaces an investment-heavy project profile). CFOs who treat these as afterthoughts discover them mid-programme — usually as an unwelcome earnings conversation.

The documented facts

The commercial model changes. Traditional on-premises SAP is bought as a perpetual licence with annual maintenance on top. SAP’s cloud offerings — GROW with SAP for the public-cloud edition, RISE with SAP for the private-cloud edition — are subscription contracts: recurring fees for access to software, infrastructure and defined services over a contract term. The spend moves from a large up-front investment plus a maintenance annuity to a continuous operating commitment.

Under IFRS, a SaaS contract is a service, not an asset. The IFRS Interpretations Committee concluded in 2019 that a customer’s right to receive access to a supplier’s cloud-hosted software is neither a software lease nor an intangible asset of the customer — it is a service received over the contract term. The follow-on agenda decision, finalised in March 2021 and not objected to by the IASB in April 2021, addressed configuration and customisation costs in such arrangements: in the fact pattern considered, those costs generally do not create an intangible asset the customer controls, and are therefore mostly recognised as an expense — unless they meet the recognition criteria of IAS 38 or qualify as a prepayment for future services.

Under US GAAP, some implementation costs are deferred. FASB’s ASU 2018-15 requires customers in a cloud computing arrangement that is a service contract to apply the internal-use-software guidance in ASC 350-40 to implementation costs: preliminary-project and post-implementation costs are expensed, while qualifying application-development-stage costs are capitalised and then amortised over the reasonably certain term of the hosting arrangement, presented in the same line as the hosting fees.

The two regimes diverge. The same transformation programme can therefore look materially different in an IFRS group and a US-GAAP group: more of the implementation spend flows straight through the P&L under IFRS, while US GAAP defers a defined slice of it. Groups reporting under both need one programme cost model that feeds two treatments.

Inference

The EBITDA optics shift — in both directions. Retiring a capitalised on-premises landscape removes future depreciation, while subscription fees and expensed configuration work land directly in operating expense. Depending on the starting position, the transition years can look worse in EBIT and EBITDA terms than the underlying economics justify. That is an accounting-presentation effect, not a value statement — but boards react to presented numbers, so the effect belongs in the business case from day one, not in a footnote at the first quarterly review.

Budget governance has to change shape. A perpetual-licence project fits classic investment governance: approve once, capitalise, depreciate. A subscription commitment behaves like a long-term operating contract — closer to a facilities or outsourcing decision than to a capital project. Treating it with project-only governance produces two familiar failures: the annual run cost surprises the operating budget after go-live, and nobody owns the renewal negotiation until it is imminent.

Financing is now a design question, not a procurement afterthought. The instruments a CFO should have priced against each other before the programme is signed include, at minimum: the subscription term and its payment phasing; the treatment of any retained private-cloud or on-premises infrastructure, where leasing structures may still apply to hardware the organisation controls; partner and vendor financing constructs for the implementation itself; and the phasing of decommissioning costs for the legacy landscape. None of these change the technical architecture. All of them change the cash-flow profile and the P&L presentation of the same architecture.

The maintenance lever changed in July 2026. The European Commission’s acceptance of SAP’s commitments on maintenance and support — covered in detail in From Handcuffs to Sailboats — affects the financing question directly: the cost of buying time on the existing landscape is now more negotiable, which changes the discount-rate mathematics of “migrate now versus migrate deliberately.”

Point of view

The strongest CFO position I have seen is neither “cloud is cheaper” nor “cloud is more expensive.” Both statements are meaningless without a defined scope, term and treatment. The strong position is procedural: no transformation business case reaches the board until it shows the accounting treatment under the group’s actual reporting framework, the multi-year cash profile including decommissioning, the renewal-point exposure, and the sensitivity of the EBITDA bridge in the transition years. A business case that cannot show those four things is not conservative or aggressive — it is incomplete.

Monday morning

Four questions for your team this week:

  • Under our reporting framework, which parts of the implementation spend will be expensed, and has that flowed into the earnings guidance for the transition years?
  • What exactly happens at the first subscription renewal — and who owns that negotiation today?
  • Which parts of the retained landscape are still financeable as assets we control, and which have become pure service spend?
  • Does our budget governance treat the run-phase commitment as an operating contract with an owner, or does it end at go-live?

The facts above are drawn from the cited public sources; the inference and point-of-view sections are the author’s judgment. This article is general executive orientation, not accounting, tax or investment advice — treatment in any specific case belongs with the group’s auditors and advisers.

Sources