---
title: BAI2 Configuration
slug: jpmorgan/bai2-configuration
description: Follow this guide to configure BAI2 bank feeds in the legacy bank feeds solution.
docTags: bSho0M8HRjDvZq9EBIWDy
createdAt: 2023-12-12T00:32:13.916Z
---

This set of instructions addresses the configuration of BAI2 bank feeds in our legacy bank feeds solution.

If you are an existing user of our legacy bank feeds solution, please refer to [Migrating Bank Feeds (NetSuite)](docId\:Ei25AXDjlaZGE0nmv-3CB) to switch to the new solution.

If you are looking for instructions for our legacy bank feeds solution, please refer to [Enabling Legacy Bank Feeds (NetSuite)](docId\:TVbOrXgjfQocQtdnnRIIT).

***

## Enabling BAI2 Bank Feeds

Refer to the steps below on how you can enable BAI2 Bank Feeds.

:::::WorkflowBlock
::::WorkflowBlockItem
### Create a Format Profile

Each Format Profile can only support one linked bank account. Complete the following steps for each of your bank accounts.

Select the **Format Profile: Configuration** tab and select **Add**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/FCFVxQ0YWIGpHwbuEOfKG_screenshot-2024-09-13-at-25905-pm.png" size="80" width="1988" height="976" position="center" caption="Configure Format Profile" showCaption="true"}

Fill in the following fields under **Primary Information**:

- **Profile Name:** Any name. We recommend you name this after the bank account you are linking.
- **Profile Type:** Bank Reconciliation
- **Connectivity Method:** J.P. Morgan BAI2 Transaction Feed
- **Transaction Parser:** BAI2 Plugin Implementation

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/ioDJhz3BAQeRAjv1iB8EN_screenshot-2024-09-13-at-35224-pm.png" size="80" width="1557" height="507" position="center" caption="Format Profile page with Primary informartion filled in" showCaption="true"}

Do not click **Save** yet.

:::hint{type="info"}
**NOTE:&#x20;**&#x54;he Connectivity Method we ask you to select above is custom and comes from your bank bundle. Everything outside of this Connectivity Method is considered native to NetSuite.
:::
::::

::::WorkflowBlockItem
### Link GL Account to the Format Profile

Now, select the **Account Linking** tab.

Choose the appropriate **Linked GL Account** in the right-hand column for the **Bank Account**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/cHFQUgyUJnqRttQoTdW4J_screenshot-2024-09-13-at-35406-pm.png" size="80" width="2045" height="819" position="center" caption="Link a GL Account" showCaption="true"}

You can skip the Code Type Mapping tab for now and revisit it later if your bank has additional transaction codes. Also, skip the Parser Configuration tab, as it is required only for CSV Bank Feeds.

Click **Save** to save this Format Profile.

:::hint{type="warning"}
**IMPORTANT:&#x20;**&#x45;ach Format Profile supports only one linked bank account; data will be imported only for the top-most account with a **Linked GL Account**. To enable Bank Feeds for additional accounts, you must repeat these steps for each one.

Navigate to **Setup → Accounting → Financial Institution → List**.&#x20;

Select **View** for the Financial Institution you previously created, then click **Add** under the **Format Profile: Configuration** tab.
:::
::::

:::WorkflowBlockItem
### Monitor Bank Import Process

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 → Bank → Banking Import History**.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/Ugo52sgRTZM9kygOIsi0b_screenshot-2024-09-13-at-35604-pm.png" size="80" width="2048" height="685" position="center" caption="Banner with a link to track your 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/ddXYqPOt9U2Gyo7OJ9dkk_screenshot-2024-09-13-at-35845-pm.png" size="80" width="2046" height="909" 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&#x20;**&#x63;olumn. Select the plus (+) sign to expand the failure reason details.

::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/Y3vP2gfRLQXpmE-v7ndZS_screenshot-2024-09-13-at-40807-pm.png" size="80" width="2042" height="455" position="center" caption="Import Failure Error" showCaption="true"}

If your Failure Reason states that a three-digit number “is not one of your recognized bank transaction codes”, please proceed to the next 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 FISPAN Support team.
:::
:::::

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

***

## BAI2 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 &#x22;Edit&#x22; 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:&#x20;**&#x49;f 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&#xA0;**
- **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:

 [jpmc.support@fispan.com](https://support.fispan.com/jpmorgan/contact-us)
