Enabling Bank Feeds (NetSuite)

Bank feeds allows for your settled bank transactions to automatically flow into NetSuite's Match Bank Data module for reconciliation, removing the need to export and import bank statements manually. To enable bank feeds, follow the instructions below.

Please take note of the following field mappings for data received from your bank within the Match Bank Data page in NetSuite.

* Information denoted with a star will only be displayed if the transaction includes it. Note that not all transactions will have all the above data.

Go to Customization → SuiteBundler → Search & Install Bundles → List.

Find the CNB Pay bundle from the list. Then, hover over the green icon and select Update.

Select Update Bundle, and select OK on the confirmation pop-up.

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.

Note: Non-administrator 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 → Scripting → Script Deployments):

Navigate to Setup → Accounting → Financial Institution.

Enter the name of your bank the Financial Institution field. Then, select Save.

On the Financial Institution, click the Format Profile: Configuration tab and select Add.

Fill in the following fields under Primary Information:

Next, click on the Account Linking tab.

Previously, each Format Profile was only able to support one linked bank account. With this new edition of Bank Feeds, a Format Profile can have multiple bank accounts and linked GL accounts.

Based on the account seen under the Bank Account column, click on the empty space below the Linked GL Account to show a drop-down. In this drop-down, select the GL account that maps to the Bank Account.

Repeat this step for all accounts you wish to enable bank feeds for.

Once all bank accounts have been linked, click Save.

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

Select Track your status in the blue banner that appears, or go to Transactions → Your 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.

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 at the following:

In the situation a bank data import fails, the failure reason can be found on the Banking Import History page.

Navigate to Transactions → Bank → Banking Import History.

Find the line item that shows the Import Status as FAILED, accompanied by a red caution icon. On that line item, click on the small plus icon on the far left to expand the row.

After expanding the row, the Failure Reason is provided.

In the occasion that a bank data import fails due to an unrecognized bank transaction code, you will need to do the following:

Please refer to the sections below for instructions on how to proceed.

Navigate 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 you have also created previously.

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, or on the Match Bank Data page.

Fill in Description based on the code's description, which can be found here: BAI.org Cash Management Balance Reporting Specifications, page 10

Bank Data Type and Credit / Debit values will be the same. They both must be either Credit, Debit, or N/A. This can also be found on BAI.org Cash Management Balance Reporting Specifications, page 10, or by referring to the below table:

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.

Once you have entered the missing BAI2 code information, click Save on the Format Profile.

In the case of a failed import, you will need to retrieve Statement IDs from the Execution Logs from either the Connectivity Method or the Transaction Parser prior to reaching out to our Support Team to resync transactions.

Navigate to Setup → Accounting → Financial Institution.

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

Select the Format Profile: Configuration tab and click on the Name of the Format Profile you have created previously.

On the Format Profile, under Connectivity Method, right click on the hyperlinked Bank Transaction Feed and open it in a new browser tab.

Under Transaction Parser, also right click on the hyperlinked Bank Transaction Feed and open it in a new browser tab.

In both of the new tabs that were opened for the Connectivity Method and Transaction Parser, click on the Execution Logs tab in the sub-menu.

The Statement IDs, Account IDs, and Number of Transactions should be identical between both the Connectivity Method and Transaction Parser. Each row corresponds to a bank accounted linked with the new bank feeds service.

Unable to see Execution Logs?

If you are unable to see any Execution Logs from the past 24 hours, you will need to add a Date filter as a Custom View. Please note that any logs that are older than 30 days are not stored by NetSuite.

From the Plug-In Implementation page that you were on for either the Financial Institution Connectivity or FInancial Institution Parser, click on the Customize View button.



On the Customize Script Server Script Log Search Results page that just opened, rename the Search Title to [BANK] Bank Feeds - Execution Log Dates.

Next, click on the Available Filters sub-tab.

Click on the drop-down on the last row of the table. Select Date from the options.

Once you have added Date, click Save. This Custom View will now be available on both the Financial Instution Parser or Connectivity Method logs.

Clicking Save will take you back to the Plug-In Implementation page. From here, click on the Execution Log tab. There will be a new option under the View drop-down, which is the Custom View you have just created. When the new Custom View is selected, a date filter will now appear.

Using the new Date filter, define the date the error occured on. This should be the same date you are missing transactions for.

Once a date within the past 30 days has been selected, the table will populate with a number of rows containing Statement IDs, Account IDs, and Number of Transactions for every bank account linked with the bank feeds service for the selected date.

Please copy and paste the contents of the whole table into an email addressed to our Support Team. Ensure the following is included in your message

With this information, our Support Team will be able to retrieve your missing transactions and resync them as part of your next morning's automatic import.

What time does the automatic import of my bank transactions trigger?

How many days worth of data does the new bank feeds solution import upon initial setup?

Do I still need to download NetSuite's Bank Statement Parsers bundle to use this new bank feeds solution?

Since all bank accounts are now matched under one Format Profile on the Financial Institution, what happens if an import fails on one bank account?

What are the differences in data in the new bank feeds compared to the old bank feeds?

If I need to do a manual import, what statement type can I use?