10.1 Absence & Time-Off Plans, Types & Accruals

10.1 Absence & Time-Off Plans, Types & Accruals

Quick Answer: In Workday HCM, Absence Management is architecturally divided into Time Off Plans and Leave of Absence (LOA) Plans. Time Off Plans govern short-term, incremental absences (such as vacation, personal days, and sick time) measured in Hours or Days, keeping the employee's worker status Active. A crucial architectural rule tested on the exam is that a Time Off Plan's Unit of Time (Hours vs. Days) is permanently locked upon creation and cannot be changed. Time Off Plans link to Accrual Plans, which define how balances accumulate across Balance Periods using configurable frequencies, service-based waiting periods, Accrual Caps, Balance Caps, and Carryover Limits. When corrections are needed, administrators use Adjust Time Off Balance for relative delta adjustments with complete audit history, versus Override Time Off Balance for absolute balance resets.

---

Time Off Plans vs. Leave of Absence Plans

Workday HCM distinguishes fundamentally between two categories of absence plans based on operational duration, ledger tracking mechanics, and their impact on the worker's operational status.

+---------------------------------------------------------------------------------------------------+
|                                 WORKDAY ABSENCE MANAGEMENT ARCHITECTURE                           |
+---------------------------------------------------------------------------------------------------+
                                                  |
         +----------------------------------------+----------------------------------------+
         |                                                                                 |
         v                                                                                 v
+--------------------------------------------------+             +--------------------------------------------------+
|                 TIME OFF PLANS                   |             |             LEAVE OF ABSENCE PLANS               |
| - Short-term, incremental absences               |             | - Extended, continuous or intermittent leaves    |
| - Vacation, Sick, Floating Holiday, Bereavement  |             | - FMLA, Medical, Parental, Military, Sabbatical  |
| - Tracked in Hours or Days against a ledger      |             | - Tracked via Start Date and End Date / Entitle  |
| - Worker Status remains ACTIVE                   |             | - Worker Status changes to ON LEAVE              |
| - Position remains occupied                      |             | - Position can be held or released for backfill  |
| - Payroll: Continues normal base salary          |             | - Payroll: Suppressed (unpaid) or leave earning  |
+--------------------------------------------------+             +--------------------------------------------------+

Architectural Comparison

---

Time Off Plans & Time Off Types

To implement time off in Workday, administrators configure two tightly linked business objects: Time Off Plans and Time Off Types.

The Relationship Between Plans and Types

• Time Off Plan: The administrative, accounting, and calculation container. It defines the rules governing eligibility, accruals, balance tracking, balance periods, caps, and carryover rules. Created via the task Create Time Off Plan.
• Time Off Type: The user-facing absence category that employees and managers select when initiating an absence request via the Request Time Off business process. Created via Create Time Off.
• A single Time Off Plan can be associated with one or multiple Time Off Types. For example, a single Paid Time Off (PTO) Plan can house both PTO Vacation and PTO Sick time off types, allowing them to draw against a unified, consolidated balance pool.

Units of Time: Hours vs. Days

When creating a Time Off Plan, the administrator must select the Unit of Time:

• Hours: Typically utilized for hourly/non-exempt workers, or in jurisdictions where statutory sick pay requires tracking time down to fractions of an hour (e.g., 1.5 hours for a doctor's appointment). Deductions interface directly with the worker's assigned Work Schedule Calendar to determine scheduled hours per day.
• Days: Typically utilized for salaried/exempt staff who take time in full-day or half-day (0.5) increments.

Exam Trap: The Unit of Time is immutable. Once a Time Off Plan is created and saved in Workday, the Unit of Time cannot be edited or converted. If an organization implements a plan in Days and later decides to track time in Hours, the administrator must create an entirely new Time Off Plan in Hours, configure new eligibility rules, enroll the population, and transition balances.

Position-Based vs. Worker-Based Tracking

Workday supports tracking time off balances at two distinct levels:

• Worker-Based Tracking (Default): The worker holds a single consolidated balance across all jobs. If a worker has multiple concurrent jobs, time off is requested against the worker overall.
• Position-Based Tracking: Balances, accruals, and deductions are maintained independently for each position the worker holds. This is essential for higher education, healthcare, and retail environments where an employee may hold two distinct part-time roles (e.g., Adjunct Lecturer and Lab Assistant) with separate leave policies and accrual rates.

---

Accrual Plans & Calculation Mechanics

An Accrual Plan defines the mathematical engine that credits earned time off to a worker's balance over time. It is linked directly to a parent Time Off Plan.

Accrual Definitions & The Calculation Engine

Accrual Plans evaluate business rules using the Workday Calculation Engine. An Accrual Definition can be structured as:

1. Fixed Amount: A flat grant credited each period (e.g., 10 hours per month).
2. Tenure-Based / Length of Service Bands: Accrual amounts escalate based on the worker's continuous service tenure. Built using Lookup Table or Arithmetic calculated fields:
   • 0 to 4 Years of Service: 10 hours per month (120 hours/year)
   • 5 to 9 Years of Service: 13.33 hours per month (160 hours/year)
   • 10+ Years of Service: 16.66 hours per month (200 hours/year)
3. Hours-Worked Accrual: Common for hourly or casual workforces where workers accrue leave proportionally based on actual hours reported on timecards (e.g., 1 hour of paid leave accrued for every 30 hours worked).

Accrual Frequencies

Workday supports flexible accrual cadences matching organizational payroll or fiscal cycles:

• Annual (Front-Loaded): The entire year's entitlement is granted on the first day of the balance period (e.g., January 1).
• Monthly: Accrues once per calendar month (typically on the 1st or last day of the month).
• Semi-Monthly: Accrues twice per month (24 cycles per year).
• Bi-Weekly: Accrues every two weeks (26 cycles per standard year, with leap-year handling for 27-period cycles).
• Weekly: Accrues every week (52 cycles per year).
• Per Pay Period: Aligns dynamically with the worker's assigned payroll pay group schedule.

Waiting Periods (Accrual vs. Usage)

Organizations frequently restrict leave for newly hired workers through Waiting Periods:

• Accrual Waiting Period: The worker earns zero accruals until completing a specified duration of service (e.g., no accrual for the first 90 days from Hire Date). Once reached, accruals begin prospectively (or retrospectively if back-granting is configured).
• Usage Waiting Period: The worker accrues time immediately upon hire, but Workday blocks the worker from submitting time off requests against that balance until completing a probationary threshold (e.g., 90 days from hire).

Balance Periods & Plan Year Cycles

A Balance Period defines the operational cycle over which accruals accumulate, usage is tracked, and carryover rules execute:

• Calendar Year: Runs January 1 through December 31.
• Fiscal Year: Aligns with corporate fiscal accounting boundaries (e.g., July 1 through June 30).
• Anniversary Year: Individualized for each worker, running from the worker's Hire Date or Length of Service Date to their annual anniversary.

---

Carryover Limits, Caps & Proration Rules

Managing liabilities requires precise controls over how much time employees can accumulate, retain, or lose across balance period boundaries.

+---------------------------------------------------------------------------------------------------+
|                                 CAPS & CARRYOVER ARCHITECTURE                                     |
+---------------------------------------------------------------------------------------------------+

   [ Accrual Calculation Engine ] ---> Grants +10 Hours / Month
                |
                v
     +--------------------+   Is Accrual Cap Reached? (e.g., Max 120 hrs/year)
     |    ACCRUAL CAP     |   --> YES: Halts periodic accruals from generating.
     +--------------------+   --> NO: Allows accrual to pass into balance.
                |
                v
     +--------------------+   Is Balance Cap Reached? (e.g., Max 160 hrs total ledger)
     |    BALANCE CAP     |   --> YES: Caps cumulative ledger; extra hours forfeited.
     +--------------------+   --> NO: Balance increments successfully.
                |
                | (At Balance Period Year-End: Dec 31)
                v
     +--------------------+   Evaluate Carryover Rule (e.g., Max 40 hrs carryover)
     |   CARRYOVER CAP    |   --> Up to 40 hours roll into new plan year.
     +--------------------+   --> Excess balance above 40 hours is forfeited (or paid out).
                |
                v (Optional: Expiration Date)
     +--------------------+   March 31: Any remaining carryover hours expire from ledger.
     | EXPIRATION DATE    |
     +--------------------+ 

The Three Distinct Balance Caps

Exam questions frequently challenge candidates to differentiate between Workday's three distinct capping mechanisms:

1. Accrual Cap: Restricts the total amount of time off an employee can earn within a single balance period or calculation cycle (e.g., maximum 120 accrued hours per year). Once an employee has accrued 120 hours, the calculation engine stops crediting further accruals until the next balance period, regardless of how many hours the employee takes.
2. Balance Cap (Maximum Balance Limit): Sets an absolute ceiling on the cumulative balance a worker can hold in their ledger at any given moment from all sources combined (accruals + carryover + adjustments). If a worker reaches the 160-hour balance cap, future accruals are blocked or forfeited until the worker takes time off and reduces their balance below 160 hours.
3. Carryover Cap (Rollover Limit): Enforces the maximum balance that can transition from the closing balance period into the new balance period.

Carryover Rules & Forfeitures

At the end of a balance period, Workday evaluates the plan's carryover configuration:

• Unlimited Carryover: All unused balance rolls forward into the new year.
• Capped Carryover: Workers roll forward up to a maximum threshold (e.g., 40 hours); any remaining balance above the cap is systematically forfeited ("Use It or Lose It").
• Carryover Expiration Date: Rolled-over balances can be assigned a hard expiration date (e.g., March 31 of the following year). If the employee does not take the carried-over hours prior to the expiration date, Workday executes an automated forfeiture transaction.
• Negative Balance Carryover: Determines whether an employee who ends the year with a negative balance carries that deficit forward into the new plan year or has it cleared.

Proration on Hire and Termination

• Mid-Period Hire Proration: When an employee is hired mid-month or mid-pay period, Workday calculates a prorated accrual based on: (Days Employed in Period $\div$ Total Days in Period) $\times$ Standard Accrual Amount, or using Workday's built-in proration calendar rules.
• Termination Balance Payout: When an employee separates, the termination business process evaluates the Time Off Plan's payout configuration. If enabled, Workday calculates the final accrued-to-date balance and sends the payable hours/days to Workday Payroll or external payroll integrations via the Time Off Payout business process component.

---

Balance Tracking & The Core Balance Formula

Workday Absence Management maintains a real-time, transaction-based audit ledger for every worker enrolled in a Time Off Plan. Candidate balances are calculated dynamically using the system's foundational balance equation.

The Foundational Ledger Equation

$\text{Ending Balance} = \text{Beginning Balance} + \text{Accruals} + \text{Adjustments} - \text{Taken Time Off}$

$\text{Available Balance} = \text{Ending Balance} - \text{Pending Requests}$

Ledger Component Definitions

• Beginning Balance: The balance brought forward from the prior balance period after applying carryover caps and forfeitures.
• Accruals: Cumulative time granted by the accrual calculation engine in the current balance period.
• Adjustments: Discretionary manual or automated credits/debits applied to the ledger.
• Taken Time Off: Approved, completed absence events falling on or before the calculation effective date.
• Pending Requests: Absence requests that have been submitted but are awaiting approval, or approved requests scheduled for future dates within the active period. Workday displays Available Balance in self-service to prevent workers from overdrawing their balance across multiple future requests.

Real-Time Event Processing vs. Scheduled Absence Runs

• Event-Driven Balance Calculation: In Workday, absence requests evaluate balances in real time. When a worker opens the Absence Calendar, Workday dynamically evaluates completed transactions, pending requests, and scheduled hours on the fly.
• Absence Run (Batch Processing): Used to execute enterprise-wide scheduled calculations, such as periodic accruals, carryover rollovers, balance forfeitures, and year-end closeouts across thousands of workers via Schedule Absence Calculation.

---

Time Off Adjustments & Overrides

When ledger discrepancies occur—such as payroll audit corrections, prior service credits, or policy exceptions—administrators have two distinct tasks available in Workday.

Adjust Time Off Balance vs. Override Time Off Balance

Exam Tip: If an exam question asks how to award an employee an extra 8 hours of vacation due to an exceptional weekend project while preserving complete audit history, the correct answer is Adjust Time Off Balance with a value of +8. Never select Override Time Off Balance for standard operational adjustments.

---

Step-by-Step Configuration Workflows

1. Creating a Time Off Plan and Accrual Plan

To configure a complete accrual-based time off plan:

Task: Create Time Off Plan
  -> Enter Plan Name (e.g., "US Salaried Vacation Plan")
  -> Select Unit of Time: "Hours" (Permanent selection)
  -> Define Balance Period: "Calendar Year" (Jan 1 - Dec 31)
  -> Attach Absence Eligibility Rule: "Country is United States AND Time Type is Full_Time"
  -> Check "Track Balances": Yes
  -> Configure Caps: Balance Cap = 200 Hours
  -> Configure Carryover: Max Carryover = 40 Hours | Expiration Date = March 31
  -> Create & Attach Accrual Plan:
       - Accrual Frequency: "Monthly"
       - Accrual Method: Length of Service Calculation Table
       - Waiting Period: 90 Days from Hire Date
  -> Click OK to commit

2. Creating and Linking a Time Off Type

Once the plan is established, create the worker-facing entry type:

Task: Create Time Off
  -> Enter Time Off Name: "Vacation Time Off"
  -> Select Associated Time Off Plan: "US Salaried Vacation Plan"
  -> Select Unit of Time: "Hours" (Matches plan)
  -> Define Position Visibility / Self-Service Entry: Enabled
  -> Configure Absence Validation Rules: Prevent Negative Balance
  -> Click OK to activate

---

Configuration & Comparison Reference

---

Certification Pitfalls & Common Exam Traps

1. The Irrevocable Unit of Time: A recurring exam trap involves an organization wishing to change an existing plan from Days to Hours. Exam choices will propose editing the plan, running a unit conversion process, or altering tenant absence options. All are incorrect. The Unit of Time is locked permanently upon plan creation; a new plan must be configured.
2. Accrual Cap vs. Balance Cap Confusion: When a question describes an employee who has reached an Accrual Cap of 120 hours and is awarded an administrative manual adjustment of +10 hours, candidates often incorrectly assume the adjustment is blocked. The accrual cap only blocks the accrual calculation engine; manual adjustments and carryovers are governed by the Balance Cap.
3. Adjust vs. Override Balance Distinction: Remember that Adjust Time Off Balance applies a mathematical delta (+/-) that maintains the integrity of prior ledger entries, whereas Override Time Off Balance forcefully sets the balance to an absolute number, effectively severing ledger continuity prior to that date.
4. Event-Driven Recalculation: When an employee submits a time off request, Workday does not wait for a nightly batch job to validate balances. Balance checks and validation rules execute instantaneously in real time against the active ledger.