---
title: Switching from CSV to BAI2 Bank Feeds (NetSuite)
slug: svb/switching-from-csv-to-bai2-bank-feeds-netsuite
description: Learn about step 3 of the code type mapping process in this comprehensive document. Explore essential strategies for accurately mapping code types, ensuring seamless integration and compatibility. Discover expert tips and best practices to streamline the 
docTags: bSho0M8HRjDvZq9EBIWDy
createdAt: 2023-02-14T00:10:32.000Z
---

This set of instructions address issues some users have had with our old CSV bank feeds solution.

If you are an existing user of our old bank feeds solution, please refer to [Migrating Bank Feeds (NetSuite)](docId:6Up_qmBYOEF7ot2c5ySA3) to switch to the new solution.

If 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.

***

## Overview

:::hint{type="warning"}
**IMPORTANT: **Last Updated - February 13, 2023
:::

There have been some reports from users of CSV-formatted Bank Feeds receiving the following error on the Banking Import History page:

"The file could not be parsed or imported, because of the following error:

Invalid footer lines configuration. Verify that the value in the Footer Lines field matches the number of footer rows in the CSV file."

If you are one of these users experiencing this on one or more bank accounts, please follow the instructions below to switch your Bank Feeds format from CSV to BAI2 for affected accounts to avoid any potential disruption to your month-end close.

***

## Step 1: Update the Connectivity Method and Transaction Parser

Navigate to  **Setup → Accounting → Financial Institution → List**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/My2fEroMmwuSfwjUbIEFk_screenshot-2024-09-16-at-122044-am.png" size="80" width="2718" height="1172" position="center" caption="Navigate to Financial Institution" showCaption="true"}

Click **Edit** on the Financial Institution that you have created previously when enabling bank feeds.

Select the Format Profile: Configuration tab and select **Edit** on the Format Profile you have created previously for the affected account.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/PZgESGZ5PXCgusTwP1_CV_screenshot-2024-09-16-at-122128-am.png" size="80" width="2712" height="1006" position="center" caption="Click "Edit" beside the affected Format Profile" showCaption="true"}

On the Format Profile page, update the following fields:

- **Connectivity Method:** \[My Bank] BAI2 Transaction Feed
- **Transaction Parser:** BAI2 Plugin Implementation

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/R4SxG947PGXyzY5LMm-kX_screenshot-2024-09-16-at-122147-am.png" size="80" width="2856" height="1132" position="center" caption="Update the Format Profile" showCaption="true"}

Depending on whether your bank has additional bank transaction codes, we may revisit the Code Type Mapping tab later. You may safely skip any changes to this tab for now, and the **P**arser Configuration tab, which is only used for CSV-formatted Bank Feeds.

Click **Save**.

***

## Step 2: Monitor the Process

Select **Track your status** in the blue banner that appears, or go to **Transactions → Bank → Banking Import History**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/VudgfJTVuPZqulkMa7IEq_import-status.png" size="80" width="2048" height="685" position="center" caption="Track the Import Status" showCaption="true"}

If the import was successful, you will see **Completed** under the **Import Status** column.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/lfR-_MYqiEDUCI24HBh0q_completed-bai2.png" size="80" width="2048" height="909" position="center" caption="Completed Import Status" 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.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/tM-F1ECnxwR31eiNcywlI_failed-bai2.png" size="80" width="2042" height="455" position="center" caption="Failed Import Status" showCaption="true"}

If your Failure Reason states “is not one of your recognized bank transaction codes”, please proceed to the **Code Type Mapping** step.

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.

[svb.support@fispan.com](mailto\:svb.support@fispan.com)

***

## Step 3: Code Type Mapping

Return 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 had a failed import.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/bv2zh9hwvxdul4KxPGGNk_screenshot-2024-09-13-at-42350-pm.png" size="80" width="2028" height="545" position="center" caption="Click "Edit" beside the Format Profile where the import failed" showCaption="true"}

Click on the Code Type Mapping tab.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/K68zWZfcnPQI5kv_ThSTG_screenshot-2024-09-13-at-42448-pm.png" size="80" width="2038" height="609" position="center" caption="Code Type Mapping tab on a Format Profile" showCaption="true"}

:::hint{type="info"}
**NOTE: **If the Code Type Mapping could not be completed during the initial setup of this Format Profile, it is because the system has not read any bank transactions yet and does not know if there are additional codes that require mapping.
:::

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.

Fill in **Description** with something that will help you identify the bank transaction code.

**Bank Data Type** and **Credit / Debit** values will be the same. They both must be either Credit, Debit, or N/A.

To determine whether your Bank Transaction Code is a Credit or Debit, refer 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 FISPAN Support.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/R1gddZVfxrV9j3Kc7YYgp_screenshot-2024-09-13-at-42710-pm.png" size="80" width="2042" height="607" position="center" caption="Complete Code Mapping" showCaption="true"}

After filling in the above fields, click **Save**. This will trigger another import.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/8VRc4tWTTRK0qrqCG3T_U_screenshot-2024-09-13-at-35604-pm.png" size="80" width="2048" height="685" position="center" caption="Track the status of your bank import" showCaption="true"}

Return to the Banking Import History page by either clicking **Track your status** in the blue banner that appears, or by navigating to **Transactions → Bank → Banking Import History**.

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**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/Cv-chSV9zwAer7A5nFmz6_screenshot-2024-09-13-at-41934-pm.png" size="80" width="2048" height="909" position="center" caption="Completed Banking Import" showCaption="true"}

For any issues with enabling Bank Feeds or Code Type Mapping, please reach out to FISPAN Support at the below email address:

[svb.support@fispan.com](mailto\:svb.support@fispan.com)