Sage 100

Payroll Tax Table Updates - Government Compliance

Seriously?

We'll provide maintenance and support, but only if it isn't too hard. Your bill will go up every year regardless of whether we actually provide any maintenance or support.

I may just offer all my payroll customers a free data export for the professional payroll service of their choice...

Has Sage notified the channel of this policy change?

There is a ""Note If you are not the person who installs the updates, please forward this email to the appropriate person."". So, Sage is asking the client to inform the partner of the policy change.

I'm headed to NYC tomorrow. Will see what words of wisdom Sage has.

I spoke to Linda Cade. Nothing really to report other than what you'd expect - apologies, do better, etc. I'm not exactly sure who the main boss is in NA for the Sage 100 line. I'm led to believe that it remains in a bit of flux especially in marketing.

Thanks for following up Wayne. This issue seems to affect users that have employees in Oregon that are on version 2016 and 2017. I am not sure how many users are affected, but if I were one of them I would be searching for new software.

For now this is who is impacted. If there are other states that impact difficult tax changes then Sage is saying customers need to be on 2018 to get program patch. Lots of finger pointing about why the lack of communication but I don't feel anything changes

Apparently there was a Sage City post on this [here](https://sagecity.na.sage.com/support_communities/sage100_erp/b/sageerp_100_blog/posts/2018---the-year-of-the-tax-change) . I still think Sage should have addressed this more clearly back in February and should have sent notice to the partners first.

If Sage's subscriptions and maintenance can consider compliance updates to be optional, they need to get out of the payroll business.

I don't have time to be reading every post on every web site searching for mission-critical information. Sage needs to email or better communicate with the partners. It makes everyone look bad when customers know more than we do. Even if this issue was clearly communicated to partners, it is still ridiculous.

Anyone know what other states/jurisdictions fall into this situation like Oregon?

I don't know for sure but at Sage Session - NYC someone kept bringing up PA

{bump} Still wondering if anyone knows for sure of other jurisdictions that apply here in addition to Oregon. Can anyone confirm PA or others?

Let me check with Sage.

I assume still 'crickets', @MoiraGoggin?

chirp

My apologies, to be more clear, see attached.

Same here - complete radio silence.

Should have some info from Linda Raby sometime this week.

I am told that the next service update for payroll was made available to the ""master developers"" this week...

I am hearing the same thing. Next PU is just around the corner, then nothing till December. Unfortunately, clients are waiting for a fix that will not make it till year end.