Skip to main content

OCR or AI? How to choose document intake for Priority ERP

Updated · Leon Shmueli, Founder & CEO

The short answer

OCR turns an image of a page into text, and document intake for Priority needs what comes after the reading: AI reads the document, a scanned PDF or a photo alike, finds the customer or supplier, matches every line to your items and opens the record in the right Priority form. When something is missing or contradicts, the document waits for a person, and every document gets a fingerprint so it is never entered twice.

How does a document go from the mailbox to a Priority form?

  1. The document comes in

    By email, on WhatsApp, as a PDF, a scan, a photo or an Excel file.

  2. AI reads it

    And finds the customer or supplier.

  3. Every line is matched

    To your items, by your rules.

  4. The record opens in the right form

    Or the document waits for a person, when something is missing or contradicts.

How it works

  1. A document comes inEmail, WhatsApp, PDF, scan, photo or Excel
  2. AI reads
    Customer or supplierFound from the document
  3. Already entered?A fingerprint on every document
  4. line by line
    Matched to your itemsMissing or contradicting? It waits for a person
  5. A record in the right formIn Priority
A document from the mailbox to Priority: read, the customer or supplier found, the lines matched, and a duplicate or a doubt stopped before writing.

Every intake we have already built, document by document with its form, is on the page document intake for Priority.

What is the difference between OCR and AI in document intake?

OCR, optical character recognition, turns an image of a page into text. AI reads the document, a scanned PDF or a photo alike, and the difference is what happens after the reading: matching to the customer or supplier, the items and the order, and stopping for a person when something doesn't fit.

OCR aloneAn intake built for you
What comes outText from the pageA record in the right Priority form
A customer's part numberStays as writtenMatched to your item, by the customer's part number, the price list or a valid quote
When something is missing or contradictsSomeone has to noticeThe document waits for a person, no guessing
A document sent twiceRead twiceCaught before Priority, by its fingerprint

Which document goes into which Priority form?

The documentComes fromOpens in Priority
A customer's orderEmail with a PDF, or an Excel fileSales order
A supplier invoiceEmail with a PDF, or the supplier's ExcelSupplier invoice
A return notice from a chainEmailCredit
A supplier's documentA supplier's document or emailPurchase order
A delivery notePhotoGoods receipt
A supplier price listWhatsAppSupplier price list
A request for a quoteWhatsApp voice noteQuote

Any other form Priority opens to the API can be read, created and updated, subforms included. In Priority's API documentation, a record is created together with its lines in the same request, and a file is attached to a record in its attachments form.

What happens when the AI is not sure?

It stops. A document that reaches the ERP is money, stock and customers, so every intake is built to stop when it is unsure, and to leave a trail of everything that happened:

  • Asks, never guesses: a customer or an item missing from an order? The rep gets an email, and the line is never filled in by a guess.
  • Approval before writing: from a photo, a voice note or a supplier's update, nothing is written to Priority before Approve.
  • Several companies: in a Priority with several companies, every document goes to the right company. When the evidence disagrees, it waits for a person.
  • Nothing lost: every step that fails is logged with its reason.

How is a double entry prevented?

Every incoming document gets a fingerprint, so a file sent twice is caught before it reaches Priority, and an invoice that already exists is never entered again.

And the allocation number?

The allocation number is read from the invoice, from a PDF in an email and from an Excel file alike, and, where you need it, checked before the invoice is entered. The rule, and the amount it applies from, are in the guide the allocation number on supplier invoices.

Which questions to ask before choosing document intake?

Six questions worth asking any vendor before you choose:

  • Which Priority forms does the document go into, subforms included?
  • What is each line matched on: the customer's part number, the price list, a quote?
  • What happens when something is missing or contradicts: a guess, or a stop for a person?
  • How is a document sent twice caught?
  • Is the allocation number read, and is it checked where needed?
  • Is the intake built to your rules, or does everyone get the same template?

Common questions

Do I need OCR to enter documents into Priority?
AI reads the document, a scanned PDF or a photo alike. What sets it apart from plain OCR is what happens after the reading: matching to the supplier, the items and the purchase order, and stopping for a person when something doesn't fit.
Which documents can be entered into Priority?
Sales orders from email and Excel, supplier invoices from PDF and Excel, credits from return notices, purchase orders from supplier documents, goods receipts from a photo of the delivery note, supplier price lists from WhatsApp and quotes from a voice note. Any other form Priority opens to the API can be built the same way.
How is this different from an off-the-shelf invoice-capture tool?
An off-the-shelf tool gives everyone the same intake, usually for supplier invoices only. Here the intake is built for your forms and rules, and for every document: sales orders, credits, purchase orders, goods receipts, supplier price lists and any other form Priority opens to the API.
What happens when the AI is not sure what it read?
It stops. An order with something missing sends the rep an email, an invoice that doesn't match its purchase order goes to review, and from a photo or a voice note nothing is written before Approve.
How much does it cost?
Every intake is built for your documents and forms, so it has no price list. First we build a plan together, and someone from the team comes back with all the details.

Sources

About the author

Leon Shmueli, Founder & CEO of LeonAI. Working with Priority ERP since 2006.

Leon Shmueli on LinkedIn