Sage 100

Payroll 2.0 Issue from Client, first payroll in 2019, anyone else having this issue? @MichelleTaylor1 is this the same thing you saw? Did you report it to Sage? **Michelle, I just wanted to alert you to an issue I encountered while running payroll this time. Any Garnishment that is percentage based did not completely load with the change to the new year. I have to go into each one, open it, and then it pushes the amount remaining into the proper place and I can process the garnishment. Only on the Garnishments that carry a balance remaining. It also was happening on the deductions in GCS. I had to open the deduction for uniforms to get it to transfer the information over and show the balance remaining. Once I did, it loaded and seems to be fine, but I only clicked on the ones that I knew were still owing (I have a spreadsheet). I don't know if it has loaded for those who have already completed their uniform deductions.**

Yes, ma'am, sounds like the same thing! I talked with Sage late on Friday - they are working on an ""emergency fix"" but don't know when that will be published, nor if this issue is included. So, customers must manually change each deduction (for each employee) in order to properly run payrolls.

Oh man. This is gonna be bad news to break. This client has 13 companies, with 75-300 employees per company. Yikes.

I didn't help, though I did plead for our customers!

Maybe I can create a report to compare the balances from 2108 to 2019? Anyone know what tables those are stored in? Fortunately this client is on SQL, so it will be easy to grab the data.

I saw this too and thought maybe I didn't understand it. The balance shows the same every year for a garnishment.

Yep - we too are discovering that Garnishments, 401k Loans...almost anything with a ""Goal Balance"" from the prior year, are not being deducted from Employee's paychecks after a Year End Close. Yowsers...

Received a voicemail from the Payroll team at Sage today - they are issuing hotfix, but don'e know exactly when, in the next couple of weeks.

Just tell your customer to wait a few weeks before making the next payroll

I'm sure that will be okay with the employees. Just tell them they could have solidarity with the Federal workers with the government shutdown in progress... (I'm kidding obviously! Don't attack me!)

Please write the above issue down on a piece of paper. Bring it with you to MOTM in February. Then when Sage is on stage and one of them asks why you think more people did not adopt payroll .... bring out the paper to refresh Sage's memory. But in reality, I think Sage will spin it to say ""see, if you urged your employees to upgrade sooner this wouldn't have happened"". Let's get those Sage Town Hall bingo cards ready...

@MoiraGoggin How about an #ASKSAGE90Minds2019 hashtag in HL? I am wondering if this hashtag will come over on the 11th :)

What is your hurry? For the past five + years, I have been sending a variant of this email every January. Date field return the year from the system date, not the module date. Some years I only get poked in the eye once, others I am not as fortunate. Have already had one client burned, I am sure there will be others. And I am sure every reseller has similar tales to tell of their clients posting to the wrong date. They flat out refuse to fix the employer matching PR deduction GL issue.

@Michelle.Taylor - I am being told by Sage gurus that the hotfix to correct the problem with Deductions not being taken in the new year after Year End Closing, will only be fixed in v2019. We've had other clients running on 2018 where Sage Support is telling us we need to install 2019 to correct things, and I'm truly frightened to do that. A new version that has only been out for weeks? Really? And is anyone doing a beta on these things? Anyone at all?

That will be you @SueBennett...

Wow! @SueBennett That would be much more disappointing to hear if the clients hadn't already corrected the issues. I understand why Sage is not going to update PR v.2018, and by the time customers need the fuctionality again, they will be on PR v.2019.

Whoa. Full stop. Hang on. Was I dozing the past two years? Isn't the entire reason for a payroll 2.x so that it's version independent of Sage 100 201x? What am I misunderstanding here? Why should anyone have to wait for Sage 100 2019 unless you mean the next release of payroll 2.x?

I can see why you would be confused Wayne! Payroll 2019 was just released, but it is for Payroll only. We're not talking about Sage 100 2019, only Payroll 2019 (which is compatible with Sage 100 2018 only). Not sure whose brilliant idea it was to have the Payroll module have a different version number than the rest of Sage 100, but there you go. Whoever it was is not on the front line with the clients like we are. I even had trouble with my Techs, explaining that Payroll 2019 (which is already out) is not dependent upon Sage 100 2019 being released....but is out now. And only works with Sage 100 2018...

Glad I am not the only one having difficulty wrapping my head around the new PR number scheme. I have to pause each time I see it.

@SueBennett part of the confusion is that Sage refers to their payroll version as 2.19. I have to say that what Sage is planning to do - only update the latest payroll 2.19 seems reasonable though I advised all my customers to hold on the payroll upgrade until late Q1 2019 unless they were in a tax complex state. **Thank you for your beta service.**

Yep - although Sage has told us to install 2.19 (which I still call Payroll v2019) to fix a bunch of problems, installing a new version at year end in the middle of what is already chaos, is not going to happen. Sage keeps telling me that Payroll 2.19 is really only 2.18.6 and there were not that many changes. Right. Someone is fooling someone - either they're fooling us by saying 2.19 is really only a product update, or they're fooling the clients implying it has new features since it is a new ""version"". Oh - and Therese.Logeais and Wayne too - not me, not me, not me on the Beta. I can't tell you how many Payroll clients we've lost in the last couple of years - we definitely don't have enough left to warrant spending all of the time and money on a Beta test for Sage. Now if they paid us....might be a different story. But it would have to be a lot of remuneration to fully test everything...

We have a KB article - Defect ID 110213 https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=95182&sliceId=1&cmd=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImplµsiteID=MS_Agent