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 5 lines
Maintain Plan/Coverage Definitions Usages data is stored on the [P2K_BE_PLAN_DEFINITIONS].
;[Plan|PLAN_CODE]:Plan is a user-defined code uniquely identifying the plan to the organization. Plan_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Description|DESCRIPTION]:This field provides a user-defined description of the benefit plan. Description is an optional 50-character alphanumeric field you may manually enter.
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 13 changed one line
;[Entity|ENTITY_CODE]:The Entity field identifies the organization to which this plan is restricted. This field may be left blank if there is no restriction. Entity from [P2K_CM_ENTITIES] is an optional 16-character alphanumeric field you may manually enter or use the LOV (F9).
;[Entity|ENTITY_CODE]:The Entity field identifies the organization to which this plan is restricted. This field may be left blank if there is no restriction.
At line 15 changed 6 lines
;[Plan Type|PLAN_TYPE_CODE]:This field indicates the plan type that categorizes this plan. Plan_Type_Code is a mandatory 16-character alphanumeric field you must either manually enter or use the LOV (F9).
;[Plan|PLAN_CODE]:
;[Description|DESCRIPTION]:
;[Plan Established|ESTABLISHED_DATE]:This is the date the plan was first established at the organization. Established_Date is an optional date field you may manually enter.
;[Plan End Date|END_DATE]:This is the date after which dependent coverage or beneficiary. End_Date is a mandatory date field you must manually enter.
;[Calc Seq #|CALCULATION_SEQUENCE]:This field determines the order in which the plan will be processed by the benefit calculation. Calculation_Sequence is an optional 5-digit numeric field that will default from the Plan Type ([IBPT]) form but may be overridden by you.
;[Plan Type|PLAN_TYPE_CODE]:This field indicates the plan type that categorizes this plan.
At line 22 changed 8 lines
;[Policy #|POLICY_NUMBER]:This field supplies the insurance policy number assigned by the insurance carrier. Policy_Number is an optional 30-character alphanumeric field you may manually enter.
;[Calendar|CALENDAR_CODE]:This field provides the user-defined calendar code, which uniquely identifies the calendar by which the plan must be remitted. Calendar_Code is a 16-character alphanumeric mandatory field you must manually enter or use the LOV(F9).
;[Participation|PARTICIPATION_RULE]:This field indicates whether participation in a benefit plan or coverage is mandatory or optional. The participation rule on the plan definition is used as a default entry to the benefit schedule. Only the participation rule from the benefit schedule is enforced. Participation_Rule is an optional fixed lexicon ([X_PARTICIPATION_RULE]) that you may use to look up the value.
;[Access_Code|PLAN_ACCESS_CODE]:Plan Access is a security feature providing the ability to control access to different types of benefits information. Plan_Access_Code is an optional fixed lexicon ([X_SECURITY_ACCESS]) that you may use to look up the value.
;[Not Scheduled|NOT_SCHEDULED]:If the ‘Not Scheduled’ toggle is ON, then this plan may be added to the Benefit Election form ([IBEL]) without being placed on the Benefit Schedule ([IBSC]). If the toggle is OFF, the plan must be on the schedule to allow employee to elect it. Not_Scheduled is an optional toggle field.
;[Track Decline|TRACK_DECLINE]:If the ‘Track Decline’ toggle is ON, a form is created in the enrollment file when an employee declines coverage under a plan. If the toggle is OFF declined benefits are not tracked. Track_Decline is an optional toggle field.
;[Web Document|WEB_DOCUMENT]:This field is contains the file related to the benefit plan
;[Election Document|ELECTION_DOCUMENT]: This is the document that may be made available to employees in [WEBEL].
;[Plan|PLAN_CODE]:Plan is a user-defined code uniquely identifying the plan to the organization.
At line 31 changed one line
__Elections__
;[Description|DESCRIPTION]:This field provides a user-defined description of the benefit plan.
At line 33 changed 3 lines
;[Plan Election Set|PLAN_ELECTION_SET]: This field stores the plan election set the plan is tied to. This field is only to be used for Open Enrollments. The plans within the Plan Election Set must be part of the same plan type. Since Plan Election Sets are used when plans are mutually exclusive of one another, they can only be implemented if the client already restricts the employees to only enroll into one plan. This field is tied to the lexicon [X_PLAN_ELECTION_SET].
;[Open Enroll Allowed|OPEN_ENROLLMENT_ALLOWED]:If the benefit plan is to be included in the Open Enrollment process then the Open Enroll Allowed field must be populated with either ‘Always Open’ or ‘OE Periods Only’. Always Open will ensure that the benefit plan is always open to employees to elect into. OE Periods Only ensures that the benefit plan is only open during the OE Period. If the benefit plan is never to be used by the Open Enrollment process then select ‘Never Open’. This field is tied to the lexicon [X_BE_OE_ALLOWED].
;[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). This field is tied to the lexicon [X_BE_APPROVAL].
;[Plan Established|ESTABLISHED_DATE]:This is the date the plan was first established at the organization.
;[Plan End Date|END_DATE]:This is the date after which dependent coverage or beneficiary.
;[Calc Seq #|CALCULATION_SEQUENCE]:This field determines the order in which the plan will be processed by the benefit calculation.
;[Policy #|POLICY_NUMBER]:This field supplies the insurance policy number assigned by the insurance carrier.
;[Calendar|CALENDAR_CODE]:This field provides the user-defined calendar code, which uniquely identifies the calendar by which the plan must be remitted.
;[Participation|PARTICIPATION_RULE]:This field indicates whether participation in a benefit plan or coverage is mandatory or optional. The participation rule on the plan definition is used as a default entry to the benefit schedule. Only the participation rule from the benefit schedule is enforced.
;[Access_Code|PLAN_ACCESS_CODE]:Plan Access is a security feature providing the ability to control access to different types of benefits information.
;[Not Scheduled|NOT_SCHEDULED]:If the ‘Not Scheduled’ toggle is ON, then this plan may be added to the Benefit Election form ([IBEL]) without being placed on the Benefit Schedule ([IBSC]). If the toggle is OFF, the plan must be on the schedule to allow employee to elect it.
;[Track Decline|TRACK_DECLINE]:If the ‘Track Decline’ toggle is ON, a form is created in the enrollment file when an employee declines coverage under a plan. If the toggle is OFF declined benefits are not tracked.
;[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.
;[Election Document|ELECTION_DOCUMENT]: This field allows a user to specify an html document which is available to employees in [WEBEL].
!Elections
;[Plan Election Set|PLAN_ELECTION_SET]: This field stores the plan election set the plan is tied to. This field is only to be used for Open Enrollments. The plans within the Plan Election Set must be part of the same plan type. Since Plan Election Sets are used when plans are mutually exclusive of one another, they can only be implemented if the client already restricts the employees to only enroll into one plan.
;[Open Enroll Allowed|OPEN_ENROLLMENT_ALLOWED]:If the benefit plan is to be included in the Open Enrollment process then the Open Enroll Allowed field must be populated with either ‘Always Open’ or ‘OE Periods Only’. Always Open will ensure that the benefit plan is always open to employees to elect into. OE Periods Only ensures that the benefit plan is only open during the OE Period. If the benefit plan is never to be used by the Open Enrollment process then select ‘Never Open’.
;[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 48 added one line
At line 50 added one line
At line 41 changed one line
__Remittances__
!Remittances
;[Remittance Report|REMIT_REPORT_CODE]:Remittance Report is a user-defined code uniquely identifying the report within the organization.
At line 43 removed 2 lines
;[Remittance Report|REMIT_REPORT_CODE]:Remittance Report is a user-defined code uniquely identifying the report within the organization. Remit_Report_Code is a 16-character alphanumeric optional field you may manually enter or use the LOV(F9).
At line 46 changed one line
;[Remit As Of Day|REMIT_ASOF_DAY]:This field specifies the day of the remittance period on which remittances are assessed. Remit_Asof_Day is a 5-digit numeric optional field defaulting from the remittance report or you may manually override.
;[Remit As Of Day|REMIT_ASOF_DAY]:This field specifies the day of the remittance period on which remittances are assessed.
At line 48 changed one line
;[Plan Remit Seq #|PLAN_REMIT_SEQUENCE]:Remittance Sequence determines the order in which each plan will be printed when more than one benefit plan is printed on the same remittance report. Plan_Remit_Sequence is a 5 digit numeric optional field you may manually enter.
;[Plan Remit Seq #|PLAN_REMIT_SEQUENCE]:Remittance Sequence determines the order in which each plan will be printed when more than one benefit plan is printed on the same remittance report.
At line 68 added one line
;[Remit Date Rule|REMIT_DATE_RULE]:This field indicates the date at which remittances must be assessed.
At line 57 changed one line
;[Remit Date Rule|REMIT_DATE_RULE]:This field indicates the date at which remittances must be assessed. Remit_Date_Rule is an optional fixed lexicon ([X_REMIT_DATE_RULE]) that you may use to look up the value.
;[Print Zero Rule|PRINT_ZERO_RULE]:This field controls whether employees with zero premium amounts (for any reason) who are enrolled in the benefit plan should get printed on the remittance report.
At line 59 changed one line
;[Print Zero Rule|PRINT_ZERO_RULE]:This field controls whether employees with zero premium amounts (for any reason) who are enrolled in the benefit plan should get printed on the remittance report. Print_Zero_Rule is an optional fixed lexicon ([X_PRINT_ZERO_RULE]) that you may use to look up the value.
;[Remit by State|REMIT_BY_STATE]:If the ‘Remit by State’ toggle is ON, the state or province of the employee’s residence separates remittance history records. If the toggle is OFF there is no separation by state or province.
At line 61 changed one line
;[Remit by State|REMIT_BY_STATE]:If the ‘Remit by State’ toggle is ON, the state or province of the employee’s residence separates remittance history records. If the toggle is OFF there is no separation by state or province. Remit_By_State is an optional toggle field.
;[Remit by Unit or Group|REMIT_BY_UNIT_OR_GROUP]:If the ‘Remit by Unit or Group’ toggle is ON, remittance history records will be separated by group or unit, based on the employee’s [Prime Assignment Information (IEAS)|IEAS] form. If the toggle is OFF there is no separation by unit and group.
At line 63 changed one line
;[Remit by Unit or Group|REMIT_BY_UNIT_OR_GROUP]:If the ‘Remit by Unit or Group’ toggle is ON, remittance history records will be separated by group or unit, based on the employee’s [Prime Assignment Information (IEAS)|IEAS] form. If the toggle is OFF there is no separation by unit and group. Remit_By_Unit_Or_Group is an optional toggle field.
;[Print All Waivers|PRINT_ALL_WAIVERS]:If the ‘Print All Waivers’ toggle is ON, employees receiving a benefit waiver that reduces their premium to zero will still appear on the remittance report. If the toggle is OFF employees on a waiver with a zero premium will not get printed.
At line 65 removed 2 lines
;[Print All Waivers|PRINT_ALL_WAIVERS]:If the ‘Print All Waivers’ toggle is ON, employees receiving a benefit waiver that reduces their premium to zero will still appear on the remittance report. If the toggle is OFF employees on a waiver with a zero premium will not get printed. Print_All_Waivers is an optional toggle field.
At line 69 changed 5 lines
;[Coverage|COVERAGE_CODE]:Coverage is a user-defined code uniquely identifying the coverage to the organization. Coverage_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Seq #|COVERAGE_REMIT_SEQUENCE]:Remit Sequence determines the order in which all the Coverages will be printed when more than one benefit coverage is printed on the same remittance report. Coverage_Remit_Sequence is an optional 5-digit numeric field that will default from the plan or you may manually enter.
;[Policy #|POLICY_NUMBER]:Insurance Policy Number for the coverage. Policy_Number is an optional 30-character alphanumeric field that will default from the plan or you may manually enter.
;[Recipient Type|RECIPIENT_TYPE]:This field determines the recipient eligible for the coverage. This field is used for Open Enrollments. Recipient_Type is a fixed lexicon ([X_PLAN_RECIPIENT_TYPE]). If the coverage is only available to the employee, ‘Not Applicable’ must be selected. The type of recipient defined at the coverage will filter the list of benefit recipients available to the employee for that plan during the election period. The filtration is done by comparing the recipient type lexicon values to the stored values of the [relation lexicon|X_RELATION] in [IECT]. The system will check for a recipient type at the coverage first, if none are found it will then check the plan type to see if one has been defined at that level. If the system cannot locate a recipient type for either the coverage or plan type, all of the employee’s contacts defined in [IECT] will be listed for the employee to elect.
;[Contact|CONTACT_ROLE]:Contact Role identifies the contact eligible under this coverage. Contact_Role is an optional 16-character alphanumeric field you may manually enter.
;[Coverage|COVERAGE_CODE]:Coverage is a user-defined code uniquely identifying the coverage to the organization.
At line 82 added 8 lines
;[Seq #|COVERAGE_REMIT_SEQUENCE]:Remit Sequence determines the order in which all the Coverages will be printed when more than one benefit coverage is printed on the same remittance report.
;[Policy #|POLICY_NUMBER]:Insurance Policy Number for the coverage.
;[Recipient Type|RECIPIENT_TYPE]:This field determines the recipient eligible for the coverage. This field is used for Open Enrollments. Recipient_Type is a fixed lexicon ([X_PLAN_RECIPIENT_TYPE]). If the coverage is only available to the employee, ‘Not Applicable’ must be selected. The type of recipient defined at the coverage will filter the list of benefit recipients available to the employee for that plan during the election period. The filtration is done by comparing the recipient type lexicon values to the stored values of the [relation lexicon|X_RELATION] in [IECT]. The system will check for a recipient type at the coverage first, if none are found it will then check the plan type to see if one has been defined at that level. If the system cannot locate a recipient type for either the coverage or plan type, all of the employee’s contacts defined in [IECT] will be listed for the employee to elect. The page [Benefit Recipient Matrix for Open Enrollment|BENEFIT RECIPIENT MATRIX FOR OPEN ENROLLMENT] shows which relation values fall under each of the recipient types.
;[Contact|CONTACT_ROLE]:Contact Role identifies the contact eligible under this coverage.
At line 91 added 2 lines
\\
At line 94 added one line
At line 96 added one line
At line 98 added one line
At line 100 added one line
At line 102 added one line
At line 104 added 4 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 109 added one line
At line 111 added one line
At line 113 added one line
At line 87 removed one line
At line 89 changed 2 lines
!Coverages Details tab
;[Description|DESCRIPTION]:This field holds a user-provided description of the coverage. Description is an optional 50-character alphanumeric field you may manually enter.
!!Coverages Details tab
;[Description|DESCRIPTION]:This field holds a user-provided description of the coverage.
At line 92 changed one line
;[Remit Basis|REMIT_BASIS]:Remit Basis is the unit of measure in which remittances are stored and sent. Remit_Basis is a mandatory fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[Remit Basis|REMIT_BASIS]:Remit Basis is the unit of measure in which remittances are stored and sent.
At line 94 changed one line
;[Rate Basis|RATE_BASIS]:Rate Basis indicates the unit of measure that coverage rates are stored in for coverage components, plan rates or enrollment tables. All rates entered on the Rates tab must be of the 'Rate Basis' indicated here. Rate_Basis is a mandatory fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[Rate Basis|RATE_BASIS]:Rate Basis indicates the unit of measure that coverage rates are stored in for coverage components, plan rates or enrollment tables. All rates entered on the Rates tab must be of the 'Rate Basis' indicated here.
At line 96 changed one line
;[Frequency|FREQUENCY_CODE]:Frequency defines the condition under which the benefit is processed. The processing frequencies may be set by month, pay period, type of pay and number of times within a pay period. Frequency_Code is a mandatory 16-character alphanumeric field you must either manually enter or use the LOV (F9).
;[Frequency|FREQUENCY_CODE]:Frequency defines the condition under which the benefit is processed. The processing frequencies may be set by month, pay period, type of pay and number of times within a pay period.
At line 98 changed 3 lines
----
!Components tab
Coverage Components identify which benefit components are applicable to a particular benefit coverage. They specify the information on the rules, usercalcs, [elements|PAY ELEMENTS], field values, factors and constants associated with a coverage.
;[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.
At line 102 changed one line
;:%%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.%%
;[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.
At line 130 added 14 lines
;[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.
----
!!Components tab
\\
Coverage Components identify which benefit components are applicable to a particular benefit coverage. They specify the information on the rules, UserCalcs, [elements|PAY ELEMENTS], field values, factors and constants associated with a coverage.
\\ \\
;%%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 107 removed one line
;:Component_Sequence is a 5-character numeric mandatory field that is provided.
At line 111 removed one line
;:BC_Code is a provided mandatory 16-character alphanumeric field you may manually enter or use the LOV (F9).
At line 115 changed one line
;[Rule|BC_RULE_CODE]:This field is used to describe the possible options available for each benefits component. The rules shown are applicable to the highlighted benefits component in the BC Code field of the form. BC_Rule_Code from the [P2K_BE_BC_RULES] table is a mandatory 2-character numeric field either provided, manually enter or selected with the LOV (F9).
;[Rule|BC_RULE_CODE]:This field is used to describe the possible options available for each benefits component. The rules shown are applicable to the highlighted benefits component in the BC Code field of the form.
At line 119 changed 3 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.
;[Allow Value Override|ALLOW_VALUE_OVERRIDE]:If the ‘Allow Value Override’ toggle is ON, the system allows you to see value on [IBEL], and update it (must also have ‘enter on enrollment’ ON, and ‘enter on enrollment’). Allows users to override value on [IBEN]. If the toggle is OFF, a value may not be overridden. Both original values and overridden values are stored. The program will use the original or the override based on this toggle.
At line 123 changed one line
;[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). PC_Code is a 4-digit numeric optional field you may manually enter or use the LOV (F9).
;[Enter Enrollment|ENTER_ENROLLMENT]:If the ‘Enter Enrollment’ toggle is ON, the coverage component value may be overridden on the employee's enrollment form. This allows the user to enter the value when enrolling. Both 'Allow Value Override' and 'Enter Enrollment' must be on, and BC action including ‘Store on Enroll’, in order to see on [IBEL]. If the toggle is OFF, the component may not be overridden.
At line 125 removed 10 lines
;[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. Element_Code is a 16-character alphanumeric optional field you may manually enter or use the LOV (F9).
;[PC Abbrev.|PC_ABBREVIATION]:Abbreviation is a description of the [pay component|PAY COMPONENTS] chosen. PC_Abbreviation is a 30-character alphanumeric field defaulting from the [pay component|PAY COMPONENTS].
;[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. User_Calc_Code is a 16-character alphanumeric optional field you may manually enter or use the LOV (F9).
;[Allow Value Override|ALLOW_VALUE_OVERRIDE]:If the ‘Allow Value Override’ toggle is ON, the system allows you to see value on [IBEL], and update it (must also have ‘enter on enrollment’ ON, and ‘enter on enrollment’). Allows users to override value on [IBEN]. If the toggle is OFF, a value may not be overridden. Both original values and overridden values are stored. The program will use the original or the override based on this toggle. Allow_Value_Override is an optional toggle; the value of which is provided for each benefits component.
;[Enter Enrollment|ENTER_ENROLLMENT]:If the ‘Enter Enrollment’ toggle is ON, the coverage component value may be overridden on the employee's enrollment form. This allows the user to enter the value when enrolling. Both 'Allow Value Override' and 'Enter Enrollment' must be on, and BC action including ‘Store on Enroll’, in order to see on [IBEL]. If the toggle is OFF, the component may not be overridden. Enter_Enrollment is an optional toggle; the value of which is provided for each benefits component.
At line 139 changed one line
;:If the toggle is OFF, the component may not be overridden. Enter_Benefit_Lines is an optional toggle; the value of which is provided for each benefits component.
;:If the toggle is OFF, the component may not be overridden.
At line 174 added one line
At line 176 added 14 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 150 changed 2 lines
!Rates tab
Coverage Rates specify the set of rates applied to a specific step within the coverage detail.
!!Rates tab
At line 193 added 2 lines
Coverage Rates specify the set of rates applied to a specific step within the coverage detail.
\\ \\
At line 154 changed one line
\\
At line 157 removed one line
;:Coverage_Step_Code is a mandatory 16-character alphanumeric field you must manually enter.
At line 159 changed one line
;[Description|DESCRIPTION]:This field describes the rate step. Description is an optional 50-character alphanumeric field you may manually enter.
;[Description|DESCRIPTION]:This field describes the rate step.
At line 161 changed one line
;[Up to Limit|UP_TO_LIMIT]:Up to Limit (up to but not including) specifies the upper limit to which the step applies when the rates vary based on age, salary or other range criteria. Used for component B0500, Rule 05, 06, 08 and 09. Up_To_Limit is an optional 18-digit numeric field you may manually enter.
;[Up to Limit|UP_TO_LIMIT]:Up to Limit (up to but not including) specifies the upper limit to which the step applies when the rates vary based on age, salary or other range criteria. Used for component B0500, Rule 05, 06, 08 and 09.
At line 163 changed one line
;[Next Step|NEXT_STEP_CODE]:Next Step code indicates the next set of rates that will apply when rates are stepped based on a date. Next_Step_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Next Step|NEXT_STEP_CODE]:Next Step code indicates the next set of rates that will apply when rates are stepped based on a date.
At line 165 changed one line
;[Flex Amount|FLEX_AMOUNT]:This field provides the amount of the flex fund credit being contributed by the organization; used for component B0810, Rule 07. Flex_Amount is an optional 18-digit numeric field you may manually enter.
;[Flex Amount|FLEX_AMOUNT]:This field provides the amount of the flex fund credit being contributed by the organization; used for component B0810, Rule 07.
At line 167 changed one line
;[Premium 1 Rate|PREMIUM1_RATE]:This is the regular premium rate used in normal premium calculations; used for component B0600, Rule 02. Premium1_Rate is an optional 18-digit numeric field you may manually enter.
;[Premium 1 Rate|PREMIUM1_RATE]:This is the regular premium rate used in normal premium calculations; used for component B0600, Rule 02.
At line 169 changed one line
;[Premium 2 Rate|PREMIUM2_RATE]:Additional premium rate used when a second premium rate must be applied after a coverage limit is reached (e.g. $0.50 per $1,000 on 1st $50,000 coverage, $1.00 per $1,000 for any coverage in excess of $50,000). Used for component B0610, Rule 02. Premium2_Rate is an optional 18-digit numeric field you may manually enter.
;[Premium 2 Rate|PREMIUM2_RATE]:Additional premium rate used when a second premium rate must be applied after a coverage limit is reached (e.g. $0.50 per $1,000 on 1st $50,000 coverage, $1.00 per $1,000 for any coverage in excess of $50,000). Used for component B0610, Rule 02.
At line 171 changed one line
;[ER Contribution Rate|ER_CONTRIBUTION_RATE]:This is the rate used in the employer's contribution calculation; used for component B0800, Rule 02. ER_Contribution_Rate is an optional 18-digit numeric field you may manually enter.
;[ER Contribution Rate|ER_CONTRIBUTION_RATE]:This is the rate used in the employer's contribution calculation; used for component B0800, Rule 02.
At line 173 changed one line
;[EE Deduction Rate|EE_DEDUCTION_RATE]:This field provides the rate used in the employee's deduction calculation; used for component B1000, Rule 02. EE_Deduction_Rate is an optional 18-digit numeric field you may manually enter.
;[EE Deduction Rate|EE_DEDUCTION_RATE]:This field provides the rate used in the employee's deduction calculation; used for component B1000, Rule 02.
At line 175 changed one line
;[Taxable Benefit Rate|TAXBEN_RATE]:This is the rate used in the taxable benefit calculation; used for component B1200, Rule 02. Taxben_Rate is an optional 18-digit numeric field you may manually enter.
;[Taxable Benefit Rate|TAXBEN_RATE]:This is the rate used in the taxable benefit calculation; used for component B1200, Rule 02.
At line 177 changed one line
;[User 1 Rate|USER1_RATE]:This field provides the first user-defined rate. User1_Rate is an optional 18-digit numeric field you may manually enter.
;[User 1 Rate|USER1_RATE]:This field provides the first user-defined rate.
At line 179 changed one line
;[User 2 Rate|USER2_RATE]:This is the second user-defined rate. User2_Rate is an optional 18-digit numeric field you may manually enter.
;[User 2 Rate|USER2_RATE]:This is the second user-defined rate.
At line 181 changed one line
;[User 3 Rate|USER3_RATE]:This is the third user-defined rate. User3_Rate is an optional 18-digit numeric field you may manually enter.
;[User 3 Rate|USER3_RATE]:This is the third user-defined rate.
At line 184 changed one line
!Waivers tab
!!Waivers tab
\\
At line 228 added 2 lines
\\
;[Employment Status|STATUS_CODE]:The employment status of an employee may be pending approval, active, on a leave of some type, or terminated.
At line 187 changed one line
;[Employment Status|STATUS_CODE]:The employment status of an employee may be pending approval, active, on a leave of some type, or terminated. Status_Code is a mandatory 16-character alphanumeric field you must manually enter or use the LOV (F9).
;[Up to Limit|UP_TO_LIMIT]:This field indicates the highest age for which this reduction rule applies, if applicable.
;[Waiver Method|WAIVER_METHOD]:This field indicates who pays the premium amount when an employee is on a benefit waiver.
At line 189 changed one line
;[Up to Limit|UP_TO_LIMIT]:This field indicates the highest age for which this reduction rule applies, if applicable. Up_To_Limit is a mandatory 18-digit numeric field you must manually enter.
;[Coverage Reduction %|COVG_REDUCTION_PERCENT]:This field indicates by how much the coverage/benefit amount is reduced.
At line 191 changed one line
;[Waiver Method|WAIVER_METHOD]:This field indicates who pays the premium amount when an employee is on a benefit waiver. Waiver_Method is an optional fixed lexicon ([X_WAIVER_METHOD]) that you may use to look up the value.
;[Premium Reduction %|PREM_REDUCTION_PERCENT]:This field indicates by how much the premium is reduced.
At line 193 changed one line
;[Coverage Reduction %|COVG_REDUCTION_PERCENT]:This field indicates by how much the coverage/benefit amount is reduced. Covg_Reduction_Percent is an optional 5-digit numeric field you may manually enter.
;[EE Reduction %|EE_REDUCTION_PERCENT]:This field indicates by how much the employee deduction is reduced.
At line 195 changed 5 lines
;[Premium Reduction %|PREM_REDUCTION_PERCENT]:This field indicates by how much the premium is reduced. Prem_Reduction_Percent is an optional 5-digit numeric field you may manually enter.
;[EE Reduction %|EE_REDUCTION_PERCENT]:This field indicates by how much the employee deduction is reduced. EE_Reduction_Percent is an optional 5-digit numeric field you may manually enter.
;[ER Reduction %|ER_REDUCTION_PERCENT]:This field indicates by how much the employer contribution is reduced. ER_Reduction_Percent is an optional 5-digit numeric field you may manually enter.
;[ER Reduction %|ER_REDUCTION_PERCENT]:This field indicates by how much the employer contribution is reduced. \\
At line 243 added one line
\\
At line 203 changed one line
\\ \\
At line 247 added one line
At line 249 added 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