Skip to main content

Arrears not calculating correctly in salary processing

Made a change to an employee's rate, but the arrears aren't generating correctly.

O
Written by Onyema Onyejekwe
Updated over a month ago

When processing salaries, arrears may not generate correctly for an employee due to several factors.

Below, we outline common scenarios that can cause inaccuracies in arrears calculations.


Null or zero multiplier for previous rate

If the multiplier for the employee's previous rate is null or zero, the system will not generate any arrears because there is no prior pay to calculate against. To ensure correct arrears payment, you need to manually enter a timesheet.


Incorrect pay group

If an employee was initially set up in the wrong pay group during payroll processing and then moved to the correct pay group, you need to process a manual timesheet entry to pay the correct arrears since the system does not accommodate this scenario.


Incorrectly entered new rate

Check that the new rate has the correct effective date recorded for that row.


Transaction date outside payroll period

Check the timesheet transaction date reflects the date of the salary change or a later date.


Multiple salary changes in the same period

If the employee experiences two or more salary changes (e.g., an increment and a promotion) within the same period, you need to enter a manual timesheet entry to pay the correct arrears, as the system does not handle this situation.


Input date on or before complete update date

If the input date for the allowance/salary line matches or predates the complete update date, the system considers the history row as processed in the previous payroll run. To resolve this, enter a manual timesheet to pay the correct arrears.


Discrepancy in pay days in period

If the pay days in the period are set to five days but the calculation uses seven days, you need to process a manual timesheet entry to pay the correct arrears.


No net pay row for the period

If the period lacks a net pay row, no arrears will be generated. To resolve this, you need to enter a manual timesheet to pay the correct arrears.


Employee changed pay groups

When an employee changes pay groups (e.g., from weekly to fortnightly), timing issues may arise. Run payroll updates in the old pay group first, and once that is complete, proceed with updates in the new pay group.


Incorrect number of units on nett pay row

If the number of units on the net pay row in the day history is incorrect, please raise a new case online and reference this article title. A support analyst will update the field accordingly.


Incorrect pay group for new starter

If a new employee is placed in the wrong pay group and then moved, the system indicates that the employee has been paid for those days based on the last processed period. Enter a manual timesheet to ensure the correct arrears payment


Positive input retro job needed for hourly pay codes

For hourly type pay codes, you need to run the positive input retro (PIR) job to generate the necessary retrospection payments.


Incorrect Rejoin Date generating unexpected arrears

Please raise a new case online and reference this article title. A support analyst will check and remove the rejoin date and correct the employee's latest pay start date if necessary.

After correcting the data, you need to re-run the Generate Salaries job.


Retrospection on a pay group

To switch on retrospection for an individual pay group, follow the steps below.

  1. Click Settings, then under Codes, click Pay Groups.

  2. From the Pay Group dropdown menu, select the relevant pay group.

  3. Enable the Retrospection toggle then click Save.

Did this answer your question?