NetSuite cannot match an item in a CSV import
Check the item reference in the right context: a transaction line, kit member, related item, or manufacturing cost template.
The cost item or category cannot be matched
Message may mention: item.
What it means
The item may be missing or paired with the wrong cost category.
Import context: Manufacturing cost templates.
Check this first
Check the item's purchasing information as well as its identity.
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.
If that looks right
Documentation checked September 16, 2026.
An invoice item cannot be matched
Message may mention: item.
What it means
The invoice cannot match its item.
Import context: Invoices and credits.
Check this first
Check the invoice form's item selection, active state, and name-versus-ID mapping.
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.
If that looks right
Documentation checked September 16, 2026.
A related item uses a different display name
Message may mention: Invalid Item Reference Key.
What it means
For this import, a related item's store display name can affect name matching.
Import context: Related items.
Check this first
Check the displayed value on the related item and whether the mapping expects a name or internal ID. If the store display name is populated, Oracle identifies that name as the relevant name reference in this scenario. This explanation is specific to related items.
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.
If that looks right
Documentation checked September 16, 2026.
A kit member cannot be matched
Message may mention: Invalid item reference key.
What it means
The kit cannot match a member item.
Import context: Kits and packages.
Check this first
Check that the member exists and is active, then align the member-item mapping with the name or internal ID in the file. The relevant field is the member reference, not the kit's own identity.
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.
If that looks right
Documentation checked September 16, 2026.
A sales order item cannot be matched
Message may mention: item.
What it means
The sales order cannot match its item.
Import context: Sales orders.
Check this first
Check the selection and reference type.
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.
Did the spreadsheet change the item reference?
An item reference can look like a number even when its characters need to be preserved exactly. Compare the saved CSV value with the reference copied or exported from NetSuite.
For example, if NetSuite's reference is 001234 and the CSV contains 1234, those are different references. Spreadsheet conversion is one possible cause of this error.
Show the steps
- Confirm whether the Item mapping expects a name, internal ID, or external ID. Get the exact reference of that kind from NetSuite.
- In the spreadsheet, set the destination cells to Text before pasting or importing the references.
- Restore the original references from NetSuite. Formatting a value as Text after characters have been lost does not bring them back.
- Save the CSV. Open it in a text editor and check that the item reference still has the expected characters, including any leading zeros.
- Retry with the appropriate Transactions > Sales Order import setup and the matching Item reference type. Use Update when changing existing sales orders; use the data-handling mode appropriate to the intended job otherwise.
The purpose of the Text setting is to preserve the identifier. CSV files do not retain an Excel column's formatting, so the saved text is the final check. Changing spreadsheet formatting does not change NetSuite's Name/Internal ID/External ID mapping.
If that looks right
If the saved reference already matches NetSuite, return to the item-selection and mapping checks. A correct reference may still be unsuitable for the sales order. Formatting is not the explanation for every invalid-item message.
If that looks right
Read Oracle's guidance · Microsoft: Keeping leading zeros and large numbers · Microsoft: CSV export behavior
Documentation checked September 16, 2026.
Related errors
- NetSuite cannot identify the record to import
- NetSuite says the record already exists
- The item unit or record type does not match
- NetSuite could not match a record or parent item
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite