Sage 100

v2015, PU 3 Std ACA - Apparently the ACA $$'s are not populating the fields properly between December and January for bi-weekly PR. **From the client to Sage - This information did not solve the problem. I have attached our report so you can see. It is not splitting our Jan 8th pay date (period ending Jan 2nd) between the two years so it looks as if all of our employees are part time. The calculation for that Jan 8th pay date should have been 2/14 for Jan and 12/14 for hours to Dec.** Has anyone else had this reported to them? Any fixes? Sage seems to be flummoxed.

Not sure but read through some of the ""how does Sage compute ACA"". I thought there were a few disclaimers in there which may or may not be applicable. Sage seemed to be taking the position that they'd get you 80% of the way there but check the other 20%.

There is a PDF on how this calculation is down between months but I will lay down odds that no Sage employee has checked it between years...

I ran into the same problem with just one client and opened a case with Sage. Carmen sent me info on how the calculation is done but that did nothing for me. The system calculated 8 FT/FTEs for December when all other months were in the 60 to 70 FT/FTE range. We ended up running a perpetual history report and manually calculated the correct number for December. When I told Carmen that, I got the following response: **_I am going to forward this to Financials because I have 3 cases all with the same issue and even on my data I can recreate. This can't be right. You should not have had to manually calculate using Perpetual History to correct the number._**

@MaryJoKrueger - I was JUST going to put a plea out to you. Carmen is the support analyst working on this issue and she sent the same calc to my client. Attached. Wonder how long we will be waiting.

I guess this is why Sage originally wanted to do the payroll price increase BEFORE year end...

I wouldn't hold my breath waiting for Sage. I logged it to Sage on 1/13 and she started with sending me that document too. I got the above response yesterday.

I'd bet any money Sage is going to make a big push to get the bigger and more complicated payrolls to Sage Payroll Service.

They can push all they want but that doesn't mean it'll happen. It's a tough sell because the only time saving is the quarterly report filing and W2 filing. Even if Sage is doing payroll, ultimately the client will be responsible for ACA data.

From my client **I just received a call for this from Sage (Gina). She said the same thing and they are looking into it** She did not get a case ID # for me.

From the Client **Here is the fix. So easy. I was running it for the year, which I'm sure most people were. It worked, but I did get an error when trying to update to the employer maintenance. However it did work.** From Gina Thompson at Sage - Case 8005050242 **Please run the ACA ALE report in your live company, selecting pay ending dates 1/3/2015 01/02/2016.**

That didn't work in my case. We tried several different date ranges to no avail. Glad it worked for you though!

We had to run the in the live company with the payroll check dates, not the period end dates, and the correct data was included.

Follow up from Client **I apologize for the error 47 you receive when updating the ACA ALE report. Our engineering team is currently working on a fixing the program. From our testing it appears that the employee counts are updating correctly into ACA Employer Maintenance > Monthly Detail, after ending out of the error message. We are trying to get the fix included in the next product update (PU4) if not it will be included in PU 5 for Sage 100 version 2015.** Guess it is not hot fix worthy...