Balance tracking is a foundational and non-editable characteristic of a time off plan after the plan is saved. Workday specifically identifies Track Balance, Period Schedule, and Unit of Time as fields that cannot be changed after creating and saving the plan. Consequently, an administrator cannot convert the existing plan into a non-balance-tracking plan by clearing either the Track Balance setting or its balance period.

A balance-tracking plan contains architecture that is not present in a basic plan, including a balance period, accrual calculations, carryover behavior, upper and lower limits, balance visibility, and accrual and time-off balance processing. Removing only the balance period would leave the plan configuration internally inconsistent. Adding another accrual would further reinforce balance tracking rather than remove it.

The correct remediation is to remove the incorrectly configured plan and create a new basic time off plan without balance tracking. Before deletion, the administrator should confirm that no production time off requests, accrual results, adjustments, or other transactions depend on the plan. If operational data already exists, the replacement requires controlled migration and effective-dated planning rather than an immediate deletion. Within the stated scenario, deletion and recreation is the valid configuration response.

The Accrual and Time Off Adjustments/Overrides by Batch ID report is specifically designed to review adjustment and override records associated with a particular import batch. Put Absence Input assigns or carries a batch identifier that enables administrators to isolate the records created by that EIB load.

The report displays batch totals for each affected accrual or time off and provides employee-level adjustment or override data by processing period. This supports reconciliation of the expected record count, worker population, accrual component, effective period, and imported values. It can include transactions for plans with or without balance tracking.

View Time Off Balance displays calculated plan balances but does not isolate the imported accrual override records by batch. Leave Results for Worker reports leave entitlement and leave-request information. All Worker Time Off reports time off requests and statuses rather than accrual input transactions.

Administrators should compare the report totals against the EIB source file and investigate rejected, duplicated, or incorrectly effective-dated records. The batch-specific report provides a more reliable audit trail than reviewing workers’ resulting balances individually.

Study Guide reference: Absence Management Reports, Dashboards, and Calendars – Accrual and Time Off Adjustments/Overrides by Batch ID .

Leave Type Segmented Security controls which specific leave types a security role can access when placing a worker on leave. Although the worker satisfies the leave type’s eligibility criteria, the leave will not appear for the manager unless it belongs to a Leave Type Security Segment accessible through the manager’s segment-based security group.

The Request Leave of Absence business process security policy determines whether a manager can initiate leave requests generally. If that initiation security were missing, the manager would be unable to initiate the business process, rather than simply being unable to see one newly created leave type. Opting in to segmented security does not automatically assign new leave types to existing segments. New leave types must be added to the appropriate security segment deliberately.

The administrator should add the new leave type to the manager’s Leave Type Security Segment, confirm that the Manager role is included in the associated segment-based security group, and verify access to the Leave Type Segmented Setup domain. Pending security policy changes must also be activated where applicable.

Study Guide reference: Leave of Absence – Leave Type Segment Security .

A time off plan’s Upper Limit specifies the maximum number of hours or days that a worker can accumulate in the plan balance. Setting the upper limit to 200 hours instructs Workday to compare the worker’s calculated balance with that ceiling during accrual processing. When a calculated accrual would raise the balance above 200 hours, Workday reduces the accrual by the excess amount. The excluded amount is reported as forfeited accrual.

For example, if a worker has 195 hours and is scheduled to accrue 12 hours, the preliminary balance is 207 hours. Workday applies the 200-hour upper limit and reduces the accrual by seven hours. The worker receives five hours, producing a final balance of 200 hours.

A Carryover Limit applies only when balances move from one balance period to the next; it does not prevent the balance from exceeding a threshold during the current period. Maximum Unpaid Time Off Units Allowed validates requests that exceed the available paid balance and is unrelated to accumulation. A Lower Limit controls how far a balance may be reduced before requested time becomes unpaid. Consequently, only the Upper Limit directly enforces the maximum accumulated plan balance.

The time off plan must specify a time off in the Time Off for Termination Adjustment field. This configuration tells Workday which time off component to use when generating the adjustment that removes the worker’s entire remaining balance during termination processing.

When the Adjust Time Off Balances service step runs in the Termination business process, Workday evaluates the eligible plan, determines the remaining balance, and creates a termination adjustment using the designated time off. The adjustment reduces the plan balance to zero. Where payroll integration or Workday Payroll calculations are appropriately configured, that adjustment can support payment of the outstanding amount.

A payout accrual is not required because an accrual ordinarily adds units to a time off plan; it does not remove and pay the existing termination balance. Accrual Frequency Method controls whether ordinary accrual processing occurs at the start or end of a processing period and does not establish termination payout behavior. Time Off Forfeiture Adjustment is used when a balance is being forfeited under plan rules, not when the organization intends to pay the balance upon termination.

Study Guide reference: Absence Management Business Processes – Automating Payout of Plan Balance upon Termination , particularly the time off plan’s termination-adjustment configuration.

Maintain Accrual and Time Off Limit Overrides allows an administrator to suspend the accrual’s upper limit for a defined period. The worker’s accrual is being forfeited specifically because the plan balance has reached the 120-hour limit. Suspending that limit enables the normal five-hour accrual to continue processing even while the worker’s balance exceeds 120 hours.

Maintain Accrual and Time Off Adjustments/Overrides changes the accrual result for selected periods but does not remove the upper-limit restriction. Even an accrual adjustment or override can be reduced or eliminated when the upper limit is applied. Maintain Time Off Plan Override Balances replaces the calculated plan balance as of a particular period start date; it does not authorize future accruals above the plan limit. Maintain Time Off Plan Carryover Overrides controls carryover amounts and expiration dates between balance periods.

The administrator should define the exact periods during which the limit suspension applies. The worker continues receiving the plan’s standard accrual while the override is effective. When the limit override ends, the standard 120-hour ceiling becomes applicable again, and later accruals may be reduced or forfeited depending on the worker’s balance.

Study Guide reference: Absence Management Administration – Maintain Accrual and Time Off Limit Overrides .

The Put Override Balance EIB performs mass time off plan balance overrides. It is appropriate because 200 acquired workers require the same type of beginning-balance conversion. Each worker’s eligible plan balance can be established at 40 hours as of the applicable period start date, after which Workday uses that amount as the starting point for subsequent accrual and time off calculations.

Import Request Leave of Absence loads leave-of-absence events and does not establish time off plan balances. Adjust Time Off creates mass time off adjustment or correction transactions; it is not the delivered EIB for setting the authoritative opening balance. Enter Time Off loads time off requests through the Request Time Off business process and would reduce balances instead of establishing them.

The effective date must align with the start of a period for which each worker is eligible. Administrators must also understand that an override replaces the calculated balance at that point. Workday does not recalculate the overridden balance for the override date or earlier dates when retroactive activity is subsequently entered. Data validation should therefore confirm worker eligibility, plan, unit of time, effective date, and the 40-hour value before loading.

Study Guide reference: Absence Management Administration – Maintain Time Off Plan Carryover and Balances for Employees .

Years of service resolves as a numeric calculation, so the appropriate table is Advanced Lookup Table – Numeric Calculation Search Criteria . The lookup table uses the calculated years-of-service value to locate the applicable range and return the corresponding accrual amount. For example, the table might return three hours for one through five years, five hours for six through ten years, and eight hours for service greater than ten years.

Advanced Lookup Table – Report Field Search Criteria is used when the search value comes directly from a single-instance or multi-instance report field, such as Job Profile. Text Report Field Search Criteria applies when the source is a text field, such as a city name. No Search Criteria provides only a default value and cannot differentiate results according to service bands.

The numeric table should define complete, non-overlapping service ranges and include a suitable response for every expected value. The resulting lookup calculation can then be selected as the accrual amount. Effective dating can be used when service-based accrual rates change over time without requiring the entire accrual configuration to be rebuilt.

Study Guide reference: Calculations for Time Off Plans – Advanced Lookup Tables in Lookup Calculations .

The five-year service requirement determines whether a worker is eligible to use the Sabbatical Leave type. Therefore, the leave of absence rule must be placed in the additional eligibility criteria on the leave type . Workday evaluates this criteria when determining which leave types are available to the worker. If the worker does not satisfy the rule, Sabbatical Leave is excluded from the worker’s selectable leave options.

Validation criteria operate later in the transaction lifecycle. They evaluate whether an entered leave request is valid, typically when the request is submitted or saved for later. A validation may generate an error or warning, but it is not the appropriate configuration when the requirement is to prevent the leave type from appearing initially. A leave family groups related leave types and supports shared processing, but it does not replace leave-type eligibility for a requirement specific to Sabbatical Leave. An eligibility override would also be inappropriate because the requirement establishes standard eligibility rather than an exception to it.

Study Guide reference: Leave of Absence – Leave-Type Eligibility and Additional Criteria . The relevant distinction is between eligibility rules controlling availability and validation rules controlling transaction acceptance.

The Allow Override for Entry On Behalf Of Worker checkbox permits authorized managers and administrators to override a time off validation when entering, revising, or correcting time off for an employee. The users must belong to security groups authorized for the applicable “enter on behalf of worker” action in the relevant Absence business process security policy.

The eight-hour restriction should remain a hard validation for employees. When an employee attempts to exceed the configured maximum, Workday prevents submission. When an authorized manager or administrator enters the request on the employee’s behalf, Workday displays a warning identifying the validation failure but permits the authorized user to continue. This supports exceptional cases without weakening the general employee restriction.

Clearing Do Not Allow Request would convert the validation into a warning for employees as well, allowing them to submit requests above eight hours. Segmented security controls access to particular time offs; it does not grant permission to disregard a quantity validation. A time off plan eligibility override determines which workers qualify for the time off and has no effect on the maximum daily request. The administrative-override checkbox is therefore the targeted control for the stated exception.