I'm setting up Automatic Bank Statement Imports in our Sandbox to see if it will work for us, and switching over to this from an existing method that as far as I can tell, is only running in the Production environment of our NetSuite. One of our account managers is testing it out and it's mostly working. However, aside from it occasionally making erroneous auto-matches in the Match Bank Data screen's Review tab that have to be undone, there's a worse problem I want to focus on: Three of the Accounts show no activity at all for the past month and a half that we've had it running on a daily import schedule. Banking Import History shows every few days that the import failed, with this error:

There was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded.

This is strange to me because the schedules I have set up only should try to import one file for each bank once per day, and these files have different names and source folder paths. They both use the SFTP Connectivity in their respective Format Profiles, and the BAI2 Parser plugin. And they work fine most of the time. One Bank uses username/password auth, the other uses a Private Key. The problem is happening on both Banks, but only for activity that is immediately offset by sweeping entries to other bank accounts, but they should still have activity that offsets against the GL. This could be a coincidence, or maybe the BAI2 files sent on those days where it fails only contain those kinds of sweeping activities? I don't know, I can't see the BAI2 files that come in via this automatic bank statement import setup. But I'll see if someone can get them for me from the Banks. I need to figure out whether the missing activity is in the files that didn't import (because it thought they were already imported), or whether it's correct in saying that it's the exact same file, not just seemingly the same.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like there are a few potential issues that could be causing the problem with your Automatic Bank Statement Imports. 1. File Format: Ensure that the file format is correct and compatible with NetSuite. If you're using a BAI2 file, you may need to use a parser from the Bank Statement Parser SuiteApp, as the default parser only works for certain banks. 2. BAI Codes: NetSuite only maps certain BAI codes out of the box. If there are BAI codes in your file that do not match, this could be causing the issue. 3. Date Ranges: Check the date ranges in your file. If the date in your file is off, this could be causing the entries not to show up under any TO BE MATCHED, MATCHES TO SUBMIT OR EXCLUDED Subtab. 4. Bank Feed Issues: Bank feeds can be buggy and are not always reliable. They use service from Yodlee and Saltedge for the feed, which are essentially a screen scraper. This technology is not foolproof, which is why issues can occur. 5. Connection Issues: If you're having to rebuild the connection every day to import anything, this could be a sign of a connection issue. To resolve these issues, you may need to modify the file format, check the BAI codes, adjust the date ranges, or consider switching to ABSI via SFTP, which is more reliable than bank feeds. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******