All posts AI-Native Enterprise

Salesforce fixed the CRM. Workday fixed HR. Nobody owns the handoffs.

The short answer

Agentic AI in an ERP means agents that read the ERP’s state and act on it in order-to-cash, procure-to-pay and supply-chain exceptions, and it will not replace the ERP, which stays the system of record for the ledger, stock and tax. The value sits in the handoffs between the ERP, the CRM and the service desk, where no single vendor’s agent sees the whole process. Only 16% of the nearly 500 IT leaders in Bain’s August 2025 benchmarking survey expect agents to affect more than 25% of ERP functionality within three years, although 78% expect some of it to be replaced or augmented.

SAP maintains S/4HANA until the end of 2040, and SAP now sells ECC customers a paid route to keep ECC running past 2030. The record stays; the work around it moves.

Each large vendor made its own function faster: Salesforce the customer record, Workday the people record, SAP operations. The cost sits between them: the credit hold waiting for a sales director, the disputed invoice parked in the service desk, the late container that exists only in an email thread. Foundation Capital named the same three incumbents in December 2025 and bet that startups in the agent’s execution path will capture the record of those decisions. We think the company should hold that record in its own stack, because a record rented from a startup is still rented.

Key takeaways

  • The ERP stays the system of record. Only 16% of IT leaders in Bain’s survey expect agents to affect more than a quarter of ERP functionality within three years.
  • Each vendor’s agent sees its own system first. Joule, Agentforce and ServiceNow reach other systems, but each keeps the log on its own platform.
  • At least five vendors claim to be the registry for agents beyond their own system: SAP, Salesforce, ServiceNow, Workday and Microsoft.
  • The access path is contested in Europe. SAP restricts autonomous AI outside its endorsed architectures; the Bundeskartellamt’s July findings cover data extraction, not that restriction.
  • The asset to own is the decision trace at the handoff. Gartner calls “Who owns what the system learns from you?” the most important clause in the next generation of software contracts.

Agentic AI vs ERP: what is the difference?

An ERP records the state of the business; an agent does work. What vendors now sell as agentic ERP is agents reading and writing that state, and Gartner calls the cross-system version “agentic arbitrage”: AI agents completing business tasks across multiple enterprise systems.

Four generic shapes, not client cases, show where that work sits. In order-to-cash, the quote is built in the CRM, the invoice runs in the ERP, the customer disputes a line through the service desk, and cash application waits until finance reads the ticket. In procure-to-pay, the three-way match fails in the ERP and the supplier’s explanation sits in an inbox. In a supply-chain exception, the ERP shows the original date while three people decide in a Slack thread whether to expedite. When someone joins or changes role, Workday records it, the access requests wait in ServiceNow and the new approval limit waits in SAP.

Bain found that 35% of respondents say their ERP enables AI adoption and 27% say it hinders it. Joshua Greenbaum of Enterprise Applications Consulting told TechTarget what is missing: “You can design a great order-to-cash system with an LLM. But absent that context, you’re just pretending you have a standardized process.” An agent inside one system makes that system faster. Redesigning the handoff is the harder job, and it is the difference between layering AI on top and re-architecting the work.

SAP Joule, Salesforce Agentforce and ServiceNow: what can each agent see?

Each sees its own system natively and now reaches others, by calling their agents or reading their data in place. None is neutral about where a cross-system decision gets recorded.

Native reachReaches other systems byContext and logs land inClaims to govern
SAP JouleSAP Knowledge GraphCalling third-party agents over A2A; Business Data Cloud for non-SAP data; Joule Work across non-SAP systems (H2 2026); inbound A2A planned for Q4 2026SAP’s context layerSAP and non-SAP agents (AI Agent Hub)
Salesforce AgentforceCustomer 360 and Data 360MuleSoft; Data 360 Zero Copy; Federated Search into Databricks (announced, from H2 2026)Data 360Any agent (MuleSoft Agent Fabric)
ServiceNowIT, HR and service workflowsZero Copy Connector for SAP ECC and S/4HANA, read in place; its workflows exposed over MCPServiceNowAI in SAP, Oracle and Workday (AI Control Tower)
Owned context engine in your stackThe systems you connectEach system’s endorsed APIA store you ownWhat your own registry decides

SAP’s Knowledge Graph maps entities and processes “across a customer’s SAP landscape”, says the Sapphire 2026 release, and Christian Klein said SAP’s agents “have to also understand non-SAP data”, which is why SAP put Business Data Cloud “in the context layer”. SAP’s Architecture Center shows Joule already calling pro-code agents built in any A2A-compliant framework. The reverse, third-party agents calling Joule Agents, is planned for general availability in Q4, and the Architecture Center, updated in October 2026, still lists that bidirectional link through Agent Gateway as not yet supported. Joule can now call other vendors’ agents, but the context it reasons over is SAP’s, and so is the record of what was decided.

Salesforce does the same from the customer side. Agentforce 360 calls Data 360 the layer “that gives every agent context”, and MuleSoft Agent Fabric offers “a single place to register, orchestrate, govern, and observe every agent, regardless of where it was built”; Salesforce’s own example puts an “SAP Agent” under it. Data 360 already reads Databricks through Zero Copy, and Federated Search, announced with Databricks in June 2026 to let Agentforce agents search Databricks, rolls out from the second half of 2026.

ServiceNow reads the ERP in place and keeps the work. Its Zero Copy Connector for ERP has SAP ECC and S/4HANA as primary connectors, so ServiceNow workflows and agents query SAP tables without copying them, and Action Fabric exposes its approval chains and business rules to outside agents over MCP. “Others let agents read and write data. We let agents execute governed work,” said Nenshad Bardoliwalla, ServiceNow’s group vice president of product management for AI products. AI Control Tower was set to find AI in SAP and Workday through 30 new integrations, with general availability then expected in August 2026.

Workday’s Agent System of Record also governs agents “from our partners and third parties”, and Microsoft’s Agent 365, generally available since 1 May 2026, is sold as a control plane for “every agent across your organization”. A mid-cap on all five has five candidate registries for one joiner-mover-leaver agent, and the record of what it decided is split across them.

When is one vendor’s agent the right choice?

When the process starts and ends inside one suite. Order-to-cash that never leaves S/4HANA, or an IT request opened and closed in ServiceNow, gets native semantics and permissions from Joule or Now Assist; an owned layer there is overhead. It earns its cost where a process crosses vendors: a billing dispute raised in Salesforce, parked in ServiceNow and settled as a credit note in SAP.

For most mid-caps the realistic alternative to an owned layer is the system integrator already running the S/4HANA migration or the Agentforce rollout. An integrator is a partner of the platform it implements, so its agent proposal will tend to start in Joule Studio or Agentforce. Ask where the agent and its decision log will live, and whether both leave with you when the programme ends. What Salesforce’s own implementation partners report about Agentforce is worth reading first.

Can third-party AI agents reach SAP or Dynamics 365 data?

Yes: SAP data through SAP-endorsed pathways, Dynamics 365 through a metered MCP server. Where “endorsed” ends is a contract question, and a contested one.

The Register reported in April 2026 that SAP’s new API policy prohibits API use with “(semi-) autonomous or generative AI systems that plan, select, or execute sequences of API calls” outside SAP-endorsed architectures. SAP has since republished it with an FAQ, core position unchanged. “For SAP-to-non-SAP scenarios, this means that reliable support is only available where SAP has explicitly published and documented the underlying interfaces,” said Jens Hungershausen, chairman of DSAG, the German-speaking SAP user group.

On 30 July 2026 the Bundeskartellamt closed its preliminary investigation into SAP, opened after complaints including one from Celonis, without proceedings. It found “currently sufficient data extraction options” and said the API policy does not remove extraction options that were previously permissible. Its findings concern data access for third-party applications such as process mining and do not mention the restriction on autonomous AI. SAP says its policy “does not restrict these capabilities”; Info-Tech’s Scott Bickley warned that CIOs “should not mistake it for a validation of SAP’s data access model”.

Microsoft took the opposite line. Its Dynamics 365 ERP MCP server gives “any compatible agent platform” access to finance and operations tools, scoped by the agent’s security role, and bills tool calls at rates that differ between Copilot Studio and other clients. SAP controls the path, Microsoft meters it.

George Brocklehurst, a managing vice president at Gartner, warned that CIOs “may find their AI strategy blocked not by capability but by clauses they have already signed”.

SAP Business Data Cloud vs Fabric vs Databricks: where does ERP context live?

All three can now hold the state of an SAP estate, mostly without copying it, so the choice is less exclusive than the comparison pages suggest. None holds why a decision was made at a handoff.

How SAP data gets thereAdds for agentsStatus, October 2026
SAP Business Data CloudNative data products with SAP semanticsKnowledge Graph, JouleLaunched February 2025
DatabricksSAP Databricks inside Business Data Cloud; Delta Sharing outwardUnity Catalog, Unity AI GatewayLaunched February 2025, staged rollout by cloud
Microsoft FabricMirroring into OneLake; zero-copy BDC Connect plannedFabric IQ ontology (preview)BDC Connect planned for Q3 2026; no GA announcement found by mid-October

Business Data Cloud launched with data products that “maintain their original business context and semantics” and SAP Databricks inside it. Zero-copy connectors followed for Snowflake, generally available in May 2026, BigQuery, generally available in July 2026, where Google cites the German supplier ElringKlinger testing it over SAP BW/4HANA data, and Amazon Athena, announced at Sapphire 2026. Fabric can already mirror S/4HANA, ECC and BW into OneLake and add Fabric IQ; BDC Connect for Fabric was planned for Q3 2026.

Pick on cost, skills and where the rest of your data sits, then decide separately where the decision record goes: a zero-copy share carries the posted credit note, not the reason the dispute was settled that way. Palantir’s Ontology models actions as well as data, but it runs only on Palantir.

Will AI agents replace SaaS? Nadella’s claim, read by an ERP owner

No. Agents reprice the per-seat interface; they do not replace the system of record. Gartner puts up to $234 billion of application software spending at risk by 2030, about 20% of enterprise SaaS spending, and expects pressure on seat-based pricing. “You are no longer buying software primarily for people; you are increasingly buying it for agents,” Brocklehurst said.

On the BG2 podcast in December 2024 (transcript via Cloud Wars), Satya Nadella said “the notion that business applications exist” is “probably where they’ll all collapse, right, in the Agent Era”, because they are “essentially CRUD [create, read, update, delete] databases with a bunch of business logic”. Once that logic sits in “the AI tier”, he said, “people will start replacing the back-ends”. Microsoft was “seeing pretty high rates of wins on Dynamics back-ends and the agents’ use”, he added, and would “go pretty aggressively and try to collapse it all”.

Read it as an ERP owner. The first half is plausible: the logic coordinating a credit hold, a dispute and a changed delivery date already lives outside any back-end, mostly in inboxes. The second half is a sales argument from the vendor of Dynamics 365. If the AI tier is Copilot, Joule or Agentforce, the logic moves from one vendor’s back-end to another vendor’s front-end, and the company still does not own it.

So act at renewal. Where an agent now does work a per-seat licence paid for, negotiate the seats down and move that budget into a layer the company owns rather than the same vendor’s agent tier. Systems of record with compliance and audit roles are “structurally different”, AlixPartners’ Jordan Berger told ERP Today.

What is a decision trace, and who should own it?

A decision trace is the record of how one specific decision was made at a handoff: the inputs from each system, the policy and its version, the exception, the approver and what changed. Systems of record keep the outcome. The trace is what lets an agent handle the next case the way your company would.

The term comes from Foundation Capital, which locates that context in “Slack threads, deal desk conversations, escalation calls, and people’s heads”. Three facts make ownership urgent.

The thread is guarded. Slack’s API terms bar third-party applications from training a large language model on Slack data and from bulk export, and, on its real-time search APIs, from keeping persistent copies or indexes of another organisation’s data; Hunton reads the change as locking that data inside Slack. So the decision record should store the decision itself (inputs by reference, policy version, approver, outcome) and link to the thread rather than copy it.

Gartner treats ownership as a contract question. Every correction, exception and workflow an agent handles creates organisational knowledge, which Gartner tracks as a Knowledge Retention Rate, and Brocklehurst told CIO: “If it accrues to the vendor’s shared models, your operational experience is improving a product your competitors also use.”

The EU Data Act gives switching rights over the input and output data your use generates, excluding the provider’s intellectual property and trade secrets, and removes switching charges from 12 January 2027. It does not say whether an agent’s decision history is your output or the provider’s know-how. High-risk uses under the EU AI Act add record-keeping duties, covered in audit trails for AI agents.

The company should own the record: a context engine inside its own stack, model-agnostic, that agents read from (the cross-system state, the rules, the past decisions) and write to at every handoff they touch. That has a cost. It is one more system to run, and a record no agent reads back is only storage.

What should you settle before the next ERP, CRM or service-desk renewal?

Settle the access path, the authoritative registry and the ownership of the decision record before anyone designs an agent. Each is a clause, and clauses are cheaper at renewal than after go-live.

DSAG understands SAP’s API policy to apply initially to new customers and contracts, and says SAP has not clarified how it will treat renewals or extensions. The renewal is where to write the answer down.

  1. Does each contract permit third-party autonomous agents, and by which API? For SAP, get the endorsed pathways for your use case in writing.
  2. Which registry is authoritative when several vendors claim the same agent?
  3. Who owns the agent’s decision logs and the cross-system decision record, and do both leave with you?
  4. Is ERP state shared zero-copy or replicated, and who pays per call?
  5. Where an agent now does the work a seat paid for, does the seat count come down, and where does that budget go?
  6. Is the agent being built on the vendor’s platform because the process needs it there, or because the integrator’s partnership does?

The maintenance dates set the timing. Business Suite 7 has mainstream maintenance to the end of 2027 and extended maintenance to the end of 2030. SAP’s transition option covers 2031 to 2033, and since an October 2026 update possibly to the end of 2035, but only for systems moved to SAP ERP, private edition before the end of 2030: another contract, and another place for these clauses. If the systems around the ERP still run on mainframe code, see what agents change in mainframe and COBOL modernisation.

Then pick one cross-vendor handoff tied to a number you already report, such as days sales outstanding or the share of invoices that fail three-way match. Each day of DSO holds about a 365th of annual revenue in receivables, roughly EUR 1.4M at EUR 500M of revenue. That is the shape of a Nucleo engagement: forward-deployed engineers redesign that handoff, build the context engine it runs on (the cross-system state, the rules and the decision record) inside your stack, model-agnostic, and deploy agents on top.

FAQ

What is agentic AI in ERP? Agents that read the ERP’s state and act on it: chasing a failed three-way match, releasing a credit hold, re-planning around a late delivery. The ERP still records the ledger, stock and tax, and most of the agent’s work also crosses the CRM, the service desk and email.

Will AI agents replace ERP systems? No. The ERP stays the system of record, and SAP maintains S/4HANA until the end of 2040. In Bain’s survey of nearly 500 IT leaders, only 16% expected agentic AI to affect more than 25% of ERP functionality within three years.

Will AI agents replace SaaS? They reprice the per-seat interface, not the system of record. Satya Nadella said business applications would ‘collapse’ in the agent era as their logic moves to an AI tier, but if that tier is Copilot, Joule or Agentforce, the logic still belongs to a vendor.

Can AI agents still access SAP data under SAP’s new API policy? Through SAP-endorsed pathways, yes. SAP’s April 2026 policy restricts API use with autonomous AI systems outside architectures SAP endorses. In July 2026 the Bundeskartellamt found sufficient options for extracting SAP data into third-party applications, but its findings do not address the AI restriction, so your contract decides.

SAP Business Data Cloud vs Microsoft Fabric vs Databricks: where should ERP data live? Pick on cost, skills and where the rest of your data sits. Business Data Cloud embeds SAP Databricks and shares SAP data zero-copy with Snowflake and BigQuery; Fabric mirrors SAP data into OneLake, with zero-copy BDC Connect planned for Q3 2026 and no GA announcement found by mid-October. None holds the decision record.

What is a decision trace? The record of how one specific decision was made: the inputs gathered across systems, the policy and version applied, the exception, the approver and what changed. Foundation Capital named the idea in December 2025. Systems of record keep the outcome and usually lose the trace.

Who owns what an AI agent learns from your company? Whoever the contract says. Gartner’s George Brocklehurst calls ‘Who owns what the system learns from you?’ the most important clause in the next generation of software contracts. The EU Data Act covers the input and output data your use generates but excludes the provider’s intellectual property and trade secrets, so write the decision record in as yours.



Nucleo is an AI-native transformation company for European mid-caps. Our forward-deployed engineers redesign the handoffs between your systems and build the context engine your company runs on, inside your stack and model-agnostic, starting from one handoff. See how an engagement works, or write to us.

Sources: Bain, agentic AI and ERP; SAP, S/4HANA maintenance to 2040; SAP, SAP ERP private edition transition option; Foundation Capital, context graphs; CIO, Gartner on SaaS spending at risk; TechTarget, agentic AI and ERP; SAP, Sapphire 2026 release; SAP, Sapphire 2026 keynote; SAP Architecture Center, A2A agents with Joule; SAP, the future of the enterprise is autonomous; Salesforce, Agentforce 360; MuleSoft Agent Fabric; Salesforce and Databricks; ServiceNow, Zero Copy Connector for ERP release notes; Reworked, ServiceNow Action Fabric; Runtime, ServiceNow AI Control Tower; Workday, Agent System of Record; Microsoft Learn, Agent 365 overview; Microsoft, Agent 365; The Register, SAP API policy; GovInfoSecurity, SAP API policy explained; DSAG, new SAP API policy; Bundeskartellamt, preliminary investigation into SAP; SAP, statement on the Bundeskartellamt; CIO, Bundeskartellamt and SAP; Microsoft, Dynamics 365 ERP MCP server; SAP, Business Data Cloud launch; Databricks, SAP Databricks; Snowflake, SAP BDC Zerocopy Connector; Google Cloud, BDC Connect for BigQuery; SAP, BDC Connect for Fabric; Microsoft, mirroring SAP in Fabric; Microsoft, Fabric IQ; BG2, Satya Nadella episode; Cloud Wars, Nadella on BG2; ERP Today, AI agents and ERP; Slack, API terms of service; Hunton, Slack API terms; European Commission, Data Act explained.

The future belongs to those who see it before it is obvious, and build it while everyone else is still out there scouting for the best AI tools.