Engineering & Infrastructure — United Kingdom · SAP Licensing · Updated February 2026
01 Client Background: A Leading UK Engineering Firm with Complex SAP Dependencies
The client is a major engineering firm headquartered in the United Kingdom with over 50,000 professionals deployed across global projects spanning infrastructure, energy, transport, and environmental engineering. SAP is the backbone of the firm's enterprise operations. SAP ECC manages financials, project accounting, materials management, and human capital management, while various third-party systems and field devices integrate with SAP to support project delivery, time recording, and resource allocation across distributed global project sites.
The complexity of the firm's SAP environment reflects the nature of large-scale engineering operations. Thousands of employees interact with SAP directly through the SAP GUI or web-based interfaces. Thousands more interact with SAP data indirectly through third-party project management tools, field reporting applications, mobile time-recording systems, and automated interfaces that read from or write to SAP without the user ever logging into the SAP system directly.
This indirect access pattern is the single most common and most contentious area of SAP licensing disputes and has been the basis for audit claims across industries worldwide.
The firm had operated its SAP landscape for over a decade, during which time the IT environment had grown organically. New third-party integrations had been added as project requirements evolved, user populations had shifted as the firm expanded into new geographies and engineering disciplines, and the relationship between actual day-to-day SAP usage and the firm's licence entitlements had become increasingly misaligned.
02 The SAP Audit: £12 Million in Claimed Non-Compliance
SAP initiated a licence audit under the measurement rights provisions in the firm's SAP contract. The audit was conducted by SAP's internal audit team using SAP's standard measurement methodology, which involves extracting user and system access data from the SAP landscape and comparing it against the firm's licensed entitlements. SAP's audit findings identified three primary areas of claimed non-compliance.
Indirect Access Claims
SAP claimed that thousands of users who accessed SAP data through third-party systems required SAP named user licences. Project management tools, field devices, time-recording applications, and automated data interfaces were all flagged. SAP's position was that any system or user that reads from or writes to SAP, regardless of whether they log into SAP directly, requires a corresponding SAP licence. This interpretation, if accepted, would have required the firm to licence a substantial portion of its 50,000+ workforce. This represented the largest component of the £12 million exposure.
Licence Type Misalignment
SAP's audit identified users whose licence types did not match their actual system usage. Users with lower-cost licence types (such as SAP Limited Professional or SAP Employee Self-Service) were performing transactions that SAP classified as requiring higher-cost licence types (such as SAP Professional). SAP's measurement classified users based on the most expensive transaction they had executed, regardless of how frequently they performed that transaction or whether the transaction was performed accidentally.
Unmonitored User Growth
The firm's SAP user population had grown beyond its licensed entitlements over the course of several years. New employees, contractors, and project-specific users had been provisioned with SAP access as business needs required, but the firm's internal processes had not consistently tracked new user creation against available licence capacity. This was the most straightforward component to quantify and address.
03 Redress Compliance's Engagement: Four-Phase Audit Defence
The firm engaged Redress Compliance to challenge SAP's audit findings, reduce the financial exposure, and negotiate a resolution aligned with the firm's actual SAP usage rather than SAP's maximised compliance interpretation.
Redress Compliance's approach follows a structured four-phase audit defence methodology that has been refined across numerous SAP audit engagements and consistently delivers reductions of 70 to 95% from SAP's initial claims: audit review and analysis, usage validation and optimisation, negotiation with SAP, and governance framework implementation.
Redress Compliance's independence from SAP was essential for this engagement. As an advisory firm with no SAP partnership, reseller relationship, or referral arrangement, every analysis and recommendation was aligned exclusively with the firm's interests. SAP's audit team has an inherent commercial interest in maximising the audit outcome. Independent advisory ensures that the audit findings are challenged rigorously, systematically, and with the technical depth required to counter SAP's methodology effectively.
04 Phase 1: Audit Review and Analysis
Redress conducted an in-depth analysis of SAP's audit findings, examining every component of the £12 million claim to identify inaccuracies, overstatements, and areas where SAP's interpretation of the licence agreement did not align with the contractual terms or actual usage patterns.
Indirect Access Claim Analysis
Redress examined every third-party integration that SAP had flagged as generating indirect access liability. The analysis revealed that SAP's methodology had significantly overestimated the indirect access exposure. Several integrations were read-only reporting connections that did not create, modify, or process SAP data in ways that triggered licensing obligations under the firm's contract. Other integrations used SAP data that was replicated to external databases, and the users accessing those external databases never interacted with the SAP system at all. Redress compiled detailed technical evidence documenting each integration's actual data flow.
Contract and Entitlement Review
Redress conducted a thorough review of the firm's historical SAP contracts, amendments, and order forms dating back over a decade to identify favourable clauses, historical entitlements, and contractual provisions that SAP's audit team had overlooked or misinterpreted. The firm's original contract contained specific provisions regarding third-party system access that were more favourable than SAP's current standard terms. Certain licence types included broader usage rights than SAP's audit methodology had assumed. Historical amendments contained entitlements that had not been reflected in SAP's compliance calculation.
Licence Type Classification Review
Redress challenged SAP's methodology for classifying users into licence types. SAP's approach classified users based on the single most expensive transaction executed, even if that transaction was performed once accidentally or as part of a testing exercise. Redress analysed actual usage patterns over a twelve-month period, demonstrating that many users classified by SAP as requiring Professional licences had only performed the higher-tier transactions on isolated occasions and that their consistent usage pattern aligned with their existing lower-cost licence types.
05 Phase 2: Usage Validation and Optimisation
While Phase 1 focused on challenging SAP's audit findings, Phase 2 focused on proactively optimising the firm's SAP licensing position to reduce the actual compliance gap. Reducing this genuine gap before entering negotiation strengthens the firm's position by demonstrating good faith and limiting the baseline from which SAP calculates its commercial expectations for the resolution.
Indirect Access Remediation
For integrations that did generate legitimate indirect access liability, Redress recommended technical changes to reduce or eliminate the licensing requirement. This included redirecting certain data flows through SAP's standard APIs, implementing middleware that prevented unnecessary SAP data writes from third-party systems, and reconfiguring field device integrations to batch data through a single service account rather than generating individual user-level access events.
Licence Reallocation
Redress identified underutilised SAP licences across departments and geographies and reallocated them to areas where the firm genuinely needed additional capacity. This reallocation addressed some of the user growth beyond entitlement without requiring any new licence purchases. The firm had sufficient total licences but they were assigned to users who no longer needed them.
Legacy System Decommissioning
Several legacy systems that integrated with SAP were no longer actively used or had been superseded by newer platforms. These legacy integrations were still running and generating SAP access events that SAP had included in its indirect access calculation. Redress recommended decommissioning these legacy systems, which eliminated the associated indirect access liability and reduced ongoing infrastructure and maintenance costs.
User Account Cleanup
Inactive user accounts belonging to departed employees, completed project contractors, and test accounts were identified and deactivated. In an engineering firm with high contractor turnover on global projects, the number of inactive and orphaned accounts was substantial and represented a meaningful portion of the audit claim. Removing these accounts reduced the user count and eliminated a portion of the licence type misalignment claims.
06 Phase 3: Negotiation and Resolution with SAP
With a comprehensive evidence base from the audit review and a strengthened compliance position from the optimisation actions, Redress developed and executed a negotiation strategy with SAP's commercial team. All technical evidence was compiled, all optimisation actions were completed, and the firm's corrected compliance position was fully documented before the first substantive negotiation meeting with SAP.
The negotiation was structured around three key elements: the corrected compliance position demonstrating that SAP's £12M claim was significantly overstated, the proactive remediation evidence showing good faith, and the firm's strategic value as a long-term SAP customer.
Negotiation Results: £12M Reduced to £800K
Indirect Access Claims: 90%+ Reduction
Redress's technical evidence demonstrated that the majority of SAP's indirect access claims were overstated or incorrectly classified. The detailed data flow analysis, combined with the contractual provisions identified in the contract review, reduced the indirect access component of the claim by over 90%. SAP accepted the technical evidence and revised its assessment for the integrations that Redress had challenged.
Licence Type Misalignment: Evidence-Based Reversal
The twelve-month usage pattern analysis demonstrated that the majority of users classified by SAP as requiring upgrade to Professional licences had consistent usage patterns aligned with their existing lower-cost licence types. SAP's methodology of classifying users based on a single transaction was challenged successfully, reducing this component of the claim significantly.
Cost-Neutral Resolution: £800K Investment
The final settlement of £800,000 was structured as a cost-neutral resolution. The payment was applied entirely toward additional SAP licences that the firm needed to support its growth plans and new project requirements. Rather than paying a compliance penalty, the firm invested £800,000 in licences that delivered genuine business value, including additional named user licences for expanding geographies and updated licence types.
Relationship Preservation
The negotiation was conducted professionally and collaboratively, preserving the firm's relationship with SAP. The firm depends on SAP for mission-critical operations and needed to maintain a productive commercial relationship for future support, upgrades, and contract negotiations. The resolution established a constructive precedent for future interactions with SAP's audit and commercial teams.
07 Phase 4: Governance Framework Implementation
The final phase focused on preventing future compliance risks by implementing a comprehensive SAP licensing governance framework. Without governance, the organic drift between usage and entitlements that created the original audit exposure will inevitably recur.
Real-Time Usage Tracking
Implemented monitoring tools that track SAP user activity, licence type consumption, and indirect access events in real time. The monitoring system generates automated alerts when usage approaches licence thresholds, when new integrations are created that could generate indirect access liability, or when user classifications drift from their assigned licence types. This real-time visibility replaces the previous approach of discovering compliance gaps only when SAP conducted an audit.
Governance Procedures
Established formal processes for SAP user provisioning, integration management, and licence allocation. New SAP users must be approved through a licensing review process that assigns the correct licence type based on planned usage. New third-party integrations must undergo a licensing impact assessment before deployment. Quarterly licence reviews reconcile actual usage against entitlements and recommend reallocation or procurement actions.
Team Capability Building
Delivered targeted training for IT, procurement, and project management teams to enhance their understanding of SAP's licensing model, indirect access implications, and compliance obligations. The training covered SAP named user licence types, indirect access scenarios specific to engineering project environments, and the firm's contractual terms. This ensures that teams responsible for SAP-related decisions understand the licensing consequences of their technical and operational choices.
08 Outcome: Financial and Strategic Impact
"Redress Compliance transformed a daunting audit process into an opportunity for operational improvement. Their expertise saved us millions and provided us with a roadmap for future compliance and cost management. They were an invaluable partner throughout the journey."
The engagement delivered transformative results across financial, operational, and strategic dimensions. The £12M audit claim was reduced to £800K. A 93% reduction that saved the firm £11.2 million in potential compliance costs.
The £800K settlement was structured as a cost-neutral investment in additional SAP licences that supported the firm's growth plans and new project requirements. The firm paid nothing in penalties and instead acquired licences that delivered genuine operational value for expanding geographies and evolving project needs.
Operationally, the licence reallocation, legacy system decommissioning, and user account cleanup reduced ongoing licensing costs and eliminated unnecessary infrastructure that had been generating phantom indirect access events.
Strategically, the firm's relationship with SAP was preserved and strengthened. The collaborative resolution established a positive precedent for future interactions. The governance framework provides continuous assurance that the firm's SAP licensing remains compliant and optimised, significantly reducing the risk and potential financial impact of any future SAP audits.
| Outcome Dimension | Before Redress Engagement | After Redress Engagement |
|---|---|---|
| Financial exposure | £12 million audit claim | £800,000 cost-neutral settlement (93% reduction) |
| Indirect access position | Thousands of users flagged with overstated methodology | Claims reduced 90%+ through technical evidence |
| Licence alignment | Misaligned types and surplus inactive accounts | Right-sized, reallocated, and actively managed |
| Governance | No formal SAP licensing governance | Real-time monitoring, formal processes, trained teams |
| Net result | £11.2M saved, licences acquired for growth, ongoing compliance assured | |
09 Lessons for Engineering and Professional Services Firms Facing SAP Audits
Challenge Indirect Access Claims Rigorously
Indirect access is the most common and most overstated component of SAP audit claims. SAP's standard methodology frequently overestimates indirect access exposure by classifying integrations that do not generate licensing obligations under the specific contractual terms. Every indirect access claim should be challenged with detailed technical evidence of actual data flows, combined with a thorough review of the contractual provisions that define what constitutes licensable indirect access.
Review Historical Contracts Thoroughly
SAP contracts accumulate amendments, order forms, and supplementary terms over years or decades. Historical contracts often contain provisions that are more favourable than SAP's current standard terms. These provisions remain contractually valid and can significantly reduce audit exposure. A thorough contract review going back to the original agreement frequently reveals entitlements and usage rights that SAP's audit team has not considered.
Optimise Before You Negotiate
Proactive optimisation actions like licence reallocation, legacy system decommissioning, user cleanup, and integration remediation reduce the genuine compliance gap before the negotiation begins. This strengthens the negotiation position by demonstrating good faith and reducing the baseline from which SAP calculates its commercial expectations. Organisations that optimise before negotiating consistently achieve better outcomes than those that negotiate first and optimise later.
Structure Settlements as Investments
A cost-neutral settlement where the payment is applied toward additional licences rather than treated as a compliance penalty is achievable in many SAP audit situations. The customer acquires licences that support their business needs rather than paying a penalty with no return, and SAP secures ongoing licence revenue and customer commitment. Positioning the settlement as an investment in the relationship changes the negotiation dynamics entirely.
Frequently Asked Questions
The reduction was achieved through four complementary strategies: rigorous technical analysis demonstrating SAP's indirect access claims were significantly overstated, thorough contract review identifying favourable historical provisions SAP had overlooked, evidence-based challenge of SAP's licence type classification methodology using twelve months of actual usage data, and proactive optimisation actions (licence reallocation, legacy system decommissioning, user cleanup) that reduced the genuine compliance gap before negotiation. The final £800K settlement was structured as an investment in additional licences rather than a compliance penalty.
SAP indirect access occurs when users or systems access SAP data through third-party applications, middleware, or automated interfaces rather than logging into SAP directly. SAP's position is that any system or user reading from or writing to SAP requires a corresponding licence. This interpretation is contentious because it potentially requires organisations to licence thousands of users who never interact with SAP directly. SAP's standard audit methodology frequently overestimates indirect access exposure, and the specific contractual terms governing indirect access vary between customers and contract generations.
SAP contracts accumulate amendments, order forms, and supplementary terms over years or decades. Historical contracts often contain provisions that are more favourable than SAP's current standard terms. For example, older contracts may have broader definitions of permitted usage, different indirect access provisions, or specific entitlements that SAP's audit team does not consider. These historical provisions remain contractually valid and can significantly reduce audit exposure when identified and applied to the audit response.
Proactive optimisation reduces the genuine compliance gap before the negotiation begins. Actions like reallocating underutilised licences, decommissioning legacy integrations, cleaning up inactive user accounts, and remediating indirect access configurations demonstrate good faith and reduce the baseline from which SAP calculates its commercial expectations. Organisations that optimise before negotiating consistently achieve better outcomes because SAP's negotiating leverage is reduced when the remaining gap is smaller and well-documented.
A cost-neutral settlement is one where the financial resolution is applied entirely toward additional SAP licences that the organisation needs for future growth, rather than treated as a compliance penalty. In this engagement, the £800K was invested in additional named user licences and updated licence types that supported the firm's expansion plans. This approach benefits both parties: the customer acquires licences that deliver genuine business value, and SAP secures ongoing licence revenue and customer commitment.
SAP audit defence engagements typically span 10 to 16 weeks from initial audit response through final negotiated resolution. The timeline depends on the complexity of the SAP landscape, the number of third-party integrations generating indirect access claims, the depth of historical contract analysis required, and SAP's responsiveness during the negotiation phase. Starting the engagement as soon as the audit notification is received provides the most time for thorough analysis and optimisation before negotiation.
Reductions of 70 to 95% from SAP's initial audit claims are consistently achievable when the defence is conducted with rigorous technical analysis, thorough contract review, and proactive optimisation. SAP's standard audit methodology is designed to identify the maximum possible compliance exposure, and the initial findings almost always contain elements that can be challenged successfully. The specific reduction depends on the composition of the audit claim, the strength of the organisation's historical contract terms, and the extent to which indirect access claims are overstated.
📚 Related Reading
SAP Digital Access Advisory Service → SAP Contract Negotiation Playbook → SAP Licence Optimisation Services → SAP DAAP: Evaluate, Negotiate, Avoid Traps → SAP Contract Negotiation Service → SAP Knowledge Hub →SAP Audit Defence
Service
Digital Access Advisory
Service
SAP Advisory Services
Service
SAP Knowledge Hub
Knowledge Hub