ERROR: A termination transaction must be entered so pay can be processed successfully for a terminated employee.
If you are supposed to be paying a terminated employee, you need to add the Termination Allowance into the pay. This could be allowance code X or some other code specific to your database.
ERROR: No last full pay found for marginal tax calculation.Tax at marginal rates: Normal gross earnings .00, using calculation method LF (last full pay sequence = 0).Normal gross earnings were automatically calculated.
Open the Pay Header (Day's worked transaction) and either select a different pay, use Average Earnings or Use Override Gross and add an Override Gross amount.
Please click Here for more information.
ERROR: Entity “PayGlobal.Business.Appointment” has an invalid date range. Start date is 1/7/2024 and end date is 30/6/2024
Edit the employee’s Appointment record and amend the dates correctly.
ERROR: A direct credit deduction for this Employee has an empty bank account for this pay
There is a deduction set up with “Direct Credit” YES that does not have a bank account in the deduction in the pay. You need to open the deduction and add the bank account.
ERROR: Zero proof failure in one or more employee pays
ERROR These pays must be corrected before a final process.
ERROR Pay processing procedures UNSUCCESSFUL
The “Zero proof failure processing pay sequence” is normally caused by Employee details were changed after the pay was opened. Delete the employee from the pay and re-process. This should resolve the issue.
ERROR: Other open pays were found for this employee that are not linked to termination payments. Please process and close the other pays first, or delete the transactions in them for the employee.
ERROR Pay processing procedures UNSUCCESSFUL
-
Use the Delete Employee from Pay Sequence function as they are being terminated in a separate pay.
-
Delete the employee from the Pay Sequence. For assistance click here
-
Do not re-process the Standard Pay until the manual pay is closed.
ERROR: Error running pay processing datamodule
ERROR Error is Cannot locate associated Award item belonging to AwardRate with ID of '956'. (AssociationResolutionException)
ERROR Pay processing procedures UNSUCCESSFUL
This might occur if some Award Rates had been sychonised in with an Incorrect Award code to attach it to. You need to remove the Rates that are not attached to an award. Check Organisation / Entitlements / Award Rates for records with a blank Award Code.
Cost Centre Errors
ERROR Cost centre '322' expired on 02/07/2017.
Processing 1234567 John Doe
ERROR Cost centre '8718' expired on 02/07/2017.
ERROR Some costcentres and/or jobcodes have expired
(when compared to the period ending date of this pay sequence)
ERROR Pay processing procedures UNSUCCESSFUL
You will need to remove the Expiry Date on the CostCentre record in the CostCentre table.
ERROR Could not locate CostCentre with code '**********'
This error usually occurs when a new Costcentre has been setup, but the corresponding costcentres for ‘wildcarding’ (EG: Super, Annual Leave, Oncosts etc.) have not been setup
To resolve this error, add the missing costcentres to the Costcentre table.
ERROR: Other open pays were found for this employee that are not linked to termination payments...
This error occurs when an employee is being terminated in a manual pay when they have transactions in an open standard pay.
To resolve this issue and process the manaul pay before closing the standard pay, you need to delete the employee from the Standard Pay. Click here for instructions
Do not reprocess the Standard Pay until you have closed the Manual Pay.
ERROR: Object reference not set to an instance of an object
This error can occur when costcentres have been removed via a Sychronisation or were never setup.
To resolve, you will need to add the missing costcentres back into the Costcentre table.
ERROR: There is no valid SuperSettings record for this pay period, process failed.
To resolve this error, make your way to Payroll / Superannuation / Super Settings Groups and open the default group.
-
Click on Edit then right click and select ‘Add Record’
-
Enter the Start Date, Max Earnings base ($) and SG minimum percentage.
-
Save and close.
Refer to the latest End of Year procedures for the proper values to enter.
Click here for the EOY Manuals
Error: Current KiwiSaver State record with a State of "Holiday" and KiwiSaver savings suspension period has expired. Process failed.
Employee has been on a KiwiSaver Suspension/Holiday. Because KiwiSaver Suspensions/Holidays are only valid for 1 year, this has now expired.
To Resolve you will either need to add another Kiwisaver Holiday State record (if you have received a notification from the IRD) or add a new In/Out etc. record depending on the employees circumstances.
ERROR Leave credit "ADO" could not be processed because the employee does not have that leave credit assigned.
The error occurs when you import leave, from ESS, Time & Attendance or another source and the employee does not have that leave credit setup on their employee record on the Leave Credits tab.
If the employee is supposed to have the Leave Credit on their record, either add the Leave Credit Table on the Leave/Leave tab or adjust the table to the correct one including the Leave Credit.
If the employee is not entitled to apply for that leave type, delete the transaction from Transaction view and re-process the pay.
Error Occurred : Attempted to divide by zero.
This issue occurs when the YTD Code does not match the pay its being processed in.
To resolve this issue, change the YTD code on the accumulators for the pay to the correct year’s code.
See the following links for further assistance with changing the accumulator.
Adjust Manual Pay Accumulators - AU
Adjust Manual Pay Accumulators - NZ
ERROR occurred : Entity 'PayGlobal.Business.Payroll.EmployeeSuperannuationFund' has an invalid date range. Start date is 30/06/25 and end date is 15/06/25. Start date must be less than or equal to the end date.
This error occurs when there is invalid dates on Superfund Records.
To resolve this issue, open the offending Employee Super Fund record and fix the dates.
ERROR The employee needs to have a current active superfund given the employee has a KiwiSaver state of "In" or "Holiday" or "Exempt". Please fix.
This issue can occur if the employee does not have an active superfund with cover the pay being processed.
To resolve you will either need to amend the dates so they have a current superfund on the Employee’s Superannuation tab or add a Kiwisaver state of out or similar.
Error occurred : No AllowanceGroup provided
This issue occurs when a new Payroll rule or a Payroll rule is updated that includes and allowance group that does not exist in your database.
To resolve this issue you will need to check any newly created payroll rules or recently updated payroll rules that include allowance groups for the calculation.
If you cannot find the rule, please contact MYOB PayGlobal support for assistance.
Error occurred : Employee Definition of Week record missing for Employee "", Effective Date "" (MissingEmployeeDefinitionOfWeekException)
This issue can occur if the employee does not have an active Definition of a week record with dates that cover the pay being processed.
To resolve you will either need to amend the dates if incorrect on the Definition of a week record, or add one if the employee does not have one.
ERROR Error is Entity 'PayGlobal.Business.Payroll.AwardRate' has an invalid date range. Start date is 29/06/2009 and end date is 27/06/2009. Start date must be less than or equal to the end date. Recommend an integrity check be done. (DateRangeConstraintException)
This error will occur if the Start date is later than the end date on any ‘Award Rate’ in your database. This may have occurred if the new rates were synchronised into your database incorrectly.
See example below:
The highlighted record has a start date of 29/06/2009 to 27/06/2009.
To resolve this issue, you will need to find the incorrect record and adjust the end date.
ERROR Could not write to table TransPerPaySequence as it is currently locked paySequenceId=1525, processingId="c7969034-8961-4d82-9fcf-3ef5ea71fec4"
This error may occur if the Process Pay function has been run by multiple users and the first process has locked the table or the Process Pay action has been initiated multiple times by the same user if it was hanging.
To resolve this issue, please contact MYOB PayGlobal Support to have the lock removed via SQL.