Global Tier 1 Automotive Supplier: How We Cut SAP Indirect Access Exposure by 80%

The Situation

Each of these manufacturers operated a global ECC or S/4HANA backbone that fed three categories of non-SAP systems: a Manufacturing Execution System (MES) on the shop floor, a dealer and aftermarket parts portal, and a supplier collaboration platform. Hundreds of millions of documents flowed in and out of SAP every year. None of the human users on those external systems held an SAP Named User licence.

The audit letter cited Note 2305757 on indirect access, the 2018 Digital Access pricing model, and a SAP for Me extract showing every system integration registered against the production tenants. SAP's commercial team quantified exposure two ways. First, on the old Named User basis: every dealer, technician, and supplier rep needed a licence, putting the back-licence claim at $30M to $45M in three of the four largest engagements. Second, on the Digital Access basis: every Sales Order, Delivery, and Material Document originating outside SAP would attract a per-document fee, with the larger of the two numbers presented as the binding ELP. Add support and back maintenance, and the opening claim sat between $40M and $60M.

Internal SAP teams had no documented architectural inventory of every integration. The procurement teams could not answer SAP's first question without disclosing data they had not yet validated. The default reaction across all three engagements was to ask SAP for a Digital Adoption Acceleration Programme (DAAP) settlement quote and pay it down. We were called before that conversation closed.

What We Did

1. Froze the data flow to SAP. Before a single new document went to SAP's measurement team, we audited what had already been shared via STAR, USMM, and the Solution Manager Maintenance Planner. Two of the three clients had already disclosed broader integration scope than necessary. We containerised the scope of the audit and pushed back, in writing, against further volunteered data.
2. Built a forensic integration inventory. Our team rebuilt the architecture map of every connection into the SAP backbone. We separated technical integrations into four buckets: human-driven (eligible for indirect access claims), system-driven inbound (creating documents), system-driven outbound (consuming documents, generally not chargeable), and pure batch interfaces that SAP's contractual definition does not cover.
3. Challenged the Digital Access document count. SAP's measurement assumed every Material Document and every Invoice was a chargeable document. We applied the SAP Digital Access price list rules strictly. Sub-document inserts, status updates, and reposts do not count as chargeable creations. In each engagement, applying the rule precisely cut the chargeable count by 40 to 60 percent before any other defence.
4. Reclassified the dealer portal. SAP's claim treated the dealer portal as a Named User scenario. Our review of the actual data flows showed that dealers did not create SAP documents directly. They submitted requests to an intermediary system that, after human gate review, generated documents in SAP. We argued the chargeable event sat with the gate-review user inside the SAP system, not with the dealer outside. SAP accepted the argument in two of three cases and partially conceded in the third.
5. Negotiated a forward Digital Access subscription. Once the chargeable population was right-sized, we converted the residual exposure into a forward-looking subscription priced against actual recent volume, not a five-year back-licence. The Cloud Extension Policy and the 2022 contractual options around DAAP gave us the framework to convert a one-shot punitive payment into a predictable annual line item.
6. Rewrote the contractual definition of indirect use. The single most valuable move. We negotiated specific contractual language into the new Order Form that defines what constitutes indirect use for this customer, scopes it to the named integrations, and caps annual document growth before any repricing trigger fires. The pattern protects the buyer against the next audit cycle, not just this one.

The Outcome

Across the engagements, the final settlement positions fell into a tight band. Opening SAP claims of $40M to $60M settled at $7M to $14M, a reduction of 70 to 85 percent. The aggregate back-licence demand was eliminated in every case. In its place, each customer signed a forward Digital Access subscription priced against a verified document volume, with annual growth caps and a renegotiation trigger written into the Order Form. The subscription line item runs at 8 to 12 percent of the original SAP opening claim, annualised. None of the four engagements ended in escalation to SAP's legal team. None required litigation.

Three secondary outcomes mattered as much as the headline number. First, internal SAP scope creep stopped. Procurement and architecture teams now operate under a documented integration register reviewed quarterly, so the next measurement cycle starts from a known position, not a discovery exercise. Second, the dealer portal architecture was redesigned during the engagement to interpose a single human-gated document entry layer, neutralising the future indirect access argument permanently. Third, the contract clauses we negotiated now act as a template for the parent group's other operating companies entering SAP renewal cycles.

What Other Enterprises Can Take From This

Manufacturers face a structural indirect access risk that retailers and financial services do not. The shop floor, the dealer network, and the supplier base sit outside SAP but feed it documents every minute of every working day. SAP's audit teams know this. The 2018 Digital Access pricing model exists in large part because manufacturers are the easiest place to apply it. If your business runs an MES, a dealer or distributor portal, or a supplier collaboration platform that creates documents in SAP, you have an indirect access exposure today, whether SAP has raised it yet or not.

The two errors we see repeatedly are early disclosure and acceptance of SAP's document classification. Most internal teams answer SAP's measurement questions in good faith, sharing architecture diagrams and integration inventories before knowing how SAP will interpret them. By the time the back-licence claim arrives, the data has already been packaged for SAP's case. The defence then becomes a retreat from disclosed positions rather than an argument from first principles. The right time to read the SAP CLA on indirect use, the Digital Access price list rules, and your own contractual definitions is before the audit letter arrives, not after.

The second error is treating Digital Access as a one-way conversation. SAP presents the back-licence claim and the per-document price as the position. They are an opening bid. The chargeable document count is challengeable on architectural grounds. The settlement vehicle is convertible from a back-licence to a forward subscription. The price per document is volume-band negotiable. Most material outcomes come from arguing the architecture, not from arguing the numbers SAP put in front of you. For more on the underlying mechanics, our SAP audit defence guide walks through the document classifications, USMM behaviour, and contractual definitions that drive these claims.