Fix NetSuite Invalid IssueInventoryNumber CSV Error
A Transfer Order CSV import fails on a lot that fulfills fine manually because each TO item generates three lines, and your CSV points to the wrong one.
Sarah Jenkins, CPAPrincipal Finance Automation Specialist
On this page
When you import an Item Fulfillment from a Transfer Order via CSV, the Invalid issueinventorynumber reference key error stops the entire upload. The frustrating part? That same lot fulfills perfectly when you pick it manually in the UI.
This error isn't about the lot number itself. It's about which line on the Transfer Order your CSV is pointing to.
Why Transfer Order Lines Behave Differently
A Transfer Order in NetSuite doesn't store one line per item. In the transactionline table, every item on a TO generates three separate lines:
| Line Type | Purpose | Line Number Offset |
|---|---|---|
| Operational (anchor) | What you see on the TO screen | Base line (0) |
| Fulfillment | The Item Fulfillment line | TO line + 1 |
| Receipt | The Item Receipt line | TO line + 2 |
This structure is part of how NetSuite's Inventory Management handles transfer orders. The TO record itself initializes both the item fulfillment and item receipt transactions, and each carries its own line reference in the database.
When you import an Item Fulfillment from a Sales Order, the line references work the way you'd expect. Transfer Orders break that assumption. Your CSV must reference the fulfillment line, not the operational line you see on the TO record.
The Fix: Adjust Your Order Line Reference
If your Transfer Order shows the item on Line 1, the fulfillment line in the database is actually Line 2.
Here's the mapping you need in your CSV import:
- Order Line (or Line ID): Use the TO line number plus 1
- Item: The internal ID of the item
- Lot Number: The lot text value
For a single-line TO, your CSV should reference line 2 for the fulfillment, not line 1.
Worked Example
Say your Transfer Order has:
- Line 1: Item A (lot LOT-001)
- Line 2: Item B (lot LOT-002)
Your Item Fulfillment CSV should reference:
| Column | Value |
|---|---|
| Order Line | 2 (for Item A's fulfillment) |
| Item | Internal ID for Item A |
| Lot Number | LOT-001 |
The receiving line would be line 3 for Item A, which matters if you're also importing the Item Receipt.
Why the UI Works but CSV Fails
The UI handles this line translation automatically. When you click Fulfill on a Transfer Order, NetSuite knows to create the fulfillment against the correct internal line. The CSV import does not. It takes your line reference literally and validates it against the issueinventorynumber field on that specific line.
If you reference the operational line (the one you see on screen), the import looks for lot inventory on a line that doesn't carry fulfillment data. Hence the Invalid issueinventorynumber reference key error.
Verify Your Line Numbers First
Before you touch the CSV, confirm the actual line structure with a saved search:
- Go to Transactions > Management > Saved Searches > New
- Choose Transaction as the record type
- Add a filter: Type is Transfer Order
- Add these columns:
- Document Number
- Item
- Line
- Transaction Line Type
This search shows you the three lines per item. Match your CSV's order line to the row where Transaction Line Type equals Fulfillment. The SuiteScript Records Guide documents the transactionline table structure if you need to verify the field relationships programmatically.
What About the Item Receipt?
The same logic applies in reverse. When you import the Item Receipt for that Transfer Order, reference the receipt line (TO line + 2).
If you import both fulfillment and receipt from the same CSV source, you'll need two separate imports with different line offsets.
Mixing Item Types on One Fulfillment
One more constraint worth knowing: NetSuite's CSV import struggles when an Item Fulfillment mixes lot-numbered, serialized, and non-tracking items on the same import. If your TO has a mix, split the fulfillment into separate CSV imports by item type. The system handles homogeneous item types cleanly; mixed types can trigger additional validation errors that look unrelated to the actual issue.
Still Stuck? Check the Character Encoding
If the line fix doesn't resolve it, the lot text itself may carry invisible characters. NetSuite's UI and saved searches often strip or hide trailing spaces and non-breaking characters. The CSV import matches text exactly.
Open the lot's Inventory Number record and check the Lot Number field for hidden characters. If you suspect encoding issues, re-export the lot list and compare the hex values. A UTF-8 vs. Windows-1252 mismatch can produce characters that display fine but fail validation.
When One Error at a Time Isn't Enough
NetSuite's CSV import stops at the first validation error. The CSV Import Error Reporting documentation describes how post-processing errors get collected into a zip file sent via email, but validation errors during the import itself halt the process. There's no native setting to return a full row-by-row log. You'll fix one error, re-import, and hit the next.
For bulk transfers, this trial-and-error loop gets expensive fast. A small SuiteScript that loops through the fulfillment lines and validates the lot references before you import will save hours. Scripts can surface every failing line in a single execution, which the native import won't do.
The Practical Takeaway
The Invalid issueinventorynumber reference key error on Transfer Order fulfillments almost always comes down to line numbering. The lot is fine. The item is fine. Your CSV is pointing at the wrong internal line.
Reference the fulfillment line (TO line + 1) and the import will behave the way the UI does. If you're processing high volumes of Transfer Order fulfillments regularly, a validation script that checks line references against transactionline before import will get you to a clean, reconciled, and audit-ready state without the manual back-and-forth. Your auditors will thank you for keeping the fulfillment subledger accurate on the first pass.
