Custom Scheduling for Automated Bank Transaction Imports ...

Updated for February 23, 2026, adding payment date prediction and email notification controls.

·6 min read·3 views·View Oracle Docs

FEATURE: Custom Scheduling for Automated Bank Transaction Imports

CATEGORY: Banking

NetSuite's 2026.1 release introduces a game-changer for managing bank transaction imports. With custom scheduling for automatic imports, businesses can now align transaction import timing with specific business needs and bank data availability. Starting in NetSuite Weekly Update February 23, 2026, this feature now supports payment date prediction for invoices, enhancing your ability to manage cash flow more effectively.

Understanding Custom Scheduling in NetSuite

Before 2026.1, automated bank imports were limited to a single, daily window. These imports occurred anywhere from 4:00 AM to 7:00 AM Pacific Time, potentially leading to delays in data reconciliation. With the new feature, administrators and developers now have the power to define import schedules that best suit their operations.

Key Components of the Import Schedule

  • Frequency: Set how often your imports occur, from daily to specific intervals.
  • Interval: Choose the time unit (days, weeks, etc.) for repeated imports.
  • Start Date and Time: Define when your first import should start.
  • Time Zone: Select the preferred time zone to ensure imported data aligns with your local work hours.

These configurations ensure that bank data is available when needed, streamlining reconciliation processes and enhancing financial accuracy.

Configuring Import Schedules

Accessing Financial Institution Records

  1. Navigate to Setup > Accounting > Financial Institution > List in NetSuite.
  2. Select or create a financial institution to open its record.

Setting Up a New Import Schedule

  1. Within the financial institution record, switch to the Format Profile tab.
  2. Ensure the Profile Type is set to 'Bank Reconciliation' and the Connectivity Method is not 'Manual Import'.
  3. Fill the Import Schedule Subtab with either default values or custom entries.
  4. Link Accounts: A GL account must be linked under the Account Linking subtab to activate scheduling.

Tips for Effective Scheduling

  • Utilize the Manage Import Schedules button on the Match Bank Data page for quick navigation.
  • Although scheduling can be set for inactive profiles, imports will not execute until these profiles are activated.
  • Partial schedule entries are invalid; ensure completeness in your schedule setup.

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, contact NetSuite Support to request activation. After support has activated the feature, you can enable it at Setup > Company > Setup Tasks > Enable Features under the Accounting subtab. 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.

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.
  • Predicted Overdue Days (system-generated): Displays the predicted number of overdue days when payment is expected after the due date.
  • Predicted Payment Date Availability (system-generated): Displays whether a prediction is available for an invoice.
  • Predicted Payment Date Last Updated (system-generated): Displays the most recent update to the predicted payment date.

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.

Version History

  • 2026.1: Introduced custom scheduling for automated bank transaction imports.
  • Weekly Update February 23, 2026: Added Payment Date Prediction for Invoices and Enhanced Controls for Import Email Notifications.

Key Takeaways

  • NetSuite's flexible scheduling allows for more timely bank data updates post-2026.1.
  • Import scheduling is accessible only when the Profile Type is set to 'Bank Reconciliation' and relevant accounts are linked.
  • The scheduling interface provides defaults, but customization is encouraged for more tailored operations.

With these new scheduling capabilities, NetSuite users can significantly improve their banking processes and focus on strategic financial management rather than manual reconciliations.

Frequently Asked Questions (4)

How can I ensure bank transaction imports are aligned with my local work hours?
You can select your preferred time zone when setting up the import schedule. This ensures that imported data aligns with your local work hours, providing more timely updates and streamlining reconciliation processes.
What happens if I set up an import schedule for an inactive profile?
Imports will not execute until the profiles are activated. Scheduling can be done for inactive profiles, but they must be activated to begin functioning.
How do I enable the Payment Date Prediction feature in NetSuite?
To enable Payment Date Prediction, contact NetSuite Support to request activation. Once activated by support, enable it under Setup > Company > Setup Tasks > Enable Features in the Accounting subtab with Administrator role access.
Which permissions are necessary to manage import email notifications for file uploads?
The 'Import Online Banking File (Create or Full)' permission is required to manage notifications for file upload success and error events.

Weekly Update History (1)

Bankingadded

Added an entry for Custom Scheduling for Automatic Imports.

View Oracle Docs
Source: Custom Scheduling for Automatic Imports Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?