BAI2 Configuration
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) 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).
Enabling BAI2 Bank Feeds
Refer to the steps below on how you can enable BAI2 Bank Feeds.
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.
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
Do not click Save yet.
NOTE: The 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.
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.
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.
IMPORTANT: Each 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.
Select View for the Financial Institution you previously created, then click Add under the Format Profile: Configuration tab.
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.
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.
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.
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.
Click on the Code Type Mapping tab.
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 |
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 |
For any codes between the 900-999 range that are continuing to fail, please reach out to FISPAN Support.
After filling in the above fields, click Save. This will trigger another import.
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.
For any issues with enabling Bank Feeds or Code Type Mapping, please reach out to FISPAN Support at the below email address: