An AI layer for the ERP is software that sits between the email inbox and the ERP. It understands the supply chain documents that arrive by email, supplier invoices, customer orders, delivery notes, import files, customs documents, identifies who sent each one, checks it against the matching record in the ERP, and only then enters the data through a direct, bi-directional connection.

The ERP itself is very good at holding records. It is not built to read a PDF from a supplier it has never seen, or to notice that the quantity on an invoice is higher than what the warehouse received. In most companies people fill that gap, by reading, comparing and typing. The AI layer takes that gap. That is the idea behind DOConvert 2.4.0, the AI layer for your ERP.

This article explains what the layer does, document by document, what it is not, and how one invoice moves through it.

What the AI layer does

Understands the document

An invoice from a new supplier, a customer order as an Excel sheet, a packing list from a forwarder. The layer recognises what it is and what each field means, with no template per sender.

Identifies the sender

The supplier, the customer or the forwarder behind the email is tied to its record in the ERP. That record brings the open orders, the price list and the terms.

Checks against the ERP record

The purchase order for an invoice. The price list for a customer order. The import file for a bill of lading. Line by line, before anything is written.

Stops what does not match

A price above the PO, a quantity above the receipt, a missing document in an import file. Each stops with a plain reason, and a person decides.

Enters what matches

The invoice, the sales order or the receipt is created in the ERP as a native record, linked to the PO or the customer. No retyping, no CSV.

What it looks like per document type

Supplier invoices

Read, tied to the supplier, matched to the PO and the goods receipt, entered. The AP team stops keying supplier invoices from email and handles the exceptions instead.

Customer orders

A PO from a customer becomes a sales order, after the items are mapped to your catalog and the prices are checked against the customer’s list. The same flow handles customer orders from PDF and email in any format.

Delivery notes and packing lists

Checked against the open PO so the warehouse knows what should arrive. The goods receipt is created from the document, not typed from it.

Import files and customs documents

Commercial invoice, packing list, bill of lading and customs entry, from different senders on different days, held together as one case. Import file processing in Priority ERP is the clearest example of a flow the ERP alone cannot run.

What it is not

Not a replacement for the ERP

The ERP stays the system of record. The layer feeds it checked data and reads from it. Nothing moves out.

Not OCR with a nicer screen

Reading characters is the first step. The layer is defined by the check against the ERP and the entry, not by the read.

Not middleware

There is no Make, n8n or Zapier scenario in the chain. The layer connects directly, to Priority through the DOConvert Priority connector, to Oracle Fusion Cloud ERP and to Infor M3.

Not a chatbot

It does not answer questions about your data. It does a specific job, documents in, checked records in the ERP.

How it works with DOConvert

DOConvert is the AI layer for the ERP. Here is one supplier invoice on Oracle Fusion Cloud ERP, the same flow runs on Priority and Infor M3.

The invoice arrives by email

A PDF with 30 lines. Nobody forwards it or uploads it.

DOConvert identifies the supplier

From the sender and the document. The supplier record and its open purchase orders are read from Oracle Fusion.

The PO and the receipt are read

Lines, quantities, prices and received quantities. The comparison runs line by line, the way Oracle Fusion invoice matching done automatically describes it.

Exceptions stop with a reason

Say 28 lines match. Two show quantities above what was received. They stop with a short note, and the invoice waits for the buyer.

The invoice is entered

Once decided, the invoice is created in Oracle Fusion, linked to the PO and the receipt. The AP team sees a checked invoice, not a PDF. This is the shift from paper trails to document evolution that Avi Rafalson, DOConvert’s CEO, writes about in The future of work.

Who it fits

• CFOs and VPs Finance who want every supplier invoice checked against the PO before it is entered
• VPs of Operations with orders, delivery notes and import files arriving by email all day
• IT and IS managers on Priority ERP, Oracle Fusion Cloud ERP or Infor M3 who want a direct connection with no middleware
• Companies of 200 to 5,000 employees, and larger groups that start with one subsidiary

Questions and answers

Does the AI layer change anything inside the ERP?

No. It reads records and creates records through the standard connection. Your ERP setup, workflows and approvals stay as they are.

Where does the data live?

In your environment. DOConvert runs in the cloud or on your own servers, and talks directly to the ERP. No third platform holds copies.

Does it work for a group with several companies?

Yes. Many groups start with one subsidiary and extend from there.

How long does it take to set up?

A typical DOConvert implementation takes about 10 business days.

Want to see it on your own documents? Book a Demo or Get Started