Michigan Automotive Supplier. SAP indirect access claim cut 83 percent.

A Michigan automotive supplier faced an SAP audit claim built on named user counts for every EDI and middleware connection. Document flow evidence and the digital access framework closed the claim 83 percent below the opening number.

Why did SAP raise an indirect access claim against the supplier?

SAP raised the claim because the supplier's EDI and middleware traffic touched ECC through a handful of technical accounts, which the audit treated as unlicensed access by every external party behind them. Order releases from OEM customers, advance shipping notices, and 3PL confirmations all flowed through these interfaces.

The audit position priced thousands of external users as named users under the SAP licensing framework. The supplier's actual contract predated the digital access model, which let the auditor choose the interpretation that maximized the claim.

• Audit trigger: middleware accounts with high transaction volume and no matching named user population.
• Publisher position: every external party exchanging documents with ECC needs a named user license.
• Customer reality: machines, not people, exchanged standardized EDI documents at predictable volumes.

What did the document flow evidence actually show?

The evidence showed a machine to machine integration estate, not a hidden user population. Mapping six months of interface logs counted the real document types and volumes, and that count became the only defensible pricing basis in the room.

Why does document counting beat named user pricing for EDI?

Because EDI volume is bounded and auditable while assumed user counts are not. Nine document types at counted volumes priced at a fraction of the named user theory, and SAP's own digital access model legitimized that counting basis.

How was the SAP audit claim defended step by step?

The defense rebuilt the facts before discussing money, in a fixed sequence that kept SAP responding to evidence rather than anchoring on assumptions.

1. Freeze the audit scope in writing and route all data requests through one owner.
2. Extract six months of interface logs and classify every inbound document type.
3. Map each middleware account to its actual integration purpose and volume.
4. Reprice the flows under the digital access document model as the counter position.
5. Negotiate closure on the evidence, keeping any S/4HANA conversation in a separate track.

What role did the S/4HANA proposal play in the negotiation?

SAP offered an S/4HANA conversion as the settlement wrapper, presented as making the claim disappear. The supplier declined and settled the audit standalone, because folding a disputed claim into a migration contract converts a one time dispute into a decade of inflated baseline spend under RISE with SAP style bundles. Support and maintenance terms stayed untouched.

What was the commercial outcome for the automotive supplier?

The audit closed 83 percent below the opening claim, priced on counted documents rather than assumed users. The supplier kept its ECC roadmap independent and entered later S/4HANA discussions without a settlement hanging over the table.

• Claim reduction: 83 percent off the opening position at close.
• No forced migration: the settlement stayed standalone with no bundled conversion.
• Forward posture: quarterly interface reviews now track document volumes against entitlements.

Could the exposure have been avoided entirely?

Largely yes. A standing map of interfaces, document types, and volumes would have left SAP nothing to anchor on. Estates that maintain that map settle indirect access questions in weeks, not quarters, in our engagement file.

Where the common advice on SAP indirect access claims is wrong

The standard advice is to treat an indirect access claim as leverage to negotiate a discounted S/4HANA or RISE migration, on the theory that the claim disappears into the new contract. We disagree. In roughly 20 to 30 SAP engagements Fredrik Filipsson advised in 2024 to 2025, buyers who folded audit settlements into migration deals paid more across the following three years than buyers who settled standalone, because the disputed amount quietly inflated the migration baseline. The buyer side move is to fight the claim on document flow evidence first, settle it on its own merits, and then negotiate any migration from a clean table.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Inventory every interface that writes into or reads from your SAP estate.
2. Classify the document types and monthly volumes on each interface now.
3. Map every middleware and service account to a documented integration purpose.
4. Model your exposure under both named user and digital access pricing before SAP does.
5. Keep any audit settlement separate from S/4HANA or RISE negotiations.
6. Set a quarterly interface review with named ownership and an escalation path.

Frequently asked questions

What triggered the SAP audit at the Michigan automotive supplier?

High transaction volume through middleware accounts triggered it. EDI flows from OEM customers and a 3PL entered ECC through technical accounts, and the audit treated every external party behind them as an unlicensed named user.

How much was the SAP indirect access claim reduced?

The claim closed 83 percent below the opening position. Counted document flows under the digital access model replaced assumed named user populations as the pricing basis.

What is SAP indirect access in plain terms?

Indirect access is any use of SAP data or functions through a non SAP system, such as EDI, middleware, or a web portal. SAP can license it per named user or per digital access document, and the choice of model changes the cost by multiples.

Is the digital access model always cheaper than named users?

No. Document pricing wins for bounded machine to machine flows like EDI, but estates with low document volume and few external users can be cheaper under named users. Model both before accepting either.

Did the supplier have to buy S/4HANA to settle the audit?

No. The settlement was standalone, and the supplier kept its migration roadmap independent. Folding disputed claims into migration contracts inflates the baseline you pay on for years.

How do you prepare for an SAP indirect access review?

Build the evidence before the letter arrives. Inventory interfaces, classify document types, count volumes, and map service accounts to purposes. An estate with that map removes the assumptions an audit claim is priced on.