AdemeroHelp

Import Paige invoices into Sage Intacct from CSV

Export a batch of invoices from Paige, copy the one-row-per-document CSV into Intacct's bill import template, and load it from Accounts Payable > Bills > Import — bills with vendor, dates, bill number, account, and amount filled from Paige; PDFs attached by hand if you want them.

For everyone30 minutes the first time, 10 minutes per batch afterVerified 2026-09-05

Before you begin

  • A Sage Intacct user with permission to import AP bills
  • Vendor IDs and account numbers known (a vendor list export from Intacct helps)
  • A Paige scan job with an invoice document type whose fields include vendor name, invoice number, invoice date, due date, and total

At the end of this guide, a batch of invoices that Paige read becomes a batch of AP bills in Sage Intacct in one import — vendor, dates, bill number, account, and amount filled from Paige's CSV — with nothing to build.

Intacct's importer uses its own template, downloaded fresh each time because it reflects your company's dimensions and custom fields. Paige's CSV has one row per document with a column per field; the work is a copy between the two. The importer does not attach files — Intacct's own documentation notes the supporting document ID column isn't implemented for import — so attach PDFs by hand afterwards, or use the API path.

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 — Fill Intacct's template

  1. In Intacct, go to Accounts Payable > All > Bills, select Import, and click Download template. Open the template in the same spreadsheet. Its required columns include VENDOR_ID, CREATED_DATE, DUE_DATE, LINE_NO, ACCT_NO, and AMOUNT; the rest depend on your configuration.

  2. Fill one row per bill (or per line):

    Template column Fill from
    VENDOR_ID The Intacct vendor ID for Paige's Vendor Name — look it up against a vendor export (VLOOKUP)
    RECORDID (bill number) Invoice Number
    CREATED_DATE Invoice Date
    DUE_DATE Due Date
    LINE_NO 1
    ACCT_NO The expense account number you post invoices to
    AMOUNT Total, as a plain number
    Dimensions (department, location, …) Whatever your company requires; the template shows which are mandatory
  1. Keep dates in your Intacct date format, and leave any supporting-document column blank.

  2. Save as CSV.

Step 3 — Import

Back in Accounts Payable > All > Bills > Import, choose the CSV and run the import. What you should see: Intacct reports how many bills were created and lists any rows with errors and the reason.

Step 4 — Attach the PDFs (optional)

Open each bill (Accounts Payable > All > Bills, Edit), open the Attachment field's menu, choose Add, and add the matching PDF from Paige's export (the CSV's file-name column tells you which is which). Each bill holds one attachment, which can contain several files. To never do this by hand, use the API path.

When it doesn't work

SymptomWhere to look
Rows rejected on the vendorVENDOR_ID must be the ID, not the name.
Rows rejected on a dimensionYour company requires a department, location, or other dimension on AP lines. Fill it in the template.
Rows rejected on the dateMatch your Intacct date format exactly.
Bills imported twiceUse Paige's Status: Not Exported filter when exporting and export each batch once; a duplicate bill number for the same vendor is also rejected by Intacct.

If a Paige field is consistently misread, improve its extraction guidance: Write extraction guidance the AI can follow.