Inventory status does not match the stock being removed
Check the item, location, lot, bin, and status together, as well as the Status reference type.
Inventory status does not match the stock being removed
Message looks like
Invalid inventorystatus reference key {status} for issueinventorynumber {number}.
What it means
NetSuite could not use that status with the inventory detail on this line. The status might exist elsewhere, but the import still needs the correct item, location, lot, bin, and status combination.
Import context: Inventory adjustments.
Check this first
Verify how Status is mapped. If the file contains an internal ID, the mapping must use that reference type. Then inspect the exact inventory balance the line is meant to reduce.
Show the steps
Steps for this error
- Open the inventory balance for the item, location, lot or serial number, bin, and status named by the failed row.
- Confirm whether the Status mapping uses Name or Internal ID, then compare the saved CSV value with that type.
- Correct the confirmed mismatch and retry one inventory-detail line.
Does the stock have a bin assignment?
If the item uses bins and the relevant stock has no bin assignment, investigate whether put-away is outstanding. Confirm the physical bin before changing the import. A blank bin is not an error for every item.
If that looks right
This is a field example with supporting inventory documentation. A status marked available is different from a stock balance available in a particular bin. Check whether the item uses bins at that location before treating a blank bin as an error.
If that looks right
Documentation checked September 16, 2026.
Related errors
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.