Summary

• SAP Connect introduced Joule Work and expanded assistants intended to operate across enterprise workflows.
• SAP cited early customer deployments, including a Novartis sourcing pilot, alongside internal productivity claims.
• SAP Pay brings embedded payment functions to Cloud ERP, with availability depending on the particular service and market.

German enterprise software group SAP is extending its Joule technology across finance, procurement, human resources and other business applications, seeking to give AI assistants controlled access to the workflows and information already maintained within enterprise systems.

The announcements at SAP Connect on 6 October cover Joule Work, specialist assistants and the SAP Business AI Platform. They also include embedded payments and procurement integrations, linking conversational software with processes that can create records, trigger actions and affect commercial transactions.

Some capabilities are already being tested or used by customers, while others are entering wider rollout. SAP presented examples from Novartis, Nestlé and PwC, but their projects differ in scope and maturity, making it inaccurate to treat every announcement as a completed deployment with independently established financial returns.

The commercial ambition is to reduce the gap between requesting information from an AI system and completing a task inside the applications a business uses. Achieving that requires reliable data context, appropriate permissions and ways to trace what the software has done when an automated action produces an unexpected result.

Joule enters existing enterprise processes

Enterprise software contains complex relationships between employees, customers, products, suppliers and financial records. A request that appears straightforward to an employee may require information from several applications, each maintaining its own controls and representation of a transaction.

Joule Work is intended to provide a common natural-language interface across that environment. SAP says its business knowledge technology supplies context that helps the software interpret records and their relationships rather than simply retrieving isolated values from a database.

The distinction becomes important when an assistant is asked about a supplier payment or a procurement problem. Relevant information may span orders, invoices, contracts and delivery records, and an apparently correct answer can still be misleading if these items are associated with the wrong business entity.

Clear permissions also matter because an employee’s access to information does not necessarily permit changing it. An assistant that can retrieve a purchase order should not automatically be able to approve a transaction or alter a supplier record.

SAP says it has deployed Joule internally and reports productivity improvements across selected functions. These figures are company measurements drawn from its operating context and should not be interpreted as a guaranteed performance improvement for customers with different processes or systems.

Customer projects reveal different stages of adoption

Novartis has described a pilot of SAP’s Joule Sourcing Assistant, which aims to support procurement activities and reduce some manual work. The description confirms a trial rather than a completed global conversion of sourcing decisions to autonomous operation.

Nestlé is examining AI assistance within its wider SAP transformation, where customer and financial records must remain consistent across a large international business. Using those systems effectively requires the underlying processes and data definitions to be maintained across different markets.

PwC has discussed billing-related assistance designed to identify issues earlier. Whether that improves collection or administrative costs will depend on the quality of records, employees’ use of the recommendations and the integration of the assistant into established approval processes.

These cases show why the level of autonomy must be evaluated for each task. Highlighting a possible discrepancy can be relatively low risk, while changing an invoice or authorising a payment introduces financial and accountability consequences.

Payments become part of the software environment

SAP has also announced SAP Pay, a service intended to embed payment execution and reconciliation into Cloud ERP. The offering is powered by Tereina, a payments business established within SAP, and aims to reduce movement between accounting processes and external payment operations.

Businesses routinely manage invoices, approvals and payment instructions through different systems. Bringing those functions together may reduce duplicated administrative work, but organisations still need to assess banking coverage, authentication, fraud controls and the commercial costs of transaction processing.

An embedded payment offering also creates dependencies on the availability of regulated services in each market. A product announcement does not establish that every customer can immediately use all payment methods or transfer funds in every jurisdiction.

Further procurement integrations announced with Moody’s and ORO Labs connect risk information and workflow orchestration with SAP applications. Those partnerships expand the range of information and processes accessible through the platform, while increasing the importance of understanding third-party data and service dependencies.

Agents require oversight across application boundaries

Joule Assistants are intended to undertake sequences of tasks rather than respond only with text. SAP is supporting mechanisms for connecting to agents developed outside its own software products, reflecting the reality that most enterprise customers operate technology from numerous vendors.

Interoperability can reduce manual handoffs, but responsibility becomes harder to trace when one agent requests a task from another. An organisation needs to know which identity authorised the action, which information was accessed and whether an approval rule applied at the correct stage.

Audit records and access controls can support investigations after a failure, although they do not ensure that source data is accurate or that every recommendation is appropriate. Customers will need testing arrangements that examine workflows from beginning to end, including cases where a connected system is unavailable.

Governance also involves maintaining an inventory of active agents. As departments introduce specialised tools, administrators must understand ownership, access privileges and the business processes that each agent can affect.

Operating value depends on implementation

SAP is attempting to connect AI capabilities with the enterprise applications already used to manage commercial operations. Customers whose information and processes are largely maintained in SAP may find it easier to introduce integrated services than organisations working across multiple disconnected platforms.

Yet adoption costs extend beyond the model or assistant itself. Businesses must prepare data, redesign approvals, train staff and monitor how automated actions perform under ordinary operating conditions. The value of a successful pilot can change considerably when the same process is introduced across regions with different regulatory and commercial requirements.

The October announcements establish an expanding product portfolio and examples of early use rather than universal deployment. Their commercial significance will become clearer through reliable operating measures, including completion rates, errors, administrative costs and the ability to maintain accountability as more transactions are automated.