Leave Results for Worker displays leave results for a specific employee as of a selected date. It includes each leave type taken during the applicable balance period, the leave calendar period, units taken, the remaining entitlement balance, and details of individual leave requests. Both in-progress and completed leave events can be included.

Time Off Results Summary reports high-level time off plan balances and results for selected organizations and periods. It does not provide the worker-specific leave entitlement and leave-request detail required here. View Time Off Balance reports time off plan information such as carryover, year-to-date accruals, paid time off, and remaining time off balances; it does not report leave type entitlement results. Manage Absence Cases is used to administer absence cases and associated reintegration activities, not to review leave balances.

The report’s as-of date determines the applicable leave balance period and the leave activity included in the results. This is important for leave types using rolling calendars or other configurable balance-calendar definitions. Appropriate leave-of-absence security is required to view the worker’s results.

Study Guide reference: Absence Management Reports, Dashboards, and Calendars – Leave of Absence Reports .

The Entry Option is configured on the time off component, not on the time off plan. Selecting Enter through Workday Time Tracking or Time Off permits eligible workers to enter the absence through either Time Tracking or the Workday Absence calendar and related time off tasks.

Because the change must begin on January 1 of the next year, the administrator should create a new effective-dated snapshot of the time off with January 1 as its effective date. This preserves the current entry behavior through December 31 and introduces the new configuration prospectively. Updating the initial snapshot would rewrite the component’s earlier configuration and could affect historical or current-period behavior, which is inappropriate for a planned future rollout.

Workday treats the time off, accrual, and time off plan as effective-dated absence setup components. However, their configuration responsibilities differ. The plan defines items such as the period schedule, unit of time, limits, accrual frequency, and balances. The individual time off defines how users may enter requests. Therefore, options A and C target the wrong component, while option B targets the correct component but applies the wrong effective-dating method. Option D preserves configuration history and activates the correct entry channel on the required date.

Scheduling: Payment Date Month = 01 (January) restricts normal annual processing to the January period. For workers who are already eligible, this scheduling rule causes the accrual to process on the January payment date, supporting the requirement to award the full-year entitlement at the beginning of each calendar year.

Scheduling: Worker Hired Mid-Period serves a different part of the design. It identifies workers hired after the January processing event so they can receive a prorated award on hire. Scheduling: Last Period of the Balance Period would process the accrual at the end of the year and is inconsistent with a January 1 award. Scheduling: Front-Loaded indicates that the accrual is granted in advance but does not, by itself, identify January as the processing month.

The annual January condition and mid-period-hire condition can be configured on separate scheduling rows. Workday applies OR logic between separate rows, enabling the accrual to process either during January for existing eligible workers or upon a qualifying mid-period hire. The accrual’s amount calculation determines whether the worker receives the full or prorated entitlement.

Study Guide reference: Calculations for Time Off Plans – Using Calculations for Scheduling Rules .

A balance-tracking leave type requires the ordinary leave request configuration plus the elements necessary to calculate an entitlement balance. The leave family organizes the leave type for user selection. On Leave status visibility controls who can see that the worker is on leave, while the eligible worker type establishes whether the leave applies to employees, contingent workers, or both.

Track Balance must be enabled. Calculated fields define the balance-calendar start and end dates, establishing the period over which Workday calculates entitlement minus leave taken. The unit of time ensures that entitlement and leave usage are consistently expressed in hours or days. Calendar Display determines whether entitlement information appears in the Absence Calendar or Time Off and Leave Calendar. Leave entitlement defines the maximum available units, and Days to Include determines which requested dates or hours reduce the balance.

Period schedules, accrual frequency, upper and lower limits, and carryover rules are time off plan mechanics. Payroll, benefit, and stock effects are optional cross-functional settings, not a complete required configuration. Option A contains the full required set identified by Workday.

Supporting Data displays contextual information that helps a worker understand the effect of a leave request. The administrator can configure calculated fields or Workday-delivered report fields to show the worker’s available leave entitlement, the amount consumed by the current request, and the projected entitlement balance if the request is approved.

Supporting data is configured on the Validations/Supporting Data tab of the leave type. By default, Workday uses the report or calculated field name as the displayed label, although the administrator can provide a Label Override to make the information clearer. Supporting data can also help approvers interpret warnings or determine whether a request should be approved or rejected.

Eligibility Criteria determines whether the leave type is available to the worker and does not present projected balance information. Leave Reasons capture the reason for the absence, such as illness or family care. Cascading Leave defines a sequence in which one leave type follows another. None of these options provides the required entitlement details during the request. Supporting Data is therefore the correct configuration for presenting current and projected leave-balance information to the requester.

The Leave Payment Type field is configured when the applicable country-specific Workday Payroll product is in scope. It connects the tenanted Absence leave type with the Workday-delivered statutory payment or earning configuration used by payroll. This relationship enables Workday Payroll to process the leave according to the statutory rules for the relevant country and leave category.

The field is therefore relevant when Workday Payroll for Australia, the United Kingdom, or France is implemented and the leave type is associated with a supported statutory leave. Absence and payroll administrators must coordinate the leave type, statutory payment classification, payroll earning, and related payroll-processing rules so that approved leave produces the intended payment outcome.

When Workday Payroll for the applicable country is not in scope, the Workday-delivered payroll relationship is not used by the tenant’s payroll processing. Configuring the field would not provide the required external-payroll integration by itself. The United States options are also incorrect because the scenario explicitly concerns statutory leave configurations for Australia, the United Kingdom, or France. The determining factor is whether the corresponding Workday Payroll country product participates in processing the statutory leave.

Cascading leave configuration defines the sequence in which one leave type transitions to another. The Long Term Disability Leave Type must therefore be selected in the Next Leave Type field on the Cascading Leave tab of the Short Term Disability Leave Type. This establishes Long Term Disability as the successor when the short-term leave reaches its configured end.

Adding the leave types to the same absence type group only organizes them in the absence-selection interface. A leave family categorizes related leave types but does not create an automated transition. The Additional Leave Types field coordinates leave-taken calculations so that one leave can reduce another leave’s entitlement; it does not define which leave should start after the current leave ends.

The succeeding leave remains subject to its eligibility rules. When automated processing reaches the transition date, Workday can generate a return request for Short Term Disability and a new request for Long Term Disability. The Request Leave of Absence business process must also include the Automated Leave Processing service, normally with a step delay that determines when the transition is evaluated.

Study Guide reference: Absence Management Business Processes – Cascading Leaves .

The Include all Leave Types from Leave Family setting causes units taken for other leave types in the same family to count as leave taken against the current leave type’s entitlement balance. Because the requirement is reciprocal—usage of any one leave must reduce all three balances—the setting must be selected on each of the three leave types.

For example, if Leave A, Leave B, and Leave C share a family and a worker takes five days of Leave A, Workday must count those five days against the entitlement balances of A, B, and C. Selecting the setting only on Leave A would make Leave B and Leave C count against A, but it would not automatically cause an event for Leave A to reduce the other balances. Coordinated relationships must be configured from the perspective of every balance that should be reduced.

The leave types must use compatible units of time for family-level coordination. Intermittent Time Offs links a time off with a leave type; it does not coordinate multiple leave types. An absence table defines a selectable absence construct and does not establish shared entitlement deductions. Applying the family coordination option to all three leave types creates the required concurrent reduction behavior.

Workday Absence, Payroll, and Time Tracking can share the same period schedule when the schedule’s frequency and period dates satisfy each application’s requirements. The Usage field identifies which Workday applications are permitted to use that schedule. Therefore, the administrator should edit the existing schedule and add Absence to the Usage field.

Creating a duplicate schedule is unnecessary and introduces avoidable maintenance risk. Two schedules containing equivalent periods can diverge when future periods, lock dates, or application-specific configuration are updated independently. Reusing the existing schedule maintains a consistent period framework across Time Tracking and Absence.

Eligibility configuration determines which workers are assigned or eligible for a schedule within an application; it does not make a Time Tracking schedule available to Absence. Adding Absence-related criteria to a Time Tracking eligibility rule also mixes application responsibilities and fails to update the schedule’s declared usage. Likewise, simply adding an Absence eligibility rule without enabling Absence in the Usage field does not establish the required application association. Once Absence is added to Usage, the administrator can select the schedule on the new time off plan and configure any appropriate Absence eligibility separately.

A leave type is the central configuration object governing a specific form of leave of absence. It defines the rules that apply when a worker requests or is placed on personal leave, bereavement leave, short-term disability, parental leave, or another extended absence.

The configuration identifies the associated leave family, the unit of time used for the request, eligible worker populations, additional eligibility criteria, validation rules, entitlement structure, and whether Workday tracks an entitlement balance. It can also control the On Leave status visibility, calendar display, Days to Include calculation, payroll effect, benefit effect, accrual effect, and other cross-functional consequences. For balance-tracking leave types, the definition additionally includes balance-calendar dates and entitlement calculations.

A period schedule belongs to time off plan configuration rather than leave type configuration. Supervisory organization membership is determined through HCM organization and staffing structures, while payroll calendars and pay-period processing belong to Payroll. Therefore, the leave type’s defining function is to assemble the policy, eligibility, validation, entitlement, visibility, and processing rules for one specific category of leave.