Skip to main content

Unable to update an absence end date: The workflow 'Absence - Reject SelectPay Absence' failed unexpectedly

Unable to end an open ended sickness: The workflow 'Absence - Reject SelectPay Absence' failed unexpectedly.

H
Written by Harry Ledger
Updated over 3 months ago

This guide details the troubleshooting steps to follow if you are unable to add an end date to an open-ended sickness.

  1. In the Absence zone, click Absence, then Absence History.

  2. Open the record for the open-ended absence.

  3. Check to see if there is a Paid Up To date populated. If a date has been entered, to change the absence end date, it will need to be made a fully paid absence by amending the absence end date to match the above Paid Up To date.

  4. A new record for any remaining absence after that date will then need to be entered.

If no Paid Up To date is visible, please follow the steps below.

  1. Navigate to your Absence Transactions process by searching for Absence Transactions in the search bar.

    πŸ“Œ Note: If you do not have this on your menu, you will need to add it manually.

  2. The Originator column will show where the absence was created. If there is a record for the employee that has originated from SelectPay, then this will need to be actioned to remove the block.

  3. If the Status column shows Rejected then by selecting this record and clicking Accept you will be accepting the rejection. As an example, an absence was entered with no end date, this was rejected on the SelectPay side, and this rejection is then accepted by Select HR, and the record is deleted.

If the affected employee does not show in this list, then please raise a new case online and reference the title of this article, confirming the name of the employee.

What if I can't make any amendments to the absence at all?

This is likely going to be caused by the fact that the absence has been processed in both systems separately and has also been fully paid out. Now that they no longer match, and the absence has been paid out, the absence transaction may have become stuck.
​
If you believe this is the case for you after following the above troubleshooting, please raise a new case online and reference the title of this article.

Did this answer your question?