Skip to main content

Payday filing errors

Resolving errors with payday filing through myIR integration

Jessica McLean avatar
Written by Jessica McLean
Updated over 2 weeks ago

If you are using the myIR integration in PaySauce file your own payday filing and the filing fails you will have received notification about the error. In this article is a list of common errors and how to resolve them.

Once the error is resolved please contact PaySauce Support so we can resend your payday filing.

If you would prefer to do this yourself via myIR click here to find out how.

Errors

myIR account

Common errors in payday filing you may encounter relating to your myIR account.

Error

How to fix the errors

Authentication failure

The authentication failure error occurs when there has been a change to your IRD log in details/portal e.g. password has changed.
​
To fix this, you will need to disconnect your MyIR connection in PaySauce by going to Company Settings > Integration > myIR then clicking on the 'X' button. You will then be able to Connect to IRD again using your updated MyIR username and password details.

Missing authentication token(s)

The missing authentication token error occurs when there has been a change to your IRD log in details/portal e.g. password has changed - same as authentication failure above.

Unauthorised access / delegation / vendor

This MyIR login does not have the appropriate permissions to send payday filing. You can review our MyIR integration article for information on the required permissions and how to set them.

Pay run

Other errors in payday filing you may encounter relating to information from the pay run.

Error

How to fix the errors

The IRD has no record of employee (given name and surname)

Ensure the employee's details are correct in PaySauce and you have submitted the payday filing of employee details to the IRD so that the IRD has the employee on record prior to resubmitting the payday filing of employment information.

The recorded date of birth does not match what the IRD has on file

Check the employee's date of birth within the employee's details in PaySauce. Submit the payday filing of employee details to IRD to correct details first before resubmitting the payday filing of employment information.

The recorded start date does not match what the IRD has on file

Check the employee's start date within the employee's employment details in PaySauce. Submit the payday filing of employee details to IRD to correct details first before resubmitting the payday filing of employment information.

The IRD is expecting tax code <employee tax code> for this employee

Check the employee's tax code within the employee's tax settings in PaySauce. Submit the payday filing of employee details to IRD to correct details first before resubmitting the payday filing of employment information.

Duplicate payday submission

You have already previously submitted the payday filing employment information for the same reporting period. Check to ensure whether you need to submit a payday filing amendment.

Period too far into the future

Unable to submit payday filing with pay period date too far into the future. Check your pay period date and ensure the correct dates are set.

Invalid filing period

Same as "Period too far into the future" above.

XML request failed validation

Data issue not accepted by the IRD e.g. negative gross earnings. Negative earnings are not accepted by the IRD. You will need to ensure gross earnings are presented as positive amounts.


You should also check the business phone numbers entered do not include any spaces or brackets.

Payroll contact phone number is required in the business IRD settings

The phone number must contain 9 digits, including the area code. For international numbers, there is a maximum of 12 digits allowed, no special characters.

Very rarely you may be presented with a payday filing error that says 'did not decode status' or 'object object'. These happen very infrequently and need to be investigated by our Support team when they occur, so if you see this message please report it to our Support team.

Did this answer your question?