Updating Connectivity Plug-ins for Import Error Codes

This procedure provides a generic approach for updating your Financial Institution Connectivity Plug-in to use standardized import error codes when raising exceptions. Implement this update to ensure that import failure reporting in NetSuite is actionable and consistent.

Note:

Standardized error codes will be adopted by the Bank Feeds SuiteApp in a phased rollout, beginning with Yodlee in the upgrade targeted for March 11, 2026. Support for MX and Salt Edge is planned for a subsequent release in April 2026. Until these upgrades, only custom or third-party plug-ins that have been updated as described in this topic will surface standardized error codes.

To update your connectivity plug-in to use standardized error codes for import-level errors:

Identify all import-level exception cases.

Review your plug-in's parseData function and any code that handles overall import failures. Examine all existing error handling in parseData (including all throw, catch, or error-handling statements) that could halt the entire import process (for example, file format errors, connectivity issues, or inactive required plug-ins).
Map each error to a standardized import error code.

For each import-level failure you identify, map it to the corresponding standardized error code listed in Bank Import Error Codes (Reference). Double-check all branches of your error handling, including rarely encountered or edge case errors from your banking APIs. This will ensure that every import-level error scenario is mapped to a standardized error code.
Update your exception-handling logic.

Replace any legacy exception that used a custom error name or free-text message with the standardized approach.

Note:
The provided code samples are examples and should be adapted to your plug-in implementation.

Legacy approach (before standardization):
```
                throw error.create({
    name: 'MY_IMPORT_ERROR',
    message: 'Custom failure reason'
}); 

              
```
Standardized approach (required for standardized error codes):
```
                parseData: function (context) {
    try {
        // Import parsing logic
    } catch (e) {
        throw error.create({
            name: 'BANK_IMPORT_STANDARD_ERROR',
            message: '0000000000'// Use the code that matches the specific failure scenario
        });
    }
} 

              
```
Set the name property to 'BANK_IMPORT_STANDARD_ERROR'.

Set the description property to the standardized error code that corresponds to the failure scenario. For a list of error codes and scenarios, see Bank Import Error Codes (Reference).

Additional Guidance

For additional guidance, do the following:

Test your plug-in to simulate various import-level errors and confirm that the UI displays the expected standardized error codes and messages. For more information, see Conditions for Testing a Financial Institution Connectivity Plug-in.
For details about updating parser plug-ins to use standardized error codes for import-level errors, see Updating Parser Plug-ins for Import Error Codes.
For information about receiving account-level errors, see Updating Connectivity Plug-ins for Account Error Codes.
For information about receiving parser errors, see Updating Parser Plug-ins for Parser Error Codes.

For more information about import error codes or mapping scenarios, see Bank Import Error Codes (Reference). If you need assistance, contact NetSuite Support.

To update your connectivity plug-in to use standardized error codes for import-level errors:

Additional Guidance

Related Topics