How to Negotiate SAP Enterprise Support Credits

Why 40-60% of SAP Enterprise Support Credits Go Unclaimed

Enterprise Support contracts deliver MaxAttention credits—typically 30-50 per year—yet most organizations capture only 40% of actual entitlement. This is not accidental; it's structural.

MaxAttention credits are the currency of SAP support priority. Each credit purchases 4 hours of dedicated support engineer time, unlimited back-and-forth, and expedited issue resolution. The contractual entitlement is clear. The problem: SAP does not automatically notify you of annual allocations, does not report consumed vs. available balances, and has no obligation to carry over unused credits.

The result? Credits expire silently at year-end. Support teams consume some credits in reactive crisis mode. No one tracks the baseline allocation. Budget holders see no line item for credits in quarterly reviews. CFOs do not know they paid €80K for support services used at 35% capacity.

At renewal, SAP's position is simple: "You did not use them. Let's begin again." That clause in section 4.2.1 of your support annex—the one about carryover? It says credits are "subject to mutual agreement." In SAP's experience, mutual agreement requires leverage.

The 3-Step Enterprise Support Credit Audit

Step 1: Establish Your Baseline Entitlement

Begin with your current Master Licensing Agreement and all amendment letters. Look for:

• Support Level: Confirm Enterprise Support (22% of NLV) is in effect. Standard Support (18%) includes no MaxAttention credits.
• Credited Products: Enterprise Support includes credits only for SAP applications on maintenance. HANA, Analytics Cloud, SuccessFactors, Ariba, Fieldglass, and BTP services typically have separate support terms. Exclude cloud subscriptions.
• Annual Credit Allocation: Enterprise Support standard includes approximately 1 credit per 3-5M in licensed NLV (Net License Value). A company with €100M in core application NLV receives ~20-30 credits annually. Verify this in the support schedule (typically Annex A or Schedule 2).
• Carryover Clause: Check if prior-year unused credits carry into the current year. Many contracts state credits "do not carry over unless otherwise agreed." This is the leverage point.

Step 2: Audit Actual Credit Consumption

Request from SAP Support Administration a complete PBC (Professional Business Consultation) consumption report covering the past 12-36 months. This report should itemize:

• Date of PBC engagement
• Credits consumed per engagement
• Issue category (implementation, optimization, troubleshooting, etc.)
• Support engineer assignment
• Time logged (often exceeds contractual credit allocation—a red flag for underpricing)

Cross-reference this against internal records:

• Support ticket logs: Extract all high-priority (P1/P2) tickets flagged as "MaxAttention" or "named engineer" services over the period.
• Finance records: Check if any PBC invoices were submitted separately. SAP sometimes bills credits as discretionary services outside the contract, creating a gap between "contractual entitlement" and "what we actually used and paid for."
• Project archives: If your team conducted SAP implementation or major system upgrades, PBC support was likely consumed but not tracked against the credit allocation.

Step 3: Calculate Your Carryover and Gap Position

Create a simple table:

Each credit is worth approximately €2,500-3,500 depending on your contract rate. A company with a €35K annual credit loss is burning €105K per 3-year cycle.

Negotiating Enhanced Credit Terms at Renewal

Build Your Negotiation Case

Present SAP with three documents:

• Audit Summary: "Over the past 3 years, we received 84 credits, consumed 43, and have 28 unaccounted for due to lack of carryover notification and inadequate reporting."
• SAP Delivery Evidence: Attach PBC logs, support tickets, and engineer time sheets showing both contractual consumption and contract value delivered.
• Market Comparison: Reference industry benchmarks showing that competitors with similar NLV achieve 75-90% credit utilization through carryover + reporting infrastructure. This shows your loss is not operational—it's contractual.

Propose a Carryover Schedule

Standard carryover language: "Unused credits from Year 1 carry over to Year 2 in full; unused credits from Year 2 carry over to Year 3 at 75% of balance; credits from Year 3 expire unless specifically approved by both parties in writing."

A better carryover schedule for your position:

• Unused credits carry over for up to 3 years (allows you to batch large projects and claim credits retroactively).
• Minimum carryover balance increases by 20% annually if consumption is below 60% of entitlement (creates incentive for SAP to reduce credit allocation or support quality, but also for you to consume credits more actively).
• Any credits used beyond contractual entitlement are absorbed at the standard per-credit rate (€2,500/credit), not as discretionary invoicing.

Specify Credits as Named Services in Contract

Amend your support schedule to include a new section:

"MaxAttention Credit Service Schedule"

• Annual allocation: [X] credits
• Per-credit value: €2,500
• Minimum notification: SAP must provide written notice of annual allocation and carryover balance by [Date]
• Consumption reporting: SAP provides quarterly PBC delivery reports itemizing credits consumed, engineer assigned, and remaining balance
• Carryover: Credits carry forward as defined in Section 4.2.1 (Carryover Schedule)
• Named allocation: [X] credits reserved for mission-critical incident support; [Y] credits allocated to optimization projects; [Z] credits flexible allocation

Converting Unused Credits to Cash Discount Equivalents

If your support team has no capacity to consume accrued credits, negotiate a cash buyback. This is often more valuable than carryover if you anticipate:

• Cloud migration reducing SAP on-premise system complexity
• Upcoming contract termination or renegotiation
• Internal restructuring reducing support needs

Valuation Formula:

Unused Credits × €2,500 = Equivalent Discount on Renewal Support Fee

Example: If you carry 35 unclaimed credits from 2024-2025, that's 35 × €2,500 = €87,500 credit equivalent. At renewal, negotiate a €87,500 reduction in your Year 1 support fee (22% × NLV) or apply it to a 1-year discount on your entire support portfolio.

SAP's position will be: "Credits have no cash value; they are contract services." Counter with: "Then we should carry them indefinitely until consumed, or you should not issue them. If they are services we cannot consume, the contract has not delivered promised value—and that is a renewal risk."

Locking Credit Terms in Your Contract

Never leave credit terms to "mutual agreement" (SAP's favorite phrase). At signature, you need explicit contract language:

Common Negotiation Objections and Rebuttals

"Credits have no cash value—they are services only."

Rebuttal: "Then why is SAP issuing them in a quantity we cannot consume? If they are unlimited services, remove the allocation. If they are limited, they have implicit value, and that value should be reflected in contract terms that prevent expiry without notification and carryover."

"Carryover creates unlimited liability for SAP."

Rebuttal: "Standard carryover with 3-year expiry is market practice in Enterprise Support. We are requesting the same terms your top 50 customers hold. If you cannot deliver 3-year carryover, reduce the annual allocation and increase the per-credit value to reflect higher utilization pressure."

"Your support team should manage credit consumption proactively."

Rebuttal: "We agree. That requires quarterly reporting and advance notice of expiry. You provide neither. Once you implement automated reporting (which every competitor offers), we will take responsibility for consumption planning. Until then, this is a service delivery failure on your part."

The Bottom Line

MaxAttention credits are not a freebie—they are part of your Enterprise Support contract that you paid for. Yet 40-60% go unclaimed because SAP has no incentive to make them easy to claim. The three-step recovery process (audit → carryover negotiation → contract lock-down) is repeatable at every renewal cycle.

For a €100M enterprise, this typically means €70-110K in recovered value per renewal cycle. At 3-5 year intervals, that compounds to significant savings. The effort required is 2-3 weeks of internal audit work and 4-6 weeks of contract negotiation. The ROI is 500-1000%.