NetSuite 2026.2
Your account’s upgrade timing and enabled capabilities determine which features you can use. Start with the workflows and dependencies affected by the release.
Start with the impact, then read the detail
A release announcement can touch several owners: a finance team exporting reports, a developer maintaining custom scripts, or an administrator preparing authentication changes. Use this hub to identify the relevant topic and build a short, accountable review list.
Our guidance separates documented changes from recommended preparation. A recommendation to test a workflow is a planning step, not a claim that the workflow will fail.
Choose your path
Understand the release
Use Release Notes for the official documentation and Feature Updates for a closer look at changes to everyday work. Record the account version before deciding whether a feature applies.
Protect your connections
Use SuiteCloud & Integrations and Security & Deprecations when you maintain code, development tools or external systems. Bring the notice to the person who owns the affected connection.
Prepare people and processes
Use Release Readiness to organize representative tests and What’s Next to plan for announced future changes. Keep optional adoption separate from required compatibility work.
Keep three kinds of updates in view
Oracle’s documentation distinguishes scheduled version upgrades, monthly enhancements and independently released SuiteApps. A useful review covers the products you actually operate, rather than assuming that every component follows one release date.
Give each relevant item a business owner, a technical owner where needed, a decision and a next review date. That small record is more actionable than a long list of announcements.