ERP AI integration means an AI agent reads the work that arrives outside your ERP, such as order emails and PDF invoices. It checks that work against the ERP's own data and writes the result back through the ERP's own interfaces. The ERP stays the system of record. An AI agent can work this way in Business Central, SAP, Dynamics 365 F&O, Infor, AFAS and Navision.
Most companies that make, move and sell physical products already have a working ERP. What they lack is a way to get the day's paperwork into it without someone retyping it. At Lleverage we think the ERP question is about access, testing and control, and almost never a reason to wait for a migration. Our AI agents for order management and invoice matching work inside the ERP you run today, and our engineers connect it with your team. To walk through your own system with us, book a demo.
Below are the ERPs we see most in Dutch and European manufacturing and distribution: for each, how an agent connects, what it reads and writes, what the vendor's own AI covers, and where a customer already runs it in production. For the general case of an older or API-less system, our guide on connecting AI agents to legacy and on-prem ERPs goes deeper.
What is ERP AI integration?
ERP AI integration connects an AI agent to your ERP so it can do a back-office job end to end. The agent reads incoming documents, looks up customers, items, prices and open orders in the ERP, and creates the sales order or matches the invoice the way a person would. The ERP checks every field it fills.
Two kinds of AI get called ERP AI. The first is built into the ERP by its vendor: an assistant that summarises a record, suggests order lines or answers a question about a list. The second sits in front of the ERP and takes a whole job off a desk. This guide is mostly about the second kind, and it says where the first kind fits better.
Software of this kind is already everywhere in our market. According to Eurostat's 2025 survey of ICT use in enterprises, 41% of small EU enterprises and 89% of large ones use ERP software. Many of those systems were installed long before anyone thought about AI agents, and some still run on a server in the building.
At Lleverage, ERP AI integration follows 4 rules:
- Nothing is migrated, and nothing is copied into a second database to go stale there.
- The agent fills the fields a person fills, through the ERP's own interfaces, so the ERP applies the same validation it applies to your team.
- The ERP account behind the connection sets what the agent can see and change, and you narrow it further per action.
- Switch the agent off and the ERP is exactly as it was the day before.
Which ERPs can an AI agent work in today?
Lleverage works in SAP (S/4HANA and ECC), Microsoft Dynamics 365 Business Central and Finance and Operations, Navision, Infor, Exact, AFAS, Epicor, Ridder iQ, IBM AS/400, Oracle and NetSuite. Business Central, Dynamics 365 and an on-premise Ridder iQ already run agents in production at customers with a published story.
The table below covers the 6 ERPs in this guide's title. "In production" means a customer runs it, with a published customer story. Every other ERP is one we work in, set up with your team during delivery.
| ERP | Who usually runs it | How the agent connects | In production at |
|---|---|---|---|
| Business Central | Mid-sized distributors and manufacturers | Business Central API, online or on your own servers | Topa, Koninklijke Dekker, Xpol, Oude Reimer |
| Dynamics 365 Finance and Operations | Larger groups with several legal entities | Managed connection, signed in with a Microsoft account | SIG Benelux |
| SAP S/4HANA and ECC | Large and upper mid-market companies | Set up with your SAP team, scoped by the SAP account it uses | Works in, no published story yet |
| Infor | Manufacturers and distributors | Through its own interfaces, or the screen where there is none | Works in, no published story yet |
| AFAS | Dutch companies running finance, HR and payroll in one suite | Through its own interfaces | Works in, no published story yet |
| Navision | Companies on the older Microsoft ERP | User name and password, or the screen where there is no API | Works in, no published story yet |
More on each in ERP integrations, with separate pages for Business Central, SAP and Exact Online.
How does ERP AI integration work in Business Central and Navision?
In Business Central the agent works through the Business Central API. It finds and creates customers, looks up items and vendors, creates sales orders, quotes and sales invoices, and creates purchase invoices with their lines. Most actions name the company first. Online, on your own servers and Navision are all supported.
Business Central is the ERP with the most published customer stories on our side. Our team sets the connection up with yours, and you sign in with a Microsoft account that has access to the environment. For app-only access, an administrator can use a certificate instead of a client secret. The connection then shows in your Lleverage project, where you choose which actions it may run and which need an approval first.
The jobs that come up most on Business Central:
- Sales orders from the order inbox: the agent reads the email, PDF or spreadsheet, ties each line to an item or the customer's own item reference, checks price, stock and credit, and creates the sales order.
- Purchase invoices matched before posting: each line is held against the purchase order and the posted receipt. Those inside your tolerances are posted; the rest stay unposted for finance with the difference named.
- Customers, vendors and items kept in step: a change in the CRM or the webshop is checked against the card in Business Central, and a vendor bank account or a credit limit goes to its owner.
On Business Central this runs in production. At Topa Bathroom Products over 90% of incoming orders are processed into Business Central without any manual input, and customers can have their order confirmation within 30 seconds. At Koninklijke Dekker the agent reads orders from PDF, Excel and email and checks products, availability and pricing before the order is created. Xpol chose the other setting: the agent pre-fills the order in Business Central and a person signs off every draft, saving about 20 minutes per large order across 150 orders a week.
Navision follows the same pattern with fewer moving parts. The connection signs in with a user name and password, reaches the server without opening it to the internet, and can create customers and sales orders, look up vendors and items, and read sales invoices. Where an older version has no API to call, the agent works the screen with the access a person has.
How does an AI agent connect to Dynamics 365 Finance and Operations?
Dynamics 365 Finance and Operations connects through a managed setup with our team: you sign in with a Microsoft account that has access to the environment. The agent can then create and update sales orders and their lines, create sales quotations and purchase orders, create customers, and look up vendors, released products and invoices, company by company.
F&O environments usually hold several legal entities, so most actions ask for the company first. That keeps an order for one entity from landing in another. The F&O account's own permissions decide what the connection can see and change. On top of that you switch off the actions a job does not need.
SIG Benelux runs this in production, together with our partner SPAIK. Every order email at its sales desk used to be retyped into Dynamics 365. Now 73% of order emails arrive as a draft ready to review, and 88% of lines match the right article first time, including lines that arrive without an article number. The project ran as a four-week Kickstart. The data question worried the team most, and the order history already in the ERP answered it.
"I knew the technology made this possible. My biggest question was the quality of our data. It was a positive surprise to see the order history was enough of a base to get results this fast." Ditte Smit, Marketing Director, SIG Benelux
An ERP that has run for a few years holds the same kind of history: the translations your desk makes by hand, such as this description, from this customer, means that article. At SIG the agent used that history, so nobody had to write the rules down first.
How does AI integration work with SAP S/4HANA and ECC?
On SAP, our team sets the connection up with your SAP team, for S/4HANA in the cloud or on your own servers and for SAP ECC. The SAP account it uses decides what the agent can see and change. The agent can create sales orders, sales quotations, purchase orders, customers and products, and look up business partners, suppliers and billing documents.
Lleverage has been an SAP partner since September 2026. A cloud system signs in with your SAP account; a system on your own servers uses a user name and password or an API key, and is reached without opening it to the internet. Where there is no interface to call, the agent works the screen with the access a person has, and nothing beyond it.
Workflows can also start on SAP events. When SAP records a new sales order, purchase order, sales quotation, billing document, customer or supplier, a workflow can pick it up, for example to route a large purchase order for approval. Lleverage checks SAP for these on a schedule, so there can be a short delay.
A common SAP question is about timing. Many SAP estates still run ECC. SAP announced in 2020 that mainstream maintenance for the core applications of SAP Business Suite 7 runs until the end of 2027, with optional extended maintenance until the end of 2030. An agent that works in ECC today, and in S/4HANA after the move, takes manual work off the desk while the migration runs. We cover the wider view in AI automation for SAP users.
We have no published SAP customer story yet. Ask us for a demo in an SAP system.
What about Infor, AFAS and the other ERPs?
Infor and AFAS connect the same way as the rest: through their own interfaces, with the access of the account behind the connection, filling the fields a person fills. Where a system has no interface for the job, our engineers build a custom integration or the agent works the screen. Neither has a published customer story with us yet.
AFAS links sales, purchasing, projects and finance in one system, with HR and payroll alongside. On AFAS the manual work is the same as on any ERP. Customer orders and supplier invoices arrive as emails and PDFs, and someone types them in. The agent reads them, checks them against AFAS and fills in the fields. Our comparison of AFAS and Business Central covers which ERP fits which kind of company.
On Infor the agent works through Infor's own interfaces where they cover the job. Our engineers scope the route during delivery with your Infor administrator. The agent is tested against your own configuration in a test environment.
Exact Online has its own page on AI agents in Exact. Ridder iQ shows what an on-premise system without an API takes. At Microtechniek, an on-premise Ridder iQ had no API module. A Ridder specialist installed it on site, and our team reverse-engineered the cloud API to work with the on-premise environment. Now between 45 and 71 purchase orders a week are written into the ERP without anyone typing them. That is more than 500 hours a year back for the admin desk.
For a system with no native connection at all, a custom integration covers it. It supports common authentication methods, including OAuth2 client credentials, API keys and NTLM for Windows systems, and the credential is entered on a secure page instead of in a chat. SPL Treatments runs a legacy desktop ERP with no API at all, so there the agent prepares the treatment route for each first-time part and a person keys the result.
Should you use your ERP vendor's own AI first?
Often yes, for what it does well. Copilot is included in the Business Central licence, and SAP offers Joule. Both help people inside the ERP. An AI agent from Lleverage fits when a whole job should leave the desk, when the work starts in an inbox or another system, or when the ERP runs on your own servers.
Microsoft says Copilot in Business Central is included in the licence at no extra cost, and that it is exclusive to Business Central online: it is not available on-premises or in a private cloud. Its Sales Order Agent and Payables Agent are billed separately, in Copilot Credits. SAP describes its Joule Assistants as using role and process context to coordinate AI agents and execute workflows across the business.
| Question | The ERP vendor's own AI | A Lleverage AI agent |
|---|---|---|
| Where it works | Mostly inside the vendor's own ERP | In the ERP and in the inbox, Teams, SharePoint, the CRM and the portal around it |
| Business Central on your own servers | Copilot is online only | Online, on your own servers and Navision |
| Cost model | Copilot is in the Business Central licence; its agents are billed in Copilot Credits | One monthly price per agent, integration included |
| Best fit | Help inside the pages people already use | A whole job, such as order entry or invoice matching |
On Business Central online, we think Copilot is worth switching on first: it is in the licence and saves time from day one. Our pages on Business Central and SAP compare the vendor's AI with ours line by line, and SAP Joule explained goes further on SAP.
How do you keep control of what the agent changes in your ERP?
You keep control in 3 layers. The ERP account behind the connection limits what the agent can reach. In Lleverage you enable only the actions a job needs and require an approval for the ones you choose. And the agent scores its confidence on each piece of work: below your line a person decides.
The confidence line decides how much goes through untouched. The agent scores how sure it is of each order, invoice or record. Below the line a person decides, above it the work goes through on its own, and only you move the line. Topa lets most orders go straight into Business Central. Xpol, on the same ERP and the same platform, has a person sign off every draft.
Some actions always stay with a person. The agent never releases a payment. A changed vendor bank account or credit limit goes to the person who owns that record. Disputes go to someone in credit control with the history gathered. When the agent needs an answer, such as a missing PO number, it asks the right colleague in Teams or Slack and carries on with the reply.
Every action the agent takes is logged against the record it touched. Lleverage holds SOC 2 Type II and ISO 27001, is EU hosted by default and is GDPR compliant. More on approvals, roles and the audit trail is on our control page.
How do you start an ERP AI integration project?
Start with one job on one ERP: usually order entry or supplier invoices. Name an owner, give the agent an account with only the rights the job needs, and test on real documents in a test environment. The first process typically runs supervised within a few weeks, built by our forward deployed engineers with your team.
A practical sequence:
- Pick the job by volume. Count the order emails, supplier invoices or confirmations your team types in each week, and how long each takes. Microtechniek's order entry took about 10 minutes an order by hand.
- Collect a week of real documents. The odd formats, the forwarded emails and the orders without article numbers decide the design.
- Agree access with IT: one account for the agent, scoped to the job, a test environment with realistic data, and a route to an on-premise server that does not open it to the internet.
- Run supervised first. The agent prepares the work and your team checks it. SIG Benelux ran its automation alongside the team, so everyone saw where it failed without any customer noticing.
- Move the line as the numbers earn it. Once the agent is right on a type of document, let that type through on its own and keep the rest with a person.
- Add the next job. The connection already exists, so invoice matching or master data on the same ERP starts from there.
Pricing is one monthly price per agent, with integration, AI usage and ongoing improvement included, and no seats. We price after we have seen the work. Bring your document counts and a week of examples to a demo with our team, and we will show how the agent would handle them in your Business Central, SAP, F&O, Infor, AFAS or Navision.
Frequently asked questions
What is ERP AI integration?
ERP AI integration connects an AI agent to your ERP so it can do a back-office job end to end. It reads orders, invoices and confirmations where they arrive, checks them against customers, items and prices in the ERP, and writes the result through the ERP's own interfaces. The ERP stays the system of record and checks every field.
Can an AI agent work with Business Central on-premises or Navision?
Yes. Microsoft's Copilot is exclusive to Business Central online, but a Lleverage agent connects to Business Central online, to installations on your own servers and to Navision, without opening them to the internet. Where an older Navision version has no API, the agent works the screen with the access a person has, and nothing beyond it.
Does ERP AI integration work with SAP ECC?
Yes. Our team connects the agent with your SAP team, for SAP ECC and for S/4HANA in the cloud or on your own servers. The SAP account it uses decides what it can see and change. The agent creates sales orders, quotations, purchase orders, customers and products, so work comes off the desk before and after a migration.
Do we need to migrate data or add middleware first?
No. Nothing is migrated and nothing is copied into a second database. The agent reads from the systems that already hold the record and writes the work back into them. Where a system has no native connection, our engineers build a custom integration or the agent works the screen. Switch it off and your systems are unchanged.
How long does it take to connect an AI agent to an ERP?
The first process typically runs supervised within a few weeks, built by our forward deployed engineers with your team. ERP connections are set up together with our team because each environment needs its own configuration. On-premise systems and those without an API are connected as part of that same delivery, alongside your IT team.
Who approves what the agent does in the ERP?
You do. The ERP account limits what the agent can reach, you choose which actions need an approval, and a confidence line decides which work goes through on its own. Below the line a person decides, and only you move it. The agent never releases a payment, and every action is logged.



