Sage 100

Is everyone in agreement that Payroll 2.0 will be required for any Washington State Payroll users? My guess is we could create a state deduction for the Employee and employer deduction earnings but the Quarterly tax and W2's will be a mess? @SueBennett what is your take on it?

Hi Jim - Yes, Diane answered with an affirmative if you are talking about the new Washington Paid Family & Medical Leave. She said the Washington ""Tax"" is already in Payroll 2.x because CLAD has already programmed it. For everyone else, you are correct - we'll have to do a deduction...fun times. You know - like we did with the Oregon Transit Tax Calculation for folks not yet on 2.x. Incidentally, you probably already know (but others might not) Jon Reiter programmed a fix that DSD resells to move the SDI withholding (which is what we used Oregon Transit Tax for clients not on Payroll 2.x yet) into the Transit Tax field. We use it when clients upgrade to Payroll 2.x - so their historical reports will be correct as will be their Quarterly Reports. Yay for Jon!

Yes, it will only be available in Payroll 2.18 and is added via the latest tax update within payroll. We are starting to test it. What I know so far is in Tax Profile Maintenance for WA there are 2 new fields for withholding and liability. Company Tax Group Setup holds the employer rate and the employee rate is the difference between the total rate and the employer rate.

And actually, for folks not on Payroll 2.18, I think we'll have to do multiple deductions for the Employee, since the Family Leave has one calculation and the Medical Leave has a different calculation. Since there are multiple steps in each of the calculations, that is not going to be fun.

Also a nightmare for clients not on Payroll 2.18 if they have employees where the same employee may work in multiple states in addition to WA since it only applies to WA wages so either the deductions have to be manually entered or manually edited for those cases.

it is NOT pretty.

Thanks @SueBennett @ShariEckersley

Let us know if Jon decides to work his magic to sell a solution to make this easier for clients who will be still using v2016 or v2017 for a while.