Analytics Legends logoAI & Analytics Legends
Menu
Sign inSign up
Guide

SAP AI Units pricing: what one unit buys, how the pool works and how to size it

As of 2026-10-30

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

SAP AI Units are the single prepaid currency for SAP's Premium AI. They are bought annually, sit in one shared pool per customer, are drawn down only when Premium AI actually performs work, and expire after twelve months if unused. SAP publishes the consumption rates in AI Units, for example 0.02 AI Units per SAP-delivered agent action in 2026, but no general price in euros per unit: the currency price is in your contract. The work is therefore to forecast consumption, not to look up a tariff.

Looking for a ? Cédric Mary, SAP AI & Analytics Architect & Team Lead, takes SAP Business AI, Joule and Business Data Cloud missions.

What SAP publishes about AI Units, and what it does not

Published by SAP: the unit itself, purchased annually under SKU 8019164 according to SAP's Business AI pricing FAQ; the rule that one pool serves every Premium AI capability; the twelve-month expiry; and a list of consumption rates per capability, expressed in AI Units, in the SAP Discovery Center AI catalogue.

Not published: a general currency price per AI Unit, a volume discount curve, or a multi-year price commitment. The only currency figure on an SAP page is a worked example on the Joule for Consultants product page, read on 23 September 2026, which prices one AI Unit at EUR 7 for illustration. Use it to sanity-check orders of magnitude, never as a quote.

SAP also marks its rates as subject to change. The Business AI commercial model has already been restructured once in 2026, so any figure on this page is dated, and should be re-read against the SAP pricing page before a proposal.

The published rates, per capability

Joule Agents: each SAP-delivered agent action consumes 0.02 AI Units in 2026. An action is one step, such as calling a service, triggering a workflow or generating a response, and a task can take several. Joule Assistants, which orchestrate agents, carry no separate charge.

SAP Joule for Consultants: 35 AI Units per assigned user per month, with a pooled allowance of 22,900 requests per user per month, then 2 AI Units per 1,000 requests beyond the pool. The Joule for Consultants page states that units are sold in blocks of 100.

AI features such as Document AI or Document Grounding: charged per request or per record, at the rate the Discovery Center catalogue lists for each feature.

Joule Base and embedded Base AI: no AI Units at all. A one-time, zero-euro entitlement, SKU 8019544, accepts SAP's AI terms; a customer already holding the AI Units SKU skips it.

What AI Units do not pay for: custom AI you build and run on SAP AI Core, which is metered in BTP capacity units against your BTP contract, and BDC or Datasphere capacity units. These are three different meters, and they never convert into each other.

How the pool behaves: one balance, twelve months, no rollover

Every Premium AI capability draws on the same balance. A Document AI extraction, an agent action and a Joule for Consultants seat all reduce one number. For a buyer this has two consequences.

First, forecast at estate level, not per product. A team that sizes its agents in isolation, while another team switches on a document feature, will find the shared pool empty months early.

Second, size to measured consumption. Units bought in a large first-year block and not consumed are lost at month twelve; nothing rolls over into the next contract year. A small first purchase, a monthly review and a top-up is cheaper than a generous block that expires.

The consumption view sits in SAP for Me under Finance & Legal, Business AI. It shows the balance, monthly consumption by product and feature, and units approaching expiry, with a daily refresh. It does not split consumption by user, or production versus test, so a team that needs that split must instrument it on its own side. Buying the units into the wrong BTP global account is a documented pitfall: check the account before the order is placed.

Decision table: sizing an AI Units purchase

Only Joule Base and embedded AI in use — Units needed: none · Action: accept SKU 8019544 and stop there.

Agents in a pilot — Units needed: actions per task × tasks per month × 0.02 × 12 · Action: measure actions per completed task in the pilot before ordering at scale.

Multi-agent design, an orchestrator calling sub-agents — Units needed: the single-agent estimate × the measured fan-out · Action: count every hand-off and tool call, each is a billed action.

Consultants on Joule for Consultants — Units needed: 35 × assigned users × months, rounded up to the next block of 100 · Action: adjust assigned users monthly, SAP allows it.

Document-heavy process — Units needed: documents per year × the per-record rate in the Discovery Center · Action: read the rate for the exact feature, not a neighbouring one.

Several of the above in one estate — Units needed: the sum, one pool · Action: one owner for the forecast and a monthly balance check.

Worked examples, with SAP's figures and ours kept apart

SAP's own example, on the Joule for Consultants page: 5 consultants × 12 months × 35 AI Units = 2,100 AI Units, priced there at EUR 14,700 at the EUR 7 example rate. For a single consultant, 12 months need 420 AI Units; units sold in blocks of 100 mean the buyer orders 500, so 80 units expire unused if nothing else draws on the pool.

An agent case, as our arithmetic and not an SAP quotation: 20,000 tasks a year at an assumed 6 actions each is 120,000 actions × 0.02 = 2,400 AI Units. If the design turns out to fan out to three sub-agents and each task really takes 18 actions, the same volume needs 7,200 AI Units. The assumption that moves the number is the action count per task, never the number of users.

Put both on one pool and the forecast is 2,100 + 2,400 = 4,500 AI Units for the year, with the agent line carrying the uncertainty. That is the line to pilot and measure before the order.

What SAP TechEd 2026 changed, and did not

SAP's TechEd press release of 27 October 2026 announced a time-bound promotion: for select customers, deploying and running custom agents on the SAP-managed Joule Studio runtime is free until December 2026, and design-time tooling remains free under fair-use limits. It also introduced tooling to manage AI value and consumption. It published no new AI Unit rate; the 0.02 rate per agent action remains the only published agent rate in the sources we reviewed.

The agent catalogue is what grows. SAP announced 40 assistants and 300 agents between SAP and its partners at TechEd (SAP News, 28 October 2026). More agents on offer means more ways to consume the same pool, so the forecast deserves a refresh each time a new agent is switched on.

For the full Joule picture, from Joule Base to Joule for Consultants, read the SAP Joule pricing guide; for the custom-agent side, the Joule Studio pricing guide.

What we cannot assert

SAP publishes no currency price per AI Unit, no discount curve and no rate beyond 2026; the EUR 7 figure is a worked example on an SAP product page, read on 23 September 2026. The action count per task for a given agent is not published, and the per-record rates of individual AI features must be read in the Discovery Center catalogue at the time of purchase. We could not fetch sap.com directly (HTTP 403); rates come from the platform's concept cards, which cite SAP's pricing FAQ and July 2026 commercial-model whitepaper.

Frequently asked

How much does one SAP AI Unit cost?

SAP publishes no general currency price per AI Unit; it is set in your contract. The only figure on an SAP page is a worked example on the Joule for Consultants product page, read on 23 September 2026, that uses EUR 7 per unit for illustration.

Do SAP AI Units expire?

Yes. According to SAP's pricing FAQ, AI Units are purchased annually and expire after twelve months if unused. Nothing rolls over, so size the purchase to measured consumption and review the balance monthly in SAP for Me.

How many AI Units does a Joule agent use?

Each SAP-delivered agent action consumes 0.02 AI Units in 2026. A task can take several actions, and an orchestrating agent calling sub-agents multiplies them, so measure actions per completed task in a pilot.

Are AI Units the same as BTP capacity units?

No. AI Units pay for SAP's Premium AI. Custom AI on SAP AI Core is metered in BTP capacity units against the BTP contract, and BDC or Datasphere use their own capacity units. The meters do not convert into each other.

Does Joule need AI Units?

Joule Base, the assistant that finds, navigates and guides, needs none: it is included in SAP cloud subscriptions after a zero-euro entitlement, SKU 8019544. Joule Agents, AI features and Joule for Consultants consume AI Units.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

Open missions

120 live roles and contracts in SAP AI & Joule right now — see the SAP AI & Joule missions · freelance SAP contracts.