Managing Multiple Resolutions through a Driver When There Are Earning, Deduction, and Positive Input Assignments
This topic discusses how Global Payroll processes accumulator-driven elements when there are earning/deduction assignments and positive input entries for the same elements.
It explains how Global Payroll:
Defines user field sets for earnings and deductions with accumulator drivers.
Fills out user field sets for an accumulator-driven element.
Matches element resolutions initiated by accumulator drivers.
Defines the processing order.
The concepts discussed here are critical to understanding the interaction between accumulator driven elements, positive input entries, and element assignments.
Note: This topic supplements the information on the interaction between positive input entries and element overrides in the Setting Up Overrides topic. You should review the Setting Up Overrides topic before reading the information in this topic.
Earnings or deductions driven by an accumulator inherit their user field sets—their associated user fields and values—from the user keys of the accumulator that drives their resolution.
All earnings and deductions using accumulator drivers must follow these rules:
The user fields of the earning or deduction must be in the same order as the user keys of the driver accumulator.
Earnings or deductions cannot be linked to a driver accumulator with no associated user key.
There must be at least one user field (corresponding to a user key on the accumulator) associated with the earning or deduction.
The values of the user fields associated with accumulator-driven elements can come from several different sources. They can come from:
Supporting element overrides entered on the earning/deduction assignment pages (payee level overrides).
Overrides values entered at the pay group, calendar, or other levels.
From arrays, formulas, brackets, or other elements that are set up to populate the user fields.
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).
The processing rules that apply when earning and deduction assignments occur with positive input also apply when accumulator driven elements occur in combination with element assignments and positive input:
See Defining Interactions Between Positive Input Entries and Element Assignments with User Field Sets.
Earning/deduction assignments are calculated first within each unique user field set and dictate the processing order of matching positive input entries.
After earning/deduction assignments, the system processes positive input entries with matching user field sets in instance number order.
Note: If positive input overrides an element assignment, the positive input inherits the processing order of the assignment it replaces.
Next, the system processes positive input entries without matching user fields in instance number order.
In addition, the system observes the following rule for accumulator-driven elements:
Driver occurrences with no element assignment or positive input user field set match are processed after positive input entries.
Example: Process Order with Accumulator Driven Elements
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 Assignment, positive input is abbreviated PI, and the positive input action types of override and additional are abbreviated Over and Add.
|
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 for the tax deduction:
|
E/D Assignment |
E/D Assignment |
E/D Assignment |
E/D Assignment |
|
|---|---|---|---|---|
|
Element Name |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
|
Instance Number |
1 |
2 |
3 |
4 |
|
Process Order |
10 |
30 |
20 |
30 |
|
Amount |
1000 |
750 |
175 |
225 |
|
User Field (State) |
State 1 |
State 1 |
State 4 |
State 5 |
This table lists the positive input entries for the tax deduction:
|
PI (Over) |
PI (Over) |
PI (Over) |
PI (Add) |
PI (Over) |
PI (Add) |
|
|---|---|---|---|---|---|---|
|
Element Name |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
Tax Deduction |
|
Instance Number |
1 |
2 |
3 |
4 |
5 |
6 |
|
Amount |
600 |
555 |
175 |
225 |
325 |
500 |
|
User Field (State) |
State 1 |
State 2 |
State 6 |
State 2 |
State 6 |
State 5 |
The system resolves nine instances of the tax deduction in the following order:
|
Resolution Number |
Amount |
User Field (State) |
Override |
|---|---|---|---|
|
1 |
600 |
State 1 |
Positive Input Override |
|
2 |
175 |
State 4 |
Element Assignment |
|
3 |
225 |
State 5 |
Element Assignment |
|
4 |
500 |
State 5 |
Positive Input Additional |
|
5 |
555 |
State 2 |
Positive Input Override |
|
6 |
225 |
State 2 |
Positive Input Additional |
|
7 |
175 |
State 6 |
Positive Input Override |
|
8 |
325 |
State 6 |
Positive Input Override |
|
9 |
99 (3300 x 3%) |
State 3 |
Driver Occurrence |
In this example:
The system processes the user field set with the lowest process order number first (State 1, process order number = 10).
The system then processes the user field set with the next highest process order number (State 4, process order number = 20).
The system continues to order and process elements in this way until it runs out of matching user field sets. The last element it processes is a driver occurrence for State 3 with no matching element assignment or positive input entry (the system gives this driver occurrence the highest process order number [the lowest priority].
Note: The system element CURR_DRIVER_VAL has a value only when an element assignment or positive input entry has a corresponding accumulator driver instance. If there is no corresponding accumulator instance, the value of CURR_DRIVER_VAL is zero. Consequently, when you enter data for earning/deduction assignments or positive input without a driver instance, you must specify the value of the Base and/or Amount fields. Thus, in the current example, the entries for State 4, State 5, and State 6 require a value for the Base or Amount.