SAP Named User License Negotiation. A buyer side white paper.

SAP named user negotiation turns on classification first and discount second, because the type each user is assigned to sets the price long before any percentage discount is ever applied to the order form.

This white paper is for SAP procurement leaders preparing a named user negotiation. Read it with the named user types guide and the SAP Practice page.

What are the main SAP named user types?

SAP named users split into a small set of types, each with its own price. Professional users sit at the top, with lighter types beneath for limited and self service work. SAP frames its user based model on the SAP ERP pages.

How does the user type ladder work?

Each step down the ladder trades capability for cost. The aim is to place each person on the lowest type that still covers their real work in the system.

• Professional user: full operational access, highest price.
• Limited professional user: narrower scope at lower cost.
• Employee user: self service tasks at the lightest price.
• Developer user: build and configuration access, priced separately.

Where does named user classification go wrong?

The biggest error is assigning professional users by default. Staff who only approve or report end up on the most expensive type, and the cost carries year after year. SAP agreement terms sit in the SAP agreements center.

How does classification feed audit risk?

Under classification creates exposure if usage exceeds the assigned type. Over classification wastes money. A defensible mapping protects both the budget and the audit position.

What levers move an SAP named user deal?

The levers that hold are a measured classification baseline, a cap on future user growth, and bundling the user talk into the wider renewal. SAP cloud direction is covered in SAP news.

Why start from a measured baseline?

The SAP supplied user count reflects assigned types, not actual usage. Measuring real activity gives you a lower, defensible number to anchor the negotiation on.

• Measure usage: classify from activity, not legacy assignment.
• Cap growth: fix the price for new users in advance.
• Bundle the talk: negotiate users inside the full renewal.

When should you run the named user negotiation?

Run it inside the renewal window, not after the order is signed. Once the renewal closes, the user mix is locked and the leverage is gone until the next cycle.

Where the common advice on SAP named user negotiation is wrong

The standard advice is to push hard on the headline discount percentage and treat the user mix as fixed. We disagree. Across the named user negotiations Fredrik Filipsson advised on in 2024 to 2025, discount alone moved the deal 5 to 15 percent, while reclassification moved it 15 to 30 percent. The buyer side move is to fix the classification first, then negotiate discount on the corrected, lower base. A large discount on an over classified estate still leaves you paying professional prices for self service work. Settle the mix before you ever discuss the percentage.

40

Named user negotiations advised

15 to 30%

Saving from reclassification

4

Core named user types

Source: Redress Compliance advisory engagement file, 2024 to 2025.

The discount is the conversation everyone has. The classification is the conversation that actually decides the price.

What to do next

1. Export every named user with the assigned license type.
2. Pull actual usage and map each user to the lightest fitting type.
3. Quantify the cost of current over classification.
4. Set a measured baseline as the negotiation anchor.
5. Cap the price for future user growth in the contract.
6. Bundle the user mix into the full renewal discussion.
7. Re run the classification before each renewal cycle.

Frequently asked questions

What are the main SAP named user types?

SAP named users split into professional, limited professional, employee, and developer types. Each carries its own price, with professional the most expensive and employee the lightest for self service work.

Why does classification matter more than discount?

Classification sets the price before any discount is applied. A large discount on an over classified estate still leaves you paying professional prices for users who only do self service work.

What is the most common named user mistake?

The most common mistake is assigning professional users by default. Staff who only approve or report end up on the most expensive type, and that cost repeats every year.

How much can reclassification save?

Across our engagements, reclassification commonly cuts named user cost by 15 to 30 percent. Discount alone typically moves a deal only 5 to 15 percent without touching the user mix.

How does named user classification affect audits?

Under classification creates exposure if real usage exceeds the assigned type, while over classification wastes budget. A defensible, measured mapping protects both the audit position and the cost.

Should you measure usage before negotiating?

Yes. The SAP supplied count reflects assigned types, not actual usage. Measuring real activity gives you a lower, defensible baseline to anchor the negotiation on.

When is the best time to negotiate user types?

Negotiate inside the renewal window, not after signing. Once the renewal closes the user mix is locked and the leverage is gone until the next cycle.

How do developer users fit the model?

Developer users hold build and configuration access and are priced separately from the standard ladder. They also attract audit attention, so the count should be tight and justified.