# Import Paige invoices into NetSuite with the CSV Import Assistant

Export a batch of invoices from Paige, shape the one-row-per-document CSV into NetSuite's vendor bill import layout, and load it with the CSV Import Assistant — vendor, date, reference, and expense lines filled from Paige, PDFs attached by hand if you want them.

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

Canonical: https://help.ademero.com/paige/integrations/import-paige-invoices-into-netsuite-with-the-csv-import-assistant

**At the end of this guide, a batch of invoices that Paige read becomes a batch of vendor bills in NetSuite in one import — vendor, date, reference, and an expense line filled from Paige's CSV — with nothing to build.**

NetSuite's importer wants two things Paige's CSV doesn't have as-is: a **unique ID per bill** on every row (NetSuite's *external ID*), and the **vendor as an internal or external ID**, not a name. Both are a column each in a spreadsheet. The importer takes no attachments; attach PDFs by hand afterwards, or use the [SuiteScript path](/paige/integrations/create-netsuite-vendor-bills-from-paige-with-suitescript).

## 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 when the download is ready; 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 it for NetSuite

Add and adjust columns so each row carries what a vendor bill needs:

| Column | Value |
| --- | --- |
| `External ID` | A unique ID per bill — `PAIGE-` plus the invoice number works, or the PDF file name's unique part. Required on every row. |
| `Vendor` | The NetSuite vendor's **internal ID** or **external ID**. Replace Paige's `Vendor Name` with the ID (a `VLOOKUP` against a vendor export from NetSuite). |
| `Date` | `Invoice Date`, in your NetSuite date format |
| `Due Date` | `Due Date` |
| `Reference No.` | `Invoice Number` |
| `Account` | The expense account — if your account uses account numbers, include both number and name, for example `6150 Office Expense` |
| `Amount` | `Total` as a plain number |
| `Memo` | Optional, for example the document type |

One row per bill gives one expense line. For several lines per bill, repeat the row with the same `External ID` and different account and amount — NetSuite groups rows by external ID.

Save as CSV.

## Step 3 — Run the Import Assistant

1. Go to **Setup > Import/Export > Import Tasks > Import CSV Records**.
2. **Import Type:** *Transactions*. **Record Type:** *Vendor Bill*. Choose the CSV and click **Next**.
3. **Import Options:** *Add*. Click **Next**.
4. **Field Mapping:** match your columns to NetSuite fields. Map `External ID` to **External ID** *and* to **Reference No.** if you want it visible on the bill, `Vendor` to **Vendor** (choose *Internal ID* or *External ID* as the reference type), `Date` to **Date**, `Reference No.` to **Reference No.**, and the expense columns to **Expenses: Account** and **Expenses: Amount**. Click **Next**.
5. Name the import (so you can reuse the mapping) and click **Save & Run**.

**What you should see:** the import queues; on **Setup > Import/Export > View CSV Import Status** it finishes with the number of bills created and a link to any rows that failed with the reason.

## Step 4 — Attach the PDFs (optional)

Open each bill and attach the matching PDF under **Communication > Files** (the CSV's file-name column tells you which is which). To never do this by hand, that's the SuiteScript path.

## When it doesn't work

| Symptom | Where to look |
| --- | --- |
| Rows fail on the vendor | You mapped a name; NetSuite wants an internal or external ID. |
| Rows fail on the date | The format doesn't match your NetSuite preference. Make every date the same. |
| Rows fail on the account | The account name must be exact; include the number if account numbers are on. |
| Bills doubled | Two imports of the same batch. Use Paige's **Status: Not Exported** filter and export once; External IDs also let NetSuite reject duplicates on a second import. |

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

- [Create NetSuite vendor bills from Paige with SuiteScript](https://help.ademero.com/paige/integrations/create-netsuite-vendor-bills-from-paige-with-suitescript)
- [Connect Paige to NetSuite](https://help.ademero.com/paige/integrations/connect-paige-to-netsuite)