Vendor bill files or purchase order mappings conflict
Check bill headers, linked detail files, and whether the bill is sourced from a purchase order.
Choose the message that matches your import.
The bill has no linked detail
Message looks like
You must enter a line item for this transaction
What it means
A vendor bill saved without any line. Bills with expenses import as two linked files, and the expense file's amount column must be named Total.
Import context: Vendor bills.
Check this first
Check the two-file setup: a shared external ID key, expense lines linked to the bill, and a Total column.
Show the steps
Steps for this error
- For vendor bills with expenses, use two linked files: a bill file and an expense file.
- Give both files a shared External ID key: map the bill file’s to Vendor Bill: External ID and the expense file’s to the Vendor Bill Expenses line.
- In the expense file, name the amount column Total, not Amount, and include the account.
- Retry one bill.
If that looks right
Documentation checked September 16, 2026.
The primary bill file repeats a key
Message looks like
Multiple rows in your primary CSV file have the same value for the key column. Please edit this file to eliminate rows with duplicate key column values for field 'ExternalId'
What it means
The primary bill file repeats the same external ID on more than one row, and the header file can only hold each bill once.
Import context: Vendor bills.
Check this first
Keep one row per bill in the primary file and move detail rows to the linked file.
Show the steps
Steps for this error
- In a multiple-file vendor bill import keyed on external ID, check the primary bill file for repeated external ID values.
- Keep one row per bill in the primary file; detail rows belong in the linked file.
- Retry the import.
If that looks right
This primary-header check applies to a multiple-file import. Repeating a transaction key on legitimate detail rows in a single-file import is a different case.
If that looks right
Documentation checked September 16, 2026.
Purchase-order sourcing conflicts with detail lists
Message looks like
purchase order list
What it means
The import is trying to source a bill from purchase orders while also supplying its item or expense lists.
Import context: Vendor bills.
Check this first
Choose the supported approach for the bill you intend to create. Oracle's described purchase-order linking import does not support partial billing.
Show the steps
Check how the detail rows are linked
- Confirm whether this is a single-file or multiple-file import.
- Identify the parent record key and the key used to connect each detail file.
- Verify that every required detail row points to an intended parent, with no spelling or whitespace changes in the linking value.
- Check the import's field mapping for the detail sublist. Defaults alone do not establish that detail rows were imported.
- Separate a record identifier from a line identifier. They serve different purposes.
For vendor bills, the documented multi-file structure separates bill headers from expenses, and can use another file for items. Repeat the linking key in the detail files. A duplicate key in a primary header file is different from a transaction key correctly repeated across detail rows.
For assemblies, link member rows to the assembly. For routings, check the operation sequence within each routing. For customer/contact combinations, keep each record's identity and fields separate. Check the actual mapping fields for the record being imported.
If that looks right
Documentation checked September 16, 2026.
Related errors
- An item on a received line cannot be changed
- NetSuite cannot match a transaction or location line
- The import has no linked item, expense, or member lines
- NetSuite cannot apply a payment or credit
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.