Select your platform and then browse by platform category

Who are you and what section are you in?

Xero error: Salary/pay has been locked in Xero and cannot be updated

Error

Type Feature Error Name
Sync error Pay Salary/pay has been locked in Xero and cannot be updated

Explanation

The error "The salary/pay has been locked in Xero and cannot be updated" occurs when there is a mismatch between the salary version data in Employment Hero HR and Xero. This issue typically arises when:

  • Manual updates: Salary or pay rates are updated directly in Xero but not in the HR platform, leading to inconsistencies between the two systems.
  • Locked salary versions: Once a salary version is locked in Xero (e.g., included in a pay run), it cannot be updated. Instead, a new salary version must be created.

Xero enforces this logic to maintain data integrity, and the error seen in Employment Hero reflects the sync response returned by Xero.

Note: To avoid errors, treat Employment Hero as the source of truth for pay details across integrated platforms. Ensure any updates are made in the EH platform first.

Solution

To resolve the error, follow these steps:

  1. Verify pay details: Ensure that pay details in both Employment Hero and Xero match before updating an employee file. This will ensure a successful sync.
  2. Create a new salary version:
    • If the error occurs, create a new salary line in Employment Hero.
    • Use a current or past effective date when creating the new salary version.
  3. Manually sync: After adding the new salary line, manually sync the updated pay details to reconnect the integration.

By maintaining consistency between the platforms and following these steps, you can avoid or resolve the sync issue efficiently.

Explore related content:

  • 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