Skip to main content
Answer

What is the purpose of the ACA Reporting screen?

  • January 7, 2025
  • 4 replies
  • 109 views

darylbowman
Captain II
Forum|alt.badge.img+15

I am attempting to help a friend get accurate information on the ACA Reporting screen. The data listed seems very unreliable. For instance, many employees are listed has having no hours from Jul-Dec of 2024. One long-term employee shows up in only one month, despite being paid weekly.

I’ve scoured the web, but there seems to be next-to-no information about it.

Best answer by brandontfrank

I provided a backup to Acumatica. Still waiting to hear from them.

FYI this is the response we received -

“We have determined it is a bug. Sorry we could not provide an update sooner, it took a while to determine the conditions of the bug.

This issue will be experienced by all employees who have multiple entries in Employment History, i.e. in EPEmployeePosition table.

It is planned to be fixed in the 2024R118 release, which will be available March 21st.

4 replies

Sonia Echols
Acumatica Moderator
Forum|alt.badge.img+1
  • Acumatica Moderator
  • January 7, 2025

Hi Darylbowman,

You will need to create an SR and provide the friends DB.  


Forum|alt.badge.img
  • Jr Varsity III
  • February 17, 2025

@darylbowman did you ever get clarification on this? We are experiencing the same thing. Certain full-time employees that only show up for a month or two. It’s all over the place with the data. I have an open Acumatica case but awaiting a response.

 

I have an import scenario ready to import to update the values that are off but it’s erroring out as it cannot insert new rows, only modify existing rows in the aca reporting screen.


darylbowman
Captain II
Forum|alt.badge.img+15
  • Author
  • February 18, 2025

I provided a backup to Acumatica. Still waiting to hear from them.


Forum|alt.badge.img
  • Jr Varsity III
  • Answer
  • February 27, 2025

I provided a backup to Acumatica. Still waiting to hear from them.

FYI this is the response we received -

“We have determined it is a bug. Sorry we could not provide an update sooner, it took a while to determine the conditions of the bug.

This issue will be experienced by all employees who have multiple entries in Employment History, i.e. in EPEmployeePosition table.

It is planned to be fixed in the 2024R118 release, which will be available March 21st.