Concept: Hours Aggregation on Pay Results
You can configure Workday to aggregate the hours from these sources into 1 line:
- Pay inputs.
- Workday Time Tracking time blocks.
Criteria for Aggregation
Workday aggregates hours from pay inputs or time blocks on which all of these attributes are the same:
- Company
- Costing company
- Currency override
- Pay component
- Position
- Rate
- Workers compensation codes
- Worktags
Pay inputs and time blocks that differ in any of these attributes aggregate separately.
- Example
- Robert worked 10 8-hour days this pay period. Daily pay inputs were identical, except for the costing company.
- The 64 hours costed to company A aggregate into 1 result line.
- The 16 hours costed to company B aggregate into another result line.
- Example
- Lindsey worked 10 8-hour days this pay period. She received a compensation increase from 20 to 22 on the sixth day. This proration event creates a separate subperiod and therefore separate result lines:
- 40 hours at the 20 rate aggregate into 1 result line.
- 40 hours at the 22 rate aggregate into another result line.
Hours That Don't Aggregate
Workday doesn't aggregate:
- Ongoing pay inputs.
- Inputs with more than 1 input line, such as hours and rate.
Adjustments aggregate only with other adjustments. Overrides aggregate only with other overrides.
Aggregation and Ongoing Multiple Work Jurisdictions (USA)
When you use ongoing multiple work jurisdictions (OMWJ), Workday aggregates input and time block hours according to the allocation percentages.
- Example
- Christopher's work jurisdiction allocations are as follows:
- California: 40%
- Oregon: 40%
- Hawaii: 20%
- In the current pay period, he has these inputs:
- Input 1 (Monday): 10 hours
- Input 2 (Tuesday): 5 hours
- Without aggregation, Christopher has 6 pay result lines:Pay ComponentWorktagRelated CalculationAmountInput AmountHourly Pay [USA]CaliforniaHours (unprorated)4 hours10Hourly Pay [USA]OregonHours (unprorated)4 hours10Hourly Pay [USA]HawaiiHours (unprorated)2 hours10Hourly Pay [USA]CaliforniaHours (unprorated)2 hours5Hourly Pay [USA]OregonHours (unprorated)2 hours5Hourly Pay [USA]HawaiiHours (unprorated)1 hour5
- With aggregation, Christopher has 3 pay result lines:
- Pay ComponentWorktagRelated CalculationAmountInput AmountHourly Pay [USA]CaliforniaHours (unprorated)6 hours15Hourly Pay [USA]OregonHours (unprorated)6 hours15Hourly Pay [USA]HawaiiHours (unprorated)3 hours15
When you enter an override State worktag on a pay input, Workday doesn't aggregate that input with inputs that it allocates according to OMWJ splits.
- Example
- You add another 8-hour pay input for Christopher, with a California override worktag so California tax rates apply to all 8 hours. Workday adds a pay result line for the input and doesn’t add it to the OMWJ-allocated California hours.
Pay Component | Worktag | Related Calculation | Amount | Input Amount |
|---|---|---|---|---|
Hourly Pay [USA] | California (OMWJ split) | Hours (unprorated) | 6 hours | 15 |
Hourly Pay [USA] | Oregon | Hours (unprorated) | 6 hours | 15 |
Hourly Pay [USA] | Hawaii | Hours (unprorated) | 3 hours | 15 |
Hourly Pay [USA] | California (override worktag) | Hours (unprorated) | 8 hours | 8 |
Retro Calculations
Workday can aggregate hours for retroactive pay inputs. You can configure hours aggregation on the
Effective Dated
tab of the pay component. Workday uses the snapshot in effect at the end of the pay period to determine whether to aggregate retroactive pay input for prior periods.
- Example
- The pay component Hourly Pay has 3 effective-dated snapshots:
- 2019-01-01
- 2019-03-15
- 2019-04-01
- You add retroactive pay inputs for the monthly pay period 2019-03-01 through 2019-03-31. Workday checks the status of theAggregatecheck box for the pay component related calculation in the 2019-03-15 snapshot. When selected, Workday aggregates the hours.
Because Workday aggregates hours when calculating payroll, you won't see aggregated hours on pay results that Workday calculated before you enabled aggregation.
Rounding in Payroll Calculations
You might see a nominal difference in pay results when you compare unaggregated result lines to result lines that Workday aggregates. Since rounding occurs after Workday completes the calculations, rounding the aggregated result line produces a more precise sum.
- Example
- Pay result lines without aggregation enabled:HoursRateTotal7.12515.15000107.947.12515.15000107.947.12515.15000107.94Sum323.82
- Pay result line with aggregation enabled:HoursRateTotal21.37515.15000323.83Sum323.83