In short
An SAP licence has traditionally been about the users who work with SAP. But what if a webshop, an app or another system creates data in SAP? Then that system uses SAP indirectly. SAP calls this indirect access and can charge licence fees for it. Well-known cases woke many companies up: in 2017 the drinks group Diageo lost a court case brought by SAP over users who worked with SAP indirectly through Salesforce, and that same year the brewer AB InBev reached a settlement after a claim of hundreds of millions.
Digital access
Since 2018 SAP has offered a pricing model based on documents: digital access. You then pay not per connected user, but for the documents that external systems create in SAP, such as sales orders, invoices, purchasing documents and financial postings. Merely reading data generally does not count in that model; creating documents does.
Why this matters for integrations
- Every interface that creates documents in SAP may count.
- The chosen architecture determines how many documents are created. An interface that creates a document per line costs more than one that bundles them.
- A low-code app or portal on top of SAP is a common source of indirect use.
So choose the integration architecture deliberately, interface by interface.
What you do
- Map out your interfaces. Which systems only read, and which create documents?
- Read your contract. Which licensing model do you have, and what does it say about indirect use?
- Design deliberately. For each interface, choose the form of integration and the number of documents with care.
- Check with SAP or your licensing partner before you put a major interface live.
What to watch out for
This article is an explanation, not legal or licensing advice; your contract is what counts. Even so, if you take this into account in the architecture up front, you avoid surprises at the next licence audit.
Would you like advice on SAP licences for integrations? Request a free advice conversation.
Updated on