User reclassification opportunities post RISE go live.

The FUE entitlement inside a RISE with SAP contract is split across bands, with each user counted into a band based on the functional capability the user is expected to consume. The band assignment made at signature is sized against the role mapping captured during the negotiation, which is itself sized against an SAP recommended classification. In production, a meaningful percentage of the user population sits in a band higher than the actual transactional activity warrants. The reclassification work that moves the misclassified users to the correct band, and that documents the reclassification against the contract, consistently surfaces between four and nine percent of the FUE entitlement cost across the firm engagement base. This piece walks the reclassification opportunity, the evidence, and the process.

The standard band assignment overstates the actual consumption

The standard RISE band assignment is driven by the SAP transaction allocation against each functional role. A user assigned to a finance role at the design stage will, by default, be classified into the Advanced or Core band based on the breadth of finance transactions the role is expected to perform. The classification is honest at the design stage, in the sense that it reflects the functional capability the user might require. The classification is conservative at the operational stage, in the sense that it does not reflect the transactions the user actually performs in production.

The pattern repeats across the user population. Users assigned to operational roles in supply chain, manufacturing, sales, and customer service are classified against the breadth of capability the role might require, with the classification applied uniformly across the user population in the role. In production, a significant percentage of users in each role perform a narrower set of transactions than the breadth their classification covers. The narrower transactional footprint maps to a lower band, and the reclassification surfaces the difference as a saving against the entitlement.

The evidence is in the transaction telemetry

The reclassification work is grounded in the actual transaction telemetry captured inside the SAP system. The system records each transaction code that each user executes, along with the frequency, the time of day, and the business object accessed. The telemetry runs continuously, and the data accumulates from the first day the user logs in. The reclassification analysis uses the telemetry from the first six months of production operation as the evidence base, with attention to seasonal patterns and to the variation across the business cycle.

The analysis maps each user against the transactions actually executed in the six month window, classifies the transactions against the SAP band definitions, and identifies the users whose actual transactional footprint sits inside a lower band than the assigned classification. The output of the analysis is a user level reclassification recommendation, with the documented evidence supporting each recommendation. The work has to be precise because the SAP review of the reclassification will challenge each recommendation, and the evidence has to survive the challenge.

The most common misclassification patterns

The firm has tracked the reclassification patterns across the engagement base, and four patterns account for the majority of the saving opportunity. The first pattern is the user assigned to the Advanced band who performs only display and reporting transactions, without exercising the update capability that the Advanced band covers. These users belong in the Core or Self Service band depending on the breadth of their reporting work.

The second pattern is the seasonal or part time user assigned to a permanent band classification. These users may perform transactional work for a defined period each year or for a defined portion of their work week, and the classification can sit in a lower band that reflects the actual usage pattern. The third pattern is the user who has changed roles since the original classification, with the role change moving the transactional footprint into a different band. The fourth pattern is the user who has been onboarded into a different role than the original design contemplated, with the classification still reflecting the design role rather than the actual operational role.

The reclassification process has three steps

The reclassification process has three steps that the buyer organisation has to run. The first step is the analysis against the transaction telemetry, with the documented evidence captured for each recommended reclassification. The analysis is run inside the buyer organisation, with the technical infrastructure required for the transaction telemetry extraction and the analytical work to produce the recommendations.

The second step is the joint review with SAP. The review is contemplated inside the FUE recategorisation clause that the negotiation should have rewritten, which sets the documentation requirements and the joint review process. The buyer organisation presents the recommendations against the documented evidence, and the SAP team reviews the recommendations against the band definitions and the contractual classification rules. The third step is the application of the agreed reclassifications inside the SAP system, with the user level changes reflected in the system configuration and in the consumption telemetry against the entitlement.

The contractual hooks that enable the reclassification

The reclassification process depends on contractual hooks that the original negotiation should have set inside the RISE contract. The first hook is the documented band definition, which makes the classification rules unambiguous and supports the buyer side analysis. The second hook is the true down mechanism, which mirrors the SAP true up mechanism and allows the buyer organisation to reduce the entitlement when the transactional footprint contracts.

The third hook is the joint review cadence, which sets the regular cycle for the reclassification work and prevents the SAP team from deferring the review indefinitely. The fourth hook is the audit and documentation rights, which give the buyer organisation the access to the transaction telemetry and the right to commission an independent analysis of the user classification. Without these contractual hooks, the reclassification work is constrained by the standard RISE template, which favours the SAP commercial position and resists the downward classification adjustments.

The cadence of the reclassification work

The reclassification work runs on a structured cadence rather than as a one off exercise. The first reclassification cycle runs six months after go live, when the production telemetry has accumulated enough data to support the analysis. The second cycle runs at the end of year one, capturing the seasonal patterns and the role changes that have occurred across the first full operational year. The cycles continue at twelve month intervals across the remainder of the term, with the cadence ensuring that the entitlement aligns with the actual consumption rather than drifting upward against the original classification.

The cadence is critical because the user population evolves continuously. New users are onboarded, existing users change roles, business units are reorganised, and the transactional footprint shifts across the term. A reclassification exercise that runs once and then stops will surface a one off saving and then drift back against the contracted entitlement as the population evolves. A reclassification programme that runs on the structured cadence captures the saving at each cycle and holds the entitlement against the actual consumption across the term.

The compounded saving across the seven year term

The reclassification work compounds across the seven year term. The first cycle typically produces between three and five percent of FUE entitlement saving against the original classification. The subsequent cycles produce smaller incremental saving against the prior cycle, with the cumulative saving across the seven year term reaching between fifteen and twenty five percent of the original FUE entitlement cost. The compounded saving is consequential, and it is recovered through operational work rather than through new commercial negotiation.

The work depends on the contractual foundation that the original negotiation should have established, on the analytical capability that the buyer organisation has to develop, and on the operational cadence that the post signature programme has to maintain. The reclassification opportunity is one of the highest yield post signature workstreams across the firm engagement base, and it is one of the most consistently overlooked. The buyer organisations that have integrated the reclassification work into the post signature programme close the seven year term with an FUE cost line that holds against the actual consumption. The buyer organisations that have not integrated the work close the term with an FUE cost line that has drifted upward against the original classification, with the drift recoverable only through renegotiation at renewal. The work begins in the first ninety days after signature with the establishment of the transaction telemetry monitoring, and it continues through to the renewal with the structured cadence of analysis, joint review, and operational adjustment. The discipline is the value, and the value compounds.