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 11 changed 2 lines
!!Define Plan/Coverage Definitions (IBPN) - Plan Details Tab
;[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).
!!Plan Details tab
;[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).
At line 15 added one line
At line 17 added one line
At line 19 added one line
At line 21 added one line
At line 23 added one line
At line 19 changed one line
;[Last Remittance|LAST_REMIT_DATE]:This field holds the date this plan was last remitted to the insurance carrier (or reconciled for internal plans). Each time the remittance process is run, this date is updated by the system to reflect the latest date processed. When a user runs remittances for a specific time period, the system checks that there are no missing remittance periods since the last run.\\ \\ __High Line recommends this field be initialized to the end of the remittance period prior to the commencement of parallel testing for testing purposes, and to the remittance period prior to the live date for production purposes.__\\ \\Last_Remit_Date is an optional date field will be updated by the system, however you may alter this field.
;[Last Remittance|LAST_REMIT_DATE]:This field holds the date this plan was last remitted to the insurance carrier (or reconciled for internal plans). Each time the remittance process is run, this date is updated by the system to reflect the latest date processed. When a user runs remittances for a specific time period, the system checks that there are no missing remittance periods since the last run.
;:%%warning It is recommended that this field be initialized to the end of the remittance period prior to the commencement of parallel testing for testing purposes, and to the remittance period prior to the live date for production purposes.%%
;:Last_Remit_Date is an optional date field will be updated by the system, however you may alter this field.
At line 33 added one line
At line 35 added one line
At line 37 added one line
At line 24 changed one line
;[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.
;[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.
At line 43 added one line
At line 45 added one line
At line 28 changed 2 lines
;[Access_Code|PLAN_ACCESS_CODE]:Plan Access is a security feature providing the ability to control access to different types of benefitsinformation.\\ \\__This feature is not currently available. Planned for a future release.__\\ \\ Plan_Access_Code is an optional fixed lexicon ([X_SECURITY_ACCESS]) that you may use to look up the value.
;[Approval Required|APPROVAL_REQUIRED]:If the ‘Approval Required’ toggle is ON, employer authorization is required before an employee can enroll in the specified plan. If the toggle is OFF authorization is not required.\\ \\Approvals are set up through the IDAR form.\\ \\Approval_Required is an optional toggle field.
;[Access_Code|PLAN_ACCESS_CODE]:Plan Access is a security feature providing the ability to control access to different types of benefits information.
;:%%information This feature is not currently available. Planned for a future release.
;:Plan_Access_Code is an optional fixed lexicon ([X_SECURITY_ACCESS]) that you may use to look up the value.
;[Approval Required|APPROVAL_REQUIRED]:If the ‘Approval Required’ toggle is ON, employer authorization is required before an employee can enroll in the specified plan. If the toggle is OFF authorization is not required.
;:Approvals are set up through the IDAR form. Approval_Required is an optional toggle field.
At line 59 added one line
At line 32 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 form ([IEAS]). If the toggle is OFF there is no separation by unit and group. Remit_By_Unit_Or_Group 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. Remit_By_Unit_Or_Group is an optional toggle field.
At line 34 changed one line
\\
At line 36 changed one line
!!Define Plan/Coverage Definitions (IBPN) - Coverages Tab
!!Coverages Tab
At line 69 added one line
At line 71 added one line
At line 73 added one line
At line 75 added one line
At line 77 added one line
At line 79 added one line
At line 81 added one line
At line 83 added one line
At line 85 added one line
At line 87 added one line
At line 89 added one line
At line 91 added one line
At line 93 added one line
At line 95 added one line
At line 55 changed one line
!!Define Plan/Coverage Definitions (IBPN) - Coverages Tab - Details
!!Coverages Tab - Details
At line 102 added one line
At line 104 added one line
At line 106 added one line
At line 60 changed one line
\\
At line 62 changed one line
!!Define Plan/Coverage Definitions (IBPN) - Coverages Tab - Components
!!Coverages Tab - Components
At line 64 changed 21 lines
\\
\\
__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.__
\\
\\
;[Seq #|COMPONENT_SEQUENCE]:Sequence specifies the order in which the Benefits or Payroll Calculation Program will calculate the benefits components.\\ \\ ''For example, in order to calculate the employee deduction to be collected in a pay, it may be necessary to know the premium amount. In order to know the premium, it is necessary to know the coverage amount. Therefore, the sequence of which of these items (Benefits Components) should be found, derived or calculated first is essential for proper benefit enrollment maintenance.''\\ \\ __It is recommended the sequence numbers not be changed without the supervision of a High Line consultant.__\\ \\Component_Sequence is a 5-character numeric mandatory field provided by High Line.
;[BC|BC_CODE]:BC Code is a High Line provided code to define the benefits component. All BC codes begin with the letter “B” followed by a 4-digit number.\\ \\__Definitions of each of the benefits components may be found in the Benefit Components section of this document.__\\ \\BC_Code is a mandatory 16-character alphanumeric field you may manually enter or use the LOV (F9).
;:%%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.%%
;[Seq #|COMPONENT_SEQUENCE]:Sequence specifies the order in which the Benefits or Payroll Calculation Program will calculate the benefits components.
;:For example, in order to calculate the employee deduction to be collected in a pay, it may be necessary to know the premium amount. In order to know the premium, it is necessary to know the coverage amount. Therefore, the sequence of which of these items (Benefits Components) should be found, derived or calculated first is essential for proper benefit enrollment maintenance.
;:%%information It is recommended the sequence numbers not be changed without the supervision of a consultant.%%
;:Component_Sequence is a 5-character numeric mandatory field that is provided.
;[BC|BC_CODE]:BC Code is used to define the benefits component. All BC codes begin with the letter “B” followed by a 4-digit number.
;:%%information Definitions of each of the benefits components may be found in the Benefit Components section of this document.%%
;:BC_Code is a provided mandatory 16-character alphanumeric field you may manually enter or use the LOV (F9).
At line 125 added one line
At line 127 added one line
At line 129 added one line
At line 131 added one line
At line 133 added one line
At line 135 added one line
At line 137 added one line
At line 139 added one line
At line 141 added one line
At line 143 added one line
At line 145 added one line
At line 147 added one line
At line 156 added one line
At line 158 added one line
At line 160 added one line
At line 162 added one line
At line 164 added one line
At line 166 added one line
At line 168 added one line
At line 170 added one line
At line 172 added one line
At line 174 added one line
At line 176 added one line
At line 178 added one line
At line 186 added one line
At line 188 added one line
At line 190 added one line
At line 192 added one line
At line 194 added one line
At line 196 added one line
This page (revision-46) was last changed on 07-Jul-2022 14:44 by Karen ParrottTop