The SAP license position statement is the document that, more than any other, determines what the buyer-side negotiation can achieve. It is the document that procurement uses to ask for what it asks for, that counsel uses to set the defensive boundary, and that the independent advisor uses to size the engagement. It is also the document that most procurement functions treat as a reporting artefact rather than as a commercial instrument. The difference between a position statement built as an instrument and one built as a report is, in our portfolio, a consistent multiple on the negotiation outcome.
What the statement is
The license position statement is a one-document summary of the buyer's SAP entitlements, current use, the gap between them, and the strategic options that follow from the gap. It is built from underlying measurement data (USMM, LAW, engine measurements, the topology map) and from contract analysis (entitlements, restrictions, exclusions, carve-outs). The statement is not a measurement extract; it is the interpretation of the measurement against the contract.
The statement is signed by the named SAM owner and counter-signed by the procurement category owner. Sign-off is the procedural step that makes the statement load-bearing inside the buyer organisation.
The three reading purposes
The statement is read by three audiences, each with different needs. The Chief Procurement Officer reads it for the commercial framing: what is the SAP relationship worth, what is the optimisation opportunity, what is the audit exposure. The General Counsel reads it for the legal framing: what is the contract footprint, what is the indirect-access exposure, what is the defensive position. The independent advisor reads it for the engagement framing: what is the buyer's position, what is the negotiation lever, what is the settlement target.
A statement built well serves all three reading purposes. A statement built poorly serves only the SAM team that produced it.
The entitlement section
The entitlement section sets out every SAP entitlement the buyer holds, reconciled against the contracts that grant them. The reconciliation is line by line: each entitlement is mapped to the contract document, the line item, and the date of the entitlement. Entitlements with restrictions (territory, affiliate, use case) carry the restriction in the entitlement record.
The discipline here matters because audit findings turn on entitlement restrictions more than buyers expect. The SAP contract sometimes restricts a named-user license to a particular legal entity or geography. Use of the license outside that restriction is, in the audit framing, unlicensed use. The entitlement section is the document that surfaces those restrictions before the audit does.
The use section
The use section sets out current operational use of SAP, reconciled against the measurement data. Named-user use is reconciled against USMM. Engine use is reconciled against the engine measurements. Document-based use is reconciled against the digital-access count. Indirect use is reconciled against the integration topology map.
The reconciliation is dated, signed, and footnoted with the data sources. The dated reconciliation is the document that becomes the buyer's position in the next audit. A use section that is six months old is a use section that no longer reflects the operational environment and that SAP will discount in any negotiating context.
The gap section
The gap section is the analytical heart of the statement. For each entitlement class, the section identifies the gap between entitlement and use. Two kinds of gaps are documented. Shelfware is the case where entitlement exceeds use; the gap is a candidate for contraction in the next renewal. Exposure is the case where use exceeds entitlement; the gap is a candidate for either remediation or settlement.
The gap section is also where the buyer-side reading of contested measurements lives. If SAP's USMM extract would produce an exposure number that the buyer disputes (because of role-mapping disagreements, because of named-user reclassification arguments, because of carve-out interpretations), the gap section documents both the SAP-framing number and the buyer-framing number, with the analytical bridge between them.
The shelfware opportunity
Shelfware is the part of the gap section that procurement teams underinvest in. A renewal negotiation that surfaces three years of accumulated shelfware as a candidate for contraction routinely lands a discount that is larger than the headline renewal discount. The position statement is the document that makes the shelfware case visible. Without the statement, shelfware accumulates inside the cost base.
The exposure calculation
Exposure is the part of the gap section that the audit conversation turns on. Each exposure item is sized in three numbers: the SAP-framing claim value at list price, the SAP-framing claim value at the buyer's negotiated discount, and the buyer-framing settlement target. The three-number framing is the buyer-side analytical structure for every audit negotiation.
The options section
The options section sets out the commercial pathways available given the entitlement and gap analysis. Standard option categories are: renewal-with-contraction (shelfware reduction at renewal), conversion-to-digital-access (indirect exposure converted to document-based licensing), RISE conversion (on-premise estate converted to cloud subscription), competitive replacement (estate moved off SAP for specific use cases), and run-on-lapsed-maintenance (maintenance paid in arrears with deferral leverage).
Each option is sized in three-year forward economic terms. The sizing is not precise; it is directional. The directional sizing is what the procurement leadership uses to decide which conversation to open first.
The refresh cadence
The statement is refreshed on a defined cadence. The minimum cadence is annual, before the buyer's fiscal-year planning cycle. The recommended cadence is quarterly, with a full re-baseline annually. Buyers in active migration windows or post-acquisition integration windows refresh more often.
The discipline of the refresh cadence is the part of the position statement program that creates compounding value. A statement refreshed quarterly produces fewer surprises in the audit cycle, fewer last-minute commitments in the renewal cycle, and fewer concessions in the indirect-access cycle. The compounding effect is documented in our pillar on SAP license compliance.
The ownership question
The statement is owned by the SAM lead, but the operational drafting is typically distributed across the SAM team, the basis team, the integration architects, and counsel. The independent advisor is involved as a reviewer and as the analytical lead on contested measurements. The named owner is responsible for the sign-off and for keeping the statement live between refresh cycles.
Where the ownership question goes wrong, it goes wrong in two directions. Either the statement is owned by a SAM team without procurement involvement, in which case the commercial framing is missing. Or the statement is owned by a procurement function without SAM involvement, in which case the measurement reconciliation is missing. The successful model in our portfolio is dual ownership with a single named lead.
The filing question
The statement is filed in a defined location with restricted access. The restriction is procedural: the statement contains the buyer's negotiating position, and the position is not for distribution outside the named audit team. The filing location is set out in the readiness program and is the document that the independent advisor accesses on each refresh.
What the statement becomes in a negotiation
In an audit negotiation, the statement becomes the buyer's substantive position paper. In a renewal negotiation, the statement becomes the basis for the contraction conversation. In an indirect-access conversation, the statement becomes the topology framing. In an S/4HANA migration, the statement becomes the conversion sizing. In each case, the statement is the document that anchors the buyer's position and that the SAP framing has to engage with.
For context, the License Optimization Framework white paper sets out the analytical structure behind the statement, and the tech firm true-up case file documents the use of the statement in a SuccessFactors negotiation that landed at a forty-seven per cent reduction.
The position statement is the cheapest document in the buyer's portfolio that produces the largest negotiating effect. Built once, refreshed quarterly, signed by the named owner. The discipline is procedural, not analytical.
If your organisation does not have a current position statement, the first work is the entitlement reconciliation. Our license compliance assessment service sets out how we structure that work, and the S/4HANA topic page covers the migration-specific extensions of the position document.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.