If you encounter an error while running a validation job that has previously completed successfully for the pay group, but no hours were generated, it may be due to one of the following reasons.
We have compiled a list of possible causes for this error message, along with steps to resolve them.
Change in pay frequency
The employee's pay frequency has changed, for example, from fortnightly to monthly.
To resolve this, our support team needs to check the configuration. Please raise a new case online, referencing this article's title and include the following details:
Details of the affected employee.
Pay group
Pay period
No rate of pay
There is no recorded rate of pay for the employee.
To resolve this issue, review the employee's setup and ensure a rate of pay is recorded. Once confirmed, re-run the Generate Salaries and Allowances (PAY290) job.
Positive Input
The employee is currently on positive input.
To resolve this issue, follow these steps in the back office:
Make sure that if a salary is to be generated for the employee, they are not on positive input.
Click CorePay then click Employee.
Click Maintain Employee Details.
If no salary is due, this is expected.
Hours not signed off
The hours have not been signed off in CoreTime for the employee on positive input.
To resolve this issue, if the employee should be paid via CoreTime timesheets, ensure that hours have been confirmed and sent from CoreTime.
Employment status
The employee's employment status is out of sync. For instance, a rejoin date may still be populated when the employee should be fully active.
To resolve this, our support team needs to check the configuration. Please raise a new case online, referencing this article's title and include the following details:
Details of the affected employee.
Pay group
Pay period