Acumatica AP Automation: AP Document Recognition and Accounts Payable Invoice Capture

Acumatica AP automation, explained

Acumatica AP automation means capturing, coding, approving and paying vendor bills inside Acumatica ERP without manual data entry. Acumatica ships part of this as AP Document Recognition, which reads a PDF submitted to the Incoming Documents form and fills in an AP bill for a person to review and save. Acumatica documents firm boundaries in its own help: PDF files only, avoid files over 10 MB because quality degrades, recognition may fail over 50 pages, best results with en-us files, and the number of recognized documents is limited by the applied license. An AI extraction layer in front of Acumatica handles the bills those boundaries exclude. Last updated July 2026.

What Acumatica AP Document Recognition does and does not cover

The flow is straightforward once the AP Document Recognition Service feature is enabled. You open the Incoming Documents form, drag a PDF into the preview area and click Recognize. Acumatica hands the file to an external recognition service, and the document moves through a short set of states: New, Pending Recognition, In Progress, then Recognized or Error. When it lands on Recognized, the summary area and the detail lines are populated with the values read from the invoice, and you click Save and Continue to create an AP document on the Bills and Adjustments form with a status of On Hold. Nothing posts without a person looking at it, which is a sensible design rather than a flaw.

The boundaries matter once volume arrives. Acumatica tells you to avoid large PDF files of more than 10 MB because recognition quality may decrease as document size and complexity increase, and it warns that recognition may fail on documents longer than 50 pages. It recommends files with the en-us locale for best results, so dates arrive as MM/DD/YYYY. It states plainly that complete accuracy cannot be guaranteed. And because the recognition runs on an external service, the number of recognized documents is limited by the applied license, which means throughput is a commercial question, not a configuration one. Intake is manual too: documents arrive by upload or through the Acumatica add-in for Outlook, so there is no unattended inbox sweep collecting invoices overnight.

Where InvoiceExtractor fits, and what it does not do

InvoiceExtractor is the capture layer, not an AP suite. It does not run Acumatica approval maps, execute payments, or replace AP Document Recognition for teams whose invoices already fit comfortably inside its limits and license count. What it does is read any vendor bill regardless of page count, file size, format or delivery route, split multi-invoice files, capture the complete line-item table and export a CSV ready to load. Teams that also need approval routing and payment execution on top pair it with accounts payable automation covering approval and payment. Because intake into Acumatica is manual, finance teams whose bills arrive across several mailboxes often gather them first with a service that brings every mailbox into one place.

If you are weighing native ERP capture against a dedicated extraction layer, the same question comes up on every mid-market platform. Our Business Central AP automation page covers the Payables Agent and its 10-page and 5 MB caps, NetSuite AP automation and Sage Intacct AP automation cover the equivalent native features there. For the wider category, read our accounts payable automation software page, and invoice data capture software explains how templateless AI reading differs from the template-trained OCR most ERP modules wrap.

Loading extracted bills into Acumatica

Once invoices are extracted you hold a CSV with one row per line item and identical headers across every vendor. Acumatica gives you three practical routes to load it. An import scenario built on a data provider pointed at your file is the standard tool for a repeatable bulk load, and it is the one most VARs reach for first. The Load Records from File action on the Bills and Adjustments detail grid handles a quick one-off batch of lines without building anything. Developers post through the contract-based REST API for a scheduled, hands-off pipeline. All three need the vendor record and the expense account or inventory item to already exist in Acumatica, which is the single most common reason a first import fails. Our step-by-step walkthrough on how to import invoices into Acumatica covers all three routes, and importing invoices to an ERP compares the pattern across systems. For teams matching bills to purchase orders, purchase order data extraction captures the PO side, and invoice matching software explains three-way matching.