Matching Element Resolutions Initiated by Accumulator Drivers
In Global Payroll, the same matching rules that apply to element assignments and positive input entries apply in the case of accumulator-driven elements (the matching rules simply extend to the accumulator driven earnings and deductions). In other words, when an element with an accumulator driver instance occurs in the same slice or segment with element assignments and positive input entries, the system compares the user field sets of the element assignments or positive input entries with those of the driver instances to determine to which instances the element assignments and positive input entries apply. A match occurs when the system encounters identical user field sets in the same slice or segment.
See Matching Earning and Deduction Assignments with Positive Input Entries When There are User Fields.
Example 1: Matching Accumulator-Driven Elements with Earning/Deduction Assignments and Positive Input
A tax deduction is defined with a driver accumulator (State Taxable Gross Accumulator).
Every driver instance matches with either an instance of positive input or an element assignment.
The tax deduction has one user field: State.
The tax deduction has a calculation rule of Base x Percent.
Assume that the percent is defined as a formula that uses the state to retrieve the applicable percent.
Assume that the base is defined as CURR_DRIVER_VAL.
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.
During payroll processing, the system encounters two instances of the driver:
Note:
In this example, earning/deduction assignment is abbreviated E/D Assignment, and positive input is abbreviated PI.
| Driver (Accumulator Name) | User Key (State) | Result Value |
|---|---|---|
|
State Taxable Gross |
State 1 |
6000 |
|
State Taxable Gross |
State 2 |
5500 |
This table lists the earning/deduction assignments and positive input entries for the tax deduction:
| E/D Assignment | PI (Override) | |
|---|---|---|
|
Element Name |
Tax Deduction |
Tax Deduction |
|
Instance Number |
1 |
1 |
|
Process Order |
20 |
N/A |
|
Amount |
600 |
225 |
|
User Field (State) |
State 1 |
State 2 |
The system resolves two instances of the tax deduction in the following order:
| Resolution Number | Amount | User Field (State) | Override Source |
|---|---|---|---|
|
1 |
600 |
State 1 |
Element Assignment |
|
2 |
225 |
State 2 |
Positive Input Override |
In this example:
-
There are two instances of the driver element (State 1 and State 2).
-
The system matches the driver instance for State 1 with the earning/deduction assignment based on identical user field values.
-
The system matches the driver instance for State 2 with the positive input override based on identical user field values.
-
The earning/deduction assignment and the positive input entry override the corresponding element definitions.
Example 2: Not All Driver Instances Match with Element Assignments or Positive Input
A tax deduction is defined with a driver accumulator (State Taxable Gross Accumulator).
Not all driver instances match with either an instance of positive input or an element assignment.
The tax deduction has one user field: State.
The tax deduction has a calculation rule of Base x Percent.
Assume that the percent is defined as a formula that uses the state to retrieve the applicable percent, and that the formula returns a value of 3% for states 1, 2, and 3.
Assume that the base is defined as CURR_DRIVER_VAL.
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.
During payroll processing, the system encounters three instances of the driver:
Note:
In this example, earning/deduction assignment is abbreviated E/D Assign., positive input is abbreviated PI, and the positive input action type of override is abbreviated Over.
| Driver (Accumulator Name) | User Key (State) | Result Value |
|---|---|---|
|
State Taxable Gross |
State 1 |
6000 |
|
State Taxable Gross |
State 2 |
5500 |
|
State Taxable Gross |
State 3 |
3300 |
This table lists the earning/deduction assignments and positive input entries for the tax deduction:
| E/D Assign. | E/D Assign. | E/D Assign. | PI (Over) | PI (Over) | PI (Over) | |
|---|---|---|---|---|---|---|
|
Element Name |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
|
Instance Number |
1 |
2 |
3 |
1 |
2 |
3 |
|
Process Order |
20 |
10 |
30 |
N/A |
N/A |
N/A |
|
Amount |
600 |
555 |
175 |
225 |
325 |
500 |
|
User Field (State) |
State 1 |
State 4 |
State 5 |
State 2 |
State 6 |
State 5 |
The system resolves six instances of the tax deduction:
| Resolution Number | Amount | User Field (State) | Override Source |
|---|---|---|---|
|
1 |
555 |
State 4 |
Element Assignment |
|
2 |
600 |
State 1 |
Element Assignment |
|
3 |
500 |
State 5 |
Positive Input Override |
|
4 |
225 |
State 2 |
Positive Input Override |
|
5 |
325 |
State 6 |
Positive Input Override |
|
6 |
99 (3300 x 3%) |
State 3 |
Driver Occurrence |
In this example:
-
The system matches the accumulator instance for State 1 (6000) with the element assignment for 600. It processes the element assignment and not the accumulator instance (the assignment overrides the accumulator instance).
-
The system matches the element assignment for State 5 (175) with its corresponding positive input instance (500). It processes the positive input instance and disregards the element assignment (the positive input overrides the element assignment).
-
There are no other user field set matches. The system processes the remaining positive input overrides and the driver occurrences with no matching positive input entry or element assignment (99).