ER 91637 Make future-dated enrollment events reflect employee's future-dated eligibility
Our Benefits staff has noticed that when a future-dated enrollment event is created, the employee's current eligibility is referenced, not their future eligibility matching the date of the enrollment event. This means that when an employee has a future-dated transfer with an FTE change that will make them newly benefit-eligible, their change-of-status enrollment event cannot be created in advance - if it is, the employee's current benefits eligibility (or lack thereof) will be wrongly reflected in the enrollment event. Instead, our Benefits staff has to consult a spreadsheet daily looking for current-dated transfers who might have a change in eligibility, and then they have to manually create the change-of-status enrollment event on or after the effective date of the transfer.
I've created ER 91637 asking for future-dated enrollment events to reflect the employee's benefits eligibility as of the date of the enrollment event. This would allow future-dated enrollment events for transferring employees to be created in advance of the effective date of the transfer, would prevent the daily manual workaround by Benefits staff, and would prevent missing enrollment events for transferring employees.
Please endorse this enhancement request if you see the value in it!
Comments
-
Hi Noelle,
We have similar issues with employees moving to a newly eligible for benefits status so I endorsed your enhancement.
We have been able to schedule a job to create new hire and rehire life events so that they are created on the day the employee starts working using a custom group. However, we have been unable to schedule a job to create life events for newly eligible employees because the change date is not easily available to reference in a custom group. If you are tracking the newly eligible change date in one of the Other Date fields on the employee business class, you might be able to schedule a job to create the life event using a custom group.
0 -
To piggyback on Rhonda's suggestion, we use Other Date 2 field as a custom date field that triggers all types of benefit enrollment events. We found that using any of the out of the box date fields would not work for us because we have a very complex benefits program.
0 -
Do you have a custom program to populate the Other Date 2 field? And do you populate it for all benefit eligible employees?
0 -
Great question. Yes, we have a custom hire, rehire and transfer flow built into the system that calculates the correct Other Date 2 and populates it for us.
0 -
Hi Rhonda,
Thank you for the endorsement, and for your suggestion!
We just recently started filling out the Enrollment Event and Event Date fields on the Hire & Rehire forms, which is automatically creating the new hire enrollment event now (though it is future-dated, to match the EmploymentStartDate). I'm curious, what are the advantages to having the job create the enrollment event on the employee's start date instead of having the enrollment event created automatically from the Hire & Rehire forms? One advantage I can see is that if the employee's start date, FTE, etc. were changed before they started working, we wouldn't have to manually delete and re-create the enrollment event to update it. Are there other advantages that you're aware of?
0 -
Hi Noelle,
As you mentioned, start date changes are the main reason we scheduled the job to created new hire and rehire life events. We have so many start date changes that our Benefits team was performing many manual tasks to clean up life events.
Another reason we scheduled this job is to ensure employees don't receive the email notification to complete their life event before their start date. The email notification is delivered when the life event is created. Before making this change there were occasions when an employee received the notice to their personal email and they tried logging into the system before their start date.
0 -
Thanks! That's great food for thought.
0 -
Waking this up as I imagine the enhancement was rejected. Wondering if anyone has found any other good ways to do this.
0 -
The enhancement request received 11 endorsements, is in Deferred/Future Consideration status, but is also in a State of Prioritized. I'm not quite sure how to interpret that combination, but it's 2 years old this month, and obviously nothing has happened with it yet.
0
Categories
- All Categories
- 3 General Posts
- 6 Public Sector
- 5.8K Developer Community
- Migrated Forums
- Cloud Migration
- 5 Community News
- 2 User Groups
- 4 Featured Content
- Featured Developer
- Featured Public Sector
- 4 Featured Forums
- Featured Healthcare
- 2 Announcements
- Customer Bulletins
- In the Birst Space
- Legacy Blog Posts
- 132 RMS News
- Site News