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. Is it going to be enough to add 856 to the Format Profile's "Code Type Mapping" list? Other research I have done suggests that this is a "sweep-in" code, which sounds to me like some kind of transfer from one account to another. Each line beginning with 16,856 in the BAI2 file ends with a, 11-digit number followed by ten zeroes, and is followed by a line beginning with 88,CUR FR followed by a 10-digit number that didn't appear in the 16,856 line. Am I going to have to program my own special Bank of America format parsing plugin, or can the BAI2 Plugin Implementation included in the "Bank Statement Parsers" bundle with ID 293699 handle it properly?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue you're facing with the BAI2 transaction code 856 is not uncommon. The BAI2 file format is a common format developed by the Bank Administrative Institute for exchanging data, including securities transactions and lockbox deposits. NetSuite supports BAI2 Prior-Day Reporting for Bank Reconciliation. However, it appears that certain transaction codes, such as the 856 you mentioned, may not be natively supported by NetSuite. This could be the reason why you're receiving an error when trying to import the BAI2 file over SFTP using ABSI. To resolve this issue, you may need to map the 856 transaction code to a bank data type in NetSuite. This can be done by adding the 856 code to the Format Profile's "Code Type Mapping" list. This should allow NetSuite to recognize the 856 code when importing the BAI2 file. As for the "sweep-in" nature of the 856 code, it does sound like it could be a type of transfer from one account to another. However, without more specific information about the nature of these transactions, it's difficult to say for certain. Regarding the need for a custom Bank of America format parsing plugin, it's possible that the BAI2 Plugin Implementation included in the Bank Statement Parsers bundle could handle this. However, without more information about the specific requirements of your bank and the nature of the transactions, it's difficult to say for certain. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******