The item unit or record type does not match
Check the item type and unit type before changing purchase, sales, or stock units.
Record type does not match the existing record
Message looks like
The record you are attempting to load has a different type: {actualType} from the type specified: {requestedType}
What it means
NetSuite found a record, but the operation is trying to open it as a different type.
Reading the two types
| Part of the message | What it tells you |
|---|---|
| After different type: | The type NetSuite found on the existing record. |
| After type specified: | The type the operation requested. |
Oracle lists this message under SSS_RECORD_TYPE_MISMATCH. Oracle's error reference
Reported item-import example
In the reported example, otherchargesaleitem identifies an Other Charge for Sale item, while otherchargepurchaseitem identifies the Other Charge for Purchase type the operation requested. Sale item type, purchase item type
If that sale item is the intended update target, choose the Other Charge for Sale record type for the item import. If you intended to update a purchase item, check why the row points to a sale item before proceeding. The same message format can describe other mismatched types.
Import context: Record updates. The steps below apply to item imports. If the message comes from another record type or a script running during the import, use the relevant branch below.
Check this first
Open the record identified by the failing row and confirm that it is the record you meant to update. Then compare its type with the import's Record Type selection.
If the row points to the wrong record, correct its identifier. Changing the import type to suit an unintended record would target the wrong data.
Show the steps
For item imports: match the item import to the existing item
- Confirm the target. Check the identifier used to match the existing item, including its mapping. Open that item in the same NetSuite account and check its type.
- Start the import with the matching type. Open Import CSV Records under Setup > Import/Export. On Scan & Upload CSV File, select Items, then the Record Type that matches the item you confirmed. For the reported sale-item example, choose Other Charge for Sale only if that sale item is the intended update target.
- Use Update for an update-only job. On Import Options, select Update when the purpose is to change existing records.
- Review the mapping. Map the intended record identifier and the fields to change. Recheck the mapping after changing the selected type.
- Check the file's scope. If it contains different item types, separate the update rows by the Record Type each requires. Review the prepared import before running it.
Other Charge items have separate purchase, sale, and resale import types. Inventory and assembly items also have distinct choices, including serialized and lot-numbered types. Match the actual item subtype. Supported item import types
If that looks right
Read Oracle's supporting guidance
This is a documented message family. The reported Other Charge pair and the documented inventory example are separate cases. The checks are not a confirmed resolution of this reported import.
- Error Status Codes
- Other Charge for Sale Item
- Other Charge for Purchase Item
- Item Record Types that Can Be Imported
- record.load(options)
- Inventory Item Import Errors
- Using Item Records in SuiteScript
Documentation checked September 16, 2026.
A unit has no unit type to belong to
Message looks like
Invalid purchaseunit reference key xx for unitstype <NULL>Invalid saleunit reference key xx for unitstype <NULL>Invalid stockunit reference key xx for unitstype <NULL>
What it means
NetSuite needs the item's unit type before it can accept its purchase, sales, or stock unit.
Import context: Item records.
Check this first
If the item has no unit type, map the correct one along with the unit fields. Check that each unit belongs to that type. An identifier for a unit is not an identifier for a unit type.
Show the steps
Steps for this error
- Open the item and identify its Units Type before checking Purchase, Sale, or Stock Unit.
- Confirm each imported unit belongs to that unit type and that the mapping targets the matching field.
- Import the unit type with the unit values when the item does not already have one.
If that looks right
Documentation checked September 16, 2026.
Related errors
- A related item uses a different display name (Related items, Item records)
- The parent and child have different item types (Item records)
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.