SAP Joule pricing in 2026. Count the AI allowance in agent runs.

SAP bundles roughly 200 AI actions per Advanced FUE, and a Joule agent draws 5 to 10 actions per run, so the allowance covers 20 to 40 agent runs. Since July 2026 that consumption is part of every SAP cloud renewal.

How does SAP Joule pricing work in 2026?

SAP prices Joule in two tiers. Business AI Base, which covers interactive Joule and the embedded AI features, is included in SAP cloud subscriptions and has been bundled in RISE and S/4HANA Cloud since July 2025. Business AI Premium is a separate purchase, paid for in AI Units.

AI Units are the single consumption currency across Joule and Joule agents. They behave like a prepaid balance that capabilities draw down as they run. SAP sells them annually with a minimum purchase of 100 units, they expire after 12 months if unused, and the remaining balance is visible in SAP for Me.

Why SAP replaced the seat with a unit

An automated agent is not a user. A per user metric cannot price machine driven work that runs with no human in the loop, and the AI Unit exists to charge for exactly that work.

The unit also changes who pays. The balance is consumed across the whole tenant, not per department. Without internal chargeback, no cost center sees the draw and no manager owns the number.

What SAP is changing in the Q3 2026 rollout

SAP's own training material describes a phased rollout of a new Premium AI model during Q3 2026. These are the changes that matter for budgeting.

• Features move to Base. Most generative AI features now sold in per user per month packages become part of Base.
• Packages retire. Those per user per month packages are phased out.
• Agents are metered per action. Agents become the core of Premium, and every agent action consumes 0.02 AI Units.
• One exception. Joule for Consultants stays at 35 AI Units per user per month.
• Custom agents free for now. SAP says custom agents run at no additional cost through the end of 2026 under a current promotion. Usage from that period will understate what the same agents cost from 2027, so record it anyway.

Separately, use based pricing became the default for SAP cloud renewals in July 2026. You can no longer decline it, so Business AI consumption now sits inside the core renewal negotiation. We cover the renewal specifics in what changes at the July 2026 Business AI renewal.

How many agent runs does the bundled AI allowance cover?

About 20 to 40 agent runs per Advanced FUE. In the quotes we reviewed, SAP bundled roughly 200 AI actions per Advanced FUE, pooled across licenses. A multi step agent draws 5 to 10 times what an interactive prompt draws, so the 200 actions shrink sharply once you count in the unit you will consume.

Treat the pooled allowance as a starting balance. A company with a large Advanced FUE count starts with a large pool, but a roadmap that automates a handful of workflows on a schedule will clear it well before renewal. Scheduled agents run whether or not anyone is at work.

Why an agent draws so much more than a prompt

An interactive prompt is one turn: Joule answers and stops. An agent reads context, plans, calls systems and writes results back, and every one of those steps draws from the same balance.

• Higher draw per execution. A business task that used to be one prompt becomes a five step agent and draws five to ten times the units.
• More executions. The agent runs on a timer or on every incoming document, so it executes far more often than a person would ever ask.
• No natural brake. A person stops asking questions when the working day ends, while a scheduled agent keeps running through nights, weekends and holidays.

The first two effects multiply each other. The comparison of assistant and agent cost is in Joule agents versus the Joule assistant, and the metering mechanics are in SAP AI Units explained.

What does a Joule agent roadmap cost once the pool runs out?

Once the pool is spent, every agent run is billed at the overage rate shown in the table above. The dollar total is modest at first. The problem is timing, because the pool empties months before renewal and the overage was never in the budget.

Take a hypothetical company with 400 Advanced FUE. We assume the allowance covers one contract year, so check the period in your own order form, because it changes the answer. The pool is 400 times 200, or 80,000 actions, which is 8,000 to 16,000 agent runs.

Three agents are enough to outrun the pool. The date matters more than the total, because at the high end finance meets an unplanned invoice a third of the way into the year. Every agent added after that month is billed at the overage rate from its first run.

How the answer changes with company size

The allowance scales with Advanced FUE, but agent demand scales with process volume and schedules. Those two rarely move together.

• 150 Advanced FUE. The pool is 30,000 actions, or 3,000 to 6,000 agent runs. One hourly agent needs 43,800 to 87,600 actions a year, so a single automation empties the pool on its own.
• 3,000 Advanced FUE. The pool is 600,000 actions, or 60,000 to 120,000 agent runs. A few agents fit comfortably, which is why large buyers feel safe in year one. The exposure comes when several business units build agents in parallel against one shared balance.
• Any size, scheduled workloads. At overage, one hourly agent costs $3,504 to $15,768 a year on its own. Multiply that by the number of scheduled agents on your roadmap.

Why is the free Business AI Base tier a budget risk?

Base is a risk because nothing measures it. Interactive Joule sits largely inside the Base entitlement, so finance never sees a bill for chat and no team sets up consumption reporting for a line that costs nothing.

The company then spends a year forming its sense of AI usage from a period when usage was free and light by design. When Premium is enabled, the workload changes shape at the same moment the billing does. The forecast for a metered agent run rate is then built on a history of unmetered chat.

Why we disagree with "it is included, just switch it on"

SAP account teams advise switching Business AI on because it is already included. We disagree. In roughly seven out of ten SAP cloud environments we modeled across 2024 and 2025, the bundled Base entitlement masked a Premium and AI Units run rate that would have landed as an unbudgeted true up within two renewal cycles.

Switch Base on, but measure it from day one as if it were billed. Then price Premium at the current renewal, while you still have volume to trade.

Why per user AI budgets fail

AI budgets are often built per user, because that is how SAP software was bought for decades. A per user budget has no line for an agent that runs every hour. Meanwhile the overage rate was set months earlier, in an order form no one costed against agent volume.

The difference between a pilot and a run rate is a scheduling decision, usually made by someone who never sees the invoice.

What have we seen in SAP cloud renewals in 2024 and 2025?

Across roughly 35 to 45 SAP RISE and S/4HANA Cloud renewals we benchmarked in 2024 to 2025, the same consumption patterns came up again and again. They explain why the first true up is when most buyers learn what their agent roadmap costs.

• The agentic multiplier, 5 to 10x. A multi step agent run drew 5 to 10 times a single interactive Joule prompt, which is why a chat baseline cannot forecast agent cost.
• The hidden meter. Free Base usage hid the Premium run rate to come in most of the environments we modeled, the pattern described in the previous section.
• Overage priced but not modeled. Overage ran roughly $0.08 to $0.18 per action in the quotes we reviewed, and the FUE action allowance was rarely mapped against real usage before signature.
• Assumed inclusion. Buyers assumed AI was included and first met the AI Units line at the Premium upsell, with no consumption history to negotiate against.

The exposure we found sat in agent consumption. Interactive chat was small, predictable and mostly covered by Base.

What should you negotiate in the SAP order form for AI Units?

Negotiate the action allowance, the AI Unit price and the overage rate as three separate terms, and add a consumption cap. The overage rate you eventually pay depends on how hard the allowance and unit price were argued in the order form. Governance alone does not hold a run rate once agents are scheduled.

Contract wording to ask for

• Allowance definition. State what counts as an action, the allowance per Advanced FUE, the period it covers and that it is pooled across the tenant. Without a written definition you cannot check a single invoice line.
• AI Unit price hold. Fix the unit price for the full subscription term, including top up purchases, so mid term additions are not repriced at list.
• Overage rate in the paper. Write the overage rate into the order form at or below the committed unit price, so running past the pool does not trigger a premium rate.
• Consumption cap. Consumption above an agreed ceiling should require written approval from a named person. A cap in the contract survives a change of team, a new roadmap and a scheduling decision in an unrelated project.
• Carry forward. AI Units expire after 12 months by default. Ask for unused units to roll into the next year, or to run for the full subscription term.
• Consumption data. Require monthly usage data by agent and by application, including Base usage, so you can build the baseline your next renewal depends on.
• Credit for moved features. If you pay for a per user package whose features SAP shifts into Base, ask for its remaining value as AI Units or a price reduction.

What the SAP account team will say, and what to say back

• "Business AI is included, so there is nothing to negotiate." Base is included. We want the Premium allowance, unit price, overage rate and cap priced in this order form, while the renewal is open.
• "Buy a larger AI Units block now and the unit price drops." Units expire after 12 months, so an oversized block is prepaid waste. We will commit to our modeled volume and want top ups at the same unit price.
• "You cannot forecast agents yet, so we will settle it at true up." That is the reason for a cap and a price hold today. At true up we would have no alternative supplier and no time, and the price would reflect that.
• "SAP for Me shows your consumption in real time." Monitoring shows the draw after it happens. It does not limit the invoice, which is why we want the cap in the contract.

Timing matters as much as the terms. Our notes on AI attach pressure and timing and SAP fiscal quarter timing cover how to use the calendar in your favor.

How do you measure your own Joule consumption before renewal?

Start with what SAP already shows you, then fill the gaps yourself. SAP for Me reports AI Unit usage and the remaining balance in real time, but Base draws no AI Units, so interactive Joule usage will not appear there.

Build the baseline in four steps

1. Ask SAP for Base usage data in writing. Request monthly Joule usage for your tenant by application, and make regular delivery a contract term.
2. List every planned agent. For each one, record its trigger (schedule, document or event), expected runs per month and the business owner.
3. Convert runs to actions and dollars. Multiply runs by the number of steps each agent takes, then price the result at the overage rate in your quote. SAP's published rate for 2026 is 0.02 AI Units per agent action, so 50,000 agent actions draw 1,000 AI Units. SAP does not define an agent action publicly, so ask your account team to confirm in writing that the actions in your allowance are the same unit it meters.
4. Compare against the pool month by month. Find the month the pool runs out. That month, more than the annual total, decides how much time you have to act.

Govern agent enablement like a change

Make every new agent, and every schedule change on an existing one, a change request with a named owner and a cost center. Set up internal chargeback, because an unowned shared pool is drawn down by whichever team automates first.

For the wider SAP cloud commercial picture, including BTP credits, see our BTP credits guide and the full library in the SAP knowledge hub.

What to do next

1. Restate your allowance in agent runs. Divide the pooled action count by 5 to 10, so the number in the business case matches the unit you will consume.
2. Measure Base now. Get usage data flowing before Premium is enabled, so a real baseline exists when the meter starts to bill.
3. Price the agent roadmap. Convert each planned agent into runs per period, then into actions and dollars at the overage rate in your quote, and find the month the pool runs out.
4. Split the commercial terms. Negotiate the allowance, the unit price and the overage rate separately, and put a consumption cap in the order form.
5. Control enablement. Treat every new agent as a change request with a named owner and internal chargeback.
6. Get a second opinion on the SAP proposal. Our SAP advisory team models the AI Units run rate with you and checks the order form before you sign.

Frequently asked questions