Contents
Key takeawaysWhat an AI Unit isThe Advanced FUE allowanceOverage and the order formForecasting consumptionWhat we saw in renewalsWhat to do nextFAQAn SAP AI Unit is a prepaid credit that meters Business AI per action across the tenant. Agents draw it far faster than chat, and the effective rate is fixed in the order form, so the negotiation window closes at signature.
- The unit is a shared balance. AI Units are prepaid credits drawn per action across the whole tenant, so no user owns them and per user budgets miss them.
- Base draws nothing. Joule Base and embedded AI need no units, while Premium capabilities, above all Joule agents, spend the balance.
- The bundled allowance is a pilot window. It pools across Advanced FUE and covers months of chat but only weeks of scheduled agents, so measure burn with it and never budget against it.
- The price is set at signature. Unit price, allowance treatment and overage rate are all fixed in the order form, and most buyers we saw left the overage rate as printed.
- Forecast from agents. Count actions per agent workflow at its scheduled frequency, because that is where the draw comes from.
- Know SAP's published rules. Units are bought annually with a 100 unit minimum, expire after 12 months, and show in SAP for Me.
What is an SAP AI Unit?
An SAP AI Unit is a prepaid consumption credit for SAP Business AI. It meters use per action across the whole tenant whenever a capability runs beyond the bundled Base tier. The unit is a shared balance, so it does not belong to any user, and the draw grows with the complexity of the task.
That last point is where per user budgets go wrong. SAP software was bought per user for decades, so AI budgets were built per user too. The meter never counts users, which is why per user budgets missed it by a wide margin once agents were switched on.
What SAP publishes about AI Units
SAP's own pricing page and training material set out the commercial rules. We checked them in September 2026.
- Base AI draws nothing. Joule Base (asking questions, finding the right screen, retrieving information, contextual guidance) and the embedded AI inside SAP applications come with every SAP cloud subscription and need no AI Units.
- Premium AI draws the balance. SAP delivered Joule agents are priced at 0.02 AI Units per agent action for 2026, and Premium AI features are charged per request or per record.
- Units are bought annually. They are ordered under SKU 8019164, the minimum purchase is 100 AI Units, and unused units expire after 12 months.
- One pool. Units sit in a single pool that any Premium capability in the tenant can draw from. SAP for Me shows the balance, the usage by package and the billing in near real time.
- Excess is billed. Use beyond the purchased volume is charged pay per use at the applicable AI Unit rate, unless you switch the agents or features off in SAP for Me first.
- Custom agents bill elsewhere. AI you build yourself is free to design. In production it is billed on compute, storage, transactions and AI tokens through the BTP Enterprise Agreement, as described in how BTP capacity units and cloud credits are calculated. SAP waives the Joule Studio runtime for custom agents through the end of 2026.
SAP also says most generative AI capabilities that now need AI Units will move into Base AI at no extra cost later in 2026. Per user packages will retire, except SAP Joule for Consultants, which is charged 35 AI Units per assigned user per month. That leaves agents as the main consumer of the balance.
SAP publishes no dollar price per AI Unit. The price you pay is whatever your order form says.
| Element | How it works | What it means for the budget |
|---|---|---|
| Base tier | Bundled capabilities that draw no units | The free floor. Know its boundary feature by feature, because the meter starts where it ends. |
| AI Unit | A prepaid credit drawn per action beyond Base, tenant wide | A budget built per user misses it entirely. |
| FUE allowance | A set number of actions per Advanced FUE, pooled tenant wide | It grows with headcount, while agent demand grows with schedules and process volume. |
| Overage | A per action rate for use past the prepaid balance and the allowance | The effective price, fixed at the order form and carried into every renewal. |
Why task complexity sets the draw
An interactive prompt draws little. A document extraction draws more. A scheduled agent that chains steps across a workflow draws at every step, on a timer, whether or not anyone is watching.
So the balance is sized by the draw profile of your roadmap. The average action tells you little, and a forecast built on chat volume will come in low.
The Meters: BTP Credits and AI Units
How does the AI allowance bundled with Advanced FUE work?
In the quotes we reviewed, SAP bundled roughly 200 AI actions with each Advanced FUE in the FUE subscription, pooled across the tenant. At chat volumes that pool looks like months of headroom. A few scheduled agents can spend it in weeks.
The correct use of the allowance is measurement. While consumption is free, record the real burn per capability and per agent. That record becomes the forecast you size the paid tier against, and it is the only evidence you will have at the negotiating table.
A worked example: 500 Advanced FUE
Take a hypothetical company with 500 Advanced FUE. The pool is 500 times 200, or 100,000 actions. We assume the allowance covers one contract year and that each prompt using a Premium generative feature draws one action. Prompts that stay in Joule Base draw nothing and are left out. Check both assumptions against your order form.
| Line | Actions per month | Actions per year |
|---|---|---|
| Premium chat: 200 users, 3 prompts a day, 21 working days | 12,600 | 151,200 |
| Three agents, each running every 15 minutes around the clock, 8 actions per run, 30 day months | 69,120 | 829,440 |
| Total demand | 81,720 | 980,640 |
| Pooled allowance (500 x 200) | 100,000 | |
| Actions past the allowance | 880,640 | |
| Overage at $0.08 per action | $70,451 | |
| Overage at $0.18 per action | $158,515 |
On chat alone, the pool lasts about 8 months, and the year ends 51,200 actions over, or $4,096 to $9,216 at the same rates. Add the three agents and the pool is gone in about five weeks. The agents account for 85 percent of the demand, and none of it shows up in a chat history.
At SAP's published rate of 0.02 units for each agent action, the agent line alone equals about 16,589 AI Units a year. Divide the dollar amount on your order form by that figure and you have your real price per agent action, which you can then compare with the overage rate.
Why we would not budget against the bundled allowance
The usual advice is to spend the included allowance first and buy AI Units once it runs out. We disagree, because by the time the pool is empty, the overage rate has been signed for the whole term.
In the renewals we reviewed, the first scheduled agents cleared the allowance in weeks, and everything after was billed at a rate no one had negotiated. Use the allowance as a pilot window instead: measure burn per agent while it is free, then size the paid tier and set the overage terms before you sign.
Enterprise AI Contract Negotiation Guide
The contract terms that keep AI consumption meters priced the way you forecast them, across SAP and other AI vendors.
Get the white paper →What do SAP AI Units cost once the allowance runs out?
Overage ran about $0.08 to $0.18 per action in the quotes we reviewed. The effective rate is set at the order form, and consumption only prices at whatever was signed. That means the negotiation window closes at signature, and in our reviews it mostly closed unused.
Three numbers decide your AI Unit economics, and all three are fixed when the order form is signed:
- The unit price on prepaid balances.
- The allowance treatment: whether it pools, rolls over or expires.
- The overage rate that prices everything past both.
Our Joule AI Units pillar covers the allowance arithmetic for agent runs, and the agents versus assistant cost analysis compares the two workloads in SAP detail.
Contract terms to ask for
- A written action definition. State what counts as an action and how it maps to SAP's published AI Unit rate for agents, so every invoice line can be checked.
- Allowance terms. Record the actions per Advanced FUE, the period they cover, that they pool tenant wide, and whether unused actions roll forward.
- A pinned unit price. Hold the AI Unit price for the full subscription term, including top up purchases made mid term.
- A capped overage rate. Set overage per action at or below the prepaid price per action, so running past the pool never costs more than planning for it.
- Consumption alerts and a ceiling. Require notice at agreed thresholds and written approval before use passes a set limit.
- Carry forward. Units expire after 12 months by default. Ask for unused units to roll into the next year or to run for the full term.
- Credit for features moving to Base. If units bought now pay for generative AI features that SAP shifts into Base later, ask for those units to be credited or reassigned to agents.
What the account team will say, and what to say back
- "The allowance will cover you in year one." Ask for the consumption model per agent on your roadmap, and for the allowance period and action definition in the order form. If the allowance covers you, those terms cost SAP nothing.
- "The overage rate is standard." It is printed on your order form, so it is a term like any other. Ask for it at or below the prepaid price per action, fixed for the term.
- "Commit to a larger block now for a better unit price." Units expire after 12 months. Commit after you have measured burn during the allowance window, with a price hold on later top ups.
- "Most generative AI is moving to Base, so this line is small." That concentrates the meter on agents, which is exactly where your roadmap is heading. It makes the agent rate the price to negotiate.
How should you forecast SAP AI Unit consumption?
Forecast bottom up from the agent roadmap: actions per agent workflow, at its scheduled frequency, weighted for complexity. Chat volume is a minor line. Buyers who priced units against interactive volume found the draw came from the agents on the roadmap, a forecasting error we have also seen with other vendors' AI consumption meters.
How to read your own consumption
- Register every agent. Record the owner, the trigger or schedule, and the typical number of steps per run.
- Pull the SAP for Me data weekly. Use the usage breakdown by package and the remaining balance, and keep your own copy of each week's figures. SAP for Me is also where you switch off an agent that is burning faster than planned.
- Compare measured burn with the register. Where an agent draws more than its step count suggests, ask SAP to explain the metering before the paid tier is sized.
- Charge back internally. The pool is tenant wide, so give each business unit its own line, or the first team to automate spends everyone's balance.
How the answer differs for a small and a large tenant
The allowance scales with Advanced FUE, but agent demand scales with process volume and schedules. The two rarely move together.
- 100 Advanced FUE. The pool is 20,000 actions. One agent running every 15 minutes at 8 actions per run draws 768 actions a day and empties the pool in 26 days on its own.
- 5,000 Advanced FUE. The pool is 1,000,000 actions. The same three agents plus Premium chat from 2,000 users draw about 195,120 actions a month, so the pool lasts about five months. Large buyers feel safe in year one, and the exposure arrives when several business units build agents in parallel against one balance.
What have we seen in SAP cloud renewals from 2024 to 2026?
Across roughly 35 to 45 SAP cloud renewals that I benchmarked between 2024 and 2026, the AI Unit balance was the least understood line in the quote. Two patterns came up again and again.
- Forecasts built on chat. Units were priced against interactive volume while the scheduled agents on the roadmap carried the real draw.
- Overage accepted as printed. In most quotes the overage rate went unnegotiated, and every later renewal inherited it.
The allowance is a free window to measure real burn. Budget against it and you will pay overage at a rate you never negotiated.
The pattern is not unique to SAP. Our token cost surge report traces the same sequence across other vendors' credit schemes: a consumption meter added beside seat subscriptions, forecast on interactive intuition, then repriced by automation no one modeled.
The July 2026 renewal changes raise the stakes on this line. Put the AI Unit meter at the front of the renewal file, next to the FUE count it rides on, and give it the same scrutiny.
What to do next
- Map the Base boundary. List each AI feature in use and mark which ones draw AI Units, since everything past Base spends the balance.
- Run the allowance as a pilot. Measure burn per capability and per agent while consumption is free, and never budget against the pool as a ceiling.
- Build the forecast from the agent roadmap. Count actions per workflow at scheduled frequency, and treat chat volume as a minor line.
- Negotiate before signature. Settle the pinned unit price, the overage cap, the allowance terms and carry forward in the order form.
- Price AI Units with the FUE count. Bring the line to the front of the renewal alongside the subscription it rides on. Our SAP practice can model the meter with you, working only for the customer.
Frequently asked questions
What is an SAP AI Unit?
It is SAP's virtual currency for Premium Business AI: a prepaid credit held in one pool for the tenant and drawn per action whenever a capability runs past the Base tier. Joule agents are the heaviest consumer. Because the pool is shared, the useful budget question is how often your workflows run, and headcount barely enters it.
How many AI Units come with SAP FUE subscriptions?
The quotes we reviewed bundled roughly 200 AI actions per Advanced FUE, pooled across the tenant. The allowance is stated in actions while purchased balances are stated in AI Units, so ask SAP to write the conversion and the allowance period into the order form. Then use the allowance to measure real burn before you size the paid tier.
What do SAP AI Units cost at overage?
Between $0.08 and $0.18 per action across the quotes we reviewed. SAP publishes no dollar price per AI Unit, so your rate is whatever the order form says. Most buyers we advised accepted the printed rate, and it became their real AI price as soon as automation used up the allowance.
How should we forecast SAP AI Unit consumption?
List every planned agent with its trigger, schedule and steps per run, multiply out to actions per month, and check the total against the burn you measure during the allowance window. Forecasts drawn from chat history came in well short once agents went live, in our benchmarks and in other vendors' credit schemes.
When can the AI Unit price be negotiated?
Only before the order form is signed. After that, every action is priced at the signed rate for the term. Ask for a pinned unit price that also covers top ups, an overage rate capped at or below it, and the allowance terms in writing, and negotiate them together with the FUE subscription the units ride on.
Why did our AI Unit balance run out so fast?
Almost always scheduled agents. They draw complexity weighted actions on timers, through nights and weekends, at rates interactive users never reach, so a pool that looked like months of headroom clears in weeks. Build the bottom up forecast now and renegotiate the tier before the overage rate compounds the surprise.
Do SAP AI Units expire?
Yes. SAP sells AI Units annually and unused units expire after 12 months under its published terms. Buying a large block early to secure a lower unit price can waste money if agents go live later than planned. Ask for carry forward into the next year, or buy the first year's units after you have measured real burn.
Is there a list price for one SAP AI Unit?
SAP does not publish one. Its pricing page gives consumption rates, such as 0.02 AI Units per Joule agent action, which means one unit covers 50 agent actions. The dollar price per unit is set in each order form, so work out the effective price per action you are offered and compare it with the overage rate.