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 looks like
Invalid category reference key xx
What it means
The expense category on the row cannot be matched, usually because it is inactive or its name does not match the category list exactly.
Import context: Employees and expense categories.
Check this first
Check the category active state and exact displayed name, or switch the mapping to internal IDs.
Show the steps
Steps for this error
- Check that the expense category is active under Setup > Accounting > Expense Categories with Show Inactives checked.
- When matching by name, compare the CSV value with the Category dropdown on the expense report form.
- To avoid name issues, choose Internal ID as the reference type for the Category field on the Field Mapping page.
- Retry one line.
If that looks right
Documentation checked September 16, 2026.
A custom item field cannot match its selection
Message looks like
Invalid custitem reference key xxx
What it means
A custom item field points at a list, and the value on the row is not one of that list's active selections, or the reference type does not match.
Import context: Item records.
Check this first
Open the field definition from the ID in the error and compare the value with the allowed selections.
Show the steps
Steps for this error
- Use the custom field ID in the error to open the field definition and identify its source list or record.
- Compare the CSV value with an allowed active selection and the chosen reference type, including spaces, spelling, and letter case.
- For multi-select values, verify the configured separator before adding any missing list option.
If that looks right
Documentation checked September 16, 2026.
The lead source cannot be matched
Message looks like
Invalid Lead Source Reference Key
What it means
The lead source on the row is not in the account's Lead Sources list, or its name does not match the list's naming, which can include a campaign ID.
Import context: Leads and prospects.
Check this first
Compare the value with the Lead Sources list and include the campaign ID when the list shows one.
Show the steps
Steps for this error
- Compare the CSV value with the Lead Sources list: under Lists > Marketing > Marketing Campaigns when Marketing Automation is enabled, otherwise under Setup > Sales > CRM Lists.
- Match the displayed naming exactly. When the list shows the campaign ID with the title, include both, for example 34 OnlineForm.
- Add missing lead sources to the list or correct the file, then retry one row.
If that looks right
Documentation checked September 16, 2026.
A website is needed to identify its category
Message looks like
Invalid category reference key Information for website <NULL>
What it means
A site category needs its website, and the Site field is not receiving one, so the category reference resolves to nothing.
Import context: Website categories.
Check this first
Include the site name as it was created in NetSuite or set it as a mapping default.
Show the steps
Steps for this error
- A site category needs its website: include the site name as it was created in NetSuite and map it.
- Or set a default value for the Site field on the Field Mapping page with the edit icon.
- Retry one row.
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
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.