Upload a PDF or scanned invoice and InvoicesOCR pulls the vendor, reference number, dates, tax, totals, and line items into a clean spreadsheet you can map to an Acumatica AP bill import scenario. Stop retyping supplier invoices into Acumatica by hand.
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...
Acumatica records each supplier invoice as an AP bill, but unless you license the AP Document Recognition service, 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 Bills and Adjustments screen or into an import file. That manual step is where the hours go.
Each PDF or scanned invoice has to be read and keyed into the AP bill fields, one value at a time, before it posts.
Typing a full line-item table into the document detail is tedious, so people post a single total and lose the detail Acumatica could have held against each line or GL account.
A wrong date format, a missing vendor ID, an unmapped column, or a currency symbol inside an amount makes an Acumatica import scenario fail with row errors.
A few invoices are manageable; a stack of fifty supplier invoices at month end turns AP entry in Acumatica 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 an Acumatica AP bill import scenario, the document header and the detail lines, then run the import. The reading and typing step is gone, and there is no recognition add-on to license.
PDFs, scans, and phone photos from any vendor, with no template to build per supplier.
Vendor and document totals for the header, plus description, quantity, unit cost, and amount for every line, ready for an AP bill import scenario.
Download a clean spreadsheet you can map to your Acumatica import scenario and save as CSV or Excel, the formats import scenarios read.
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 scenario 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 an Acumatica 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, reference number, dates, tax, totals, and line items and returns Excel or CSV.
Line up the columns with your Acumatica AP bill import scenario, the header fields and the detail lines, save the file, then run the import by scenario.
Tip: Keep a consistent date format and leave out currency symbols so the import scenario succeeds.
US businesses on Acumatica and the people who keep AP posting accurate without hours of manual entry.
Load supplier invoices as AP bills in batches instead of typing each one.
Turn the supplier invoice pile into one clean Acumatica import file.
Give clients a repeatable way to get invoice data into an AP bill import scenario.
Standardize how the team gets vendor invoices into Acumatica.
Last updated June 2026
Acumatica records a supplier invoice as an AP bill on the Bills and Adjustments screen, which posts the vendor liability and the related expense or inventory accounts. To bring bills in without typing them, most teams use an import scenario on the Import by Scenario screen. The scenario reads an Excel or CSV data source and maps your columns to the AP bill fields: the vendor, the vendor reference number, the bill date, terms, branch, and the detail lines with description, quantity, unit cost, account, and amount. You set the mapping once, then run the same scenario for every future batch.
That is exactly the gap InvoicesOCR fills. It reads each PDF or scanned invoice and gives you the vendor, reference number, bill date, due date, tax, total, and the full line-item detail as columns in Excel or CSV. You arrange those columns to match your AP bill import scenario once, then reuse that layout for every batch. Because the values come out clean, as plain numbers and consistent dates, the import does not stall on the formatting errors that scenarios reject, and you can turn on the duplicate vendor reference check in AP preferences to catch bills loaded twice.
Acumatica does offer a way to read PDFs: the AP Document Recognition service, a licensed add-on that uses OCR and machine learning to pull invoice fields into the Incoming Documents screen, where each file sits in a pending status until it is recognized and turned into an AP bill. It is a capable feature, but it has to be licensed and enabled, it carries a monthly page allowance with charges beyond it, and it is positioned for English-language invoices in the US and Canada. InvoicesOCR is the alternative when you would rather not adopt and pay for that service: you read any invoice in the browser and get a clean spreadsheet you import yourself, with no add-on, no page meter, and full control of the data before it posts. Check Acumatica directly for current AP Document Recognition limits and pricing.
An AP bill 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 bills, and that is the document the extracted spreadsheet is built for. Capturing line items rather than a single lump total means your Acumatica records keep the detail you need for GL distribution, tax, and reconciliation against a PO receipt.
Already on a different system as well? The same extracted spreadsheet also produces a NetSuite vendor bill import or a SAP Business One A/P invoice import from the same data.
Acumatica is common in construction and distribution, where bills come with retainage, job costs, or per-SKU pricing. Those workflows have their own pages: invoice extraction for construction for subcontractor and material bills with retainage, and invoice extraction for retail for wholesale and distributor invoices priced by unit. Procurement teams matching bills to POs will also want invoice processing for procurement managers.
You import invoices into Acumatica with an import scenario on the Import by Scenario screen, which reads an Excel or CSV data source and maps your columns to the AP bill fields. You fill the header and detail lines, map them once, and run the import to post AP bills. InvoicesOCR extracts the data from your PDF or scanned invoices into a spreadsheet you arrange to match that scenario.
An AP bill in Acumatica is the document that records a supplier invoice on the Bills and Adjustments screen. Releasing it posts the vendor liability and the related expense or inventory accounts, and it carries the header details plus the line items. It is the document most teams use when bringing received supplier invoices into the system.
Yes. You prepare the data in Excel or CSV and import it through an import scenario. InvoicesOCR reads each supplier invoice and returns a file with the vendor, dates, amounts, tax, and line items, so you map the columns to your AP bill scenario and import a batch instead of typing each invoice by hand.
AP Document Recognition is a licensed Acumatica add-on that uses OCR and machine learning to read PDF invoices into the Incoming Documents screen and turn them into AP bills. It must be enabled, carries a monthly page allowance with charges beyond it, and is positioned for English invoices in the US and Canada. InvoicesOCR is the alternative when you would rather not license it.
Only with the licensed AP Document Recognition service. Without that add-on, Acumatica does not extract data from a PDF on its own and needs structured data in an import scenario. InvoicesOCR fills that gap by reading the PDF and returning the vendor, dates, totals, and line items as a clean spreadsheet you import yourself.
An import scenario maps the columns of an Excel or CSV file to fields on an Acumatica screen, such as the AP bill. You define the mapping once on the Import by Scenario screen, point it at your data file, and run it to create records in bulk. You can skip rows with errors and review what loaded, then fix and rerun any that failed.
Yes. Import scenarios are 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 bill entries.
An AP bill 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 bills, which is what the InvoicesOCR output is structured for.
InvoicesOCR produces an Excel or CSV file ready for an Acumatica AP bill import scenario, rather than posting through the contract-based API for you. That keeps you in control of how each batch is reviewed and loaded, and the same output also works for NetSuite, SAP Business One, and QuickBooks imports.
Turn PDF invoices into formatted Excel spreadsheets.
Build a NetSuite vendor bill import from the same data.
Keep complete line-item detail in your books.
The full tool that reads any invoice layout.
