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

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
18 26-Nov-2021 10:22 6 KB JMyers to previous
17 26-Nov-2021 10:22 8 KB JAiken to previous | to last
16 26-Nov-2021 10:22 8 KB JMyers to previous | to last
15 26-Nov-2021 10:22 8 KB JMyers to previous | to last
14 26-Nov-2021 10:22 8 KB JMyers to previous | to last
13 26-Nov-2021 10:22 8 KB JMyers to previous | to last
12 26-Nov-2021 10:22 8 KB JMyers to previous | to last
11 26-Nov-2021 10:22 8 KB JEscott to previous | to last
10 26-Nov-2021 10:22 8 KB JEscott to previous | to last
9 26-Nov-2021 10:22 8 KB JEscott to previous | to last
8 26-Nov-2021 10:22 8 KB JEscott to previous | to last
7 26-Nov-2021 10:22 8 KB RForbes to previous | to last
6 26-Nov-2021 10:22 8 KB RForbes to previous | to last
5 26-Nov-2021 10:22 8 KB KateN to previous | to last
4 26-Nov-2021 10:22 8 KB KateN to previous | to last
3 26-Nov-2021 10:22 8 KB KateN to previous | to last
2 26-Nov-2021 10:22 7 KB KateN to previous | to last
1 26-Nov-2021 10:22 7 KB KateN to last

Page References

Incoming links Outgoing links
IBBC
IBBC

Version management

Difference between version and

At line 1 added 2 lines
[{TableOfContents }]
At line 5 removed 2 lines
\\
;[Seq #|COMPONENT_SEQUENCE]:The Sequence field 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 that should be collected, it is 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.'' \\ \\Sequences are numbered in the order needed for processing, this means that some of the sequences __do not__ correspond to the BC code. It is recommended the sequence numbers not be changed without the supervision of a consultant.\\ \\Component_Sequence is a mandatory 5-digit numeric field that is provided.
At line 8 changed one line
;[Benefit Component|BC_CODE]:The BC code is a provided code defining 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 ‘List of Benefit Components’ section.__\\ \\BC codes are numbered to be able to group certain types of components together. i.e. B1000’s are all related calculating an employee’s deduction amount.\\ \\BC_Code is a mandatory 16-character alphanumeric field that is provided.
;[Seq #|COMPONENT_SEQUENCE]:The Sequence field specifies the order in which the Benefits or Payroll Calculation program will calculate the benefits components.
At line 10 changed one line
;[Description|DESCRIPTION]:This is the description of the benefits component highlighted. Description is an optional 50-character alphanumeric field that is either provided or that you may manually enter.
;:For example, in order to calculate the employee deduction that should be collected, it is necessary to know the premium amount.
At line 12 changed one line
;[Prompt|FIELD_PROMPT]:Prompt is displayed to the user when in the <BC Value> field.\\ \\''For example, if the benefits component were “B0020 – Enrollment Base Date”, an appropriate prompt would be “Enter Base Date”.''\\ \\Field_Prompt is a 30-character alphanumeric optional field that is either provided or that you may manually enter.
;: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.
At line 14 changed one line
;[Field Type|FIELD_TYPE]:This is the type of field for the information returned by the benefits component; valid entries (provided) are Char, Number, Date and Boolean. Field_Type is a mandatory fixed lexicon ([X_FIELD_TYPE]) you may use to look up the value.
;:Sequences are numbered in the order needed for processing, this means that some of the sequences do not correspond to the BC code. It is recommended the sequence numbers not be changed without the supervision of a consultant.
At line 16 changed one line
;[BC Action|BC_ACTION]:The BC Action field identifies the action that will be performed by this benefits component. BC_Action is a mandatory fixed lexicon ([X_BC_ACTION]) you may use to look up the value.
;[Benefit Component|BC_CODE]:The BC code is a provided code defining the benefits component. All BC codes begin with the letter “B” followed by a 4-digit number.
At line 18 removed one line
;[Component Text|COMPONENT_TEXT]:The Component Text field provides detailed documentation of the coverage component: its use, purpose, and any dependencies or relationships to any other components. An optional field allows space for more in-depth descriptions of the benefits component. Values are provided and may be edited to suit the installation. Component_Text is an optional 2000 character alphanumeric field that is either provided or that you may manually enter.
At line 20 changed one line
;[User Calc Allowed|USER_CALC_ALLOWED]:If the ‘UserCalc’ toggle is ON, the system allows users to 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. User_Calc_Allowed is an optional toggle, the value of which is provided for each benefits component.
;:%%information Definitions of each of the benefits components may be found in the [Benefit Components|BENEFIT COMPONENTS#Benefit Component Codes] section.%%
At line 22 changed one line
;[Pay Components Allowed|PAY_COMPONENT_ALLOWED]:Each benefit component used by a benefit plan is stored with the value returned from the benefits calculation.\\ \\If the ‘Pay Component’ toggle is ON, allows users to also select a [pay component|PAY COMPONENTS] where the result of this calculation may be stored. In this manner, amounts calculated for benefit lines or enrollment may be recorded in [Payroll|MODULE-PR] and therefore will show on a pay register, the employees pay stub and/or the financial ledgers (as required). \\ \\Without a specified [pay component|PAY COMPONENTS], the amount calculated would not be recorded for payroll or costing purposes. Generally used for premiums, employee deductions, employer contributions, taxes and taxable benefits.\\ \\Pay_Component_Allowed is an optional toggle, the value of which is provided for each benefits component.
;:BC codes are numbered to be able to group certain types of components together. i.e. B1000’s are all related calculating an employee’s deduction amount.
At line 24 changed one line
;[Element Allowed|ELEMENT_ALLOWED]:If the ‘Element’ toggle is ON, the system allows users to enter an element to calculate the benefits component. This is appropriate for those benefits components that might be calculated using a group of pay components (such as Time Worked). The rules for the benefits component must include a “Use an Element” rule for this field to be used. Element_Allowed is an optional toggle, the value of which is provided for each benefits component.
;[Description|DESCRIPTION]:This is the description of the benefits component highlighted.
At line 26 changed one line
;[Value Allowed|VALUE_ALLOWED]:If the ‘Value’ toggle is ON, the system allows users to enter a value for the benefits component. This could occur when setting up a new plan, when adding an employee manually to a plan, or when adding benefit lines for an employee.\\ \\If a value is allowed, the user will be able to access the <BC Value> field and enter a value in it. This field would not be used for policies where the value is calculated or derived.\\ \\Value_Allowed is an optional toggle, the value of which is provided for each benefits component.
;[Prompt|FIELD_PROMPT]:Prompt is displayed to the user when in the <BC Value> field.\\ \\For example, if the benefits component were “B0020 – Enrollment Base Date”, an appropriate prompt would be “Enter Base Date”.
At line 28 changed one line
;[Enter Benefit Lines|ENTER_BENEFIT_LINES]:If the ‘Enter Benefit Lines’ toggle is ON, this indicates that data from the Benefit Lines ([IBBL]) form may override the coverage component value. 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.
;[Field Type|FIELD_TYPE]:This is the type of field for the information returned by the benefits component; valid entries (provided) are Char, Number, Date and Boolean.
At line 30 changed one line
;[Enter Enrollment|ENTER_ENROLLMENT]:If the ‘Enter Enrollment’ toggle is ON, this indicates that the coverage component value may be overridden on the employee's Benefit Enrollment ([IBEN]) form. 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.
;[BC Action|BC_ACTION]:The BC Action field identifies the action that will be performed by this benefits component.
At line 32 changed one line
;[Enter Remit History|ENTER_REMIT_HISTORY]:If the ‘Enter Remit History’ toggle is ON, this indicates that the coverage component value may be overridden with data from the Remit History ([IBRH]) form. If the toggle is OFF, the component may not be overridden. Enter_Remit_History is an optional toggle, the value of which is provided for each benefits component.
;[Component Text|COMPONENT_TEXT]:The Component Text field provides detailed documentation of the coverage component: its use, purpose, and any dependencies or relationships to any other components. An optional field allows space for more in-depth descriptions of the benefits component. Values are provided and may be edited to suit the installation.
At line 34 changed one line
;[Update Remit History|UPDATE_REMIT_HISTORY]:If the ‘Update Remit History’ toggle is ON, this indicates that the Update Remit History process should pick up the actual amount calculated by [UPCALC]. If the toggle is OFF, the Update Remit process should pick up the amounts defined in the coverage setup, whether these amounts were actually realized in the pay process.\\ \\__Please note that if this toggle is turned on for even ONE benefit component the application will process all components as if they had this toggled on as well. A coverage cannot be set up with some components to report actual (Payroll) amounts and others plan (benefit) amounts.__\\ \\Update_Remit_History is an optional toggle, the value of which is provided for each benefits component.
;[User Calc Allowed|USER_CALC_ALLOWED]:If the ‘UserCalc’ toggle is ON, the system allows users to 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.
At line 36 changed one line
;[BC Rule Code|BC_RULE_CODE]:A 2-digit code is provided 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 [P2K_BE_BC_RULES] is a mandatory 2-character numeric field that is provided.
;[Pay Components Allowed|PAY_COMPONENT_ALLOWED]:Each benefit component used by a benefit plan is stored with the value returned from the benefits calculation.\\ \\If the ‘Pay Component’ toggle is ON, allows users to also select a [pay component|PAY COMPONENTS] where the result of this calculation may be stored. In this manner, amounts calculated for benefit lines or enrollment may be recorded in [Payroll|MODULE-PR] and therefore will show on a pay register, the employees pay stub and/or the financial ledgers (as required). \\ \\Without a specified [pay component|PAY COMPONENTS], the amount calculated would not be recorded for payroll or costing purposes. Generally used for premiums, employee deductions, employer contributions, taxes and taxable benefits.
At line 38 changed one line
;[Description|DESCRIPTION]:High Line provides a description of the BC Rule Code. Description from [P2K_BE_BC_RULES] is an optional 50-character alphanumeric field that is provided.
;[Element Allowed|ELEMENT_ALLOWED]:If the ‘Element’ toggle is ON, the system allows users to enter an element to calculate the benefits component. This is appropriate for those benefits components that might be calculated using a group of pay components (such as Time Worked). The rules for the benefits component must include a “Use an Element” rule for this field to be used.
At line 40 changed one line
;[Next BC|BBC_ID_NEXT]:This field is used to show inter dependencies between benefits components. The BC code found provides a “chain” to the next logical BC code that will be used for this benefits plan. This field is useful to help the user keep track of which components may be necessary to edit for each plan.\\ \\ ''Examples:\\If a plan steps the coverage based on the employee’s age, then Benefits Component B0500 (Coverage Step Method) would use Rule 05 (Use Employee’s Age). The next BC code for Rule 05 of B0500 would be B0510 (Step by Age).''\\ \\BBC_Id_Next from [P2K_BE_BC_RULES] is a mandatory 10-character numeric field that is provided and may be edited.
;[Value Allowed|VALUE_ALLOWED]:If the ‘Value’ toggle is ON, the system allows users to enter a value for the benefits component. This could occur when setting up a new plan, when adding an employee manually to a plan, or when adding benefit lines for an employee.\\ \\If a value is allowed, the user will be able to access the <BC Value> field and enter a value in it. This field would not be used for policies where the value is calculated or derived.
At line 42 changed 2 lines
;[BC Rule Text|BC_RULE_TEXT]:This field holds detailed documentation of any special set up requirements or prerequisites for using the rule. This is an optional field to allow space for more in-depth descriptions of the benefits component rules. Values are provided and may be edited to suit the installation. BC_Rules_Text is a 2000-character alphanumeric optional field that is either provided or you may manually enter.
\\
;[Enter Benefit Lines|ENTER_BENEFIT_LINES]:If the ‘Enter Benefit Lines’ toggle is ON, this indicates that data from the Benefit Lines ([IBBL]) form may override the coverage component value. If the toggle is OFF, the component may not be overridden.
At line 43 added 21 lines
;[Enter Enrollment|ENTER_ENROLLMENT]:If the ‘Enter Enrollment’ toggle is ON, this indicates that the coverage component value may be overridden on the employee's Benefit Enrollment ([IBEN]) form. If the toggle is OFF, the component may not be overridden.
;[Enter Remit History|ENTER_REMIT_HISTORY]:If the ‘Enter Remit History’ toggle is ON, this indicates that the coverage component value may be overridden with data from the Remit History ([IBRH]) form. If the toggle is OFF, the component may not be overridden.
;[Update Remit History|UPDATE_REMIT_HISTORY]:If the ‘Update Remit History’ toggle is ON, this indicates that the Update Remit History process should pick up the actual amount calculated by [UPCALC]. If the toggle is OFF, the Update Remit process should pick up the amounts defined in the coverage setup, whether these amounts were actually realized in the pay process.
;:%%information Please note that if this toggle is turned on for even ONE benefit component the application will process all components as if they had this toggled on as well. A coverage cannot be set up with some components to report actual (Payroll) amounts and others plan (benefit) amounts.%%
;[BC Rule Code|BC_RULE_CODE]:A 2-digit code is provided 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.
;[Description|DESCRIPTION]:A description of the BC Rule Code.
;[Next BC|BBC_ID_NEXT]:This field is used to show inter dependencies between benefits components. The BC code found provides a “chain” to the next logical BC code that will be used for this benefits plan. This field is useful to help the user keep track of which components may be necessary to edit for each plan.
;:Examples:\\If a plan steps the coverage based on the employee’s age, then Benefits Component B0500 (Coverage Step Method) would use Rule 05 (Use Employee’s Age). The next BC code for Rule 05 of B0500 would be B0510 (Step by Age).
;[BC Rule Text|BC_RULE_TEXT]:This field holds detailed documentation of any special set up requirements or prerequisites for using the rule. This is an optional field to allow space for more in-depth descriptions of the benefits component rules. Values are provided and may be edited to suit the installation.
----
![Notes|Edit:Internal.IBBC]
[{InsertPage page='Internal.IBBC' default='Click to create a new notes page'}]
This page (revision-18) was last changed on 26-Nov-2021 10:22 by JMyersTop