Bank Statement File Name Import Matching

The Auto Bank Statement Import (ABSI) SuiteApp uses the file name pattern defined on your SFTP connectivity configuration to match and identify which bank statement files to import into NetSuite. The following table describes how the system controls your bank data imports on certain scenarios.

Scenario

Result

No file match or no available file on the financial institution server.

Bank statement file import will fail.

File match but system identifies that the same file name was already previously imported from the same bank.

Bank statement file import will fail.

When files are not uploaded due to parsing errors, the failed file import records must be deleted before you can reupload them. For more information, see Deleting SFTP Connectivity Failed Import Record.

File contains parsing error and has the same file name as another file previously imported from a different bank.

Bank statement file import will fail.

First, check the failure reason of your import to verify and resolve the error. Then, delete the failed file import record to allow the system to import a statement file with a similar name from a different bank.

Note:

To help identify which import file record to delete, take note of the Internal ID or Configuration ID, which is available on the execution log of the failed import.

For more information, see Deleting SFTP Connectivity Failed Import Record.

After deleting the failed import record, you can manually request the system to perform another import. To do this, see Updating Imported Bank Statement Files.

A file matched and was imported successfully in NetSuite but there are remaining matching files in the financial institution’s server that have not been imported.

This scenario can occur if the system identifies multiple files that matched your file name pattern.

For multiple matching files, the system only imports the first bank statement file that matches your file name pattern. The remaining files are imported on the next import schedule or can be retrieved immediately by manually requesting the system to perform another import. To upload the remaining files through manual import request, see Updating Imported Bank Statement Files.

Using the Administrator role, you can check the execution log of your import details record to verify if there are pending files that needs to be imported into NetSuite. To do this:

  1. Using the Administrator role, go to Customization > Plug-ins > Plug-In Implementations.

  2. Click the SFTP Connectivity plug-in implementation.

  3. On the Execution Log subtab,, search for the log related to your import detail record.

  4. In the Details column, a message will indicate if there is a pending number of files remaining on the financial institution’s server.

The Download Filename Pattern field on your SFTP connectivity configuration is set to blank

When there is more than one file available on the financial institution server, the system only imports the first bank statement file not yet available in NetSuite.

The remaining files are imported on the next import schedule or can be retrieved immediately by manually requesting the system to perform another import. To upload the remaining files through manual import request, see Updating Imported Bank Statement Files.

Using the Administrator role, you can check the execution log of your import details record to verify if there are pending files that needs to be imported into NetSuite. To do this:

  1. Using the Administrator, role, go to Customization > Plug-ins > Plug-In Implementations.

  2. Click the SFTP Connectivity plug-in implementation.

  3. On the Execution Log subtab,, search for the log related to your import detail record.

  4. In the Details column, a message will indicate if there is a pending number of files remaining on the financial institution’s server.

Related Topics

Managing SFTP Connectivity File Imports
Bank Statement File Import
Automatic Bank Statement File Import
Updating Imported Bank Statement Files

General Notices