How to automate order entry: from email, PDF and EDI to a checked sales order in the ERP

An EDI order arrives with every value labelled; an email that says "same as last week but 12 of the 5 kg" arrives with nothing labelled. The channel changes how much work is done when the order reaches you, never which checks it needs.

Start with a count: one month of messages by channel and customer, non-orders marked. It is the baseline for every later measure.

Email intake is a watched mailbox. At Biodéal, the Outlook inbox is wired to a Microsoft Graph webhook, so processing starts within seconds of an email arriving (case study). Microsoft's agent for Business Central watches a designated mailbox, filters out messages outside its scope (offers to sell, discount requests) and ignores attachments such as terms and conditions sent with the purchase order (Sales Order Agent overview). Both start with the first check: is this an order at all? For the X12 sets themselves, see the guide to EDI 850, 855, 856 and 810.

An order desk works through a sequence of questions, most of them answered by a record already in the ERP. Automating entry means asking the same questions against the same records, and stopping at the first one without a clean answer.

Source: Business Central agent, item references, best price, credit warnings (Microsoft Learn); catalog numbers (SAP Business One); external item identifiers (Supply Chain Management).

Customer and ship-to

Microsoft's agent identifies the customer only by matching the sender's address to the E-Mail field of a contact card, because matching on a name would let someone impersonate a customer. The consequence it documents: when a colleague forwards a customer's email, the agent sees the colleague (overview). Plan a rule for forwarded orders and for customers who write from several addresses. A new delivery address is held every time.

Items and customer part numbers

Most orders that stop do so because nobody knows which of your items the customer meant. Business Central keeps the customer's number as an item reference, which can carry the customer's unit and variant (Microsoft Learn); SAP Business One as a business partner catalog number, with one default per item and partner (web client guide, 1.6.3); Supply Chain Management as an external item identifier (Microsoft Learn). Microsoft's agent tries exact identifiers first (item number, vendor item number, GTIN, references), then attributes, then a fuzzy search (overview).

If that table is empty, filling it is the first project, whatever the tool. Build it from a few months of orders as customers sent them, matched to what your team entered, and keep it in the ERP so it survives a change of tool. Every line a person resolves should add a reference. A line with two candidates is held: picking one is a guess.

Units and pack sizes

A line read perfectly can still be wrong: 66 units or 66 cases. Your masters say what a value means, never the customer's document. At Biodéal, when a form gives a quantity with no unit, the system compares the document's unit price with SAP's rate for each possible unit: a litre of milk at €1.17 can only be a carton, not a case of six at about €7. Inferred lines are entered and flagged; the case study says this turned a 12-line order that used to be rejected into one entered automatically (case study).

Prices, discounts and credit

The ERP prices the line, not the customer's PDF. Business Central calculates a best price from the customer's agreements, the item, unit, quantity and dates, using the bill-to customer (Microsoft Learn). The check compares the customer's price with the ERP's: within your tolerance, the line goes in at the ERP's price; outside it, a person decides. Discounts follow the same rule.

Credit is the check most often assumed. Business Central warns when an order exceeds the credit limit or the customer has an overdue balance, and Microsoft states that "you can post even if the credit limit exceeds" (Microsoft Learn). A warning shown to an automated process is nothing unless the process turns it into a hold.

Dates, repeats and revisions

Parse unambiguous dates, hold "03/04" or "week 14", and compare the date with what the ERP can promise; Business Central's agent can use capable-to-promise for items not in stock (overview). EDI has messages for changes: the 850 is answered by an 855 and changed by an 860, itself answered by an 865 (X12). Email has none: a resent PDF, a revised PO and "please cancel line 3" all arrive as new emails. The key is customer plus PO number, with the lines compared when it matches; Biodéal's agent follows an order across emails as it is created, merged or replaced (case study). The rules for each kind of repeat are in the guide to sales order exception handling before ERP entry.

An order goes straight in when every check passes. Anything else is held, and three decisions shape the hold. They belong to you, not to the tool.

• Where the gate sits. Orders can be written as drafts or quotes until released, or written directly with only held ones waiting. SAP Business One keeps drafts, "the preliminary version of a document", which the Service Layer turns into orders with SaveDraftToDocument and the web client with Add (Service Layer reference, web client guide, 1.4.9). Business Central's agent always creates a quote first, since a quote has no effect on planning, reservations or availability; settings can then convert it to an order without sending it to the customer (overview). Start with drafts and loosen customer by customer.
• Line or order. Clean lines may go in while one is held, never when the doubt is about the customer, the ship-to or a repeat PO. Biodéal enters the lines it can and sends the doubtful one out as an alert with a diagnosis: the order neither fails whole nor loses a line.
• What the reviewer sees. The source at the right place, the value read, the candidates from your masters, the check that held it. A reviewer who must reopen the email and search the ERP is doing the entry again.

Cancellations of picked or shipped orders, new customers and new delivery addresses always go to a person. So does every outgoing message to a customer: Microsoft's agent has a designated user approve each one (overview).

The four approaches are not rivals: each removes keying for a different kind of customer, and most order desks combine two or three. Sort customers by order count over three months: the few large ones are EDI candidates, the regulars portal candidates, the long tail is where reading tools and agents earn their place.

OCR, often the first thing tried on PDF purchase orders, reads the document; template capture adds where each field sits on a given layout. Neither decides which item "88-120-B" is, whether 66 means units or cases, or whether the PDF is yesterday's resent. See OCR vs LLM for document extraction and AI agents vs RPA. A portal, such as Odoo's shop restricted to logged-in customers (Odoo 18 documentation), is cheapest once customers use it.

What the ERP vendors document

Business Central's Sales Order Agent or a third-party tool?

On Business Central, test Microsoft's agent first, on a week of real orders. It is built in, available in every country and supports English, French, German, Spanish, Italian and Dutch among others; in other languages it "might not function as intended" (Microsoft Learn). It consumes Copilot Credits and stops processing new emails when they run out (overview). Look further if customers send spreadsheets (PDF, PNG and JPG are the documented attachment formats), if it struggles on your layouts, or if your rules (pack rounding, routing by volume, shipping calendars) go beyond its settings. SAP S/4HANA Cloud Public Edition has an equivalent limited to English and German files (SAP Learning).

However it is read, the order ends as a record created through the ERP's own interface, so its validations, numbering and pricing apply. That is why no new ERP is needed. SAP describes the Business One Service Layer as "a new generation of extension API" built on HTTP and OData (Working with SAP Business One Service Layer, 1.3). A sales order is created with POST /Orders; SAP's appendix shows the same order through the older DI API, a Documents object of type oOrders. Catalog numbers are exposed as AlternateCatNum (Service Layer reference). Biodéal's orders go through the Service Layer (case study); details for SAP are on the SAP sales order automation page.

Business Central's agent works through the pages as a user would, within the permissions an administrator gives it, and can attempt to resolve a validation error by reading it (overview). Whatever the route, write each order once: store the customer and PO number with it, so a retry after a timeout finds the order instead of creating a second one.

The same week can give four touchless rates. Write the definitions down before any pilot and apply them to the baseline and the pilot alike.

The order entry error cost calculator turns the baseline into hours and cost. Run a pilot in parallel with the team for at least two full weeks, on customers that include the awkward formats; the method is in the document automation pilot guide.