NetSuite cannot match a transaction or location line
Decide whether to update, add, or replace lines, then use the keys for that specific sublist.
A location-specific update is missing the location key
Message may mention: Adding New Line to Sublist Locations is not Allowed.
What it means
NetSuite cannot tell which location row to update.
Import context: Item records.
Check this first
Map the location within the item's Locations sublist when importing values such as reorder point or preferred stock level. A location elsewhere in the import does not necessarily identify this sublist row.
Show the steps
Check the record reference
- Find the field named in the error on the import's Field Mapping page.
- Open its edit control and check the selected reference type.
- Compare that setting with the actual CSV value. A number could be a name, an external ID, or an internal ID. Its appearance alone does not establish the type.
- Locate the intended record in the same account. Confirm its identity and whether it is available for this transaction.
- Correct the file or mapping so they agree. Use a default only when it applies to every affected row.
If you need to see internal IDs, enable them in your personal preferences or include them in a saved-search export. Supported reference types vary by field. Name matching is generally case-insensitive, so changing capitalization alone should not be the standard recommendation.
For a duplicate-record message, determine whether you intend to update the existing record or create a different one. Do not generate new external IDs simply to get past the error. For inactive records or subsidiary restrictions, verify the intended business setup before changing it. Those are account decisions, not text-cleanup operations.
Decide whether to update, append, or replace lines
- Identify the item being updated.
- Inspect its existing Locations sublist.
- Map the location key within that sublist to identify the row.
- Check the intended reorder point or stock-level values before retrying. A body location field does not necessarily identify the sublist row.
If that looks right
Documentation checked September 16, 2026.
A sales order reports a deleted line
Message may mention: deleted since.
What it means
The update's line handling needs review.
Import context: Sales orders.
Check this first
Check existing lines before replacing a sublist.
Show the steps
Decide whether to update, append, or replace lines
Ask first: Are you changing existing lines, adding new lines, or replacing the whole list?
- To update a line, export and use its real line key.
- To add lines through the documented transaction-item workflow, map the line-key column with blank values for the new lines.
- When an item appears more than once, the item reference alone may not identify a unique line.
- Do not invent sequential line IDs from spreadsheet row numbers.
Sublist replacement is a separate choice. Enabling it replaces existing sublist content with the imported content. With replacement off, behavior depends on whether the sublist supports matching by keys. Get the complete intended list before choosing replacement. Item pricing and demand plans need their own guidance.
Do not generalize these line-key rules to every sublist. Use the import documentation for the selected record type and sublist.
If that looks right
Documentation checked September 16, 2026.
An update asks you to choose an item
Message may mention: choose an item.
What it means
The update may use incorrect line identifiers.
Import context: Sales orders.
Check this first
Export the actual line IDs.
Show the steps
Decide whether to update, append, or replace lines
Ask first: Are you changing existing lines, adding new lines, or replacing the whole list?
- To update a line, export and use its real line key.
- To add lines through the documented transaction-item workflow, map the line-key column with blank values for the new lines.
- When an item appears more than once, the item reference alone may not identify a unique line.
- Do not invent sequential line IDs from spreadsheet row numbers.
Sublist replacement is a separate choice. Enabling it replaces existing sublist content with the imported content. With replacement off, behavior depends on whether the sublist supports matching by keys. Get the complete intended list before choosing replacement. Item pricing and demand plans need their own guidance.
Do not generalize these line-key rules to every sublist. Use the import documentation for the selected record type and sublist.
If that looks right
Documentation checked September 16, 2026.
Repeated items make line matching ambiguous
Message may mention: Ambiguity.
What it means
Repeated items make line matching unclear.
Import context: Transactions.
Check this first
Identify existing lines explicitly.
Show the steps
Decide whether to update, append, or replace lines
Ask first: Are you changing existing lines, adding new lines, or replacing the whole list?
- To update a line, export and use its real line key.
- To add lines through the documented transaction-item workflow, map the line-key column with blank values for the new lines.
- When an item appears more than once, the item reference alone may not identify a unique line.
- Do not invent sequential line IDs from spreadsheet row numbers.
Sublist replacement is a separate choice. Enabling it replaces existing sublist content with the imported content. With replacement off, behavior depends on whether the sublist supports matching by keys. Get the complete intended list before choosing replacement. Item pricing and demand plans need their own guidance.
Do not generalize these line-key rules to every sublist. Use the import documentation for the selected record type and sublist.
If that looks right
Documentation checked September 16, 2026.
Sales-team contributions exceed 100%
Message may mention: contribution, 100%.
What it means
Imported and existing sales-team percentages may exceed the allowed total together.
Import context: Transactions.
Check this first
Review the complete team.
Show the steps
Decide whether to update, append, or replace lines
- Review the complete sales team already on the transaction.
- Compare its contributions with the proposed imported team.
- Check whether imported and existing percentages together exceed 100%.
- Establish the complete intended team before choosing how to update its sublist.
Documentation checked September 16, 2026.
Related errors
- An item on a received line cannot be changed
- The import has no linked item, expense, or member lines
- Vendor bill files or purchase order mappings conflict
- 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