An account, vendor, employee, or entity cannot be matched
Check the record identity and whether its subsidiary, currency, and active state fit the import.
- The employee cannot be matched (Time entries, Employees and expense categories)
- The item cannot match its asset or cost account (Item records)
- The account may not fit the subsidiary (Journal entries)
- The journal entity may not support the currency (Journal entries)
- The purchase-order vendor cannot be matched (Purchase orders)
- An entity subsidiary needs its full hierarchy (General imports)
- A book-specific journal rejects its currency (Journal entries)
The employee cannot be matched
Message looks like
Invalid employee reference key
What it means
The time entry cannot match the employee it names, usually because the value does not agree with the mapping choice of name or internal ID.
Import context: Time entries and Employees and expense categories.
Check this first
Compare the employee value with the mapping's choice of name or internal ID. A name must match the format the Time Tracking form shows for the employee.
Show the steps
Steps for this error
- Use the employee internal ID in the file, or the employee name exactly as the Time Tracking form shows it.
- On the Field Mapping page, open the Employee field and set the reference type to Internal ID or Names to match the file.
- Retry one entry.
If that looks right
Documentation checked September 16, 2026.
The item cannot match its asset or cost account
Message looks like
Invalid assetaccount reference key xxxInvalid cogsaccount reference key xxx
What it means
The asset or COGS account on the row cannot be matched, usually an inactive account, a subsidiary restriction, or a reference type mismatch.
Import context: Item records.
Check this first
Open the intended account and compare the CSV value with the mapping's Name or Internal ID choice.
Show the steps
Steps for this error
- Open the intended asset or COGS account and confirm its active state and subsidiary availability.
- Match the CSV value to the mapping’s Name or Internal ID reference type. A name must follow the format on the item’s Accounting subtab, including the number prefix and parent path when those are enabled. A mapping default can supply one account for every item.
- Retry one item after correcting that account reference.
If that looks right
Documentation checked September 16, 2026.
The account may not fit the subsidiary
Message looks like
Invalid account reference key 'xxx' for subsidiary 'xxx'
What it means
The account on a journal line is not available to the subsidiary the journal posts to, or the account reference does not match the mapping.
Import context: Journal entries.
Check this first
Open the account and check its subsidiaries, then compare the CSV value with the mapping's reference type.
Show the steps
Steps for this error
- Open the account named by the failed journal line and check its subsidiaries and active state. A name must match the format shown in the Account dropdown on Make Journal Entries.
- Compare the saved account value with the mapping’s Name or Internal ID reference type.
- Correct the account or subsidiary assignment, then retry one balanced journal.
If that looks right
Documentation checked September 16, 2026.
The journal entity may not support the currency
Message looks like
Invalid entity reference key xx for currency xx
What it means
The entity on a journal line cannot be used, usually because it is inactive, its displayed name differs from the CSV, or its currency does not match the journal.
Import context: Journal entries.
Check this first
Check the entity's active state, displayed name, and currencies against the journal's transaction currency.
Show the steps
Steps for this error
- Confirm the entity on the journal line is active.
- Compare the CSV value with how the entity is listed in NetSuite, including any ID prefix in the displayed name.
- Check the entity’s currency against the journal transaction currency. Add the transaction currency as a secondary currency on the entity record when the primary differs.
- Retry one journal.
If that looks right
Documentation checked September 16, 2026.
The purchase-order vendor cannot be matched
Message looks like
Invalid entity reference key
What it means
The vendor on the purchase order cannot be matched, usually an inactive vendor, a name that differs from the record, or the wrong reference type.
Import context: Purchase orders.
Check this first
Open the intended vendor and compare the CSV value with the mapping's Name or Internal ID choice.
Show the steps
Steps for this error
- Open the vendor intended for the purchase order and confirm it is active and available to the transaction subsidiary.
- Compare the CSV value with the Vendor mapping’s selected reference type. A name must match the Vendor field on Enter Purchase Orders exactly.
- Correct the vendor reference and retry one purchase order.
If that looks right
Documentation checked September 16, 2026.
An entity subsidiary needs its full hierarchy
Message looks like
Invalid subsidiary reference key xxxTransaction subsidiary xx is not valid for entity xx. Please choose a different entity.
What it means
The subsidiary reference does not match, often because a child subsidiary needs its full path, such as Parent : Europe : Spain.
Import context: General imports.
Check this first
Compare the value with the subsidiary's full displayed hierarchy.
Show the steps
Steps for this error
- Open the intended subsidiary and copy the value in the form expected by the Entity Subsidiary mapping.
- If matching by name, include the required parent hierarchy; if matching by ID, select that ID type.
- Correct one entity row and retry it.
If that looks right
Documentation checked September 16, 2026.
A book-specific journal rejects its currency
Message looks like
Invalid currency reference key x for accountingbook y
What it means
A book-specific journal entry is trying to set its currency, and that field is not yours to set: NetSuite fills it from the other fields on the record.
Import context: Journal entries.
Check this first
Remove the currency from the mapping for book-specific journal lines and let NetSuite supply it.
Show the steps
undefined
- Find the currency column mapped for the book-specific journal entry.
- Remove that mapping; the system fills the currency from the record’s other fields.
- Retry one journal.
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.