License S/4HANA embedded features against your contract, not against what the system lets you switch on. Embedded is not the same as entitled.

Across 25 to 40 SAP S/4HANA license reviews in 2024 to 2025, embedded features active without a matching entitlement drove six figure audit findings on estates that believed they were fully compliant.

Prepared by Redress Compliance · June 2026 · Representative SAP estate scenario (benchmark scenario, not a quote).

Embedded means a feature ships inside the core system, not that it is free to use. Some embedded features are fully covered by your S/4HANA entitlement. Others are present and switchable, yet still need a separate license once you turn them on. The first job is to sort the two.

The line is not the user interface. Two features can sit side by side in the same Fiori launchpad, one covered and one chargeable. The line is the contract scope and the metric SAP measures. Use the table below as the starting map, then confirm each row against your own agreement.

Why does the included line move with your contract?

The same feature can be included on one agreement and chargeable on another. A cloud subscription bundles more than a brought forward on premises contract. A premium tier includes AI capacity a base tier does not. So the map is contract specific, and a peer benchmark is a guide, not a ruling.

What is the first non obvious mechanic to name?

Activation is the trigger, not heavy use. A feature switched on once and barely used can still register in the measurement and still carry a back charge from the activation date. Treat the on switch as the licensable event.

S/4HANA Embedded Analytics is included with your S/4HANA license and needs no separate subscription. It runs on core data model views and serves operational reporting inside the transactional system. For day to day analytics on live data, it is the covered route.

The risk starts when the project reaches for more. Standalone SAP Analytics Cloud for planning, enterprise dashboards, and blended sources is a separate named user subscription. SAP BW and BW/4HANA for a governed warehouse are separate products too. The table draws the four way line.

The contrarian read on duplication runs the other way too. Many estates buy standalone SAC seats for users who only ever touch operational reporting that Embedded Analytics already covers. That is paid twice. Map users to the route they actually use before you renew either line.

How do you keep the analytics line clean?

• Segment users: separate operational reporting users from planning and dashboard users before assigning any SAC seat.
• Tag the source: confirm whether a report runs on core views or on a separate warehouse, because that decides the license.
• Gate the upgrade: require a license check before a project promotes a covered report into a standalone tool.

Base AI is included and premium AI is metered. SAP Business AI Base, including Joule Base, ships with S/4HANA Cloud Public Edition and the RISE base and premium tiers at no extra charge. It covers navigational, informational, and simple analytical assistance built into the product.

The metered line is the AI Unit. Premium features, advanced analytical assistance, and agent actions consume AI Units, a consumption metric that measures model calls, document processing, and inference. Base allotments are modest. Premium use can run well past them, and the overage is billable.

Figure 2. Premium AI features draw AI Units past the included base allotment; the 180,000 unit overage is billable (benchmark scenario, not a quote).

The non obvious mechanic is that AI Units are a burn down balance, not a flat right to use. Once consumption passes the included allotment, every further premium action draws billable units. A pilot that scales without a cap turns a free trial into a renewal line item.

How do you control AI Unit exposure?

• Meter before scale: measure unit consumption in a pilot before any enterprise rollout of premium features.
• Separate base from premium: keep teams on base scenarios unless a premium feature has a funded business case.
• Pre commit deliberately: commit a unit volume only at a price that drops with size, never on an open ended draw.

Process automation is partly included and partly separate. In RISE with S/4HANA Cloud Private Edition, SAP Build entitlements for Build Apps, Build Process Automation, and Build Work Zone scale with your licensed Full Use Equivalent count. The entitlement is real, but it is sized, not unlimited.

Beyond the bundled scope, the BTP platform meters consumption. The cloud platform draws on a credit pool, commonly set at one percent of net annual contract value with a defined minimum and maximum. SAP Signavio for process mining and redesign is a separate license that does not come with S/4HANA at all.

The trap here is treating SAP Build as free because it appears in the cloud bundle. The entitlement scales with FUE, so a heavy automation program on a small user base can exhaust the sized allotment and push consumption onto the credit pool. Size the program against the entitlement before you build.

Digital access is licensed on documents, not on who or what created them. SAP defines nine document types that count: sales orders, purchase orders, invoices, deliveries, material documents, service and maintenance documents, manufacturing orders, quality management documents, and time management documents. An embedded automation that creates one of these creates a counted document.

That is the indirect path most teams miss. A workflow, a bot, or an interface that posts an order is the same chargeable event as a user keying it, because the document is what counts. The exposure is the document volume through every path, direct and embedded.

Figure 3. Counting every embedded document inflates exposure; mapping to creating source cuts the billable base by about two thirds (benchmark scenario, not a quote).

The contrarian move is to attack the count before the price. Most negotiations argue the per document rate, which is negotiable, yet a corrected document count of 1.1 million instead of a raw 3.2 million is the larger lever. Removing chained and duplicate documents through source mapping cuts the billable base by about two thirds in the worked estate.

How do you control the document count?

• Map by source: attribute each document to the creating event, then exclude chained and duplicate records.
• Decide the model: compare digital access against traditional licensing and pick the cheaper basis for your volume.
• Fix the unit price early: negotiate the per document rate under the adoption program before volume rises at renewal.

Numbers make the risk concrete. The worked estate below is Meridian Components, a representative 4,500 user manufacturing business on a RISE private edition conversion. It is a benchmark scenario, not a quote, sized to show how the three embedded paths compound over three years.

Figure 1. Representative three year exposure of $420K, built from the section 6 worked estate (benchmark scenario, not a quote).

Read the totals as cumulative. The annual run rate is about $140,000 across the three paths, so by year three the back charge reaches $420,000 if nothing is mapped or licensed. The figure is not a penalty rate; it is the list value of usage that was always measurable.

Where the common advice on embedded features is wrong

The standard advice is that if a feature ships inside S/4HANA you are entitled to use it, so activation is safe. We disagree. In the reviews Fredrik ran in 2024 to 2025, embedded and entitled were treated as the same thing in roughly three out of four estates, and that assumption produced the largest audit findings.

The counter move is to separate what is technically available from what your contract actually grants, then gate activation against entitlement. A feature present in S/4HANA is not your contract granting the right to use it. The gap is exactly where measurement runs land.

The conversion to S/4HANA or RISE is the one moment you can reset the embedded line. Once signed, the bundle scope and the metrics are fixed until the next renewal. Use the window to price embedded and separate the way you actually use them, not the way the opening quote assumes.

Three levers move the outcome more than the list price. Each is a contract mechanic, not a discount ask.

• Scope disaggregation: require the bundle broken into priced components so embedded analytics, AI capacity, and automation can be benchmarked separately.
• Entitlement substitution: convert unused on premises rights into the embedded scope you will actually use, rather than buying it new.
• Count correction: fix the digital access document count and unit price in the contract before volume grows post go live.