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

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

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
5 26-Nov-2021 10:22 8 KB JEscott to previous
4 26-Nov-2021 10:22 8 KB JEscott to previous | to last
3 26-Nov-2021 10:22 7 KB JEscott to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
CONVERTING BENEFIT ENROLLMENTS
CONVERTING BENEFIT ENROLLMENTS

Version management

Difference between version and

At line 34 changed one line
If the [BC Code|BC_CODE] values can be derived from other information already loaded into the database (such as the employees wage rate), there is no need to load more than one record for each benefit plan/coverage per employee. Most benefit enrollment records can be loaded in without setting the value for the [BC Code|BC_CODE] or amount fields. The next time the enrollment record is processed through a pay cycle and the unofficial record is created, all the Benefit components amounts will be calculated based on the rules defined for each.
If the [BC Code|BC_CODE] values can be derived from other information already loaded into the database (such as the employees wage rate), there is no need to load more than one record for each benefit plan/coverage per employee. Most benefit enrollment records can be loaded in without setting the value for the [BC Code|BC_CODE] or amount fields. The next time the enrollment record is processed through a pay cycle and the unofficial record is created, all the [Benefit components|BENEFIT COMPONENTS] amounts will be calculated based on the rules defined for each.
At line 36 changed one line
However, these calculations can vary for each plan and coverage each plan/coverage definition within the application will have to be checked to know if a [BC Code|BC_CODE] and Amount value will be needed during the conversion of the data.
However, these calculations can vary for each plan and coverage each plan/coverage definition within the application will have to be checked to know if a [BC Code|BC_CODE] and [Amount|AMOUNT] value will be needed during the conversion of the data.
At line 38 changed one line
Enrollment into any benefit plan will require a minimum of one record for each employee, plan and coverage combination within the application. If the plan and coverage combination does not need any [BC Code|BC_CODE] values converted, there will be only one record which will have a null value in the [BC Code|BC_CODE] and Amount fields. If the plan and coverage combination requires amounts to be loaded and converted into the ENROLLMENT records, the [BC Code|BC_CODE], Amount and Amount Override fields will need values. There may be one or more records in the interface table based on the number of [BC Code|BC_CODE] values that need to be converted.
Enrollment into any benefit plan will require a minimum of one record for each employee, plan and coverage combination within the application. If the plan and coverage combination does not need any [BC Code|BC_CODE] values converted, there will be only one record which will have a null value in the [BC Code|BC_CODE] and [Amount|AMOUNT] fields. If the plan and coverage combination requires amounts to be loaded and converted into the ENROLLMENT records, the [BC Code|BC_CODE], [Amount|AMOUNT] and [Amount Override|AMOUNT_OVERRIDE] fields will need values. There may be one or more records in the interface table based on the number of [BC Code|BC_CODE] values that need to be converted.
This page (revision-5) was last changed on 26-Nov-2021 10:22 by JEscottTop