Back to Release Notes
SuiteBanking
NetSuite Unknown
2026-04-08

Financial Institution Parser Plug-ins Must Adopt Standardized Error Codes

NetSuite is deprecating free-text exception messages in Financial Institution Parser Plug-ins in favor of standardized errorCode values. Both methods work today, but custom error strings will be removed in a future release.

Affects:Financial Institution Parser Plug-inFinancial Institution Connectivity Plug-inSuiteBanking

What changed

Financial Institution Parser Plug-ins now support a standardized error-handling method alongside the existing legacy approach. The two methods differ as follows:

  • Legacy method — Raise exceptions with free-text message values. These surface as user-facing failure reasons during bank-statement imports.
  • Standardized method — Raise exceptions with predefined errorCode values and a set of required properties. This produces consistent, actionable feedback in the NetSuite UI.

Both methods apply to two error categories:

  • Import-level errors — failures during the file-import step.
  • Parser errors — failures during statement parsing.

The same standardized-code pattern also applies to Financial Institution Connectivity Plug-ins, covering import-level and account-level error codes.

Deprecation timeline

Custom free-text failure reasons will be phased out in a future release (exact version not yet announced). Until then both paths are supported, but Oracle is strongly encouraging immediate migration. The source does not specify which release will enforce the cutoff — monitor future release notes for a hard deprecation date.

What to do

  1. Review Oracle's Bank Import Error Codes (Reference) for the full list of available errorCode values and the scenarios they map to.
  2. In every custom or third-party parser plug-in, replace free-text exception messages with the appropriate standardized errorCode and required properties. Follow the code samples in Updating Parser Plug-ins for Import Error Codes and Updating Parser Plug-ins for Parser Error Codes.
  3. If you also maintain custom connectivity plug-ins, update those separately using the guidance in Updating Connectivity Plug-ins for Import Error Codes and Updating Connectivity Plug-ins for Account Error Codes.
  4. Test in a sandbox by triggering each error path (bad file format, missing fields, authentication failure, etc.) and verify the standardized codes render correctly in the bank-import UI.
  5. Deploy to production before the future deprecation date to avoid broken error messaging once free-text support is removed.

Open questions

The source does not state which NetSuite release introduced this change or which release will remove legacy support. If your organization tracks plug-in compliance, flag this item for follow-up when Oracle publishes the hard-deprecation timeline.

Source: Oracle NetSuite Release Notes

More in SuiteBanking

SuiteBanking
2026.1

Financial Institution Connectivity Plug-ins Moving to Standardized Error Codes

Financial Institution Connectivity Plug-ins must migrate from free-text exception messages to standardized errorCode values. Both methods work today, but custom failure reasons will be removed in a future release.

SuiteBanking
2026.1

Financial Institution Parser: createNewTransaction() Now Supports Category Field

As of 2026.1.12, the createNewTransaction() method in the Financial Institution Parser plug-in interface now supports a category field inside additionalFields, letting plug-in authors pass institution-supplied transaction categories into NetSuite.