Workday Absence Management calculates a worker’s future time-off balance dynamically—not from a static counter—by starting from the worker’s most recent stored balance snapshot and stepping forward period by period to the requested As Of Date. Along the way, the calculation engine evaluates period accruals, carryover forfeitures at balance period boundaries, upper accrual caps, lower balance limits, and every Approved or Pending time-off request through that date.
When an employee sees a different number on Absence Balance (or Time Off Balance) than they expected on a future holiday date, the discrepancy almost always traces back to period boundary timing, unapproved requests in the queue, or a stale stored balance snapshot.
The Projected Balance Formula in Workday UI
On a time-off plan configured with Track Balance enabled (Create Time Off Plan / Edit Time Off Plan), Workday renders the Projected Balances grid during Request Time Off, Revise Time Off, and Review Time Off Corrections tasks:
$$\text{Available} = \text{Accrued (through As Of Date)} - (\text{Approved Requests} + \text{Pending Requests})$$
$$\text{Remaining} = \max(\text{Available} - \text{Paid Units in Current Request},\ \text{Time Off Lower Limit})$$
Four rules govern how Workday populates the Projected Balances columns:
- Saved for Later Excluded: Requests in
Saved for Laterstatus do not deduct fromAvailable. As soon as a worker clicks Submit, the pending event immediately reducesAvailablefor any future As Of Date on or after that request. - Lower Limit Floor on Remaining: If
Time Off Lower Limitis0andUnpaid Time Allowed?isYes, a worker with6available hours who requests8hours seesRemaining: 0and (for reviewers)Unpaid: 2. IfTime Off Lower Limitis-4, requesting8hours against a6-hour balance yieldsRemaining: -2andUnpaid: 0. - Corrections Show the Delta: When a worker corrects an already approved request from
4hours to6hours,Availablealready reflects the approved4hours, andRequesteddisplays+2(or-2when reducing from6to4). - Termination Adjustments Included: If an active future-dated termination exists for the worker and termination adjustments are enabled on the plan, projections on or after the termination date reflect those adjustments.
How Period Timing, Carryover, and Caps Change Future Numbers
Workday does not simply multiply a monthly rate by the number of months until the future date. It simulates every absence period along the plan’s Period Schedule and Balance Period in strict chronological sequence.
| Configuration Setting | Task / Location | Effect on Future Projected Balance |
|---|---|---|
| Configuration SettingAccrual Frequency Method: Start of Period | Task / LocationEdit Time Off Plan or Edit Accrual |
Effect on Future Projected BalanceAdds the period’s accrual first, enforces the Upper Limit (forfeiting excess hours immediately), then deducts time off taken during that period, and finally checks the Lower Limit. |
| Configuration SettingAccrual Frequency Method: End of Period | Task / LocationEdit Time Off Plan or Edit Accrual |
Effect on Future Projected BalanceDeducts time off taken during the period first, checks the Lower Limit (potentially forcing unpaid hours mid-period), then adds the period’s accrual at the period end date, and checks the Upper Limit. |
| Configuration SettingSame-Day Processing Order | Task / LocationEngine rule on identical date | Effect on Future Projected BalanceWhen carryover, an accrual, and a time-off entry fall on the exact same calendar date, Workday processes Carryover first, Accrual second, and Time Off deduction third. |
| Configuration SettingAccrual Priority & Time Off Priority | Task / LocationCalculation tab on Edit Time Off Plan |
Effect on Future Projected BalanceLower priority numbers run first (Priority = 1 before Priority = 2). When two accruals share a plan cap of 120 hours, Priority 1 fills the cap first and Priority 2 forfeits the overflow. |
| Configuration SettingCarryover Limit at Balance Period Boundary | Task / LocationBalance tab -> Carryover section on Edit Time Off Plan |
Effect on Future Projected BalanceWhen a future projection crosses into a new Balance Period (for example, January 1 on a calendar-year plan), Workday caps the carried-over balance at the configured constant or conditional calculation (such as 80 hours, or 120 hours for California workers) before adding new-year accruals. |
| Configuration SettingAccrual Expiration | Task / LocationConcept: Accrual Expiration / Override Accrual Expiration |
Effect on Future Projected BalanceGrants or carryover balances with an expiration rule drop out of Available on dates after their expiration boundary. |
Worked Example: Start of Period vs. End of Period Near an Upper Cap
Suppose a Vacation plan has an Upper Limit of 120 hours, accrues 12 hours per month, and a worker starts the month at 110 hours while taking 8 hours of vacation mid-month:
- Start of Period: Workday adds
12hours on day 1 (110 + 12 = 122), trims2hours at the120upper cap, and subtracts the8vacation hours, leaving a projected end-of-month balance of112hours. - End of Period: Workday subtracts the
8vacation hours first (110 - 8 = 102), adds12hours on the period end date (102 + 12 = 114), checks the120cap (no forfeiture), and leaves114hours. - Querying Mid-Month: If the worker checks their balance As Of the 15th of that month on an End of Period plan, the current month’s
12-hour accrual has not posted yet—it only appears when the As Of Date reaches or passes the period end date.
Stored Balances vs. Retroactive Changes
To prevent timeouts when projecting years of period history, Workday caches checkpoints using the Schedule Time Off Calculated Balance Process task (plus an automatic background fallback on the third Sunday of every month at 01:00 local time for plans whose last stored date is more than 13 months old).
When diagnosing an unexpected future balance, check whether a retroactive change occurred before the worker’s last stored balance date:
- Retroactive Time-Off Requests or Corrections: Workday automatically accounts for retroactive absence events even if they fall before the last stored balance date.
- Retroactive Job Changes or Plan/Accrual Edits: Workday does not automatically invalidate balances stored after a retroactive FTE change, work-state transfer, or accrual-rate edit. You must run Remove Stored Balances or Recalculate Balances for Workers starting from a date earlier than the retroactive effective date.
To inspect period-by-period math directly in the UI, open the worker’s profile and select Related Actions -> Time and Absence -> View Time Off Results by Period. Inspect the closing balance of the last period of the current year alongside the opening period of the next year to see exact carryover and forfeiture figures.
Reading Future Projected Balances via Workday APIs
Integrations, custom employee screens, and AI assistants have three supported paths to read time-off balances, but they differ in how they accept an effective future date.
1. Absence Management REST API (absenceManagement/v5)
GET /balances is the cleanest REST endpoint for projected worker balances because it accepts both worker (required) and effective (yyyy-mm-dd) query parameters, and enforces contextual worker security (Self-Service: Time Off Balances, Self-Service: Leave of Absence Entitlements, or manager/admin Worker Data: Time Off domains):
GET /ccx/api/absenceManagement/v5/{tenant}/balances?worker=3aa5550b7fe348b98d7b5741afc65534&effective=2027-07-15&category=7bd6531c90c100016d4b06f2b8a07ce
Accept: application/jsonKey parameter behavior on GET /balances:
worker: Workday ID (WID) of the worker.effective: Target projection date inyyyy-mm-ddformat (for example,2027-07-15). Workday runs the absence calculation engine through that date and returns dynamic balances per eligible plan.category: Optional WID filter restricting results to Time Off (7bd6531c90c100016d4b06f2b8a07ce), Leave of Absence Type (17bd6531c90c100016d74f8dfae007d0), or Absence Table (17bd6531c90c100016da3f5b554007d2).
To pair the projected balance with the individual approved or pending dates subtracting from it, call GET /workers/{ID}/timeOffDetails?fromDate=2026-11-15&toDate=2027-07-15.
2. Custom RaaS Report with Effective Date Prompt
If your organization needs custom columns—such as Accrued YTD, Carryover Remaining, Pending Units, and Projected Ending Balance side by side—build a custom report on a time-off balance data source (such as timeOffPlanCalculatedAndOverrideBalancesForWorker or calculatedBalancesForOrganizationByWorker), expose the report’s Effective Date prompt, and enable Enable as Web Service. Pass the future date to the RaaS JSON endpoint under the caller’s OAuth session.
3. SOAP Get_Time_Off_Plan_Balances (Absence_Management)
The Get_Time_Off_Plan_Balances SOAP operation retrieves dynamic Time Off Plan Balances by Employee_Reference, Time_Off_Plan_Reference, or Organization_Reference with Contextual Security: Yes. Use Response_Filter (As_Of_Effective_Date) when querying balance state as of a target date from SOAP-based integrations.
Diagnostic Checklist for Mismatched Future Balances
- Check Pending Events: Open the worker’s Absence Requests (or Time Off and Leave Requests) tab and filter for
Submitted/In Progressrequests between today and the target date. - Verify Period End Date vs. Target Date: Confirm on
Edit Time Off Planwhether the accrual posts atStart of PeriodorEnd of Period. Asking for a balance as of August 14 on a semi-monthlyEnd of Periodschedule excludes the August 15 accrual. - Check Year-End Carryover Boundary: If the target date crosses into the next Balance Period, inspect
View Time Off Results by Periodacross the boundary period to verify how much unused balance forfeited at midnight. - Check Hours-Worked Accruals: Plans whose accrual calculation sums
Payroll Hours Related Result Lines for Periodaccrue zero hours in future uncalculated pay periods because future payroll results do not exist yet—only scheduled fixed/rate accruals project automatically into future periods. - Check Stored Balance Snapshots: Run
View Schedules for Time Off Calculated Balance Processand recalculate the worker’s balances if a retroactive FTE or eligibility edit predates the last stored snapshot.
When employees ask “How many vacation hours will I have on July 15 if I take three days in March?”, tools like Kiweely Bridge and custom absence screens built on Kiweely Leaf (both coming next) pass the exact future effective date to Workday live under the employee’s own Self-Service: Time Off Balances permission rather than estimating accrual math outside the tenant.
Frequently asked questions
Does Workday include pending unapproved time-off requests in future balance projections?
Yes. Workday calculates Available time off as Accrued time minus both Approved and Pending time-off requests up to and including the target date. Requests with a status of Saved for Later are excluded.
Why does changing Accrual Frequency Method from Start of Period to End of Period change a worker's projected balance?
Start of Period adds the period accrual and applies the upper accrual cap before subtracting time off taken in that period, whereas End of Period deducts time off and checks the lower limit before adding the period accrual.
Why did a retroactive accrual rate change not update a worker's projected balance?
Workday does not automatically recalculate stored balances when job or plan configuration changes take effect before the worker's last stored balance date. Run Remove Stored Balances or Recalculate Balances for Workers from a date prior to the change.
Which REST API parameter returns a worker's projected absence balance for a future date?
Pass the future date in yyyy-mm-dd format to the effective query parameter on GET /balances in the absenceManagement/v5 REST API along with the required worker Workday ID.