Every Priority ERP site that buys goods has the same desk. Supplier invoices arrive by email, someone opens each PDF, finds the purchase order in Priority, compares the lines, and types the invoice in. Priority ERP invoice automation is supposed to end that, and it does, but only when the automation checks the invoice before it enters it.
That is the part most tools skip. Reading the PDF is easy now. Knowing that line 7 is priced above the PO, that the goods for line 12 never arrived, and that this invoice number was already entered last month, is the work. It is the same work that makes import file processing in Priority ERP hard, and the same answer applies.
This article walks through what the flow has to do, where the old approaches fall short, and how it runs with a direct connection to Priority.
What Priority ERP invoice automation has to do
Read any supplier’s invoice
Hundreds of suppliers, hundreds of layouts, two or three languages. The system has to understand the document without a template per supplier.
Identify the supplier in Priority
The sender address and the document together point to one supplier record and its open purchase orders. Without that step there is nothing to match against.
Match every line
Item, quantity, unit price and currency against the PO, received quantity against the goods receipt. This is three-way matching, done per line, not per total.
Stop what does not fit, with a reason
A price above the PO goes to the buyer. A quantity above the receipt goes to the warehouse. A duplicate stops cold. Each one carries the numbers, so nobody has to look them up.
Create a native Priority record
What matches is entered as a regular purchase invoice in Priority, linked to the PO and the receipt. Not a file in a shared folder, not a row in a middleware queue.
Where the common approaches fall short
OCR and a Priority import
OCR gives you text. Someone still has to turn text into the right PO lines, in the right units, and check the totals. The keying moved, it did not disappear.
Templates per supplier
A template works until the supplier changes its layout, which happens every year or two. With 300 suppliers that is a template breaking every few days.
Middleware chains
Make, n8n or a custom script between the mailbox and Priority. One more system to maintain, one more place the data sits, and usually no read access to the PO, so no matching. The difference is explained in the piece on AI document processing tools that connect directly to the ERP.
Entering first, checking later
Some tools enter everything and flag problems afterwards. The wrong price is now in Priority, the payment run is tomorrow, and the AP team is correcting records instead of reviewing exceptions.
What to check before you choose
Does it read from Priority, not only write to it
Matching needs the PO and the receipt. If the tool cannot read Priority records, it cannot check anything.
Does it handle partial deliveries and several POs
One invoice covering four POs and two partial receipts is normal. Each line has to find its own PO line.
Does it work without a template
Ask for a trial on your own supplier invoices, including the ugly ones. If setup per supplier is required, the answer is no.
Where does the data live
Cloud or on your own servers, and in both cases inside your environment. No third-party queue holding your invoices.
How it works with DOConvert
DOConvert is the AI layer for the ERP. It connects directly to Priority through the DOConvert Priority connector, which is bi-directional, so it reads purchase orders and receipts and writes invoices back. Here is one supplier invoice.
The invoice arrives by email
The supplier sends it to a mailbox you define. DOConvert identifies the supplier from the sender and the document, in any layout, with no template.
The PO and the receipt are pulled from Priority
Open purchase orders for that supplier are read through the connector, together with the goods receipts against them.
Every line is checked
Twenty lines. Eighteen match the PO and the receipt. One is priced above the PO, one is a quantity the warehouse has not received.
Exceptions stop with a reason
The price difference goes to the buyer with the PO price beside the invoice price. The quantity difference goes to the warehouse with the received quantity. Nobody searches.
The invoice is entered in Priority
After the decisions, the invoice is created in Priority as a native purchase invoice, linked to the PO and the receipt, with the decisions recorded. This is how you stop keying supplier invoices that arrive by email without moving the checking to someone else. DOConvert is listed on the Priority Market.
Who it fits
AP teams on Priority ERP that receive hundreds of supplier invoices a month and still key them.
Controllers and finance managers who want exceptions caught before the payment run, not after.
IT and IS managers who want a direct connection to Priority with no middleware, and are looking at Priority ERP document automation as a whole.
Manufacturers, distributors and importers with 200 to 5,000 employees, in the UK and in Israel.
Questions and answers
Does it need a template for each supplier?
No. DOConvert understands the document rather than its layout. A new supplier works on the first invoice.
What happens when an invoice has no purchase order?
It stops with a note. For recurring service suppliers you can define a different handling in advance.
Does it work with Priority in the cloud and on premises?
Yes. The DOConvert Priority connector works with both, and DOConvert itself can run in the cloud or on your own servers.
Can it handle invoices in other languages and currencies?
Yes. Foreign supplier invoices in English, German or Chinese, in their own currency, go through the same flow.
How long does implementation take?
A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers.
Want to see it on your own documents? Book a Demo or Get Started