Salary arrears may be generated for an employee even when no arrears are due to several factors.
Below, we outline common reasons for the incorrect generation of salary arrears and provide resolutions for each scenario.
Incorrectly entered salary row
If a new salary row was entered with an effective date in the past, follow these steps to resolve the issue in back office.
Click CorePay then click Employee.
Click View Employee Details then click Rate History.
Check that no incorrect rows exist for the employee with a past effective date.
To delete an incorrect row, follow these steps.
Click CorePay then click Pay Rates.
Click Maintain Employee Position/Point.
Check that the employee has not already been paid on this rate.
Unprocessed salary amendment
If a salary amendment has not been processed correctly, check that all salary amendments for employees have been properly processed in the last period.
This issue may arise if a salary change was made and timesheets were generated, but payroll periods were manually moved forward for testing.
The system will attempt to recover any arrears in the following period.
New position rate entered
Check whether a new position rate was entered and linked to the employee's record during this period. The PAY290 program (Generate Salaries and Allowances) does not support this.
Please raise a new case online and reference the title of this article. Include the following details:
Employee number
Pay group
Payroll period in question.
Employee moved pay groups
If an employee changed pay groups during the period, it could lead to timing issues. Rerun the jobs for both pay groups to address this.
Personal rate setup
Confirm that the employee is set up with either a personal rate or a position and point rate, but not both.
Career break payment
If the employee had a hold date for a career break and is now receiving payments, our support team needs to run scripts on the database to resolve this.
Please raise a new case online and reference the title of this article and include details of the employee affected.
Incorrect changes to existing position
If changes were made to the employee's position incorrectly, such as populating the Weekly Basic with the annual salary without updating the annual salary, the system will reverse previously paid amounts.
To resolve this, review the position and ensure all details are correct, then re-run the Generate Salaries job.
Populated rejoin date
If the employee rejoined in a previous period and the rejoin date remains populated, support will need to clear this.
Please raise a new case online and reference the title of this article and include details of the employee affected. Then, rerun the Generate Salaries and Allowance jobs.
CorePersonnel amendment issues
If you entered an amendment in CorePersonnel that created a new salary record but incorrectly deleted the old record, this could generate arrears in CorePay.
To resolve this issue, support will need to review the data for the employee. Please raise a new case online and reference the title of this article and provide details of the affected employee.
The retro spans a period of absence
To resolve this issue, support will need to review the data for the employee.
Please raise a new case online and reference the title of this article and include the affected employee's details.
Blank Pay355 (Complete Update) date
If the Pay355 (Complete Update) date appears blank on the Employee Utility screen, support will need to review the data for the employee.
Please raise a new case online and reference the title of this article and include details of the employee affected.