Migrating Bank Feeds (NetSuite)

to leverage the latest improvements in bank feeds functionality, including increased reliability and better balance reporting, your netsuite administrator must update the bank bundle, deactivate the existing bank feeds configuration, and set up the new service using the \[bank] transaction feed parser instructions to complete these steps can be found on this page overview this update introduces a new, dedicated transaction parser, replacing the dependency on netsuite's built in parser this change provides greater control over the data and ensures you can take advantage of future enhancements to the quality and mapping of bank feed data some of the key improvements to the existing functionality of bank feeds include the following reliability a new fispan owned transaction parser removes the dependency on netsuite's parser, allowing for greater control and consistency over the data fed into the reconciliation module balances the account balance field on the match bank data page will now update every time transactions are pushed into netsuite, a fix for the previous limitation scalability enabling this service is required to access future improvements to bank feed data quality and mapping historical transactions at setup you now have control over your historical data sync at setup without needing to contact support for netsuite 2026 1 or later during the account linking process for newly linked accounts , you can select an earliest transaction date for import this allows you to automatically import up to 60 days of historical transactions upon setup, or pick a future date to delay your initial import (note this feature is only applicable to new accounts getting linked existing account linkings remain unchanged) for netsuite 2025 2 upon initial setup for newly linked accounts, the system will automatically import up to your last 60 days of historical transactions by default if you have any question regarding transaction import, please reach out to after successfully setting up your bank feeds connection data field mapping the following table details how the data received from your bank maps to the fields within the netsuite match bank data page with the updated service netsuite (match bank data) transaction data field transaction date settled date type transaction type transaction number check number (if non null) or customer reference name counter party name memo description amount amount 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 step 1 locate bundle go to customization → suitebundler → search & install bundles → list step 2 update bundle find the santander treasury fusion 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 step 3 mark existing bank feeds as inactive important it is highly recommended that, before completing the bank feed migration that you trigger one last sync for any outstanding transactions to do this, navigate to match bank data and click update imported bank data for all accounts with bank feeds go to setup → accounting → financial institution → list click edit beside the financial institution you have set up previously for bank feeds on the financial institution, select the inactive checkbox optionally, you may also rename the financial institution to make it clear that this financial institution is no longer in use click save deactivating this financial institution will deactivate all connected bank feeds and stop bank transactions from being imported into the match bank data module for all format profiles on this financial institution step 4 create a new financial institution navigate to setup → accounting → financial institution enter the name of your bank the financial institution field then, select save step 5 create a new format profile on the financial institution, click the format profile configuration tab and select add fill in the following fields under primary information profile name any name, we suggest profile profile type bank reconciliation connectivity method transaction feed transaction parser transaction feed 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 space below the linked gl account to show a dropdown in this dropdown, select the gl account that maps to the bank account repeat this step for all accounts you wish to enable bank feeds once all bank accounts have been linked, click save important please ensure you link all of your bank accounts on the same day to avoid missing transactions for any unlinked bank accounts step 6 monitor bank import process note you may not see transactions in the match bank data page upon setup, as our bank feed solution will import all prior day transactions the day after setup and continue to do so onwards as soon as the format profile is 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 → → banking import history if the import is 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 santander support\@fispan com mailto\ santander support\@fispan com troubleshooting identifying errors in the situation where a bank data import fails, the failure reason can be found on the banking import history page navigate to transactions → → 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 unrecognized bank transaction codes in the event that a bank data import fails due to an unrecognized bank transaction code, you will need to do the following map any missing bai2 codes retrieve statement ids from connectivity method / parser execution logs contact a with the following statement ids from impacted accounts the date the import failed the date of the transactions that are missing please refer to the sections below for instructions on how to proceed mapping bank transaction codes locate the financial institution 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 bank transaction code details fill in the following fields for the bank transaction code that was unrecognized bank transaction code the three digit code from the error message seen on the banking import history page, or on the match bank data page description fill in with the code's description, which can be found here bai org cash management balance reporting specifications, page 10 https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf bank data type credit / debit 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 https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf , or by referring to the table below 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 bai org cash management balance reporting specifications, page 10 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 bai org cash management balance reporting specifications, page 11 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 support save the code details once you have entered the missing bai2 code information, click save on the format profile important netsuite will attempt to re import bank transactions, but they will not yet appear on the match bank data page you will still need to retrieve the statement ids and contact support with affected dates to request a re sync retrieving statement ids from execution logs 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 note netsuite will only store 30 days' worth of execution logs and, by default, will only display the past 24 hours' worth of logs locate the financial institution navigate to setup → accounting → financial institution → list 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 open transaction feed on the format profile, under connectivity method , click the hyperlinked bank transaction feed, and open it in a new browser tab under transaction parser , also click the hyperlinked bank transaction feed and open it in a new browser tab locate execution logs in both of the new tabs that were opened for the connectivity method and transaction parser , click 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 account linked with the new bank feeds service note the connectivity method (financial institution connectivity) downloads bank transactions from the execution logs here will display any errors relating to connectivity issues with the transaction parser (financial institution parser) pushes the downloaded bank transactions from into the match bank data page in netsuite the execution logs here will display any errors relating to missing bai2 codes or other formatting issues in the bank transaction data 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 customize view 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 create custom view 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 the dropdown in the last row of the table select a date from the options once you have added the date , click save this custom view will now be available on both the financial institution parser and connectivity method logs access the custom view 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 dropdown, which is the custom view you have just created when the new custom view is selected, a date filter will now appear locate execution log using the new date filter, find the date the error occurred 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 several rows containing statement ids, account ids, and the number of transactions for every bank account linked with the bank feeds service for the selected date copy the contents of the whole table and paste into an email addressed to ensure the following is included in your message execution log table contents (containing statement ids from impacted accounts) the date the import failed the date of the transactions that are missing with this information, our will be able to retrieve your missing transactions and resync them as part of your next morning's automatic import santander support\@fispan com mailto\ santander support\@fispan com faqs i want to change the time of day my transactions sync how do i do that? if you are on netsuite 2026 1, navigate to the format profile of your financial institution record and look for the import schedules subtab there, you can adjust the frequency, start time, and preferred time zone for your automated imports how many days' worth of data does bank feeds import upon initial setup? you can choose exactly how many days of historical data to import (up to 60 days prior) by setting the earliest transaction date for import during the setup process if you don't set a date, netsuite will automatically import up to your last 60 days of historical transactions by default can i change my "earliest transaction date" after i set it up? once your format profile is saved and the first import runs, the date you selected is locked in if you made an error, you will need to unlink and re link the bank account to select a new date i set a future start date during setup, but i don't see any transactions yet why? if you set a future date for your initial import, netsuite will pause your data sync and wait until that exact date arrives to pull the data you will not see any transactions flow into the match bank data page until that scheduled date occurs do i still need to download netsuite's bank statement parsers bundle to use bank feeds? no, this solution does not require netsuite's bank statement parsers bundle we recommend users keep this bundle installed so the option to revert your bank feeds solution to the old one is still available in case 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? import failures with bank feeds are rare in the case of failures, netsuite will not successfully sync transactions for all linked bank accounts until any errors, such as missing bai2 codes, have been resolved, and has re triggered a re import refer to the troubleshooting section of this guide for more details what are the differences in the data in bank feeds compared to the legacy bank feeds? the new bank feeds use bai codes, which provide more details for the transaction types for example, previously, you would only see debits and credits as transaction types in the new bank feeds, you will see more detailed transaction types such as debits, credits, ach, transfers, fees, deposits, interest, payments, and checks if i need to do a manual import, what statement type can i use? if you are utilizing bank feeds, you will only be able to use the bai2 formatting option otherwise, your manual import will fail with the error "the file could not be imported because the date is not in the correct format "