In an SAP licence measurement,
the customer states the number.
In SAP’s cloud general terms, the Verification of Use clause states that the customer monitors its own use and reports anything in excess of the contracted usage metrics and volume; SAP may monitor to verify. On-premise, the SAP Software Use Rights allow SAP to audit use, in general once a year, by system measurement, and the customer may conduct that measurement with SAP’s tools unaltered. The word audit does not appear in the cloud general terms read for this analysis: the verification mechanism is the Verification of Use clause. In both contract families, the declared number comes from the customer’s side. The rule ends at consumption-based BTP, where, according to SAP’s documentation, the billed number comes from SAP’s metering.
The duty to report is the customer’s.
In the private cloud, SAP triggers automated user measurement every month. The contractual duty to monitor and report use is the customer’s. The table also covers the public cloud, purchase through a partner, and consumption-based BTP, the one model where the documentation read describes no declaration.
| Model | Who triggers the measurement | Who declares | What the contract provides |
|---|---|---|---|
| SAP Cloud ERP Private (private cloud) | SAP, every month, automatically | The customer, which reports use above what was contracted | Verification of Use: the customer monitors its own use and reports any excess; SAP may monitor to verify |
| S/4HANA Cloud Public Edition and GROW with SAP (public cloud) | The contract documents read name no measurement instrument. | The customer, which reports use above what was contracted; the metric depends on the Order Form line (User, or in GROW the FUE, a unit that weights user types). In GROW, according to SAP Knowledge Base Articles (KBAs), the system assigns each user a price category derived from the business roles it is given; on Alkemia’s reading, the company checks the declared allocation against that category | Verification of Use, where the Order Form incorporates the general terms; the customer monitors user IDs across systems, and use above what was contracted caused by duplicated IDs may lead to additional fees |
| On-premise | SAP, when it audits; the customer may conduct the measurement with SAP’s tools unaltered | The customer, in a self-declaration completed independently of the technical measurement function modules | SAP may audit use, in general once a year, by system measurement |
| Cloud bought through a partner | Not addressed in the terms read | The customer, who reports any excess to the partner | SAP may forward data on use in excess to the partner |
| Consumption-based BTP (BTPEA and CPEA, with prepaid cloud credits, and Pay-As-You-Go) | SAP meters the consumption | The documentation read describes no declaration: the monthly balance statement carries the cost | In the sample Order Form, consumption sits outside the subscription’s Excess Use clause; the consumption terms of an executed contract were not read |
Each row rests on SAP documents, given in the sources.
The trap is inferring the duty from who operates the meter. The clause does not say whether an automated SAP measurement discharges the customer’s obligation to monitor and report. On Alkemia’s reading, it does not: in the private cloud, the meter classifies users from the authorisations the customer maintains, and the clause asks the customer itself to report use in excess. That reading joins a contract term to an operational fact, which is why it is worth confirming against the company’s own contract, with counsel.
What changes when the number is the company’s declaration, and where it stops being one.
- A
A declared figure needs its own derivation
On Alkemia’s reading, the independence requirement reaches the route to the figure.
The SAP Software Use Rights require the self-declaration form to be completed independently of the technical measurement function modules. On Alkemia’s reading, using the value the tool returned as a substitute for the company’s own determination is what that sentence rules out. Every self-declared figure (for example revenue, spend or headcount) needs to arrive with the calculation and source behind it: the business system, the period and the entity scope. In GROW, the customer allocates FUE across use packages, and, according to SAP KBAs, the system assigns each user a price category from the business roles it is given; on Alkemia’s reading, the declared allocation calls for its own derivation, checked user by user against that category. The Software Use Rights sentence is in the current global edition; each company’s contract incorporates a specific edition, and the Order Form is where to read which one.
- B
In the cloud, contracted volume does not shrink mid-term
The contracted commitment holds until the end of the term.
The cloud general terms state that the customer may not reduce the contracted usage metrics during the subscription term and that Order Forms are non-cancellable. The rule concerns the contracted metrics: using less during the term does not reduce what was contracted. In GROW, the FUE allocation across use packages can change during the term, with the contracted total retained and no FUE divided between use package types. On Alkemia’s reading, any move on a subscription that depends on giving contracted volume back waits for renewal.
- C
The partner’s contract with SAP can reach your use
Whoever runs the measurement or sees the draft comes to know the figure.
Under the SAP PartnerEdge General Terms and Conditions published for Latin America, a partner that becomes aware of any third party using an SAP product without authorisation, including one of the partner’s own customers using it beyond licensed levels, must inform SAP without undue delay, assist SAP in pursuing its rights, and temporarily stop providing SAP products to that third party until the matter is resolved to the partner’s and SAP’s satisfaction. The definition of SAP products includes cloud services, subscriptions and maintenance. On Alkemia’s reading, an extract or a draft position seen by a partner’s staff can reach SAP through the partner’s own contract. The case of a company that bought direct and whose environment the partner only operates depends on reading its excess as unauthorised use by a third party, and that is the interpretive step in this reading. The documents the partner signed take precedence over these general terms, and whether the customer’s agreement with the partner can limit what it discloses is a question for counsel.
- D
On consumption-based BTP, the lever moves
On Alkemia’s reading, when SAP produces the number, control lies in consumption and reconciliation.
For BTP’s consumption-based models, SAP’s documentation describes a monthly balance statement with the cost of each service, and it is that statement that carries the binding cost information; the cockpit figures are informational. Under BTPEA and CPEA, the month’s cost is deducted from prepaid cloud credits, overages are billed in arrears at list price, and a top-up buys additional coverage without undoing consumption that has already happened. For the CPEA, SAP’s public FAQ (March 2026), operational documentation to be confirmed against the Order Form, adds that unused cloud credits expire at the end of each annual credit period, that this list price is subject to the price guarantee, and that the balance statement goes to the commercial contact named in the CPEA. On Alkemia’s reading, credit still unused at the end of the period is prepaid money lost, in the same way that an overage is an additional charge. Pay-As-You-Go has no credit balance: billing is monthly, in arrears. In all three, according to the same documentation, a budget set in the cockpit does not stop consumption when it is exceeded. According to SAP’s documentation, the global account is the only contractually billable entity; subaccount figures serve internal allocation. On Alkemia’s reading, the company’s lever here is governance within the month and monthly reconciliation. Whether the general terms’ duty to monitor and report applies to a number SAP itself produces is not written in the documents read, and is a question for counsel.
On subscriptions and on-premise, the part of a measurement the company controls is the declaration. It is also the part the company answers for, and the one that travels with it into the cycles that follow.
Alkemia’s reading
A licensing position has two sides.
Counting only the exposure hands the company half of the ledger. The position that is useful in a negotiation also records unclaimed value, such as unused licences and contracted rights nobody exercises.
Self-declaration shows both sides at once. On Alkemia’s reading, a declaration nobody can reconstruct is exposure, because the company cannot defend it. It is also value possibly lost, because it may be overstated and nobody can show that either. That is why preparation concentrates on what the company declares, and on building the evidence for the true figure from the business system, the period and the entity scope.
Five points to decide before the measurement.
- 01
Incorporated edition
Which edition of the SAP Software Use Rights, or of the cloud general terms, your Order Form incorporates, and whether it stays fixed or follows the current edition. The independent self-declaration requirement applies to a company whose contract carries an edition that contains it.
- 02
An owner for every declared figure
For each self-declared metric, and for the FUE allocation in GROW, who derives the value, from which system, period and entity scope, with the calculation kept. In GROW, according to SAP KBAs, the system assigns each user a price category (Core, Advanced or Self-Service) derived from the business roles, the access profiles assigned to that user: check the declared allocation against that category and record where the two diverge. If the category corresponds to the contract’s use package (the type of access each FUE entitles), which the documents read do not establish, on Alkemia’s reading the split across use packages is controlled through role design. A declaration nobody can reconstruct cannot be defended.
- 03
Who runs the extracts and who sees the draft
If an SAP partner operates your environment, assess with counsel who executes the measurement and who receives the preliminary position. The partner’s contract with SAP obliges it to report unauthorised use, subject to the documents it signed; on Alkemia’s reading, whether a direct buyer’s excess falls under that obligation depends on the interpretive step described in consequence C.
- 04
Users before each cycle
In the private cloud, the meter SAP triggers classifies users from the authorisations the customer maintains, and those authorisations must fit the user types. In the public cloud, with more than one system, the Service Use Descriptions require user IDs to be monitored across them, through Central User Administration or manually. Who reviews this before each cycle, and with what evidence.
- 05
Consumption and reconciliation on BTP
If the company runs consumption-based BTP: who watches budgets and thresholds within the month (and, under the CPEA, the credit balance that, according to SAP’s public FAQ, expires at the end of each annual credit period), who reconciles each balance statement at global-account level (against the Order Form’s credits under BTPEA and CPEA, against consumption and the applicable prices under Pay-As-You-Go), and who raises a dispute in time. Under the direct-sale cloud general terms read (section 5.2), where the Order Form incorporates them, the window is 1 month from the invoice date, and the undisputed portion remains payable; whether it applies to the BTP balance statement is a point to check in the contract; on a purchase through a partner, the instrument signed with the partner governs.
Each company is governed by the contract it signed. Validate each point against your Order Form and the editions it incorporates, with legal and licensing support.
Know the position before SAP measures it.
A pre-audit establishes the licensing position before the measurement: exposure and unclaimed value, as a range with a stated confidence, read from the company’s own contracts and extracts. Every extract runs in the customer’s environment. Alkemia holds no SAP PartnerEdge agreement and does not deliver the pre-audit through an entity that holds one.
Discuss your decisioncontact@alkemia.io
The contractual claims come from documents SAP publishes.
SAP licence measurement, in contract terms.
- Who is responsible for measuring SAP licence use?
- It depends on the contract family and the commercial model. On a cloud subscription, the Verification of Use clause places the duty on the customer: it monitors its own use and reports anything in excess of the contracted usage metrics and volume, and SAP may monitor to verify. On-premise, SAP may audit by system measurement, the customer may conduct that measurement with SAP’s tools unaltered, and the self-declaration, which is the customer’s, is completed independently of the technical measurement. On consumption-based BTP, according to SAP’s documentation, the billed number comes from SAP’s metering.
- Do SAP’s cloud general terms provide for an audit?
- The word audit does not appear in the cloud general terms read for this analysis. The verification mechanism is the Verification of Use clause, and that heading is the one to locate in the company’s own contract.
- Can usage metrics on an SAP cloud subscription be reduced during the term?
- The cloud general terms say they cannot: the customer may not reduce the contracted usage metrics during the subscription term, and Order Forms are non-cancellable. Using less during the term does not reduce the contracted volume, and in GROW the FUE allocation across use packages can change, with the contracted total retained and no FUE divided between use package types.
- In S/4HANA Cloud Public Edition, who is accountable for use?
- The contract documents read name no measurement instrument for the public edition. The duty is unchanged: monitoring and reporting comes from the Verification of Use clause, where the Order Form incorporates the cloud general terms. The Service Use Descriptions add a duty of their own: with several systems, the customer monitors user IDs across them, through Central User Administration or manually, and use above what was contracted caused by duplicated IDs may lead to additional fees.
- On consumption-based BTP, does the customer declare use?
- The SAP documentation read for this analysis describes no declaration: SAP meters the consumption and the monthly balance statement carries the cost, which under BTPEA and CPEA is deducted from prepaid cloud credits and under Pay-As-You-Go is billed monthly in arrears. For the CPEA, according to SAP’s public FAQ (March 2026), unused credits expire at the end of each annual period, and the balance statement goes to the commercial contact named in the CPEA. Whether the cloud general terms’ duty to report applies to that number is not written in the documents read, and is a question for counsel.
- Can an SAP partner that sees my environment inform SAP about excess use?
- The SAP PartnerEdge General Terms and Conditions for Latin America oblige a partner that becomes aware of unauthorised use by any third party, including use by one of the partner’s own customers beyond licensed levels, to inform SAP without undue delay. For a company that bought direct and whose environment the partner only operates, the obligation depends on reading its excess as unauthorised use by a third party, which is Alkemia’s reading. The specific documents the partner signed take precedence over these general terms, and the reach in each case is a question for counsel.
This analysis reads contract terms published by SAP. The mechanics of consumption-based BTP and what SAP’s tools show come from SAP public documentation listed in the sources. It is a reading of terms and documentation, to be confirmed with legal and licensing support; each company is governed by the contract it signed, including the edition its Order Form incorporates. Readings identified as Alkemia’s are inferences and should be confirmed with counsel.
SAP and the SAP product names mentioned are trademarks of SAP SE or its affiliates. Alkemia does not speak for SAP.