Why does this bank statement import error occur some days and some days not? The imports are scheduled only once a day, but sometimes I see this on the same day as a successful import. Error message: Import-level FailureThere was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded. The bank statements are imported for use in the Match Bank Data page, by the Automatic Bank Statements Import, using Financial Institutions and their Format Profiles and the BAI2 parsing plugin. This is not done using a custom script.

AI generated answer (using internal Slack threads):

The error message you're seeing, "Import-level FailureThere was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded," suggests that the same file is being uploaded more than once. This could be due to a number of reasons: 1. Duplicate File Uploads: If the same file is being uploaded more than once in a day, it could lead to this error. Ensure that the file is only uploaded once per day as per the schedule. 2. File Name Issues: As one of the conversations suggests, the length of the file name could be a factor. If the file name is too long, it could cause issues with the upload process. 3. Incorrect File Format: The file format could also be a factor. If the file is not in the correct format (BAI2 in this case), it could lead to errors. Ensure that the file is in the correct format before uploading. 4. Mismatch in BAI Codes: As suggested in one of the conversations, there could be a mismatch in the BAI codes. NetSuite only maps certain BAI codes out of the box. If there are codes that do not match, it could lead to issues with the upload. 5. Incorrect Account Mapping: If the account mapping is not correct, it could lead to issues with the upload. Ensure that the account mapping is correct before uploading the file. 6. Date Issues: If the date in the file is off, it could lead to issues with the upload. Ensure that the date in the file is correct. To resolve this issue, you may need to review your file upload process and ensure that all the above factors are correctly addressed. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******