How to add document OCR to Acumatica
Short answer
Run documents through an OCR and extraction layer, either Acumatica's own recognition features if your edition has them or an external service, then create draft bills, receipts or attachments through the REST API with per-field confidence and a review queue. Always keep the original file attached to the record.
Paper still reaches Acumatica shops in the form of vendor invoices, packing slips, certificates of conformance, mill test reports, bills of lading and signed delivery notes. Someone keys the header, someone attaches the PDF, and the fields are inconsistent between operators.
Two different jobs hide under the word OCR. One is turning an invoice into a bill, with vendor, date, amounts and lines. The other is filing a certificate against the right lot or receipt, where the text matters less than the link. Both need different review rules.
Acumatica's file attachment model is the anchor: any document can have files, and the REST API can upload them. Build around that and the audit trail takes care of itself.
What teams use it for
AP invoice capture
Extract vendor, invoice number, date, tax and totals, optionally lines, and create a draft bill matched to the PO and receipt.
Packing slip to purchase receipt
Read quantities from a supplier's packing slip, propose a purchase receipt and highlight differences from the PO.
Certificates of conformance and mill certs
Identify supplier, heat or lot number and part, and attach the document to the receipt and lot record for traceability.
Signed delivery notes
Read the shipment number from the scanned note, attach it to the shipment and flag the sales order as delivered.
Expense receipts
Pull date, merchant and amount from a phone photo and prefill an expense claim line.
Acumatica integration surface
- File attachments on every document: upload through the REST API files endpoints or the attachment screen and tie to the entity key.
- Invoice recognition features for AP in some Acumatica versions and editions: check your release notes and licence for what is included, as names and scope change between versions.
- Contract-based REST API: create Bill, PurchaseReceipt and ExpenseClaim drafts, read PurchaseOrder and Vendor for matching.
- Lot and serial class setup plus the lot number fields on receipts, which the certificate flow must populate or attach to.
- Generic Inquiries to find open PO lines and unmatched receipts for three-way matching logic.
How it works
- 1
Decide the document classes
List invoices, slips, certificates and delivery notes separately. Each has a schema, a target Acumatica object and a risk level.
- 2
Standardise intake
Scan to a folder, forward to a mailbox, or upload from a mobile app. Convert to searchable PDF and detect pages and orientation.
- 3
Extract with confidence
OCR plus a layout-aware model produces fields and a confidence per field. Totals are checked by arithmetic: lines plus tax must equal the total.
- 4
Match to master data
Vendor from name and tax ID, PO from reference number, items through vendor cross reference. Anything not found stays blank.
- 5
Create the draft
Post a bill or receipt in a hold or balanced-but-unreleased state through the REST API and attach the source file.
- 6
Review thresholds
Auto-route only when every critical field is above threshold and the PO match is exact; everything else goes to a person with the image next to the fields.
Example flows
Vendor invoice with PO
Trigger: A PDF invoice lands in the AP mailbox.
- The service extracts vendor, invoice number, dates and totals.
- It locates the PO from the reference and compares receipts.
- Totals tie and the vendor matches, so a draft bill is created and flagged ready.
- An AP clerk checks the side by side view and releases it.
Result: A routine invoice takes seconds to approve and mismatches are called out explicitly.
Certificate of conformance for a receipt
Trigger: A scanned CoC is uploaded after goods arrive.
- The service reads supplier, part number, lot or heat number and standard.
- It finds the open receipt by supplier and lot.
- The document is attached to the receipt and the lot record.
- If no receipt matches, the document goes to quality with the extracted fields.
Result: A traceable link between the cert and the physical lot exists before the material is issued.
Keeping data on-prem
Supplier documents carry pricing and sometimes controlled technical data. On-premises Acumatica shops can run OCR and an open-weight vision or layout model on their own server and write only structured fields and the original file into the ERP. This avoids sending drawings or certificates to a third-party cloud. A modest GPU or even CPU-only OCR is sufficient for typical invoice volumes; heavier models are needed for messy scans.
Security checklist
- Segregate duties: the person who creates or reviews the draft should not be the sole releaser of payment.
- Hold bank account changes found in documents for manual verification.
- Retain the original with a checksum so later disputes can show what was received.
- Restrict the integration user to draft creation, not release or payment actions.
Ways to get it done
Built-in recognition if licensed
Effort: Configuration and training time.
AP invoices where Acumatica's own capture covers your layouts.
Third-party capture app
Effort: Weeks to implement plus per-document fees.
High invoice volume with a packaged workflow and support.
Custom pipeline or Netray build
Effort: Scoped per document class.
Certificates, packing slips, controlled documents and anything that must remain on your servers.
Pitfalls
- !Trusting a per-document confidence average instead of checking critical fields individually.
- !Posting tax and totals extracted from different lines without a reconciliation check.
- !Treating all documents as invoices when certificates need linkage, not accounting entries.
- !Poor scan resolution and skewed phone photos; fix capture before tuning models.
- !Missing duplicate detection, so the same invoice emailed twice becomes two bills.
Frequently asked questions
Does Acumatica have built-in OCR?
Acumatica has offered invoice recognition for accounts payable in some versions and editions, and it continues to evolve. Verify what your release and licence include. Anything beyond AP invoices, such as certificates, usually needs an external tool.
How do we attach a scanned document to an Acumatica record?
Use the file attachment function on the document screen, or upload through the REST API files endpoint against the entity. Keep a consistent naming convention and document type so files can be found later.
What confidence threshold should we use?
Set it per field and per document class, starting strict and loosening only with measured accuracy. Amounts, vendor and invoice number deserve a higher bar than a description line.
Can OCR read engineering drawings?
It can pull title block data like part number and revision, but reading dimensions reliably is a different problem. Use extraction for metadata and attach the drawing to the item or order.
Is a cloud OCR service acceptable?
For general invoices often yes, subject to your contracts and local law. For export-controlled or customer-restricted documents, process on your own infrastructure and check your obligations with your compliance lead.
Want Document OCR working on your Acumatica?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment