German Automotive Manufacturer Avoids €4M Audit Risk and Negotiates Phased RISE with SAP Migration

The Client: Automotive Manufacturing at Scale

The client is a Tier 1 automotive supplier with approximately 12,000 employees across nine manufacturing sites in Germany, Poland, and the Czech Republic, supplying components to four major German automotive OEMs. Its SAP ECC landscape — EHP 7, installed in 2017 — covered the full manufacturing and supply chain operation, including production planning, plant maintenance, quality management, materials management, and financial consolidation.

The client had invested significantly in a proprietary supplier integration portal that allowed OEM customers and upstream suppliers to exchange production schedules, capacity data, just-in-time delivery windows, and quality conformity documentation directly with the SAP backend. The portal had been in operation since 2019, handling approximately 2.8 million transactions annually across approximately 180 connected external partners — OEM procurement systems, tier-2 suppliers, and logistics providers.

In March 2025, the client received an SAP audit notification requesting participation in an enhanced licence audit under the LAW process. The timing coincided with a period of significant pressure within the German automotive supply chain, where multiple Tier 1 suppliers had already been subject to SAP indirect access claims following the expanded audit activity SAP had initiated across manufacturing-sector clients from 2024 onward. The client's IT director recognised the supplier portal as a likely audit target and engaged independent advisers before responding to SAP's notification.

The Indirect Access Exposure: What the Portal Was Doing

Understanding the Document Flow

Under SAP's Digital Access licensing model, which applies to any system interaction that creates, modifies, or reads SAP data through a non-SAP interface, the chargeable unit is a document created within SAP per year, segmented by document type. The supplier portal's transactions were mapped against SAP's document type taxonomy:

• Production schedule synchronisation events were creating planned order modifications — a chargeable document type — each time an OEM system pushed an updated delivery window to SAP. At roughly 400,000 events annually, this was the single largest volume category.
• Quality notification exchanges from OEM quality systems were creating quality defect notifications and corrective action records in SAP's QM module — a further 180,000 documents annually.
• Delivery confirmation records from the logistics integration were creating goods movement documents in SAP — approximately 220,000 annually across nine sites.
• Invoice reconciliation messages from supplier systems were triggering SAP MM invoice verification document creation — approximately 340,000 annually.

Total: approximately 1.14 million chargeable document creation events annually, across four document types, for four years. At SAP's applicable list prices for the relevant document categories, the retroactive exposure for the four-year period was quantified at approximately €4.2 million, with an ongoing annual licence requirement of approximately €1.1 million per year that was not in the IT budget.

Why This Exposure Existed

The portal had been designed and deployed by the client's internal IT team in 2019. The team had no knowledge of SAP's Digital Access rules at the time of design — the licensing framework was introduced with SAP's 2018 Digital Access announcement, and the practical implications for manufacturing integrations were not widely understood by IT teams deploying ECC landscapes at that point. The SAP account team had been aware of the portal's existence — it had been discussed as a competitive advantage in customer conversations — but had never raised it as a potential Digital Access topic in four years of account management.

This is the pattern we see consistently across automotive and manufacturing clients: integration architectures that were built for operational efficiency without licensing input, in environments where the SAP account team was fully aware of the integration and chose not to raise it commercially until an audit created the opportunity to price it at maximum enforcement rates.

The Response Strategy: Audit Defence Before Commercial Resolution

Phase 1: Independent Quantification

The first requirement, before engaging SAP's audit team in any substantive conversation, was to produce the client's own independently verified quantification of the exposure. SAP's audit process — if the client responded to the notification without a pre-prepared position — would proceed with SAP's own measurement tools producing SAP's own document counts, applied against SAP's list pricing with no reduction for the client's commercial history or future spend commitment.

The independent quantification exercise examined the portal's transaction logs against SAP's document type taxonomy, applying the same measurement methodology SAP's audit team would use but before SAP had the opportunity to run its own numbers. This produced the client's position: 1.14 million chargeable documents annually at the applicable category pricing, producing a four-year retroactive exposure of approximately €4.2 million at list. This figure became the baseline for all subsequent commercial discussions.

The quantification also identified approximately 380,000 annual transactions that the client's technical team had initially counted as chargeable but that fell outside the Digital Access scope under SAP's measurement rules — specifically, certain read-only data sync events that did not create SAP documents. This 25 percent reduction in the initially estimated exposure was commercially significant and only identified through independent technical analysis.

Phase 2: Digital Access Adoption Programme (DAAP)

SAP's Digital Access Adoption Programme provides a pathway for customers to resolve historic indirect access exposure through a forward-looking licence commitment at a rate substantially below the retroactive enforcement pricing. Under DAAP, the client agrees to licence the relevant document types going forward at the published programme rates, and SAP reduces or waives the historic retroactive claim in exchange for the multi-year commitment.

The DAAP approach is not volunteered by SAP's audit team. It is only accessible to clients who know it exists and specifically request it as the commercial resolution mechanism. Entering the audit response process without knowing about DAAP means accepting the enforcement pathway — which produces a settlement based on historic list pricing with minimal reduction for future commitment.

The client's negotiation team requested DAAP resolution explicitly, supported by the independent quantification that provided a credible counter to SAP's audit findings. The DAAP negotiation produced a settlement for the historic four-year period and a forward licence for the document types at rates that reflected the client's overall SAP spend relationship and its commitment to S/4HANA migration.

Phase 3: Converting the Audit into a Migration Agreement

The most commercially significant element of the negotiation was converting the audit resolution into the framework for the client's S/4HANA migration. The client had been evaluating an S/4HANA migration for two years but had been unable to commit to a timeline — the nine-site manufacturing landscape included highly customised production planning processes that required significant remediation before standard S/4HANA functionality could be deployed.

SAP's audit team's objective is revenue from compliance. SAP's account team's objective is long-term contracted revenue from migration. These objectives can be aligned: an organisation that commits to a phased S/4HANA migration as part of an audit resolution gives SAP's account team a strategic win that justifies significant flexibility on the audit settlement from SAP's commercial leadership. The client's advisers structured the conversation explicitly to create this alignment — making the migration commitment the commercial currency that reduced the audit settlement and secured the phased migration timeline the operations team required.

The Final Negotiated Position

The Phased Migration: Why It Mattered Operationally

The 2027 end of mainstream maintenance for ECC EHP 6–8 creates genuine pressure on clients to commit to S/4HANA migration timelines. SAP's account team had used this deadline as leverage in pre-audit renewal conversations, positioning 2027 as a hard constraint that required the client to commit immediately to an aggressive migration timeline. The Horváth 2025 survey of 200 major SAP customers found that only 37 had completed their S/4HANA migration — with more than 60 percent of those in progress running over budget and behind schedule. For a nine-site automotive manufacturer with complex production planning customisations, a 2027 migration deadline was operationally unrealistic.

The negotiated phased timeline — completion by end of 2029 — extended the operational window by two years while securing the client's ECC maintenance continuity through the extended maintenance programme at no uplift, a provision that is technically available under SAP's maintenance framework but rarely offered proactively by account teams who are incentivised to sell RISE subscriptions rather than extended on-premise maintenance.

What Automotive Suppliers Should Know

The German automotive manufacturing sector is one of SAP's highest-priority indirect access audit targets as of 2025 and 2026. The supply chain integration architectures that characterise Tier 1 and Tier 2 suppliers — JIT/JIS delivery portals, quality system integrations, OEM procurement system connections — generate exactly the document types that SAP's Digital Access model is designed to capture. The question is not whether an automotive supplier operating a connected supply chain portal has indirect access exposure. It is how large that exposure is and whether it is quantified and managed before SAP quantifies it first.

Third-party maintenance from providers including Rimini Street remains a viable alternative for ECC estates where the migration timeline cannot be compressed to 2027 — typically offering rates up to 50 percent below SAP's extended maintenance pricing. For a manufacturing operation where the operational risk of a compressed S/4HANA migration outweighs the extended maintenance premium, this is a relevant commercial option that SAP does not discuss proactively and that changes the leverage balance in migration timeline negotiations.