How to add document OCR to Epicor Prophet 21
Short answer
Run incoming vendor invoices, packing slips, bills of lading and credit memos through OCR and a layout-aware extraction model, match the results to open P21 purchase orders and receipts, and post draft AP invoices or receiving records through the P21 APIs. Route anything below a confidence threshold to a reviewer with the source image beside the fields.
For a distributor, the paper trail is heavy: hundreds of vendor invoices a week, packing slips that arrive with freight, and credit memos that need to land against the right purchase order. Accounts payable keys most of it by hand, and receiving staff reconcile slips to POs by eye.
OCR alone is not the answer. Reading text off a page is the easy part. The value comes from matching the extracted vendor, PO number, items and quantities to what P21 already knows, and from catching the differences: price variances, short shipments, freight lines and tax.
This page covers the document types worth capturing, how they connect to P21 AP and receiving data, and how to set confidence thresholds so clerks review exceptions instead of every page.
What teams use it for
Vendor invoice capture
Extract vendor, invoice number, dates, lines, freight and tax, and create a draft AP voucher linked to the matching PO.
Three-way match
Compare invoice lines to PO lines and received quantities, flagging price and quantity variances before posting.
Packing slip to receipt
Read the slip at the dock and pre-fill a receipt against the PO, so the receiver confirms counts rather than typing item numbers.
Credit memo and return matching
Identify vendor credits and link them to the original invoice or return authorisation so credits are not lost.
Certificates and test reports
Capture material certs, mill test reports and manufacturer certificates, indexed by item and lot or heat, for products that require them.
Customer proof of delivery
Link signed delivery receipts to the invoice so disputes can be resolved from a stored image rather than a search.
Epicor Prophet 21 integration surface
- P21 middleware transaction services for creating AP invoice or voucher records and receiving transactions; the exact services and required fields depend on your version and configuration.
- Purchase order header and line data, including received quantity and open quantity, read through the APIs or a read-only SQL Server view (po_hdr and po_line style tables, verified locally).
- Vendor master, remit-to and vendor item cross-reference data to match vendors and map vendor part numbers to your item IDs.
- Document storage or attachment handling in P21 or a linked repository, so the original image sits with the voucher. Capability varies by version and add-ons.
- AP approval and matching rules already in P21, which should remain the system of record for tolerances and holds.
How it works
- 1
Collect documents
Ingest from a scan folder, an AP mailbox and a dock scanner or mobile capture. Normalise everything to PDF or image pages with a document ID.
- 2
OCR and layout analysis
Run OCR with table detection so line items keep their columns. Keep per-field confidence and bounding boxes for the review screen.
- 3
Classify and extract
Identify invoice, packing slip, credit memo or cert, then extract the fields for that type with a model constrained to a fixed schema.
- 4
Match to P21
Resolve the vendor, find the PO by number, then match lines by vendor part number and quantity, recording the match score for each line.
- 5
Validate
Check totals add up, dates are plausible, the invoice is not a duplicate, and price and quantity are within your tolerance for the vendor.
- 6
Review queue
Show low confidence or variance items with the image and extracted values side by side. Corrections feed vendor-specific layout hints.
- 7
Post as draft
Create the voucher or receipt through the P21 API as a draft or pending record, with the image attached, and let P21 run its own approval rules.
Example flows
Invoice with a price variance
Trigger: A vendor invoice PDF arrives in the AP mailbox.
- OCR extracts lines and totals with confidence scores.
- The PO is found and lines are matched.
- One line price is above tolerance, so the invoice is flagged.
- The clerk sees the image, accepts the variance or contacts purchasing.
Result: Only the exception takes time and the rest posts as drafts.
Dock receiving from a packing slip
Trigger: A receiver photographs the slip on arrival.
- The slip is read and the PO number identified.
- Expected lines are pre-filled from the open PO.
- The receiver confirms counts and notes damage.
- A receipt is created for the confirmed quantities.
Result: Receiving is faster and more accurate and AP can match to a real receipt later.
Mill cert filing
Trigger: A material cert PDF arrives with a shipment of steel stock.
- The document is classified as a cert.
- Heat number, item and PO are extracted.
- The cert is linked to the receipt or lot record.
Result: A customer asking for a cert months later gets it in seconds.
Keeping data on-prem
Invoices carry vendor pricing and bank details, so many distributors prefer to keep capture inside their network. Run OCR and layout models on a local GPU or even CPU for modest volume, store images on an internal file share or document repository, and call the P21 middleware internally to post drafts. Open-source OCR and open-weight vision-language models are viable, though accuracy on poor scans and handwriting should be tested on your own samples before you commit. A cloud OCR service can be acceptable for some, but then you need a data processing agreement and a clear retention policy.
Security checklist
- Restrict the posting account to creating drafts and attaching documents, not releasing payments.
- Detect duplicate invoices by vendor, number, amount and date before posting.
- Flag changed bank details or remit-to addresses for out-of-band verification.
- Retain originals and extraction results with immutable audit logs for the retention period you need.
- Segregate duties so the person who reviews capture is not the sole approver of payment.
Ways to get it done
Off-the-shelf AP automation product
Effort: Weeks to configure, with per-document subscription pricing.
Good when you mostly need invoices and there is a vendor with a tested P21 connector.
Build in-house
Effort: Two to four months for a reliable AP and receiving flow.
Possible with an OCR engine and the P21 APIs if you have capable developers and a modest vendor set.
Partner such as Netray
Effort: A pilot on one document type, then expand.
When you need on-premises processing, mixed document types such as certs and delivery receipts, and learning from reviewer corrections.
Pitfalls
- !Trusting OCR totals without checking arithmetic and line sums lets errors reach AP.
- !Skipping vendor-specific layouts causes repeated errors on your top ten vendors; tune those first.
- !Posting directly to released vouchers bypasses controls; use drafts.
- !Ignoring freight, tax and miscellaneous charges, which often cause the mismatch.
- !Low quality scans: fix capture quality at the source before adding more modeling.
Frequently asked questions
Does Prophet 21 include OCR for invoices?
Epicor and its partners offer document and AP automation options, but what is included varies by version and subscription. Check with Epicor or your reseller. If you need something broader, an external capture layer can still post through the P21 APIs.
How much of invoice processing can be touchless?
For repeat vendors with clean PDFs and a matching PO, a large share can pass without edits, but results vary widely. Measure on your own invoices and set thresholds per vendor rather than relying on a generic percentage.
Can it read handwritten delivery receipts?
Printed fields are fine, handwriting is harder. For signatures, store the image and link it; do not rely on extracting handwritten text. Use review for handwritten quantities and notes and test accuracy on your real documents.
How are non-PO invoices handled?
Route them to a coding workflow where the model suggests GL accounts based on vendor history, and a clerk confirms. Keep approval rules in P21 so spend controls stay in the system of record.
Do we need a GPU?
Not always. Modest volumes can run OCR on CPUs. Vision-language models for complex layouts benefit from a GPU. Size to your daily page count and the response time reviewers expect, and test with your own samples first.
Want Document OCR working on your Epicor Prophet 21?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment