The SAP vs. AB InBev Licensing Dispute: What Every SAP Customer Needs to Know in the Age of AI

There is a legal dispute from nearly a decade ago that most SAP customers either never heard about or dismissed as an isolated event. It is neither. As SAP pushes harder on its Autonomous Enterprise vision, Joule AI agents, and stricter API policies, the implications of that dispute are more relevant today than when it happened. If your organization runs SAP or is considering S/4HANA, this post explains what occurred, why it matters now, and what you should do about it.

What Happened: SAP’s $600M Arbitration Claim Against AB InBev

In February 2017, SAP America Inc. commenced an arbitration proceeding in New York against Anheuser-Busch Companies LLC, the US subsidiary of AB InBev, the world’s largest brewing company. According to AB InBev’s 2016 SEC filing on Form 20-F, SAP’s statement of claim alleged multiple breaches of a September 2010 software license agreement, “based on allegations that company employees used SAP systems and data, directly and indirectly, without appropriate licenses, and that the company underpaid fees due under the SLA.” SAP sought damages potentially in excess of $600 million and also sought reformation of the contract.

The case was conducted through private commercial arbitration under the American Arbitration Association, which meant filings and rulings were not matters of public record. AB InBev stated in its 2017 Annual Report, filed with the SEC in March 2018, that “the parties settled the dispute on 30 June 2017 and the matter is now closed.” Neither party disclosed the financial terms of the settlement.

The dispute is widely understood to have involved “indirect access”: the allegation that AB InBev’s employees accessed SAP data through a non SAP intermediary, reportedly Salesforce, without the corresponding SAP licenses. A contemporaneous UK case against Diageo, decided by the High Court in February 2017, established that even indirect access to SAP systems through a Salesforce application required named user licenses, a ruling that generated significant outcry from SAP customers across the industry.

This was not a case of software piracy or non-payment of invoices. SAP sued one of its largest, most sophisticated customers for using the customer’s own operational data to integrate with a third party platform the customer had separately licensed. That distinction matters enormously for how SAP customers should think about their licensing exposure today.

What This Means for SAP Customers Today

If this dispute happened in 2017, why does it matter now? Because the business environment has changed in ways that make the licensing and integration risk more acute, not less.

Three developments have made the stakes higher:

• SAP has formalized its API controls through a published API Policy that restricts how customers may use SAP interfaces, particularly for AI and automation
• SAP is actively promoting its Autonomous Enterprise vision and Joule AI platform as the default path for agentic automation inside S/4HANA environments
• The broader shift toward composable ERP and best of breed AI tools means more organizations are building integrations between SAP and third party systems, exactly the pattern that generated the AB InBev dispute

The risk has not gone away. It has multiplied.

SAP’s API Policy and What It Actually Says

SAP’s published API Policy (v.4.2026a) makes several restrictions explicit. According to the document, SAP prohibits API use for “interaction or integration with (semi-)autonomous or generative AI systems that plan, select, or execute sequences of API calls” except through SAP endorsed architectures and service specific pathways. It also prohibits “scraping, harvesting, or systematic and/or large-scale data extraction or replication” except through designated pathways.

In plain terms: if your organization wants to connect a third party AI agent or large language model to your S/4HANA environment, SAP expects you to do it through SAP-approved channels, not through arbitrary API calls. Whether those restrictions are legally enforceable against all customers in all jurisdictions is a separate question. The policy itself is clear.

When we advise clients preparing for S/4HANA selection and implementation, this is a conversation we now have in every engagement. The technology choices your organization makes about AI integration will have licensing and contractual implications that did not exist even two years ago.

SAP’s Autonomous Enterprise Vision and the Lock-In Question

SAP introduced its Autonomous Enterprise concept at SAP Sapphire in May 2026, centering it on the Joule AI platform, Joule Assistants, and over 200 specialized agents across finance, supply chain, HR, and other domains. SAP’s vision is that if customers go all-in on this stack, AI agents will run business processes from end to end with humans setting direction and reviewing outcomes.

That vision has genuine merit. But it raises a question every SAP customer should be asking: what happens if you want to use a different AI tool?

The AB InBev dispute illustrates the answer. If your organization wants to connect a third-party AI agent to your SAP data, SAP’s current API policy suggests you need to do it through SAP-sanctioned paths. If you connect it through other means, you may be creating the same kind of licensing exposure that cost AB InBev a settlement of undisclosed but reportedly substantial size.

This is the vendor lock in question made concrete. SAP customers who have invested heavily in S/4HANA, Ariba, Concur, SuccessFactors, and now Joule are progressively giving SAP more pricing power. The cost of switching is high. The cost of non-compliance, as AB InBev demonstrated, can also be high. SAP controls both levers.

In our experience advising organizations on digital transformation strategy, vendor lock in risk is almost always underestimated during the selection phase and acutely felt years into the relationship. S/4HANA customers today are entering a world where the lock-in dynamics are more sophisticated than they were in previous ERP generations.

Cost Exposure: The Pricing Power Implications

The AB InBev dispute also illustrates something that extends beyond licensing compliance: it demonstrates that SAP is willing to use its legal leverage to protect its revenue model. That willingness has implications for how SAP will price its products over time.

SAP is investing heavily in S/4HANA, Joule, and the Business AI Platform. That investment has to be recouped. Organizations that are deeply embedded in the SAP ecosystem and that lack credible exit options are the most natural source of that recoupment through price increases, new licensing models, and expanded Digital Access charges as automation and AI agents generate more document events.

SAP’s Digital Access licensing model, which charges based on the number of documents generated through non-SAP interfaces, was partly introduced in response to the indirect access controversy following the Diageo and AB InBev cases. It simplified the licensing model in some ways. But it also created a new exposure: as your organization automates more processes and generates more documents through third-party systems that connect to SAP, your Digital Access fees can rise in ways that are difficult to predict.

SAP Is Not Wrong About the Technology Direction

It is worth being precise about what this post is and is not arguing. SAP S/4HANA remains one of the most capable ERP platforms available. The investment SAP is making in AI and agentic capabilities is real. Joule Assistants, as demonstrated at Sapphire 2026, can compress processes that used to take days into minutes. For organizations with complex, global operations, the SAP ecosystem offers depth that most competitors cannot match.

The concern is not with the technology. The concern is with the control model that surrounds it: the licensing terms, the API restrictions, the arbitration-based dispute resolution, and the implicit assumption that once you are deeply embedded, the terms of the relationship will be set by SAP rather than negotiated between equals.

That is a legitimate concern for any organization making a multidecade commitment to an enterprise platform.

What SAP Customers Should Do

The AB InBev case is not a reason to avoid SAP. It is a reason to approach SAP with clear eyes about the terms of the relationship. Here are the most important actions to take.

Move on Your Own Timeline

SAP has a 2030 migration deadline for legacy ECC customers. That deadline creates pressure, and SAP partners and sales teams will emphasize it. But the deadline reflects SAP’s business model priorities, not your organization’s operational readiness. If you are not ready, do not let the noise in the SAP community drive a premature commitment. A poorly timed S/4HANA implementation is significantly more expensive than a delayed one. When we advise clients on organizational change management for S/4HANA, we consistently find that organizations that rush into implementation to meet vendor deadlines are the ones that struggle most post go-live.

Redefine What SAP Means to Your Organization

Rather than treating S/4HANA as a platform that must handle every business function, consider treating it as a system of record for core financial, regulatory, and operational data. Other systems, including third party AI tools, can then work around that core. This reduces your dependency on SAP for innovation-driven functions where best of breed tools outperform what SAP offers, while keeping the core stable and compliant.

Identify which API integrations SAP has published and sanctioned, and which ones are unsanctioned. That distinction will be critical as your organization expands its AI footprint.

Understand Your Digital Access Exposure

Work with your SAP account team or an independent advisor to model your current and projected Digital Access consumption. Every time a non SAP system creates a sales order, purchase order, or other document in S/4HANA, that transaction may count toward your Digital Access usage. As automation expands, this can grow faster than expected. Build that growth into your total cost of ownership model before it appears as a surprise on a licensing invoice.

Negotiate From a Position of Strength While You Have One

The best time to negotiate with SAP is before you are fully embedded. If you are in the selection phase or early in your S/4HANA journey, negotiate:

• Price caps or limits on annual subscription and Digital Access fee increases
• Clear definitions of which integrations and API uses are sanctioned
• Data ownership and portability rights, including your right to extract data in machine readable formats
• Audit rights and notification requirements before any compliance review
• Exit provisions and transition assistance terms

If you are a larger organization, you have leverage. Use it. The AB InBev settlement demonstrated that even a company with 25,000 employees and global operations could end up in arbitration with SAP over licensing terms. Organizations with less scale and less legal sophistication are even more dependent on getting the contract right before signing.

Evaluate Third Party AI Integrations Carefully

If your organization is planning to connect generative AI tools, large language models, or agentic AI platforms to your S/4HANA environment, have a legal and technical review of SAP’s current API Policy before doing so. SAP’s policy explicitly limits unsanctioned AI integration. The licensing and contractual exposure from running an unsanctioned AI integration against your SAP environment is real and documented.

For more on how to evaluate S/4HANA successfully as an independent investment rather than a vendor-driven decision, our Definitive Guide to a Successful SAP S/4HANA Digital Transformation covers the planning, governance, and risk management steps that protect your organization throughout the program.

Questions We Hear Most

Does the AB InBev Settlement Set a Legal Precedent for SAP Customers?

The settlement itself does not set precedent because it was reached through private arbitration under confidentiality. The Diageo case, which was decided in an English High Court and is therefore public, does carry legal weight in UK jurisdictions. It established that indirect access to SAP systems through a Salesforce application required named user licenses even when users never touched the SAP interface directly. SAP customers globally should treat that ruling as an indication of how SAP interprets its licensing terms, even if it is not binding outside UK courts.

Is the Risk Higher for Organizations Using AI Agents Than for Those Who Weren’t?

Yes, materially so. AI agents by design execute sequences of API calls, often at high volume and in automated sequences. SAP’s current API Policy explicitly addresses this scenario and restricts it to SAP endorsed pathways. An organization deploying a third party AI agent that autonomously queries and writes to S/4HANA without going through SAP Business Technology Platform or another SAP sanctioned integration layer is creating licensing exposure that did not exist in the period before AI. In our experience, this is one of the most underestimated risks in current SAP modernization programs.

Should You Avoid SAP Because of This Risk?

No. The risk is manageable with the right contracts, the right technical architecture, and the right independent advice. SAP remains one of the most capable enterprise platforms available, and for complex global organizations, it is often the right choice. The issue is not whether to use SAP. It is whether to use SAP with realistic expectations about the vendor relationship, carefully negotiated contracts, and a clear eyed view of where your data rights begin and end.

If your organization is working through S/4HANA selection, implementation, or AI integration strategy and wants independent guidance, contact us at eric.kimberling@thirdstage-consulting.com.