Switching from CSV to BAI2 Bank Feeds (NetSuite)

This set of instructions addresses issues some users have had with our legacy CSV bank feeds solution.

If you are an existing user of our legacy bank feeds solution, please refer to Migrating Bank Feeds (NetSuite) to switch to the new solution.

If you are looking for instructions for our legacy bank feeds solution, please refer to Enabling Legacy Bank Feeds (NetSuite). Our legacy bank feeds solution will no longer be supported as of the bank plugin version 2024.2.0.

There have been some reports from users of CSV-formatted Bank Feeds receiving the following error on the Banking Import History page:

"The file could not be parsed or imported, because of the following error:

Invalid footer lines configuration. Verify that the value in the Footer Lines field matches the number of footer rows in the CSV file."

If you are one of these users experiencing this on one or more bank accounts, please follow the instructions below to switch your Bank Feeds format from CSV to BAI2 for affected accounts to avoid any potential disruption to your month-end close.

Navigate to  Setup → Accounting → Financial Institution → List.

Click Edit on the Financial Institution that you have created previously when enabling bank feeds.

Select the Format Profile: Configuration tab and select Edit on the Format Profile you have created previously for the affected account.

On the Format Profile page, update the following fields:

Depending on whether your bank has additional bank transaction codes, we may revisit the Code Type Mapping tab later. You may safely skip any changes to this tab for now, and the Parser Configuration tab, which is only used for CSV-formatted Bank Feeds.

Click Save.

Select Track your status in the blue banner that appears, or go to Transactions → Bank → Banking Import History.

If the import was successful, you will see Completed under the Import Status column.

If the import fails, you will see Failed in the Import Status column. Select the plus (+) sign to expand the failure reason details.

If your Failure Reason states “is not one of your recognized bank transaction codes”, please proceed to the Code Type Mapping step.

If your Failure Reason is anything other than an unrecognized bank transaction code, please take a screenshot of the error message and email it to the Support team.

[email protected]

Return to Setup → Accounting → Financial Institution.

Click Edit on the Financial Institution that you have created previously.

Select the Format Profile: Configuration tab and select Edit on the Format Profile that had a failed import.

Click on the Code Type Mapping tab.

Fill in the following fields for the bank transaction code that was unrecognized:

The Bank Transaction Code will be the three-digit code from the error message seen on the Banking Import History page.

Fill in Description with something that will help you identify the bank transaction code.

Bank Data Type and Credit / Debit values will be the same. They both must be either Credit, Debit, or N/A.

To determine whether your Bank Transaction Code is a Credit or Debit, refer to the table below:

Source: BAI.org Cash Management Balance Reporting Specifications, page 10

Customized type codes should fall within the following ranges:

Source: BAI.org Cash Management Balance Reporting Specifications, page 11

For any codes between the 900-999 range that are continuing to fail, please reach out to FISPAN Support.

After filling in the above fields, click Save. This will trigger another import.

Return to the Banking Import History page by either clicking Track your status in the blue banner that appears, or by navigating to Transactions → Bank → Banking Import History.

If you receive a Failure Reason once more for an unrecognized bank transaction code, please repeat the above steps until the Banking Import status returns as Completed.

For any issues with enabling Bank Feeds or Code Type Mapping, please reach out to FISPAN Support at the below email address:

[email protected]