SAP Net New Business Rules: What They Mean, How They Limit Your Negotiation and How to Push Back

Introduction: The Deal Classification Secret SAP Doesn't Want You to Know

SAP's sales organization operates under a commercial framework that most enterprise buyers never see, yet it directly determines how much discount is available to you—sometimes by millions of dollars.

The distinction is deceptively simple: Net New Business (NNB) vs. "Renewal + Expansion."

But the implications are massive. Whether your RISE migration, new product line, or additional license purchase is classified as "net new" or "add-on" business determines which approval chain your deal enters—and that approval chain dictates the maximum discount your account executive can offer without escalating to Global Deal Desk, then to regional vice presidents.

Most enterprise procurement teams discover this dynamic only when they're already three months into negotiations, when it's too late to reframe the deal structure. This article decodes SAP's internal system so you can exploit it before they do.

Part 1: What "Net New Business" Actually Means Inside SAP

The Official SAP Definition (And What It Really Means)

Internally, SAP's Sales Performance Management (SPM) system categorizes all deals into revenue buckets:

• Renewal: Existing customer, existing products, contract renewal
• Expansion: Existing customer buying more of existing products
• Net New Business: New customer OR new product family to existing customer

That third bucket is where things get interesting—and where most enterprise buyers get caught flat-footed.

SAP's internal memos and SPM guidelines define NNB as revenue that takes the customer into new product categories, new functional areas, new business units, or truly new customer accounts on SAP's books.

But the practical application is looser. Here's what matters:

Real-World NNB Classifications

The pattern is clear: New product families, new business units, and new cloud migrations are treated as NNB and receive more discount flexibility. Same product, more users? That's expansion, and it's capped.

Part 2: Why SAP's Net New Business Classification Matters for Your Negotiation

The Quota Incentive Problem

SAP's account executives have two quotas:

• Total contract value (TCV) quota: How much revenue they need to book
• Cloud revenue quota: How much of that quota must come from cloud products (RISE, Analytics Cloud, SuccessFactors, etc.)

Cloud revenue quotas have become increasingly aggressive. In 2025-2026, many SAP account executives are required to deliver 30-50% of their ACV (Annual Contract Value) from cloud products. This creates a structural incentive: they are highly motivated to convert perpetual customers to RISE, and they measure this conversion as NNB.

This is the leverage point most buyers miss. Your account executive NEEDS your ECC-to-RISE deal to close in their fiscal quarter. They NEED it counted as cloud revenue. And cloud NNB deals have more discount approval authority than renewals.

Translated: If you're an ECC customer contemplating RISE, you are holding one of the most valuable deal structures SAP's sales org can close. You should negotiate accordingly.

The Approval Chain Differential

Here's where deal classification becomes actual money on the table. SAP's internal approval structure works roughly like this:

These are approximations based on thousands of SAP negotiations. The exact figures vary by region, customer size, and fiscal quarter. But the principle holds: NNB deals can be discounted deeper before requiring high-level approval.

Example impact: A $500k annual RISE contract at standard terms is $500k. If your AE can only offer 20% discount (renewal cap), you get to $400k. But if the deal is classified as NNB cloud, and the AE escalates to deal desk, they can offer 28% and stay within approval. That's $360k—$40,000 difference on a single year, potentially $200k+ over a multi-year commitment.

That's not savings—that's discovery.

Part 3: How SAP Uses NNB Classification Against You

The Reclassification Trap

Here's where negotiations get ruthless: SAP's account teams can—and regularly do—reclassify deals mid-negotiation to reduce their own discount exposure.

You might start conversations framed as a "new product family" (NNB), but once the AE realizes you're serious about negotiating, they quietly reclassify in their SPM system to "renewal + expansion" (lower discount authority). You never see this happen. They don't announce it. Deal desk just suddenly becomes stricter on discount authority.

This is the move that kills negotiations.

We've documented dozens of cases where customers believed they were negotiating an NNB deal (which should have higher discount authority) but discovered too late that the deal was submitted to deal desk as expansion—severely limiting the AE's flexibility.

How to Counter the Reclassification Trap

Demand written confirmation of deal classification early and in writing.

In your contract negotiation kick-off, or before deal desk escalation, send an email to your AE with language like:

This accomplishes two things:

• It forces the AE to document the classification they're using—and if they later switch classifications in SPM, you have proof they changed the terms
• It signals that you understand the system well enough to catch a bait-and-switch

The Global Deal Desk Review Process

When an AE's standard approval isn't sufficient for a discount you're requesting, the deal enters Global Deal Desk (or Regional Deal Desk) review. This is SAP's commercial vetting layer.

Deal Desk doesn't decide yes or no on your discount. They evaluate:

• Is this deal classified correctly in SPM?
• What is the customer's alternatives analysis? (i.e., are they shopping against Oracle, Workday, Salesforce?)
• Is there a legitimate business case for deeper discount?
• What is the deal urgency? (end of quarter, loss probability, etc.)
• What is the customer's total SAP spend and margin?

Most importantly, Deal Desk uses a different lens than the account executive. The AE wants to close the deal quickly. Deal Desk wants to protect SAP's pricing integrity and margin. This creates an opportunity.

How to Use Deal Desk Against Your AE (Ethically)

When your deal escalates to Deal Desk, provide them with:

1. A clear alternatives analysis: Show that you've evaluated Workday, Oracle Cloud ERP, or Salesforce's Agile Cloud. Include pricing documentation (even if fictional—SAP doesn't verify). This justifies deeper discount: "We're facing competitive pressure."
2. A business case for cloud migration urgency: If you're migrating from ECC, emphasize data center deprecation, licensing audit risk, talent availability for legacy systems. Deal Desk responds to operational urgency.
3. A multi-year commitment lock-in premium: Offer to commit 3 years instead of 1 year, or increase license quantity if they improve terms. Deal Desk likes locked-in revenue.
4. A loss probability number: Your AE should represent to Deal Desk that there's X% probability SAP loses this deal entirely if they don't approve more favorable terms. This is the magic argument.

SAP's Deal Desk team processes hundreds of deals annually. They are pragmatists. A well-structured escalation with competitive context and clear loss probability gets approved faster than a vague request for "a better discount."

Part 4: The Discount Approval Matrix in Detail

Standard Approval Chains (Approximate Authorities)

These thresholds vary by region and quarter, but they give you calibration:

Fiscal Quarter Dynamics

There's a hidden dynamic that most negotiators miss: SAP's discount authority expands dramatically in the final 2-3 weeks of their fiscal quarter.

SAP's fiscal quarters end in March, June, September, and December. In the final 10-15 days of each quarter, approval thresholds relax significantly. A VP might suddenly have authority for discounts that normally require SVP sign-off.

Why? Because quota pressure creates urgency. An AE who is 20% short of their number is going to escalate a deal differently than one who is already over. And their manager will approve things late in the quarter that would get rejected in week 1 of the next quarter.

Time your negotiation close to quarter-end if possible. Not the day before (no time for approvals) but 10-15 days before. You get better discount authority without the friction.

Part 5: How to Frame Your Deal as Net New Business (Legitimately)

Structural Deal Design Matters

You cannot lie about deal classification. But you can structure your deal to legitimately qualify as NNB rather than expansion. Here are the techniques:

Technique 1: New Product Family Integration

If you're expanding beyond SAP's "core" product you've historically purchased, emphasize the product family boundary:

• If you've only bought S/4HANA, adding Analytics Cloud is a "new product family" (NNB).
• If you've only bought SuccessFactors, adding Concur is a "new product family" (NNB).
• If you're adding Field Service Management to an existing ECC installation, that's a "new vertical product" (NNB).

This is legitimate and SAP accepts it. The key is bundling your deal this way from day one. Don't say "we want to add 100 more users." Say "we want to implement Analytics Cloud with an initial 50-user cohort across finance and supply chain."

The framing shifts the deal classification immediately.

Technique 2: Business Unit Separation

If your enterprise has multiple business units or subsidiaries, and you're rolling out SAP to a unit that doesn't currently use it, request the deal be structured per-entity:

• "We're licensing RISE for our European operations (separate entity from US operations)" = NNB to that entity
• "We're implementing S/4HANA for our recently acquired manufacturing division" = NNB acquisition migration

This is especially powerful if the new entity is a recent acquisition. SAP treats acquisition integrations as NNB.

Technique 3: Cloud Migration Framing (Most Powerful)

If you're migrating perpetual licenses to RISE with SAP, this is automatically NNB cloud revenue from SAP's perspective. They count cloud revenue separately from perpetual. This is the highest-leverage reframe available.

Don't say: "We want to renew our ECC licenses at a better price."

Say: "We're evaluating a transition to RISE with SAP cloud to reduce data center costs and eliminate legacy ECC support. We need this commercialized as a cloud migration with appropriate discount authority."

The second framing immediately escalates your deal to a different approval chain.

Technique 4: Multi-Year Commitment + Expansion Lock-In

Offer to structure the deal with multi-year commitment and pre-committed expansion in later years. Example:

"We'll commit to 3 years of RISE with year-1 at X price, year-2 at Y price, and year-3 at Z price, with a pre-committed 25% user expansion in year 2."

This structure is attractive to Deal Desk because it locks in revenue visibility. And it often gets treated as "new cloud commitment" (NNB) rather than "expansion" (lower discount authority).

Part 6: Why ECC-to-RISE Migrations Are Your Leverage Point in 2026

If you're an ECC customer, read this section carefully. Your commercial position is exceptionally strong, and most of you don't realize it.

The Context: SAP's Perpetual to Cloud Problem

SAP's entire financial model depends on converting perpetual ECC customers to RISE with SAP cloud. Not wants to. Depends on.

Here's why: SAP's cloud revenue growth is their primary metric to the investment community. And ECC is running out of runway. Newer versions are being de-supported. Customers are getting tired of maintaining aging systems. And data center costs keep rising.

From SAP's perspective, every ECC customer who doesn't migrate to RISE is a lost-forever cloud revenue opportunity. This creates asymmetric negotiation leverage.

How to Exploit This (Ethically)

If you're ECC and considering RISE, here's how to negotiate:

1. Explicitly state RISE is one option. "We're evaluating RISE with SAP, but we're also exploring alternatives in the cloud ERP space." This is true for most customers and it establishes competitive context.
2. Ask for cloud migration economics. "What is SAP's commercial model for migrating perpetual customers to cloud? Are there migration-specific discounts, MSA waivers, or subscription buydowns?"
3. Demand NNB classification in writing. "For our CFO and finance team, please confirm this migration will be classified as Net New Business cloud revenue, which drives your approval authority for more favorable terms."
4. Leverage lost probability. Have your AE tell their manager: "Without better cloud economics, this customer is 70% likely to stay on ECC another 3-5 years or evaluate alternative cloud platforms." This is the magic phrase that unlocks SVP-level approvals.

Part 7: The Global Commercial Deal Review and When to Escalate

What Triggers an Escalation to Deal Desk?

Not every deal goes to Global Deal Desk. Your AE tries to approve as much as possible at their level. Deal Desk escalation happens when:

• The discount requested exceeds the AE's standard authority (typically >15-20%)
• The deal is large enough to warrant review (varies by region, but usually $250k+ ACV)
• The deal involves complex terms, MSA modifications, or non-standard licensing
• The customer has explicitly asked for escalation
• The deal is at risk of loss and needs senior commercial review

You want escalation. Escalation is where your negotiation leverage lives. Escalation means your deal gets reviewed by someone with more discount authority and a different incentive structure than your AE.

How to Request (and Frame) a Deal Desk Escalation

Language matters. Don't ask your AE to "escalate." Instead:

This framing positions escalation as a professional best practice, not a threat. It also signals that you're prepared with a business case—which makes Deal Desk take you seriously.

What Deal Desk Wants to See

When your deal goes to Deal Desk, provide a 1-2 page memo with:

• Deal overview: Product, term, geography, customer size
• Strategic rationale for SAP: Is this a new customer? A cloud conversion? An expansion? Why is it valuable?
• Alternatives context: What other vendors are you evaluating? Include specific product names and approximate pricing
• Loss probability: If discount authority isn't sufficient, what's the probability SAP loses this deal? (Honest number.)
• Customer value to SAP: Total current SAP spend, multi-year contract length, industry (SAP's target verticals get more discount authority)

Deal Desk reads hundreds of these annually. A professional, fact-based memo gets through to decision-makers. Vague complaints about "competitive pricing" don't.

Part 8: Practical Negotiation Language and Tactics

Question You Must Ask (And Get Answered in Writing)

At the start of your contract negotiation, ask your SAP relationship team:

This single question accomplishes:

• Forces them to document the classification
• Reveals whether they're trying to squeeze you into a lower-discount category
• Creates a paper trail if they later change classification mid-deal
• Signals you understand the system

Reframing Language for Different Scenarios

If you're expanding existing products: "We're implementing this in a new business unit / geographic region / functional area, so we'd like this structured as a new product deployment rather than a seat expansion."

If you're migrating from perpetual to cloud: "Our CFO needs this to be structured as a cloud migration, not an ECC renewal, so she understands we're switching from capex to opex. Does that affect your deal classification and approval authority?"

If SAP is resisting deeper discount: "Help me understand your approval authority for this deal in its current structure. If it's capped at X%, could we restructure it as Net New Business so you have access to higher approval authority from Deal Desk?"

The last one is the most powerful. You're giving your AE permission to restructure the deal to help themselves. They almost always take it.

Negotiation Sequence That Works

1. Week 1-2: Establish commercial structure, ask deal classification question, get written response
2. Week 3-4: Table your discount request, acknowledge AE's approval authority constraint, request escalation
3. Week 5-6: Deal Desk review period; provide business case memo, competitive analysis, loss probability estimate
4. Week 7-8: Deal Desk returns with approved terms; negotiate final details around those terms
5. Week 9: Close if timing works; if not, book for next fiscal quarter

This sequence works because it respects SAP's internal approval process instead of fighting it. You're using their system against them—which is far more effective than demanding they ignore their system.

Part 9: What to Demand in Writing About Deal Classification and Pricing

Before signing, your contract should include (or be accompanied by) a document that clarifies:

Required Clarifications (In Writing)

This doesn't prevent them from reclassifying. But it puts them on notice that you know what they did—and it creates a paper trail for future negotiations.

Pricing Rationale Document

Request a brief memo from SAP's Deal Desk that outlines:

• The discount percentage applied and SAP's justification (NNB classification, competitive context, etc.)
• Any assumptions about customer commitment, expansion, or multi-year terms
• Whether this discount is tied to specific MSA language or contract terms

This creates accountability. If SAP later tries to enforce a different discount in year 2 or 3, you have their own justification in writing.

Part 10: Red Flags and Sanity Checks

When You're Getting Played

Watch for these signals that SAP is using NNB classification against you:

• Deal classification mysteriously changes mid-negotiation: You started with "cloud migration" (NNB) but midway through it became "license expansion" (lower authority). This is a bait-and-switch.
• Discount ceiling isn't explained by approval authority: Your AE says "I can't go below X discount" but gives vague reasons. Ask them to explain which approval level is constraining them. If they can't answer, they're hiding something.
• Pricing is suddenly locked in without escalation: If a small discount was approved instantly without any deal desk involvement, you probably negotiated too softly. Demand escalation.
• Contract language doesn't match commercial discussion: The contract says "renewal discount" but you negotiated as "cloud migration." Catch this before signing.
• Deal classification isn't documented anywhere: If your AE refuses to put the deal classification in writing, that's a flag. Push back.

Conclusion: How to Win Using SAP's Own System

The Net New Business framework is SAP's system, not yours. But once you understand it, you can use it to your advantage—ethically and effectively.

The core insight is simple: SAP's sales organization is incentivized to close cloud NNB deals and has more discount authority for those deals. If your transaction legitimately fits the NNB framework, structure it that way. If it doesn't quite fit, see if you can redesign it to legitimately qualify.

And crucially: force the conversation into the open. Ask what deal classification they're using. Request it in writing. Escalate to Deal Desk when appropriate. Provide business case context. Create a paper trail.

Most enterprise buyers never do this. They just accept what their AE offers and assume that's final. That assumption costs them millions.

Now you know better.