Summary
Description
Sage is committed to keeping our customers secure and making sure we reduce threats and take advantage of the latest technology, meaning from time to time we need to upgrade the underlying components of our products.
We have 3 key changes within Sage 200 that will require action from you to ensure our customers continue to receive a secure uninterrupted service. The planned changes affect our TLS security protocol, Sage ID & Banking services.
Resolution
IMPORTANT UPDATE: Please see the following Communication relating to the release of additional patches for Sage Licence Service, TLS and Internet Explorer.
What Does This Mean for My Business & Customers?
Steps, including upgrades, will need to be completed by key dates to ensure the software continues to work & services aren't disrupted. The steps you’ll need to take vary depending on a customer’s Sage200 version and / or connected services combination and will range from a registry change to reinstalling or upgrading the product.Versions from 2013 upwards, regardless of Sage 200 product variation are impacted in some way so it’s important to review our detailed guide to determine the next steps. To limit the impact to our partners & customers we’re sharing this information with you simultaneously to allow you to take a single set of steps and best plan for your customers.
TLS is a security protocol required for services such as Sage ID and the Sage License Service. TLS (Transport Layer Security) is a widely adopted security protocol designed to facilitate privacy and data security for communications over the Internet
What are the upcoming changes?
- TLS 1.0 / 1.1 is due to be deprecated from our product range to ensure customers are taking advantage of new technology. The Sage 200 application uses TLS as does a variety of our connected services including Sage CRM. Action will be required depending on the version of the software and the connected services they use.
- Sage ID: Sage ID is transforming. Sage is undergoing a transformation to a new system which is an underpinning strategy for our future identity. Sage ID will support new standards such as JWT (JSON Web Token) and Open ID and will replace our current Sage ID offering. This means any customers using Sage ID via core product or connected feature(s) will need to take action to ensure no disruption to their service.
- Sage ID connected services include the Sage API, WebSOP and Salary & Supplier Payments. If you use any of this funcionality please see your version for action required below.
- Banking and Bank feeds: Our banking service will be involved with 3 key changes, TLS, Sage ID and new legislation (Open Banking). The date by which action needs to be taken will depend on which elements the customer uses and their current software version.
- For Open Banking, customers will fall into 1 of 3 key pots and we’ll contact you regarding the customers impacted to advise of the necessary steps for this element.
- Bank is Open Banking Ready: re-enter your banking credentials by 14 March 2020, the software will prompt for these details from 03 March 2020, we have created an article to assist you with this.
- Bank is Open Banking Ready – technology change required: Some of the banks involved in Open Banking require technology changes. Once the software has been updated, simply re-authenticate your service.
- Bank is not Open Banking Ready - Unfortunately, some connections are not Open Banking ready. Existing connections will continue to work until 14 March 2020. Click here to view the screens a customer would see in this scenario. Check the latest status for banks at www.sage.com/OpenBanking
We have created this article to remind you of your options in the event of a loss of feed.
What are the key dates?
- Banking: Anyone using open banking will need to take action by 09 March 2020.
- Sage ID: Using this service will require action before 30 August 2020.
- TLS: The date varies depending on which connected service is being used, please refer to our article for further details.
Sage Licensing Service:
- 2013 / 2015 / 2016 versions action required by 30 Sept 2021
- Summer 2017 version action required by 30 Sept 2022
- Winter 2017 / Spring 2018 / Summer 2018 versions action required by 30 Sept 2022
- Winter 2018 / Spring 2019 versions action required by 30 Sept 2023
Sage 200 V4 - v2011
No impact
Sage 200 Standard Online
We will make the necessary changes to the software and auto update during a specified maintenance window as a mandatory upgrade.
Details will be updated to our service maintenance pages.
Some customers may be impacted by the new banking legislation changes, depending on your contract we’ll contact partners or customer to discuss what’s needed.
Sage 4 Education
We will make the necessary changes to the software and auto update during a specified maintenance window as a mandatory upgrade.
Details will be updated to our service maintenance pages.
Some customers may be impacted by the new banking legislation changes, depending on your contract we’ll contact partners or customers to discuss what’s needed.
2013 / 2013 R2 / 2015
The retirement of TLS 1.0 / 1.1 impacts both the Sage License Service & Sage 200 CRM.
Due to this protocol being retired, customers using these versions must upgrade no later than 30 September 2021. Either a remastered version of 2016 SP2, Summer 2017 (RM), Summer 2018 (RM) or 2020 R1 can be selected. As this is an upgrade we’d always recommend taking the latest version possible to provide the most value & benefits to the customer.
- CRM: Further advice on the application to follow.
2016
Sage License Service and the following connected services are impacted, the date action is required will depend on the service(s) in use:
- Salary & Supplier Payments
Requirements: Software reinstall of remastered 2016 build, available from March 2020 or upgrade to a newer version
Deadline: 31 August 2020
- API inc WebSOP
Requirements: Software reinstall of remastered 2016 build, available from March 2020 or upgrade to a newer version
Deadline: 31 August 2020
- Sage License Service
Requirements: Software reinstall of remastered 2016 build, available from March 2020 or upgrade to a newer version
Deadline: 30 September 2021
- CRM : Further information can be found here.
Summer 2017
The Sage License Service and the following connected services are impacted, the date action is required will depend on which service(s) the customer uses:
- Banking Cloud
Requirements: Using Direct bank feeds, a registry change can be made, this must be done before 12 March 2020.
- Salary & Supplier Payments
Requirements: Software reinstall of remastered Summer 2017 build, available from March 2020 or upgrade to a newer version.
Deadline: 31 August 2020
- API inc WebSOP
Requirements: Software reinstall of remastered Summer 2017 build, available from March 2020 or upgrade to a newer version.
Deadline: 31 August 2020
- Sage License Service
Requirements: Software reinstall of remastered Summer 2017 build, available from March 2020 or upgrade to a newer version.
Deadline: 30 September 2022
- CRM: Further information can be found here.
Winter 2017 / Spring 2018 / Summer 2018
The Sage License Service and the following connected services are impacted, the date action is required will depend on which service(s) the customer uses:
- Banking Cloud
Requirements: Using Indirect bank feeds, migration to Open Banking is required by 09 March 2020, followed by software reinstall of remastered Summer 2018 build, available from 03 March 2020 or upgrade to a newer version.
Deadline: 09 March 2020
Using Direct bank feeds, a registry change can be made, this must be done before 12 March 2020.
- Salary & Supplier Payments
Requirements: Software reinstall of remastered 2016 build, available from March 2020 or upgrade to a newer version
- API inc WebSOP
Requirements: Software reinstall of remastered Summer 2018 build, available from 03 March 2020 or upgrade to a newer version.
Deadline: 31 August 2020
- Sage License Service
Requirements: Software reinstall of remastered Summer 2018 build, available from 03 March 2020 or upgrade to a newer version.
Deadline: 30 September 2022
- CRM: Further information can be found here.
Winter 2018 / Spring 2019 / Summer 2019
The Sage License Service and the following connected services are impacted, the date action is required will depend on which service(s) the customer uses:
- Banking Cloud
Requirements: Using indirect bank feeds, migration to Open Banking is required by 09 March 2020. This is to be followed by installation of 2020 R1 build available from 03 March 2020.
Deadline: 09 March 2020
Using Direct Bank Feeds, a registry change can be made. This must be done before 12 March 2020.
- Salary & Supplier Payments
Requirements: Software installation of 2020 R1 build (or newer version), available from 03 March 2020
- API inc WebSOP
Requirements: Software installation of 2020 R1 build, available from 03 March 2020.
Deadline: 31 August 2020
- Sage License Service (excluding Summer 2019)
Requirements: Software installation of 2020 R1 build (or newer version), available from 03 March 2020.
Deadline: 30 September 2023
- CRM: Further information can be found here.
Upgrading your licence
Need a little more room? To add extra companies, users, employees or more to your software licence, leave your details and we'll be in touch.
Africa
Asia
Australia
Canada
France
Ireland
Kenya
Nigeria
Portugal
South Africa
Spain
United Arab Emirates
United States
Germany