Global Professional Services Firm: How We Cut $4M to $5M Annually Through SAP Named User Reclassification

The Situation

Each of the two firms operated a globally consolidated SAP estate across HR, Finance, and project accounting. The Named User population in each case sat above 18,000 active accounts. SAP's contracted user count had grown organically over a decade. New project codes and acquisitions had defaulted new joiners into Named User Professional, the highest-cost classification. The classification logic that should have routed casual users, expense submitters, and timesheet entrants into Limited Professional or Employee Self-Service had drifted out of operation. Procurement signed the renewal on the assumption that the user count was correct because the SAP measurement cycle had not raised an issue.

The trigger was the same in both engagements. A budget review identified the SAP licence line as the second-largest software cost, and the CFO asked why. The internal SAP team had no defensible answer beyond historic precedent. The procurement team had no benchmark against which to compare the Named User Professional count. Neither firm had run a forensic role-versus-licence analysis since the original go-live. SAP's account team, predictably, supported the existing classification distribution because it underwrote the existing revenue.

We were retained in each case to validate or rebut the classification distribution, identify a defensible reclassification population, and engineer a contractual mechanism to recognise the saving without triggering an audit response from SAP. The brief was tactical and quiet. The work had to be evidence-based.

What We Did

1. Built a user-by-user usage profile. Using STAR transaction histories, login records, and HR role definitions, we built a 24-month profile for every active Named User Professional in scope. The exercise produced for each user: average sessions per week, distinct transaction codes used, business object access patterns, and contracted role designation. The data formed the evidence base for reclassification decisions.
2. Mapped roles against the SAP contractual licence definitions. The SAP price list defines Limited Professional as a user whose business role is limited in scope and complexity, and Employee Self-Service as a user accessing only their own HR data and submitting timesheets, expenses, or limited self-service requests. We applied those definitions strictly against the measured behaviour. The exercise identified that roughly 30 to 40 percent of the Named User Professional population met the contractual definition of Limited Professional, and a further 20 to 25 percent met the definition of ESS.
3. Restricted the reclassification list to defensible cases. Not every borderline user was reclassified. We applied a conservative test: a user was reclassified only if 12 months of transaction history supported the lower classification, the role definition aligned, and the manager could attest the role would not expand in the next 12 months. The discipline protected the saving against future audit challenge.
4. Activated ESS provisioning where it was contractually free. Many SAP contracts include a baseline ESS allocation that the customer never activates. We confirmed contractual entitlement, worked with HR and IT to provision ESS access for the eligible population, and shifted the entitlement use without additional contract spend.
5. Renegotiated the licence mix in the next contract cycle. The reclassification produced a measurable surplus of Named User Professional entitlement against actual need. We worked through the next renewal to convert the surplus into a contracted mix that matched the measured reality, sustaining the saving annually rather than relying on internal compliance discipline.
6. Built the quarterly compliance check. The reclassification work only sustains if the firm runs a quarterly check on new joiners and role changes. We documented the methodology, built it into the SAP team's standard operating procedure, and trained the internal team to maintain the discipline without ongoing external support.

The Outcome

Across the two engagements, annual SAP licence cost fell $4M to $5M per firm. The reductions were sustained across the contracted multi-year terms, with quarterly compliance discipline preventing drift back to the original classification distribution. The reclassification work was completed without triggering an enhanced audit response, because the basis for the change was contractually grounded and the supporting evidence was already documented. SAP's account teams accepted the reclassification on submitted evidence in both engagements, with marginal pushback on a small subset of edge cases that were resolved through dialogue rather than escalation.

Two secondary outcomes mattered structurally. First, the firms now operate a defensible Named User position that holds up under measurement scrutiny. The SAP audit risk for these specific engagements has fallen materially because the classification distribution matches measured usage. Second, the procurement teams have a benchmark methodology they apply to every renewal and every new system rollout, so the licensing economics get reviewed before signature rather than after.

What Other Enterprises Can Take From This

Named User Professional is the default classification SAP applies when no one pushes back. The price differential between Named User Professional and Limited Professional is substantial, typically 3 to 5 times. The differential between Named User Professional and Employee Self-Service is larger again. Most enterprises with mature SAP estates carry a population in the wrong classification. The over-provisioning is rarely intentional. It accumulates over time as new joiners default into the highest-cost licence and no one runs the reclassification work to bring the population back into balance.

The right starting point is transaction history, not role title. A user's contractual classification is determined by what they actually do in SAP, not by what their job description says. STAR, SLAW, and the standard ABAP user log tables contain the evidence. The analysis is not complicated, but it is time-consuming, and the reclassification decision requires judgement at the boundary cases. The discipline of writing down the test, applying it conservatively, and documenting the evidence is what protects the saving against future audit.

The contractual mechanism matters as much as the analysis. Reclassifying users in the SAP system without renegotiating the contracted licence mix produces a temporary saving that disappears at the next renewal. The right structure recognises the reclassification in the next Order Form, converts the surplus to a smaller contracted population, and protects the position with quarterly compliance discipline. For the underlying mechanics of how Named User classifications work and where the boundaries sit, our SAP licensing basics guide walks through the licence types, the contractual definitions, and the evidence tests that determine classification.