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

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
37 26-Nov-2021 10:22 20 KB rforbes to previous BSS_EVIDENCE_REQ(System_Preference) ==> BSS EVIDENCE REQ(System_Preference)
36 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS D REASON REQ ==> BSS D REASON REQ(System_Preference)
35 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS_EVIDENCE_REQ ==> BSS_EVIDENCE_REQ(System_Preference)
34 26-Nov-2021 10:22 20 KB jmyers to previous | to last
33 26-Nov-2021 10:22 20 KB jmyers to previous | to last
32 26-Nov-2021 10:22 20 KB jmyers to previous | to last
31 26-Nov-2021 10:22 29 KB jmyers to previous | to last
30 26-Nov-2021 10:22 32 KB jmyers to previous | to last
29 26-Nov-2021 10:22 35 KB jmyers to previous | to last
28 26-Nov-2021 10:22 37 KB jmyers to previous | to last
27 26-Nov-2021 10:22 37 KB jmyers to previous | to last
26 26-Nov-2021 10:22 38 KB jmyers to previous | to last
25 26-Nov-2021 10:22 39 KB jmyers to previous | to last
24 26-Nov-2021 10:22 43 KB jmyers to previous | to last
23 26-Nov-2021 10:22 43 KB jmyers to previous | to last
22 26-Nov-2021 10:22 43 KB jmyers to previous | to last
21 26-Nov-2021 10:22 43 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
OPEN ENROLLMENT SET UP
OPEN ENROLLMENT SET UP

Version management

Difference between version and

At line 10 changed 4 lines
;[Sequence|CALCULATION_SEQUENCE]:The Calculation Sequence field determines the order in which this plan type will be processed by payroll. This sequence is also used by the BSS module to determine the order the plan types are displayed to the employee in the election form ([WEBOEE]). If a sequence is not defined, the plan types will display in alphabetical order. Calculation_Sequence is a 5-digit numeric field provided but may be user altered.
;[Sequence|CALCULATION_SEQUENCE]:The Calculation Sequence field determines the order in which this plan type will be processed by payroll. This sequence is also used by the BSS module to determine the order the plan types are displayed to the employee in the election form ([WEBOEE]). If a sequence is not defined, the plan types will display in alphabetical order. This sequence is automatically provided, but may be altered.
At line 19 removed 12 lines
;Recipient Type:This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level.
;Plan Type URL:A URL can be defined to provide the employees with a link to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website. This will be displayed on the SS election form beneath the Election Intro ext.
;Description:Ensure a description has been defined and is reflective of the plans within the plan type as this will be visible in WEBOEE. Basic HTML tags can be used to tailor the look of the text.
;Election Intro Text:This field is used to include introductory text to the plans. This can be used to provide additional instructions to employees. Basic HTML tags can be used to tailor the look of the text.
At line 36 removed one line
At line 48 removed one line
At line 121 added one line
At line 140 removed 14 lines
Step 2: IMLN- Maintain Lexicons
A common requirement of benefit elections is that an employee is eligible to a set of plans that are offered from different carriers and are mutually exclusive of one another (the employee is only allowed to elect one plan out the set). We are now able to handle this requirement by grouping these plans into a “Plan Election Set”. A plan set code is used to group these plans together. The plan set code is user defined in a lexicon called X_PLAN_ELECTION_SET in IMLN. The plan set code should be reflective of the type of plans included in the set. The plan set code is then added to IBPN to each of the plans to be included in the set.
Before employees can submit their elections, they are prompted for a decline reason for the elections they declined. This decline reason is based on the lexicon X_BE_DECLINE_REASON. This is a user defined lexicon which clients must populate with suitable decline reasons.
Step 3: IMST – Define Client Site Information
By default decline reasons are required; however, if it is a client’s policy not to require reasons for declines, the site preference BSS D REASON REQ must be defined in IMST with a value of N.
The site preference BSS_EVIDENCE_REQ may be defined with a value of Y to force an employee to provide Evidence/Documentation during the Open Enrollment before they can submit their elections. If this is defined with a Y a validation message will be displayed to the employee. If a value of N is provided, the employee will still be prompted to submit evidence however they will still able to submit their elections if no evidence is uploaded.
Step 4: IPPGU / IPPGC – Define US/CDN Pay Categories
In order to determine which pay frequency detail record to use to calculate the EE and ER period/monthly/annual calculations, a new pay category is required with the type ”Open Enrollment”. This category will not be used by any payroll calculations.
Step 5: IPPF – Define Processing Frequencies
The new pay category must be added to all of the pay frequencies that are used by the benefit plans associated to the Events for Open Enrollment. The Times Per Year field for this category must be populated with the number of times per year that the benefit plan is to be processed by payroll. This number will be used in conjunction with the rate basis for the category in the EE and ER calculations.
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop