← All posts Article · Nov 16, 2026

Five Ways to Stop Retyping Email Data Into Your ERP, Compared

Lennard Kooy··10 min read
Five Ways to Stop Retyping Email Data Into Your ERP, Compared

Email to ERP automation means the orders, confirmations and invoices that arrive by email reach your ERP without a person retyping them. Five kinds of tool claim to do it: flow tools, the ERP's own import tools, EDI and portals, RPA and AI agents. The first 4 move data that is already structured. AI agents read the free text and PDFs that cause the retyping.

Picture an order desk at a wholesaler. A customer emails a PDF purchase order, another types 6 lines into the body of a mail, a third sends an Excel sheet with their own article codes. Someone copies each one into a spreadsheet, tidies the codes and quantities, and keys the result into the ERP. Supplier confirmations and purchase invoices go through the same hands.

At Lleverage we think the copying exists because what arrives by email is unstructured, and most integration tools only move data that is already structured. Workflow tools help once the data is clean. An AI agent that reads the email and creates the sales order in the ERP is what removes the manual step. That is what our order management agents do, and you can book a demo to see one on your own inbox.

Why does the spreadsheet sit between the inbox and the ERP?

The spreadsheet is where people turn prose into rows the ERP accepts. An ERP wants a known customer number, valid article numbers, a unit it recognises and a delivery date in one format. An email gives "the usual 40 boxes of the grey M8, same as last month, before the 12th".

So the team builds a bridge by hand. They look up the customer, translate the customer's article codes into yours, check the price list and paste the lines into a sheet that matches the import format. Then they import it or key it. Every step needs someone who knows the customers.

That bridge is where many automation projects stall. Microtechniek, a mechanical engineering firm, had already replaced manual processes one after another with workflow tools and Power BI. Order entry held out, because anything that had to read from or write to the ERP stayed manual. Each purchase order took about 10 minutes by hand.

So ask of any tool whether it does the reading itself or waits for a person to do it first. Our guide to data entry automation for ERP teams covers the wider category.

What are the 5 ways to automate email to ERP data entry?

1. Flow tools such as Power Automate and Make

Flow tools connect apps and move data between them when something happens. Microsoft describes Power Automate as a way to create automated workflows between apps and services. Make calls itself an AI automation platform and lists thousands of apps it connects. A typical flow starts when an email lands in a mailbox, saves the attachment, sends a message or writes a row to a list.

They are good at moving data that is already in fields from one system to another, and approvals, notifications and file handling are quick to build. The reading is where they stop. Power Automate can call AI Builder models, which Microsoft says can automate document processing in a cloud flow, and Make offers agents. You still design the matching of customers and articles, the checks against your ERP and the route for exceptions, and you maintain them as customers change their formats. Teams comparing these tools can read our list of Power Automate alternatives.

2. The ERP's own import tools and Excel add-ins

Most ERPs accept a file. Business Central has an Edit in Excel action on most lists: you change records in Excel and publish the changes back through Microsoft's Excel add-in. Configuration packages and data imports work the same way in other systems.

These suit bulk changes and one-off loads, and the ERP checks the data on the way in. Someone still has to fill the spreadsheet, so the reading of each email stays with your team.

Business Central also has an AI agent of its own for customer orders. Its Sales Order Agent monitors a mailbox, reads the email and supported PDF, PNG and JPG attachments, finds the customer and the items, and creates a sales quote. It always creates the quote first, even when the customer asks for an order, and it can turn the quote into an order depending on configuration. A designated user reviews every outgoing message before it reaches the customer. It works inside Business Central only, and it covers customer orders, so supplier confirmations and invoices need another route.

3. EDI and customer or supplier portals

EDI swaps the email for a structured message in an agreed standard, sent straight from one company's system to the other's. A portal asks the customer or supplier to type the order into your website.

Both work well for high volume with a large partner who has the systems to send clean messages, because nothing arrives as prose. The catch is that the partner has to change how they work. A small customer who sends 2 orders a month by PDF has little reason to set up EDI or log in to your portal, and every new EDI link is a project on both sides. Our post on EDI order processing goes deeper into when it pays off.

4. RPA

Robotic process automation records the clicks and keystrokes a person makes and plays them back. Microsoft names data entry on an ERP system as one of the jobs Power Automate desktop flows automate, and RPA can work the screens of legacy systems that have no API.

It handles fixed, rule-based steps on screens that rarely change, old ERPs included. Variable input is what breaks it. A robot types what it is given in the place it was told. When an order arrives in a new layout or a screen changes after an upgrade, the robot stops or types the wrong thing. It still needs the data in fields before it starts. Our comparison of RPA and AI covers the trade-off in detail.

5. AI agents that read documents and write to the ERP

An AI agent reads the email and its attachments the way a person does, matches the customer and the articles against your ERP, checks prices and availability, and creates the record. When it is unsure, it hands the case to a person with the source beside it.

Agents handle free text, PDFs, Excel files and scans in any layout, from customers and suppliers who keep sending the way they always have. They also learn the matching that sits in people's heads, such as one customer's abbreviations for its own sites.

Text is where many companies start with AI. According to Eurostat's 2025 survey of EU enterprises with 10 or more employees, 19.95% used AI technologies. Text mining, the analysis of written language, was the most used kind, at 11.75% of all enterprises and 35.04% of large ones.

The agent's accuracy depends on the data it matches against. Clean article descriptions and customer records make it more accurate. It also needs a line, set by your company, for when a person decides.

On Lleverage, the agent reads a connected Outlook or Gmail mailbox, shared Outlook mailboxes included, and works in the ERP through its own interfaces, filling the same fields a person fills. When it needs a decision, it creates a request for the right person and carries on once they answer. Our platform integrations list the ERPs it works in, from SAP and Business Central to Ridder iQ and NetSuite.

Which option handles which kind of email input?

The kind of input you receive decides the tool more than any feature list. Fixed format means the same file layout every time, such as a CSV export. Semi-structured means a PDF or Excel order whose layout differs per sender. Free text means an order typed into the body of an email.

OptionFixed formatSemi-structured PDF or ExcelFree text in the email bodyWhat a person still does
Flow toolsYesPartly, with an AI step you buildPartly, with an AI step you buildBuilds and maintains the matching and checks
ERP import and Excel add-insYes, once in the templateNoNoFills the spreadsheet
Business Central Sales Order AgentIn the email or a PDFPDF, PNG and JPG attachmentsYesReviews outgoing emails and quotes, inside Business Central only
EDI and portalsYesNoNoOnboards each partner
RPAYesNoNoPrepares the data and fixes broken robots
AI agent writing to the ERPYesYesYesDecides the exceptions the agent flags

Most companies need more than one. EDI stays for the partners who already use it, flow tools keep running notifications and approvals, and the agent takes the email traffic nobody could structure.

Which processes should you automate first?

Start where the volume is high, the format varies and the result in the ERP is easy to check. 3 processes usually meet that test in companies that make, move or sell physical products.

  1. Sales orders. Customer orders arrive by email in every format, and every hour of delay pushes back delivery. The agent reads the order, matches customer and articles and creates the sales order. Our post on sales order automation from email to ERP walks through the steps.
  2. Supplier order confirmations. Suppliers confirm purchase orders with changed dates, quantities or prices, and someone has to compare each one with the order. The agent updates the purchase order or flags the difference. See purchase order confirmation automation and our procurement agents.
  3. Purchase invoices. Invoices are matched against the order and the receipt within your tolerances before they are posted. Our accounts payable agents never release a payment.

Topa Bathroom Products, a Dutch wholesaler with about 700 customers, started with sales orders. Orders arrived as plain text emails, PDFs, CSVs and Excel sheets. Over 90% of incoming orders are now processed into Business Central with no manual input, and customers receive their order confirmation within 30 seconds.

"We had four and a half people · about 3.8 full-time equivalents · sitting there all day long, manually entering every single order into our Business Central ERP." Bryan van Ingen, Operations Director, Topa Bathroom Products

Those 3.8 FTE moved to after-sales and service planning. The same pattern works on an on-premise ERP. Microtechniek's agent writes between 45 and 71 purchase orders a week into Ridder iQ without anyone typing them, and gives the admin desk more than 500 hours a year back.

What should you check before buying an email to ERP automation tool?

Three checks rule out most of the options that will disappoint.

  • It works with the ERP you already run. Ask whether it writes into your system as it is, on-premise or cloud, with your custom fields. A tool that needs a new ERP module, a migration or a middle database adds a project before it saves an hour.
  • A person approves the exceptions. Ask what happens when the tool is unsure. The answer should be a named person who sees the source document and the proposed record side by side and decides. On Lleverage the agent scores how sure it is of each piece of work, and only you move the line above which it goes through on its own.
  • Nothing changes for customers or suppliers. Ask whether anyone outside your company has to send orders differently. If the answer is yes, you have bought an EDI or portal project.

Two more questions are worth asking on a call. How does it learn a new customer's format: by someone building a template, or by reading it? And who maintains the rules when your price list or article codes change?

Frequently asked questions

Can Power Automate read order emails and enter them into my ERP?

Power Automate can start a flow when an email arrives and pass data to an ERP connector. Reading a free-text order or a PDF needs an AI Builder model or another AI step. You then build the matching of customers and articles, the checks against your ERP and the route for exceptions yourself, and keep them working as formats change.

Do we need EDI to stop retyping orders?

No. EDI suits large partners who can send structured messages from their own systems. Most customers who email PDFs or typed orders will not move to EDI. An AI agent reads those emails as they are, so your EDI partners stay on EDI and everyone else keeps ordering the way they do today, with no change on their side.

What is the difference between RPA and an AI agent for ERP data entry?

RPA repeats fixed clicks and keystrokes, so it needs clean data in fields and screens that stay the same. An AI agent reads the email itself, works out what the customer wants, matches it to your articles and creates the record. When it is unsure, it hands the case to a person instead of typing a guess.

Which documents can an AI agent read from email?

An AI agent reads the email body and attachments such as PDFs, Excel and CSV files and scanned images. Topa's agent handles plain text emails, PDFs, CSVs and Excel files from about 700 customers. The agent matches what it reads against your ERP data, so clean article descriptions and customer records make it more accurate.

How long does it take to automate email to ERP data entry?

With Lleverage, the first process typically runs supervised within a few weeks. Our forward deployed engineers build it with your team on your own emails and your ERP. Supervised means a person checks the agent's work until the numbers show it can handle more on its own, and only you decide when that happens.

How do you see it working on your own inbox?

Pick one process, usually sales orders, and collect a week of real emails, including the ones only one colleague knows how to handle. Note which ERP you run and where the exceptions go today.

Bring that to a call with us. We show an agent reading your kind of emails and creating the records in your ERP, and we tell you which parts stay with a person. Book a demo and we will plan the first process with your team.

Give your back office an AI workforce.