Common Close Pay Errors
Please note:
- If you need to Rollback the pay to fix it, you will need everyone else logged off the database.
To Rollback, refer to the PayGlobal Help File for further information 
- You can use the Eject User function and apply the lock to stop more users logging in.
Refer to the PayGlobal Help File for further information
Error | Solution |
|---|---|
| Close Routines failed - Last successful step was 0 - Failed during MastUpdate | This will be an employee that has been moved to a different period code. You will need to delete them from the pay you are trying to close.
|
| General zero FTE Hours proof failure by : 1094.42 Fault detected with employee : 3424 Zero proof FTE hours : 1094.42 Failed during IntegrityOk | This is usually caused by an employee being paid more than 999.99 hours annual leave on termination. This error can also occur if you are reversing a termination and the negative AL termination hours are more than -99.99. To resolve issue you will need to manually enter the Annual Leave on Termination with quantities of less than 999.99 or less than -99.99 hours in multiple transactions. |
| Not all employee/entity updates were completed. The most common reason for this is that another user has these records locked. Once those users have released these records, then the pay closing procedures can be resumed.Failed during EntityUpdateClose routines failed, last successful step was 0 - | This is usually caused by a User Defined field being updated on close pay with amounts that exceed the size of the User Defined Field Settings.For example:Field Size of UDF is 6 and 2 decimals. This means that you can enter 999.99 (the decimal point counts as a character). |
Not all employee/entity updates were completed. The most common reason for this is that another user has these records locked. Once those users have released these records, then the pay closing procedures can be resumed. Failed during EntityUpdate Close routines failed, last successful step was 1000 - EntityUpdate | This is usually caused when either the FTE or Total Amount on the Costcentre exceeds the field size. The size is 10 numerals, including decimal point. To resolve, clear out the Total Amounts / FTE on the Costcentre records. |