NetSuite could not match a record or parent item
Check the record identifier first. For parent or matrix-item errors, use the conditional item hierarchy checks.
The parent and child have different item types
Message looks like
Invalid parent reference key xxx
What it means
The parent item is a different item type than the items being imported, and a parent must share its children's type.
Import context: Item records.
Check this first
Compare the parent's item type with the import's record type before creating or selecting a different parent.
Show the steps
Steps for this error
- Compare the parent item’s type with the imported item’s type. A parent must be the same item type as its children.
- If the parent was created with the wrong type, inactivate or delete it and recreate it with the right type under Lists > Accounting > Items.
- If the parent is correct, select the record type that matches it in the Import Assistant.
- Retry one item.
If that looks right
Documentation checked September 16, 2026.
NetSuite could not find a matching record
Message looks like
Could not find any records by this name.Could not find any records
What it means
NetSuite could not match a record needed for this row. If you are updating existing records, start with the value that tells NetSuite which record to change. If that checks out, look at the records referenced by the other mapped fields.
The message does not tell you which lookup failed. It does not establish that the record was deleted, that you selected Name as the reference type, or that the item is a matrix item.
Import context: General imports and Inventory items and Item records and Chart of Accounts and Vendor-Subsidiary Relationship.
Check this first
Pick one failed row. Check the import's Record Type, Data Handling setting, and the field used to identify the record being updated. Compare that identifier with the actual record in the same NetSuite account.
For an Inventory Item import using Update, begin with the item's own identity. The ID of a vendor, account, parent item, or another related record will not identify that item.
Show the steps
Identify the intended record and check the mapping
- Open one intended record in NetSuite. Confirm that it is the record you want to change and that the import's Record Type matches it.
- On Field Mapping, find the mapping that identifies the record itself. Check the NetSuite destination field, not just the CSV column heading.
- Compare the saved CSV value with the record's identifier. Use the relevant branch below for names, internal IDs, or external IDs.
- If the identity matches, inspect the related fields in the same row. A correct item ID does not establish that its parent, vendor, account, or custom-field reference is also correct.
- Correct the confirmed mismatch and retry one intended update. Check the resulting record before rerunning the remaining failed rows.
Use Update when changing existing records. Switching to Add or Update can create records that were not intended, so it is not a general fix for a failed match. Data handling options
If this is a matrix-child item update
Oracle documents this exact error when a matrix child is identified incorrectly by name. Keep the child and parent in separate fields:
| Item Name/Number | Subitem of |
|---|---|
| Shirt-Blue-Small | Shirt |
Do not put Shirt : Shirt-Blue-Small in Item Name/Number for this scenario. Alternatively, identify the child using its verified internal ID.
This example is specific to matrix-child updates. Other imports can have different name and hierarchy requirements. Oracle's matrix-child example
If this is a Chart of Accounts update
Check which ledger account the row identifies. Keep its account number, name, and internal ID distinct. A verified account internal ID can identify the existing account while other mapped fields supply the intended changes.
If a mapped field references an account by name, check the complete value expected by that field. For example, when its list shows 42000 Product Sales, supplying just 42000 or just Product Sales does not match Oracle's documented format. This rule concerns that account reference; it does not mean every Account Name column should have a number added to it. Account import and reference guidance
If this is a Vendor-Subsidiary Relationship import
For Update, check that the intended vendor-subsidiary relationship already exists. Open the vendor's Subsidiaries subtab and compare it with the row being imported.
Then review the relationship import's identity fields and its separate Vendor and Subsidiary mappings. Check what each supplied ID identifies before using it. The relationship does not have a standalone record page in the usual interface.
If the relationship is new, confirm that creating it is the intended task before choosing the appropriate data-handling option. Vendor-subsidiary import guidance
If that looks right
For a dropdown or list field, open its mapping settings and compare the selected reference type with the supplied value. The option may be Name, Internal ID, External ID, or another supported type. Not every field supports every option. These settings are separate from mapping the main record's own Internal ID. Reference types
If the message includes a script error or stack trace, have the script owner identify the failed lookup. The short message alone cannot establish whether the failure came from the import's record matching or another lookup during processing.
Keep the failed-row evidence together
Keep one failed row, the complete error, and screenshots of the import options and field mapping together. Those show what the import was trying to find.
If that looks right
Read Oracle's supporting guidance
The matrix-child correction is a documented scenario. The other checks are assembled from supporting guidance, not a confirmed diagnosis. The reported Inventory Item update has no tested resolution.
- Choose Data Handling for Import
- CSV Import FAQ
- Could not find any records by this name
- Chart of Accounts Import
- Vendor-Subsidiary Relationship Import
- Select Reference Types
- Error Status Codes
Documentation checked September 16, 2026.
The parent reference is affected by display-name settings
Message looks like
Invalid parent reference key xxx
What it means
A preference that displays item codes with display names can change the name needed by this import.
Import context: Item records.
Check this first
Compare the CSV value with the displayed combination and keep the matrix-option and external-ID fields intact. Prefer correcting the reference over changing a company preference just to make a name match.
Show the steps
Steps for this error
- Check whether Show Display Name with Item Codes is enabled in General Preferences. The parent reference must then include the display name or code.
- Either disable that preference, or include the item name/number with the display name or code in the file, together with the External ID and Matrix Option fields.
- Retry one item.
If that looks right
Documentation checked September 16, 2026.
Related errors
- Item-reference errors: choose your import context
- Spreadsheet changes to names and identifiers
- Scripts and permissions: when error details point there
- Record type does not match the existing record (General imports, Item records, Inventory items)
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.