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 may mention: line item.
What it means
The bill has no linked detail.
Import context: Vendor bills.
Check this first
Check expense-file linkage and sublist mappings.
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.
The primary bill file repeats a key
Message may mention: primary, duplicate.
What it means
The primary file repeats a bill key.
Import context: Vendor bills.
Check this first
Keep one header row per bill in a multi-file import.
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
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 may mention: purchase order list, item/expense 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
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite