A list or custom field selection cannot be matched
Check the list behind the field, the allowed selection, and the mapping reference type.
The expense category cannot be matched
Message may mention: category.
What it means
The expense category cannot be matched.
Import context: Employees and expense categories.
Check this first
Check its active state, displayed name, and mapping 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.
If that looks right
Documentation checked September 16, 2026.
A custom item field cannot match its selection
Message may mention: custitem.
What it means
The value supplied to a custom item field does not match an allowed selection.
Import context: Item records.
Check this first
Identify the field from its script ID, then inspect the list or record it references. Check spelling, spaces, and the chosen reference type. For several selections in one cell, check the multi-select separator too. Confirm a missing selection belongs in the list before adding it.
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.
Check multiple selections and hierarchy
- Identify whether the value represents a parent/child path, several selections, or an ordinary text value.
- Check the separator selected for this import.
- Make sure that separator does not split part of a real identifier.
- Check for a repeated selection within one cell.
- When updating the complete set, retain existing selections that must remain.
Hierarchy and multi-select separators serve different purposes. Oracle describes colon-separated hierarchy paths and a configurable single-character separator for multiple selections. Follow the record-specific requirements where they differ.
Hierarchy and multi-select guidance
For manufacturing routings, check the routing-specific separator and whitespace requirements. Do not silently trim all record values or apply one whitespace rule across every import.
If that looks right
Documentation checked September 16, 2026.
The lead source cannot be matched
Message may mention: Lead Source.
What it means
NetSuite cannot match the lead source.
Import context: Leads and prospects.
Check this first
Check the configured list and include the campaign identifier when it forms part of the displayed value. The list's location depends on whether Marketing Automation is enabled.
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 website is needed to identify its category
Message may mention: category, website, <NULL>.
What it means
NetSuite needs a website before it can identify the site's category.
Import context: Website categories.
Check this first
Map the website or select a default when every row belongs to that site. Then check the category within that site.
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.
Related errors
- NetSuite cannot identify the record to import
- NetSuite says the record already exists
- NetSuite cannot match an item in a CSV import
- The item unit or record type does not match
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite