# Import Paige invoices into Acumatica with an import scenario

Set up an Acumatica CSV data provider and import scenario once, then load each batch of invoices Paige read into Bills and Adjustments with Prepare and Import — vendor, dates, vendor reference, account, and amount filled from Paige's CSV.

Product: paige · Audience: system-administrator · Time: 1 hour the first time, 10 minutes per batch after · Last verified: 2026-09-05

Canonical: https://help.ademero.com/paige/integrations/import-paige-invoices-into-acumatica-with-an-import-scenario

**At the end of this guide, a batch of invoices that Paige read becomes a batch of AP bills in Acumatica in one run — vendor, dates, vendor reference, account, and amount filled from Paige's CSV — with an import scenario you set up once and reuse.**

Acumatica's import has three parts: a **data provider** that describes the file, an **import scenario** that maps its columns to a screen (here **Bills and Adjustments**), and the **Import by Scenario** form where you upload each batch and click **Prepare**, then **Import**. Attachments aren't part of it; attach PDFs by hand from each bill's **Files**, or use the [REST API path](/paige/integrations/integrate-paige-with-the-acumatica-rest-api).

## Step 1 — Get the CSV out of Paige

- **Download:** in Paige, open **Documents**, click **Export**, and in the **Export Documents** dialog choose the **Scope**, the **Filters** (**Reviewed** only, **Field Data** with fields, **Status** not yet exported), tick **Download** under **Destinations**, and confirm. Paige emails a link; the zip contains the PDFs and the data files, including the one-row-per-document CSV.
- **SFTP:** if the scan job exports to SFTP, turn on **Generate combined metadata file** on the **FTP** card so each export run also writes the combined CSV.

Open it in a spreadsheet. **What you should see:** a header row with the PDF file name, the document type, and one column per Paige field, then one row per invoice.

## Step 2 — Shape the CSV

Add two columns Acumatica needs that Paige doesn't know:

| Column | Value |
| --- | --- |
| `Vendor` | The Acumatica vendor ID for Paige's `Vendor Name` (`VLOOKUP` against a vendor export) |
| `Account` | The expense GL account for the line (and `Subaccount` if you use them) |

Keep `Invoice Number`, `Invoice Date`, `Due Date`, and `Total` as they are; make `Total` a plain number and all dates one format. Save as CSV — the header row is what the data provider reads as field names.

## Step 3 — Create the data provider (once)

1. Open the **Data Providers** form (Integration > Data Providers), click **+** to add one, and name it `Paige invoices`.
2. **Provider Type:** *CSV Provider*. In the **Files** tab, upload the CSV from Step 2.
3. On the toolbar click **Fill Schema Objects**, then in the **Source Fields** pane click **Fill Schema Fields**. **What you should see:** your CSV's header names listed as fields.
4. Save.

## Step 4 — Create the import scenario (once)

1. Open the **Import Scenarios** form, click **+**, and name it `Paige – AP bills`.
2. **Screen Name:** *Bills and Adjustments*. **Provider:** `Paige invoices`. **Provider Object:** the CSV.
3. In the mapping table, add rows that set the bill's fields from the file's columns:
   
   | Target object / field | Source field |
   |---|---|
   | Document Summary → Type | `='Bill'` |
   | Document Summary → Vendor | `Vendor` |
   | Document Summary → Date | `Invoice Date` |
   | Document Summary → Due Date | `Due Date` |
   | Document Summary → Vendor Ref. | `Invoice Number` |
   | Document Details → Account | `Account` |
   | Document Details → Ext. Cost (or Amount) | `Total` |
   | Document Details → Transaction Descr. | `='Paige – ' + [Document Type]` or a fixed text |
   
   Add a mapping for the **Save** action at the end so each bill is saved. If your company requires a branch, terms, or subaccount, map those too — the import fails on any field the screen would require.
4. Save.

## Step 5 — Run each batch

1. Open **Import by Scenario**, choose `Paige – AP bills`, and on the **Files** tab upload the batch's CSV.
2. Click **Prepare**. **What you should see:** the rows appear in the prepared-data grid with status *Prepared*.
3. Click **Import**. **What you should see:** each row's status becomes *Processed*; rows with problems show an error text you can fix and re-run (leave **Break on Error** unchecked so one bad row doesn't stop the batch).
4. Open **Bills and Adjustments**. **What you should see:** one bill per invoice with the vendor, dates, vendor reference, and line.

Attach PDFs from each bill's **Files** icon if you want them.

## When it doesn't work

| Symptom | Where to look |
| --- | --- |
| Prepare finds no fields | The data provider's schema wasn't filled, or the header row changed. Re-run **Fill Schema Fields**. |
| Rows fail on Vendor | The value isn't an Acumatica vendor ID. |
| Rows fail on a required field | Branch, terms, subaccount, or another field your screen requires isn't mapped. |
| Dates rejected | Match your locale's date format. |
| Bills doubled | Export each batch once from Paige (use the **Status: Not Exported** filter). |

If a Paige field is consistently misread, improve its extraction guidance: [Write extraction guidance the AI can follow](/paige/document-processing/write-extraction-guidance-the-ai-can-follow).

## What's next

- [Integrate Paige with the Acumatica REST API](https://help.ademero.com/paige/integrations/integrate-paige-with-the-acumatica-rest-api)
- [Connect Paige to Acumatica](https://help.ademero.com/paige/integrations/connect-paige-to-acumatica)