-
BAI2 Transaction Code 856 fails in Automatic Bank Statement Import - Format Profile
I'm trying to set up Automatic Bank Statement Import, and I encountered a problem that prevents us from importing a Bank of America BAI2 file: 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…
-
Auto Bank Statement Import (ABSI) Banks
We are exploring the use of the Auto Bank Statement Import (ABSI) SuiteApp to automatically import bank statements into NetSuite for multiple Indian bank accounts. However, we have a few questions regarding its functionality and setup. Is there any cost for the Auto Bank Statement Import (ABSI) SuiteApp? Are all banks,…
-
ABSI - handling encrypted files
The following mentions that the ABSI (Auto Bank Statement Import) cannot decrypt PGP files: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159004446906.html My questions: 1. Can it handle any other types of encrypted files (other than PGP)? 2. If it can't decrypt now, will the functionality be…
-
NetSuite Admin Tip | Resolve Error: “Record Not Saved” in Format Profile > Account Linking subtab
Setting up the Bank Feeds SuiteApp and Auto Bank Statement Import in NetSuite can greatly simplify your bank reconciliation process by automatically importing transaction data from your financial institutions. This reduces manual work, improves data accuracy, and enhances overall efficiency. As part of this setup,…
-
New to NetSuite | Resolve Error: “Record 'customrecord_absi_file_import_sftp' was not found" in ABSI
Scenario: A user manually initiated the bank import process by clicking the ‘Update Imported Bank Data’ button in the Match Bank Data page, intending to retrieve new bank transactions. However, upon reviewing the Banking Import History, it was observed that the import process failed. The failure was accompanied by the…
-
New to NetSuite | Troubleshooting ABSI Error in NetSuite: File was already uploaded.
Another common error that NetSuite users may encounter when using Auto Bank Statement Import (ABSI) via SFTP is as follows: "There was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded.” Possible Causes of This Error Timing Mismatch Between File Upload…
-
New to NetSuite | Troubleshooting ABSI Error in NetSuite: No files were uploaded.
When using Auto Bank Statement Import via SFTP in NetSuite, users may encounter the following error: “There was a problem connecting to your financial institution. The file name in the configuration record did not match any bank statement file names. No files were uploaded.” This issue is explained in SuiteAnswers Article…
-
How to receive an error when a Bank Import fails?
Hi, We use the ABSI SuiteApp and also use sFTP so we import our bank statements automatically every day. Sometimes when there are no transactions, there is no file to import but still NetSuite tries to import it and then we receive this error - "There was a problem connecting to your financial institution. The file name in…
-
Auto Bank Statement Import (ABSI) SuiteApp is importing only one statement on each schedule
Hello Gurus, I'm trying to automatically import bank statements through ABSI SuiteApp. I have configured Format Profile with SFTP Connectivity and CAMT053 parser. In the account linking subtab I have 30+ linked accounts. But when ABSI starts its automatic import schedule, only one statement file is imported. Is this…
-
ABSI - Change import schedule
Hello, We've been using Auto Bank Statement Import to retrieve bank statement from the Bank. Now there is a need to schedule the import differently for our office globally. What are the options to have different import schedule? Thanks,