Grouping Deltas Using User Field Levels
Global Payroll enables you to group or separate deltas for an earning or deduction based on matching user field sets. You control the level of matching needed to group deltas for an element by defining the match requirements—that is, you can require matching on the first user field only before deltas can be grouped, on both the first and second user fields, on the first, second, and third user fields, and so on.
To control how the system groups retroactive deltas for forwarding to the current period, select one of the following user field levels when you define an earning or deduction element:
| User Field Level | Description |
|---|---|
|
None |
Element level grouping (all deltas combined regardless of differences between user field sets) |
|
Group through User Field 1 |
Partial set (only User Field 1 must be identical to combine deltas) |
|
Group through User Field 2 |
Partial set (only User Fields 1 and 2 must be identical to combine deltas) |
|
Group through User Field 3 |
Partial set (only User Fields 1, 2, and 3 must be identical to combine deltas) |
|
Group through User Field 4 |
Partial set (User Fields 1, 2, 3, and 4 must be identical to combine deltas) |
|
Group through User Field 5 |
Partial set (User Fields 1, 2, 3, 4, and 5 must be identical to combine deltas) |
|
All User Fields Defined |
Complete set (all user fields must be identical to combine deltas) |
Note:
You set the Retro Delta User Field Level on the User Fields page.
See Earnings - User Fields for Element <name> Page.
The examples in this topic illustrate how deltas are grouped or separated based on the user field level.
Example 1: User Field Level = None
Assume that there is retroactive processing in Period 2 back to Period 1, and that the user field level is set to None for element E1.
The retroactive method is forwarding.
The results for Period 1 (V1R1) are:
| Earnings | Instance | Amount | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
300 |
State 1 |
Location 1 |
ABC |
|
E1 |
2 |
200 |
State 1 |
Location 2 |
DEF |
|
E1 |
3 |
150 |
State 3 |
Location 3 |
ABC |
When Period 1 is recalculated (V1R2), the results are:
| Earnings | Instance | Amount | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
400 |
State 1 |
Location 1 |
ABC |
|
E1 |
2 |
300 |
State 1 |
Location 2 |
DEF |
|
E1 |
3 |
200 |
State 3 |
Location 3 |
ABC |
The system stores the following deltas for E1 in the result tables:
| Earnings | Delta Number | Delta | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
250 |
Note:
Because deltas are stored at the element level, the system sums the deltas for each user field set (100 + 100 + 50 = 250). No user field values are stored.
Example 2: User Field Level = All User Fields Defined (Complete Set)
Assume that there is retroactive processing in Period 2 back to Period 1, and that the user field level requires a complete user field match to group retroactive deltas.
The retroactive method is forwarding.
The results for Period 1 (V1R1) are:
| Earnings | Instance | Amount | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
300 |
State 1 |
Location 1 |
ABC |
|
E1 |
2 |
200 |
State 1 |
Location 2 |
DEF |
|
E1 |
3 |
150 |
State 3 |
Location 3 |
ABC |
When Period 1 is recalculated (V1R2), the results are:
| Earnings | Instance | Amount | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
400 |
State 1 |
Location 1 |
ABC |
|
E1 |
2 |
300 |
State 1 |
Location 2 |
DEF |
|
E1 |
3 |
200 |
State 3 |
Location 3 |
ABC |
The system stores the following deltas for E1 in the result tables:
| Earnings | Delta Number | Delta | User Field 1 (State) | User Field 2 (Location) | User Field 3 (Company) |
|---|---|---|---|---|---|
|
E1 |
1 |
100 |
State 1 |
Location 1 |
ABC |
|
E1 |
2 |
100 |
State 1 |
Location 2 |
DEF |
|
E1 |
3 |
50 |
State 3 |
Location 3 |
ABC |
Note:
Because the user field level requires a complete match to sum retroactive deltas, the system stores the deltas separately by user field set.
Example 3: User Field Level = Through User Field 1 (Partial Set )
Assume that there is retroactive processing in Period 2 back to Period 1, and that the user field level requires a match through User Field 1 to group retroactive deltas.
User Field 1 is Company.
The retroactive method is forwarding.
The results for Period 1 (V1R1) are:
| Earnings | Instance | Amount | User Field 1 (Company) | User Field 2 (State) | User Field 3 (Location) |
|---|---|---|---|---|---|
|
E1 |
1 |
300 |
ABC |
State 1 |
Location 1 |
|
E1 |
2 |
200 |
DEF |
State 1 |
Location 2 |
|
E1 |
3 |
150 |
ABC |
State 3 |
Location 3 |
When Period 1 is recalculated (V1R2), the results are:
| Earnings | Instance | Amount | User Field 1 (Company) | User Field 2 (State) | User Field 3 (Location) |
|---|---|---|---|---|---|
|
E1 |
1 |
400 |
ABC |
State 1 |
Location 1 |
|
E1 |
2 |
300 |
DEF |
State 1 |
Location 2 |
|
E1 |
3 |
200 |
ABC |
State 3 |
Location 3 |
The system stores the following deltas for E1 in the result tables:
| Earnings | Delta Number | Delta | User Field 1 (Company) | User Field 2 (State) | User Field 3 (Location) |
|---|---|---|---|---|---|
|
E1 |
1 |
150 |
ABC |
||
|
E1 |
2 |
100 |
DEF |
Note:
The system stores deltas by company (User Field 1) in this example.