SAP Renewal Stakeholders: Who Needs to Be Involved, Internally and Externally

Renewal is not a one-person job. The four roles that a sound SAP contract governance model requires are all called upon simultaneously during renewal, each operating on a different time horizon. Assembling the stakeholder team only shortly before negotiations begin means forfeiting exactly the lead time that separates a structured negotiating position from a reactive one.

---

Why Renewal Cannot Be One Person's Responsibility

SAP contract renewal touches several dimensions at once: contract documentation and deadline management, budget planning and cost allocation, mandate-backed negotiation, and the strategic decision about the next contract term. These dimensions cannot be consolidated into a single role without one of them falling through the cracks.

In practice, a familiar pattern emerges. The Contract Manager tracks deadlines but holds no negotiation mandate. Procurement holds the mandate but lacks the data foundation. Controlling has the numbers but is brought in late. The Executive approves the outcome but only once time pressure builds. Each of these constellations represents a governance moment that is not fully used.

The renewal governance moment is complex enough to require a structured team: four roles, clearly defined time horizons, and coordination that starts early. Organizations that assemble this team too late find themselves simultaneously running preparation work during the negotiation phase, work that should have been completed long before.

The phase model of the SAP Renewal Negotiation Framework defines the timeline: structured preparation begins at M-18, and the stakeholder team is formally constituted no later than M-12. What each role contributes within that framework, and when each becomes active, is what this article covers.

---

Contract Manager: Deadline Guardian and Clause Expert

The Contract Manager is the role that must enter the renewal process earliest. Not because negotiations are already underway, but because the foundations without which no negotiation can be meaningfully prepared take time to build.

What the Contract Manager Contributes

The Contract Manager knows the contract. That sounds obvious, but it often is not: in many organizations, the complete contract record, the Order Form, all Schedules, and all subsequent Amendments, is not fully and currently documented in a single location. Changes from earlier renewal cycles, Transformation Incentive arrangements, and special conditions frequently appear in documents that are not part of the central contract repository.

The Contract Manager's first task starting at M-18 is therefore to refresh the contract documentation. Which documents exist? Which are missing? Which special agreements from the last renewal are still in effect? Validate Schedule 5 as the price list reference: unit prices, volume tiers, minimum quantities. Identify and document all deadlines for the renewal calendar.

The Core Task at M-9

At M-9, the data foundation is in place and Phase 3 of the renewal process begins: the clause review. The Contract Manager assesses the six critical clause areas in the current contract, the price adjustment clause, the auto-renewal clause, the SLA structure, exit rights, the divestiture clause, and subscription flexibility. The output is a documented clause delta: what the current contract says, and what should be formulated differently in the next term.

This clause delta is the foundation for negotiation. Without it, Procurement enters a conversation with SAP without knowing which clauses warrant change.

The Governance Moment: Deadline Calendar

The Contract Manager also owns the deadline logic: the auto-renewal decision deadline, termination notice periods, the 45-day announcement window for price increases, and lockout periods for new subscriptions in the final six or twelve months before contract expiry. These deadlines are not details that can be tracked informally. They require an active calendar with defined escalation paths. This responsibility typically sits with the Contract Manager.

---

Procurement: Negotiation Lead and Budget Mandate

Procurement does not enter at the start of the renewal process, but it needs sufficient lead time to build the negotiating position that a structured conversation with SAP requires. Bringing Procurement in at M-6 while simultaneously expecting it to lead the negotiation means relying entirely on a clean handoff of data and scenarios from other roles. That is an organizational gamble.

What Procurement Contributes

Procurement owns the budget mandate for the new term. Without that mandate, the negotiation lacks decision authority: what can be offered, what is the limit, where is the defined negotiating range? These questions must be answered before the first formal conversation with SAP.

Procurement also owns the structured benchmarking process: what SAP is offering under what conditions, and how that compares to the organization's actual usage situation and to publicly available market data. Sources such as Gartner research, public DSAG reports, and redresscompliance.com provide context, but they do not replace an organization's own data foundation.

Active from M-12

Starting at M-12, Procurement begins scenario analysis and budget planning. Drawing on the usage data from Phase 1 and the scenarios defined in Phase 2, it develops budget frameworks for three renewal scenarios: status-quo extension, volume or component adjustment, and full renegotiation. Each scenario carries different implications for budget requirements and timeline.

Core Task at M-6: Lead the Negotiation

Procurement leads the renewal conversation with SAP, with a complete data foundation, a defined negotiating range, and Executive approval in place. Proactive outreach, rather than waiting reactively for SAP to set the agenda, determines who controls the initial framing.

One aspect that is frequently addressed too late in negotiation preparation: the combination of termination rights triggered by an announced price increase and an active renegotiation process. A customer's right to terminate in response to a SAP-announced price increase is contractually defined. It can be used as a tactical signal. Procurement needs a clear position on whether and how to use this option before the conversation begins.

---

Controlling: Usage Analysis and Budget Scenarios

Controlling is the role without which Procurement cannot develop credible budget scenarios, and without which the data foundation for the renewal negotiation remains incomplete. At the same time, Controlling is often the role that is formally brought into the renewal process latest.

What Controlling Contributes

Controlling owns the cost allocation for the current period, the analysis of actual consumption by business unit, and the cost projection for the next term. Which business unit has used which SAP services, and in what volume? This question is relevant both for the internal charge-back of the current period and for planning the next one.

Without Controlling, usage data exists but lacks attribution. Procurement has quantities but no budget figures. The Executive has scenarios but no financial basis for a well-grounded decision.

Active from M-12

Starting at M-12, Controlling prepares the usage analysis and closes out the internal charge-back for the current period. FUE utilization by user type, BTP credit consumption by cost center, CAS usage by business area, these outputs are the foundation for Step 3 of the renewal readiness process: a complete preparation of the last 12 months of consumption data.

Core Task at M-9: Build Budget Scenarios

At M-9, Controlling builds the budget scenarios for the three renewal options. These scenarios translate volume data and clause scenarios into budget figures. The Executive needs this foundation to make an informed decision about the negotiating framework.

A governance moment that becomes particularly visible at Controlling: the interaction between volume adjustment and the pricing mechanism. An organization that wants to reduce volume in the next term needs to understand how tiered pricing structures and CPI interactions affect the unit price. A volume reduction that drops the contract into a lower tier can raise the unit price, even without a CPI adjustment. This calculation belongs in the scenario analysis, not in the negotiation room.

---

Executive: Strategic Decision and Approval

The Executive makes the strategic decision: which renewal scenario to pursue. And approves the negotiating framework before Procurement enters the first formal conversation with SAP.

What the Executive Contributes

The Executive brings the budget mandate and the strategic framing: what role does SAP play in the portfolio over the next three to seven years? What volume makes strategic sense? These questions exceed the operational horizon of the other three roles and require a decision-making level that keeps the overall portfolio in view.

At the same time, the Executive is the role whose involvement most frequently comes too late. When Procurement enters negotiations and the Executive has not yet approved a negotiating framework, decision gaps open up at the most critical moment. SAP is negotiating with a counterpart who lacks final decision authority.

Active from M-12

Starting at M-12, the Executive reviews the three scenarios and sets the decision framework: what is the strategic goal, what budget range is broadly approved, and which clause objectives are non-negotiable? These questions do not need to be resolved at the level of detail, but the strategic framework must be in place before Controlling and Procurement complete their detailed work.

Core Task at M-6: Approval and Signature

No later than M-6, the Executive approves the negotiating framework: what latitude does Procurement have in the negotiation? What is the target outcome, and what is the fallback if SAP cannot be moved within that range?

At the end of the renewal process, the Executive signs the new contract. That closes the loop: the strategic decision is formally executed.

---

How the Stakeholder Team Is Organized

The four roles describe functions, not necessarily distinct individuals. In smaller organizations, one person may cover two roles, typically Contract Manager and Controlling, or Procurement and Executive. What should not be combined: negotiation leadership and approval of the negotiating framework in the same person. This separation is not a bureaucratic formality; it ensures that the negotiation lead has a clear principal and a defined mandate.

The Constituting Moment

The stakeholder team is formally constituted no later than M-12. That means: responsibilities per role are documented in writing, a communication cadence for the renewal process is established, and each role knows which data it must deliver by which point in time.

This constituting step is itself a governance moment, and one that is frequently skipped. Without it, roles work in parallel but not in coordination. The Contract Manager finalizes the clause review while Controlling is still waiting for the usage data needed to build the budget scenarios. Or Procurement enters the SAP conversation before the Executive has approved the negotiating framework.

External Expertise as a Complement

Alongside the four internal roles, external expertise can be a structured addition: an independent assessment of the contract position, market benchmarking, or support with data preparation. The right time for this is Phase 2, between M-12 and M-9, not Phase 4 when negotiations are already underway. External expertise brought in during the negotiation phase has no time to build its own data foundation and is therefore dependent on whatever has already been prepared internally.

---

Common Coordination Failures and Their Root Causes

Three patterns that appear regularly in renewal processes share a common cause: the stakeholder team was not constituted early enough, or the handoffs between roles were not structurally defined.

The clause review arrives too late. The Contract Manager begins the clause review at M-6 instead of M-9. The result: Procurement enters the first SAP conversation without a documented clause delta. Negotiation objectives are shaped reactively by SAP's proposal rather than proactively by the organization's own analysis.

The data foundation is not prepared. Controlling is brought in too late and delivers usage data only after negotiations have begun. Procurement works from estimates because the actual foundation is not yet available. Budget scenarios are unvalidated.

Executive approval is missing during the negotiation. The negotiating framework has not been approved in advance. Procurement must defer or informally seek decisions mid-negotiation, slowing the pace and giving SAP an information advantage.

These three patterns cannot be resolved by adding more effort in the negotiation phase. They originate earlier and require earlier structuring.

---

Conclusion: Four Roles, One Governance Moment

The renewal governance moment is complex enough to require a structured team. The four roles, Contract Manager, Procurement, Controlling, and Executive, each bring distinct competencies and distinct time horizons. A structured negotiating position that closes an SAP renewal with a defined outcome emerges only when all four roles are coordinated and engaged at the right time.

Constituting the stakeholder team is itself a governance moment: it should happen no later than 12 months before contract expiry, with clearly documented responsibilities and a defined communication cadence.

Organizations looking to structure the renewal process from the start will find the complete framework in the SAP Renewal Negotiation Framework: from the 12-to-18-month timeline to the data foundation and the critical clauses. The starting point is the organization's own contract position: what is agreed, what is actually being used, and where is the delta? The FinOptory Contract Review delivers that foundation in four weeks. Fixed fee: EUR 7,900.

---

FAQ

Which four roles must be involved in an SAP renewal?

Contract Manager, Procurement, Controlling, and Executive. Each role owns a specific dimension of the renewal process: deadline management and clause review (Contract Manager), budget mandate and negotiation leadership (Procurement), usage analysis and budget scenarios (Controlling), strategic decision and framework approval (Executive). When one role is missing, a decision gap opens up that becomes visible during the negotiation phase.

When should the stakeholder team for an SAP renewal be constituted?

No later than 12 months before contract expiry (M-12). The Contract Manager enters the process actively at M-18. The full team is formally constituted at M-12: responsibilities documented, communication cadence established, data requirements defined per role. Organizations that assemble the team only at M-6 forfeit the lead time needed for scenario analysis, clause review, and budget planning.

What happens if the Executive is brought in too late?

Procurement enters the SAP conversation without an approved negotiating framework. Decisions must be obtained during the negotiation, which slows the pace and creates information asymmetries. The strategic direction for the next term is set under time pressure rather than as a prepared decision.

Can one person cover multiple roles in the renewal process?

Yes, particularly in smaller organizations. What should not be combined: negotiation leadership (Procurement) and approval of the negotiating framework (Executive) in the same person. This separation ensures that the negotiation lead has a clear principal and a defined mandate.

When is the right time to bring in external expertise for an SAP renewal?

Phase 2, between M-12 and M-9. At that point, the data foundation is in place, scenarios are being defined, and an independent perspective on the contract position is still actionable. External expertise brought in during the negotiation phase (M-6 to M-0) no longer has time to build its own analysis.

---

This article is part of the SAP Renewal Negotiation Framework. Further reading: Renewal Timeline in Practice and Building the Data Foundation for SAP Renewal.

Author: Bernhard Mändle, FinOptory. Published: May 2026.