1. What's New
  2. Release Notes
  3. NetSuite 2026.1 Release Notes
  4. Banking

Banking

This release note was updated March 16, 2026.

NetSuite 2026.1 includes the following enhancements to banking features:

Enriched Bank Data for Transaction Matching

In both Classic and Next mode, you can now use the Enriched Bank Data feature to improve the accuracy of matching imported bank transactions to your general ledger in NetSuite. Generative AI automatically extracts entity information from the memo andI like this payee or payor fields of imported bank transactions, resulting in better matching for ambiguous or previously unmatched transactions. The matching step itself does not directly use AI.

After all system and custom rules have been applied, any transactions that remain unmatched are eligible for enrichment-based matching. This process identifies matches with the same amount, a transaction date within seven days, and similar extracted entity information. Enrichment-based matching runs during bank data import and when reconciliation rules are rerun manually. Transactions already matched by system or custom rules aren't considered.

Matched transactions display a multicolored vertical line next to them on the Match Bank Data and Reconcile Account Statement pages. The match details popup indicates when a match is enrichment-based.

This feature is enabled by default. You need the same permissions required to access the Match Bank Data page and to import bank data. To change the feature's status, sign in as Administrator and go to the Accounting subtab under Setup > Company > Setup Tasks > Enable Features.

For more details, see Enriched Bank Data for Transaction Matching.

Note:

Matches that use entity information extracted by generative AI could be erroneous. All matches should always be reviewed before finalizing reconciliation.

Payment Date Prediction for Invoices

In both Classic and Next mode, you can now view predictions for when customers are expected to pay invoices. These predictions are generated using machine learning and are available on the Invoices page and invoice forms.

Note:

Payment date predictions use machine learning models based on historical payment data. These predictions are estimates, not guarantees. Use this information as a helpful planning aid, but always consider additional business context and judgment.

To enable the Payment Date Prediction feature (disabled by default), go to Setup > Company > Setup Tasks > Enable Features and open the Accounting subtab (support activation no longer needed). The Administrator role is required. Predictions are updated periodically for all open invoices. The initial set of predictions may take up to one day to appear after enablement.

To generate predictions, your account must include at least 12 weeks of historical payment data and at least 50 paid invoices that occurred before the start of that 12-week period.

Note:

This feature is not supported on Release Preview accounts.

When the feature is enabled, the following new read-only fields appear on the invoice form. For custom invoice forms, you need to manually enable these fields in Customization > Forms > Transaction Forms (Administrator role required).

  • Predicted Payment Date (generated by AI) - Displays the date when payment is likely, based on historical customer payment patterns using AI. Appears on the invoice record and the Invoices page.

  • Predicted Overdue Days (system-generated) - Displays the predicted number of overdue days when payment is expected after the due date. Appears on the invoice record and the Invoices page.

  • Predicted Payment Date Availability (system-generated) - Displays whether a prediction is available for an invoice. Appears on the Billing subtab of an invoice.

  • Predicted Payment Date Last Updated (system-generated) - Displays the most recent update to the predicted payment date. Appears on the Billing subtab of an invoice.

You can also manually enter payment estimates in the Billing subtab of an invoice. These fields are always visible and editable even if the Payment Date Prediction feature isn't enabled:

  • User-Estimated Payment Date (manual entry) - Enter your estimated payment date, if known.

  • User-Estimated Payment Date Source (manual entry) - Specify the source for your estimate, with options like Company Estimate or Customer Promised Date. This field is required when you enter an estimated payment date. The field is automatically cleared if the estimated payment date is removed.

For more information about payment date predictions, see Payment Date Prediction for Invoices.

Enhanced Controls for Import Email Notifications

You now have improved flexibility and visibility into how email notifications are sent for both automatic imports and file uploads. Notification delivery varies based on the import type, your configured preferences, and permission settings.

For automatic imports using a format profile, you can assign a Notification Email address (designated email address) to receive both success and error notifications. To access a format profile, go to Setup > Accounting > Financial Institution. Select a financial institution and click View. Under the Format Profile: Configuration subtab, select an existing format profile.

  • On successful import, notifications are sent to the designated email if Send Success Messages Too (Failure Messages Are Always Sent) is enabled.

  • On error or partial success, notifications are always sent to the designated email, regardless of the success notification setting.

  • If no designated email is set, notifications may be sent to other recipients. These include the format profile creator (if their user notification preference is enabled) and the company's return email address (if enabled by the administrator). The format profile creator receives notifications as a fallback if all other options are opted out.

  • You may receive multiple notifications if both user and company preferences are enabled.

For file uploads, the following is true:

  • The designated email address in the format profile is not used for file uploads.

  • On success, notifications go to the user who performed the upload if their notification preference is enabled.

  • On error or partial success, the user who performed the import always receives the notification, and they cannot opt out.

  • The company return email address also receives notifications if company-level notification is enabled, for both success and error scenarios.

Configuration and Access Requirements

  • The Notification Email field and Send Success Messages Too (Failure Messages Are Always Sent) box in the format profile are set by the profile owner or editor. These options are only available if the profile type is Bank Reconciliation and the connectivity type isn't Manual Import.

  • User notification preferences are configured at Home > Set Preferences and include the following:

    • Notify Me Of Successful Manual Bank Imports

    • Notify Me Of Successful Automatic Bank Imports

    • Alert Me Of Issues With Automatic Bank Imports

  • The company return email and related notification settings are managed by the administrator using company-wide notification preferences at Setup > Company > General Preferences. The company return email is an address set by the administrator for receiving company-level notifications. Four new company-wide notification preferences are available:

    • Email Return Address When A Manual Bank Import Is Done

    • Email Return Address When An Automatic Bank Import Is Done

    • Email Return Address If A Manual Bank Import Has Issues

    • Email Return Address If An Automatic Bank Import Has Issues

  • The following permissions are required:

    • Import Online Banking File (Create or Full) for file upload notifications.

    • Financial Institution Records (Create or Full) for automatic import and related alerts.

If you use a custom workflow for bank import notifications, review your routing and notification preferences to ensure they align with these new behaviors.

Custom Scheduling for Automatic Imports

Starting from 2026.1, you can schedule automated bank transaction imports based on your business needs and your bank's data availability. Previously, automated imports for bank reconciliation occurred only once daily between 4:00 to 7:00 AM Pacific Time. Each format profile set up for bank reconciliation now includes an Import Schedule subtab. You can choose the frequency, interval, start date, start time, and preferred time zone for automated imports. Flexible import scheduling supports timely bank data updates and supports more efficient reconciliation processes.

The Import Schedule feature is available under the format profile of a financial institution record. To access a financial institution record, go to Setup > Accounting > Financial Institution > List.The Import Schedule subtab appears only for profiles with Profile Type field set to Bank Reconciliation. Additionally, the Connectivity Method field must also be set to a connectivity plug-in, not Manual Import.

When you create a new profile, the scheduling fields under the Import Schedule subtab are automatically populated with default values:

  • the unit of time as Day,

  • the frequency as Repeat Every 1 day,

  • and a randomized import time between 4:00 and 7:00 AM Pacific Time.

You can edit the schedule in both new and existing format profiles. Ensure to meet one of the following criteria:

  • All fields are filled, using either the default values or your own values.

  • All fields are left blank. The system will use the default values.

All fields must be either fully completed or left blank. Partial entries are not allowed.

To use the Import Schedule feature, at least one account must be linked to activate scheduling options. If no accounts are linked in the Account Linking subtab, the Import Schedule subtab appears, but its fields remain unavailable. To manage import schedules on the Match Bank Data page, you need to have the Financial Institution Records permission with edit-level access.

With the import schedule feature, you can do the following:

  • Schedule automated imports for each format profile set up for bank reconciliation.

  • View the last successful import date and time in your time zone on the Format Profile and Match Bank Data pages.

  • Use the new Manage Import Schedules button on the Match Bank Data page header for faster navigation and adjustments. This button directly takes you to the appropriate format profile if one is configured. Active profiles are prioritized and listed alphabetically. If no profiles exist, the button takes you to the Financial Institutions page.

If a profile doesn't have account mapping or is set to Manual Import, there is no associated import schedule. Imports don't run until the necessary conditions are met. For inactive profiles, the associated schedule remains paused until the profile is reactivated. The schedule can be edited while the profile is inactive, but imports don't run until the profile is active.

For more information, see Setting Up a Bank Import Schedule.

Control Start Date for Transaction Imports

You can now specify the exact start date for importing transactions from a bank account to linked general ledger accounts. This gives you greater control during account linking setup, ensuring that only transactions within your chosen date range are imported.

A new column, Earliest Transaction Date for Import, appears in the Account Linking subtab of the format profile. This column appears when you select Bank Reconciliation as the Profile Type and a connectivity plug-in as the Connectivity Method. The column displays for each account linking, allowing a unique date to be set for every newly linked account. For each new account linking, the default date is set to 60 days before the current date. You can adjust this to any date within the available 60-day range.

Note:

The following SuiteApps do not currently support configuring the earliest transaction date for imports. Instead, the date is fixed at 60 days prior to the current date. The related field and column do not appear in format profiles that use these SuiteApps:

  • Australia Bank Feeds

  • Auto Bank Statement Import

  • Brazil Banking Integration

If you're setting up multiple new account linkings, you can set the same date across all your new linkings. To do so, use the Earliest Transaction Date for Import (All Accounts) field and the Apply button. This makes configuration easier at scale.

Important:

After you save the format profile and the initial import is completed, you can't edit the Earliest Transaction Date for Import for account linkings. The only exception is when the linked account is changed in NetSuite. When you add a new bank account using the connectivity plug-in, you can set the start date as part of linking the account in NetSuite.

The mass update action affects only newly created account linkings. Existing linkings remain unchanged.

Warning:

Setting a future date as the earliest transaction date is permitted, but it may result in missed or unexpected transaction import timing. You should only set a future date if you specifically want to delay your initial import. When you set a future date, no transactions are imported until a scheduled import occurs on or after the future date. At that point, the system imports all transactions received between the day after the format profile was created and your specified future start date. This may result in a high volume of transactions being imported at the same time.

If all account linkings are set with a future start date, the initial import doesn't occur at save. If at least one account linking uses today or a past date, the initial import occurs immediately after saving.

To access this feature, go to Setup > Accounting > Financial Institution, select or create a format profile for bank reconciliation, and open the Account Linking subtab.

For more information about this feature, see , Creating Format Profiles for Bank Reconciliation.

Update Imported Data for Connected Accounts On Demand

You can now impsmaller ort the most recent transaction data from your Account Information Service Provider (AISP) for connected accounts on demand. Examples of AISPs include Yodlee, MX, Salt Edge, and American Express. This feature supports bank reconciliation and corporate card expenses. This feature is available after the required plug-in updates have been implemented (see the For Plug-In Developers section).

Note:

This feature is now supported for bank reconciliation in Bank Feeds SuiteApp version 26.1.0. For details, see Updating Imported Bank Feeds Data.

For corporate card expenses, the AMEX Corporate Card Integration SuiteApp supports on-demand updates, but with certain limitations (see the Limitations section).

Previously, scheduled imports occurred once daily and included only data already available from your AISP. With this enhancement, if supported by your plug-ins, you can prompt the system to update transaction data from your AISP and initiate an import. This ensures your records are as current as possible.

A new Update Imported Bank Data button is available at the top of the Format Profile page when in view mode. Using this button initiates an on-demand import for all connected accounts configured in the format profile, if your plug-ins support it. This action updates your records with the latest data for reconciliation or review. If the required plug-in methods aren't implemented, clicking Update Imported Bank Data imports only data already available from your AISP.

To access this feature, go to Setup > Accounting > Financial Institution. Select a financial institution record and click View. In the Format Profile: Configuration subtab, select an existing format profile or click Add to create a new profile. The Update Imported Bank Data button appears at the top of the Format Profile page when in view mode.

You can continue to use the existing Update Imported Bank Data button on the Match Bank Data page to update imported data for a specific account.

For format profiles scheduled for automatic imports every 6 or 12 hours, the system now automatically initiates data updates on that schedule, if your plug-ins support it.

Limitations

For Corporate Card Expenses format profiles, the AMEX Corporate Card Integration SuiteApp uses a file-based process. You can use the AMEX Connectivity Plug-in to update data, but it will only update data if a new file is already available from American Express. The plug-in can't request a new file from American Express at the time of import, so updated data may not always be available. The SuiteApp doesn't perform real-time refreshes or request new files from American Express.

Error Handling

If a data update can't be completed for one or more accounts, you may see new account-level error messages related to update failures. For more details about the new standardized error codes, see Standardized Error Codes for Imports.

For Plug-In Developers

The Financial Institution Connectivity Plug-in now supports new methods for importing the latest data, which can be used for custom plug-in implementations:

  • Implement the refreshData(context) method to enable on-demand data updates. For more information, see refreshData(context).

  • For Corporate Card Expenses profiles, also implement getRefreshRequestStatus(context) to support data import status checks. For more information, see getRefreshRequestStatus(context).

Standardized Error Codes for Imports

Standardized error codes and clearer messages are available for bank import failures when supported by your connectivity and parser plug-ins. Standardized error codes and messages are replacing plain-text failure reasons across overall imports, account-specific imports, and file parsing errors. This provides you with more consistent and actionable feedback.

Important:

As of March 11, 2026, standardized error codes for Yodlee connections are supported in Bank Feeds SuiteApp version 26.1.0 (or later). Support for MX and Salt Edge is planned for a subsequent release in April 2026.

The removal of free-text failure reasons is targeted for NetSuite release 2026.2, beginning in August 2026. Upgrade dates may vary by customer account and region. Custom or third-party plug-ins should be updated before your upgrade to use standardized error codes and messages. SuiteApp-provided plug-ins are updated through SuiteApp upgrades. For more details, see the Requirements section.

If you see a free-text failure reason, a warning indicates that these are being phased out. The warning is visible if you have Edit access for the Financial Institution Records permission.

You'll see standardized error codes and messages on three pages, depending on your setup. Free-text failure reasons continue to appear for plug-ins or connections that don't yet support standardized error codes.

Banking Import History Page

The Banking Import History page (Transactions > Bank > Banking Import History) now displays standardized error codes for import-level, account-level, and parser plug-in errors. In failed or partially completed imports, error messages associated with each code appear, as well as a list of affected general ledger accounts. Free-text failure reasons continue to appear for plug-ins that have not yet been updated. To improve performance, import failure details now load only when you expand a row.

Format Profile Page

On the Format Profile page, the Account Linking subtab now displays standardized account error codes from your selected connectivity plug-in. Errors appear as a tooltip when you hover over the error icon in affected account rows. Free-text errors continue to appear for plug-ins that haven't yet been updated.

Match Bank Data Page

The account status growl message on the Match Bank Data page (Transactions > Bank > Match Bank Data) now displays standardized errors for general ledger accounts. The system prioritizes account-level and parser errors over import-level errors. If multiple errors exist for an account, you're prompted to review details on the Banking Import History page.

Default Parser Enhancements

Default BAI2 and CSV parsers now automatically report parser-level errors in addition to import-level errors, with no parser plug-in updates required. If multiple issues are found in a file, these errors are captured and displayed on the Banking Import History page. Errors are often shown with line number and position to support more precise troubleshooting. Default parsers now catch exceptions and convert them into parser errors, improving error detail and increasing resilience.

Requirements

If you use custom or third-party connectivity and parser plug-ins, those plug-ins need updating. If you have the administrator role, contact your plug-in author to do the following. Otherwise, contact your administrator for help.

  • Update your custom or third-party connectivity plug-in to use the new errorCode field (replacing failureReason) for account errors.

  • Update your custom or third-party parser plug-in to use the new addError API for reporting parsing errors.

  • Update your custom or third-party connectivity and parser plug-ins to use the new method for throwing exceptions that include standard import-level errors.

For more information, see the following help topics:

For a list of all standardized error codes, scenarios, and messages, see Bank Import Error Codes (Reference).

Enhanced Presentation of To Be Generated Transactions During Bank Reconciliation

NetSuite has enhanced the presentation of transactions that auto-create rules suggest during bank matching and reconciliation. Previously, the review experience displayed less context. The Review tab and the side-by-side details modal on the Match Bank Data and Reconcile Account Statement pages now display more transaction context and clearer statuses. You can more easily review and verify general ledger transactions generated by auto-create rules.

A new GL Account column is available on the Review subtab of the Match Bank data page and Reconcile Account Statement page. The column is only visible if an auto create rule is active and displays a GL account for impacted rows. The account name is a clickable link that opens the respective GL account page.

In the side-by-side Matched Transaction details modal, the Imported Bank Data grid includes Memo. The Account Transactions grid includes Memo and may display Department, Class, and Location when any of those segments are populated on the transaction. A GL Account column is also available only when the auto-create rule is active.

On Match Bank Data page, the View Details column for To Be Generated transactions displays the transaction type ( for example, Deposit to Be Created instead of Matched). On the Reconcile Account Statement page, the View Details column for rows generated by auto-create rules displays Created andMatched.

Transaction Category Support for Imported Transactions in Financial Institution Parser Plug-in

Note:

This update is intended for plug-in authors and does not impact end-user UI or behavior right now. Existing integrations continue to work as before if no transaction category is supplied.

NetSuite has enhanced the Financial Institution Parser Plug-in to capture an optional transaction category for each imported banking transaction. Plug-in authors can provide a category value through the API by including a category field in the additionalFields parameter when calling createNewTransaction. For more details, see createNewTransaction().

If a transaction category is supplied by the financial institution as part of the transaction data, NetSuite stores the category value in each imported transaction record. The category is not visible in the UI and can't be used yet. Storing this data now enables future enhancements in transaction matching.

Plug-in authors are encouraged to begin including the category field when importing banking data to prepare for future functionality.

General Notices