RSMUS.comNetSuite’s release cycle continues to accelerate innovation—but with that progress comes an increasing need for organizations to stay ahead of platform changes that can materially affect integrations, reporting, and day‑to‑day operations.
The 2026.1 release introduces several breaking changes, behavioral shifts, and formal deprecations that require immediate attention. For organizations relying on custom integrations, third‑party vendors, or legacy SOAP‑based services, these updates are not optional considerations—they are operational requirements.
Below is a practical breakdown of the most impactful changes, along with guidance on where clients should focus now to avoid upgrade‑related disruptions later.
Critical and breaking changes
The following updates can break existing workflows or integrations upon upgrade if not remediated in advance.
Journal line Sublists are now keyed
All journal types now use keyed sublists, enforcing stricter line‑level uniqueness.
Integrations using REST, CSV, or SOAP that reuse the same line identifier across multiple journal lines may fail validation. Clients should review and test all journal‑line update processes before upgrading to ensure line identifiers remain unique.
Item Subrecord Script IDs have changed
To comply with NetSuite’s 40‑character limit, several item subrecord script IDs have been shortened.
Any SuiteScript, SuiteQL, or SuiteAnalytics Connect queries that reference the old script IDs will fail. Clients must update all references to the new IDs documented in SuiteAnswers #1025032.
NetSuite.com ODBC Data Source Removed
The legacy NetSuite.com ODBC data source is no longer available after upgrade.
All SuiteAnalytics Connect queries must now use NetSuite2.com. Organizations that have not already migrated should do so immediately to avoid reporting interruptions.
Custom Tool Script SDF Object Renamed
Custom Tool Script definitions have changed:
- SDF object renamed from tool to toolset
- Script ID prefix updated from customtool_ to custtoolset_
- Attribute exposeto3rdpartyagents renamed to exposetoaiconnector
All existing Custom Tool Scripts must be updated to reflect these naming changes to avoid deployment failures.
Address Subrecord Filtering Behavior Updated
Address sub records are now filtered to include only those linked to the specific parent record.
Integrations that previously relied on unfiltered or cross‑entity address results should be reviewed and adjusted to align with this updated behavior.
SOAP Endpoint End‑of‑Life Acceleration
NetSuite 2025.2 is the last planned SOAP endpoint.
Clients should upgrade SOAP integrations to version 2025.2 immediately. In parallel, organizations should begin coordinating with third‑party vendors to migrate existing SOAP web services to REST Web Services by 2029.1. All new integrations should be built using REST.
Automated Bank Statement Import Enhancements
The Auto Bank Statement Import SuiteApp received several quality‑of‑life improvements:
- Notifications can now be sent to specific emails for errors—and optionally for successful imports
- Custom daily schedules are supported
- Multiple imports per day are now possible, recurring every six or 12 hours
While no remediation is required, clients should review existing configurations to take advantage of these enhancements.
Bill Capture Currency Sourcing Change
The default currency‑sourcing behavior for Bill Capture has changed.
Clients already live on Bill Capture should validate this preference to confirm it still aligns with their expected workflow. This review should be included in any 2026.1 upgrade discussion.
Deprecations and upcoming End‑of‑Life items
While the following changes are not immediate blockers, they require proactive planning to avoid future disruption.
Token‑Based Authentication for New Integrations
Timeline: 2027.1
No new integrations will be permitted using token‑based authentication (TBA) for SOAP, REST, or RESTlets. Existing TBA integrations will continue to function, but all new integrations must adopt OAuth 2.0.
PKCE Required for OAuth 2.0 Authorization Code Grant
Timeline: 2027.1
All new OAuth 2.0 authorization‑code integrations must include PKCE parameters for both public and confidential clients.
SOAP Web Services Gradual Retirement
Timeline: Through 2028.2
Support for new SOAP integrations ends in 2027.1. The 2025.2 SOAP endpoint remains supported through 2028.1. All SOAP integrations must migrate to REST Web Services by 2029.1.
Banking Error Handling Standardization
Timeline: Future release
Free‑text banking failure reasons will be replaced with standardized error codes. Banking plug‑ins should plan to adopt the new error Code and add Error APIs.
JDBC Driver Upgrade
Timeline: Immediate
Upgrading to JDBC driver version 8.10.184.0 is strongly recommended to address known security vulnerabilities.
Planning ahead
These changes reflect a broader NetSuite trend toward tighter validation, stronger security models, and a continued move away from legacy integration patterns. Organizations that proactively assess their integrations, engage vendors early, and incorporate these updates into their upgrade planning will be far better positioned to minimize disruption and support future growth.
Take action before upgrading
NetSuite 2026.1 introduces breaking integration changes and accelerated end‑of‑life timelines that can disrupt operations if left unaddressed.
Connect with an RSM NetSuite specialist to assess your environment, identify risk areas, and build a proactive remediation plan ahead of your upgrade.
Tyler Foss
Tyler Foss is the Manager of Application Development and Integration in RSM’s Central Region, leading teams responsible for designing, customizing, and implementing NetSuite solutions. He brings nine years of integration development experience with deep expertise in the NetSuite API, including SuiteTalk, REST, RESTlets, and SuiteScript‑driven integration patterns. Tyler focuses on delivering reliable, high‑performance solutions that consistently meet client expectations while adhering to NetSuite’s performance standards.