File Import Error Messages for Bank Statement Parsers

The file cannot be imported because the currency code [code] in the file does not match the currency code for the same account in NetSuite. Check your format profile record or contact your bank to correct the error and re-upload the file again.

The account currency in your bank statement file doesn't match the mapped account's currency in NetSuite.

Check which currency should be used. For details on checking account information in NetSuite, see Viewing the Chart of Accounts.

To fix the bank statement file, contact your financial institution.

The file upload failed because the file contains an incorrect date format. OFX Statement files use <YYYY-MM-DD> date format. Contact your bank to correct the error, and re-upload the file again.

Invalid date format.

To fix the date format in your bank statement file, contact your financial institution.

The file cannot be imported because the account [ID] in the file does not match an account in NetSuite. Check the Account Mapping in the format profile record or contact your bank to correct the error and re-upload the file again.

There's no matching account in NetSuite.

Check the account mapping in your format profile. Under the Account Linking subtab, make sure each account ID is linked to a GL account.

The file upload failed because it contains transactions that were not successfully posted in the bank's system. Contact your bank to correct the error and re-upload the file again.

The Status code in your bank statement file isn't 0 (zero) or Success.

Contact your financial institution to check the correct status of your transactions.

The file upload failed because the calculated Closing Balance does not match the Closing Amount in the file. Contact your bank to correct the error, and re-upload the file again.

The opening balance (tag :60:) plus the statement amount (tag :61:) doesn't equal the closing balance (tag :62:).

Contact your financial institution for help.

The file could not be imported because the currency code [code] for an account does not match the currency code for the same account in NetSuite.

The account currency on your bank statement file doesn't match the mapped account's currency in NetSuite.

Check which currency should be used. For details on checking account information in NetSuite, Viewing the Chart of Accounts.

To fix the bank statement file, contact your financial institution.

The file upload failed because the file contains an incorrect data at line [number] for [tag :X:]. Amounts must include only one comma or period as a decimal separator. Contact your bank to correct the error, and re-upload the file again.

Multiple commas were found.

To remove extra decimal separators, contact your financial institution.

The file could not be imported, because the account [name] in the file does not match an account in NetSuite.

The Transaction Account (tag :25:) value in your MT940 file is missing from your format profile.

Check the account mapping in your format profile. Under the Account Linking subtab, make sure each account ID is linked to a GL account.

The file upload failed because the file contains an incorrect Amount Indicator. Expected Amount Indicator values are C, D, RC, or RD. Contact your bank to correct the error, and re-upload the file again.

The Amount Indicator has an unknown value.

The Amount Indicator must be C, D, RC, or RD. To fix the file, contact your financial institution.

The file upload failed because the file contains an incorrect date format. MT940 statement files use the <YYMMDD> date format. Contact your bank to correct the error, and re-upload the file again.

Wrong date format for tag :61:.

Check your bank statement file and make sure the date in tag :61: is in YYMMDD format. Contact your financial institution for help.

The file upload failed because the file contains an incorrect booking date format. MT940 statement files use the <MMDD> date format in the Booking Date field. Contact your bank to correct the error, and re-upload the file again.

Wrong booking date format.

Check your bank statement file and make sure the booking date in tag :61: is in MMDD format. Contact your financial institution for help.

The file upload failed because it contains an unknown transaction code [XYZ]. Update you format profile to add non-Swift transactions codes and re-upload the file again.

There's an unknown transaction code.

Contact your financial institution for help.

The file upload failed because the file contains an incorrect date format. BAI2 Statement files use the <YYMMDD> date format. Contact your bank to correct the error, and re-upload the file again.

Wrong date format.

Contact your financial institution for help.

The file upload failed because the file contains an incorrect Funds Type. Expected Funds Type values are 0, 1, 2, S, V, D, or Z. Contact your bank to correct the error, and re-upload the file again.

Wrong Funds Type value

Contact your financial institution for help.

The file upload failed because it contains multiple file header records. The file must only have one File Header. Contact your bank to correct the error, and re-upload the file again.

The statement file has multiple file headers.

Contact your financial institution for help.

The file upload failed because the total sum of transactions imported per account does not match the Account Control Total amount in the file. Contact your bank to correct the error, and re-upload the file again.

The Account Control Total value in the Account Trailer (49) record is wrong.

Contact your financial institution for help.

The file upload failed because the total number of records per account does not match with the Account Trailer Control in the file. Contact your bank to correct the error, and re-upload the file again.

The number of records in the Account Trailer record is wrong.

Contact your financial institution for help.

The file upload failed because the total sum of transactions per group does not match the Group Control Total in the file. Contact your bank to correct the error, and re-upload the file again.

The Group Control Total value in the Group Trailer record is wrong.

Contact your financial institution for help.

The file upload failed because the total number of Account Records per group does not match the Number of Accounts in the Group Account Trailer record in the file. Contact your bank to correct the error, and re-upload the file again.

The Number of Accounts value in the Group Trailer record is wrong.

Contact your financial institution for help.

The file upload failed because the total number of records per group does not match with the Group Trailer Control in the file. Contact your bank to correct the error, and re-upload the file again.

The number of records in the Group Trailer record is wrong.

Contact your financial institution for help.

The file upload failed because the total sum of transactions imported does not match the File Control Total amount in the file. Contact your bank to correct the error, and re-upload the file again.

The File Control Total value is wrong.

Contact your financial institution for help.

The file upload failed because the total number of Group Headers in the file does not match the Number of Groups in the File Trailer record. Contact your bank to correct the error, and re-upload the file again.

The Number of Groups value in the File Trailer is wrong.

Contact your financial institution for help.

The file upload failed because the total number of records in the file does not match the total number of records in the File Trailer record. Contact your bank to correct the error, and re-upload the file again.

The number of records in the File Trailer is wrong.

Contact your financial institution for help.

The file upload failed because it contains an extra Record 88 with no preceding record. Contact your bank to correct the error, and re-upload the file again.

The Continuation (88) record doesn't have a preceding record type.

Contact your financial institution for help.

The file upload failed because the file contains extra fields in one or more records. Contact your bank to correct the error, and re-upload the file again.

The record has extra fields.

For example, the (49) record only needs 3 fields but the statement file has extra field values.

Contact your financial institution for help.

The file upload failed because it contains one or more incorrectly formatted record. Every record in the file must end with a forward slash. Contact your bank to correct the error and re-upload the file again.

The records or lines in the file don't end with a forward slash.

Contact your financial institution for help.

The file upload failed because the Customer Account Number field is missing. A complete BAI2 file must contain Records 01, 02, 03, 16, 88, 49, 98, or 99 including all the mandatory fields. Contact your bank to correct the error, and re-upload the file again.

A required field is missing.

Contact your financial institution for help.

The file upload failed because the Amount field has an invalid field data: "100.00". Contact your bank to correct the file, and re-upload it again.

A field has invalid data.

For example, the Amount field expects a number, but the field has a different data type.

Contact your financial institution for help.

The file upload failed because the record code is invalid. Expected record code values for BAI2 files are 01, 02, 03, 16, 88, 49, 98, or 99. Contact your bank to correct the error, and re-upload the file again.

The record code is not valid.

Contact your financial institution for help.

The file upload failed because the record code is missing. A complete BAI2 file must contain Records 01, 02, 03, 16, 88, 49, 98, or 99. Contact your bank to correct the error, and re-upload the file again.

One of the records in the file doesn't have a record code.

Contact your financial institution for help.

The file upload failed because the file is blank. Contact your bank to correct the error, and re-upload the file again.

The file is empty.

Contact your financial institution for help.

The file upload failed because file format is incorrect. Contact your bank to correct the error, and re-upload the file again.

The file format is wrong.

Contact your financial institution for help.

The file upload failed because the file is incomplete. A complete BAI2 file must contain Records 01, 02, 03, 16, 88, 49, 98, or 99. Contact your bank to correct the error, and re-upload the file again.

The file is missing one or more records.

Contact your financial institution for help.

The file upload failed because of an internal error. Please contact support if the problem persists.

An internal or unexpected error occurred.

Contact Support for help.

The file upload failed because of <error> error at line number <line number>. If you have repeatedly received this error message, contact customer support.

An internal or unexpected error occurred.

Contact Support for help.

The file upload failed because one of the records in the file has missing fields. Contact your bank to correct the file, and re-upload it again.

One of the records has missing fields.

Contact your financial institution for help.

The file upload failed because the parser has not completed processing a previous record due to an error. A new record cannot be processed. Contact customer support.

Can't create a new record because of a previous error.

Contact Support for help.

The file upload failed because the Group Header and Account Identifier are missing. A complete BAI2 file must contain Records 01, 02, 03, 16, 88, 49, 98, or 99. Contact your bank to correct the error, and re-upload the file again.

Can't import the bank statement file because the Group Header and Account Identifier are missing.

Contact your financial institution for help.

The file upload failed because the Group Header, Account Identifier, and Transaction Detail are missing. A complete BAI2 file must contain Records 01, 02, 03, 16, 88, 49, 98, or 99. Contact your bank to correct the error, and re-upload the file again.

Can't import the bank statement file because the Group Header, Account Identifier, and Transaction Detail are missing.

Contact your financial institution for help.

The file upload failed because it does not conform with the valid CAMT.053.001.02 XML Format. Contact your bank to correct the error, and re-upload the file again.

The uploaded XML failed the CAMT.053.001.02 XSD validation.

Contact your financial institution for help.

The file mapping must begin with “<BkToCstmrStmt> <Stmt>” to import the transactions from the file to NetSuite.

Incorrect parser configuration.

On the format profile record, under Parser Configuration subtab, check the File Mapping value of your NetSuite mapped fields. All file mapping must begin with <BkToCstmrStmt> <Stmt>.

Each tag used in the file mapping must be enclosed in “<” and “>”, and must be separated by a space. For example, <BkToCstmrStmt> <Stmt> <Acct> <Id> <IBAN>.

The file mapping values in the Parser Configuration subtab of your format profile don't follow the correct tag format.

Tags must be in this format:

• Enclosed in angle brackets ( < > )

• Separated by a single space

The configurations for the following field(s) will be removed:

<NetSuite field names>

Click OK to restore the default file mapping or click Cancel to manually configure the file mapping for the affected fields.

All mappings for a specific field in the Parser Configuration subtab are deleted.

Check your parser configuration and make sure all standard NetSuite fields are present.

For the list of default mapping values for CAMT.053 parser, see Configuring CAMT.053 Parser.

The Credit/Debit value is sourced from the statement file to determine the GL Impact of the transaction. Click OK to set the value to N/A and use the indicator in the file or click Cancel to override the amount indicator in the file.

The Credit/Debit field in the Transaction Code Mapping subtab is set to something other than N/A.

Check your parser configuration.

The bank statement file contains {number} transactions that are not yet posted or booked in your bank account. Only booked or posted transactions are imported.

The status of the imported transaction isn't set to Book.

Contact your financial institution for help.

The file mapping {file mapping value} for NetSuite Field {NetSuite field value} already exists. Please enter a unique file mapping path.

Your parser configuration has duplicate file mapping rows.

On your format profile, under the Parser Configuration subtab, remove any duplicate file mapping rows.

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.

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.

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.