 These set of instructions address 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 

If you are looking for instructions for our legacy bank feeds solution, please refer to 

There have been some reports from users of CSV formatted Bank Feeds receiving the below 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 below instructions to switch your Bank Feeds format from CSV to BAI2 for affected accounts to avoid any potential disruption to your month-end close.

Step 1: Update the Connectivity Method and Transaction Parser

Setup → Accounting → Financial Institution → List

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

 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 

 tab later. You may safely skip any changes to this tab for now and the 

 tab, which is only used for CSV formatted Bank Feeds.

 in the blue banner that appears, or go to 

Transactions → Bank → Banking Import History

If the import was successful, you will see 

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 

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.

Setup → Accounting → Financial Institution

 on the Financial Institution that you have created previously.

 on the Format Profile that had a failed import.

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

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

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

 values will be the same. They both must be either 

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

Customized type codes should fall within the following ranges:

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 

Return to the Banking Import History page by either clicking 

 in the blue banner that appears, or by navigating to 

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:

Learn about the crucial third step of code type mapping and discover how to effectively implement it. Find valuable insights and tips in this comprehensive document, which also features multiple mentions of the email address [customer.service@fispan.com].

BAI2 Configuration

Switching from CSV to BAI2 Bank Feeds

YourBank

MyBank

Adding Accounts to Bank Feeds (NetSuite)

J.P.Morgan

J.P. Morgan

Welcome

Getting Started

Pre-Onboarding Checklist (NetSuite)

Installation and Set-up

Post-Onboarding Checklist (NetSuite)

Configuration

Vendor Bank Details

Temp

Vendor Payables

Bank Statements (NetSuite)

Account Transfers (NetSuite)

Positive Pay (NetSuite)

Remittance Advice (NetSuite)

Employee Expense Reports (NetSuite)

Features

Switching from CSV to BAI2 Bank Feeds

Step 3: Code Type Mapping