We are pleased to announce the upcoming Release of BenefitElect (BE). As always, we hope the features and fixes demonstrate our commitment to you, our clients, software that is designed to help you be successful as you navigate the world that is Benefit Administration. Here is a breakdown of items addressed in the release
Break in Service
The system has been modified to let users know when Break in Service processing is occurring on a selected employee. Now, when an HR Admin rehires an employee, they will receive a message to let them know break in service processing is occurring and user will be redirected to the employee home. The employee information will be left in the search so the HR Admin can go back to the record easily.
The Break in Service rules have been enhanced to further support different enrollment rules upon rehire. For example, you could have a standard reinstatement rule: If rehired within 90 days, employee picks up coverage immediately upon rehire date. However, you can now add a sub rule to indicate if the employee is rehired within 30 days of last employment, benefits are to be reinstated using original effective date. Please reach out to your System Analyst for more details if you are interested in hearing further details into this new functionality.
We have changed the default behavior for employee status grid to sort data in descending date order. Therefore, the most recent employee status records will display first. This is especially beneficial if your organization has a re-occurring workforce and therefore several status records may exist for an employee.
- However, if you prefer to see information in ascending order, any user can change the sort order and upon next and future access the sort order will remain as you selected until you change it. **Note, we previously made a similar type of change in a previous release, however, it was determined the setting could get lost and that has been corrected.
In a prior release we made enhancements so that employee field pop ups would render in a consistent location on screen when using Chrome, Firefox, and Edge. We have now made similar improvements for IE 11.
IMPORTANT NOTICE regarding the support of different browsers for the BE HR Admin Application.
Although we will continue to support IE 11 if used with Windows 10 operating system, we strongly encourage all clients to use the following browsers to ensure the best user experience:
- Chrome, Firefox, and Edge
Please reach out to your system analyst if you have any questions or concerns.
A small change to add a $ before the amount of employee cost in the enrollment site header on the 4.6 theme
Additional IBC validation has been added to hold off processing an additional IBC if other processing from a prior IBC is still occurring. This relates to New Hire enrollment, Prehire, Rehire, new users being established, and Automapping processing that is triggered from an IBC. This change is to ensure that when an IBC is loading, the process has access to the latest employee data on file for consideration.
Multiple changes are occurring behind the scenes to support payroll integrations through API’s. **More to come on this in future releases.
**Note, already live in production: The default wording and formatting on the notification that will go out to Prehire’ s when the Bulk Prehire method is used has been improved upon.
Added functionality so that when an employee goes from Prehire to Active status, the next time the now employee logs into system they will be directed to change their password, allowing them to access the enrollment site the same as other employees in subsequent years.
Added support for the use of IPAD’s with specific browsers in assisting the HR Admins with onboarding Prehire’ s into the BE system. Please reach out to your System Analyst if this is something that you are interested in hearing more amount as the functionality is specific to the onboarding process.
Multiple changes are occurring under the hood in support of a new updated reporting tool. **More to come on this in future releases.
Corrected issue where an incorrect stop date was being applied to overage dependents if their birthdate was at the end of the month for certain months. Now, regardless of their birthdate, the stop date will be the end of the month.
Addressed a potential user security issue for clients that use organizations, and a user was set up without organizations.