When SAP Ties Your ERP Discount to Taking AI and BDC Scope

SAP account teams are now presenting AI Units, Joule capacity, and Business Data Cloud as inseparable from the ERP discount, because attached scope is what their backlog number is built on. This page shows you how to unbundle the price, what the separate lines are actually worth, and the precise week in the cycle to refuse the attach without surrendering a point of core discount.

The Attach Is a Quota Motion, Not a Product Decision

Start from the arithmetic on SAP's side of the table, because it explains everything the account executive is about to say. Software license revenue fell 32%. Cloud gross margin slipped 0.7 points to 74.6%. Cloud backlog sits at EUR 22.9 billion, up 27%, and Cloud ERP Suite now carries 88% of total cloud revenue. Management told the market that AI and Business Data Cloud appeared in more than 90% of the 50 largest deals. Read those four numbers together and the conclusion is unavoidable: the attach is a backlog-manufacturing exercise. Backlog is booked on contracted scope, not on consumption, so an AI Units line and a BDC line signed today count fully toward the number even if your users never touch a Joule prompt. The AE is not evaluating whether your finance function needs agentic close automation. He is filling a committed-scope target that his comp plan pays on, which is the mechanic we lay out in detail in what SAP sales reps are actually paid on. Name it out loud in the room, and do it with the figures attached. In our experience across these deals, an AE who hears a buyer say "more than 90% of your top 50 deals carried AI or BDC scope, and I understand why that matters to your backlog line, so let's price it separately" stops using the "this is how we sell now" framing inside one meeting. The framing only survives while the buyer believes it is a product policy. Expect the pressure to intensify rather than ease: SAP has publicly committed to dozens of assistants and more than 400 autonomous suite agents, and every one of those is a future attach vector requiring its own capacity line. The scope you accept this year becomes the baseline SAP measures next year's growth against.

Backlog is booked on contracted scope, not on consumption, so an AI Units line signed today counts fully even if nobody ever writes a Joule prompt.

Why the Bundle Exists: The Packaging Change That Made It Possible

The attach became possible because SAP changed the packaging. RISE with SAP as a branded tier structure (Base, Premium, Premium Plus) has been retired for SAP Cloud ERP, private edition, and the capabilities that used to justify the higher tiers, advanced AI and the fuller Joule functionality among them, now sit on their own lines. That is the whole game. When advanced AI lived inside Premium, the discount conversation was one negotiation over one price. Once it moved onto a separate SKU, the AE gained something he did not have before: a line he can withhold, threaten to reprice, or dangle as the reason your ERP discount cannot move past a given band. Business AI Base has been bundled into RISE and S/4HANA Cloud since July 2025, so the free tier exists, but base Joule capability is capped and exceeding the cap spills into AI Unit consumption. Premium requires AI Units outright. In practice that means the "included" AI is a metered trial with a cliff, and the cliff is where the paid line begins. Understand also that between $500K and $2M of annual infrastructure cost has migrated off the old RISE line item onto BTP, Datasphere, and AI Unit budgets, so a flat-looking ERP price is often a shifted price.

Business Data Cloud carries a separate and more dangerous mechanic, and it is contractual rather than commercial. The service description requires a qualifying cloud subscription and states that the BDC subscription must cover a User count equal to or greater than the corresponding application. That ratio is not a discount policy an AE can waive in the room. It means BDC entitlement scales automatically as your ERP seat count grows, and it means every acquisition, every division rollout, every FUE true-up quietly drags a BDC increase behind it. Underneath the single BDC line sit three separate meters: Databricks Units for processing, Databricks Storage Units for storage, and FUE as the allocation ratio. Unless you negotiate an explicit cap, a growth ceiling, or a decoupling amendment before signature, you have signed an escalator with three independent dials that SAP reads and you do not.

Price the Attached Scope on Its Own Line, and Watch the Discount Move

The reason SAP wants one number is that the attached scope is where the soft money sits. Structured negotiations on Joule capacity SKUs and BTP credit allocations consistently produce 35 to 55 percent reductions against SAP's opening proposal, which is a wider band than the ERP line itself delivers at most spend tiers. Compare that to the ERP benchmark: 40 to 55 percent off list for buyers above $50M in annual SAP spend, 30 to 45 percent between $10M and $50M, and 20 to 35 percent for first-time cloud buyers. If you are a $25M buyer, the AI line has more headroom than your ERP line does. Blend the two and SAP funds a thin AI concession out of an ERP discount you were going to earn anyway on volume, tier, and competitive pressure. That is the entire trick. The "blended program discount" is not a courtesy, it is a mechanism for making a 22 percent AI Unit discount look like part of a 44 percent enterprise outcome.

Demand three separately quoted lines before any commercial conversation continues: ERP FUE, AI Units and Joule capacity, and BDC capacity with its underlying meters. Refuse to evaluate a program-level percentage. Then run each line against its own benchmark. In my experience across SAP tables, the moment you force line-level pricing the AI number moves first, because the account executive has more authority there and less internal scrutiny on it. The ERP discount tends to hold roughly where it was, which tells you the bundle was never actually funding it.

Two enforcement points. First, no discount above 40 percent on the ERP line has been observed without a credible competing proposal in play, and credible means a signed NDA, a scoped SOW, a named executive sponsor, and an implementation partner. Second, insist the AI and BDC discounts are stated as standalone percentages in the order form, not derived from the program total, so that a later true-up or expansion cannot be repriced at list. Time the whole exercise against SAP's fiscal calendar, because line-level pricing pressure lands hardest in the weeks before September 30.

The Unit Economics That Break the Business Case

Once the lines are separate, the AI number stops being a discount question and becomes a consumption forecast question, which is where most of these deals fall apart quietly eighteen months after signature. The entitlement is roughly 200 AI actions bundled per Advanced FUE, with overage priced near $0.08 to $0.18 per action depending entirely on how hard the FUE allowance was negotiated at the outset. That per-action figure looks trivial in isolation. It is not, because the consumption profile SAP is selling you is agentic, not interactive. A Joule agent consumes roughly five to ten times the units of a single interactive prompt, and SAP has signaled more than 400 autonomous suite agents by year-end. Overage is typically billed at three to five times the contracted rate. Stack those multipliers and a modest agent rollout consumes the bundled allowance inside a single quarter, after which every incremental action is priced at the worst rate in the contract.

One BDC line is three meters: processing, storage, and an FUE ratio that grows every time you add ERP seats.

BDC is worse because it is not one meter. Processing runs on Databricks Units, storage on Databricks Storage Units, and FUE acts as the allocation ratio. The service description also requires the BDC subscription to be equal to or greater than the same number of users as the corresponding application, so BDC scales automatically as ERP seats grow. That is a contractual escalator, not a commercial one, and it will not be fixed by a discount percentage.

Do not sign until SAP produces, in writing and on letterhead, a 24-month consumption forecast modeled against these specific rates, with the assumptions stated: agents deployed, actions per agent per month, DBU and DSU projections, and the FUE ratio at month 24. Then convert that forecast into a contractual cap: overage priced at contracted rate rather than a multiple, and a pooled allowance across AI Units and BDC capacity so an overrun in one is absorbed by underuse in the other. Remember what happened to the ERP line when packaging changed: roughly $500K to $2M of annual cost moved off RISE and onto BTP, Datasphere, and AI Unit budgets. Buyers who did not price that separately found it mid-implementation, with no leverage left. Ask your account team what their backlog credit is on the attached scope, then price accordingly.

Timing the Refusal: Before Signature, and Inside the Q4 Window

The refusal is a perishable asset. SAP's fiscal year closes September 30, and the discretionary authority that lets a regional VP sign off on 45% or 50% off list concentrates in July through September. That means the sentence "we are not taking AI Units or BDC in this transaction" carries commercial weight in mid August and almost none in mid November. This is not because the product changed; it is because the person who can approve an exception has already banked the quarter and no longer needs your signature to hit a number. Time the conversation using the same logic you would apply to any SAP quarter-end and fiscal-year signing decision, and understand that the delta is measurable: the swing between a Q4 close and a Q1 close on the same scope is routinely several points of discount, which is the entire subject of the Q4 versus Q1 comparison in this cluster.

The harder timing rule is sequencing, not calendar. If you sign RISE first and agree to "come back to AI next year," you have handed SAP the only lever you had. Before signature, the AI attach is competing against your willingness to walk from a nine figure ERP commitment. After signature, it is competing against nothing. Worse, once Joule agents are running in production against live master data and finance users have built approvals around them, operational dependency prices the renewal for you. Market experience is consistent here: the leverage curve does not decline gently after go-live, it collapses, because the alternative is now an internal change program rather than a procurement decision.

Expect the reset threat: "this discount is only valid through quarter end and resets next quarter." Treat that as accurate about their authority and irrelevant to your decision, with one caveat. Buyers who let the deal slip two or three weeks into the new quarter genuinely do lose the position, because the AE's urgency evaporates and rebuilding it takes a full quarter. So set your own internal deadline at roughly ten days before September 30, decide before then whether you are signing core-only, and be prepared to hold entirely until the following July rather than drift into October negotiating from a weaker seat.

What SAP Will Say Back, and How Long 'Non-Negotiable' Survives

Predict the script and you defuse most of it. First, the AE calls the attach a program requirement: AI and Business Data Cloud are "part of the Cloud ERP platform" and cannot be removed. Ask which contract document says so, in writing. Business AI Base is already bundled in Cloud ERP; Premium is a separate paid add-on consuming AI Units. BDC's own service description requires a qualifying cloud subscription and a user-count ratio, which is a scaling clause, not a purchase obligation. Nothing in the paper obliges you to buy Premium AI capacity at signature.

Second, expect the pricing dodge. SAP's own leadership has said publicly it wants to move AI toward value-based pricing around business outcomes rather than traditional software licenses. In the room this becomes refusal to quote a per-unit rate. Do not accept an outcome narrative in place of a number. Demand, in writing: the per-AI-Unit rate, the actions included per Advanced FUE, the overage rate per action, and the DBU and DSU rates behind BDC. Without those four figures you cannot model anything, and the reason they are withheld is that agentic consumption runs roughly five to ten times an interactive prompt and overage typically prices at three to five times contracted rate.

Third, the generous-looking move: AI "included at no incremental cost in year one." That is a renewal liability, not a discount. The ratio clause grows the BDC commitment with your seat count, and use-based renewal defaults land the true cost in years two and three. If you accept it, cap it: fixed renewal uplift, a stated per-unit rate held for the full term, and an explicit right to drop the AI lines at renewal without touching the ERP discount.

Fourth, the discount reset threat, which is the honest one and the reason timing matters. Hold anyway. Across large SAP deals, language presented as non-negotiable typically becomes negotiable within two to three weeks of sustained, prepared pressure, particularly once the conversation moves above the AE. And know the hard boundary: no observed discount above 40% has occurred without a live competing proposal, meaning signed NDA, scoped SOW, named executive sponsor, and an implementation partner. If you want the top band while refusing the attach, that competitor work has to be real. Understanding what SAP sales is actually compensated on tells you why they will trade the attach before they trade the core.

First Moves This Week

Start by destroying the single-number proposal. Inside 48 hours, send your account team a written instruction to re-quote as three separate lines: Cloud ERP (FUE count and per-FUE rate), AI Units and Joule Premium capacity, and Business Data Cloud with DBU, DSU, and the FUE allocation ratio broken out. Ask in the same letter for the per-unit AI Unit rate, the per-action overage rate, the bundled action allowance per Advanced FUE, and a 24-month consumption model signed by SAP that assumes agentic usage at 5 to 10 times interactive prompt volume. Refuse "outcome-based" or "value-based" framing outright: if SAP cannot state a unit rate, SAP cannot state a price, and any commitment you sign becomes an uncapped meter.

Then attack the two clauses that compound. The BDC service description ties your BDC user count to your ERP user count on a greater-than-or-equal basis, which means every ERP seat you add for the next five years automatically buys BDC. Strike the ratio clause or cap it at a fixed number, not a formula. Do the same on uplift: SAP's 5% default compounds to 25 to 35% cumulative over five years, and 2.5 to 3% is achievable in our experience on deals of this size.

Set your refusal date now, inside the July to September window when quota authority is highest, and name the executive you will escalate to when the AE calls the attach non-negotiable. Build the six-week signature-readiness runway backwards from that date, and read the escalation ladder guidance before you need it. Understanding what your rep is actually compensated on tells you exactly how much the attach is worth to them.

A strong outcome, in numbers: core ERP discount held at your spend band (40 to 55% for above $50M annual spend), AI and BDC discounted 35 to 55% independently of that band, no user ratio clause, escalation capped at 2.5 to 3%, and every attached SKU cancellable at anniversary without touching the ERP term.

Related advisory: the full topic guide.

Frequently asked questions

Can SAP legally require me to buy AI or Business Data Cloud to get my ERP discount?

No. There is no contractual requirement tying an ERP discount to AI or BDC scope. The attach is a sales motion driven by backlog and quota, and the 'program requirement' framing is a closing tactic. In practice it becomes negotiable within two to three weeks of sustained, well-prepared commercial pressure.

How much discount should I expect on AI Units and Joule capacity if I price them separately?

Buyers in structured negotiations consistently reach 35 to 55% off SAP's initial proposals on Joule capacity SKUs and BTP credit allocations. That is typically wider headroom than the ERP line itself, which is precisely why SAP prefers a single blended program discount. Insist on three separately quoted lines.

What is the Business Data Cloud ratio clause and why does it matter?

SAP's BDC service description requires a qualifying cloud subscription and states that the BDC subscription must cover a number of Users equal to or greater than the corresponding application. That makes BDC scale automatically as your ERP seat count grows, converting a one-time attach into a permanent cost escalator unless you negotiate a cap.

When in the SAP fiscal year should I refuse the AI attach?

SAP's fiscal year ends September 30 and account teams carry their highest discount authority from July to September. Refuse inside that window and before signature. Refusing after the ERP contract is executed, or once agents are running in production, removes your leverage and reliably produces worse pricing.

Does the July 2026 use-based pricing default mean I have to accept consumption pricing?

No. Use-based pricing became the default posture on SAP cloud renewals from July 2026, which moves AI consumption into the core negotiation rather than leaving it as an opt-in add-on. It is a default, not a mandate, and capped or committed structures remain available to buyers who ask for them in writing.

What does a strong outcome look like in numbers?

Core ERP discount held inside your spend band (40 to 55% above $50M annual spend, 30 to 45% between $10M and $50M), AI and BDC priced on separate lines at 35 to 55% off initial proposal, no BDC user ratio clause, per-unit AI and DBU rates documented, and annual escalation capped at 2.5 to 3% instead of the 5% default.