Proration with Element Segmentation
If you do not define proration correctly when setting up accumulator driven earnings or deductions, you could get unexpected results.
For example, if you place a driver accumulator on a segmentation event list, you should not prorate the element it drives. This is because slicing the driver automatically causes slicing of both the accumulator members and the driven element. However, if you do not place the driver on a segmentation event list, and the element it drives is on the event list, the driver and the driven element will not be sliced equally, and the two will not match. In a situation like this, you should prorate the driven element.
Example: Element Segmentation of Earnings and Deductions with Accumulator Drivers; Driver Not on Segmentation Event List
The accumulator AC1 drives deduction D1.
AC1 is not included in the element segmentation event definition; D1 is included (when there is segmentation, only D1 is sliced).
AC1 has these members: earnings E1, E2, and E3.
STATE is a user key for AC1 and a user field for D1.
D1 is defined as Base x Percent (assume the percent is the same for each State).
Base = CURR_DRIVER_VAL and Percent = 15%.
Note:
CURR_DRIVER_VAL is a delivered system element that can be used to retrieve the current value of a driver accumulator if that accumulator is used in the calculation of an element. We discuss this and other system elements later in this topic.
Assume a monthly pay period with a segmentation trigger defined for January 15.
E1 = 700, E2 = 1000, and E3 = 1500.
This table contains the earnings results:
| Earnings | Instance Number | Amount | User Field |
|---|---|---|---|
|
E1 |
1 |
350 |
State 1 |
|
E1 |
2 |
350 |
State 2 |
|
E2 |
1 |
500 |
State 1 |
|
E2 |
2 |
500 |
State 2 |
|
E3 |
1 |
750 |
State 1 |
|
E3 |
2 |
750 |
State 2 |
This table contains the accumulator results:
| Accumulator | Instance Number | Slice Dates | Amount | User Field |
|---|---|---|---|---|
|
AC1 |
1 |
January 1–31 |
1600 |
State 1 |
|
AC1 |
2 |
January 1–31 |
1600 |
State 2 |
The following table shows the deduction results with proration turned off:
| Deduction | Instance Number | Slice Number | Slice Dates | Amount | User Field |
|---|---|---|---|---|---|
|
D1 |
1 |
1 |
January 1–14 |
240 |
State 1 |
|
D1 |
2 |
2 |
January 15–31 |
240 |
State 1 |
|
D1 |
3 |
1 |
January 1–14 |
240 |
State 2 |
|
D1 |
4 |
2 |
January 15–31 |
240 |
State 2 |
Note:
When proration is turned off, the results are overstated.
This table shows the deduction results with proration turned on:
| Deduction | Instance Number | Slice Number | Slice Dates | Amount | User Field |
|---|---|---|---|---|---|
|
D1 |
1 |
1 |
January 1–14 |
120 |
State 1 |
|
D1 |
2 |
2 |
January 15–31 |
120 |
State 1 |
|
D1 |
3 |
1 |
January 1–14 |
120 |
State 2 |
|
D1 |
4 |
2 |
January 15–31 |
120 |
State 2 |
Related Topics