Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

PwC’s case for moving to SAP S/4HANA is not simply that a newer ERP is desirable. In a feature published by SAP on August 21, 2025, PwC argued that a modern ERP core could give its global network a more consistent base for data, processes, cloud extensions and AI. That foundation matters most when AI is expected to do more than answer questions: it must interpret business context and take governed action.

The argument is strategic, not a published return-on-investment calculation. PwC reported multiple territories live on S/4HANA and said it was testing conversational AI with SAP applications, but did not disclose quantified savings, deployment scope or autonomous agents in production. Those distinctions matter when other SAP customers assess whether AI really changes their migration case.

What PwC says it was trying to change

PwC describes a set of pressures familiar to large global organizations: scaling delivery, reimagining operations, managing costs and giving employees more capable digital experiences. The firm also wanted to build on existing investments in cloud, analytics and generative AI. Its thesis is that these goals are difficult to pursue through disconnected pilots if the underlying ERP data and processes remain fragmented.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

According to the SAP-hosted feature authored by PwC, PwC adopted RISE with SAP early, has multiple territories live on S/4HANA, and was adding sites. It also says the firm digitally mapped business processes, established global standard data models, developed cloud-native extensions and began testing conversational AI experiences with SAP applications.

These are PwC-reported milestones, not independently audited results. The feature does not provide country or user counts, a rollout calendar, migration cost, quantified benefits, or the precise technical architecture of its extensions. It also does not say that AI agents were executing end-to-end transactions autonomously in production.

Why agentic AI raises the stakes for ERP

A language model alone is not a dependable business agent. To act safely, an agent needs access to reliable and current business information, consistent definitions, a clear process to follow, and interfaces that expose only permitted actions. In an enterprise, it also needs permissions, approval thresholds, exception handling and an audit trail.

The dependency chain is practical:

  1. Reliable data: Transaction records and master data must be accurate enough to inform decisions.
  2. Understandable processes: The system must expose valid steps, business rules and ownership of exceptions.
  3. Governed access: APIs or other supported interfaces must enforce the user’s role and approval limits.
  4. Useful assistance: A copilot can answer questions or guide users within that context.
  5. Controlled action: An agent can perform routine steps only where authorization, monitoring and human escalation are defined.

That is why ERP modernization can matter more when an organization wants cross-process, transactional AI at scale. It does not mean every AI application requires S/4HANA: a company can use AI with legacy or non-SAP systems, and can begin pilots before migration. But fragmented data and inconsistent process rules make reliable, governed action harder.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

SAP makes a related claim in its current RISE with SAP positioning, which presents AI as more useful when grounded in operational processes, business rules and domain knowledge. That is SAP’s product positioning, not evidence that a migration by itself delivers those capabilities or outcomes.

What “shifts in persona experiences” means

Here, “persona” is best understood as a user’s role and work context—not a chatbot’s personality. In a traditional ERP experience, employees typically navigate screens and reports designed for their jobs. A conversational experience may let a finance user ask for an explanation of a variance, a procurement employee look up a purchase order, or an executive receive role-relevant insight without manually traversing several dashboards.

An agentic experience goes further: software may plan and carry out a sequence of permitted steps, while referring ambiguous or higher-risk cases to a person. Conversational access and autonomous execution are not the same thing. A natural-language request can still be informational or navigational; transactional actions require much tighter authorization and control.

SAP describes Joule for supported S/4HANA Cloud Public Edition scenarios as offering informational, navigational and transactional interactions. Its documentation also notes that entitlement and authorization requirements may apply. Availability depends on the product scenario, release, permissions and customer arrangement; it should not be assumed for every SAP installation.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

PwC’s feature refers to four digital pillars, but does not provide a sufficiently clear, text-verifiable list of their names. It also offers no detailed persona taxonomy, interface examples or user-adoption metrics. The role-based interpretation above explains the phrase in context; it is not a claim that PwC publicly documented a complete persona architecture.

The foundation is data and process discipline, not a new interface

AI can amplify the quality—or the defects—of its inputs. An incorrect supplier record can lead to a poor recommendation. Duplicate customers or materials can complicate matching and automation. Inconsistent classifications undermine reporting across business units. If process steps are undocumented or ownership is unclear, an agent may not know what action is valid or who should resolve an exception.

PwC’s feature emphasizes reliability at the source, during transactions and in classification, alongside digital process mapping and standard data models. It suggests automation and copilots may help maintain data quality, but does not provide measured evidence that they did so. S/4HANA does not automatically clean bad data; migration can carry forward old inconsistencies unless data ownership, remediation and validation are explicit workstreams.

Process standardization is similarly consequential. Common processes and definitions can make global reporting and automation easier, but may constrain local practices or require business units to change. The trade-off should be explicit: standardize where consistency creates control or scale, and preserve variation only where there is a real business, regulatory or market reason.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Clean core and extensions

A clean-core approach means keeping the ERP core close to supported standard functionality where possible, using supported interfaces, and placing differentiated extensions in governed layers rather than embedding every change in the core. The aim is to reduce upgrade friction and make integrations and future capabilities easier to manage. It is an architectural discipline, not a guarantee that a system will be simple or AI-ready.

PwC says it built cloud-native extensions, but its account does not specify whether they were in-app, side-by-side, or built on SAP Business Technology Platform (BTP). That distinction matters: buyers should ask which components own business logic and data, how extensions are tested across upgrades, and whether supported APIs and access controls are used. SAP’s RISE materials connect cloud modernization, clean core and AI, but vendor messaging is not a substitute for an architecture review.

What the PwC account establishes—and what it does not

Publicly reported by PwC Not established in the feature
Multiple territories live on S/4HANA, with more sites being added Exact number of territories, entities, users or rollout dates
Digital process mapping and global standard data models Data-quality scores, governance details or adoption consistency
Cloud-native extensions Detailed architecture, extension platform or integration count
Testing conversational AI with SAP applications Production deployment of autonomous agents or end-to-end execution
A strategic rationale linking ERP modernization to automation and AI Independently verified ROI, savings, productivity gains or full cost model

PwC also describes itself as the world’s largest S/4HANA Cloud Public Edition user. That is the firm’s claim in an SAP-hosted feature; the account does not supply independent ranking evidence. The same caution applies to any award or scale claims in promotional customer material.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

When AI strengthens the migration case

A conventional migration business case tends to count subscription and implementation costs against infrastructure savings, reduced maintenance and specific process efficiencies. PwC’s argument is that this can miss platform value: standard processes and more consistent data may reduce friction for later analytics, automation, conversational access and AI-enabled workflows.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

That broader value is plausible but should be treated as a strategic hypothesis until tied to measurable outcomes. Before approving a program on the strength of AI, executives should ask:

  • Data readiness: Are critical master data, classifications and transaction records accurate, governed and owned?
  • Process readiness: Are end-to-end processes documented, and which variations can be standardized?
  • Actionability: Can applications expose supported, governed interfaces for the business objects and actions an agent needs?
  • Authorization: Can AI operate within existing role-based access, approval thresholds and separation-of-duties controls?
  • Exception handling: Who handles ambiguity, policy exceptions and failed actions?
  • Auditability: Can the organization record recommendations, actions, approvals, overrides and outcomes?
  • Architecture: Will extensions and integrations support upgrades rather than deepen core customization?
  • Adoption: Do users have a reason to trust and use the new experience instead of workarounds?
  • Economics: Are subscription, implementation, integration, change-management and AI usage costs all included?

Measure the use case, not just the migration. Useful measures might include exception and rework rates, completion time, data-error rates, control failures and user adoption, alongside implementation cost. A faster interaction is not valuable if it increases errors or bypasses necessary review.

Cloud edition and commercial realities

PwC’s feature identifies its use of S/4HANA Cloud Public Edition, but does not explain which workloads or territories use which edition. That choice should not be generalized to every SAP customer. Public Edition favors standardized processes and limits some forms of customization; it can suit organizations prepared to adopt common practices. Private-cloud options may provide more flexibility or migration continuity for complex estates, but can retain greater customization and governance burdens. The right fit depends on requirements, not on the AI thesis alone.

Likewise, “Joule” is not a universal, standalone entitlement with one simple price. SAP says Joule Base is included with eligible SAP cloud subscriptions that integrate with Joule; eligibility and scope matter. SAP’s page for Joule with S/4HANA Cloud Public Edition lists price upon request and indicates AI Units may be required. SAP publicly displayed USD 67.17 per month for blocks of 100 capacity units per year on its AI Units page; this is a list-price signal, not a complete estimate of project or usage cost. Contract terms, country, discounts, entitlement and consumption all affect the commercial picture.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

SAP’s Joule page also advertises up to 90% faster execution of navigation and transactional tasks. That is SAP’s product claim, not a PwC result or independent benchmark. Buyers should validate relevant capabilities in their own supported release and measure performance against their own baseline.

In practice, the buying journey can span ERP subscriptions, migration and process redesign, data governance, integration and extension development, AI entitlements, training and ongoing monitoring. A quote for the ERP subscription alone will not represent the full cost of an AI-enabled operating model.

Bottom line for other SAP customers

PwC’s account makes a useful strategic point: migration becomes more consequential when the target is reliable, governed AI that can work across standardized business processes, rather than merely a refreshed ERP interface. It does not prove that every migration pays off, that S/4HANA is required for every AI use case, or that PwC has deployed autonomous agents at scale.

Use AI as a reason to examine the ERP foundation, not as a substitute for a business case. If data ownership, process consistency, permissions, exception paths and measurable outcomes are unresolved, moving to S/4HANA alone will not resolve them. If the organization needs transactional AI across its core operations, those foundations—and the migration and governance work to establish them—become harder to defer.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.