Cloud ERP Enterprise Agreement and Digital Access: What the Scope Actually Covers

Many RISE customers assume that Digital Access is fully included in their contract. For internal systems, that is often true. What "internal" means, where external systems, IoT platforms, and partner portals fall outside that boundary, and which governance moments arise as a result: those are questions the contract text answers, not the sales conversation.

What the Enterprise Agreement Actually Covers for Digital Access

RISE with SAP is typically structured as an Enterprise Agreement. This contract model consolidates various usage rights under a single framework, making it fundamentally different from classic on-premise individual licenses. For Digital Access, that has an important consequence: in Enterprise Agreements, Digital Access for internal integrations is often included as an unlimited entitlement. No separate document quota, no overage provisions for internal systems, no standalone DAAP amendment required for that scope.

That sounds like complete predictability, and it is, as long as your integration footprint stays within the defined scope.

The key term is "internal." It is contractually defined in the Digital Access Supplement, not in everyday language. And the definition there is narrower than many RISE customers expect.

What Is Specifically Included

The EA inclusion typically covers systems that simultaneously meet the following conditions:

The system is operated by the same legal entity that holds the RISE contract.
The system is identified by name or system category in the Enterprise Agreement, or falls under an affiliate clause that explicitly names group companies.
The system operates within the contractually defined system landscape, not outside it.

For integrations that meet these conditions, no separate Digital Access charges arise, regardless of how many document items are generated per month. That is a genuine governance moment: the integration landscape for internal processes can be shaped with relative freedom within these boundaries.

What Is Explicitly Not Included

Four categories regularly fall outside the EA inclusion in practice.

External third parties with direct interface access. When a supplier confirms purchase orders or sends delivery notifications into SAP through a procurement portal, that supplier is an external party. Their system access does not fall under the EA inclusion, even if the portal is operated on behalf of your company.

Externally operated SaaS platforms. An e-commerce platform that transfers customer orders into SAP as sales orders is not an internal system. It is a third-party service running an interface. Digital Access for the resulting sales order items arises outside the EA inclusion.

IoT platforms and connected manufacturing environments. Production-adjacent IoT systems often generate very high volumes of manufacturing order items and goods movement items. When these platforms are operated by a specialist vendor or exist as standalone systems outside the EA scope, the inclusion does not apply. Volume makes this case particularly relevant.

Customer and dealer portals for B2B transactions. When business customers or dealers trigger orders, service requests, or goods movements in SAP directly through a portal, that is not internal system access. Named-user licensing for external business partners is not workable in practice. Digital Access via a DAAP amendment is the structurally correct solution for this scenario.

Three Edge Cases That Require Clarification in Practice

The "internal vs. external" distinction sounds clear-cut. In operational reality, three constellations regularly call for careful contract analysis.

Group companies and affiliates. If the RISE contract is held by the parent company but a subsidiary creates documents through an SAP interface, that is not automatically covered by the EA inclusion. Affiliate clauses govern whether, and which, group companies are included. The scope varies considerably across contract versions and negotiation outcomes. Without explicitly reviewing the contract, you cannot reliably determine whether a subsidiary qualifies as "internal."

Outsourcing partners and managed service models. When an external service provider creates SAP postings on behalf of your company, for example a logistics outsourcing partner that books goods receipts, that is not internal system access. The service provider is not a contracting party; their systems are not part of the defined EA scope. Even if the posting is economically attributable to your own operations, that does not automatically hold under licensing law.

Technically operated systems on behalf of the customer. In some infrastructure models, systems are technically operated by a third party but entirely on behalf of, and at the expense of, the RISE contracting party. Whether that qualifies as internal within the meaning of the EA inclusion is a matter of interpretation that cannot be answered categorically. The wording in the Digital Access Supplement is decisive. When in doubt, written clarification from SAP before go-live is advisable.

What RISE Customers with Older Contract Versions Should Review

Many RISE implementations build on an SAP contract history that reaches back to the on-premise era. Migrating to RISE does not automatically harmonize all contract components to the current standard.

Three scenarios are common.

First: the RISE contract was signed, but the DAAP amendment for external integrations has not yet been negotiated. The EA inclusion covers internal systems, but the scope outside that inclusion has no contractual basis for document-based licensing. Integrations in that area exist in a licensing gray zone.

Second: the contract was derived from an older on-premise agreement, and the Digital Access Supplement does not match the current SAP standard document. In that case, it is unclear whether the nine document types are covered under the applicable definition and whether the EA inclusion for internal systems reflects the current contract definition.

Third: the integration inventory from the on-premise era was carried over into the RISE architecture, but no systematic license review took place. Interfaces that were previously covered by named-user licenses or historical indirect access rules need a fresh assessment in the RISE contract context.

A contract generation check is the first step in all three scenarios. Which GTC version applies? Which supplements are in place? Has the DAAP amendment for external integrations been executed? These questions can be answered with a structured review of the contract documentation. If the Digital Access Supplement cannot be located, that is already a relevant finding.

Current SAP contract templates are publicly available in the SAP Trust Center at sap.com/about/trust-center/agreements.html. The published version there provides a reference baseline that your own contract may deviate from.

Four Governance Moments That Arise from the EA Scope

The EA inclusion is not a one-time clarification item. It is an ongoing governance subject. Four governance moments arise directly from the scoping logic of the RISE Enterprise Agreement.

Governance moment, usage: Which integrations produce document volumes, and do those volumes fall inside or outside the EA inclusion? Which systems are approaching a threshold where switching the licensing path could become economically worthwhile? This monitoring is not a one-time project; it belongs in the ongoing governance rhythm.

Governance moment, entitlements: Which interfaces have a solid licensing basis, and which exist in an undefined zone? Every new integration that goes live ideally passes a license review before go-live. Whether an interface falls under the EA inclusion or requires a DAAP amendment is a question that is far easier to answer before production than after.

Governance moment, infrastructure: Middleware changes in the course of RISE migrations can alter the licensing status of individual integrations. An interface that was configured as an internal system via SAP PI/PO may, after migration to a BTP-based architecture, generate different document types or appear in a different system configuration. The integration inventory needs to reflect these changes promptly.

Governance moment, costs: For integrations outside the EA inclusion, Digital Access charges arise and appear as a separate line item on the SAP invoice. Reconciling that line item against measured document volume is a routine verification step. Discrepancies may point to calculation differences between SAP's measurement system and your own tracking, and should be resolved promptly.

FAQ

Is Digital Access fully included with RISE with SAP?

For internal integrations within the defined scope of the Enterprise Agreement, Digital Access is often included without limit. "Fully" is not quite accurate: external systems, customer and supplier portals, externally operated SaaS platforms, and IoT environments outside the EA scope generally fall outside the inclusion. The contract text, specifically the Digital Access Supplement, is the authoritative reference.

What is the difference between "internal" and "affiliate" in the RISE Enterprise Agreement?

In the Digital Access Supplement, "internal" typically refers to the direct contracting party and its own systems. "Affiliate" is a separate category for associated companies. Whether group companies qualify as affiliates, and whether affiliates are covered by the EA inclusion, depends on the specific contract. Affiliate clauses vary considerably across contract versions.

Do I need to reassess my integrations for Digital Access after a RISE migration?

Yes. The RISE migration does not automatically carry over the licensing basis from the on-premise contract. Integrations that relied on named-user licenses or historical indirect access rules need a fresh assessment in the RISE contract context. A middleware change in particular can alter the Digital Access profile of an integration.

What happens if the DAAP amendment has not been executed after the RISE migration?

For external integrations outside the EA inclusion, there is then no contractual basis for document-based licensing. Those integrations exist in a licensing gray zone. SAP can identify this gap in an enhanced audit. A DAAP amendment can be executed retroactively and typically includes a retrospective true-up.

Next Steps

The EA scope for Digital Access is a question for the contract, not for assumptions. A structured contract review clarifies which integrations in your RISE portfolio fall under the EA inclusion, which require a DAAP amendment, and what options are available at your next renewal.

Book a contract review: Clarity on the scope of your EA inclusion and the licensing status of your integrations, in four weeks. Fixed price, EUR 7,900.

Further reading: Digital Access in RISE Agreements: What the EA Inclusion Covers and What It Does Not and Digital Access and Indirect Access: Terminology, Licensing Options, Governance.