How to import vendor bills into NetSuite

You import vendor bills into NetSuite with the CSV Import Assistant, at Setup > Import/Export > Import CSV Records, by choosing the Vendor Bill record type and uploading a CSV file of bill headers and lines. Oracle sets out the rules on its Vendor Bill Import help page: every bill needs a unique ID, a reference to the vendor record and at least one line.

This guide covers what the file needs, the steps as Oracle documents them, what a manual import leaves to your team, and how the same work is automated. Everything about NetSuite here was checked against Oracle’s NetSuite help on 16 October 2026.

What do you need before you import vendor bills into NetSuite?

From Oracle’s vendor bill and Import Assistant help pages:

• The Import CSV File permission, which Oracle lists as the requirement for using the Import Assistant.

• A unique ID for every bill, included on every line of every file. Oracle recommends external IDs for new data.

• A vendor reference for each bill, given as the vendor’s internal ID or external ID. Oracle advises against identifying the vendor by name.

• Account values in the right format. If Use Account Numbers is enabled at Setup > Accounting > Accounting Preferences, give the number and name together (for example 11000 Accounts Payable). If it is off, give the name alone.

• Amounts that agree. Where the file holds Amount, Tax Amount and Gross Amount, Gross Amount must equal Amount plus Tax Amount.

• An Exchange Rate field mapped, if the Multiple Currencies feature is enabled. Currency comes from the referenced vendor.

• Tax codes set up in advance, with a Tax Code and Tax Amount on each item and expense line, if your account uses Advanced Taxes.

Expense lines travel in their own file. If your bills only have item lines, one CSV can hold everything. If they include expense lines, Oracle says to use the multiple files option: one file for the bill headers and one for expenses, plus a third for items if you have them, each carrying the same external ID so the lines join up with their bill.

Classes, departments, locations and custom segments can be set for the whole bill or on each item and expense line, so the coding decisions are made in the file itself.

How to import vendor bills into NetSuite

The Import Assistant runs in five steps and checks each one before it lets you move on:

1. Go to Setup > Import/Export > Import CSV Records to open the Import Assistant.

2. On Step One Scan & Upload File, select the import type and the Vendor Bill record type, choose the character encoding and column delimiter, and select your file. Choose the multiple files option if your bills include expense lines.

3. On Step Two Import Options, choose how the data is handled. Oracle’s data handling options are Add for new records, Update for records already in NetSuite, and Add or Update for a mix. New bills use Add.

4. If you uploaded more than one file, complete Step Three File Mapping. This step only appears for multi-file imports.

5. On Step Four Field Mapping, check the default mappings. Map the vendor, the unique ID and the required Items sublist fields, plus Exchange Rate if you use Multiple Currencies.

6. On Step Five Save Mapping & Start Import, give the import map a name so you can reuse it, then run the import.

7. Check the result on the Job Status page at Setup > Import/Export > View CSV Import Status. For completed jobs, the page links to a results.csv file listing any records that were not processed because of errors, so you can correct them and import again.

Steps checked against Oracle NetSuite’s help on 16 October 2026.

Can a NetSuite vendor bill import link to purchase orders?

Yes, with limits. Oracle’s vendor bill import page says the Purchase Order field on the Field Mapping page can link a bill to one or more purchase orders, referenced by name, external ID or internal ID. A bill mapped to a purchase order cannot also carry mapped Items or Expenses in the same import, and partial billing of a purchase order is not supported.

Oracle also notes that vendor bills are typically imported to bring in open payables, and advises against importing any single transaction with more than 5,000 lines.

What are the limits of a manual vendor bill import?

The CSV import does what it is designed to do: it moves bill data into NetSuite in bulk. The work before and after the file stays with your team.

• Someone still reads every supplier invoice and keys its header and lines into the spreadsheet, with the right vendor ID, account and tax code. The import loads data a person has already typed.

• Coding is only as good as the columns. Department, class, location and custom segment values are whatever the person preparing the file entered.

• Purchase order linking is all or nothing for each bill. Partial billing is not supported, and the import page does not describe checking a bill against item receipts.

• Approval sits outside the file. The vendor bill import page says nothing about approval, so sign-off happens before the spreadsheet is built or after the bills are already in NetSuite.

• Errors appear at import time. Mapping and data problems show up in the results file after the job runs, and the fix is to correct the CSV and import again.

• The invoice itself does not travel with the record. The vendor bill import page does not describe attaching the supplier’s PDF, so the document a bill came from lives somewhere else unless someone attaches it by hand.

How to automate vendor bill processing in NetSuite

Automation replaces the spreadsheet with the steps around it: capture the invoice, read it, code it, match it, approve it, then post it to NetSuite through an integration.

Our NetSuite AP automation connects through the SuiteTalk REST and SOAP APIs with token-based authentication, so there is no SuiteScript to write or maintain. Vendor records, GL accounts, subsidiaries, custom segments and purchase orders sync from NetSuite. In practice:

• Capture: invoices arrive through several channels and AI extraction reads them. Purchase orders, vendor bills and credit memos are all handled.

• Coding: departments, classes, locations and custom segments come from your NetSuite setup, and the coding learns your patterns over time.

• Matching: bills are matched against NetSuite purchase orders and item receipts, with partial receipts and variance thresholds configurable. Our guide to three-way matching explains the checks.

• Approval: approvals route on amount, subsidiary, vendor or any NetSuite field, with escalation for overdue approvals. Existing SuiteFlow routing, conditions and escalation rules keep working as configured. More on invoice approval workflows.

• Posting: approved invoices create vendor bills in NetSuite with GL coding, departments, classes and locations. Stratas identifies whether each invoice is item-based against a purchase order or expense-based, and creates the matching NetSuite transaction type.

• Audit: every action is logged and linked to the NetSuite transaction ID.

In multi-subsidiary accounts, Stratas works out the subsidiary from the invoice data, and each subsidiary keeps its own chart of accounts, currency and approval rules. Exchange rates come from NetSuite’s currency tables, and vendor bills post with the right accounting book context where multi-book accounting is in use.

The CSV Import Assistant still has its place for loading open payables in bulk. For the invoices that arrive every day, the integration posts each bill once it has been read, matched and approved.