Switching from CSV to BAI2 Bank Feeds (NetSuite)

last updated february 13, 2023 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 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 connectivity method \[my bank] bai2 transaction feed transaction parser bai2 plugin implementation 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 step 2 monitor process 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 frb support\@fispan com step 3 code type mapping 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 why code type mapping could not be completed during initial set up of this format profile is because the system has not read any bank transactions yet, and therefore does not know if there are additional codes that require mapping fill in the following fields for the bank transaction code that was unrecognized bank transaction code description bank data type credit / debit 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 how to determine whether your bank transaction code is a credit or debit, please refer to the below table type codes description 001 099 account status type codes 100 total credits summary type codes 101 399 credit summary and detail type codes 400 total debits summary type codes 401 699 debits summary and detail type codes 700 799 loan summary and detail type codes 900 999 customized type codes source https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf customized type codes should fall within the following ranges type codes description 900 919 account status codes 920 959 credit summary and detail 960 999 debit summary and detail source https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf 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 frb support\@fispan com