 These set of instructions cover the setup of our legacy bank feeds solution that will no longer be supported as of bank plugin version 2024.2.0.

If you are an existing user of our legacy bank feeds solution, please refer to

If you are new to bank feeds are are not currently using our legacy solution, please refer to 

The bank bundle adds support for Bank Feeds through a custom Connectivity Method, which allows transactions from your bank accounts to flow automatically into NetSuite's Match Bank Data module. To enable Bank Feeds in your NetSuite environment, please follow the steps outlined in this guide. This guide will walk you through two methods of enabling bank feeds, via:

Which method to use is your choice, but most users prefer CSV for richer detail.

Please note that aside from the custom Connectivity Method that is named after your bank, everything else discussed in this guide is owned and managed by NetSuite. This includes, but is not limited to, the following:

While owned and managed by NetSuite, the following cannot be customized:

The Bank Feeds feature requires your bank bundle to be updated to version 2021.16.0 or newer. For users on newer version, you may skip to 

Customization → SuiteBundler → Search & Install Bundles

 bundle from the list. Then, hover over the green icon and select 

The bundle will take a few moments to update – it will appear as pending and then show the progress of the update. Once complete, the status column on the Installed Bundles page will show a check mark.

 users who will be setting up and managing Bank Feeds must have the following permission:

They must also be added as an audience for the following Script Deployment (can be found under Customization 

Step 3: Install Bank Statement Parsers Bundle

Customization → SuiteBundler → Search & Install Bundles

, select the appropriate bundle (293699), and select 

The bundle will take a few moments to install – it will appear as pending and then show the progress of the install. Once complete, the status column on the Installed Bundles page will show a check mark.

 on the bank account for which you would like to use the reconciliation feature.

Use Match Bank Data and Reconcile Account Statement Pages” 

box to enable this feature for the account.

Setup → Accounting → Financial Institution

Users have the option to enable either CSV Bank Feeds or BAI2 Bank Feeds. While some users may wish to have some bank accounts connected to CSV and others to BAI2, this is uncommon and does not provide any added benefit. We recommend users to pick either CSV or BAI2 for all bank accounts they wish to enable bank feeds for.

Refer to the below steps on how you can enable CSV Bank Feeds, otherwise skip down to the 

[CSV] Step 1: Create a Format Profile with Primary Information

[CSV] Step 2: Define Parser Configuration Parameters on the Format Profile

Ensure the following fields are shown under the 

 to save the Parser Configurations. Do not click 

[CSV] Step 3: Link a GL Account to the Format Profile

[CSV] Step 4: Monitor Bank Import Process

As soon as the Format Profile was saved, a blue banner will appear to notify you that NetSuite is beginning the bank import process.

 in the blue banner that appears, or go to 

Transactions → Your Bank → Banking Import History

If the import was successful, you will see 

column. Select the plus (+) sign to expand the failure reason details.

Please take a screenshot of the error message and download the CSV provided from the link in the error message. Then, email this information to support.

Refer to the below steps on how you can enable BAI2 Bank Feeds.

[BAI2] Step 1: Create a Format Profile with Primary Information

Each Format Profile can only support one linked bank account. Complete the following steps for each of your bank accounts:

[BAI2] Step 2: Link a GL Account to the Format Profile

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.

[BAI2] Step 3: Monitor Bank Import Process

Transactions → Bank → Banking Import History

If your Failure Reason states that a three-digit number “

is not one of your recognized bank transaction codes

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:

City National Bank has BAI2 custom code types that fall within the below ranges:

EASI Link® Service Appendix D - BAI2 File Specifications Version 12.4.0

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:

Excluding Duplicate Transactions

Enabling Legacy Bank Feeds (NetSuite)

Enabling Legacy Bank Feeds (NetSuite)

[BAI2] Step 4: Code Type Mapping

FAQs