This page (revision-11) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 5 KB jmyers to previous
10 26-Nov-2021 10:22 5 KB jmyers to previous | to last
9 26-Nov-2021 10:22 5 KB jmyers to previous | to last
8 26-Nov-2021 10:22 8 KB jmyers to previous | to last
7 26-Nov-2021 10:22 7 KB jmyers to previous | to last
6 26-Nov-2021 10:22 8 KB jmyers to previous | to last
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 2 KB JEscott to previous | to last
3 26-Nov-2021 10:22 2 KB JEscott to previous | to last AD HOC OPEN ENROLLMENT PROCESS FLOW ==> AD HOC OE PROCESS FLOW
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last AD HOC OPEN ENROLLMENT PROCESS FLOW ==> AD HOC OE PROCESS FLOW
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
The Open Enrollment (OE) business process requires proper setup and configuration of benefits plans, rules and rates. Much of this will already be in place if you are already using the Benefits module; however, there are new forms and new fields in existing forms to support this process.
[{TableOfContents }]
!!!OPEN ENROLLMENT PROCESS FLOW
At line 3 changed one line
Open Enrollment periods may be generated for a mass group of employees, for individual employees who have had a life or work event occur, and they may be generated on an ad hoc basis.
The Open Enrollment (OE) business process requires proper setup and configuration of benefits plans, rules and rates. Much of this will already be in place if you are already using the Benefits module; however, there are new forms and new fields in existing forms to support this process. The setup requirements are discussed in the next section.
At line 5 changed one line
Once the Open Enrollment period is generated, employee elections may be done in a single web session or over a period of time in several web sessions. When employees have completed their elections, they must submit all of their elections for approval. Upon submission, the Benefit Administrator is notified by a workflow email that the elections have been done and are awaiting approval.
On a periodic or ad hoc basis, Benefit Administrators will initiate Open Enrollment for selected employees and plans for a specified period of time. For Mass enrollments this will be done through a process called [UBOE]. Open Enrollments for ad hoc purposes are manually created in the [IBOE]. For life or work events, the Open Enrollments are created in the [IBEV], or they may be triggered by workflow when HR changes are entered in the systerm. At the time the Open Enrollment is initiated, employees who are involved will be notified by email through workflow and will be instructed to make their election choices. In Self Service [WEBOEE], is available for employees to view their elections. Before the employee begins, they are instructed to make sure their demographic and dependent information is up-to-date.
At line 8 added 10 lines
Employee elections may be done in a single web session or over a period of time in several web sessions. When employees have completed their elections, they must submit all of their elections for approval. Upon submission, the Benefit Administrator is notified by a workflow email that the elections have been done and are awaiting approval.
An employee must identify when there has been a life and/or work event that affects their benefit plans. Once the Benefit Administrator has reviewed their situation, the employee will be requested to make their elections related to their life and work event before making any mass Open Enrollment elections. Event types are defined on [IBET]; this is also where the Administrator will associate plans to an event. Employee life and work events can be recorded on [WEBEV]. Benefit Administrators can also record these events in [IBEV]. Life or Work events may be automatically created by workflow triggers when certain changes are entered in the system. These triggers would then create the life work event and thus the open enrollment, as long as the Allow Auto Open Enrollment toggle is checked ON for the Life Work event in [IBEV].
If an employee records a life or work event during an Open Enrollment period, it will be up to the Benefit Administrator to review the situation and determine which Open Enrollment period the employee should be making their elections in. The dates of the Open Enrollment period may need to be adjusted accordingly.
Occasionally, Benefit Administrators will want to open up enrollments for selected employees and plans for special reasons. Employees will be requested to make elections related to these ad hoc Open Enrollments before making any mass Open Enrollment elections.
When a Benefit Administrator receives notification that an employee has submitted their elections, the employee’s Open Enrollment will go through a review and approval process that may involve multiple approvers. Elections may be processed as soon as they are submitted. Benefit Administrators do not have to wait until the Open Enrollment period is closed.
At line 10 changed 3 lines
*If an employee declines an election they are already enrolled in and the Track Decline toggle is ON for the plan in [IBPN], the [IBEN] enrollment record will be updated with a status of Decline.
*If an employee declines an election they are already enrolled in and the Track Decline toggle is OFF for the plan in [IBPN], the [IBEN] enrollment record will be updated with a status of Decline.
*If an employee declines an election they are not currently enrolled in and the Track Decline toggle is ON for the plan in [IBPN], an enrollment record will be created in [IBEN] with a status of Decline.
*If an employee declines an election they are already enrolled in and the Track Decline toggle is ON for the plan in [IBPN], the [IBEN] enrollment record will be updated with a status of 'Decline'.
*If an employee declines an election they are already enrolled in and the Track Decline toggle is OFF for the plan in [IBPN], the [IBEN] enrollment record will be updated with a status of 'Decline.
*If an employee declines an election they are not currently enrolled in and the Track Decline toggle is ON for the plan in [IBPN], an enrollment record will be created in [IBEN] with a status of 'Decline'.
At line 18 changed one line
[Mass Open Enrollment Process Flow|MASS OE PROCESS FLOW]
The following pages outline the process flow for each type of open enrollment process:
*[Mass Open Enrollment Process Flow|MASS OE PROCESS FLOW]
At line 20 changed one line
[Life and Work Event Open Enrollment Process Flow|LIFE AND WORK EVENT OE PROCESS FLOW]
*[Life and Work Event Open Enrollment Process Flow|LIFE AND WORK EVENT OE PROCESS FLOW]
At line 22 changed one line
[Ad Hoc Open Enrollment Process Flow|AD HOC OE PROCESS FLOW|AD HOC OE PROCESS FLOW]
*[Ad Hoc Open Enrollment Process Flow|AD HOC OE PROCESS FLOW|AD HOC OE PROCESS FLOW]
The following diagram gives a high level view of the Open Enrollment process.
[OPEN ENROLLMENT PROCESS FLOW_01.JPG]
----
![Notes|Edit:Internal.OPEN+ENROLLMENT+PROCESS+FLOW]
[{InsertPage page='Internal.OPEN+ENROLLMENT+PROCESS+FLOW' default='Click to create a new notes page'}]