ISO/IEC 42001 in the SAP world: Provider-deployer separation according to Klein's Sapphire 2026 statement

1. What ISO 42001 achieves as an AIMS standard

ISO/IEC 42001 is the international standard for AI Management Systems (AIMS), published in 2023. The standard defines a framework within which organizations manage the design, development, and deployment of AI systems. Certification against ISO 42001 is voluntary, but it is increasingly cited as proof of readiness on the provider side of the EU AI Act.

The EU AI Act defines two distinct roles with different sets of obligations. Provider (Article 16) bears the obligations set out in Articles 9 to 15: risk management, data quality, technical documentation, record-keeping, transparency, human oversight by design, accuracy, and robustness. Deployer (Article 26) bears the operational obligations during actual use: use according to instructions, oversight, logging, incident reporting, DPIA, FRIA, and informing employees. ISO 42001 primarily covers the provider side, with components that become relevant for deployers.

2. SAP’s provider positioning following Klein’s Sapphire statement

SAP SE achieved ISO/IEC 42001 certification for SAP Business AI products in the first quarter of 2026. The SAP Responsible AI page (sap.com/products/artificial-intelligence/ai-ethics.html, Q1/2026) positions SAP accordingly as a provider within the meaning of Article 16.

On May 11, 2026, the first day of SAP Sapphire 2026 in Orlando, CEO Christian Klein reinforced this positioning: We plan to announce some fundamental changes to our portfolio to infuse this deep domain know-how into SAP's AI agents, and we will govern the agentic AI layer for our customers. Source: Constellation Research April 2026, Diginomica April 2026, IgniteSAP April 2026, SAVIC Technologies May 11, 2026.

The strategic consequence: SAP is positioning itself not only as a provider with ISO 42001 certification but also as a governance layer for SAP’s own agents within SAP systems. This has two implications for SAP customer organizations.

First implication: The provider side is covered by SAP for SAP products. Anyone using Joule, Joule Studio Agent Builder, SAP Business AI, or the Business Data Cloud expanded by the Reltio acquisition (completed May 7, 2026) can rely on the SAP provider certification as a building block for their own compliance argument.

Second implication: The deployer side remains with the customer. Klein’s statement does not change the non-transferability of Article 26 obligations. The SAP governance claim covers SAP agents in SAP systems. What your own agents, third-party agents, or community MCP servers do within the SAP landscape does not fall under SAP’s governance claim.

3. Three levels on which ISO 42001 impacts an SAP landscape

Level 1: Provider verification by SAP. Anyone using SAP AI products can document SAP SE’s ISO 42001 certification as part of their own supplier assessment. This is the connection point for NIS2 supply chain security obligations (Article 21 NIS2) and DORA third-party risk management obligations (Regulation (EU) 2022/2554, applicable since January 17, 2025). SAP has been classified as a Critical ICT Third-Party Service Provider (CTPP) since November 2025 and is subject to direct lead overseer supervision.

Level 2: Your own ISO 42001 implementation as a deployer. Operators who develop their own AI models, build their own Joule Studio agents, or integrate third-party AI components into SAP processes can maintain their own ISO 42001 implementation. The standard requires a documented lifecycle, defined roles, and continuous improvement. It is a management system standard in the style of ISO 9001 or ISO 27001, not a detailed technical standard.

Level 3: Operational interfaces with EU AI Act Articles 12 and 14. ISO 42001 requires risk management, record-keeping obligations, and human oversight. These elements partially overlap with Articles 9, 12, and 14 of the EU AI Act. An ISO 42001 implementation can therefore serve as an organizational framework for Article 26 compliance, but it does not replace the specific obligations.

4. Five risks between provider certificate and operator obligation

Risk 1: Confusion between provider and operator roles. Klein's statement that we will govern the agentic AI layer for our customers is sometimes interpreted by stakeholders in practice as SAP assuming full compliance responsibility for customers. That is not the content of the statement. Under the AI Act, providers and operators are separate roles with separate obligations. Confusion leads to compliance gaps on the operator side.

Risk 2: Limited scope of the SAP governance commitment. The statement applies to SAP's AI agents, i.e., Joule and the agents built in Joule Studio. It does not apply to Microsoft Copilot, which is used productively in many DACH companies via the SAP-Microsoft partnership. It does not apply to Salesforce Agentforce or Workday agents. It does not apply to community MCP servers (more than 30 inventoried projects in the marianfoo registry as of April 2026) and not to ARC-1 as an enterprise-oriented community server (Marian Zeis, April 27, 2026).

Risk 3: ISO 42001 is a management system standard, not a compliance stamp. The standard requires processes, documentation, and improvement. It does not certify that a specific AI system is compliant with Articles 9 to 15 of the EU AI Act. A conformity assessment according to Article 43 is a separate process that typically requires a lead time of three to six months.

Risk 4: The LeanIX AI Agent Hub view is SAP-centric. In Q1/2026, SAP introduced the LeanIX AI Agent Hub as a central inventory dashboard for AI agents. Inventory, yes; cross-vendor governance, no. Anyone who views the hub as a complete answer to the inventory obligation leaves Microsoft, Salesforce, and community agents out of the picture. What is considered visible becomes reality for the observer; what remains invisible still has an effect within the system.

Risk 5: Solutive AG does not have ISO 42001 certification. This is an important negative disclosure. Solutive AG's statements regarding capability mappings to Articles 12, 14, and 15 are provider declarations, not certified compliance outcomes. The only externally attested statement regarding Solutive AG is the 70 percent reduction in SOX ITGC audit effort at Bruker.

5. Six steps for a clean role matrix

First: Create a role matrix. Clarify the roles for every AI system in the SAP landscape: provider, operator, importer, distributor. Who is the provider in the specific use case (SAP for SAP Business AI, Microsoft for Copilot, the internal CISO for internally developed models), who is the operator, and who has operational oversight?

Second: Collect and verify provider certificates. Maintain ISO 42001 certificates from SAP and other providers as part of the supplier file. Monitor expiration dates. Explicitly check the scope of the certification. SAP has certification for SAP Business AI products. Anyone using a different product should verify the scope.

Third: Consider your own ISO 42001 implementation for complex operator landscapes. Organizations that deploy AI in multiple Annex III areas and must simultaneously comply with DORA, NIS2, and the EU AI Act benefit from implementing an ISO 42001 management system as an integrating framework. Implementation typically takes nine to twelve months to reach certification readiness.

Fourth: Manage cross-vendor agents separately. If you don't govern what SAP doesn't govern, someone else will—or no one will. Microsoft Copilot with productive access to SAP data, Salesforce agents with data flows into SAP customer records, community MCP servers with ABAP write access: define a specific governance element for each of these constellations, with a designated responsible party within your own organization.

Fifth: Classify Klein's statement as a vendor commitment, not a release from operator liability. Clear language is essential when communicating with auditors, financial examiners, and the BSI market surveillance authority. SAP assumes vendor obligations for SAP-native agents. The operator remains responsible for their deployment within their own context.

Sixth: Strategically categorize the Reltio acquisition. With the Reltio acquisition completed on May 7, 2026 (now Reltio, an SAP company), SAP covers the data side of AI provisioning. This provides the foundation for Annex IV data quality requirements, but it does not address the question of who is responsible for changes to productive systems triggered by AI agents.

6. Tool landscape: AIMS, Annex IV, inventory, role separation

Tools in the ISO 42001 and provider-deployer landscape are divided into three functional areas.

¹ Solutive AG is the initiator of the Change Orchestration Institute. Solutive AG itself does not hold ISO/IEC 42001 certification. Capability statements regarding the ESM Suite are provided by the vendor.

The table shows a clear division of tasks: AI model governance tools cover the vendor side (Annex IV, model lifecycle). Change governance tools cover the operator side during the change process (logging, escalation). Inventory tools like LeanIX Agent Hub offer visibility but not comprehensive cross-vendor governance.

7. Key takeaways on provider-deployer separation

SAP achieved ISO/IEC 42001 certification for SAP Business AI products in Q1 2026, positioning itself as a provider under Article 16 of the EU AI Act. Klein's Sapphire statement on May 11, 2026, reinforces this positioning with a governance commitment for SAP-native agents. Neither statement changes the operator obligations under Article 26: these remain with the SAP customer, are non-transferable by contract, and take effect on August 2, 2026, unaffected by the Digital Omnibus of May 7, 2026.

The operational consequence is a clear role matrix within your own organization, a cross-vendor agent inventory that goes beyond the SAP-centric view, and, if necessary, your own ISO 42001 implementation as an integrating management framework. Solutive AG does not hold ISO 42001 certification and is not active at the vendor model governance level; Solutive's capability statements are at the change governance level.