This page (revision-46) was last changed on 07-Jul-2022 14:44 by Karen Parrott

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

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
46 07-Jul-2022 14:44 25 KB Karen Parrott to previous
45 26-Nov-2021 10:22 24 KB kparrott to previous | to last
44 26-Nov-2021 10:22 24 KB kparrott to previous | to last
43 26-Nov-2021 10:22 24 KB kparrott to previous | to last
42 26-Nov-2021 10:22 24 KB kparrott to previous | to last
41 26-Nov-2021 10:22 23 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
IBPN
IBPN

Version management

Difference between version and

At line 6 changed one line
Maintain Plan/Coverage Definitions Usages data is stored on the [P2K_BE_PLAN_DEFINITIONS].
Maintain Plan/Coverage Definitions Usages data is stored on the [P2K_BE_PLAN_DEFINITIONS], [P2K_BE_COVERAGE_DETAILS], [P2K_BE_COVERAGE_COMPONENTS], [P2K_BE_COVERAGE_RATES], [P2K_BE_REDUCTION_RULES] and [P2K_BE_EVENT_TYPE_USAGES].
\\
At line 35 changed one line
;[Web Document|WEB_DOCUMENT]:This field is contains the file related to the benefit plan
;[Web Document|WEB_DOCUMENT]:This field allows a user to specify an html document explaining the benefit policy. This page will be displayed in the [WEBEN] form.
At line 37 changed one line
;[Election Document|ELECTION_DOCUMENT]: This is the document that may be made available to employees in [WEBEL].
;[Election Document|ELECTION_DOCUMENT]: This field allows a user to specify an html document which is available to employees in [WEBEL].
At line 44 changed one line
;[Approval Required|APPROVAL_REQUIRED]:Approval logic can be enabled at the plan level. Clients can choose No Approval Required, Approval Required (Approval is required for Open Enrollments with new elections, existing elections with changes and declined elections.), or Apr Req for Chgs Only (Approval is only required for changes made to elections).
;[Approval Required|APPROVAL_REQUIRED]:Approval logic can be enabled at the plan level for [IBEL] elections. Clients can choose No Approval Required (used by [IBEL] elections only), Approval Required or Apr Req for Chgs Only (Approval is only required for changes made to elections). Approval logic is required for Open Enrollments. All employee Open Enrollments must be first approved before they can be processed into enrollments in [IBEN]. The approval is made at the employee Open Enrollment level, not at a benefit election level meaning that the Administrator will not be approving each election change but the employee’s overall participation in the Open Enrollment.
At line 54 removed one line
At line 77 changed one line
\\
At line 91 added one line
\\
At line 105 added 3 lines
;[Max. Disabled Age|MAXIMUM_DISABLED_AGE]:If the coverage is open to dependents and there is an age restriction in place for disabled members, this field is used to store the maximum age allowed for disabled members. If there is no age restriction the user may enter 999 as the age. The election process will verify the recipient’s age based on their birth date defined in [IECT]. The disabled recipient must have the Disabled Indicator toggled ON in [IECT].
At line 111 changed one line
\\
At line 126 added 11 lines
;[OE Questions|RAS_ID]: This field allows the Benefit Administrator to select an Assessment from [IBAS]. Assessments may now be linked to a coverage allowing questions to be asked and responded to during on Open Enrollment period. If an employee elects a coverage with an assessment, an assessment event will be scheduled automatically. If there are mandatory answers within the assessment the employee will not be able to submit until the mandatory questions have been answered.
;[ACA Min. Value Self|ACA_MIN_VALUE_SELF]:A toggle to identify if the plan meets Minimum Essential Coverage, as defined by the IRS Rules. You would only toggle on a self-only coverage if it meets that criteria.
;[ACA Coverage|ACA_LINE_14]:This is used for ACA reporting on the 1095C form. The options listed are for the type of coverage selected. The value will be shown as a code in Line 14 on the 1095C form and in [VBACAE].
;[ACA Monthly EE Prem|]:This the cost to the employee for this coverage. It may be the employee deduction rate from the Rates tab, or another value. Note that this value represents a __monthly__ rate.
;[User Calcs|]:This option allows for a UserCalc to compute the ACA Monthly Employee Premium, rather than take it from the field above ACA Monthly EE Prem.
At line 139 added one line
\\
At line 125 changed 3 lines
;:%%information If there is a component that must be manually entered at the time the employee elects the coverage then the component should have a BC Action of ‘Store on Enroll’ or ‘Store on Line & Enroll’ and have the ‘Allow Value Override’ toggle ON. This ensures that the component will be provided for input in the Process Benefit Elections ([IBEL]) form. All other components may have the ‘Allow Value Override’ OFF, but still have a BC action of ‘Store on Enroll’ or ‘Store on Line & Enroll’.\\ \\A [pay component|PAY COMPONENTS] may be indicated in the <PC Code> field if the result is required for Payroll processing or reporting. The BC action must be ‘Store on BE Line’ or ‘Store on Line & Enroll’.\\ \\ If any of the ‘Convert to Pay Period Amount’ components are to be used ensure that the ‘Week per Year’ and ‘Months per Year’ fields are completed on the Group ([IDGR]) form in order for the benefit calculation to process the conversion appropriately.%%
\\ \\
;%%information If there is a component that must be manually entered at the time the employee elects the coverage then the component should have a BC Action of ‘Store on Enroll’ or ‘Store on Line & Enroll’ and have the ‘Allow Value Override’ toggle ON. This ensures that the component will be provided for input in the Process Benefit Elections ([IBEL]) form. All other components may have the ‘Allow Value Override’ OFF, but still have a BC action of ‘Store on Enroll’ or ‘Store on Line & Enroll’.\\ \\A [pay component|PAY COMPONENTS] may be indicated in the <PC Code> field if the result is required for Payroll processing or reporting. The BC action must be ‘Store on BE Line’ or ‘Store on Line & Enroll’.\\ \\ If any of the ‘Convert to Pay Period Amount’ components are to be used ensure that the ‘Week per Year’ and ‘Months per Year’ fields are completed on the Group ([IDGR]) form in order for the benefit calculation to process the conversion appropriately.%%
\\
At line 131 removed one line
;:Component_Sequence is a 5-character numeric mandatory field that is provided.
At line 135 removed one line
;:BC_Code is a provided mandatory 16-character alphanumeric field you may manually enter or use the LOV (F9).
At line 143 removed 12 lines
;[BC Action|BC_ACTION]:This is the action will be performed by this benefits component.
;:%%information You may move a component action forward from ‘Calculate’ to ‘Log to BE line’ or ‘Store on Enroll’ but may not move backwards.%%
;:BC_Action is a mandatory fixed lexicon ([X_BC_ACTION]) you may use to look up the value.
;[PC Code|PC_CODE]:Users may select a [pay component|PAY COMPONENTS] where the result of the component may be stored. In this manner, amounts calculated for benefit lines or enrollments may be recorded in Payroll, available for the Pay Register, employees’ pay stub and/or financial ledgers (as required).
;[Element|ELEMENT_CODE]:Users may enter an element to calculate the benefits component. The rules for the benefits component must include a “Use an Element” rule for this field to be used. .
;[PC Abbrev.|PC_ABBREVIATION]:Abbreviation is a description of the [pay component|PAY COMPONENTS] chosen.
;[User Calc|USER_CALC_CODE]:You may specify a usercalc to calculate the benefits component amount, date, etc. This field is appropriate for those benefits components for which the Rule 00 – “Use UserCalc” is defined. UserCalcs may also be used to verify or change the component amount calculated.
At line 176 added 13 lines
;[Value|FIELD_VALUE]:This field allows you to enter a value for the benefit component.
;[BC Action|BC_ACTION]:This is the action to be performed by the benefits component.
;:%%information You may move a component action forward from ‘Calculate’ to ‘Log to BE line’ or ‘Store on Enroll’ but may not move backwards.%%
;[PC Code|PC_CODE]:Users may select a [pay component|PAY COMPONENTS] where the result of the component may be stored. In this manner, amounts calculated for benefit lines or enrollments may be recorded in Payroll, available for the Pay Register, employees’ pay stub and/or financial ledgers (as required).
;[Element|ELEMENT_CODE]:Users may enter an element to calculate the benefits component. The rules for the benefits component must include a “Use an Element” rule for this field to be used. .
;[PC Abbrev.|PC_ABBREVIATION]:Abbreviation is a description of the [pay component|PAY COMPONENTS] chosen.
;[User Calc|USER_CALC_CODE]:You may specify a usercalc to calculate the benefits component amount, date, etc. This field is appropriate for those benefits components for which the Rule 00 – “Use UserCalc” is defined. UserCalcs may also be used to verify or change the component amount calculated.
At line 177 removed one line
Coverage Rates specify the set of rates applied to a specific step within the coverage detail.
At line 193 added 2 lines
Coverage Rates specify the set of rates applied to a specific step within the coverage detail.
\\ \\
At line 180 changed one line
\\
At line 207 changed one line
\\
At line 226 added one line
\\
At line 211 changed one line
\\
At line 243 added one line
\\
At line 227 changed one line
\\ \\
At line 251 added 14 lines
----
!!Benefit Dependencies tab
\\
%%information The information displayed in this tab is a display only and is used by Open Enrollment (OE). The data will be populated on this tab for the Secondary Plan from the setup done on the Benefit Plan Schedule form [IBSC]. The Coverages from the Secondary plan will be shown with the associated coverage required from the Primary Plan. %%
\\ \\
;[Scheduled Coverage|PRIMARY_COVERAGE]:This is the coverage from the Primary Plan that has a dependency to another plan/coverage (the Secondary Plan/Coverage)
;[Dependent Coverage|ALLOWED_SECONDARY_COVERAGE]:For the selected plan (Secondary Plan), this is the coverage that is associated to the Primary plan.
;[Default Coverage|DEFAULT_COVERAGE]: This field determines what coverage is used for the Secondary Plan when the 'Allowed Secondary Coverage' field is populated. \\- If the toggle is ON, then the system will default the coverage (i.e. if the user does nothing, they will get this coverage)\\- If “Default” is OFF, then the user must actively choose this coverage – i.e. must make a positive choice even though this is the only option.
----
![Notes|Edit:Internal.IBPN]
[{InsertPage page='Internal.IBPN' default='Click to create a new notes page'}]
This page (revision-46) was last changed on 07-Jul-2022 14:44 by Karen ParrottTop