Home  ›  SAP  ›  Audit Defence
SAP · Audit Defence Advisory

SAP audit defence — contest the measurement, don't just pay it.

We manage SAP system measurements (LAW/USMM) and indirect-access claims on behalf of the customer alone, from the notice to the settlement. SAP's opening number counts every assigned user at the highest type and every document at full digital-access value. In our 340+ engagements the average audit claim reduction is 68%, because most of the claim is classification and interpretation — not entitlement. We hold no SAP reseller agreement and take no vendor fees; the only side we are on is yours.

$1.8B+documented client savings
68%average audit claim reduction
340+enterprise engagements
95%client retention
Buyer-side only since 2016 Gartner recognised New York · London · Dubai
SAP audit defence advisory
What this service does

How does SAP audit defence work?

SAP audit defence is the independent, buyer-side management of an SAP system measurement or indirect-access review from the engagement notice to the final settlement. We take over the technical and commercial response so SAP cannot set the user classification, the document count, or the price. We do not act for SAP, resell its licences, or take vendor fees — we represent the customer alone, which is exactly what lets us contest a finding rather than rationalise it. The objective is simple: pay for genuine gaps, and nothing for SAP's worst-case classification.

Most of the claim SAP presents is interpretation, not entitlement. The USMM job assigns users to the most expensive licence type it can justify, the License Administration Workbench (LAW) consolidates duplicates as separate users across clients, and the digital-access engine counts every document — including internally generated and duplicate records — at full value. In our experience the difference between SAP's opening position and the defensible number is consistently large; the 68% average reduction is what disciplined challenge of the measurement produces.

Received an SAP audit or measurement request?

Do not submit the USMM result yet. We classify users first. Talk to us before you respond.

Contact Us →
Before / after

Where does the 68% reduction come from?

The claim shrinks finding-by-finding, not through a single concession. This is the pattern we see most often across SAP measurements — SAP's opening read on the left, the defensible position after review on the right.

Finding areaSAP's opening positionDefensible positionDriver of the reduction
Named-user typeEvery assigned user typed as ProfessionalRight-typed to actual transactions and rolesUsage evidence vs. assignment evidence
Duplicate users (LAW)Same person counted in each client/systemConsolidated to one licence across clientsLAW de-duplication run correctly
Indirect / digital accessAll nine document types at full valueInternal and duplicate documents removed; true baselineDocument-count measurement challenged
Engine metricsPeak or headcount proxy for engine consumptionMeasured actual engine usage to contractual metricEngine measurement reconciled
Inactive / technical usersCounted as licensable named usersExcluded per locked-status and system-user rulesUser-status evidence applied

Download the SAP S/4HANA Defence Playbook.

The named-user classification model, the digital-access baseline method, and the LAW/USMM response checklist we use in live audits.

Get the playbook →
The process

What does an SAP audit-defence engagement look like?

We run a controlled, buyer-side process from the moment the measurement request lands. Every step keeps the classification on the contract and the timeline on your terms.

  1. Scope and respond. We manage the response to the measurement request, define what is in scope, and stop a premature USMM submission that would over-type users and over-count documents.
  2. Independent measurement. We rebuild the true position from your own tooling, classify users to real transaction activity, and run LAW de-duplication before anything goes to SAP.
  3. Challenge the findings. We contest indirect-access, engine and inactive-user assumptions line by line, with contract and usage evidence behind each rebuttal.
  4. Settlement strategy. We convert the corrected position into a commercial outcome — and where the audit is conversion pressure in disguise, we fold it into the wider negotiation.
  5. Close and harden. We document the agreed position and tighten future measurement, digital-access and user-classification terms so the same exposure does not recur.

Audit pressure tied to an S/4HANA move?

We defend the claim and negotiate the conversion as one motion — SAP uses both as leverage, so we do too.

Contact Us →
The cluster

Go deeper on SAP audit exposure.

For the mechanics behind each finding above, read our SAP digital access defence breakdown, the SAP named-user licensing guide, the SAP engine metrics teardown, and the SAP licensing guide pillar. For the wider methodology, see our audit defence service and the cross-vendor vendor audit defence guide. Negotiating a conversion at the same time? Start with SAP negotiation.

An SAP measurement is rarely just a compliance exercise — it is leverage for the next S/4HANA or RISE deal. Treating it as both, with independent buyer-side defence, is how the 68% average reduction turns into a settlement that protects the conversion as well as the claim.

SAP audit letter on the desk?
Buyer-side defence changes the claim before you settle.

We have defended SAP measurements from single-system reviews to global indirect-access claims — for the customer, never the vendor.

The Compliance Brief

Weekly compliance intelligence for IT leaders.