Troubleshooting payroll issues

Updated by Leigh Hutchens

This article outlines two real-world examples of payroll discrepancies encountered in Quinyx, each resulting from specific configuration issues. These cases highlight how seemingly minor misconfigurations, whether in agreement templates, time settings, or salary type rules, can lead to inconsistent or incorrect payroll outcomes. For each example, we provide the symptoms, the investigative steps taken, and the root cause identified, along with key considerations for resolving similar issues in the future.

Example 1

Quinyx randomly doesn't generate a salary type from the OT method when work time exceeds the agreement hours for a part-time employee. This only happens for random people and even on random days. No changes have been made to agreement templates or shift types. This can affect payroll.

Troubleshooting

  1. Check the Time card.
  2. Check the agreement template configuration for the OT method and rules for overtime. Also check if the connected salary type is active or not.
  3. It turns out that in Time section, under Overtime/Additional time bank, “Saved time off in lieu” was ticked instead of “Paid”.

  1. Also the salary type for TOIL was not active in the agreement template, that’s why no OT salary type was generated.
Notice that changes made for rules under Time or salary type settings will NOT affect already existing punches/shifts that are connected to the agreement template. Existed punches/shifts have to be removed and re-added for the changes to kick in.

Example 2

Employee 123 does not have the correct number of days worked in payroll summary. It says that she worked 31.25 hours in summary. But as you can see, she only worked 22 hours in August from schedule. Why?

Troubleshooting

  1. Run a Salary Details report for this employee in August and compare with shifts in Schedule for August to confirm customer’s explained outcome.
  2. Check a time card on August, the salary type customer reported that is generating wrong outcome has “generated by manual rule” instead of “generated by agreement” under, which means there is salary type rule added in this shift.
  3. In edit shift, we can check the salary type rules. It turns out that under Amount, customer configured “Working hours” instead of “Exact numbers” according to the expected outcome.
Salary type rules in shifts are very customer specific. Always try different configurations in test environment to find the expected outcome.


How Did We Do?