Bank Import Error Codes (Reference)

This topic lists all standardized error codes and scenarios for bank import processes, grouped by error type and file format. Standardized error messages only appear in NetSuite for automatic imports if the required plug-in updates have been made. If you're a plug-in author, see the next section for update instructions.

Note:

Standardized error codes apply only to custom or third-party plug-ins configured to use them. The Bank Feeds SuiteApp does not currently support standardized error codes. Support is targeted for March 10, 2026.

Standardized codes for parser-level and import-level errors are automatically available for manual imports that use default BAI2 and CSV parsers, with no parser plug-in updates required. If multiple issues are found in a file, these errors are captured and displayed on the Banking Import History page. Errors are often shown with line number and position to support more precise troubleshooting.

Plug-in Author Action Required

To ensure that standardized error messages for automatic bank import processes appear in NetSuite, update your custom or third-party plug-ins accordingly. Without these updates, only free-text or generic error messages appear. The following plug-in updates are required.

Adding the errorCode field in your connectivity plug-in for account errors. See Updating Connectivity Plug-ins for Account Error Codes.
Implementing the addError API in your parser plug-in for parser-level errors. See Updating Parser Plug-ins for Parser Error Codes.
Adding import-level standardized error handling in parser and connectivity plug-ins. See Updating Parser Plug-ins for Import Error Codes and Updating Connectivity Plug-ins for Import Error Codes.

After making these updates, update your plug-in's code so that each error scenario you handle returns or sets the correct error code from this topic.

If you see a free-text failure reason in the UI, a warning displays (visible with the Financial Institution Records permission with "Edit" access). This warning is a signal that the plug-in hasn't been updated for error code support. Free-text failure reasons are targeted for removal in a future release, but plug-in updates for error code support are strongly encouraged as soon as possible.

Error Code Structure

All error codes follow this pattern: XYYYNNNNZZ

Each part of the code provides specific information about the error:

X - Error scope/type:
- 0: File/import-level error
- 1: Record-level error (transaction, balance, and so on)
- 2: Account-level error
YYY - Data format:
- 000: Format-agnostic
- 010: CSV (standard template)
- 020: BAI2
- 030: CAMT053
NNNN - Specific numeric error identifier
ZZ - Code variant or subtype (context-specific)

This format helps you quickly determine the type, context, and specifics of any error reported in a bank import process.

Import-Level Errors (Format-Agnostic)

Error Code	Error Scenario / Notes	Error Message
0000000000	Issue occurred that can't be expressed with any available error code	Unexpected error - For manual imports, please try again. For automatic imports, wait for the next scheduled import or contact support if the issue continues (Error 0000000000).
0000000001	Connectivity error	Connection issue - Your financial institution couldn't be connected. If you have the administrator role, refer to the Execution Log on the Plug-In Implementation page for details. Otherwise, contact your administrator (Error 0000000001).
0000000002	Data retrieval issue	Data retrieval issue - We connected but couldn't retrieve transaction data. If you have the administrator role, go to the Execution Log on the Plug-In Implementation page for details. Otherwise, contact your administrator (Error 0000000002).
0000000100	Inactive Bank Statement Parser plug-in	Inactive Bank Statement Parser Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000100).
0000000101	Inactive Financial Institution Parser plug-in	Inactive Financial Institution Parser Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000101).
0000000102	Inactive Financial Institution Connectivity plug-in	Inactive Financial Institution Connectivity Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000102).
0000000200	Number of transactions exceeds system processing limit	Transaction limit exceeded - Remaining transactions will be imported at the next scheduled import (Error 0000000200).
0000000300	Invalid input from Financial Institution Connectivity plug-in	Invalid input from Financial Institution Connectivity Plug-in - If you have the administrator role, contact the plug-in author to modify the plug-in accordingly. Otherwise, contact your administrator for help (Error 0000000300).
0000200000	All accounts fail	Account data unavailable - Your financial institution was unable to provide data for the requested accounts. Review and resolve the account-specific errors, if available. Otherwise, contact your administrator for help (Error 0000200000).
0000300000	Import took too long and was automatically stopped	Import time limit exceeded - For bank connections, wait for the next scheduled import. For file imports, try reimporting. Contact support if needed (Error 0000300000).
0000400000	Problem connecting to server during sFTP	Secure File Transfer Protocol (SFTP) connection unsuccessful - If you have the administrator role, review and configure your SFTP configuration to ensure values are valid. Otherwise, contact your administrator for help (Error 0000400000).
0000400001	Timeout exceeded while establishing SFTP connection	Secure File Transfer Protocol (SFTP) connection timeout - Try again later (Error 0000400001).
0000400002	Server specified in sFTP configuration didn't contain any files	No files in Secure File Transfer Protocol (SFTP) server - If you have the administrator role, review your SFTP configuration and try again later. Otherwise, contact your administrator or financial institution if needed (Error 0000400002).
0000400003	File matching sFTP configuration has already been uploaded	File already uploaded - If you have the administrator role, review your Secure File Transfer Protocol (SFTP) configuration to ensure the correct file is being uploaded. Otherwise, contact your administrator for assistance (Error 0000400003).
0000400004	File name in sFTP configuration didn't match any bank statement file names	File name not found - The file name in the Secure File Transfer Protocol (SFTP) configuration did not match any bank statement file names. If you don't have the administrator role, contact your administrator for assistance (Error 0000400004).
0000500000	Retry initiated with no error code or failure reason specified	Unexpected error - We'll automatically start another import for you within the next few hours. If the issue continues, check the Execution Log on the Plug-In Implementation page. If needed, contact support for help (Error 0000500000).

Error Code

Error Scenario / Notes

Error Message

0000000000

Issue occurred that can't be expressed with any available error code

Unexpected error - For manual imports, please try again. For automatic imports, wait for the next scheduled import or contact support if the issue continues (Error 0000000000).

0000000001

Connectivity error

Connection issue - Your financial institution couldn't be connected. If you have the administrator role, refer to the Execution Log on the Plug-In Implementation page for details. Otherwise, contact your administrator (Error 0000000001).

0000000002

Data retrieval issue

Data retrieval issue - We connected but couldn't retrieve transaction data. If you have the administrator role, go to the Execution Log on the Plug-In Implementation page for details. Otherwise, contact your administrator (Error 0000000002).

0000000100

Inactive Bank Statement Parser plug-in

Inactive Bank Statement Parser Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000100).

0000000101

Inactive Financial Institution Parser plug-in

Inactive Financial Institution Parser Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000101).

0000000102

Inactive Financial Institution Connectivity plug-in

Inactive Financial Institution Connectivity Plug-in - If you have the administrator role, reactivate the plug-in or modify the format profile to use an active plug-in. Otherwise, contact your administrator for help (Error 0000000102).

0000000200

Number of transactions exceeds system processing limit

Transaction limit exceeded - Remaining transactions will be imported at the next scheduled import (Error 0000000200).

0000000300

Invalid input from Financial Institution Connectivity plug-in

Invalid input from Financial Institution Connectivity Plug-in - If you have the administrator role, contact the plug-in author to modify the plug-in accordingly. Otherwise, contact your administrator for help (Error 0000000300).

0000200000

All accounts fail

Account data unavailable - Your financial institution was unable to provide data for the requested accounts. Review and resolve the account-specific errors, if available. Otherwise, contact your administrator for help (Error 0000200000).

0000300000

Import took too long and was automatically stopped

Import time limit exceeded - For bank connections, wait for the next scheduled import. For file imports, try reimporting. Contact support if needed (Error 0000300000).

0000400000

Problem connecting to server during sFTP

Secure File Transfer Protocol (SFTP) connection unsuccessful - If you have the administrator role, review and configure your SFTP configuration to ensure values are valid. Otherwise, contact your administrator for help (Error 0000400000).

0000400001

Timeout exceeded while establishing SFTP connection

Secure File Transfer Protocol (SFTP) connection timeout - Try again later (Error 0000400001).

0000400002

Server specified in sFTP configuration didn't contain any files

No files in Secure File Transfer Protocol (SFTP) server - If you have the administrator role, review your SFTP configuration and try again later. Otherwise, contact your administrator or financial institution if needed (Error 0000400002).

0000400003

File matching sFTP configuration has already been uploaded

File already uploaded - If you have the administrator role, review your Secure File Transfer Protocol (SFTP) configuration to ensure the correct file is being uploaded. Otherwise, contact your administrator for assistance (Error 0000400003).

0000400004

File name in sFTP configuration didn't match any bank statement file names

File name not found - The file name in the Secure File Transfer Protocol (SFTP) configuration did not match any bank statement file names. If you don't have the administrator role, contact your administrator for assistance (Error 0000400004).

0000500000

Retry initiated with no error code or failure reason specified

Unexpected error - We'll automatically start another import for you within the next few hours. If the issue continues, check the Execution Log on the Plug-In Implementation page. If needed, contact support for help (Error 0000500000).

Account-Level Errors (Format-Agnostic)

Error Code	Error Scenario	Error Message
2000000000	Unknown error that is account-specific	Unexpected account-level error - Wait until the next scheduled import to see if the issue resolves, or contact NetSuite Support for help (Error 2000000000).
2000000100	Account locked	Account locked - Access to your financial institution account has been locked, likely due to too many incorrect login attempts through NetSuite. To regain access, go to your financial institution's portal. If needed, contact your financial institution for help (Error 2000000100).
2000000200	Incorrect credentials	Incorrect credentials - The login credentials for your financial institution may have recently changed. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and provide your new credentials. Otherwise, contact your administrator for help (Error 2000000200).
2000000300	Credentials expired	Expired credentials - Go to your financial institution's portal to update your credentials. Then, if you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and provide your new credentials. Otherwise, contact your administrator for help (Error 2000000300).
2000000400	User action required with bank	Action needed with financial institution - Go to your financial institution's portal and complete any required steps. Then, if you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution. Otherwise, contact your administrator for help (Error 2000000400).
2000000500	Consent revoked	Consent revoked - The connection to your account was interrupted. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile. First, remove NetSuite's access to your account and save the format profile. Then, restore access and save the format profile again. If you're not an administrator, contact your administrator for help (Error 2000000500).
2000000600	Consent expired	Consent expired - Your last authorization session expired. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution. Otherwise, contact your administrator for help (Error 2000000600).
2000000700	MFA required	MFA needed - Two-factor authentication is needed. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution, providing the required authentication code. Otherwise, contact your administrator for help (Error 2000000700).
2000000900	Bank isn't supported at all (or no longer supported)	Financial institution not supported - If you have the administrator role, go to the Connectivity Configuration subtab in each relevant format profile, remove access to all accounts for this financial institution, and then save. Otherwise, contact your administrator for help (Error 2000000900).
2000001200	Failed to initiate refresh for account due to an unknown reason	Account refresh request failed - We couldn't refresh some accounts due to an unexpected error. Try again or wait for the next scheduled import. If the issue continues, contact NetSuite Support for help (Error 2000001200).
2000001201	Failure to refresh account data in 30-minute timeout window	Account refresh timed out - The account couldn't be refreshed within 30 minutes. Try again later or wait for the next scheduled import (Error 2000001201).

Error Code

Error Scenario

Error Message

2000000000

Unknown error that is account-specific

Unexpected account-level error - Wait until the next scheduled import to see if the issue resolves, or contact NetSuite Support for help (Error 2000000000).

2000000100

Account locked

Account locked - Access to your financial institution account has been locked, likely due to too many incorrect login attempts through NetSuite. To regain access, go to your financial institution's portal. If needed, contact your financial institution for help (Error 2000000100).

2000000200

Incorrect credentials

Incorrect credentials - The login credentials for your financial institution may have recently changed. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and provide your new credentials. Otherwise, contact your administrator for help (Error 2000000200).

2000000300

Credentials expired

Expired credentials - Go to your financial institution's portal to update your credentials. Then, if you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and provide your new credentials. Otherwise, contact your administrator for help (Error 2000000300).

2000000400

User action required with bank

Action needed with financial institution - Go to your financial institution's portal and complete any required steps. Then, if you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution. Otherwise, contact your administrator for help (Error 2000000400).

2000000500

Consent revoked

Consent revoked - The connection to your account was interrupted. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile. First, remove NetSuite's access to your account and save the format profile. Then, restore access and save the format profile again. If you're not an administrator, contact your administrator for help (Error 2000000500).

2000000600

Consent expired

Consent expired - Your last authorization session expired. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution. Otherwise, contact your administrator for help (Error 2000000600).

2000000700

MFA required

MFA needed - Two-factor authentication is needed. If you have the administrator role, go to the Connectivity Configuration subtab in the appropriate format profile and re-log into your financial institution, providing the required authentication code. Otherwise, contact your administrator for help (Error 2000000700).

2000000900

Bank isn't supported at all (or no longer supported)

Financial institution not supported - If you have the administrator role, go to the Connectivity Configuration subtab in each relevant format profile, remove access to all accounts for this financial institution, and then save. Otherwise, contact your administrator for help (Error 2000000900).

2000001200

Failed to initiate refresh for account due to an unknown reason

Account refresh request failed - We couldn't refresh some accounts due to an unexpected error. Try again or wait for the next scheduled import. If the issue continues, contact NetSuite Support for help (Error 2000001200).

2000001201

Failure to refresh account data in 30-minute timeout window

Account refresh timed out - The account couldn't be refreshed within 30 minutes. Try again later or wait for the next scheduled import (Error 2000001201).

Parser or Record-Level Errors

General Parsing or Validation Errors

Error Code	Error Scenario	Error Message
1000000000	Unknown parse error not covered by any other error codes	Unexpected parsing error - Fix any issues in your file and try again. If the problem continues, contact NetSuite Support for help (Error 1000000000).
1000000100	Invalid date given (for example, Feb 30th)	Invalid date - Use valid transaction dates that exist. For example, 2/30/2024 isn't a real date (Error 1000000100).
1000000200	Incorrect date format - MM/DD/YYYY required	Incorrect date format - Use transaction dates in MM/DD/YYYY format (Error 1000000200).
1000000201	Incorrect date format - YYMMDD required	Incorrect date format - Use transaction dates in YYMMDD format (Error 1000000201).
1000000202	Incorrect date format - YYYY-MM-DD required (CAMT file)	Incorrect date format in CAMT file - Dates must use the format YYYY-MM-DD (year-month-day). Request a corrected file from your provider (Error 1000000202).
1000000203	Incorrect date and time format in CAMT file	Incorrect date and time format in CAMT file - Dates and times must use the format YYYY-MM-DD, followed by 'T', the time, and the time zone if required. For example, 2024-06-11T14:35:20Z. Request a corrected file from your provider (Error 1000000203).
1000000204	Invalid date and time format in OFX file	Incorrect date and time format in OFX file - Dates must use the format yyyyMMdd. Dates and times must use the format yyyyMMddHHmmss (Error 1000000204).
1000000300	Incorrect number format	Incorrect number format - Use the number format 1000000.00. Amount can't include currency symbols or commas as decimal separators (Error 1000000300).
1000000400	Insufficient number of fields	Insufficient number of fields - Make sure lines contain enough required fields for a transaction. Request a corrected file from your provider if needed (Error 1000000400).
1000000401	Missing mandatory field - Amount	Missing mandatory field - Transaction amount needs to be included (Error 1000000401).
1000000402	Missing mandatory field - Date	Missing mandatory field - Transaction date needs to be included (Error 1000000402).
1000000403	Missing mandatory field - Transaction Type	Missing mandatory field - Transaction type needs to be included (Error 1000000403).
1000000404	Missing mandatory field - Account	Missing mandatory field - Account needs to be included (Error 1000000404).
1000000405	Currency missing in CAMT file	Currency missing in CAMT file - Request a corrected file from your provider with the currency field filled in (Error 1000000405).
1000000406	Balance amount missing in CAMT file	Balance amount missing in CAMT file - Request a corrected file from your provider with the balance amount included (Error 1000000406).
1000000500	Invalid transaction type	Invalid transaction type - Use valid transaction types: ACH, Check, Credit, Debit, Deposit, Fee, Interest, Payment, Transfer, or Other (Error 1000000500).
1000000501	Invalid transaction type for BAI2 file	Invalid transaction type for BAI2 - Use a valid three-digit numeric transaction type code in the file. Contact your provider for a corrected file if needed (Error 1000000501).
1000000600	Unmapped account identifier	Unmapped account identifier - Map all account identifiers in the file to known accounts (Error 1000000600).
1000000700	Invalid currency	Invalid currency - Use a valid ISO 4217 currency code enabled in your account (Error 1000000700).
1000000900	Length of field value is too long	Field value too long - Make sure not to exceed the character length in fields (Error 1000000900).
1000001001	Record count doesn't match declared value in BAI2 file	BAI2 record count mismatch - Ask your provider to regenerate the file so the declared record counts in the account, group, or file trailer match the actual number of records in each section (Error 1000001001).
1000001002	Control total mismatch in BAI2 file	BAI2 control total mismatch - Ask your provider to reconcile the control total in the account, group, or file trailer so it matches the sum of the actual record values in each section (Error 1000001002).
1000001100	File ends before it's properly closed	File incomplete - Ask your provider to resend the complete file (Error 1000001100).
1000001200	Quotes not closed in CSV file	Unclosed quotes in CSV file - Check for and close any open quote marks in your file (Error 1000001200).
1000001300	Invalid credit or debit indicator in CAMT file	Invalid credit or debit indicator in CAMT file - Request a corrected file from your provider with a supported credit or debit indicator (Error 1000001300).
1000001400	Invalid status indicator in CAMT file	Invalid processing state of a transaction in CAMT file - Request a corrected file from your provider with a supported entry status code (Error 1000001400).
1000001500	Invalid balance type in CAMT file	Invalid balance type code in CAMT file - Request a corrected file from your provider with a supported balance type code (Error 1000001500).
1000001600	Missing closing balance in statement	Closing balance for statement missing in CAMT file - Request a corrected file from your provider with the closing balance included in the statement section (Error 1000001600).
1000001700	Unknown record type - String following !Type is not recognized (QIF)	Unknown record type in QIF file - Only supported record types are permitted. These include Class, Cat, Memorized, Prices, Budget, InvItem, Template, Security, Payee, Bill, Bank, Cash, CCard, Oth A, Oth L, Invoice, Tax, and Invst. Request a new file from your provider (Error 1000001700).
1000001800	Unknown command - String following ! is not recognized (QIF)	Unknown command in QIF file - Only supported commands are permitted, which include "Type," "Account," "Option," and "Clear." Request a new file from your provider (Error 1000001800).
1000001900	Unknown category (QIF)	Unknown category in QIF file - Only supported categories are permitted, which include Expense (E) and Income (I). Request a new file from your provider (Error 1000001900).
1000002000	End of record found without a header - No Header found for corresponding ^ (QIF)	Record end missing header in QIF file - Each end of a record should have a corresponding header. Request a new file from your provider (Error 1000002000).

Error Code

Error Scenario

Error Message

1000000000

Unknown parse error not covered by any other error codes

Unexpected parsing error - Fix any issues in your file and try again. If the problem continues, contact NetSuite Support for help (Error 1000000000).

1000000100

Invalid date given (for example, Feb 30th)

Invalid date - Use valid transaction dates that exist. For example, 2/30/2024 isn't a real date (Error 1000000100).

1000000200

Incorrect date format - MM/DD/YYYY required

Incorrect date format - Use transaction dates in MM/DD/YYYY format (Error 1000000200).

1000000201

Incorrect date format - YYMMDD required

Incorrect date format - Use transaction dates in YYMMDD format (Error 1000000201).

1000000202

Incorrect date format - YYYY-MM-DD required (CAMT file)

Incorrect date format in CAMT file - Dates must use the format YYYY-MM-DD (year-month-day). Request a corrected file from your provider (Error 1000000202).

1000000203

Incorrect date and time format in CAMT file

Incorrect date and time format in CAMT file - Dates and times must use the format YYYY-MM-DD, followed by 'T', the time, and the time zone if required. For example, 2024-06-11T14:35:20Z. Request a corrected file from your provider (Error 1000000203).

1000000204

Invalid date and time format in OFX file

Incorrect date and time format in OFX file - Dates must use the format yyyyMMdd. Dates and times must use the format yyyyMMddHHmmss (Error 1000000204).

1000000300

Incorrect number format

Incorrect number format - Use the number format 1000000.00. Amount can't include currency symbols or commas as decimal separators (Error 1000000300).

1000000400

Insufficient number of fields

Insufficient number of fields - Make sure lines contain enough required fields for a transaction. Request a corrected file from your provider if needed (Error 1000000400).

1000000401

Missing mandatory field - Amount

Missing mandatory field - Transaction amount needs to be included (Error 1000000401).

1000000402

Missing mandatory field - Date

Missing mandatory field - Transaction date needs to be included (Error 1000000402).

1000000403

Missing mandatory field - Transaction Type

Missing mandatory field - Transaction type needs to be included (Error 1000000403).

1000000404

Missing mandatory field - Account

Missing mandatory field - Account needs to be included (Error 1000000404).

1000000405

Currency missing in CAMT file

Currency missing in CAMT file - Request a corrected file from your provider with the currency field filled in (Error 1000000405).

1000000406

Balance amount missing in CAMT file

Balance amount missing in CAMT file - Request a corrected file from your provider with the balance amount included (Error 1000000406).

1000000500

Invalid transaction type

Invalid transaction type - Use valid transaction types: ACH, Check, Credit, Debit, Deposit, Fee, Interest, Payment, Transfer, or Other (Error 1000000500).

1000000501

Invalid transaction type for BAI2 file

Invalid transaction type for BAI2 - Use a valid three-digit numeric transaction type code in the file. Contact your provider for a corrected file if needed (Error 1000000501).

1000000600

Unmapped account identifier

Unmapped account identifier - Map all account identifiers in the file to known accounts (Error 1000000600).

1000000700

Invalid currency

Invalid currency - Use a valid ISO 4217 currency code enabled in your account (Error 1000000700).

1000000900

Length of field value is too long

Field value too long - Make sure not to exceed the character length in fields (Error 1000000900).

1000001001

Record count doesn't match declared value in BAI2 file

BAI2 record count mismatch - Ask your provider to regenerate the file so the declared record counts in the account, group, or file trailer match the actual number of records in each section (Error 1000001001).

1000001002

Control total mismatch in BAI2 file

BAI2 control total mismatch - Ask your provider to reconcile the control total in the account, group, or file trailer so it matches the sum of the actual record values in each section (Error 1000001002).

1000001100

File ends before it's properly closed

File incomplete - Ask your provider to resend the complete file (Error 1000001100).

1000001200

Quotes not closed in CSV file

Unclosed quotes in CSV file - Check for and close any open quote marks in your file (Error 1000001200).

1000001300

Invalid credit or debit indicator in CAMT file

Invalid credit or debit indicator in CAMT file - Request a corrected file from your provider with a supported credit or debit indicator (Error 1000001300).

1000001400

Invalid status indicator in CAMT file

Invalid processing state of a transaction in CAMT file - Request a corrected file from your provider with a supported entry status code (Error 1000001400).

1000001500

Invalid balance type in CAMT file

Invalid balance type code in CAMT file - Request a corrected file from your provider with a supported balance type code (Error 1000001500).

1000001600

Missing closing balance in statement

Closing balance for statement missing in CAMT file - Request a corrected file from your provider with the closing balance included in the statement section (Error 1000001600).

1000001700

Unknown record type - String following !Type is not recognized (QIF)

Unknown record type in QIF file - Only supported record types are permitted. These include Class, Cat, Memorized, Prices, Budget, InvItem, Template, Security, Payee, Bill, Bank, Cash, CCard, Oth A, Oth L, Invoice, Tax, and Invst. Request a new file from your provider (Error 1000001700).

1000001800

Unknown command - String following ! is not recognized (QIF)

Unknown command in QIF file - Only supported commands are permitted, which include "Type," "Account," "Option," and "Clear." Request a new file from your provider (Error 1000001800).

1000001900

Unknown category (QIF)

Unknown category in QIF file - Only supported categories are permitted, which include Expense (E) and Income (I). Request a new file from your provider (Error 1000001900).

1000002000

End of record found without a header - No Header found for corresponding ^ (QIF)

Record end missing header in QIF file - Each end of a record should have a corresponding header. Request a new file from your provider (Error 1000002000).

CSV-Specific Errors

Error Code	Error Scenario	Error Message
0010000000	Headers in CSV file don't follow CSV template	Invalid CSV header - Make sure headers match our CSV template (Error 0010000000).
0010000100	File format isn't CSV	Invalid CSV file format - Make sure the file follows our CSV template: ensure headers are correct, all columns match, and save as UTF-8 CSV (Error 0010000100).

Error Code

Error Scenario

Error Message

0010000000

Headers in CSV file don't follow CSV template

Invalid CSV header - Make sure headers match our CSV template (Error 0010000000).

0010000100

File format isn't CSV

Invalid CSV file format - Make sure the file follows our CSV template: ensure headers are correct, all columns match, and save as UTF-8 CSV (Error 0010000100).

BAI2-Specific Errors

Error Code	Error Scenario	Error Message
0020000101	Extra record before file header in BAI2 file	Extra record before file header in BAI2 file - Request a corrected file from your provider that starts with the 01 FileHeader record and follows the standard order. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000101).
0020000102	Transactions seen without corresponding Account Header	Transactions without account header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding account header for every set of transactions. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000102).
0020000103	Account Header seen without corresponding Group Header	Account header without group header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding group header for every account header. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000103).
0020000104	Group Header seen without corresponding File header	Group header without file header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding file header for every group header. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000104).
0020000201	Mismatched file header and trailer	File header and trailer mismatch in BAI2 file - Request a corrected file from your provider with a properly matched opening and closing line (Error 0020000201).
0020000202	Mismatched group header and trailer	Group header and trailer mismatch in BAI2 file - Request a corrected file from your provider with properly matched group headers and trailers (opening and closing lines) for each section (Error 0020000202).
0020000203	Mismatched account header and trailer	Account header and trailer mismatch in BAI2 file - Request a corrected file from your provider with properly matched account headers and trailers (opening and closing lines) in each section (Error 0020000203).
0020000301	Missing fields in file header	Missing mandatory field in file header in BAI2 file - Request a corrected file from your provider (Error 0020000301).
0020000302	Missing fields in group header	Missing mandatory field in group header in BAI2 file - Request a corrected file from your provider (Error 0020000302).
0020000303	Missing fields in account header	Missing mandatory field in account header in BAI2 file - Request a corrected file from your provider (Error 0020000303).
0020000304	Missing fields in file trailer	Missing mandatory field in file trailer in BAI2 file - Request a corrected file from your provider (Error 0020000304).
0020000305	Missing fields in group trailer	Missing mandatory field in group trailer in BAI2 file - Request a corrected file from your provider (Error 0020000305).
0020000306	Missing fields in account trailer	Missing mandatory field in account trailer in BAI2 file - Request a corrected file from your provider (Error 0020000306).
0020000400	Invalid number in headers or trailers	BAI2 number format error - Make sure number values contain only digits, commas, periods, or parentheses (for negatives). Contact your provider for a corrected file if needed (Error 0020000400).
0020000500	Invalid date in headers (must be YYMMDD)	BAI2 date format error - Make sure all dates in headers use the YYMMDD format. Contact your provider for a corrected file if needed (Error 0020000500).
0020000501	Invalid time in headers (must be in 24-hour HHMM format)	Invalid time format in headers in BAI2 file - Request a corrected file from your provider where time values in headers use the 24-hour HHMM format (Error 0020000501).
0020000502	Invalid As Of Date modifier (must be 0, 1, 2, or 3)	Invalid date modifier in headers in BAI2 file - Request a corrected file from your provider where the As Of Date modifier in headers is set to 0, 1, 2, or 3 (Error 0020000502).
0020000600	Wrong file format or version	BAI2 file version error - Only BAI2 (version 2) files are supported. Request one from your provider (Error 0020000600).
0020000700	Input file couldn't be read	BAI2 file read error - Obtain a fresh copy from your provider (Error 0020000700).
0020000800	Invalid currency code in non-transaction sections	BAI2 currency code error - Use a valid ISO currency code in non-transaction sections. Contact your provider for a corrected file if needed (Error 0020000800).
0020000900	Unsupported or unrecognized record type	BAI2 record type error - Only records starting with 01, 02, 03, 16, 49, 88, 98, or 99 are supported. Contact your provider for a corrected file (Error 0020000900).
0020001000	Invalid group status ID (must be 1-4)	Invalid group status ID in BAI2 file - Request a corrected file from your provider where the group status ID is set to 1, 2, 3, or 4 (Error 0020001000).
1000001001	Record count mismatch in BAI2 file	BAI2 record count mismatch - Ask your provider to regenerate the file so the declared record counts in the account, group, or file trailer match the actual number of records in each section (Error 1000001001).
1000001002	Control total mismatch in BAI2 file	BAI2 control total mismatch - Ask your provider to reconcile the control total in the account, group, or file trailer so it matches the sum of the actual record values in each section (Error 1000001002).

Error Code

Error Scenario

Error Message

0020000101

Extra record before file header in BAI2 file

Extra record before file header in BAI2 file - Request a corrected file from your provider that starts with the 01 FileHeader record and follows the standard order. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000101).

0020000102

Transactions seen without corresponding Account Header

Transactions without account header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding account header for every set of transactions. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000102).

0020000103

Account Header seen without corresponding Group Header

Account header without group header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding group header for every account header. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000103).

0020000104

Group Header seen without corresponding File header

Group header without file header in BAI2 file - Request a corrected file from your provider that follows the standard order and has a corresponding file header for every group header. The order should be 01 FileHeader > 02 GroupHeader > 03 AccountHeader > 16 Transactions > 49 AccountTrailer > 98 GroupTrailer > 99 FileTrailer (Error 0020000104).

0020000201

Mismatched file header and trailer

File header and trailer mismatch in BAI2 file - Request a corrected file from your provider with a properly matched opening and closing line (Error 0020000201).

0020000202

Mismatched group header and trailer

Group header and trailer mismatch in BAI2 file - Request a corrected file from your provider with properly matched group headers and trailers (opening and closing lines) for each section (Error 0020000202).

0020000203

Mismatched account header and trailer

Account header and trailer mismatch in BAI2 file - Request a corrected file from your provider with properly matched account headers and trailers (opening and closing lines) in each section (Error 0020000203).

0020000301

Missing fields in file header

Missing mandatory field in file header in BAI2 file - Request a corrected file from your provider (Error 0020000301).

0020000302

Missing fields in group header

Missing mandatory field in group header in BAI2 file - Request a corrected file from your provider (Error 0020000302).

0020000303

Missing fields in account header

Missing mandatory field in account header in BAI2 file - Request a corrected file from your provider (Error 0020000303).

0020000304

Missing fields in file trailer

Missing mandatory field in file trailer in BAI2 file - Request a corrected file from your provider (Error 0020000304).

0020000305

Missing fields in group trailer

Missing mandatory field in group trailer in BAI2 file - Request a corrected file from your provider (Error 0020000305).

0020000306

Missing fields in account trailer

Missing mandatory field in account trailer in BAI2 file - Request a corrected file from your provider (Error 0020000306).

0020000400

Invalid number in headers or trailers

BAI2 number format error - Make sure number values contain only digits, commas, periods, or parentheses (for negatives). Contact your provider for a corrected file if needed (Error 0020000400).

0020000500

Invalid date in headers (must be YYMMDD)

BAI2 date format error - Make sure all dates in headers use the YYMMDD format. Contact your provider for a corrected file if needed (Error 0020000500).

0020000501

Invalid time in headers (must be in 24-hour HHMM format)

Invalid time format in headers in BAI2 file - Request a corrected file from your provider where time values in headers use the 24-hour HHMM format (Error 0020000501).

0020000502

Invalid As Of Date modifier (must be 0, 1, 2, or 3)

Invalid date modifier in headers in BAI2 file - Request a corrected file from your provider where the As Of Date modifier in headers is set to 0, 1, 2, or 3 (Error 0020000502).

0020000600

Wrong file format or version

BAI2 file version error - Only BAI2 (version 2) files are supported. Request one from your provider (Error 0020000600).

0020000700

Input file couldn't be read

BAI2 file read error - Obtain a fresh copy from your provider (Error 0020000700).

0020000800

Invalid currency code in non-transaction sections

BAI2 currency code error - Use a valid ISO currency code in non-transaction sections. Contact your provider for a corrected file if needed (Error 0020000800).

0020000900

Unsupported or unrecognized record type

BAI2 record type error - Only records starting with 01, 02, 03, 16, 49, 88, 98, or 99 are supported. Contact your provider for a corrected file (Error 0020000900).

0020001000

Invalid group status ID (must be 1-4)

Invalid group status ID in BAI2 file - Request a corrected file from your provider where the group status ID is set to 1, 2, 3, or 4 (Error 0020001000).

1000001001

Record count mismatch in BAI2 file

1000001002

Control total mismatch in BAI2 file

CAMT-Specific Errors

Error Code	Error Scenario	Error Message
0030000000	XML structure error	Invalid XML format in CAMT file - Request a corrected file from your provider (Error 0030000000).
0030000100	Invalid number of group headers	Invalid number of group headers in CAMT file - Request a corrected file from your provider with only one group header (Error 0030000100).
0030000200	Group header appears after statement	Group header appears after statement in CAMT file - Request a corrected file from your provider with the group header before the statement section (Error 0030000200).
0030000300	Missing or invalid creation date time in group header	Missing or invalid creation date and time in CAMT file - Request a corrected file from your provider with a valid creation date and time (Error 0030000300).
0030000400	No statement found	No statement found in CAMT file - Request a corrected file from your provider with a statement section included (Error 0030000400).
0030000500	Unmapped IBAN number	Missing or unmapped IBAN number in CAMT file - The accounts in your imported file must map to accounts in NetSuite using their IBAN numbers. Request a corrected file from your provider with correctly mapped IBAN numbers (Error 0030000500).
0030000600	Missing account in statement	Missing account in statement of CAMT file - Request a corrected file from your provider with an account in the statement section (Error 0030000600).

Error Code

Error Scenario

Error Message

0030000000

XML structure error

Invalid XML format in CAMT file - Request a corrected file from your provider (Error 0030000000).

0030000100

Invalid number of group headers

Invalid number of group headers in CAMT file - Request a corrected file from your provider with only one group header (Error 0030000100).

0030000200

Group header appears after statement

Group header appears after statement in CAMT file - Request a corrected file from your provider with the group header before the statement section (Error 0030000200).

0030000300

Missing or invalid creation date time in group header

Missing or invalid creation date and time in CAMT file - Request a corrected file from your provider with a valid creation date and time (Error 0030000300).

0030000400

No statement found

No statement found in CAMT file - Request a corrected file from your provider with a statement section included (Error 0030000400).

0030000500

Unmapped IBAN number

Missing or unmapped IBAN number in CAMT file - The accounts in your imported file must map to accounts in NetSuite using their IBAN numbers. Request a corrected file from your provider with correctly mapped IBAN numbers (Error 0030000500).

0030000600

Missing account in statement

Missing account in statement of CAMT file - Request a corrected file from your provider with an account in the statement section (Error 0030000600).

QIF-Specific Errors

Error Code	Error Scenario	Error Message
1000001700	Unknown record type - String following !Type isn't recognized	Unknown record type in QIF file - Only supported record types are permitted. These include Class, Cat, Memorized, Prices, Budget, InvItem, Template, Security, Payee, Bill, Bank, Cash, CCard, Oth A, Oth L, Invoice, Tax, and Invst. Request a new file from your provider (Error 1000001700).
1000001800	Unknown command - String following ! isn't recognized	Unknown command in QIF file - Only supported commands are permitted, which include "Type," "Account," "Option," and "Clear." Request a new file from your provider (Error 1000001800).
1000001900	Unknown category	Unknown category in QIF file - Only supported categories are permitted, which include Expense (E) and Income (I). Request a new file from your provider (Error 1000001900).
1000002000	End of record found without header - No Header found for corresponding ^	Record end missing header in QIF file - Each end of a record should have a corresponding header. Request a new file from your provider (Error 1000002000).

Error Code

Error Scenario

Error Message

1000001700

Unknown record type - String following !Type isn't recognized

1000001800

Unknown command - String following ! isn't recognized

Unknown command in QIF file - Only supported commands are permitted, which include "Type," "Account," "Option," and "Clear." Request a new file from your provider (Error 1000001800).

1000001900

Unknown category

Unknown category in QIF file - Only supported categories are permitted, which include Expense (E) and Income (I). Request a new file from your provider (Error 1000001900).

1000002000

End of record found without header - No Header found for corresponding ^

Record end missing header in QIF file - Each end of a record should have a corresponding header. Request a new file from your provider (Error 1000002000).

This topic will be updated as additional error codes are added. For implementation support, see the links above or contact Oracle/NetSuite support.

General Notices