Acumatica loads AP bills from a CSV or Excel file through an import scenario that maps your data to the Bills and Adjustments screen, not from a PDF. Upload your PDF or image invoices here and get clean rows with vendor, vendor reference, dates, line items, amounts, and tax, ready to map into your Acumatica import scenario.
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
Acumatica has a flexible import scenario engine that can load AP bills from a flat file into the Bills and Adjustments screen. The catch is that it only reads structured rows. Your invoices arrive as PDFs and scans, so the slow part is converting each document into the columns the scenario maps. That preparation is where AP teams lose hours.
An import scenario maps a CSV or Excel file to screen fields. It cannot turn a PDF supplier bill into a record, so every document has to be converted into structured rows first.
Each bill has to reference an existing vendor by Vendor ID, not the name printed on the invoice. The data has to be mapped to that ID before the scenario will create the bill.
A bill with several line items uses one flat file where the header values repeat across the detail rows. Building that structure by hand for a stack of invoices is slow and easy to break.
Without the Raise an Error on Duplicate Vendor Reference Number setting, the same bill can import twice. Catching that by eye across a large file is unreliable.
Lines need the right tax category and the bill needs the correct branch and AP account. A missing or wrong value stops the row from importing cleanly.
At month-end, keying a pile of supplier bills into Bills and Adjustments is slow, and every retyped amount is a chance for a transposed figure and a duplicate payment.
InvoiceXLSX reads your PDF and image bills with AI and exports the fields Acumatica needs as clean rows for your AP bill import scenario. You map the columns once, add the vendor ID, and run the scenario against the Bills and Adjustments screen. No retyping, no rebuilding the layout per vendor.
Upload native PDFs, scanned bills, or phone photos. The AI extracts vendor, vendor reference, dates, line items, tax, and totals from any layout.
Output arrives as structured columns you map to your Acumatica import scenario for the Bills and Adjustments screen, so values drop straight into the fields.
Each line item becomes its own detail row with description, quantity, unit cost, and amount, with the header values repeated as a flat file expects.
Process many invoices at once and export a single file, then run the scenario to create all the bills in one pass.
Download clean .csv or .xlsx that your import scenario reads, with the vendor reference on each bill for duplicate checking.
Invoices are processed over encrypted connections and deleted after extraction. Your supplier data is never sold or used to train public models.
From a folder of PDF invoices to released AP bills in Acumatica.
Upload your PDF or image bills to InvoiceXLSX. The AI reads each one and returns vendor, vendor reference, dates, line items, tax, and totals as structured rows, with the header values ready to repeat across detail lines.
Tip: Batch the whole stack in one pass, then review the values against the originals.
Match each bill to its Acumatica vendor by Vendor ID, since the scenario will not resolve a vendor by name alone. Keep the vendor reference on each bill so Acumatica can flag duplicates, then save the file as CSV or Excel.
Tip: Keep a vendor name to Vendor ID lookup so this mapping takes seconds.
In Acumatica, open or build an import scenario that targets the Bills and Adjustments screen, upload your file as the data source, map the columns to the fields, and process the records. The bills are created for review and release.
Tip: Turn on Raise an Error on Duplicate Vendor Reference Number in AP Preferences to block accidental double imports.
US businesses and finance teams on Acumatica that receive invoices as PDFs rather than clean import files.
Create a month of AP bills through an import scenario instead of keying each one into Bills and Adjustments.
Keep the close on schedule by removing manual data entry from the bill workflow.
Backfill opening AP balances and historical bills for a new client during implementation.
Handle high supplier-bill volume without adding AP headcount.
Acumatica does not have a single invoice upload button. Instead it uses import scenarios, a configurable mapping that reads a CSV or Excel file and replays it against a screen. For supplier invoices that screen is Bills and Adjustments in the accounts payable module, where each bill carries a vendor, vendor reference, dates, branch, and AP account, plus detail lines with their item or account, quantity, cost, and tax category. Because a flat file represents both header and lines, the header values repeat across the detail rows of a multi-line bill, and the scenario groups them into one document.
The part Acumatica cannot do is read the invoice itself. That is what InvoiceXLSX handles: it converts each PDF or photo into the structured rows your import scenario maps, with the vendor reference on every bill so the duplicate check on AP Preferences can do its job. Match each bill to its Vendor ID, run the scenario, and the bills are created for review and release. Saving the scenario means every future batch is a short, repeatable task rather than a day of typing into Bills and Adjustments.
Yes. Acumatica imports AP bills and AR invoices through import scenarios that map a CSV or Excel file to a screen such as Bills and Adjustments. It reads structured rows only, so you first convert your PDF or image invoices into that format, then map the columns in the scenario and process the records.
Build or open an import scenario that targets the Bills and Adjustments screen, upload your CSV or Excel file as the data source, map each column to the matching field, and process. Reference each bill by Vendor ID, repeat header values across detail rows for multi-line bills, then review and release the created bills.
No. Acumatica import scenarios read CSV or Excel files mapped to screen fields, not PDF or image files. To import PDF invoices, convert them to a structured file first. InvoiceXLSX extracts the vendor, dates, line items, and totals from each PDF so you can map them into your AP bill import scenario.
An import scenario is a reusable mapping that tells Acumatica how to read an external file and enter it on a screen, field by field. For AP bills it targets Bills and Adjustments. You upload the file, the scenario fills the fields as if typed, and the records are created in bulk for review.
Acumatica resolves the vendor by Vendor ID, not by the name on the invoice. Add the Vendor ID to each bill before importing. Keeping a simple lookup of vendor name to Vendor ID makes mapping your extracted invoice data fast and avoids unmatched-vendor errors during the import.
Turn on Raise an Error on Duplicate Vendor Reference Number on the Accounts Payable Preferences screen. With it enabled, Acumatica blocks a bill whose vendor reference already exists for that vendor. Keep the vendor reference on every row of your import file so the check can work.
Yes. Use a flat file where the header values repeat across the detail rows, and put one line item per row with its own description, quantity, cost, and tax category. The import scenario groups rows that share the same bill into a single document with all its lines.
Common causes are a Vendor ID that does not exist, a missing tax category or branch, a date in the wrong format, header values that do not repeat correctly across detail rows, or a column that is not mapped in the scenario. Confirm each bill references a valid vendor and that the scenario mapping matches your file.
