CSV File Import Error Messages

This page describes some common file import errors and how you can fix them.

CSV Files with Errors

If your CSV file has invalid characters or other errors, the import fails and an error shows on the Banking Import History page. In the Import Status details, you can see the reasons for the failure and download a CSV file with an extra column showing errors for each transaction row.

You can also see the list of CSV import error files at Documents > Files > File Cabinet > SuiteBundles > Bundle 293699 > com.netsuite.bsp > CSV Files with Errors.

The CSV import error file doesn't include the transaction's account number and is deleted automatically every 90 days.

Error Message	Cause or Scenario	Solution
Invalid date value: {date}. Verify that the Date Format on the Formatting Preferences subtab of your format profile matches the date in the uploaded file.	The parse doesn't accept the date for one of these reasons: The Date Format field value doesn't match the date in the uploaded CSV file. The uploaded files is corrupted or has missing date values.	To fix this, do the following: On the Parser Configuration subtab of your format profile, click the Formatting Preferences subtab. Check the Date Format field. Make sure it matches the date format in your statement file. Update if needed.
The file upload failed due to one of the following reasons: One or more column CSV column headers do not match the format profile's Field Mapping subtab values. The uploaded CSV file is not in UTF-8 encoded format. Check your CSV file and then try again.	The CSV import failed because the column headers don't match the mapping configuration, or the file isn't UTF-8 encoded.	To fix this, do the following: Check your parser configuration. On the Parser Configuration subtab of your format profile, click the Field Mapping subtab. Make sure the CSV column headers match the field mapping values in NetSuite. Update if needed. Make sure your CSV file is UTF-8 encoded. For details on converting your file, see Preparing CSV Parser Bank Statement Files for Import.
Invalid transaction line: {line number}. Verify that only one of the following fields has a value: Amount, Debit Amount, or Credit Amount.	The CSV file has more than one amount value.	Check your CSV file and make sure only one of these fields has a value: Amount Debit Amount Credit Amount
Invalid format for value: {number}. The following format preferences are in the configuration: Number Format: {number format}, Negative Number Format: {negative number format}. Either update your Formatting Preferences or the number format in the bank statement file.	The number field in file doesn't match the Number Format and Negative Number Format in the Format Preferences.	Check your parser configuration to match the number format in your CSV file.
One or more required column values are missing: {file mapping field}.	The CSV file is missing mapped field values.	Check your CSV file and make sure these field values are present: Required mapping fields, like Date, Account Number, or Transaction Type. Conditional required fields, like Amount, Credit Amount, Debit Amount, and Amount Indicator.
One or more lines in the uploaded CSV file contain errors. To see the list of transactions with errors, see {URL}. For files with more than 100 transactions, only the first 100 transactions with errors are shown.	One or more lines in the CSV file have errors.	Click the link to see the transaction error details.
The Credit Amount value cannot be a negative amount.	Amount Credit column has a negative amount.	Update the amount in your CSV file to a positive value.
Verify that the Transaction Type matches the value provided in the transaction amount.	The transaction type doesn't match the amount value in the transaction.	Check the Transaction Type field in your parser configuration. Make sure it matches the transaction amount in your CSV file.
The file could not be imported, because {code} is not one of the recognized bank transaction codes. {code} must be mapped to a bank data type in NetSuite. For details, contact your administrator. For a list of custom bank transaction codes, your administrator must contact your financial institution.	The CSV file has an invalid transaction type or code.	To see the list of supported transaction codes, see CSV Transaction Codes.
The Amount value cannot be a negative amount when using the Amount Indicator field.	The Amount column has a negative number.	In your formatting preferences, if you set a value in the Amount Indicator field, the amount in your CSV file must always be an absolute value.
Invalid Amount Indicator value: {amount indicator}. Verify that the Credit Indicator and Debit Indicator values on the Formatting Preferences subtab of your format profile matches the data in the uploaded file.	The amount indicator in CSV file doesn't match the Amount Indicator preference in the format profile.	To fix this, check your parser configuration: On the Parser Configuration subtab of your format profile, click the Field Mapping subtab. In Amount Indicator, check if the value matches your CSV file. You must also set the Credit Indicator and Debit Indicator preferences under the Formatting Preferences subtab when mapping the Amount Indicator field.

Error Message

Cause or Scenario

Solution

Invalid date value: {date}. Verify that the Date Format on the Formatting Preferences subtab of your format profile matches the date in the uploaded file.

The parse doesn't accept the date for one of these reasons:

The Date Format field value doesn't match the date in the uploaded CSV file.
The uploaded files is corrupted or has missing date values.

To fix this, do the following:

On the Parser Configuration subtab of your format profile, click the Formatting Preferences subtab.
Check the Date Format field. Make sure it matches the date format in your statement file. Update if needed.

The file upload failed due to one of the following reasons:

One or more column CSV column headers do not match the format profile's Field Mapping subtab values.
The uploaded CSV file is not in UTF-8 encoded format.

Check your CSV file and then try again.

The CSV import failed because the column headers don't match the mapping configuration, or the file isn't UTF-8 encoded.

To fix this, do the following:

Check your parser configuration.
1. On the Parser Configuration subtab of your format profile, click the Field Mapping subtab.
2. Make sure the CSV column headers match the field mapping values in NetSuite. Update if needed.
Make sure your CSV file is UTF-8 encoded.

For details on converting your file, see Preparing CSV Parser Bank Statement Files for Import.

Invalid transaction line: {line number}. Verify that only one of the following fields has a value: Amount, Debit Amount, or Credit Amount.

The CSV file has more than one amount value.

Check your CSV file and make sure only one of these fields has a value:

Amount
Debit Amount
Credit Amount

Invalid format for value: {number}. The following format preferences are in the configuration: Number Format: {number format}, Negative Number Format: {negative number format}. Either update your Formatting Preferences or the number format in the bank statement file.

The number field in file doesn't match the Number Format and Negative Number Format in the Format Preferences.

Check your parser configuration to match the number format in your CSV file.

One or more required column values are missing: {file mapping field}.

The CSV file is missing mapped field values.

Check your CSV file and make sure these field values are present:

Required mapping fields, like Date, Account Number, or Transaction Type.
Conditional required fields, like Amount, Credit Amount, Debit Amount, and Amount Indicator.

One or more lines in the uploaded CSV file contain errors. To see the list of transactions with errors, see {URL}. For files with more than 100 transactions, only the first 100 transactions with errors are shown.

One or more lines in the CSV file have errors.

Click the link to see the transaction error details.

The Credit Amount value cannot be a negative amount.

Amount Credit column has a negative amount.

Update the amount in your CSV file to a positive value.

Verify that the Transaction Type matches the value provided in the transaction amount.

The transaction type doesn't match the amount value in the transaction.

Check the Transaction Type field in your parser configuration. Make sure it matches the transaction amount in your CSV file.

The file could not be imported, because {code} is not one of the recognized bank transaction codes. {code} must be mapped to a bank data type in NetSuite. For details, contact your administrator. For a list of custom bank transaction codes, your administrator must contact your financial institution.

The CSV file has an invalid transaction type or code.

To see the list of supported transaction codes, see CSV Transaction Codes.

The Amount value cannot be a negative amount when using the Amount Indicator field.

The Amount column has a negative number.

In your formatting preferences, if you set a value in the Amount Indicator field, the amount in your CSV file must always be an absolute value.

Invalid Amount Indicator value: {amount indicator}. Verify that the Credit Indicator and Debit Indicator values on the Formatting Preferences subtab of your format profile matches the data in the uploaded file.

The amount indicator in CSV file doesn't match the Amount Indicator preference in the format profile.

To fix this, check your parser configuration:

On the Parser Configuration subtab of your format profile, click the Field Mapping subtab.
In Amount Indicator, check if the value matches your CSV file. You must also set the Credit Indicator and Debit Indicator preferences under the Formatting Preferences subtab when mapping the Amount Indicator field.

CSV Files with Errors

To fix this, do the following:

To fix this, do the following:

To fix this, check your parser configuration:

Related Topics