SAP opened with an exposure built from an uncorrected system measurement. Reclassifying users and counting documents properly took ninety percent of it away.
Optimize the Estate First: The SAP Work That Pays for the Negotiation
SAP prices your future from your present, so a bloated estate converts into a bloated subscription. The user cleanup, engine and shelfware rationalization, resolving indirect access on your terms, and converting clean with the credits you earned.
A leading Swiss multinational running SAP across Europe, North America and APAC received an audit finding it could not immediately explain. The exposure was large, the timeline was short, and the number had been produced by the company's own system measurement.
That last point is the one worth sitting with. SAP audits are largely self reported. You run the measurement, you submit it, and SAP prices what you tell it. An uncorrected measurement is the vendor's opening position written in your handwriting.
The engagement reduced audit exposure by 90 percent. No litigation, no settlement purchase, and no argument about the contract. The finding was simply rebuilt from an accurate picture of what the estate actually did.
See the SAP advisory practice, the SAP audit defense service, and the SAP audit defense framework.
Five things decide an SAP audit outcome.
SAP audits arrive in three broad shapes, and reading which one you are in changes how you respond.
A routine measurement review follows the annual system measurement and is largely administrative. A structured audit is a formal review with defined scope and timeline. A commercially motivated audit tends to arrive near a renewal or during a migration conversation, and its purpose is leverage rather than compliance.
This one arrived with a large indirect access component, which usually signals the third kind. See the SAP EAM and industry engine licensing playbook.
The party with better data sets the terms of an SAP audit. In this case SAP had a measurement the customer had submitted without reviewing, and the customer had nothing else.
We rebuilt the picture from four sources: the configuration management database, discovery tooling already deployed across the estate, the service management records, and the existing software asset management data.
Most organizations already own everything they need for this. It sits in tools bought for other reasons, and nobody has ever pointed them at the licensing question.
Entitlement is rarely one document. It accumulates across the original contract, subsequent amendments, support agreements, and anything inherited through acquisition.
Acquisitions are where entitlement goes missing. Licences bought by a company you purchased are frequently still valid and frequently absent from the central record, which means you may be buying something you already own.
Reconstructing the full entitlement position before responding is unglamorous and it is where a meaningful part of this reduction came from.
| Exposure driver | What SAP counted | What the evidence showed | Why the gap existed |
|---|---|---|---|
| Named user types | Professional licences across the estate | A minority genuinely using Professional functionality | Types assigned at implementation and never reviewed |
| Engine metrics | Full engine entitlement against headline metrics | Actual measured consumption on each engine | Metrics inherited from a much older deployment shape |
| Digital access | Document counts from the raw measurement | Chargeable documents after duplicates removed | System generated and duplicate documents counted as business events |
| Inherited licences | Not counted at all | Valid entitlement from an acquired entity | Never consolidated into the central entitlement record |
Split by cause, the finding stopped looking like one large number and started looking like four correctable ones.
Named user drift was the largest. SAP user types range from Professional down to far cheaper categories, and the classification is meant to reflect what a person actually does in the system. In practice everyone gets Professional at go live and nobody revisits it.
Digital access was the second. SAP's document based model charges for documents created in SAP by external systems, and a raw count will happily include duplicates, reversals and documents SAP's own processes generated.
Engine metrics and unrecorded inherited entitlement made up the rest. See the SAP digital access licensing notes.
Acknowledge, scope, then answer. In that order, and not faster than that order allows.
The most common mistake is answering too quickly. A prompt, uncorrected submission feels cooperative and hands the vendor a number you then have to argue back down.
The standard advice is to run the annual system measurement, submit it promptly, and demonstrate good faith. We disagree with the sequence. SAP audits are self reported, which means the measurement you submit becomes the vendor's opening position and the anchor for everything that follows. Run the measurement, absolutely, but run it for yourself first. Review the user classifications, strip duplicate and system generated documents out of the digital access count, and reconcile inherited entitlement before anything leaves the building. Submitting an uncorrected measurement is not good faith, it is doing the vendor's work for it, and it is far harder to argue a published number down than to submit an accurate one in the first place.
These are the moves that produced the reduction. The first three did most of it.
If an SAP audit letter has arrived, or you think one is coming, do these in order.
The eleven moves, named user reclassification, engine metrics, digital access document counting, the FUE conversion, and the buyer side position at every phase of an SAP audit.
Used across more than five hundred enterprise clients. Independent. Buyer side.
Source: Redress Compliance advisory engagement file.
SAP's opening number came from our own system measurement, which nobody had corrected in years. Half our Professional users had never needed a Professional licence, and the digital access claim counted documents twice. Ninety percent of the exposure came off.
Independent. Buyer side. The advisory firm enterprise software vendors do not want you to hire.
Audit signals, named user signals, engine licensing signals, indirect access signals, FUE conversion signals, and the broader SAP licensing leverage signals.
White Paper · Advisory
The Software Audit Defense Playbook
Turn an audit notice into a controlled negotiation: control scope, build your ELP, and compress the opening claim toward ~30%. Read it free.
The company cut its SAP audit exposure by roughly 90 percent against the publisher's opening claim. The reduction came from reframing the audit as an indirect access conversation rather than a named user count. The headline claim was never the defensible number.
The core issue was SAP indirect access, where third party systems touch SAP data and SAP seeks to license those connections. SAP's opening position valued every integration at full list. Scoping the genuinely licensable access shrank the claim sharply.
SAP indirect access is use of SAP data by non SAP applications or external users, which SAP can claim requires licensing. It matters because integrations multiply the apparent user base. The buyer side move is to map real document flows and price only what the contract covers.
Redress reconstructed the actual document and integration flows, challenged the publisher's measurement basis, and negotiated against a defensible scope rather than the opening claim. Audit defense is a measurement argument first. The data, not the relationship, moved the number.
Yes, Redress Compliance is 100 percent buyer side independent and earns no SAP commission or referral fee. That independence means the advice targets the lowest defensible settlement. Benchmarks from comparable SAP audits give the leverage.
