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 removed 2 lines
[{TableOfContents }]
At line 14 added 2 lines
;:Component_Sequence is a mandatory 5-digit numeric field that is provided.
At line 19 changed one line
;:%%information Definitions of each of the benefits components may be found in the [Benefit Components|BENEFIT COMPONENTS#Benefit Component Codes] section.%%
%%information Definitions of each of the benefits components may be found in the [Benefit Components|BENEFIT COMPONENTS#Benefit Component Codes] section.%%
At line 21 changed one line
;: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 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.
At line 23 changed one line
;[Description|DESCRIPTION]:This is the description of the benefits component highlighted.
;[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.
At line 25 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”.
;[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.
At line 27 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|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.
At line 29 changed one line
;[BC Action|BC_ACTION]:The BC Action field identifies the action that will be performed by this benefits component.
;[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.
At line 31 changed 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|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 33 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|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.
At line 35 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 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.
At line 37 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|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.
At line 39 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|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.
At line 41 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|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.
At line 43 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|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.
At line 45 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|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.
At line 47 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.
;[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.
At line 49 changed one line
;:%%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. BC_Rule_Code from [P2K_BE_BC_RULES] is a mandatory 2-character numeric field that is provided.
At line 51 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.
;[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.
At line 53 changed one line
;[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).''\\ \\BBC_Id_Next from [P2K_BE_BC_RULES] is a mandatory 10-character numeric field that is provided and may be edited.
At line 55 changed 9 lines
;[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'}]
;[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.
\\
This page (revision-18) was last changed on 26-Nov-2021 10:22 by JMyersTop