An outside AI assistant such as Claude, Microsoft Copilot or ChatGPT can now work inside several ERP systems, not just next to them. Of the 20 systems we compare, 4 document an official route that lets such an assistant create or change records under the user's own permissions, 2 allow read-only access, 4 only let it in through the vendor's own AI layer, and for 9 the vendor documents no official route at all. The difference matters more than the brand of the assistant: it decides whether the tool you already pay for can post a purchase order in your ERP, who has to approve that, and where the data goes on the way.

Two announcements in November 2026 made this a selection question. Infor opened its applications to Claude with an approval step for every change, and Microsoft set a date for processing Claude inside the EU Data Boundary. This guide compares what the ERP vendors document, checked on 17 November 2026 and linked per system. Where a vendor does not say, we write "not documented" instead of guessing. The built-in assistants (Joule, Copilot in Business Central, Ask Oracle) are covered in our overview of AI in ERP systems; this page is about assistants that come from outside.

💡 Key Takeaway

Ask three questions before you connect an assistant to the ERP: what may it change, who approves each change, and where is the data processed. The vendor documentation answers them for a handful of systems; for the rest, get the answer in writing.

What changed in November 2026?

Two vendors moved from pilots to dated commitments. On 12 November 2026, Infor and Anthropic announced Infor Industry AI for Claude: manufacturing staff can ask questions about Infor data inside Claude and, with approval, carry out actions such as creating a purchase order, reallocating stock to an urgent order or shifting production after unplanned downtime (Infor press release). Infor calls Claude its preferred assistant for its products. The connector is available to select Infor Velocity Suite customers, needs the customer's own Claude licence and must be activated by an administrator.

Microsoft announced on 5 November 2026 that Claude models in Copilot will be processed inside the EU Data Boundary (ERP Today). Today they are excluded from it, and customers in the EU, EFTA and UK have them switched off by default (Microsoft Learn). Message Center post MC1546438 sets the dates: processing moves into the boundary in early December 2026, and on 9 December 2026 Claude is switched on by default for EU and EFTA tenants that have not made a selection (MC1546438).

SAP had drawn its line earlier. Its API Policy, published on 27 April 2026, permits integration with autonomous AI agents "only via an endorsed SAP architecture", meaning the Agent Gateway for agent-to-agent calls and the MCP Gateway in SAP Integration Suite (SAP API Policy overview). In May 2026 SAP and Anthropic announced plans to bring Claude into the SAP Business AI Platform and Joule, without dates (SAP News).

Outside AI assistants in ERP: the dates that matter
27 Apr 2026SAP API Policy publishedAutonomous agents only via SAP's routes12 May 2026SAP and AnthropicPlans for Claude in Joule, no dates5 Nov 2026Microsoft announcementClaude to process inside the EU boundary12 Nov 2026Infor and AnthropicClaude acts in Infor after user approvalEarly Dec 2026EU Data BoundaryClaude in Copilot processed inside the EU9 Dec 2026Default switch in EU and EFTAClaude on unless the admin chose
Outside AI assistants in ERP: the dates that matter
DateEvent
27 Apr 2026SAP API Policy published. Autonomous agents only via SAP's routes
12 May 2026SAP and Anthropic. Plans for Claude in Joule, no dates
5 Nov 2026Microsoft announcement. Claude to process inside the EU boundary
12 Nov 2026Infor and Anthropic. Claude acts in Infor after user approval
Early Dec 2026EU Data Boundary. Claude in Copilot processed inside the EU
9 Dec 2026Default switch in EU and EFTA. Claude on unless the admin chose

Sources: SAP API Policy overview, SAP News, ERP Today, Infor, Microsoft 365 Message Center MC1546438. Checked on 17 November 2026.

Which ERP systems let an outside assistant in?

11 of the 20 document some official route, but only 4 let the assistant change data directly. The usual technique is the Model Context Protocol (MCP), the open standard through which an assistant discovers and calls tools in another system. The table shows what each vendor documents for its current release.

SystemAccessRouteWhat it may doControlSource
SAP S/4HANA Cloud Public EditionOnly through the vendor's own AI layerJoule, SAP Agent Gateway (A2A) or MCP Gateway in Integration SuiteWhat the Joule agent or the governed MCP tool exposesAPI Policy: autonomous agents only via an SAP-endorsed architectureSource
SAP S/4HANA Cloud Private EditionOnly through the vendor's own AI layerJoule, SAP Agent Gateway (A2A) or MCP Gateway in Integration SuiteWhat the Joule agent or the governed MCP tool exposesAPI Policy: autonomous agents only via an SAP-endorsed architectureSource
SAP S/4HANA On-PremiseOnly through the vendor's own AI layerJoule, SAP Agent Gateway (A2A) or MCP Gateway in Integration SuiteWhat the Joule agent or the governed MCP tool exposesAPI Policy: autonomous agents only via an SAP-endorsed architectureSource
SAP Business ByDesignNo official route documentedNew sales ended April 2026Not documentedNot documented
SAP Business OneNo official route documentedMCP code samples, no supported productNot documentedNot documented
Dynamics 365 Business CentralCan write, under user permissionsBusiness Central MCP server (online only)Reads by default; create, modify, delete and actions only per API an admin enablesSigned-in user's permissionsSource
Dynamics 365 Finance & SCMCan write, under user permissionsDynamics 365 ERP MCP serverCreate, read, update, delete, plus form and action toolsSecurity role of the agent's user; admin list of allowed MCP clientsSource
Oracle Fusion Cloud ERPOnly through the vendor's own AI layerREST call (/invokeAsync) to Fusion's own agentsWhat the Fusion agent workflow allowsRoles set per workflow in AI Agent StudioSource
Oracle NetSuiteCan write, under user permissionsAI Connector Service, MCP Standard Tools SuiteAppCreate, read, update and transform records; reports; saved searchesRole permissions; administrator roles cannot connectSource
OdooNo official route documentedExternal API, no official MCP serverNot documentedNot documented
IFS CloudNeeds a paid AI entitlementMCP and agentic accessNot documentedRequires the IFS Intelligence entitlementSource
AcumaticaRead-onlyMCPRead-only, published generic inquiriesExisting role permissionsSource
Epicor KineticNo official route documentedNot documentedNot documentedNot documented
Sage IntacctRead-onlySage Intacct MCP Server (AI Gateway)Read-only; writes only through the REST APIsDefined roles and permissionsSource
Sage X3No official route documentedThird-party connectors onlyNot documentedNot documented
Infor CloudSuiteCan write, under user permissionsInfor Industry AI for Claude; MCP servers via Infor API GatewayApproved actions, e.g. create or update purchase orders, reallocate stockUser approves each change; existing Infor roles; actions recorded in InforSource
SYSPRONo official route documentedThird-party connectors only; SYSPRO Torque uses MCP outward to shop-floor systems, not as an entry point for outside assistantsNot documentedNot documentedSource
QAD Adaptive ERPNo official route documentedNot documentedNot documentedNot documented
Unit4 ERPxNo official route documentedNot documentedNot documentedNot documented
proALPHANo official route documentedNot documentedNot documentedNot documented

Source: vendor documentation and press releases linked per row, checked on 17 November 2026; Acumatica, IFS, Odoo and SAP Business One as checked for our AI overview on 3 November 2026. "Not documented" means the vendor pages we checked do not describe a supported route; third-party connectors exist for several of these systems. ERP Pilot ranks no system on this; it is a status list, not a score.

How outside AI assistants reach the 20 ERP systems in our comparison
Can write, under user permissions4 of 20Read-only2 of 20Only through the vendor's own AI layer4 of 20Needs a paid AI entitlement1 of 20No official route documented9 of 20
How outside AI assistants reach the 20 ERP systems in our comparison
Systems
Can write, under user permissions4 of 20
Read-only2 of 20
Only through the vendor's own AI layer4 of 20
Needs a paid AI entitlement1 of 20
No official route documented9 of 20

Source: vendor documentation per system (see table above), checked on 17 November 2026. "Only through the vendor's own AI layer": SAP S/4HANA (three editions) and Oracle Fusion Cloud ERP.

The 9 systems without an official route are not closed. Integration vendors sell MCP connectors for several of them, and any system with an API can be wrapped. But then the connector, its security and its support are your responsibility, not the ERP vendor's, and the vendor's terms on API use still apply.

What may the assistant actually change?

Exactly what an administrator enables, and the defaults differ. In Business Central, the built-in MCP configuration lets agents discover and read the API pages the signed-in user may use. Creating, modifying or deleting records, or running actions such as posting a document, has to be switched on per API object with separate "Allow Create", "Allow Modify", "Allow Delete" and "Allow Actions" settings (Microsoft Learn).

Dynamics 365 Finance & SCM goes further. Its ERP MCP server offers data tools for create, read, update and delete, form tools that open pages, set field values and press buttons the way a person would, and action tools that call business logic directly. Everything is filtered by the security role of the user the agent runs as, and an administrator keeps a list of allowed MCP clients. Microsoft excludes security and user administration forms (Microsoft Learn).

NetSuite's AI Connector Service lets an assistant create, read, update and transform records, run reports and saved searches, and execute read-only SuiteQL queries. It refuses administrator roles: tools run with the permissions of the role used to connect (NetSuite help). Acumatica and Sage Intacct stop at reading; Sage states that its MCP server is read-only and that writes go through the REST APIs (Sage).

A form tool is a person with a keyboard

An assistant that can open forms and press buttons can trigger any process its user role can trigger, including postings and releases. Give the agent its own user with a narrow role instead of letting it run as a finance manager.

Who approves an action?

At Infor, the user approves every change; at most other vendors, approval is whatever you design. Infor states that its Claude plugin asks for explicit user approval before each change in Infor, that single sign-on and the existing Infor roles decide what each person can see and do, and that actions through the connector are recorded in Infor (Infor). Infor's product page adds that Claude recommends a step and executes it once the user gives the go-ahead (Infor). Underneath, the Infor API Gateway runs MCP calls under the authenticated user's identity with OAuth 2.1 rather than a shared service account, and administrators decide which external clients may reach which MCP servers (Infor OS documentation).

Microsoft and NetSuite document the permission boundary, not an approval step: the agent can do what its role allows. Whether a person confirms each action is a property of the agent you build, for example in Copilot Studio, not of the MCP server. SAP points to the controls already in the process: when AI adjusts an order or triggers a workflow, it "acts within the controls organizations depend on", the approvals and policies built into SAP (SAP News).

For the audit, the record in the ERP counts more than the chat. NetSuite keeps an execution log per integration record with user, time and request, but for 21 days in production (NetSuite help). Retention of the financial record itself has to come from the ERP's own change history, so confirm that it shows which agent user changed what.

Where is the data processed?

Wherever the assistant runs, and that is usually not where the ERP runs. Once data leaves the ERP through an MCP call, the ERP vendor no longer controls it. NetSuite says so plainly: data sent to a third-party model is governed by that provider's privacy policy, and NetSuite "can't control how external components handle authorized access, authentication tokens, or data after it leaves NetSuite" (NetSuite help). Infor's announcement does not state where the Claude connector processes data (Infor).

For Microsoft customers the answer changes in December. Until then, Claude in Copilot runs outside the EU Data Boundary. Microsoft treats Anthropic as a subprocessor under the Microsoft Product Terms and Data Protection Addendum, except for models labelled "Anthropic models with Data Retention", which run under Anthropic's own terms and need a separate opt-in (Microsoft Learn). From early December 2026 the regular Claude models are processed inside the boundary for eligible EU and EFTA tenants, and Message Center post MC1546438 does not mention the UK (MC1546438).

Act before 9 December 2026

If your EU or EFTA tenant has made no selection, Claude in Copilot is switched on for all users on 9 December 2026. To keep it off or limit it, an AI Administrator or Global Administrator sets the Anthropic subprocessor to No users or to specific groups in the Microsoft 365 admin center before that date.

Why does Microsoft's change reach the ERP?

Because Copilot Studio agents can call the Dynamics 365 MCP servers, and Copilot Studio creators choose the model, which can be Claude (Microsoft Learn). A Microsoft-centric company can therefore run a Claude-powered agent against Business Central or Finance & SCM without buying anything from Anthropic directly. The default switch on 9 December 2026 decides whether that option is open in your tenant.

Many ERP buyers sit in exactly that setup. In 189 runs of the ERP Pilot quiz from March to November 2026 that answered the Microsoft question, 62 (33%) described their company as deeply embedded in the Microsoft ecosystem, with Microsoft 365, Teams, Azure AD and Power BI core to operations, and 154 (81%) used it at least moderately. The share rises with company size: above 500 employees it is more than half.

Quiz runs deeply embedded in the Microsoft ecosystem, by company size
All runs (n = 189)33%1 to 20 employees (n = 49)22%21 to 100 employees (n = 54)30%101 to 500 employees (n = 48)31%More than 500 employees (n = 38)53%
Quiz runs deeply embedded in the Microsoft ecosystem, by company size
Share deeply embedded
All runs (n = 189)33%
1 to 20 employees (n = 49)22%
21 to 100 employees (n = 54)30%
101 to 500 employees (n = 48)31%
More than 500 employees (n = 38)53%

Source: ERP Pilot quiz data, runs from March to November 2026 that answered the Microsoft ecosystem question, English and German versions combined, n = 189 (English 173); test and internal runs excluded. The two largest size bands are merged because each has fewer than 30 runs.

What does an outside assistant cost on top?

Usually little at the ERP and more at the assistant. NetSuite states that the AI Connector Service is not a paid feature and the MCP Standard Tools SuiteApp is free, while the AI client may need a paid subscription (NetSuite help). Infor's connector requires the customer's own Claude licence and is offered to select Infor Velocity Suite customers; Infor names no price (Infor).

Microsoft is the only vendor that publishes a rate for outside clients. An agent built on a client other than Copilot Studio pays 0.1 Copilot Credits per tool call to the Dynamics 365 ERP MCP server, on top of the client's own token costs; users with Finance Premium or Supply Chain Management Premium licences are exempt from that charge. In Copilot Studio the tool calls are part of the fixed agent action rate (Microsoft Learn). What a Copilot Credit or an SAP AI Unit costs per action is set out in our comparison of ERP AI agent pricing; the licence itself remains the larger number, as the ERP price overview shows.

What should you check before you connect one?

Six points, in the order an auditor would ask them:

  1. Route: is it the vendor's own MCP server or connector, a vendor-endorsed gateway, or a third-party connector? Only the first two carry the vendor's support.
  2. Identity: does the assistant act as the signed-in person or as its own agent user? An own user with a narrow role is easier to restrict and to trace.
  3. Write scope: which objects may it create, change or delete, and which business actions (posting, release, payment) may it trigger?
  4. Approval: does a person confirm each change, as at Infor, or only the agent's design?
  5. Trail: does the ERP record which user changed the record, and how long is the connector's own log kept?
  6. Data location and terms: which model provider processes the data, in which region, under whose data processing terms?

Put it in the statement of work

Ask the vendor or implementation partner to answer the six points for your configuration in writing before go-live. A demo shows the agent with every switch on; the contract should say which switches stay off.

Should assistant access decide your ERP choice?

No, but it is a fair tiebreaker. A system that fails on deployment, accounting standards or budget does not become the right one because Claude can post in it. The ERP Pilot quiz does not score AI access at all; it removes systems on knockout criteria first. Once two or three systems remain, open access for outside assistants is a real advantage: it lets you use the AI tool your company already pays for, instead of waiting for the vendor's roadmap or buying a second assistant.

Which systems usually reach that last round for your company profile is shown in our independent comparison of the leading ERP systems. Check the access route there against the table above, and expect it to change: the systems marked "not documented" today are the ones most likely to announce something in the next releases.

💡 Key Takeaway

In November 2026, 4 of 20 ERP systems document an official route for outside assistants to write data, and only Infor documents a user approval for every change. Decide your ERP on fit first; then compare access, approval and data location for the systems that are left.