Financial Institution Connectivity Plug-ins Moving to Standardized Error Codes

Oracle is deprecating the legacy error-handling pattern used in Financial Institution Connectivity Plug-ins. Today, many custom and third-party plug-ins surface user-facing errors by throwing exceptions with free-text message strings. Going forward, plug-ins must throw exceptions using standardized errorCode values with required properties instead.

What changed

• Legacy method (deprecated): Plug-in raises an exception with a free-text message value. NetSuite displays that string to the user as-is. This applies to both import-level and account-level errors.
• Standardized method (new): Plug-in raises an exception with a predefined errorCode and required properties. NetSuite maps the code to a consistent, actionable message. This also applies to both import-level and account-level errors.
• Parser plug-ins have a parallel change: import-level and parser-level error codes must also be updated to use standardized codes.
• Both methods are supported during a transition period. A future release will remove support for free-text failure reasons entirely — no specific version has been announced.

What is affected

• Any custom or third-party Financial Institution Connectivity Plug-in that throws exceptions with free-text messages.
• Any custom or third-party Parser Plug-in that surfaces import-level or parser-level errors via free-text messages.
• Bank statement import workflows that consume errors from these plug-ins.

What to do

1. Review the full list of standardized error codes in Oracle's Bank Import Error Codes (Reference) help topic.
2. Audit your Connectivity Plug-in implementations. Replace any exception throws that use a free-text message with the matching standardized errorCode and its required properties. Do this for both import-level and account-level error paths.
3. Audit your Parser Plug-in implementations. Apply the same migration for import-level and parser-level errors.
4. Test in a sandbox account by triggering each error path (invalid credentials, unreachable institution, malformed file, etc.) and verifying that NetSuite displays the expected standardized message.
5. Deploy updated plug-ins to production before the legacy path is removed. Oracle has not committed to a specific removal date, so treat this as urgent — you do not want to be caught on a hard cutoff.

Gaps in the source

The release note does not specify the exact SuiteScript module or API surface for the new errorCode property, nor does it list the standardized codes inline. You will need to consult the Bank Import Error Codes (Reference) and the updated plug-in interface definition in NetSuite Help for the concrete enum values and required property shapes. The removal timeline is described only as "a future release" with no version number.