Migrating Bank Feeds (NetSuite)

an enhanced bank feeds service is now available action is required to begin using the enhanced bank feeds service which brings numerous improvements to the existing functionality of bank feeds including the following reliability this enhanced bank feeds service introduces a new fispan owned transaction parser and removes the dependency on netsuite's transaction parser leveraging this new parser allows for greater control over the data that is fed into the reconciliation module scalability to take advantage of future improvements to the quality and mapping of bank feed data, users must enable this enhanced bank feeds service balances previously, the "account balance" field on the match bank data page did not update due to limitations of using netsuite's parser by enabling this enhanced bank feeds service, account balances will be updated in the match bank data module every time transactions are pushed into netsuite to begin using the enhanced bank feeds service, 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 below 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 if you would like 60 days worth of transactions imported upon setup, please reach out to support after setting up your bank feeds connection as part of the enhanced bank feeds service, please take note of the following field mappings for data received from your bank within the match bank data page in netsuite netsuite (match bank data) transaction data 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 commerce connections direct bundle from the list then, hover over the green icon and select update select update bundle , and select ok on the confirmation pop up it is highly recommended 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 step 3 mark existing bank feeds as inactive 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 \[my bank] profile profile type bank reconciliation connectivity method \[my bank] transaction feed transaction parser \[my bank] 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 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 please ensure you are linking 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 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 commerce support\@fispan com troubleshooting identifying errors 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 unrecognized bank transaction codes in the occasion 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 our support team 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 bai2 codes 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 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, or on the match bank data page fill in description based on the code's description, which can be found here https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf 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 https //www bai org/docs/default source/libraries/site general downloads/cash management 2005 pdf , or by referring 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 215,578 trueleft unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type 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 once you have entered the missing bai2 code information, click save on the format profile 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 note netsuite will only store 30 days worth of execution logs and by default, will only display the past 24 hours worth of 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 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 connectivity method (financial institution connectivity) downloads bank transactions from fispan the execution logs here will display any errors relating to connecitivty issues with fispan the transaction parser (financial institution parser) pushes the downloaded bank transactions from fispan 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 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 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 support team will be able to retrieve your missing transactions and resync them as part of your next morning's automatic import commerce support\@fispan com faqs what time does the automatic import of my bank transactions trigger? netsuite will import transactions once a day between 4 to 7 am pst at the same time every day the time of import is determined randomly by netsuite and cannot be changed how many days worth of data does the new bank feeds solution import upon initial setup? this new bank feeds solution will not immediately import transactions upon initial setup the import will begin the next day in that import, it will include only the prior day transactions every import will only bring in prior day transactions if you would like 60 days worth of transactions imported upon setup, please reach out to support after setting up your bank feeds connection do i still need to download netsuite's bank statement parsers bundle to use this new bank feeds solution? no, this solution does not require netsuite's bank statement parsers bundle we recommend users to keep this bundle installed so the option to revert your bank feeds solution back 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 on the new bank feeds solution 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 fispan has re triggered a re import refer to the troubleshooting section of this guide for more details what are the differences in data in the new bank feeds compared to the old 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, fee, deposits, interest, payment and checks if i need to do a manual import, what statement type can i use? if you are utilizing the new bank feeds product, 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