Prevent Accidental Back-out of Scheduled & Unrestricted Life Events in Bulk

Welcome to this demonstration of the 25C, Prevent Accidental Back-out of scheduled and unrestricted life events in bulk in HCM Benefits.

This feature adds validation safeguards to the Back Out Life Events process for Open, Administrative, Unrestricted Open and Unrestricted life events.

Administrators need reliable safeguards when managing large-scale life event operations and protection against costly data loss and time-intensive manual recovery efforts.

By using this feature, you can prevent unintended data loss by limiting bulk backouts of life events that would result in a voided status, preserving critical enrollment information and reducing the need for manual recovery.

Let’s start with doing a quick overview of the new feature.

It only applies to the open, administrative, unrestricted open and unrestricted life events when running the back out life event processes.

A new parameter called “Estimate of Impacted People” is enabled when you select resulting status of “voided”. This parameter is defaulted to 50 but can be modified as needed. If the actual number of persons being back out exceeds the estimated by more than 5%, the system will error and you will need to modify your estimated number.

You are required to select one of the process parameters such as organization name, location, benefits group, legal entity or a person selection formula.

The new estimate of impacted people parameter field will display for both rollback and saved modes.

And selecting resulting status for Unprocessed works as normal but you should verify your reinstatement rule prior to backing out.

Now let’s take a look at this new feature. I have logged in with a user who has the benefits administrator role.

Within Benefits Administration I will select evaluation and reporting.

Staying on the summary tab I will select the Processes tab.

First we’ll look at how this new feature works with the administrative and open scheduled life events. Locate the backed-out life events process and select submit.

For this demonstration I will be backing out the January 1, 2026, open enrollment.

I’ll leave the effective date defaulted and the validation mode defaulted. I will select Open out of the list of values.

And I will change my occurred date to January 2026.

And the to occurred date to January 2026.

I am going to skip down to the resulting status area and change this to voided. Remember the validation only occurs when the resulting status is voided, not manual or unprocessed.

Notice we did add to the resulting statuses giving you more information. For the Manual we have requires manual intervention by the administrator. Unprocessed, data can be reinstated if rules are setup.

And when selecting voided you can see data cannot be reinstated. I have selected voided. And notice a new field appears, the Estimate of Impacted People. I see it’s defaulted to 50, which can be adjusted. The validation will only be done when the number of persons being backed out is greater than this estimated amount. So, if I leave the estimated number at 50 and I only have 30 employees backing out there will be no validation or no error. If the number of employees backed out is 75 then the process will error because 75 is greater than the 5% allowance on 50. I will leave at the value of 50. I will enter a reason of why we’ve backing out this life event.

And I must also select one of the parameters listed here. If I do not select one of the parameters listed here it will error. I am going to select the benefits group. Once all of the data is entered click on submit. Click on ok for the confirmation.

Scroll down to the bottom. And click on search.

I can see that my backed-out life event completed successfully.

Scrolling down I can see where I had a back-out life event that errored.

If I click on the log, I can see the error message telling me in this particular process I needed to select a parameter. Now let’s look at the new feature in the unrestricted backed out process. I will scroll up and locate the backed out unrestricted life events and select on submit.

I will let the date and validate mode default. Like with the open and administrative life event you must select one of the parameters. I will select on benefits group.

You must enter in a reason for backing out your life event. The estimate of impacted people field is already displayed and is not dependent on the resulting status, as unrestricted life events are always backed out to voided status. I will leave it at 50. Once all of the data has been entered, click on submit. Scrolling down I can see the results of our backed out unrestricted life events. If it errored we can click on the log and see what our error message is. To help determine the estimated number of persons, consider looking at life events under the summary tab. Select your status of started, select your life event in this case open. And select your view by, I will select benefits group. And then I will run.

And I can see I have total number of 12 employees with this particular life event that I might consider backing out. Another option would be to review the log for your scheduled process.

If I scroll down and search for my scheduled process for open enrollment and click on the reports icon I can get an estimate of the number of employees who have an open enrollment life event.

Here are the error messages that are returned with this new feature.

When no parameters is selected, you will see you need to select at least 1 person selection parameter in your error log.

And when the number of persons is greater than 5% of estimated amount, you will see this process affects the enrollments of 62 people, which is the number of people evaluated, which exceeds 5% of your estimate. You need to enter a new estimate and try again.

Parameters will be evaluated first and then the estimate number when returning error messages.

This concludes this demonstration. Thank you for watching.

You can refer to the 25C What’s New documentation for more information on this feature.