If the payroll validation job is stuck at 1 or fails, several reasons may be causing this issue.
To resolve it, first, retrieve the log file to identify the reason for the payroll job failure. To do this, follow these steps in portal.
Click Manage Payroll then for the relevant pay group, click Process Payroll.
Beside the relevant payroll validation job, click the three-dot icon.
Click View Log File.
📌Note: The last lines of the log file will provide an error message detailing the issue. You can also press CTRL+F and search for "ORA-" to find errors.
We’ve compiled a list of possible causes for payroll validation failures and how to resolve them. Follow the steps below based on the identified cause.
Apprenticeship levy calculation
An issue with the apprenticeship levy calculation job can cause failure. Look for the following error in the Pay140 log file:
" **Start UnHandled Exception
SOURCEREF:s33750_apprentice_levy
EMPNO :EMPNO
ERRNO :100
ERRMESS :ORA-01403: no data found
**End UnHandled Exception - Contact Support HelpDesk "
To resolve this, review the apprenticeship levy pay code. To do this, follow these steps.
Click Settings, then under UK Tax Rates, click General.
Scroll to the bottom of the page, then click Other.
Select Apprenticeship Levy.
In the Select dropdown, click Company Parameters.
If you find any inaccuracies, update the pay code then reset the job and re-run the validation.
Payroll calendar setup
An issue with the payroll calendar setup may also lead to failure. Check for the following error in the Pay140 log file:
" **Start UnHandled Exception
SOURCEREF:s3000_declare_cursors
EMPNO :
ERRNO :-1843
ERRMESS :ORA-01843: not a valid month
**End UnHandled Exception - Contact Support HelpDesk."
To resolve this, review the payroll calendar. To do this, follow these steps.
Click Settings then under Company Parameters, click Calendars.
From the dropdown menu, select the applicable company.
Check that the records for the period you are processing and the previous period are accurate.
If you find any inaccuracies, update the pay code then reset the job and re-run the validation.
If you are unable to identify the issue, please raise a new case online and reference this article. Our support engineers will review the calendar in more detail.
Pension scheme pay code setups
One or more pension scheme pay code setups may be incorrect, leading to failure. The following error appears in the Pay140 trace file:
" SOURCEREF:Pension Scheme Pay Codes should analysis type TR.
EMPNO :
ERRNO :0
ERRMESS :ORA-0000: normal, successful completion
**End UnHandled Exception - Contact Support HelpDesk."
To resolve this, ensure that any new pay codes set up for pension schemes are allocated to the correct analysis codes. To do this, follow the steps below.
Click Settings, then under Codes, click Pay Codes.
Search for the pay code then click the three-dot menu.
Click Edit, then check the Analysis Code field.
The analysis code should have the analysis type set to TR- Tax Relief Deduction. If you find any inaccuracies, update the pay code then reset the job and re-run the validation.
Net pay paycode's configuration
An issue with a net pay pay code's configuration can also cause failures. Check the Pay140 trace file for the following error:
" **Start UnHandled Exception
SOURCEREF:Net Pay Pay Code should have an analysis type NP 1800
EMPNO :
ERRNO :0
ERRMESS :ORA-0000: normal, successful completion
**End UnHandled Exception - Contact Support HelpDesk."
To resolve this, check that any new pay codes set up for net pay are allocated to the correct analysis codes:
Click Settings, then under Codes, click Pay Codes.
Search for the pay code then click three-dot menu.
Click Edit then check the Analysis Code field.
If you find any inaccuracies, update the pay code then reset the job and re-run the validation.
General Ledger (GL) Matrix configuration
An issue with the general ledger matrix configuration can lead to failures. This occurs when the system is set up as if a matrix is in place, but no matrix actually exists.
Before clearing out the failed job, we recommend downloading the log file to review it for any ORA errors. Follow these steps:
1. Click Manage Payroll then for the relevant pay group, click the three-dot icon.
2. Click Log File.
Download the file and press CTRL + F to search for ORA- errors. Pay special attention to the Pay140 trace file for the following error:
**ERRMESS: ORA-01000: maximum open cursors exceeded
ORA-06512: at "COREHR.A_PAY300_OUTPUT", line 14
ORA-04088: error during execution of trigger 'COREHR.A_PAY300_OUTPUT'**
To resolve this issue, please raise new case online and reference this article title. Remember to attach the log file.
📌Note: If a GL Matrix is supposed to be configured, please direct the request to Optimisation Services for setup.