A leading US food manufacturer faced an SAP measurement claim with a seven figure number on the table. A clean usage baseline and a named user reclassification took the final exposure down by 89 percent.
A leading US food manufacturer faced an SAP measurement claim with a seven figure number on the table. A clean usage baseline, a named user reclassification, and a document level audit took the final exposure down by 89 percent.
This engagement followed that pattern. The manufacturer ran SAP ECC across finance, supply chain, and plant operations. A routine measurement turned into a large compliance claim. The number looked alarming. It was also soft.
SAP opened with a measurement based on the USMM and LAW output plus a digital access estimate. The combined claim implied a seven figure true up.
Most of the claim sat in Professional user licenses. The measurement assigned the highest type to thousands of accounts, including dormant and shared ones.
The second large line was indirect, or digital, access. SAP counted documents created through connected systems. The count was high and unexamined. SAP publishes the model in its ERP product documentation, and the commercial terms sit in the SAP software agreements.
The measurement reflected configuration, not real use. That distinction is the whole ballgame. A measurement counts what the system can do. A baseline counts what people and processes actually did.
We rebuilt the usage picture independently before responding. The baseline pulled twelve months of activity and scored every account against contracted scope.
We profiled login frequency, transaction depth, and module access per account. Dormant and duplicate accounts were tagged and removed from the chargeable population.
Each remaining account was mapped to the lowest license type its real activity supported. Many Professional accounts moved to limited or employee self service types.
From SAP claim to settled position
| Line item | SAP opening claim | After baseline | Driver |
|---|---|---|---|
| Professional users | Very high | Sharply reduced | Reclassification to lower types |
| Limited and self service | Understated | Right sized up | Honest classification |
| Digital access documents | Large, unexamined | Materially lower | Duplicate and system records removed |
| Net exposure | Seven figures | 89 percent lower | Baseline plus document audit |
Named user type is where most SAP audit value is won or lost. The rules are precise and the buyer controls the evidence.
SAP accepts reclassification when the activity record supports it. The named user definitions sit in the SAP software use rights. We documented each move with usage data, which made the lower types defensible rather than asserted.
The standard advice from many resellers, and sometimes from the account team, is to accept the measurement output from USMM and LAW at face value and negotiate only the discount. We disagree. In roughly nine out of ten SAP audits we defended, the raw measurement counted users and documents that did not belong in the claim, and the real work was correcting the baseline, not haggling on price. The buyer side move is to rebuild the usage picture independently, challenge every classification and every counted document, and only then discuss commercial terms against a number you can defend.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A measurement counts what the system can do. A baseline counts what your people actually did. The gap between the two is where the audit is won.
The digital access line fell once we audited the documents behind it. Counting rules matter as much as the headline number.
Many counted documents were duplicates or internal system records. Under the digital access model these should not inflate the chargeable count.
With a clean document count, the conversion math improved sharply. The manufacturer kept its named user position where it was cheaper and converted only where the S/4HANA digital access route made sense.
Five lessons carry to almost every SAP audit.
No. The first SAP measurement number is an opening position, not a settled liability. It reflects system configuration rather than real use, and it almost always falls once a clean usage baseline corrects user classification and the digital access document count.
Named user overclassification drove most of the claim. Thousands of accounts carried the Professional type when their actual activity fit a limited or employee self service type. Reclassifying them with evidence removed the largest share of the exposure.
Named users can be reclassified when activity data supports a lower type. We profile login frequency, transaction depth, and module access per account, then map each account to the lowest type its real use justifies, documenting every move so SAP can verify it.
The digital access count was too high because it included duplicate and system generated documents. Under the model SAP publishes, internal and duplicate records should not inflate the chargeable count, so auditing the documents reduced the line materially.
No new licenses were purchased to close the audit. The 89 percent reduction came entirely from correcting the baseline, reclassifying users, and auditing the digital access documents, not from buying additional entitlements.
A defense of this size usually runs two to four months. Most of the time goes into building the independent baseline and assembling the activity evidence, which is the work that makes the lower numbers defensible.
USMM is the SAP self measurement program that produces the license count, consolidated by LAW. It matters because its output is the starting claim. Reading it critically, rather than accepting it, is the first step in any SAP audit defense.
Results vary, but the method repeats. Across 30 to 40 SAP audits we defended in 2024 and 2025, a clean baseline, evidenced reclassification, and a document audit consistently cut the opening claim by a large margin.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The opening SAP audit number is a negotiating posture. A buyer side baseline turns it back into a fact based conversation, and the fall from the first claim is almost always large.
