How do I set up handling of Bank of America BAI2 transaction code 856 in Format Profile for Automatic Bank Statement Import? 856 seems to be a non-standard code, that needs special treatment. When I try to import the BAI2 file over SFTP using ABSI, then I get this error: The file could not be imported, because 856 is not one of the recognized bank transaction codes. 856 must be mapped to a bank data type in NetSuite. For details, contact your administrator. For a list of custom bank transaction codes, your administrator must contact your financial institution.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue you're facing is related to the mapping of the BAI2 transaction code 856 in NetSuite. This code is not recognized by default in NetSuite and needs to be manually mapped to a bank data type. Here are the steps to do this: 1. Navigate to Setup > Company > Bank Statement Parser Plug-ins. 2. Click on the 'New Bank Statement Parser Plug-in' button. 3. In the 'Name' field, enter a name for the new parser plug-in. 4. In the 'Script File' field, upload a SuiteScript file that contains the logic for parsing the bank statement file. This script should include logic to handle the 856 transaction code. 5. In the 'Function Name' field, enter the name of the function in the SuiteScript file that should be called to parse the bank statement file. 6. Click 'Save'. Once you've created the new parser plug-in, you'll need to associate it with a bank statement file format: 1. Navigate to Setup > Company > Bank Statement File Formats. 2. Click 'Edit' next to the file format that you want to associate with the new parser plug-in. 3. In the 'Parser Plug-in' field, select the new parser plug-in that you created. 4. Click 'Save'. Now, when you import a BAI2 file that contains the 856 transaction code, NetSuite should be able to recognize and handle it correctly. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******