---
title: "Fix Workday Absence and Time Retro Recalculation — Kiweely"
description: "Why Workday stored absence balances and calculated time blocks stay unchanged after a retroactive Change Job event, and which recalculation tasks fix them."
url: https://kiweely.com/guides/workday-time-tracking-absence-retro-recalculation-errors
---

# Why Workday Absence Balances or Time Calculations Don’t Update After a Retro Job Change

Workday keeps prior stored absence balances when a retroactive job change precedes the last stored balance date, and it skips automatic time recalculations after eligibility changes. Run Recalculate Worker Time Off Balances and Run Time Calculations for a Date Range to update both.

-   **Checked** against Workday on November 13
-   Applies to **Workday Time and Absence**
-   7 min read
-   Published November 13
-   By Kiweely

Workday Absence and Time Tracking do not automatically recompute every historical period when you submit a retroactive **Change Job** event. Stored time off balances stay anchored to snapshots created after the retroactive effective date until you run **Recalculate Worker Time Off Balances**, and Time Tracking does not automatically rerun time calculations when worker eligibility changes for time calculation groups, time entry templates, time code groups, or period schedules until you execute **Run Time Calculations for a Date Range**.

## Quick Diagnostic: Which Retroactive Mechanism Blocked the Update?

Before editing accrual formulas or time calculation tags, match the symptom on the worker’s profile against the five underlying Workday behaviors below:

| Observed Symptom After Retro `Change Job` | Root Cause in Workday | Exact Task or Report to Fix / Verify |
| --- | --- | --- |
| Accrual rate changed retroactively (e.g., Feb 15), but current PTO balance still reflects the old rate | Balance was stored on a later date (e.g., Mar 1), and dynamic calculations start from the most recent stored snapshot |  **Recalculate Worker Time Off Balances** (`Start Date` on or before Feb 15) |
| Mid-period FTE or location change did not prorate the period’s accrual | Missing **Automated Accrual Adjustment** service step on `Change Job` or accrual lacks **Based on As of Date** | Edit `Change Job` BP definition and verify accrual on **Edit Accrual** |
| Approved time off on the calendar stays under an old ineligible plan or wrong absence tier | Absence table tiers and approved entries do not auto-reevaluate without explicit service steps or tasks |  **Reevaluate Absence Table Time Off Entries** or add **Remove Invalid Time Off Entries After Job Change** |
| Reported time blocks keep old tags (or lack overtime) after a retro pay rate or location change | Workday does not auto-run time calculations when Time Tracking eligibility changes, or the time period is locked | Open period if needed, then run **Run Time Calculations for a Date Range** |
| Worker transferred non-exempt to exempt midweek and lost Monday–Wednesday overtime | Tenant evaluates time calculation eligibility at week-end rather than day by day | Enable **Run Time Calculation Eligibility Day by Day** on **Edit Tenant Setup - HCM** or run **Adjust Calculated Time** |

## Why Stored Absence Balances Ignore Older Retroactive Job Changes

Workday calculates time off balances dynamically when a user opens the Absence calendar or runs a report, **starting from the most recent stored balance snapshot** rather than replaying the worker’s entire employment history from hire date. Most production tenants run **Schedule Time Off Calculated Balance Process** (typically with **Days Before Run Date** set to 91 days or more, plus Workday’s automatic fallback check on the third Sunday of every month) to persist balances and accruals for performance.

When HR enters a retroactive promotion, FTE change, or location transfer whose effective date is *earlier* than the worker’s last stored balance date, that stored snapshot acts like a wall:

text

```
Retro Change Job Effective Date:  2026-06-10  (FTE changed from 0.60 to 1.00)
Last Stored Balance Snapshot:     2026-07-01  (Stored before the retro event was entered)
Dynamic Balance Viewed Today:     Starts from 2026-07-01 -> misses June 10–30 accrual delta!
```

To force Workday to rebuild the stored snapshot and persist updated accruals:

1.  Verify you hold permission on the **Process: Calculated Balances (Run)** security domain in the **Time Off and Leave** functional area.
2.  Open the **Recalculate Worker Time Off Balances** task.
3.  Select only the affected worker(s) and affected Time Off Plan(s). Do **not** check **Run for All Workers** or **Run for All Time Off Plans** during business hours, as Workday warns both options degrade tenant performance.
4.  Enter a **Start Date** that is **on or before** the retroactive **Change Job** effective date (`2026-06-10` or earlier in the example above, and within 18 months of today for optimal performance).
5.  Run **All Calculated Balance Recalculation Changes** or **Calculated Balances for Organization (by Worker)** to confirm the delta between the previous balance and the new recalculated balance.

## Why Mid-Period Job Changes Miss Accrual Proration or Balance Transfers

If no stored balance exists after the retroactive date and the worker’s balance *still* fails to reflect the job change, check the **Change Job** business process definition and the Time Off Plan’s eligibility rules:

1.  **Test date-specific eligibility first:** Run the **Evaluate Absence Eligibility** report for the worker as of the retroactive job change date and as of the **Period Start Date** and **Period End Date**. If the plan is position-based and the worker holds multiple positions, specify the **Position** explicitly. Expand nested calculation folders in the output to see which boolean or lookup calculation returned false. (Remember not to use Payroll-only `Sub-Period Start Date` or `Sub-Period End Date` fields inside Absence calculations; Absence uses `Period Start Date` and `Period End Date`.)
2.  **Check `Change Job` absence steps:** A **Change Job** workflow only prorates, transfers, or cleans up absence records when its business process definition includes the corresponding steps:
    -   **Automated Accrual Adjustment** (service step): Required to prorate balances to the day when mid-period eligibility or FTE changes occur on accruals configured with **Based on As of Date** and an **Accrual Frequency Method** of `Start of Period` or `End of Period`. Check the **Automated Adjustments** tab on **Maintain Accrual and Time Off Adjustments/Overrides** to verify the line-item adjustment fired.
    -   **Maintain Time Off Plan Transfer Balance** (action step): Transfers balances when a worker moves between worker-based time off plans (for example, moving across regions). Note that Workday does not transfer negative balances or position-based plan balances.
    -   **Remove Invalid Time Off Entries After Job Change** (service step, placed *after* the completion step on **Change Job**): Automatically initiates **Correct Time Off** to zero out approved time off entries on or after the job change date that became ineligible or landed on non-working days after a schedule change. Keep in mind that rescinding or correcting a **Change Job** event later does *not* undo automatic corrections already processed by **Evaluate and Process Events Impacting Absence**.
3.  **Reevaluate Absence Tables if unpaid tiers triggered:** Workday does not automatically reevaluate absence table tiers after retroactive eligibility changes or accrual adjustments. Run **Reevaluate Absence Table Time Off Entries** for the worker from an as-of date on or before the job change so unpaid tier hours reallocate against newly accrued balances.

## Why Time Tracking Calculations Don’t Rerun Automatically After Eligibility Changes

In Workday Time Tracking, modifying a time block on the calendar triggers calculation rules, but **changing a worker’s job attributes does not**. Workday explicitly skips automatic time recalculation when worker eligibility changes for any of four components:

-   **Time Calculation Groups** (for example, moving into a union or California daily overtime group)
-   **Time Code Groups**
-   **Time Entry Templates**
-   **Time Period Schedules**

To recalculate historical reported time after a retroactive job change, run **Run Time Calculations for a Date Range** (secured to **Process: Run Time Calculations for a Date Range** in the **Time Tracking** functional area, plus access on the **Enter Time** business process security policy to select workers). Before clicking OK, watch out for four hard constraints:

Four Hard Rules on Manual Time Recalculations

1.  **Open periods only:** Workday calculates *only* open time periods inside your **Static Range**. If prior weeks are locked for payroll on the Time Period Schedule, clear those lock dates temporarily before running the calculation.
2.  **No terminated workers:** **Run Time Calculations for a Date Range** skips terminated workers completely, even if their termination date falls *after* the date range you selected.
3.  **Work schedule calendar changes:** Avoid spanning a single calculation run across a date range containing work schedule calendar changes; run separate subperiod ranges instead.
4.  **Resubmit modified time:** If recalculating alters hours or tags on already submitted time, that time must be resubmitted and approved before Workday Payroll will pull the change.

### Fixing the Midweek Transfer Trap (`Run Time Calculation Eligibility Day by Day`)

Suppose an hourly employee works 12 hours on Monday and 12 hours on Tuesday, then transfers retroactively on Wednesday into an exempt salaried job profile. In tenants using legacy weekly evaluation, a worker must meet the eligibility criteria for the overtime **Time Calculation Group** on the **last day of the week**. Because the worker is exempt on Sunday, Workday skips the overtime calculation for Monday and Tuesday entirely.

Check **Edit Tenant Setup - HCM** for the **Run Time Calculation Eligibility Day by Day** setting. When enabled, Workday evaluates worker eligibility and time calculation snapshots daily across the week rather than using end-of-week eligibility alone. You can test both states safely without changing tenant setup by running the **Time Calculation Debugger** report for that worker and toggling **Evaluate Time Calculation Eligibility Daily** to compare non-persisted results side by side.

## How to Verify Downstream Payroll Retro Pickup

Once Absence balances and Time Tracking blocks look right on the worker’s calendar, confirm the change reaches Payroll cleanly (see our [Workday Payroll parallel testing and retro audit guide](https://kiweely.com/guides/workday-payroll-parallel-testing-retro-audit) for full retro trace steps):

1.  Check **Payroll Status for Calculated Time Block** on the **Worker Time Block** business object. Any recalculated block that was previously paid must show `Modified After Paid`—and any pending time entry approval ([awaiting action on the Enter Time workflow](https://kiweely.com/guides/business-process-awaiting-action)) must be completed *before* retro runs, or Payroll can generate a negative retro clawback for the original paid block.
2.  Execute **Run the Retro Pay Calculation** prior to completing the next on-cycle payroll, then inspect the worker’s retro result lines to confirm the recalculated tags and absence adjustments flowed into gross-to-net pay.

Teams using [Kiweely Vine](https://kiweely.com/vine) can inspect live **Change Job** service steps, trace nested **Evaluate Absence Eligibility** [calculated fields and condition rules](https://kiweely.com/guides/condition-rule-not-working), and audit stored balance dates vs. time period lock schedules across a connected tenant before running targeted worker recalculations.

## Frequently asked questions

### Why didn't a retroactive promotion or FTE change update a worker's vacation balance?

If the retroactive Change Job effective date falls before the worker's most recent stored balance date from Schedule Time Off Calculated Balance Process, Workday continues calculating forward from the old stored snapshot until you run Recalculate Worker Time Off Balances with a Start Date on or before the job change.

### Why did a midweek transfer erase a worker's overtime hours in Workday Time Tracking?

Unless Run Time Calculation Eligibility Day by Day is enabled on Edit Tenant Setup - HCM, Workday evaluates time calculation group eligibility as of the last day of the week. Moving from non-exempt to exempt midweek makes the worker ineligible at week's end, so overtime does not calculate automatically.

### Does Run Time Calculations for a Date Range recalculate closed time periods or terminated workers?

No. Run Time Calculations for a Date Range processes only open time periods and skips terminated workers completely, even when their termination date is later than the selected calculation date range.

### How do I pass retroactively recalculated time blocks into Workday Payroll?

Ensure any modified submitted time is resubmitted and approved so the calculated time block status updates to Modified After Paid, then run the Run the Retro Pay Calculation task before completing the next on-cycle payroll.

## Sources checked

-   [Workday Admin Guide: Recalculate Balances for Workers](https://doc.workday.com/admin-guide/en-us/human-capital-management/absence/time-off/time-off-plan-balances/hel1439317148591.html)
-   [Workday Admin Guide: Manually Run Time Calculations](https://doc.workday.com/admin-guide/en-us/human-capital-management/time-tracking/time-calculations/hel1439248579156.html)
-   [Workday Admin Guide: Daily Evaluation of Worker Eligibility for Time Calculations](https://doc.workday.com/admin-guide/en-us/human-capital-management/time-tracking/time-calculations/time-tracking-calculation-concepts/concept--daily-evaluation-of-worker-eligibility-fo.html)
-   [Workday Admin Guide: Prorate Based-On-As-Of-Date Balances](https://doc.workday.com/admin-guide/en-us/human-capital-management/absence/time-off/time-off-plan-balances/yst1502486013940.html)
-   [Workday Admin Guide: Troubleshooting Time Off](https://doc.workday.com/admin-guide/en-us/human-capital-management/absence/time-off/troubleshooting-time-off/pqx1582120569337.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Workday Payroll Parallel Testing and Retro Calculation Audits in Sandbox Validate Workday Payroll configuration changes, tax updates, and semi-annual releases in a Sandbox or Implementation tenant by running Run Retro Pay Calculation, Run Pay Calculation, and Run Payroll Audit to compare gross-to-net, earnings, deductions, and retro differences.](https://kiweely.com/guides/workday-payroll-parallel-testing-retro-audit)
-   [### Workday Calculated Fields: How to Build Them and Fix Common Errors Choose the business object and scope, configure three core functions, and fix missing fields, empty results and incorrect conditions. Examples use Workday’s documented fields and options.](https://kiweely.com/guides/workday-calculated-fields)
-   [### Workday Awaiting Action: who is the step waiting on, and how do you move it? Awaiting Action means a step is waiting for someone to act, and a day or more is normal. Open Business Process > Full Process Record to see who, then have them finish it in My Tasks, or reassign, delegate or manually advance the step.](https://kiweely.com/guides/business-process-awaiting-action)
-   [### My Workday business process condition rule is not working and the step did not fire: how to troubleshoot it Work through nine checks in order: the condition’s type and polarity, which definition ran, its effective date, the Rule Tester, the field values at that moment, rule logic, how the event started, step security, and parallel step order.](https://kiweely.com/guides/condition-rule-not-working)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Troubleshooting Workday Compensation Cycle Eligibility, Proration, and Bonus Rounding Mismatches](https://kiweely.com/guides/workday-advanced-compensation-eligibility-bonus-rounding-errors)
-   [How to Fix Workday ACA 1095-C Code 2C Mismatches and Update Annual Affordability Thresholds](https://kiweely.com/guides/workday-aca-1095c-errors-affordability-setup)
-   [How to Reopen Workday Open Enrollment for One Employee After the Window Closes](https://kiweely.com/guides/workday-reopen-open-enrollment-single-worker)
-   [Why is a worker’s Workday Open Enrollment On Hold or missing after a backdated change?](https://kiweely.com/guides/workday-open-enrollment-stuck-disappeared-elections)
-   [How to Configure or Opt Out of the Modernized Workday Worker Profile and Private Tab](https://kiweely.com/guides/workday-worker-profile-header-private-public-tabs)
-   [How Future-Dated Dependents and ‘View Dependent As Of’ Work in Workday Benefits](https://kiweely.com/guides/workday-dependent-effective-dating-future-dependents)
-   [How Workday Data Cloud Zero-Copy Sharing Works with Snowflake, Databricks, and BigQuery](https://kiweely.com/guides/workday-data-cloud-zero-copy-snowflake-databricks)
-   [Workday Platform Consumption Console: what each page shows, when usage updates and what the alerts do](https://kiweely.com/guides/workday-platform-consumption-console)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [Personal vs Firm-Managed AI for Workday: A Client RFP Answer Template](https://kiweely.com/blog/personal-vs-firm-managed-ai-workday-rfp-template)
-   [Codex with wdcli: Validate, Deploy, and Stop at Development](https://kiweely.com/blog/codex-with-wdcli-stop-at-development)
-   [Pricing Workday Delivery When AI Cuts Build Time but Not Approval Time](https://kiweely.com/blog/pricing-workday-delivery-when-ai-cuts-build-time)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
