SAP audit defense, 93 percent off the claim.

An $18M claim built on inflated document counts settled at $1.2M because every line was validated against the contract before anything was paid.

How did the $18M SAP audit claim arise?

The claim arose when a routine annual measurement escalated into an enhanced audit and SAP priced unlicensed indirect access at $14.4M of the $18M total. The client was a global industrial manufacturer running ECC with Salesforce, a customer portal, and EDI flows writing into SAP.

• Trigger: system measurement results plus an architecture review during an S/4HANA sales cycle.
• Claim structure: roughly 80 percent indirect access under the digital access document model, 20 percent user classification findings.
• Pressure point: the claim landed eight weeks before the client's fiscal year close, with settlement framed as urgent.

The manufacturer engaged Redress before responding. The first move was to slow the clock: no admission, no data beyond contractual obligation, and a formal validation of every claim line.

How was the indirect access claim dismantled?

The defense cut the claim by separating billable digital access documents from double counted and out of scope documents, which removed roughly two thirds of the indirect access exposure on paper. SAP's document counting in the digital access model is generous to SAP by default; the contract and the measurement rules are not.

The order document analysis

Line item analysis showed the audit tooling counted technical documents, intermediate documents, and replicated records as billable. Mapped against the nine digital access document types, the defensible count fell from SAP's estimate by a factor of roughly three.

The user classification rework

The remaining $3.6M of the claim rested on professional user classifications. Activity based reclassification against actual transaction usage, evidenced through SAP system measurement data, cut that block by more than half.

What did the settlement look like?

The matter settled at $1.2M, a 93 percent reduction from the opening claim, structured as a forward purchase rather than a penalty. No backdated maintenance was paid.

What should SAP customers do before the next audit?

The reusable defense is preparation: know your document counts, your user classifications, and your contract definitions before SAP measures them for you.

• Count first: run your own digital access document estimate annually; never meet an audit with SAP's number as the only number.
• Classify by activity: user types should reflect measured transaction behavior, not job titles or convenience defaults.
• Control the clock: audit ultimatums are negotiation theater; evidence based validation takes weeks and is your contractual right.

Where the common advice on SAP indirect access is wrong

The standard advice is to take SAP's digital access adoption program quickly because the discount looks generous and the exposure looks frightening. We disagree. In the SAP audit defenses Morten Andersen supported in 2024 to 2025, opening document counts overstated the defensible billable position by 2 to 5 times, which means the discount was applied to an inflated base. The buyer side move is to validate the document count line by line before pricing any conversion, then negotiate the program discount against the corrected base. A discount on a fictional number is not a discount.

What the engagement data shows

Three numbers define this defense.

How to use these numbers

The reduction percentage is unusually high but the mechanism is ordinary: most SAP audit claims contain a large, contestable indirect access block that collapses under document level validation.

An audit claim is an opening position, not an invoice. The number that matters is the one that survives the evidence.

What to do next

The sequence below is the defense this manufacturer ran. Run the first three steps before any audit letter arrives.

The audit defense sequence

1. Run an internal digital access document count annually and keep the methodology documented.
2. Reclassify SAP users against measured transaction activity, not job titles.
3. Map every third party system writing into SAP and classify its document flows.
4. On receipt of a claim, validate every line against contract definitions before responding.
5. Refuse audit deadlines that are not contractual; evidence based validation is your right.
6. Negotiate settlement as a forward purchase at a discount, never as a penalty with backdated maintenance.

Related advisory: Start with the SAP audit defense framework, or engage our SAP audit defense service directly.

White Paper · SAP

SAP License Audit Survival Guide

An SAP license audit targets named user misclassification, indirect access, and LAW report gaps. Read it free.

Read the white paper

Frequently asked questions

What triggers an enhanced SAP audit?

Routine system measurement anomalies, architecture reviews during sales cycles, and S/4HANA migration discussions. This claim followed a measurement escalation during an active S/4HANA pitch.

What is SAP indirect or digital access?

Indirect access is third party systems creating or consuming SAP data without named users. SAP prices it through digital access, which counts nine document types created in the system.

How are digital access documents counted?

By document type at creation, but audit tooling routinely includes technical, intermediate, and replicated documents that are not billable. Line item validation against the nine types is the core defense.

Is the SAP digital access adoption program worth taking?

Only after correcting the document base. The program discount applied to an inflated count costs more than a validated count at list. Validate first, then negotiate the discount.

Can you negotiate an SAP audit claim?

Yes. Audit claims are opening positions. This $18M claim settled at $1.2M because the document count and user classifications were contested with evidence, not arguments.

How should we prepare for SAP system measurement?

Run your own measurement first, classify users by activity, count digital access documents annually, and document every third party integration before SAP measures them for you.