This page lists errors that can be encountered upon import of the statement file.

1. Undefined statements upon import (Multi-Statement)

A user my encounter following screen upon import:

This means that the file contains a statement from a bank account that does not match with any of the Multiple Statement - Identifiers on your bank account configurations.

• In other words, none of your bank account configurations does contain the identifier that defines the bank account.

• Simplest way to retrieve the identifier is to open the “undefined” link and copy the identifier from the name - identifier is all the characters until the underscore (“_”) sign as seen below:

This value then needs to be copied and updated on the Bank Account Configuration in the MULTIPLE STATEMENT - IDENTIFIER field:

2. Script Error: TypeError: Cannot find function getDate in object NaN.

The reason for this error is that our solution was not able to identify the dates of each statement line.

• If the Bank account is configured as CSV configuration, the Date column was not mapped correctly from the CSV file.

• Please note that columns are counted from the left side, starting from “0” position, meaning if the first CSV column is the date column, you need to set in the bank account configuration value “0” in the respective field.

3. Empty statement

If the statement is imported, but does not contain any lines, the reason could be one of the following:

• The statement is configured as CSV file, please verify the correct column mapping and try a different CSV DELIMITER

• The statement is configured as MT940 file, please check if the preference COUNTERPARTY MANDATORY ( MT940 ) is checked and disable the preference

• The statement file indeed does not contain for this bank account (within the dates) any transactions, please verify in the bank administration

4. Scheduled file import did not generate any bank statement

If you have a scheduled import of the bank statement files setup in your account and the files have been provided but were not processed into the actual bank statements, it is important to test whether such file can be indeed imported.

• The step that should be taken is to import the file manually via Transactions>Bank Reconciliation>Import statement.

• Choose the multiple statement import form on the right-hand side of the page and select the record that holds the bank account configurations for bank accounts, from which are the entries in the file.

5. SSS_INVALID_SRCH_COL An nlobjSearchColumn contains an invalid column, or is not in proper syntax: ponumber.

This error occurs when field “PO #” is added as matching parameter. By default, NetSuite populates internal ID: ponumber. The field (to be found in Sales Order) has actually Internal ID: otherrefnum. User therefore needs to manually change the TRANSACTION FIELD ID from PONUMBER to OTHERREFNUM.

6. SSS_INVALID_SRCH_FILTER An nlobjSearchFilter contains invalid search criteria: custrecord_bs_ep_bankstatement.

This error usually occurs when in accounts where Bank Reconciliation app has been installed recently. User needs to add an additional field as per the following article: Netsuite electronic payment batch (additional field)