--- title: Migrating Bank Feeds (NetSuite) slug: svb/migrating-bank-feeds-netsuite docTags: bSho0M8HRjDvZq9EBIWDy createdAt: 2024-01-13T00:36:10.840Z --- :::hint{type="danger"} ***Note:** These set of instructions cover the setup of our new bank feeds solution as of bank plugin version 2024.1.0. * I*f you are looking for instructions for our old bank feeds solution, please refer to *[Enabling Legacy Bank Feeds (NetSuite)](docId:_s7VfF1GbrZliaTJY6EBJ). *Our old bank feeds solution will no longer be supported as of bank plugin version 2024.2.0.* ::: 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. :::hint{type="info"} **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 FISPAN Support 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**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/DJ2AV6f1t41nn64Xg0vkE_image.png" size="70" width="750" height="688" caption="Go to Search & Install Bundles List" position="center" showCaption="true"} *** ## Step 2: Update Bundle ## Step 2: Update Bundle ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/2Y2ypd0o9Okj3H8rfiD5x_image.png" size="70" width="800" height="151" caption="Find SVB Go Link" position="center" darkWidth="800" darkHeight="151" showCaption="true"} Find the **SVB Go Link** bundle from the list. Then, hover over the green icon and select **Update**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/T3avqTLieJqBeCoxkg9K0_image.png" size="80" width="800" height="91" caption="Click Update Bundle" position="center" darkWidth="800" darkHeight="91" showCaption="true"} Click **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: - **Setup → Financial Institution Records – Level: Full** They must also be added as an audience for the following Script Deployment (can be found under Customization **→** Scripting **→** Script Deployments): - **SVB Go Link Trans Feed Config** (ID: customdeploy\_svb\_rpt\_feed\_s) *** ## Step 3: Mark Existing Bank Feeds as Inactive :::hint{type="warning"} **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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/FGw4mYMQsUoG3q-ftO01W_screenshot-2024-05-24-at-105143-am.png" size="80" width="1022" height="255" position="center" caption="Click Update Imported Bank Data" showCaption="true"} ::: Go to **Setup → Accounting → Financial Institution → List**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/R1aIxH4g7XDVVHfXmWRQi_image.png" size="50" width="768" height="761" position="center" caption="Go to Financial Institution List" showCaption="true"} Click **Edit** beside the Financial Institution you have set up previously for Bank Feeds. ![](https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/dKg46hwmdiS4Vy3BHDGLf_image.png "Click on \"Edit\"") 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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/JvjblYQK8StFH6kUNph2b_image.png" size="80" width="1258" height="500" position="center" caption="Click the Inactive checkbox on the Financial Institution" showCaption="true"} 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. *** [svb.support@fispan.com](mailto\:svb.support@fispan.com) *** ## Step 4: Create a New Financial Institution Navigate to **Setup → Accounting → Financial Institution.** ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/R1aIxH4g7XDVVHfXmWRQi_image.png" size="50" width="768" height="761" caption="Go to Financial Institution" position="center" showCaption="true"} Enter the name of your bank the **Financial Institution **field. Then, select **Save**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/FQtEppWvX_QTSLZP2BDMh_image.png" size="60" width="657" height="397" position="center" caption="Enter your bank's name as the Financial Institution" showCaption="true"} *** ## Step 5: Create a New Format Profile On the Financial Institution, click the **Format Profile: Configuration** tab and select **Add**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/ypalvKjhwSVwPCUPwO5vn_screenshot-2024-05-22-at-25737-pm.png" size="80" width="800" height="651" position="center" caption="Configure Format Profile" darkWidth="800" darkHeight="651" showCaption="true"} Fill in the following fields under **Primary Information**: - **Profile Name:** Any name, we suggest SVB Go Link Profile - **Profile Type:** Bank Reconciliation - **Connectivity Method:** SVB Go Link Transaction Feed - **Transaction Parser:** SVB Go Link Transaction Feed ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/2N7QQM3mCjfdbARHMsllZ_image.png" size="86" width="800" height="244" position="center" caption="Fill in the required fields under Primary Information" darkWidth="800" darkHeight="244" showCaption="true"} Next, click on the **Account Linking** tab. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/P3xGRc8qEqXfS9TUgS0v8_image.png" size="80" width="800" height="395" position="center" caption="Format Profile -> Account Linking tab" darkWidth="800" darkHeight="395" showCaption="true"} 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**. :::hint{type="warning"} **IMPORTANT:** Please ensure you link all of your bank accounts on the same day to avoid missing transactions for any unlinked bank accounts. ::: *** On the **Account Linking** subtab, use **Earliest Transaction Date for Import (All Accounts)** to control how far back NetSuite should reach when it first pulls transaction history. - This date applies to **all bank accounts by default**. - To set a different start date for one account, edit that row's **Earliest Transaction Date for Import** column directly. - To force every account back to the same date (overwriting any per-account overrides), enter a date and click **Apply Date to All Bank Accounts**. - If left blank, NetSuite defaults to importing the last 60 calendar days of available history. - You can select a start date up to **60 days in the past**. :::hint{type="info"} **IMPORTANT**: Once the first import for an account has run, this date is locked in. If you need to change it afterward, you'll need to unlink and re-link that bank account to select a new date — editing the field alone won't retroactively change what was already imported. ::: ### Configure the Import Schedule Once your accounts are linked, open the **Import Schedule** subtab on the format profile to control when NetSuite pulls transaction data from your financial institution. Complete the following fields: - **Unit of Time:** Choose the interval unit (e.g. *Day*) for how often imports should run. - **Repeat Every:** Set the frequency within that unit (e.g. *1 day* for a daily import). - **First Scheduled Import Date:** The date the first automated import should run. - **First Scheduled Import Time:** The time of day the import should kick off. - **Time Zone:** The time zone your scheduled time should be interpreted in. Click **Save** once these are set. ## Step 6: Monitor Bank Import Process :::hint{type="info"} **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 → **SVB Go Link** → Banking Import History**. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/BsGgj5K8k4yWjrJVHxHcF_screenshot-2024-05-22-at-30219-pm.png" size="80" width="818" height="97" position="center" caption="Click Track your status" showCaption="true"} If the import is successful, you will see **Completed** under the **Import Status** column. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/NN0WWR7_wbbukCoD5PQE7_image.png" size="80" width="2452" height="488" position="center" caption="Banking Import History page with a Completed import" showCaption="true"} 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 FISPAN Support. [svb.support@fispan.com](mailto\:svb.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. ::::WorkflowBlock :::WorkflowBlockItem Navigate to **Transactions → SVB Go Link → Banking Import History.** ::: :::WorkflowBlockItem 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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/wX4WHEJme0HlSqAk9B7Gx_image.png" size="80" width="800" height="71" position="center" caption="Failure Reason" darkWidth="800" darkHeight="71" showCaption="true"} ::: :::WorkflowBlockItem After expanding the row, the Failure Reason is provided. ::: :::: ### Unrecognized Bank Transaction Codes ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/6DX-D5iZBx_G9DP6Gmysw_image.png" size="58" width="800" height="809" position="center" caption="Sample import failed error on the Match Bank Data page" darkWidth="800" darkHeight="809" showCaption="true"} 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 FISPAN representative 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 :::::WorkflowBlock :::WorkflowBlockItem **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. ::: :::WorkflowBlockItem **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 My Bank support. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/oYKTI344SOfhT8ksLyiie_image.png" size="80" width="800" height="124" position="center" caption="Sample data for BAI2 code 389" darkWidth="800" darkHeight="124" showCaption="true"} ::: ::::WorkflowBlockItem **Save the Code Details** Once you have entered the missing BAI2 code information, click **Save** on the Format Profile. :::hint{type="warning"} **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 My Bank 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. :::hint{type="warning"} **NOTE: **NetSuite will only store 30 days' worth of Execution Logs and, by default, will only display the past 24 hours' worth of logs. ::: :::::WorkflowBlock :::WorkflowBlockItem **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. ::: :::WorkflowBlockItem **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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/D8Q2LP6YvKXRhaLd6D_hX_image.png" size="80" width="800" height="290" position="center" caption="Hyperlinked Connectivity Method and Transaction parser" darkWidth="800" darkHeight="290" showCaption="true"} ::: ::::WorkflowBlockItem **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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/yhK5qXRu8Z7Ay_mf6V2qw_image.png" size="78" width="800" height="245" position="center" caption="Connectivity Method (Financial Institution Connectivity) Execution Logs" darkWidth="800" darkHeight="245" showCaption="true"} ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/4pC9nWByWzxi2nNmy9rie_image.png" size="88" width="800" height="300" position="center" caption="Transaction Parser (Financial Institution Parser) Execution Logs" darkWidth="800" darkHeight="300" showCaption="true"} 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. :::hint{type="info"} **NOTE:** The **Connectivity Method** (Financial Institution Connectivity) downloads bank transactions from FISPAN. The Execution Logs here will display any errors relating to connectivity 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. ::: :::: ::::: ### 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. ::::WorkflowBlock :::WorkflowBlockItem **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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/Q_IGljAzocxeY2Y0qDCIG_image.png" size="80" width="800" height="247" position="center" caption="Click on Customize View" darkWidth="800" darkHeight="247" showCaption="true"} ::: :::WorkflowBlockItem **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. ::Image[]{src="https://app.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/sQbigUE0CP841z61lZQDQ_image.png" size="80" width="2872" height="908" position="center" caption="Rename the Search Title, then click on Available Filters" darkWidth="2872" darkHeight="908" showCaption="true"} Click the dropdown in the last row of the table. Select a **Date** from the options. ::Image[]{src="https://app.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/s5Jsdr5r-lnvXa668L3i5_image.png" size="80" width="2872" height="898" position="center" caption="Custom Default Script Notes View - filter by Date" darkWidth="2872" darkHeight="898" showCaption="true"} 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. ::: :::WorkflowBlockItem **Access the Custom View** Clicking **Save** will take you back to the Plug-In Implementation page. From here, click on the **Execution Log** tab. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/cY6UhUuuA6NfLt3PKz9b-_image.png" size="80" width="800" height="334" position="center" caption="Date filter applied" darkWidth="800" darkHeight="334" showCaption="true"} 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. ::: :::WorkflowBlockItem **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. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/cY6UhUuuA6NfLt3PKz9b-_image.png" size="80" width="800" height="334" position="center" caption="Execution Log tab" darkWidth="800" darkHeight="334" showCaption="true"} Copy the contents of the whole table and paste into an email addressed to FISPAN Support. 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 FISPAN Support will be able to retrieve your missing transactions and resync them as part of your next morning's automatic import. ::: :::: [svb.support@fispan.com](mailto\:svb.support@fispan.com) *** ## FAQs :::ExpandableHeading **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. ::: :::ExpandableHeading **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. ::: :::ExpandableHeading **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. ::: :::ExpandableHeading **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. ::: :::ExpandableHeading **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. ::: :::ExpandableHeading **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 FISPAN has re-triggered a re-import. Refer to the Troubleshooting section of this guide for more details. ::: :::ExpandableHeading **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. ::: :::ExpandableHeading **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." ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/MGukWOaa9nep2i33ldsJr_screenshot-2024-05-09-at-103643-am.png" size="80" width="1870" height="494" position="center" caption="Select NetSuite BAI2" showCaption="true"} :::