Hey everyone. I need some help hunting down a problem. 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.

This sounds more like filename-based duplicate detection than a comparison of the actual BAI2 file contents. NetSuite documents that the import fails when the same filename has already been imported from that bank. It also imports only the first file matching the SFTP filename pattern during each run, so an older file remaining on the SFTP server could repeatedly block newer files.

I'll need to find out whether they have different files that would match the pattern and then make it fail to recognize the new files coming in.

Yeah, that would be the next thing I’d check. I’d compare the actual files available on the SFTP side during the failed runs and confirm whether an older file is still matching the pattern. If possible, I’d also check the exact filename NetSuite recorded as imported in the Banking Import History and compare it with the new file name coming from the bank. That should help confirm whether NetSuite is seeing it as a duplicate or if there is another issue with the file selection process.

Unfortunately Banking Import History does not show the files when it uses automatic import methods, only when it uses manual import methods. It's using SFTP. Maybe if I used an SFTP client with the same credentials, I could grab the files 2 or 3 times a day and find out that way....

That makes sense. If Banking Import History doesn’t show the automatically imported files, then checking the SFTP side directly is probably the best next step.