# How to add document OCR to Sage 100 > Source: https://netray.co/integrations/sage-100-document-ocr > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer Run documents through an OCR and extraction step, match them to open purchase orders and receipts in Sage 100, and post accounts payable invoices through the Business Object Interface or a Visual Integrator import after a reviewer clears low-confidence fields. Keep the scanned image attached for audit. ## System Sage 100 ## Capability document-ocr ## Intro Accounts payable in a Sage 100 company often runs on paper and PDFs: vendor invoices, freight bills, packing slips and certs of conformance. They get keyed into Accounts Payable Invoice Data Entry or Purchase Order Receipt of Invoice, and someone else files the paper. OCR is the obvious fix, but plain OCR only turns pixels into text. The valuable part is knowing which text is the vendor, invoice number, PO number and totals, then checking it against what Sage believes was ordered and received. This page treats OCR as a front end to Sage's own matching logic. The ERP stays the source of truth, and the capture tool proposes, never decides. ## Use Cases ### Vendor invoice capture **Description:** Extract vendor, invoice number, date, terms, totals and lines, then stage an AP invoice linked to the PO. ### Three-way match checks **Description:** Compare invoice quantities and prices with the PO and receipt of goods, and flag variances before payment. ### Packing slip receiving **Description:** Read vendor packing slips against open PO lines to prefill receipts for the receiving clerk. ### Certs of conformance and mill certs **Description:** Capture heat or lot numbers and cert references, tied to the receipt and lot records for traceability. ### Freight bill allocation **Description:** Read carrier invoices and suggest allocation to the related receipts or orders. ## System Surface - Business Object Interface (COM): create AP invoices or purchase order receipts with Sage business rules. The preferred write path; object names vary by version. - Visual Integrator: import jobs for AP invoice data from a prepared file, a workable option when COM is hard to host. Test mapping carefully per release. - ODBC or SQL reads: vendors (AP_Vendor), open PO headers and lines, and receipt history for matching. Premium runs on SQL Server; Standard and Advanced use the ProvideX driver. - Paperless Office and document attachment: store the image with the transaction; capabilities depend on version and configuration, so confirm what you have. - Lot and serial tracking in Inventory Management: where cert and lot data need to land for traceable items. ## How It Works ### Collect documents in one place **Detail:** Use a scan folder and an AP mailbox. Preserve the original file, and give each a unique ID. ### OCR and layout extraction **Detail:** Use an OCR engine plus a layout-aware model for headers and tables. Run locally if invoices should not leave the building. ### Resolve vendor and PO **Detail:** Match vendor names and remit-to details to Sage vendors, then find the PO number on the page and load the open lines. ### Validate and score **Detail:** Check line sums against totals, compare unit price and quantity to PO and receipt, and assign a confidence per field. ### Review queue **Detail:** Show the image next to fields, highlighting those under threshold. Clerks correct rather than retype. ### Post and attach **Detail:** Create the AP invoice with BOI or a VI job, attach the image, and record who approved it. ## Example Flows ### Invoice with a price variance **Trigger:** A vendor invoice PDF lands in the AP inbox. **Steps:** - OCR reads the invoice and finds PO 8841. - Line 2's unit price is above the PO price. - The item goes to review with the variance highlighted. - The buyer approves or disputes, and AP posts only after resolution. **Result:** Price errors are caught before payment, not at the vendor statement. ### Mill cert at receiving **Trigger:** A steel shipment arrives with a mill cert scan. **Steps:** - The cert is read for heat number and material spec. - The receiving clerk confirms the PO line. - The heat number is captured to the lot record and the scan attached. **Result:** Traceability is available for a customer audit without hunting through paper. ## On Prem Invoices and certs reveal vendors, prices and sometimes controlled technical data, so on-prem capture is common. Run the OCR and layout model on a local GPU or CPU server, keep the review web app inside the network, and talk to Sage over ODBC and BOI on the LAN. Open-weight vision-language models work for many layouts, but benchmark on your own documents, including skewed scans and multi-page invoices, before trusting them. Keep the images in your document store and store only references and extracted data in your capture database. ## Security - Encrypt stored documents and limit the review app to AP and receiving roles. - Segregate duties: the person who approves extraction should not be the only person who can release payment. - Verify remit-to bank details against the vendor master and flag changes for manual verification. - Retain originals and extraction results according to your retention policy. ## Options ### Commercial AP automation add-on **Fit:** Companies wanting a packaged invoice workflow with vendor support. **Effort:** Weeks to implement plus per-document or subscription cost. ### In-house pipeline with open-source OCR **Fit:** Teams with a developer and a manageable invoice variety. **Effort:** Six or more weeks to reach reliable matching. ### Partner-built local capture with review **Fit:** You need documents to stay private and results integrated with Sage matching. **Effort:** A few weeks for a first set of vendors. ## Pitfalls - Trusting OCR on totals without checking line sums; a misread digit is common on poor scans. - Not handling multi-page invoices and continuation pages. - Matching vendors by name only when remit-to or tax ID is more reliable. - Posting invoices with no PO link, which defeats the three-way match. - Skipping a confidence threshold review, then discovering errors at payment time. ## Faq ### Does Sage 100 have built-in OCR? **Answer:** Not for invoice capture in the standard product as far as I know. Sage 100 can attach and store documents, but reading content needs an add-on or an external pipeline that posts AP invoices through the Business Object Interface or a Visual Integrator import. ### What accuracy should I expect? **Answer:** It depends on scan quality and document variety. Clean, text-based PDFs from regular vendors can be very reliable; skewed scans and handwritten notes much less so. Measure on a few hundred of your own documents and set review thresholds from that. ### Can this do three-way match? **Answer:** Yes, by comparing the extracted invoice to open PO lines and receipt records read from Sage. Variances beyond your tolerance are routed to a person rather than posted. ### Is the AP invoice import via VI reliable? **Answer:** It can be, if mapping is tested for your release and you keep it in a staging step. BOI gives stronger validation, but needs a Windows host. Choose based on your IT setup. ### Can documents stay on our own servers? **Answer:** Yes. OCR and extraction models can run locally, and the review UI can be internal. Only the mail or scan feed needs to reach the capture server. ## Search terms sage 100 ocr, sage 100 invoice ocr, sage 100 accounts payable automation, sage 100 invoice capture, mas 90 invoice scanning, sage 100 three way match, sage 100 ap invoice import, sage 100 document capture, sage 100 mill cert capture, sage 100 paperless office ocr --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json