Schulz Consulting

Consulting and Upgrades

Sage 100 Payroll Tax Update Set for 10/27/22 for New York State Health Care Workers Bonus Program (HWB)

by

The change from Sage on the NY Health Care Workers Bonus is scheduled to be on the 10/27/2022 deployment of the Payroll Tax Update.

To attract talented people into the profession at a time of such significant strain, while also retaining those who have been working so tirelessly these past two years, we must recognize the efforts of our health care and mental hygiene workforce and reward them financially for their service. To do so, as part of the Fiscal Year 2023 New York State Executive Budget legislation, $1.2 billion in funding has been allocated for the payment of bonuses for certain frontline healthcare workers.

New York State Health Care and Mental Hygiene Worker Bonus (HWB) Program

That tax update will reportedly include a NEW Earnings Tax Rule, -800139, New York Healthcare Worker Bonus. An Earnings Code will need to be setup for this Type of Bonus Payment using that Tax Rule.

That earnings code(s) will be used to pay the employee the amount calculated and approved in order to keep it separated from other earnings. Use the Tax Rule Inquiry to determine what taxes this tax rule will be subject to.

The Employer/Employee will be responsible to properly determine eligibility and bonus requirements when submitting for approval on the appropriate forms from New York State. Aatrix has stated they will not be supporting this program due to state form requirements.

NYS Healthcare Worker Bonus Program Frequently Asked Questions (FAQ)

NYS Healthcare Worker Bonus Site Information

Payroll tax updates are downloaded to Sage 100 via an Internet connection by accessing the payroll module and selecting the update option from the utilities menu.

Microsoft Offers One-Time Re-Enablement of Basic Authentication Through 12/31/2022

by

According to a September 1, 2022 blog post, Microsoft will allow a one time extension through 12/31/2022 users who have not yet met the requirement to use OAuth for more secure login to MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS), and Remote PowerShell.

Furthermore, in a 9-9-2022 blog post Microsoft clarifies that SMTP AUTH will NOT be disabled for active users of the authentication method. The company does urge users to adopt OAuth as a more secure method but clarifies that SMTP AUTH is not shutting down. At least not as of 9/9/2022.

From Microsoft blog post 9-1-2022

One-Time Re-Enablement
Today we are announcing an update to our plan to offer customers who are unaware or are not ready for this change.
When we turn off basic auth after October 1st, all customers will be able to use the self-service diagnostic to re-enable basic auth for any protocols they need, once per protocol. Details on this process are below.
Once this diagnostic is run, basic auth will be re-enabled for those protocol(s). Selected protocol(s) will stay enabled for basic auth use until end of December 2022. During the first week of calendar year 2023, those protocols will be disabled for basic auth use permanently, and there will be no possibility of using basic auth after that.

For more information on the Microsoft OAuth requirements please visit their website here.

The following Sage 100 versions currently meet the requirement use OAuth with Microsoft.

  • 2021.4+
  • 2022.1+

Does Sage sell SQL Runtime Licenses for Sage 100 Premium?

by

Sage offers SQL runtime licenses for users of Sage 100 Premium in an on-premises environment. These may be ordered from Sage who then provide all necessary registration information.

Please note the important restriction to this license as it may only be used for on-premises implementations with dedicated hardware. All servers and other devices must be fully physically dedicated to the end user. For SQL licenses to be used in a hosted environment you must purchase a full unrestricted SQL license from a Microsoft reseller.

Sage Transitions Billing for Sage AP Automation to Beanworks Effective 10/1/2022

by

Effective October 1, 2022 Sage will transition the account renewal and billing process for Sage AP Automation for Sage 100 and Sage 300 to the application’s developer Beanworks.

Customers will be contacted by Beanworks to sign a revised agreement and provide banking information for their renewal within the next 60 days.

Beanworks marketed Sage AP Automation through a white label relationship with Sage. In March 2021 Beanworks was acquired in a $100 million deal by Quadient.

Join Our Weekly Sage 100 Newsletter

Every Thursday we publish a newsletter covering Sage 100 news. Enter your information below to receive our next issue.

By clicking submit, you agree to share your email address with the site owner and Mailchimp to receive marketing, updates, and other emails from the site owner. Use the unsubscribe link in those emails to opt out at any time.

Processing…
Success! You're on the list.

Sage 100 FAQ on OAuth and TLS 1.2

by

Microsoft has announced a move to OAuth for certain users connecting applications to Microsoft’s email servers. While this announcement was subsequently clarified to exclude SMTP AUTH – we think it is still a good idea to upgrade to Sage 100 version 2021.x or 2022.x for maximum compatibility.

Microsoft announced a change to certain email sign-on security with new OAuth requirements (Originally effective beginning 10/1/2022 though subsequently amended as per information below). A requirement to use TLS 1.2 to reach Sage licensing servers goes into effect later in 2023 (September 2023) and this will potentially impact any Sage 100 system without TLS 1.2 capabilities – effectively ay Sage 100 version earlier than 2019.4.

Update 9-26-2022: Microsoft has clarified that SMTP AUTH will not be shut down and if you are using SMTP AUTH and/or are able to enable use on your Microsoft account then this should continue to work for you past the original October 1, 2022 deadline. Read the Microsoft 9/9/2022 blog post and read the Sage September 16, 2022 OAuth Update (pdf) for more details.

Microsoft continues to recommend adopting the more secure OAuth authentication method. We recommend for maximum compatibility all users of Sage 100 should continue to remain within the two most recent versions of Sage 100 – presently Sage 100 2021 and Sage 100 2022.

Review our Sage 100 OAuth and TLS 1.2 FAQ

For a more detailed explanation of the Microsoft OAuth changes please see – Deprecation of Basic authentication in Exchange Online

In each case the easiest resolution is to be on a supported version of Sage 100. If you are on the latest product update for Sage 100 version 2021 or 2022 then you shouldn’t need to take further action.

Sage 100 OAuth and TLS 1.2 Required Due Dates

On October 1, 2022, Microsoft® will disable Basic Authentication for email services and will require the use of Modern Authentication for Microsoft Exchange Server and Office 365. (Update: Please see Microsoft blog post dated 9-9-2022 which states that SMTP AUTH will remain accessible past 10-1-2022)

Sage KB 116301: How to configure Sage 100 OAuth E-Mail settings for use with a Microsoft 365 App Registration

Note: Google® ended support of Basic Authentication (less secure apps) on May 30, 2022.

Sage KB 115141: How to connect Sage 100 to Gmail using OAuth 2.0

Any Sage 100 site using Basic Authentication with Microsoft email services will experience interruptions with their Sage 100 in-product email services. To avoid related issues, Sage 100 customers should upgrade to at least:

  • Sage 100 2020.6
  • Sage 100 2021.4
  • Sage 100 2022.1

Sage 100 Advanced/Premium also should download this required patch.

Recommendation: Upgrade to the latest release of Sage 100 2020.6, 2021.4 or 2022.x where x is the latest product update.

Read – September 13, 2022 Sage FAQ on OAuth here

Read – How to configure Sage 100 OAuth E-mail settings for use with a Microsoft 365 App Registration

Sage FAQ on TLS 1.2

Effective September 2023, Sage servers will stop accepting communication from Sage 100 and Sage 300 product versions using Transport Layer Security (TLS) 1.0 and 1.1.

TLS is a security protocol that creates encryption paths over computer networks to help ensure that online communications and information cannot be intercepted. Regulatory standards have increasingly required the adoption of TLS 1.2 and the subsequent deprecation of TLS 1.0 and 1.1 due to known security risks.

Any customer using a subscription version of Sage 100 a version earlier than 2019.4 will require an upgrade to their Sage 100 to prevent a disruption in the use of their software.

If a Sage 100 user does not upgrade their software by September 2023, they will begin receiving warning messages when accessing Sage 100 due to the inability to communicate with Sage servers. The software will revert to read-only mode and restrict access.

Read – August 12, 2022 Sage FAQ on TLS 1.2 here

Recommendation: Upgrade to Sage 100 2021.x or 2022.x although Sage’s website indicates that 2019.4+ is the minimum release compatible with the TLS changes.

  • Sage Production Management enhancements
  • Simplified role security capabilities
  • Automation in reversing an entire accounts payable (AP) check run

Check back with us periodically for the latest updates to these two important changes.

Contact Us

Schulz Consulting
Connecticut Office
Click Here To Contact Schulz Consulting
Phone: 860-657-8544
Email Us
Available remotely nationwide.
We are a local branch of DSD Business Systems Connecticut.
Schulz Consulting