Cut the SAP named user bill before SAP classifies it for you. Five levers, a verified baseline, and the clauses that hold them.

SAP counts every unclassified user ID as a Professional at roughly 3,800 US dollars list. In a representative 5,000 user estate that one default manufactures 3.72 million US dollars of avoidable exposure. Five classification levers and five contract clauses take it back.

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

The SAP named user negotiation runs on a calendar SAP controls, so the buyer side discipline is to flip that control early. SAP sets the measurement date, the price reference points, and the audit posture. Each of those is a lever you can move if you start before the renewal letter arrives, and a trap if you wait.

The cycle has four moments that decide the number. Each one rewards preparation and punishes a late start. Treat the whole sequence as one campaign, not a single meeting.

Start the clock on your side

The single highest value move is timing. Begin the internal classification and baseline work three to six months before the renewal date. That window lets you measure the estate yourself, reconcile entitlement, and build the alternative before SAP frames the conversation around its own number.

The buyer side framework in four steps

• Baseline. Measure and classify the estate internally, so you hold the real number first.
• Benchmark. Price each user type against engagement data, not SAP list.
• Alternatives. Build the BATNA: reclassification, S/4HANA conversion timing, and third party support.
• Clauses. Lock the protective contract language into the signed order, not a verbal assurance.

A verified entitlement baseline is the list of license types and quantities you actually own, reconciled against what the estate actually uses. SAP prices the gap between measured use and entitlement, so the baseline is the document that decides who carries the burden of proof. Build it before SAP measures, and the burden stays with the data you control.

The baseline rests on two inputs that must reconcile. The first is contractual entitlement, read from every order form and amendment. The second is measured use, read from USMM and consolidated through the License Administration Workbench. When the two disagree, the difference is the negotiation.

The four step baseline framework

• Read entitlement. Extract every named user type and quantity from the order forms and amendments.
• Measure use. Run USMM on each production client and consolidate through LAW into one report.
• De duplicate. Map users across systems so no person counts twice.
• Reconcile. Compare measured use to entitlement line by line, by license type.

Why the baseline survives scrutiny

A baseline survives because it is built from SAP own tools and your own contracts, not from estimates. When SAP questions a count, you answer with the USMM extract, the LAW mapping, and the order form entitlement. The conversation moves from assertion to evidence, and evidence is where the buyer side wins.

Classification is the largest controllable cost in SAP named user licensing. Five levers do most of the work. Each one moves users from a higher priced type to a lower priced type that their recorded behavior justifies, with no loss of the access they actually use.

The five levers

• Reverse the Professional default. Every unclassified ID counts as Professional at roughly 3,800 US dollars. Classify all of them before measurement.
• Split Professional from Limited Professional. A clerk working one module is a Limited Professional, priced near half of Professional, not a full Professional.
• Capture the Self Service tier. View only and leave request users are Employee or Self Service users at a few hundred dollars, not Professional.
• Purge duplicate and ghost IDs. Deactivate test, service, and leaver IDs, and merge cross system duplicates through LAW.
• Remap to Full Use Equivalents. On S/4HANA, convert classic types into the FUE basket where the weighting favors you.

The Professional versus Limited Professional split

The split between Professional and Limited Professional is where most of the money sits. A Professional carries unrestricted access. A Limited Professional carries narrower rights, suited to a user who lives in one module. SAP defaults users up, so the buyer side move is to map each person to recorded transactions and push them down where behavior allows.

Where the common advice on SAP user classification is wrong

The standard reseller line is to buy a block of Professional users for safety and sort the mix out later. We disagree. In the engagements we ran in 2024 to 2025, the safety buffer became the baseline SAP measured against, and the unused Professional licenses were never reclassified down.

The buyer side move is the reverse. Classify to the floor first, license the verified count, and add a small written reclassification right rather than a block of expensive headroom.

S/4HANA prices users through Full Use Equivalents, not flat named user counts. Each classic user type maps to a weighted FUE value. The weighting rewards pushing users down the tiers, because lower tiers convert into far fewer FUEs. This is the fifth classification lever, and it is the one most estates leave on the table.

The published ratios are blunt and favorable to a clean estate. One Advanced Use counts as one FUE, five Core Use count as one FUE, and thirty Self Service Use count as one FUE. A Developer counts as two FUEs. The same classification discipline that cuts the classic count compounds under FUE math.

The conversion trap to watch

The FUE basket is favorable only if the conversion ratios are fixed in writing. SAP can restate a user mix at conversion, pushing Core users back to Advanced and inflating the FUE count. Lock the ratios and the tier mapping in the conversion order, or the published weighting becomes a moving target the day you migrate.

Classification cuts the count, but contract language holds the result. Five clauses decide whether the savings survive the next measurement and the next renewal. Each one converts a verbal assurance into an enforceable position.

• Reclassification right. The right to re measure and reclassify users down at any time, without penalty or repurchase.
• Type rate and uplift cap. Fixed per type list rates and a capped annual maintenance uplift for the full term.
• Named user grandfather. Preserve legacy user types at their legacy rates rather than repricing to the current catalog.
• FUE conversion lock. Fix the named user to FUE ratios and tier mapping if you migrate to S/4HANA.
• Measurement method. Usage measured against recorded transaction profile, with classification applied before submission, not the USMM default.

How the clauses interlock

The clauses work as a set. The type rate cap holds the price, the grandfather clause holds the legacy types, the FUE lock holds the migration math, and the measurement method clause stops the Professional default from returning at the next audit. The reclassification right ties them together by letting you act on all of them mid term.

Indirect use sits beside named users in the same measurement. SAP document based digital access model counts system to system use separately, so confirm it is scoped out of the named user count before you sign.

Discount benchmarks depend on the scenario and the alternative you hold. A renewal in place and a migration or partial exit produce different leverage, so they produce different recovery. The numbers below are benchmark ranges from our engagement file, not a single guaranteed outcome.

Two scenarios frame the range. In a renewal in place, recovery comes from the classified baseline and a credible threat to delay or reduce scope. In a conversion or partial exit, recovery comes from the timing of the S/4HANA move and the option of third party support on the legacy estate.

Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.

SAP runs a small set of repeatable tactics in named user negotiations. Each one has a clean counter, and the counter is stronger when a real alternative sits behind it. The BATNA is what turns a counter from a debating point into a credible position.

Building the BATNA across alternatives

A BATNA is your best alternative if the SAP deal falls through. For named users it has three credible legs, and each one shifts the recovery range upward when it is real and visible to SAP.

• Reclassification and right sizing. Cut the count to the verified floor, removing the need for the proposed expansion entirely.
• Migration timing. Move the S/4HANA conversion to a date that suits your budget, not the SAP calendar.
• Third party support. Hold the option of independent support on the legacy estate to release maintenance leverage.

The third leg has a real deadline behind it. SAP mainstream maintenance for Business Suite 7 runs to the end of 2027, with extended maintenance to the end of 2030. That timeline is the calendar your BATNA runs on, and it is one you can plan around rather than react to.

The side letter language we use

When a protective clause cannot land in the main order, it lands in a side letter signed alongside it. The side letter fixes the reclassification right, the FUE conversion ratios, and the type rate cap in plain language. Insist on signature, not an email. Only the signed instrument survives a change of account team.

The three phase negotiation sequence