Payroll FAQ

Updated by Leigh Hutchens

​Payroll issues are often related to incorrectly configured or missing salary types. When troubleshooting, it’s helpful to:

  • Try to reproduce the issue
  • Review any filters used when generating the payroll file
  • Confirm if the payroll can be reverted and re-run

FAQs about common issues

Q: Why is a salary type missing from the payroll file?

A: Check the following:

  • Is “Transfer to payroll” enabled in the salary type’s Global settings and Agreement template?
  • Is the salary type active on the employee’s agreement template?
Q: Why isn't an employee appearing in the payroll file?

A: Ensure the following:

  • The employee has an active agreement template.
  • Within the agreement template > Time tab > “Payroll file” is selected.
  • Punches or absences are attested, if applicable.
Q: Can I add cost center information to an existing payroll file?

A: Start by:

  • Downloading the payroll file to confirm the current output. If changes are needed, ask your Quinyx superuser to contact Quinyx Support.
Q: Why isn’t an absence showing in the payroll file?

A: Check the following:

  • The absence has underlying shifts (required for Quinyx to generate a salary for the absence).
  • An Abbreviation or Absence code is present if required by the payroll setup.

Example 1: OT salary type not generated randomly

Issue

Quinyx sometimes does not generate a salary type from the OT method when a part-time employee works more than their agreed hours. This issue occurs randomly, for different employees and on different days, even though no changes have been made to the agreement templates or shift types. The problem has impacted payroll and is ongoing.

Troubleshooting steps
  1. Check the employee’s time card to verify the customer’s reported outcome.
  2. Review the agreement template:
    • Check the OT method configuration and rules.
    • Confirm that the connected salary type is active.
Findings
  • In the Time section of the agreement template, under Overtime/Additional time bank, the setting "Saved time off in lieu" was selected instead of "Paid".
  • Additionally, the salary type for TOIL (Time Off In Lieu) was inactive in the agreement template. Because of this, no OT salary type was generated.
Important note

Changes made to rules under the Time section or salary type settings won’t affect existing punches or shifts already linked to the agreement template. To apply the changes, those punches or shifts must be deleted and re-added.

Example 2: Incorrect days worked in payroll summary

Issue

Employee 123 appears to have worked 31.25 hours in the payroll summary for August, but the schedule only shows 22 hours. The summary is incorrect - why?

Troubleshooting steps
  1. Run a Salary Details report for the employee in August.
  2. Compare the report with the scheduled shifts for that month.
  3. Review the time card for August to investigate the salary type generating the unexpected result.
Findings
  • The salary type shown on the time card was “generated by manual rule”, not “generated by agreement”, meaning a manual salary type rule was added to the shift.
  • In the shift details, under Edit shift > Salary type rules, the customer had configured the Amount as “Working hours” instead of “Exact numbers” - which caused the incorrect hour total.
Best practice reminder

Salary type rules in shifts can vary greatly depending on customer-specific configurations. It's always recommended to test different settings in a test environment to confirm the expected outcome before applying them in production.


How Did We Do?