SAP Business One versions and editions: what UK businesses need to know

Most questions about the SAP Business One version you should run come down to three things: which release your company is on today, how long SAP will keep maintaining it, and what an upgrade will involve for your finance team and your add-ons. This page answers them for UK SMEs, using what SAP publishes, and leaves out anything SAP has not said.

How SAP Business One is organised

SAP Business One is SAP's ERP for small and mid-sized companies. SAP says it is used by more than 83,000 customers and 1.2 million users, in more than 170 countries, in 28 languages and with 50 country localisations. It is sold through 850 partners, with more than 500 industry and country extensions on offer.

That last point matters for versions. You do not buy SAP Business One from SAP directly: a partner sells, implements and supports it. The partner is therefore the person who tells you what is installed, what is supported and what an upgrade would touch in your own system.

Editions of SAP Business One: what actually differs

People often search for "SAP Business One editions" expecting a Basic, Standard and Premium ladder, as with some competitors. SAP's published maintenance and upgrade information does not describe such a ladder. It describes one product, delivered as versions and updated through feature packages. In practice, the differences between two SAP Business One systems come from other places:

If a salesperson uses the word "edition", ask what exactly it covers: licences, database, hosting or version. The answer changes the quote, and it changes the risk at upgrade time.

The version line: from 8.8 to 10.0 and what comes next

SAP's maintenance page lists the families your company may still meet in the field. Versions 8.8, 8.81, 8.82, 9.0, 9.1, 9.2 and 9.3 have finished their standard maintenance period. Version 10.0 is in standard maintenance until 31 December 2028, and SAP notes that dates are subject to change.

The same page says that version 11 will follow version 10. It gives no release date. Until SAP publishes one, treat version 11 as a direction rather than a plan, and do not delay an upgrade or a new project while waiting for it.

What "latest version" really means

The question "what is the latest version of SAP Business One" has a slightly misleading answer. The latest major version is 10.0, but a company on 10.0 can be at very different levels of functionality depending on the feature package installed. Since April 2020, SAP has delivered innovation continuously through cumulative feature packages instead of waiting for a new major release. A feature package brings new features, fixes, security patches and legal updates. SAP also states that interfaces stay stable between the major version and its feature packages, which is good news for add-ons and integrations.

So when you ask your integrator which release you are on, ask for two answers: the major version and the feature package level.

Feature packages, support packages, patches and hotfixes

SAP distinguishes several kinds of update, and mixing them up causes confusion in support calls:

One rule deserves attention. SAP does not provide corrections or security patches for old feature packages, support packages, patches or hotfixes. A company can be on a supported major version and still be running a package that no longer receives fixes. For a business that handles payroll and VAT data, that is a risk to check at least once a year.

How long is a version supported?

SAP guarantees at least five years of standard maintenance for each family of SAP Business One versions. The period starts at general availability of the major release, the x.0 version, and later functional deliveries within the family are covered.

For a finance director, the practical reading is simple:

• the support clock is set by the major version, not by the date you installed it;
• a company that went live late in a family's life gets fewer years of cover than it might assume;
• the end of standard maintenance should appear in your IT plan and your budget a good while beforehand.

Do not rely on a figure remembered from a sales presentation. The maintenance page on SAP's support site is the reference, and your integrator should show you where your own version stands against it.

When should a UK company upgrade?

An upgrade is rarely urgent on a given day, but several situations make it sensible to plan one:

1. Your version has left standard maintenance. This is the clearest signal. Fixes and legal updates stop reaching you.
2. Statutory change is coming. Tax and payroll rules in the UK move, and so does the way software must connect to HMRC. Read Making Tax Digital and your ERP and ask your integrator how your current release handles it.
3. An integration needs a newer release. Banking, e-commerce, EDI or reporting tools may require a minimum level.
4. You are changing your hosting. A move to a hosting provider is a natural moment to bring the system up to date as well. See hosting and cloud options.
5. Your year-end calendar allows it. Many UK businesses avoid upgrading close to the end of the financial year or a VAT quarter.

Your accountant should be told the timing, since an upgrade can affect reports, period locks and audit trails.

How an upgrade works

SAP's rules shape the route:

• Direct upgrades only between consecutive versions. The example SAP gives is 9.3 to 10.0. A company further behind needs several steps.
• Upgrades are free of licence charge for customers with valid maintenance. SAP supplies the new version to such customers at no cost. Maintenance contracts, and what they cost, are covered under support and maintenance.
• Feature packages are lighter. Moving to a newer feature package inside version 10.0 is a smaller job than a major version change, thanks to the stable interfaces SAP describes.

A typical upgrade project covers:

1. an inventory of the current version, feature package, add-ons, custom fields, reports and integrations;
2. a test copy of the production database, upgraded and checked by the people who use it;
3. a review of add-ons, since each one needs a build that matches the target release;
4. a dress rehearsal and a go-live plan agreed with finance;
5. a short period of attentive support after go-live.

The size of that project depends on how much you have customised. A near-standard system upgrades more easily than one with years of bespoke development. If you are weighing that trade-off, customisation in SAP Business One explains where the risk sits.

Upgrade or migrate?

Sometimes the upgrade path is longer than the benefit. When a company is several versions behind, carries heavy custom code or wants to change its structure at the same time, moving data into a clean installation can be simpler than stepping through every intermediate release. Our page on migrating to SAP Business One sets out that decision, and the general ERP migration guide covers the questions to ask whichever product you use.

Questions to put to your integrator

Before you agree to an upgrade or a new installation, ask:

• Which major version and which feature package are we on today?
• When does standard maintenance end for our family of versions?
• Which of our add-ons and integrations must change for the target release?
• Is the route direct, or does it need intermediate steps?
• Who tests, who signs off, and when is the cut-over, relative to our VAT and year-end dates?
• What does the position look like for UK specifics: VAT, Making Tax Digital and payroll reporting? The page on SAP Business One in the UK gives context.

Finding an integrator for the job

Version questions are easiest to settle with a partner who knows your system. ERP Integrator is a free service: you describe your project and we put you in touch with a certified integrator suited to it. We are not affiliated with SAP, and the integrator carries out the work. How it works explains the steps.

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.