NetSuite cannot read the CSV file or its columns
Inspect the saved file for encoding, separators, quoted fields, headers, and unintended records.
The file needs to be uploaded again
Message looks like
The following file(s) could not be uploaded because of one or more errors. Please correct and re-upload.
What it means
NetSuite could not read the uploaded file, usually because the saved encoding or delimiter does not match what the Import Assistant expects.
Import context: General imports.
Check this first
Save a fresh CSV copy with the delimiter and encoding selected in the Import Assistant and upload that copy.
Show the steps
Steps for this error
- Save a fresh copy as CSV using the delimiter and encoding selected in the Import Assistant. When special characters fail, save the file as UTF-8, for example through a text editor’s Save As encoding option.
- Open the saved file in a text editor and inspect its first rows for unexpected characters or separators.
- Upload that saved copy again instead of reusing the previous upload.
Documentation checked September 16, 2026.
A row has too many columns
Message looks like
Different number of columns than in the header row
What it means
A row has a different number of fields than the header, which usually means a comma or an unclosed quotation mark split the row apart.
Import context: General imports.
Check this first
Compare the failing row field count with the header and inspect the quoting around free-text fields.
Show the steps
Steps for this error
- Compare the header’s field count with the failed row’s field count.
- Inspect commas, delimiters, and quotation marks around free-text fields on that row.
- Repair the quoting or shifted value and reopen the saved CSV before uploading it.
Documentation checked September 16, 2026.
A journal column has no heading
Message looks like
No empty or blank headers are allowed in the CSV file
What it means
The file has a column without a heading in row one, often an empty column the spreadsheet saved to the right of the data.
Import context: Journal entries.
Check this first
Give every column a heading and delete unnamed columns before saving the CSV.
Show the steps
Steps for this error
- Confirm row 1 of the file holds a heading for every column, with none blank.
- Remove unnamed columns the spreadsheet may have saved to the right of your data.
- Retry the file.
Documentation checked September 16, 2026.
A totals row asks for Account
Message looks like
Please enter the value(s) for Account
What it means
An extra row, usually a debit and credit totals row, is being read as another journal line, and a line cannot exist without an account.
Import context: Journal entries.
Check this first
Remove totals rows and any other rows that are not journal lines from the saved CSV.
Show the steps
Steps for this error
- Look for an extra row in the file, usually a totals row under the Debit and Credit columns. Every row is treated as a journal line, so a totals row asks for Account.
- Remove the totals row from the saved CSV.
- Retry the journal.
Documentation checked September 16, 2026.
The file contains unreadable characters
Message looks like
Oracle does not publish one exact wording for this case. Match it by the situation described below.
What it means
The file contains characters NetSuite cannot read, usually a copy-paste artifact or a save in the wrong encoding.
Import context: General imports.
Check this first
Re-save the file in the encoding selected in the Import Assistant and inspect the failing row in a text editor.
Show the steps
Steps for this error
- Identify the row and character position from the complete error when available.
- Open the saved CSV in a text editor and compare its encoding with the Import Assistant selection.
- Replace the confirmed unreadable character or resave with the matching encoding, then upload the new file.
Documentation checked September 16, 2026.
Related errors
- Customer type or linked contact data needs attention
- A required field is missing or cannot be written
- Item or custom list translations cannot be imported
- Sales order terms and payment method conflict
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.