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 may mention: re-upload.
What it means
NetSuite couldn't read the file.
Import context: General imports.
Check this first
Check encoding.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Documentation checked September 16, 2026.
A row has too many columns
Message may mention: columns.
What it means
A row has too many fields.
Import context: General imports.
Check this first
Check quotes and separators.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Documentation checked September 16, 2026.
A journal column has no heading
Message may mention: blank headers.
What it means
A column lacks a heading.
Import context: Journal entries.
Check this first
Inspect the first CSV row.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Documentation checked September 16, 2026.
A totals row asks for Account
Message may mention: Account.
What it means
A totals row may be treated as another journal line.
Import context: Journal entries.
Check this first
Check the final records.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
Documentation checked September 16, 2026.
The file contains unreadable characters
What it means
The file's encoding may differ from the import setting.
Import context: General imports.
Check this first
Check both.
Show the steps
Check the saved CSV structure
- Inspect the actual saved CSV, not just its spreadsheet display.
- Confirm the file's separator and encoding agree with the import settings.
- Parse quoted fields correctly. A comma inside a quoted description is not another column.
- Compare each parsed row with the header. Identify extra fields, unnamed columns, and duplicate headings.
- Check for totals, notes, and partially populated rows that were not meant to be imported.
- Save a corrected copy and inspect it again before importing.
Completely blank trailing lines and partially populated records are different. Report the actual parsed content rather than assuming that any blank-looking spreadsheet row causes an error. The import's documented size limits are per job, including combined files: 25,000 records or 50 MB. A transaction with several CSV rows is not necessarily several records.
File conventions, separators inside fields
Oracle documents that duplicate column headings can cause the later column's values to be used. For results files, preserve duplicate error columns by position instead of silently overwriting them in a parser. Let the visitor identify the latest error column. CSV preparation tips
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
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite