Invalid payroll calendar ID | Xero Error

Error

Type. Feature. Error Name.
Employee file. Pay details. A validation exception occurred, Invalid Payroll Calendar ID.

Explanation

This error occurs when an employee's pay schedule in Employment Hero does not match any current pay calendars on your Xero platform. When the Employment Hero platform encounters this issue, it will not synchronise the employee's file over to your Xero platform.

Solution

You will need to add the pay schedule to your Xero platform and then re-sync Employment Hero with your Xero platform to resolve this issue.

Resolve this error
  1. Log in to your Xero platform.
  2. Click the Organisation Name   button.
  3. Click the Settings button.
    Xero_1.jpg
  4. Click the Payroll Settings button.
    Xero_2.jpg
  5. Click the Calendars tab.
  6. Click the Add button.
    Xero_3.jpg
  7. Complete the following fields:
    • Pay period.
    • Name.
    • Start date.
    • First payment date.
    • Make this my default pay calendar for new employees.
  8.  Click the Add button.
    Xero_4.jpg
  9. Log into your Employment Hero platform.
  10. Click the   Settings menu.
  11. Click the Pay Schedules submenu.
  12. Click the   Update From Payroll button.
    Xero_5.jpg

    Helpful Hint

    The Pay Schedules page will now show a greyed out   Updated button and means Employment Hero has successfully imported your pay schedules from your Xero platform.

    Xero_6.jpg

Author recommended

So you have now resolved your xero error and you are now wondering, what next can I do. There are two recommendations I would make on this front and they are:

  • Leave balance visibility | Xero Guide This guide walks you through how to customise your employee's leave balance visibility in your Employment Hero platform.
  • Common Xero Import Conflicts This section contains a range of error resolution articles that cover common import conflicts our clients run into when syncing their Xero data.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.