If the validation job has run but displays no details on the View Gross to Nett screen, and the Run Payroll Update job submits without recording any history, while the Payroll Validation Exception Report (PAYB140) remains blank, you may receive a warning indicating that the position code XXX is not set up in the position_ref table. This issue may stem from one of the following causes.
We have compiled a list of possible causes for this error message along with solutions. Please follow the steps below in back office based on the identified cause.
Pay code deleted
A statutory or system-level pay code has been deleted.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Invalid analysis code
A pay code is set up with an invalid analysis code.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Change in pay group
An employee has changed from an Irish pay group to an English pay group, and the PRSI/NI class is not configured correctly.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
PRSI class
The employee either has no PRSI class or an invalid PRSI class.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
USC threshold length
An employee's USC threshold contains too many digits, causing the validation job to fail.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
No future period
If you are running the last period of the year, the following year may not be built into the calendar.
To resolve this, update the payroll calendar. To do this, follow the steps below.
Click CorePay then click Reference.
Click Payroll Calendar then query the company.
Check that the calendar has been built for the following year.
Check the payroll calendar.
PRD mismatch
There is a Year End 2015 PRD mismatch.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Pre-tax pay code
The pre-tax pay code has been deleted from the employee's pension scheme, or an AVC percent is set at the employee pension scheme level, but there is no pre-tax AVC pay code.
To resolve this, follow the steps below in back office.
Click CorePay then Reference.
Click Pension Schemes.
Query the pension scheme for the employee identified on the PAY140.trc
Check the Pre-Tax Pay Code fields are populated then click Save.
Re-run the validation job.
Taxable indicator
The Taxable indicator on the pension pay code is not set as Pre-Taxable.
To resolve this, check that the taxable indicator on the pension pay code is set correctly. To do this, follow the steps below.
Click CorePay then click Reference.
Click Pension Schemes.
Note each pay code for all pension schemes assigned to employees in the pay group.
To exit screen, click the exit
icon.Click CorePay then click Reference.
Click Pay Codes.
Check the Taxable indicator on each pay code.
Look for any pay codes with the Taxable indicator set to Non-Taxable or Taxable.
Change the Taxable indicator on these pay codes to Pre-Taxable.
Click Save then re-run the validation job.
Incorrect transaction date
The transaction date on the timesheet is incorrect, or the salary/basic rate is too high.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Duplicate rows
There are duplicate rows on the personal rate.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Payroll logfile path
The payroll logfile path is incorrectly set based on a clone.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Invalid analysis code
The analysis code for the pay code is invalid. You can find the pay code in the Pay140 trace file.
To resolve this, update the analysis code by. To do this, follow the steps below.
Click CorePay then click Reference.
Click Pay Codes.
Query all pay codes for the employee as identified on the PAY140.trc
Check that the Analysis Code fields are correct.
Click Save then re-run the validation job.
Leave date
An employee is leaving but does not have a leaving date. To resolve this, a support analyst will check the specific error from the log file.
Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Missing tax code
The employee's record does not have a tax code set via the Maintain Employee Details screen.
To resolve this, a support analyst will check the specific error from the log file. Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Employer pension pay code
A new employer pension pay code is incorrectly set as taxable or pre-taxable instead of non-taxable, or a change has been made to an existing employer pension pay code from non-taxable to taxable/pre-taxable.
To resolve this, you need to set up the employer pension pay code as non-taxable.
To do this, follow the steps below.
Click CorePay then click Reference.
Click Pay Codes then query all employer pension pay codes.
Check the employer pension pay codes are set up as Non- Taxable.
Click Save then re-run the validation job.
Duplicate allowance or deduction
There are duplicate allowance or deduction records for one or more employees. To resolve this, a support analyst will check the specific error from the log file.
Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Missing thresholds
No thresholds are set up for the new pay code. To resolve this, check that a new threshold deduction is set up.
To set up a new threshold, follow the steps below.
Click CorePay then click Reference.
Click Advanced Reference Features then click Reference Q-Z.
Click Threshold Deductions.
📌Note: Support may be required to set the threshold_ded to Y in the pay_code table for this pay code so that it can be recorded on the Threshold Deductions screen.
ASCable pay
There is no ASCable pay for one employee.
To resolve this issue, a support analyst will work around this by entering a one-cent manual timesheet under an ASCable pay code for employees with no ASCable pay.
Please raise a new case online and reference the title of this article. Include the following details:
Affected employees
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Space in position code
The position code has extra spaces in its name. To resolve this, a support analyst will check the specific error from the log file.
Please raise a new case online and reference the title of this article. Include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.