The named-user true-up is the annual event at which SAP reconciles the customer's named-user inventory against the contracted entitlement and proposes a true-up purchase for any shortfall. The headline number on a true-up proposal is usually too high. It is too high because the SU measurement that produced it reflects the customer's named-user inventory as configured — with the duplicate accounts that have not been merged, the dormant users who have not been deactivated, the over-classified users sitting at Professional when Functional or Limited Professional would do, the test and training accounts that should have been excluded, and the contractor accounts that have been pulled into the wrong category. Each of these can be corrected, but correction takes time, and the time has to be spent in the three months before the measurement closes, not the three weeks after the proposal arrives.
This article explains how to structure the named-user true-up cycle so the headline number reflects the optimised inventory, not the unmanaged inventory, and the four contract levers that protect the rate at which the true-up is priced.
The pre-measurement window
The pre-measurement window is the period between the prior year's measurement and the current year's measurement — in practice, the twelve months before the next USMM is run. The work in the pre-measurement window divides into two streams: inventory cleanup and classification optimisation. The inventory cleanup runs continuously and should be operationalised as a quarterly hygiene rhythm. The classification optimisation runs intensively in the ninety days before the measurement window opens.
The inventory cleanup addresses the populations that should not be in the count at all: deactivated employees who retain active SAP accounts, contractors whose engagement has ended, system accounts and technical users that have been wrongly classified, duplicate accounts arising from name changes or system migrations. The cleanup is procedural rather than analytical — the customer runs a deactivation workflow against the HR-leaver data, the contractor end-date data, and the system-account inventory, and reconciles the residual against the SU01 record.
The classification optimisation addresses the users whose role profile justifies a less expensive named-user type than the one they currently hold. The optimisation is analytical: the customer extracts the user-to-role assignments from PFCG/AGR_USERS, joins them to the role-to-licence-type mapping in the contract, and identifies the users who could be reclassified downward without breaching the contractual scope of their permitted activity. See our companion article on role-based reclassification for the detailed approach.
The four contract levers
1. The contracted price-protection clause
Many SAP contracts include a price-protection clause that fixes the price for additional named-user licences purchased within the contract term to the per-user price specified on the original order form. The clause protects the customer from rate uplifts on true-up purchases. The clause is contractually present in many master agreements but rarely surfaced by SAP in the true-up proposal — the proposal typically prices the true-up at the current rate card, which can be twenty to forty per cent above the contracted rate. The first defensive move at true-up is to find the price-protection clause and require the proposal to be re-priced at the contracted rate.
2. The bundle-conversion lever
True-up purchases at Professional rate can sometimes be converted to bundle conversions — smaller numbers of lower-tier licences plus a smaller number of Professional — that produce the same coverage at a lower total cost. The conversion requires reclassification work to determine which users genuinely need Professional rights, but the conversion economics frequently outweigh the reclassification effort by a multiple. See our companion article on Professional vs Functional vs Limited Professional for the rights-comparison framework.
3. The true-up timing lever
The contract typically allows the customer to schedule the true-up purchase within a window rather than at a fixed date. Customers who time the true-up to coincide with a broader contractual cycle — a renewal, an S/4HANA conversion event, an RISE conversion — can fold the true-up into the broader commercial negotiation and produce better economics than a standalone true-up purchase. The lever requires the customer to be aware of the timing optionality, which is rarely flagged in the proposal.
4. The certification-extension lever
SAP sometimes accepts a certification — a documented commitment to remediate within a defined window — in lieu of an immediate true-up purchase, where the customer can demonstrate that the overcount is driven by cleanup that is in progress rather than by genuine licence shortfall. The certification approach requires the customer to commit to the remediation plan and to validate completion in a follow-up measurement, but it can avoid an immediate cash outlay where the remediation will eliminate the shortfall.
The measurement-window discipline
The measurement window itself — the period during which the USMM is executed against the system — should be treated as a discrete operational event with its own discipline. Cleanup activities should be paused during the window so that the system state at measurement reflects the optimised inventory, not a partially-cleaned-up state. Reorganisations, role redesigns, and HR data loads should be deferred or pre-completed. The measurement should be executed against the system in the cleanest reasonable configuration the customer can achieve.
The window is also the time to validate the measurement output before it leaves the customer's environment. The USMM output should be reviewed by the licence-management team against the previous year's output, with material movements (large increases in Professional count, unexpected appearances in restricted categories) investigated before the file is sent to SAP. Customers who send the USMM output without review accept whatever the system has produced, including any configuration errors that have crept in since the prior measurement.
The true-up proposal response
The proposal response should follow a four-step structure. The first step is to validate the proposal against the customer's own cleaned-up inventory, identifying any populations that should not be in the count. The second step is to apply the contract levers — price protection, bundle conversion, timing, certification — that affect the proposed price and structure. The third step is to negotiate the residual on the merits, supported by the documented inventory and the contract analysis. The fourth step is to document the agreed outcome in writing so the basis for the true-up is preserved for the next cycle.
The audit-cycle integration
The true-up cycle and the audit cycle are interrelated. A clean true-up produces a clean baseline for the next audit; a contested true-up creates positions that the next audit will revisit. Customers who treat the true-up as an annual hygiene event — with the cleanup, optimisation, validation, and negotiation operationalised — consistently produce smaller true-ups and smoother audits over time. See our licence compliance assessment service for the framework we use to operationalise the cycle.
For the methodology behind named-user optimisation, see our named-user optimisation white paper. For the broader named-user context, see our named-user topic page. For a worked example of a true-up cycle restructured around the four contract levers, see our global manufacturer case study.