x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 3 replies
  • Subscribers 143 subscribers
  • Views 556 views
  • Users 0 members are here
Browse Forums
Sage 100 Contractor Announcements
119
topics
57
replies
Sage 100 Contractor General Discussion
1k
topics
4k
replies
Sage 300 CRE Announcements
168
topics
526
replies
Sage 300 CRE General Discussion
3k
topics
9k
replies
Sage Construction Management Announcements
4
topics
0
replies
Sage Construction Management General Discussion
16
topics
21
replies
Sage Estimating Announcements
39
topics
3
replies
Sage Estimating General Discussion
189
topics
448
replies
Aethenosity

How can I fix the comp code calculations? This is a Bug as far as I can tell

Posted By

The issue is that when I put in sick or holiday pay, it will be calculated as whatever that employee's default comp code is. Below, you can see an employee record with the default comp code and the UNselected "Always use employee comp code" option.

 
Here, you can see a side-by-side of the comp code report and that employee's payroll record with the error. Look at the bottom of the payroll record to see that the regular pay PLUS holiday pay amount matches the "YRD/SHOP" amount in the comp code report.
 
Last picture is the workers comp calculations. This shows that none of the codes are inactive.


I talked to Sage Support, and they think that the sick/holiday/(and bonus/per diem/etc) are being defaulted because the Employee and Employer hourly columns are blank for those codes, and so Sage is defaulting to the employee's default comp code.

I tried putting 0 and 0.000 in those columns, but it just deletes those amounts. I also tried deleting WA in the state column of the workers comp calculations for Holiday/Sick/etc. That didn't work either.

This issue has apparently been going on since at least 2017, and it is still happening as of the most recent payroll.

The issue isn't as bad as I first thought, as there are no HOURS being applied to those comp codes, and I verified that our taxes are reconciled properly at the end of the year. It just makes a bit more work, and seems like an obvious bug.

Parents Reply Children
  • 0 in reply to Aethenosity

    Hi Aethenosity. Is the report in the screenshot the 5-1-5-96 (Washington Workers Comp) report? And what version of Sage 100 Contractor was that report run in? Did you also run the 5-1-5-21 report and get the same results?

  • 0 in reply to ghollister

    Correct, this is 5-1-5-96.

    My version is (24.3.45.0)

    The specific product is Sage 100 Contractor 2022 - US Edition

    Not sure why I didn't try earlier, but 5-1-5-21 does not have the issue. We do work in multiple states though, so it is less than optimal to rely on 5-1-5-21.

    Just so you can see it, here is the same employee from THIS year (instead of 2017 like above).

    Here is the record. This work was different, and categorized under Management instead of general shop work.

    .

    This is from report 5-1-5-21

    This is from report 5-1-5-96

*Community Hub is the new name for Sage City