↓

Which NetSuite version are you on, and what changes at each release?

The NetSuite version question has a different answer from on-premise software: every customer runs the same release, delivered twice a year. Here is how editions, updates and upgrades work for UK businesses.

Last updated 28 October 2026

If you are used to on-premise software, asking "which NetSuite version do we run?" can feel like asking the wrong question. With Oracle NetSuite, there is no installer to download, no service pack to schedule on a weekend and no old release quietly running in a server room. The platform is delivered as a cloud service, and Oracle moves accounts forward as it publishes each release.

This page explains how a NetSuite version works in practice, what the editions mean, what the latest NetSuite version brings, and how a UK finance team or IT lead should plan around the release cycle. For the cost side, see NetSuite pricing; for the wider product, start with the Oracle NetSuite overview.

How a NetSuite version differs from a traditional ERP release

In a traditional ERP, each company chooses when to upgrade. Some stay on the same release for years, accumulate customisations and then face a large, expensive migration project. That freedom has a price: the further behind you fall, the harder it is to catch up.

NetSuite works the other way round. Oracle's documentation describes the current release, NetSuite 2026.2, as a planned version upgrade delivered twice a year, bringing new features, enhancements and changes across the platform. In other words, the version is a property of the service, not a decision each customer takes alone.

For a UK SME or mid-sized group, this has three practical consequences:

  • No big-bang upgrade project. You do not budget a separate "move to the next version" programme, as you might with an older on-premise product.
  • Testing becomes routine. The effort shifts from migrating to verifying that your customisations and integrations still behave as expected.
  • Release notes become required reading. Someone in your business, or your integrator, needs to own them.

If you are comparing this model with hosted alternatives, the cloud versus on-premise ERP guide sets out the trade-offs in more detail.

NetSuite editions: what they are and what they are not

People searching for NetSuite editions are usually trying to answer one of two questions: "which package do we need?" and "are we getting a cut-down product?". The useful way to think about it is this.

All NetSuite customers run the same platform release. An edition is therefore not an older or lighter software generation. It is the commercial packaging around the platform: the modules included, the number and type of user licences, and optional add-ons. Those elements are fixed in your Oracle contract, and they change as your business grows.

We do not publish edition names, user limits or price points here, because they are set by Oracle and can change. Your integrator should show you the current options in writing and map them to your needs. The table below shows the questions that actually separate one set-up from another.

Question Why it matters Where to look
Which modules are in the contract? Finance is the core, but manufacturing, inventory or HR may be separate NetSuite modules
How many users and of what type? Full users, employee self-service and warehouse staff are priced differently NetSuite pricing
Which subsidiaries or entities are covered? Multi-company UK groups need this settled early Accounting and finance
Which SuiteApps or add-ons are needed? They are published separately and follow their own notes Release notes
What support level applies? Determines who handles upgrade issues Support and maintenance

A sensible rule: do not compare "editions" in isolation. Compare the scope you need against what each package includes, and ask what happens to your price if you add a subsidiary, a warehouse or a manufacturing site.

The latest NetSuite version and what it covers

Oracle's help centre describes NetSuite 2026.2 as the current planned release. Its documentation lists a wide range of areas, and a few are worth picking out because they matter to UK businesses.

Finance and compliance

The release covers the Intelligent Close Manager, bank reconciliation and support for IFRS 18 in accounting. For a UK group reporting under IFRS, the IFRS 18 support is the line to read carefully with your auditors and finance director. For a smaller company reporting under UK accounting standards, the more relevant items are likely to be the close process and reconciliation tools.

Remember that features on a release note list are not the same as a configured, compliant UK process. VAT returns, Making Tax Digital for VAT and the reporting your accountant needs still depend on how your account is set up. Our guide to Making Tax Digital and ERP explains what to check, and the UK page for NetSuite covers local specifics.

Operations and analytics

Oracle also lists capacity planning in manufacturing and an .xlsx export from SuiteAnalytics. If you run production, the capacity planning item is relevant to your scheduling; see NetSuite for manufacturing. Finance teams that live in spreadsheets will welcome the export option, though it does not replace good report design.

Security, AI and development

The release notes mention Ask Oracle, an AI-based help and chat feature, and passwordless authentication with passkeys. For developers, the notes list event subscribers and the SuiteScript LLM module. If your business has custom code, those developer items tell you where the platform is heading. Our page on NetSuite customisation explains how to keep custom work upgrade-safe.

How Oracle organises release information

Oracle splits the documentation for a release into three families, and it helps to know which is which:

  1. Planned release notes. The twice-yearly upgrade, with new features, enhancements and changes.
  2. Monthly release notes. Improvements delivered each month after the planned upgrade.
  3. SuiteApp release notes. Add-ons published separately, on their own timetable.

A PDF version and translated versions exist as well. In practice, most UK teams only need to read the planned notes in full, scan the monthly ones, and check the SuiteApps they actually use.

Support life of a NetSuite version

On-premise vendors publish support end dates for each version, and customers plan around them. NetSuite does not work like that, and we have not found a published support window per release in the documentation we rely on, so we do not quote one. The question to ask is different: "what is our responsibility when Oracle upgrades our account?" The answer sits in your contract and in your support arrangement.

If a business-critical customisation breaks after an upgrade, you need someone who can diagnose it quickly. That is the job of a good NetSuite support and maintenance arrangement, and it is worth agreeing before go-live rather than after the first incident.

Testing before an upgrade: the Release Preview account

Oracle provides a tool that takes much of the risk out of the release cycle. A Release Preview account is a temporary, isolated test account, separate from production, that runs the new version of the software. According to Oracle's documentation, it lets you test:

  • customisations;
  • SuiteScripts;
  • web-services integrations;
  • web stores;
  • SuiteAnalytics Connect access.

A few rules apply. The account is available until your source account is upgraded, or until 14 consecutive days pass without a login, after which it is purged. It is initially open only to administrators, who can then give access to other users. And it is for testing only, never for live work.

A practical testing checklist for UK teams

Work with your integrator and accountant to cover the following before the upgrade date:

  • the month-end close and any scheduled journals;
  • VAT calculations and the data behind your Making Tax Digital submissions;
  • payroll exports and the files your payroll or RTI process depends on, as described in our guide to payroll software and RTI;
  • bank feeds and reconciliation;
  • integrations with your e-commerce platform, bank, payroll bureau or warehouse system, covered under NetSuite integrations;
  • custom reports and saved searches that your directors rely on;
  • user roles and permissions, especially for finance staff.

Assign a named owner for each item. A test nobody owns tends not to happen.

When and how to move forward

Because Oracle schedules the upgrades, "when to upgrade" really means "when to be ready". A workable rhythm for a mid-sized business looks like this:

Stage What happens Who is involved
Before the release Read the planned release notes and list the changes that touch your processes Integrator, finance lead
Preview Test in the Release Preview account Integrator, key users
Decision Fix issues, update scripts, brief users IT lead, department heads
After the upgrade Check live processes, then follow the monthly notes Support partner

Avoid scheduling go-lives or major process changes close to an upgrade. If you are mid-implementation, tell your integrator which release your project will land on; our overview of NetSuite implementation explains how projects are phased.

Versions and migration: moving from another system

A different version question comes up in migration projects. Companies leaving an older ERP, often a legacy Sage installation or a heavily customised on-premise system, ask whether NetSuite will "be the same version" as what they have today. It will not, and that is largely the point: you leave a frozen release behind and join a platform that keeps moving. The NetSuite migration page covers data, cut-over and parallel running, and our general ERP migration guide applies whichever product you choose.

If you already run NetSuite and are unhappy with how the account has aged, the issue is rarely the version. It is more often years of unmanaged customisation. A structured NetSuite audit and project rescue can show what to keep, simplify or remove.

Comparing NetSuite's release model with other ERPs

The twice-yearly cloud release is one reason some buyers prefer NetSuite and others look elsewhere. Odoo, Microsoft Dynamics 365 Business Central and SAP Business One each have their own approach to versions and upgrades, and the differences affect cost and effort. If upgrade control matters to you, read the NetSuite versus Business Central comparison and the NetSuite alternatives page, and ask each candidate how their upgrades are tested and who pays for the work.

What to ask an integrator about versions

Whichever partner you shortlist, put these questions to them:

  • How do you track each release for our account and warn us in advance?
  • Do you test our customisations in Release Preview every time?
  • What is included in support, and what is billed separately?
  • How do you keep custom code upgrade-safe?
  • Who signs off VAT and payroll checks after an upgrade?

The answers tell you more about the quality of a partner than any edition table. Our guide to choosing a NetSuite partner goes further, and how it works explains how we put you in touch with an integrator suited to your project.

Key points

  • NetSuite is one platform, upgraded by Oracle through planned releases twice a year, with monthly improvements in between.
  • The latest release documented by Oracle is NetSuite 2026.2.
  • Editions are commercial packaging, not different software generations; confirm contents in writing.
  • Release Preview is your safety net: use it every time, with named owners for UK-specific checks.
  • Support windows per version are not the right frame; focus on testing, ownership and a good support arrangement.

Frequently asked questions

What is the latest NetSuite version?

According to Oracle's documentation, the current planned release is NetSuite 2026.2. Oracle delivers a planned release twice a year, so the number changes regularly. Your own account is upgraded on a schedule Oracle sets, and your integrator can tell you which release your account is on and when the next one is due.

Can we stay on an older NetSuite version?

No, not in the way you could with on-premise software. NetSuite is delivered as a service, and Oracle upgrades accounts to each planned release. What you control is your preparation: testing customisations and integrations beforehand, reviewing the release notes and planning user communication.

What is the difference between NetSuite editions?

Editions describe the commercial packaging of NetSuite: which modules, user licences and options your contract includes. They do not mean different software generations, because all customers run the same platform release. The exact composition of your edition is set in your Oracle contract, so confirm it with your integrator before signing.

What is a Release Preview account?

It is a temporary, isolated test account that runs the new version of the software, separate from production. You use it to test customisations, SuiteScripts, web-services integrations and web stores before your live account is upgraded. It is removed once your source account is upgraded, or after 14 consecutive days without a login.

How do we prepare a NetSuite upgrade at a UK company?

Read the release notes, list every customisation and integration, and test them in Release Preview. Pay particular attention to anything touching VAT, Making Tax Digital submissions and payroll files, as a failed month-end or filing is the costly outcome. Your integrator or accountant should sign off the results before the upgrade date.

Sources

  1. Oracle NetSuite Help Center – NetSuite 2026.2 release notes
  2. Oracle NetSuite Help Center – Release Preview

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.