Skip to content

Tools

NetSuite CSV Error Translator ​

Paste the error. Find out what to check.

NetSuite import errors don't always tell you where the problem is. Find the message below for an explanation and a few practical checks.

You can paste the whole message, including any record numbers.

Your search text stays in this tab unless you choose to send it for review. We count unsuccessful searches without recording the message.

Common places imports get stuck

Search 122 documented import situations across 35 guides. A match identifies the situation described in the wording, not a confirmed diagnosis for your account.

  • Transactions

    An item on a received line cannot be changed

    NetSuite is rejecting an item change because it considers the affected line already received. That does not establish why the import is changing the item. One possibility is that the CSV row points to a different line than you intended, even if your goal was only to update a date, price, or custom field. Compare the transaction, line, and item in the CSV with the saved transaction. Then decide whether this row should update an existing line, add a new one, or replace its item.

  • Inventory cost revaluations · Customers · Custom lists · Transactions

    NetSuite cannot identify the record to import

    Check which record the identifier belongs to and whether the import expects a name, internal ID, or external ID.

  • General imports · Inventory cost revaluations · Leads and prospects · Transactions

    NetSuite says the record already exists

    Find the existing record before deciding whether to add a new one or update what is already there.

  • Kits and packages · Related items · Item records · Sales orders · Invoices and credits · Manufacturing cost templates

    NetSuite cannot match an item in a CSV import

    Check the item reference in the right context: a transaction line, kit member, related item, or manufacturing cost template.

  • Item records · General imports · Inventory items

    The item unit or record type does not match

    Check the item type and unit type before changing purchase, sales, or stock units.

  • General imports · Inventory items · Item records · Chart of Accounts · Vendor-Subsidiary Relationship

    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.

  • Item records · Website categories · Employees and expense categories · Leads and prospects

    A list or custom field selection cannot be matched

    Check the list behind the field, the allowed selection, and the mapping reference type.

  • Journal entries · General imports · Time entries · Employees and expense categories · Item records · Purchase orders

    An account, vendor, employee, or entity cannot be matched

    Check the record identity and whether its subsidiary, currency, and active state fit the import.

  • General imports · Journal entries · Vendor bills

    A department or location cannot be matched

    Compare the reference type, hierarchy, active state, and subsidiary of the selected record.

  • Customers · Customers with contacts · Prospects with contacts

    Customer type or linked contact data needs attention

    Distinguish a customer-only import from a combined customer or prospect and contact import.

  • General imports · Journal entries · Related items · Item records · Inventory cost revaluations · Sales orders · Expense reports · Employees and expense categories · Leads and prospects · Customers

    A required field is missing or cannot be written

    Find the exact field, its mapping, and the form or sublist that requires it.

  • Sales orders · Journal entries · General imports · Expense reports · Transactions

    NetSuite cannot read the date or posting period

    Compare the saved CSV text with the importing user’s date format and the intended date or period.

  • Events

    Event dates or times are missing or invalid

    Check the event’s start and end values, date format, and whether it spans dates.

  • General imports · Customers

    Country and state values do not match

    Check the country name used by the account and the state or province allowed for that country.

  • Journal entries · General imports

    NetSuite cannot read the CSV file or its columns

    Inspect the saved file for encoding, separators, quoted fields, headers, and unintended records.

  • General imports · Item records · Vendor bills · Journal entries · Single Journal Entry import · Intercompany journal entries

    Numbers or identifiers changed in the CSV

    Inspect the saved value and compare it with the original before changing precision or number formatting.

  • Sales orders · Expense reports · General imports

    NetSuite CSV import says an amount is missing

    Check which field supplies the amount, whether an expense line needs a rate or quantity, and whether a sales order item is missing its base price.

  • Vendor bills

    The header amount disagrees with the lines

    The bill's header amount is mapped, and it disagrees with the line totals NetSuite computes itself. Remove the header Amount mapping from the Vendor Bill folder and let the lines set the total.

  • Inventory adjustments

    Inventory status does not match the stock being removed

    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. 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.

  • Inventory adjustments

    Inventory adjustment quantity exceeds available stock

    The requested quantity exceeds the quantity NetSuite will allow for the selected inventory detail. The difference can be too small to notice in the spreadsheet. Compare the full saved quantity with the available quantity using the same unit. Check other rows drawing from the same balance too.

  • Inventory worksheets

    A worksheet asks for inventory detail

    The worksheet rows need inventory detail because an accounting preference requires bins on this transaction type. Confirm the import is an inventory worksheet and review the bin requirement with your admin before changing preferences.

  • Item records · Sales orders · Transactions

    NetSuite cannot match a transaction or location line

    Decide whether to update, add, or replace lines, then use the keys for that specific sublist.

  • Sales orders · Invoices and credits · Assemblies · Manufacturing cost templates · Expense reports · Manufacturing routings

    The import has no linked item, expense, or member lines

    Check the detail mapping and how each item, expense, member, or operation row connects to its parent record.

  • Vendor bills

    Vendor bill files or purchase order mappings conflict

    Check bill headers, linked detail files, and whether the bill is sourced from a purchase order.

  • Vendor payments · Invoices and credits · Customer payments

    NetSuite cannot apply a payment or credit

    Identify the payment separately from the bill or invoice, then check the document’s open amount and application rows.

  • General imports · Inventory items · Item records · Manufacturing routings

    Multiple selections are split, repeated, or missing

    Check the separator and the complete intended set. Routing locations have their own whitespace requirements.

  • Item records

    Item prices or quantity breaks cannot be imported

    Check the starting price, price level, and existing matrix before deciding how the pricing should change.

  • Custom lists · Inventory items · Item translations

    Item or custom list translations cannot be imported

    Check language setup, translation mappings, and whether the main record needs to be created first.

  • General imports

    NetSuite import failed after the record was created

    Check what saved before retrying. A script or later processing step can fail after the record exists.

  • General imports

    A saved search cannot be accessed

    A custom field on the form pulls its value from a saved search that is inactive, deleted, or private to someone else. Ask an admin to confirm the search exists, is active, and is visible to the importing user.

  • Item translations · Item records · Assemblies

    NetSuite reports an unexpected error during import

    Choose the import context before following a documented example. A generic error alone does not establish the cause.

  • General imports

    Personal language settings differ

    Your language preference does not match the company language preference, so NetSuite warns that the import may run slower. A difference between a subsidiary or parent subsidiary language and the company language can also trigger it. Compare your personal and subsidiary language preferences with the company preference. This is a warning about import speed, not a failed record.

  • Item demand plans

    An item demand plan has an identity or date mismatch

    Distinguish the plan’s identity from its item reference and check the complete planning period.

  • Manufacturing routings

    A routing operation has an invalid sequence or work center

    Check sequence numbers within each routing and confirm that the selected group is a manufacturing work center.

  • Sales orders

    Terms and payment method conflict

    The order maps both Terms and Payment Method, and NetSuite accepts only one: terms bill to an invoice, a payment method bills to a cash sale. Decide how the order should bill and map only Terms or only Payment Method.

This guide covers common errors. Your account's scripts and settings can produce other messages.

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.

NetSuite Implementation Advisory & Administration