SAP Indirect Access, The Licensing Trap Behind AB InBev's $600 Million Dispute
If your systems exchange data with SAP without anyone logging into SAP directly, there's a chance your organisation has licensing exposure it isn't yet aware of. This is known as SAP indirect access, or digital access under SAP's newer model, and for close to a decade it has been one of the most misunderstood areas of enterprise software licensing. For procurement and IT teams managing complex system landscapes, it's an easy risk to miss, simply because it doesn't show up in the places people usually look.
What Is SAP Indirect Access?
Indirect access happens when a third party system, such as a CRM, e-commerce platform or warehouse tool, creates, reads or updates data in SAP on a user's behalf. Even though no employee opens an SAP screen, SAP may still treat that activity as licensable use. Under the digital access model, this is typically measured by the number of documents created in SAP, rather than by named users.
The Diageo Case That Changed the Industry
The case most people in software licensing still point to is Diageo. In 2017, the UK High Court ruled in SAP's favour after finding that Diageo's Salesforce-based systems, which connected to SAP in the background, required additional licences. SAP had sought around £54 million, and the ruling reshaped how businesses and vendors alike think about integrations.
AB InBev and the Cost at Scale
AB InBev faced a similar issue on a much larger scale. SAP brought a claim worth around $600 million, and the brewer chose to settle privately rather than see it through, making it one of the most significant licensing disputes on record. For many organisations, it was a clear signal that indirect access wasn't a niche concern.
Why SAP Digital Access Matters More Today
Most businesses now have more systems connected to SAP than they did five years ago, not fewer. E-commerce platforms, CRM tools and warehouse systems all help teams work more efficiently, but depending on how SAP measures document volume, each of them could contribute to chargeable access. It's a natural result of growth and modernisation, which is exactly why it catches so many well-run teams off guard.
What the Audit Data Shows
Recent audit findings help put the risk into perspective. Research from Redress Compliance found that when companies measure their usage accurately, their true indirect document volumes are typically 25 to 45 percent lower than SAP's estimation tool suggests. Businesses that built their own defensible count before negotiating paid 30 to 60 percent less than those who accepted SAP's initial demand. With per-document rates varying widely and no public price list, that difference can become substantial very quickly.
How to Prepare Before an Audit
The most effective approach starts well before an audit letter arrives. Begin by mapping every system that touches SAP data, including those that only connect indirectly. From there, build your own count of what genuinely qualifies as a chargeable document, so you can review SAP's figures line by line rather than negotiating down from their starting point. SAP's rate is open to negotiation, but the number of documents you actually owe for is a matter of fact, and a well-evidenced count gives you a far stronger position than a discount on an inflated total.
Getting Support With SAP Licensing
Indirect access is complex, and it's completely understandable that it doesn't always get attention until renewal or audit time. At WYN, we've supported many clients through this kind of vendor exposure, and it's almost always simpler and more cost-effective to address before renewal than after an audit begins.
