This would save a lot of time and be very helpful!

Would be very helpful for payroll accuracy.

Would be extremely helpful if removed

Super important - would save our team hours of manual work when processing payroll, along with ensuring that the data is accurate

Would save hours when I'm processing payroll.

Please do this, it would be super helpful

very important, please action

Critical for all payroll teams

Will streamline the process, please do this!

Do it

Highly important to ensure accuracy in payroll!

100% need this!

All recent comments are spot on. This is incredibly important and not having it makes building a proper integration impossible.

This is so unbelievably painful when trying to use products such as Employment Hero that integrate with Xero Payroll.

When employees delete a leave request, they expect their balances in Employment Hero (pulled from Xero) to update in real-time.

The current workaround is for Employment Hero to send an email to the Payroll Team instructing the Payroll Team to delete the request in Xero manually.

Given how many of these requests happen, it is only practical for the Payroll Team to process these deletions fortnightly.

This leads to a high volume of support requests from Employees who think that because the system isn't reporting in real-time, the system is broken.

The Payroll Team then has to explain that it is a Xero limitation and that their leave balance will return to normal when the deletions are batch-processed at the end of the fortnight.

This is an absolutely critical feature for Xero's integration partners and it's an embarrassment that it hasn't been implemented in 6 (six) years.

Critical need for this for an integration product

Wow um, 6 years and waiting for a critical feature

Not sure why i have to vote for this feature. This is a must have operation for leave applications.

You can't do a complete integration if it doesn't support full CRUD operations. It's crazy that it's not supported, and hasn't been for so long.

This endpoint is required for integration with our AU customers. Your NZ and UK libraries support this functionality.

It's been 7 years....take stock of that for a second. 7 years to implement a basic CRUD function....