Sage 100

Just in time for year-end processing, I have at least 2 end users getting bogus data on the ACA Applicable Large Employer Report.  I ran into it a couple of weeks ago and logged it to Sage.  Of course, they said they had no other reported instances and would take a look at it.  The first user to report it to me runs it monthly as a quick way to monitor when they have to offer benefits to part time employees and of course the problems were right after I upgraded them from Sage 2017 to 2019 (payroll 2.19.4.0).  Yes, I know they should be getting actual hours worked from somewhere else.  They just use this report to watch when they get close and when they're close, they delve into actual hours.  

Since I did another upgrade today and they have over 500 employees, I thought they would be a good test.  Their report was 6 pages in 2017 with employees having hours in every single month.  After the conversion it's 1 page with only 4 employees having hours in all months.  The other 20 or so that are showing up only have hours in 1 or 2 of the months and they're really low numbers.  I have no idea what happened to all of the other employees.  

I went back to Sage with it and Richard said they had one instance where it looked like just the vacation hours were coming over to the report.  That doesn't look like what's happening in my case, though.  Supposedly they're having a meeting to review it on Friday.  

Has anyone else seen this?  If my user wasn't using it to eyeball the hours worked on a regular basis, I likely wouldn't have stumbled across  it until next month when users are actually dealing with ACA.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

@Jeff Schwenk found that Sage issued a utility to resolve issues with the wrong hours on the Applicable Large Employer report.  He posted this in a different thread.

The problem was your data.  In your legacy version there were no Earnings Types in the PR_23SEI.soa table after 9/9/2011.  I don't know how that happened as that was 8 years ago.  The new Payroll ACA uses that field and after conversion it converted the blank field to the wrong earnings type because it had no reference.  I got a utility yesterday to fix the records in the new payroll version.  I am glad you were able to get those records fixed.  There should not be a problem next year because you are entering the 2020 year data in the new version so there will be no migration/conversion of the bad records in 2020.  That is true unless you have done some of 2020 payroll in the legacy version before the upgrade.  If so, then we need to fix that data.​

I called Linda Rabe and she emailed me the utilities.  Note that you have to run the utility against each company you want to fix.  She said she will probably attach a Crystal report that she designed to the knowledgebase article so you can run the report first to make sure what you're experiencing is related to this issue.  She didn't send me the Crystal report so I'm just attaching the utility and instructions.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

Thank you!  Did she happen to mention WHEN this was going to be added to a product update?  I have a PR go live next week with 250 + employees and I really don't want to hassle next January of fixing these issue.  Not if, but when.I suppose, to be on the safe side, just run them now.....

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-30-2020 18:36
From: Mary Jo Krueger
Subject: ACA Applicable Large Employer Report Issues

@Jeff Schwenk found that Sage issued a utility to resolve issues with the wrong hours on the Applicable Large Employer report.  He posted this in a different thread.

The problem was your data.  In your legacy version there were no Earnings Types in the PR_23SEI.soa table after 9/9/2011.  I don't know how that happened as that was 8 years ago.  The new Payroll ACA uses that field and after conversion it converted the blank field to the wrong earnings type because it had no reference.  I got a utility yesterday to fix the records in the new payroll version.  I am glad you were able to get those records fixed.  There should not be a problem next year because you are entering the 2020 year data in the new version so there will be no migration/conversion of the bad records in 2020.  That is true unless you have done some of 2020 payroll in the legacy version before the upgrade.  If so, then we need to fix that data.​

I called Linda Rabe and she emailed me the utilities.  Note that you have to run the utility against each company you want to fix.  She said she will probably attach a Crystal report that she designed to the knowledgebase article so you can run the report first to make sure what you're experiencing is related to this issue.  She didn't send me the Crystal report so I'm just attaching the utility and instructions.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

She didn't say.  She did say that when they do incorporate it into a fix, it'll fix all companies but for now it has to be run against each company individually.  I grumbled about the 2 ACA utilities being released in Jan on top of the 5 other hot fixes and she agreed it was ridiculous that we all, including them, had to be dealing with these hot fixes at year end.  That didn't make me feel better about it, though.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

Original Message:
Sent: 01-30-2020 18:55
From: Jeff Schwenk
Subject: ACA Applicable Large Employer Report Issues

Thank you!  Did she happen to mention WHEN this was going to be added to a product update?  I have a PR go live next week with 250 + employees and I really don't want to hassle next January of fixing these issue.  Not if, but when.I suppose, to be on the safe side, just run them now.....

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 01-30-2020 18:36
From: Mary Jo Krueger
Subject: ACA Applicable Large Employer Report Issues

@Jeff Schwenk found that Sage issued a utility to resolve issues with the wrong hours on the Applicable Large Employer report.  He posted this in a different thread.

The problem was your data.  In your legacy version there were no Earnings Types in the PR_23SEI.soa table after 9/9/2011.  I don't know how that happened as that was 8 years ago.  The new Payroll ACA uses that field and after conversion it converted the blank field to the wrong earnings type because it had no reference.  I got a utility yesterday to fix the records in the new payroll version.  I am glad you were able to get those records fixed.  There should not be a problem next year because you are entering the 2020 year data in the new version so there will be no migration/conversion of the bad records in 2020.  That is true unless you have done some of 2020 payroll in the legacy version before the upgrade.  If so, then we need to fix that data.​

I called Linda Rabe and she emailed me the utilities.  Note that you have to run the utility against each company you want to fix.  She said she will probably attach a Crystal report that she designed to the knowledgebase article so you can run the report first to make sure what you're experiencing is related to this issue.  She didn't send me the Crystal report so I'm just attaching the utility and instructions.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176