SAP S/4HANA licensing replaces the legacy named-user catalogue with a single composite metric: the Full Use Equivalent, or FUE. Every legacy named-user category translates into a fractional FUE through a weighting matrix that SAP publishes in the Digital Access and Cloud Service Description. The conversion proposal that arrives at the procurement desk is the arithmetic output of that matrix applied to the current entitlement. Understanding the matrix is the prerequisite for understanding the proposal. Negotiating the proposal is the application of the levers documented below. The full advisory frame is covered in our S/4HANA migration compliance service.
The weighting matrix
The FUE matrix maps each legacy named-user category to a fractional FUE value. The published ratios are the starting point for every conversion proposal SAP generates.
Advanced Use
Professional, Developer, and equivalent legacy categories map at one to one. One legacy Professional licence consumes one FUE under the S/4HANA model. The category captures the heaviest users and accounts for the largest share of the FUE total in most estates.
Core Use
Limited Professional, Functional, and equivalent legacy categories map at approximately five to one. Five legacy Limited Professional licences consume one FUE. The fraction is the principal economic lever in the conversion arithmetic and the most overlooked.
Self-Service Use
Employee, Employee Self-Service, and equivalent legacy categories map at approximately thirty to one. Thirty legacy ESS licences consume one FUE. The ratio rewards estates that have reclassified to ESS prior to conversion and penalises estates that have not.
The arithmetic on a worked example
Consider an estate with 2,000 Professional licences, 6,000 Limited Professional licences, and 9,000 Employee licences. The FUE calculation is 2,000 plus 1,200 plus 300, for a total of 3,500 FUE. The conversion proposal will be priced at 3,500 FUE multiplied by the per-FUE subscription rate, with the rate dependent on the deployment model and the contract term. The total subscription line is therefore the product of three numbers: the FUE count, the per-FUE rate, and the term length.
The arithmetic is simple. Each of the three numbers is negotiable. The conversion proposal that arrives at the desk has been optimised for SAP’s revenue, not for the buyer’s consumption. Restating each number against actual usage is the heart of the negotiation.
Lever one — reclassification before conversion
Every reclassification from Professional to Limited Professional is a four-fifths reduction in the FUE consumed. Every reclassification from Limited Professional to ESS is a five-sixths further reduction. A reclassification programme run before the conversion proposal is generated changes the input to the matrix and therefore the output. Estates that defer reclassification to after the conversion frequently find the post-conversion reclassification economically less effective because the FUE quantum is already contractually locked. See the named-user reclassification playbook for the procedure and the classification rules article for the underlying logic.
Lever two — harvest before conversion
Legacy entitlements that are not in use are still counted in the conversion baseline if they are not surrendered before the conversion. The dormant 800 Professional licences in the example above contribute 800 FUE to the total. A pre-conversion harvest of the dormant tail reduces the FUE quantum directly. The licence harvesting article sets out the harvest methodology. The dormant-user cleanup article covers the detection step.
Lever three — contract term
The per-FUE rate is term-dependent. SAP offers reductions for three- and five-year commitments. The reduction is meaningful but introduces flexibility costs that are not obvious in the proposal: scaling down within term is generally not permitted, technology refresh is governed by SAP’s release cadence, and the buyer absorbs the depreciation profile of a five-year commitment on a software platform under active redesign. The term decision is a flexibility trade, not a price trade. The contract negotiation pillar covers the trade-off.
Lever four — cloud credits and BTP allowances
SAP’s conversion proposals often include cloud credits or Business Technology Platform allowances as part of the package. The credits have an apparent value at list price that rarely reflects the consumption value to the buyer. A converted credit allowance that the buyer does not consume is shelfware paid for at full price. The negotiation lever is to size the credit allowance to documented consumption forecasts rather than to accept the proposal’s default. The RISE contracts pillar covers the credit mechanics.
Lever five — price protection and uplift caps
The per-FUE rate is contractually protected only against the documented uplift cap. Proposals frequently quote an attractive year-one rate with weak protection against uplift in years two through five. Negotiating the cap is more economically significant than negotiating the year-one rate in most multi-year deals. The protection clause becomes the durable economic instrument of the contract.
The scenario table
The negotiation team should arrive at the conversion meeting with a scenario table that prices the FUE quantum at four positions: SAP’s opening proposal, the post-reclassification baseline, the post-harvest baseline, and the joint optimisation of both. Each scenario captures the FUE quantum, the per-FUE rate, the term length, and the cumulative cost across the contract term. The table moves the discussion from the proposal’s single number to the buyer’s four numbers, and the four numbers are the negotiation. The financial-services S/4HANA conversion case file walks through a worked scenario table on a 12,000-user estate.
The FUE beyond conversion
The conversion FUE quantum is the baseline for the renewal and for every subsequent expansion. Over-sizing at conversion produces over-priced renewals and over-priced expansions. Under-sizing produces uplift purchases at unprotected rates. The size at conversion is therefore the most consequential single decision in the multi-year licence economics of S/4HANA. See the S/4HANA topic page for the surrounding deployment-model considerations and the S/4HANA conversion handbook for the full methodology.
— 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.
Where to start
Estates within twelve months of a conversion decision should run the reclassification and harvest sequence before the conversion proposal is requested. The work changes the input to SAP’s arithmetic and therefore the output, and the change is durable across the contract term. The average yield in our practice across the joint reclassification-and-harvest sequence is between sixteen and twenty-eight per cent of the original conversion proposal, contributing materially to the $180M+ aggregate savings our practice has delivered.