Back to Blog
Contract Governance

SAP Contract Governance Between ITAM and FinOps

ITAMFinOpsSAP Contract GovernanceHybrid PortfolioSAP Cloud ERP

SAP portfolios are inventory and consumption at the same time. On-premise licenses behave like classic stock, BTP credits and Ariba transactions behave like continuously metered consumption. ITAM and FinOps have moved structurally closer together since their partnership in June 2025, but together they still do not fully cover an SAP portfolio, especially not the long, asymmetrically adjustable SAP Cloud ERP, Private Edition contracts sitting between them.

Why FinOps Is Increasingly Moving Onto ITAM Territory

Over the past two years, the focus of FinOps practice has shifted noticeably. According to the State of FinOps 2026 Report, 90 percent of FinOps practitioners now manage SaaS costs, up from 65 percent the year before. 64 percent now manage license costs, up from 49 percent the year before. FinOps is visibly moving toward classic IT Asset Management (ITAM) territory: licenses, contracts, compliance evidence.

For SAP portfolios, this shift meets a structure that needs both disciplines at once and that neither one fully covers. On-premise licenses with named users and FUE tiers behave like classic inventory: procured once, tracked in inventories, verified through periodic measurements. BTP credits, Ariba transactions and SuccessFactors subscriptions behave like ongoing consumption: metered monthly, billed on usage, fundamentally elastic. According to the DSAG Investment Report, 78 percent of SAP customers today run hybrid portfolios spanning multiple product types and commercial models at once.

The governance tools for these two worlds evolved separately. Software asset management tools are built for license inventories and audit evidence. Cloud cost platforms are built for continuous, granularly measurable consumption, mostly with hyperscaler environments in mind. For an SAP portfolio that contains both inventory and consumption at once, neither tool covers the full picture.

Inventory and Consumption in One Portfolio: The Hotel Analogy

This convergence has also been formally recognized since June 2025. The FinOps Foundation and the ITAM Forum have entered a strategic partnership to bring the two disciplines together in a structured way (FinOps Foundation, "Intersecting Disciplines"). The ITAM Review describes the relationship in a widely cited image: "FinOps prices the rooms, ITAM manages the hotel" (ITAM Review, January 2026). FinOps governs what a single unit of consumption costs. ITAM is responsible for the structure in which that consumption happens in the first place.

A second analogy helps make the difference concrete for an SAP portfolio: ITAM works like classic warehousing, with ordering, stocking, minimum inventory levels and stocktaking. FinOps works like just-in-time control, with ordering based on actual demand and continuous adjustment. An SAP portfolio contains both at once, often within the very same contract.

With SAP Cloud ERP, Private Edition (formerly RISE with SAP), however, even this split only applies partially, because a third zone sits between them, one that fits neither the room-pricing principle of FinOps nor the pure inventory principle of ITAM. These contracts run for 5 to 7 years, not the 1 to 3 years typical of a cloud commitment. The adjustment is asymmetric: ACV can be increased at any time, a reduction is only possible at renewal at the earliest. A single change, for example to the user count or to a module, can cascade across multiple contract line items, because the pricing logic is built derivatively. And the metric itself shifts over the contract period: named users turn into an FUE figure that is counted differently from what was originally agreed.

This combination of long contract periods, asymmetric adjustment and a shifting metric is not fully addressed by either framework. The ITFM market is accordingly growing, according to Market Research Future, from around 5 to 13.8 billion USD by 2035, an indication that the need for a governance layer between classic ITAM and classic FinOps is increasing. For more on the structure of the operating phase, see Post-signature SAP Contract Governance.

Five Steps to Govern SAP Contract Portfolios Between ITAM and FinOps

1. Segment the Contract Portfolio by Governance Logic, Not by Product Name

The first step is classifying your own contract line items by how they behave, not by what the respective SAP product is called. On-premise licenses and fixed named-user allotments follow an inventory logic: they are tracked and reviewed on a fixed rhythm. BTP credits and transaction-based line items such as Ariba follow a consumption logic: they change continuously and can be steered tactically.

This distinction determines which tool and which cadence make sense for which line item. A monthly consumption dashboard adds little extra information for a fixed named-user allotment. An annual inventory check is not sufficient for BTP credits, because unused credit expires at year-end and does not roll over to the next year.

2. Reconcile Inventory Positions Against the Contract Metric Quarterly

For line items with an inventory logic, a quarterly reconciliation between actual usage and the contractually agreed metric is worthwhile, ahead of the regular measurement via USMM and LAW. This builds a solid data basis for when a shift from named user to FUE is due, and reduces surprises in the annual measurement.

This ongoing view makes visible which direction the metric is developing in, before a transition is due. Anyone tracking this development during the contract period enters the next negotiation with their own data basis.

3. Monitor Consumption Positions Continuously, Not When the Invoice Arrives

For BTP credits, Ariba transactions and comparable consumption line items, a monthly rather than reactive view is worthwhile: burn rate, overage risk, and the allocation of consumption to individual business units. These line items change faster than the classic audit rhythm can capture.

Monthly monitoring makes deviations between planned and actual consumption visible while there is still room to act, for example by reallocating between cost centers or adjusting usage, instead of reacting only once the invoice arrives.

4. Start Renewal Preparation for Hybrid Contract Components Six Months Ahead

For RISE and SAP Cloud ERP, Private Edition contracts, which are neither pure inventory nor pure consumption, renewal preparation ideally starts six months before contract end with a complete usage data basis across all components: which modules are actively used, which clauses allow price adjustments, and where the metric has shifted since the last negotiation.

This data basis cannot be assembled in the final weeks before renewal. It builds on continuous observation over the entire contract period, not on a one-time stocktake shortly before the deadline.

5. One Owner for Assets, Change and Control Across the Whole Portfolio

The most effective step is organizational: consolidating a single responsibility that owns all three layers, what the contract states (Assets), what changes about it (Change), and what needs to be done about it on an ongoing basis (Control), instead of splitting it between an ITAM team that stops at the SAP boundary and a FinOps team that only covers SAP at the margins.

This consolidation closes the gap that sits between the two established disciplines. It covers not just inventory or just consumption, but the contract logic that connects both across the full contract term.

Conclusion

ITAM and FinOps have moved structurally closer together since the FinOps Foundation and ITAM Forum partnership, but SAP contracts sit in an area that neither discipline has historically covered. Long contract periods, asymmetric adjustments and a shifting metric are characteristics that neither a classic license inventory nor a cloud cost dashboard fully captures. Who governs your SAP contracts after signing, across all product types and the full contract term? Neither ITAM nor FinOps tools alone can answer that question. It requires its own, continuous governance practice.

About the Author

Bernhard Mändle is Managing Consultant at FinOptory. He helps organizations govern SAP contracts continuously after signing, align usage and cost, and deploy their SAP investment deliberately. Extensive experience in SAP contract negotiation and governance across On-Premise, BTP and RISE, DSAG member, independent of SAP, resellers and system integrators. More at finoptory.ai and on LinkedIn.

Sources:

Further reading:

Next Steps

Would you like your SAP contract portfolio structured across inventory and consumption?

Request Contract Check Schedule a Call

This article is part of our topic hub on SAP contract governance after signature. To have one specific contract assessed, the FinOptory Contract Check delivers a structured basis within four weeks.

Bernhard Mändle
Written by Bernhard Mändle Managing Consultant, FinOptory for SAP®

Last updated: August 2026

Back to Blog