Upload a PDF or scanned invoice and InvoicesOCR pulls the vendor, invoice number, dates, tax, totals, and line items into a clean spreadsheet you save as CSV for a Sage 100 Visual Integrator import job. Stop keying supplier invoices into AP Invoice Data Entry one field at a time.
Upload your receipts and invoices
Drop files here or click to upload
Up to 50 files
Free to try, no account needed to start
Uploading...
Sage 100 records each supplier invoice in Accounts Payable Invoice Data Entry, but the system does not read your PDFs. Someone still has to open every invoice and key the vendor, dates, amounts, tax, and each line into the screen, or into a CSV that a Visual Integrator import job loads. That reading and keying step is where the hours go.
Each PDF or scanned invoice has to be read and keyed into the AP invoice fields, one value at a time, before it posts.
Typing a full line-item table into the distribution is tedious, so people post a single total and lose the detail Sage 100 could have held against each GL account or job.
A wrong date format, a currency symbol inside an amount, a missing division, or a comma inside a vendor name makes a Visual Integrator import job stop with row errors.
A few invoices are manageable; a stack of fifty supplier invoices at month end turns AP entry in Sage 100 into an evening of typing.
InvoicesOCR reads the invoice for you and returns structured data as Excel or CSV. You arrange those columns to match a Sage 100 Visual Integrator import job, the AP invoice header and the distribution lines, then run the job. The reading and typing step is gone.
PDFs, scans, and phone photos from any vendor, with no template to build per supplier.
Vendor and invoice totals for the header, plus description, quantity, unit cost, and amount for every line, ready for an import job.
Download a clean spreadsheet and save it as CSV, the delimited format a Visual Integrator import job reads.
Process a stack of invoices at once and build one import file instead of keying them individually.
Amounts come through as plain numbers without currency symbols, and dates in a consistent format, which is what an import job needs to load without row errors.
Files are encrypted and deleted automatically after processing, so supplier data does not linger.
From a supplier PDF to a Sage 100 import file in about a minute per batch.
Drag in PDF, JPG, PNG, or scanned invoices, one at a time or as a batch.
Tip: Multi-page PDFs are supported.
InvoicesOCR reads vendor, invoice number, dates, tax, totals, and line items and returns Excel or CSV.
Line up the columns with your Visual Integrator import job for AP_InvoiceHeader and the detail lines, save the file as CSV, then run the job.
Tip: Save as CSV rather than XLSX, keep a consistent date format, and set the division to 00 if you do not use divisions, so the job loads cleanly.
US businesses on Sage 100 and the people who keep AP posting accurate without hours of manual entry.
Load supplier invoices into AP Invoice Data Entry in batches instead of typing each one.
Turn the supplier invoice pile into one clean Sage 100 import file.
Give clients a repeatable way to get invoice data into a Visual Integrator import job.
Standardize how the team gets vendor invoices into Sage 100.
Sage 100, the US mid-market ERP formerly sold as MAS 90 and MAS 200, records each supplier invoice in Accounts Payable Invoice Data Entry, which posts the vendor liability and the related expense, inventory, or job accounts. To bring invoices in without keying them, most teams build an import job in Visual Integrator. From Modules, Visual Integrator, Main, Import Job Maintenance, you point a job at the AP_InvoiceHeader table for the invoice header and at the detail table for the distribution lines, then map each Sage 100 field to a column in your source file using the Col/Pos setting. You define the mapping once, then run the same job for every future batch.
That is exactly the gap InvoicesOCR fills. It reads each PDF or scanned invoice and gives you the vendor number, invoice number, invoice date, due date, tax, total, and the full line-item detail as columns in Excel or CSV. You arrange those columns to match your import job once, then reuse that layout for every batch. Because the values come out clean, as plain numbers and consistent dates, the job does not stall on the formatting that Visual Integrator rejects.
Visual Integrator reads a delimited text source, so save your spreadsheet as a CSV before you run the job rather than pointing it at an XLSX workbook. Two details trip people up: a comma inside a text field such as a vendor name is read as a delimiter, so wrap text fields in quotes, and if your company does not use AP divisions, set the division to 00 in the file because division values are still expected. InvoicesOCR returns the data already structured into columns, so preparing that CSV is a matter of arranging columns rather than retyping every figure.
An AP invoice records a supplier invoice you owe and posts to accounts payable. An AR invoice is the sales invoice you issue to a customer and posts to accounts receivable. Most teams converting received invoices are loading AP invoices, and that is the document the extracted spreadsheet is built for. Capturing line items rather than a single lump total means your Sage 100 records keep the detail you need for GL distribution, tax, and job costing.
Already on a different system as well? The same extracted spreadsheet also produces an Acumatica AP bill import or a NetSuite vendor bill import from the same data.
Sage 100 has long been a fixture in manufacturing and distribution, and the supplier bills those companies post carry their own quirks. Plants matching raw-material and component invoices to a PO and a goods receipt can follow the line-level workflow in invoice extraction for manufacturing, while wholesalers and distributors loading high volumes of SKU-priced vendor bills will recognize the setup in invoice extraction for retail. Whoever owns the AP keying today can also read how to eliminate manual invoice data entry before the next Visual Integrator run.
Last updated June 2026
You import invoices into Sage 100 with a Visual Integrator import job. From Modules, Visual Integrator, Main, Import Job Maintenance, you create a job against the AP_InvoiceHeader table and the detail table, map each field to a column in a CSV source, and run the job to load AP invoices. InvoicesOCR extracts the data from your PDF or scanned invoices into a spreadsheet you arrange to match that job.
AP Invoice Data Entry is the Accounts Payable screen in Sage 100 where each supplier invoice is recorded before it posts. It carries the vendor, invoice number, dates, terms, and the distribution lines that hit your GL accounts. Visual Integrator can load the same data from a file instead of having someone type each invoice into the screen.
Yes, but save the workbook as a CSV first, because Visual Integrator reads a delimited text source rather than an XLSX file. You prepare the columns in Excel, export to CSV, and run the import job. InvoicesOCR reads each supplier invoice and returns the vendor, dates, amounts, tax, and line items, so you map the columns and import a batch instead of typing each invoice.
Visual Integrator is the Sage 100 module for importing and exporting data. You build an import job that points at a Sage 100 table, such as AP_InvoiceHeader, maps each field to a column in your source file, and loads records in bulk. It is the standard way to bring AP invoices into Sage 100 without keying them one at a time.
No. Sage 100 does not extract data from a PDF on its own and needs structured data in a file for a Visual Integrator import job. InvoicesOCR fills that gap by reading the PDF or scan and returning the vendor, dates, totals, and line items as a clean spreadsheet you save as CSV and import yourself.
Visual Integrator reads a delimited text file, so save your data as a CSV rather than an XLSX workbook. Wrap text fields that may contain a comma, such as a vendor name, in quotes so they are not split, and set the division to 00 if your company does not use AP divisions. InvoicesOCR returns the data already in columns, so building that CSV is straightforward.
Yes. A Visual Integrator import job is built to create many records at once from a single data file. InvoicesOCR processes a batch of invoices together and builds one structured spreadsheet, so a month-end stack of supplier invoices becomes one import rather than dozens of manual AP Invoice Data Entry sessions.
An AP invoice records a supplier invoice you owe and posts to accounts payable, while an AR invoice is the sales invoice you send a customer and posts to accounts receivable. Converting received invoices means loading AP invoices, which is what the InvoicesOCR output is structured for.
InvoicesOCR produces an Excel or CSV file ready for a Sage 100 Visual Integrator import job, rather than writing into the company database for you. That keeps you in control of how each batch is reviewed and loaded, and the same output also works for Acumatica, NetSuite, and QuickBooks imports.
Turn PDF invoices into formatted Excel spreadsheets.
Build an Acumatica AP bill import from the same data.
Keep complete line-item detail in your books.
The full tool that reads any invoice layout.
