NetSuite says the record already exists
Find the existing record before deciding whether to add a new one or update what is already there.
A custom record already uses this identifier
Message may mention: Custom Record.
What it means
Another record uses this identifier.
Import context: General imports.
Check this first
Check existing external IDs.
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 entity already uses this external ID
Message may mention: entity.
What it means
Another entity may already own that external ID.
Import context: Leads and prospects.
Check this first
Search entities by the value and establish which record the import is meant to create or update.
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 revaluation already uses this item, location, and date
Message may mention: already exists.
What it means
A revaluation already occupies this item, location, and date combination.
Import context: Inventory cost revaluations.
Check this first
Find it before deciding whether an update is appropriate.
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.
The transaction already exists
Message may mention: record already exists.
What it means
The identifier may belong to an earlier transaction.
Import context: Transactions.
Check this first
Find it before creating another.
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 cannot match an item in a CSV import
- 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