---
title: "Fix Workday Local Time Zone Report & Integration Shifts"
description: "Why Workday scheduled reports, ISU audiences, and Core Connectors drop or shift rows after local time zone changes, and how to fix effective moments and…"
url: https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts
---

# Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing

Scheduled reports and integrations drop or shift records when tenant and location time zones differ from Integration System User defaults in Pacific Time. Fix date mismatches with Today (Tenant) filters, Indexed All Workers, and explicit effective moment settings.

-   **Checked** against Workday on November 13
-   Applies to **Workday Tenant Administration**
-   7 min read
-   Published November 13
-   By Kiweely

Workday scheduled reports and outbound integrations shift dates or drop same-day transactions when worker locations and tenant settings evaluate effective dates in local time while an Integration System User (ISU), report filter, or organization hierarchy still evaluates in Pacific Time. You resolve the discrepancy by replacing user-relative `Today` filters with **Today (Tenant)**, selecting **Indexed All Workers** where audience timing matters, checking **Preserve Local Time** on sub-daily schedules, and choosing deliberately whether custom reports evaluate effective moments in local time or Pacific Time.

## How Does Workday Resolve Time Zones Across Tenant, Location, and User Levels?

Workday resolves local time zones through a three-tier hierarchy secured to the **Set Up: System** domain in the System functional area. Every blank level falls back to the level above it, and an unconfigured tenant defaults universally to Pacific Standard Time (PST):

1.  **Tenant level (`Edit Tenant Setup - System`):** The **Default Timezone** prompt defines the baseline calendar clock for daily scheduled jobs and tenant-wide date expressions. Use **Configure Preferred Time Zones** to expose specific IANA time zones in prompts across the tenant.
2.  **Location level (`Maintain Location Time Zones`):** Individual business sites inherit the tenant default unless you assign a location-specific IANA time zone.
3.  **User level (`Edit Worker Time Zone`):** Active workers inherit the time zone of their primary position’s business site. System accounts and workers without a position inherit the tenant default—or PST if no default is set or if a service runs under a fixed Pacific Time system account.

One-Way Role Assignment Setting

On **Edit Tenant Setup - System**, the **Role Assignment Time Zone Option** prompt (**Tenant Default** or **Assignee Location**) is irreversible once saved. After you move that field from blank to either option, Workday does not allow you to clear it back to blank, so test role-based routing impacts in Preview before changing Production.

| Workday Component | Time Zone Used for Evaluation | Common Post-Change Symptom | Task or Setting to Check |
| --- | --- | --- | --- |
| Custom report run by an ISU or Engagement Builder | Processing user’s time zone (often PST for system accounts) | Morning runs in Europe or Asia miss workers hired today |  **Edit Custom Report** > Filter tab (`Today (Tenant)`) and Data Source (`Indexed All Workers`) |
| Custom report effective moment | Local effective date by default; optional PST override | Row counts differ between an admin in New York and an admin in Singapore |  **Edit Custom Report** > Prompts tab (**Use Pacific Time Zone for Effective Moment**) |
| Daily, weekly, or monthly scheduled processes | Tenant local calendar time | Job fires several hours earlier or later after changing **Default Timezone** |  **Scheduled Future Processes** > **Scheduled Future Process > Edit** |
| Hourly or multi-hour scheduled processes | Fixed elapsed interval since prior run | Wall-clock run times drift by 1 hour across Daylight Saving Time |  **Preserve Local Time** check box on the schedule definition |
| Supervisory vs. financial org hierarchies | Supervisory orgs use `00:00` Tenant Default; Cost Centers and Companies use `00:00` PST | Reorg shows new manager at midnight local time, but old Cost Center rollup until `00:00` PST | Separate effective-date validation for financial vs. supervisory rollups |

## Why Do Scheduled Custom Reports and Audiences Drop Same-Day Hires?

Workday records and evaluates effective and entry dates relative to the processing user’s time zone. When an HR Partner in Tokyo (`UTC+9`) views an organization’s **Members** tab or the **All Jobs** report at `09:00` JST on October 1, Workday evaluates October 1 in JST and includes workers hired that morning. When a background job or Engagement Builder ISU runs in Pacific Time (`UTC-7` during PDT), the system clock for that ISU is still `17:00` on September 30. Any report filter comparing `Hire Date` to the runner’s `Today` evaluates against September 30 and drops every October 1 hire. This is one of the most frequent causes of [a Workday custom report returning no rows](https://kiweely.com/guides/workday-report-no-rows) on scheduled morning deliveries.

Two changes fix this mismatch in the Report Writer:

1.  **Switch dynamic date filters to `Today (Tenant)`:** Open **Edit Custom Report**, go to the **Filter** tab, and replace user-relative `Today` comparisons with the tenant-anchored global field.
2.  **Move audience reports to `Indexed All Workers`:** When resolving **Hire Date**, **Job Profile**, **Location**, or **Position Changes** for audiences, **Workers for HCM Reporting** can miss upcoming or newly active local-time hires when an ISU runs in PST. **Indexed All Workers** targets the current and upcoming workforce directly. Note that if an audience was originally built in Audience Builder on **Workers for HCM Reporting**, Workday locks the data source—you must create a new audience backed by **Indexed All Workers**.

Fails

```
Report: Daily New Hire Provisioning Feed (Data Source: Workers for HCM Reporting)
Executed by: ISU_Provisioning at 06:00 Europe/London (22:00 prior day America/Los_Angeles)
Filter:
  Field: Hire Date
  Operator: equal to
  Comparison Type: Value specified in this filter
  Comparison Value: Today
Result: Evaluates against yesterday's date in Pacific Time; drops all UK and APAC hires starting today.
```

Works

```
Report: Daily New Hire Provisioning Feed (Data Source: Indexed All Workers)
Executed by: ISU_Provisioning at 06:00 Europe/London
Filter:
  Field: Hire Date
  Operator: equal to
  Comparison Type: Value from another field
  Comparison Value: Today (Tenant)
Result: Evaluates against the tenant calendar date configured in Edit Tenant Setup - System.
```

## When Should You Enable “Use Pacific Time Zone for Effective Moment” on Reports?

Local time zone processing means two users in different regions running the same report with an effective date prompt can see different snapshots if a staffing transaction—such as **Hire**, **Change Job**, **Termination**, or **Propose Compensation Change**—became effective at midnight local time in one region but not the other.

When downstream reconciliation requires every report execution to use a single global cutoff regardless of who runs it, Workday provides a report-level override:

1.  Run **Edit Custom Report** (requires **Custom Report Creation** or **Manage: All Custom Reports** in the System functional area).
2.  Open the **Prompts** tab and confirm **Effective Date** is enabled (available on standard data sources; unavailable on search and nBox reports).
3.  Select **Use Pacific Time Zone for Effective Moment**. This forces the report to evaluate transaction effective moments in Pacific Time whenever an effective date is supplied at runtime.
4.  To standardize an entire inventory of finance or audit reports at once, run **Mass Update Reports to Use Pacific Time Zone for Effective Moment** rather than editing definitions one by one.

Conversely, if you are building date expressions with [Workday calculated fields](https://kiweely.com/guides/workday-calculated-field-date-difference-increment) on `DateTimeZone` values and want output rendered in the viewer’s local clock rather than a static zone, select the **User’s Timezone** option inside the **Build Date** calculated field configuration.

## How Do Scheduled Processes and Outbound Connectors Handle Time Zones and DST?

Changing **Default Timezone** on **Edit Tenant Setup - System** or crossing a Daylight Saving Time boundary affects scheduled jobs differently depending on their cadence and connector template:

-   **Daily, weekly, and monthly schedules:** Workday initiates these jobs based on the calendar date and wall-clock time of the tenant’s local time zone. A job scheduled for `02:00` Saturday fires when the tenant’s configured time zone reaches `02:00` Saturday in both standard and daylight saving time.
-   **Hourly and multi-hour schedules:** Sub-daily schedules measure fixed elapsed time since the previous launch. During a fall-back clock shift where `01:59:59` returns to `01:00:00`, a 2-hour job honors the 2-hour interval rather than the clock label. To keep sub-daily schedules pinned to local clock hours across DST shifts, open **Scheduled Future Processes**, select **Scheduled Future Process > Edit** (you must be the schedule owner, or take ownership via **Scheduled Future Process > Transfer Ownership**), and select **Preserve Local Time**.
-   **Core Connector change detection and worker local moments:** Standard incremental feeds rely on [Core Connector: Worker change detection](https://kiweely.com/guides/workday-core-connector-worker-change-detection) launch parameters (**As of Entry Moment**, **Effective Date**, **Last Successful as of Entry Moment**, and **Last Successful Effective Date**). If downstream payroll or identity provisioning needs effective moments aligned to each worker’s local time zone rather than a single PST cutoff, build the integration on the **Core Connector: Global Worker** template, which exports effective moments mapped to the worker’s local time zone.
-   **Inbound REST and SOAP timestamps:** When external time clocks or middleware call web services such as `Import_Time_Clock_Events` or REST endpoints using `dateTimeZone` structures, always pass an explicit UTC offset in ISO 8601 timestamps or populate the IANA `timeZone` attribute. Omitting offsets causes Workday to assume UTC (`+00:00`), shifting punches relative to local shift schedules.

Transferring Schedule Ownership Resets Output Sharing

When you run **Scheduled Future Process > Transfer Ownership** because an integration admin left the organization, Workday automatically resets report output sharing to **Do not share report output** for both specific users and security groups. Re-verify the output distribution tab immediately after transferring a schedule.

## How to Verify Your Fix in the Tenant

1.  **Verify ISU and regional persona output side by side:** Run the custom report while proxied as a regional HR Partner (for example, in `Asia/Tokyo` or `Europe/London`) and compare row counts against a scheduled background run owned by your ISU in **Process Monitor** > **Output Files**. Both runs should return identical same-day hires once `Today (Tenant)` and **Indexed All Workers** are saved.
2.  **Inspect connector launch windows in Diagnostic Audit:** After launching your connector via **Launch / Schedule Integration**, open the integration event’s **Output Files** tab and inspect **Diagnostic Audit** and **Data Changes Audit** to confirm the evaluated **Effective Moment** and **Entry Moment** match the expected local or tenant boundary.
3.  **Check next fire times on Scheduled Future Processes:** Open **Scheduled Future Processes** and confirm the next scheduled launch timestamp reflects the intended time zone and **Preserve Local Time** behavior, and check **Edit Environment Restrictions** so Sandbox refreshes do not trigger unintended outbound runs.

When auditing dozens of scheduled reports and connectors before a release or tenant time zone change, [Kiweely Vine](https://kiweely.com/vine) can read your live report definitions, flag `Today` filters on ISU-owned schedules, and compare before-and-after report outputs directly against your connected tenant with your approval.

## Frequently asked questions

### Why does an Integration System User miss today's new hires in EMEA or APAC?

Integration System Users without a position or explicit user time zone often evaluate dynamic Today filters in Pacific Time. When midnight has already passed in London or Tokyo but it is still yesterday in California, a filter checking Hire Date equal to Today excludes those new hires until midnight Pacific Time.

### When does Use Pacific Time Zone for Effective Moment apply on a custom report?

That check box on the Prompts tab of Edit Custom Report only applies to reports built on standard data sources when an effective date is entered at runtime. It is not available on search or nBox reports.

### Why did an hourly scheduled integration shift by one hour after Daylight Saving Time?

Hourly and multi-hour schedules in Workday honor fixed elapsed intervals between runs rather than wall-clock hours. Enable the Preserve Local Time option on the schedule if you need sub-daily jobs to stay anchored to specific local clock times across Daylight Saving Time transitions.

### Do Cost Center and Company hierarchy changes follow the tenant default time zone?

No. Workday honors the tenant default time zone only for Supervisory Organization hierarchy effective dates. Company, Cost Center, Region, Location, and custom organization hierarchy reorganizations still take effect at midnight Pacific Standard Time.

## Sources checked

-   [Setup Considerations: Time Zones](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/time-zones/mcn1548806148902.html)
-   [Set Tenant Time Zone](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/time-zones/dan1370797668269.html)
-   [Concept: Workday Scheduled Processes](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/background-processes/dan1370797788576.html)
-   [Set Up Prompt Options for Custom Reports](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/set-up-reports/oof1496961011924.html)
-   [Troubleshooting: Custom Report Audiences Exclude New Hires Due to Time Zone Differences](https://doc.workday.com/admin-guide/en-us/manage-workday/collaboration/engagement-builder/troubleshooting--custom-report-audiences-exclude-n.html)

## Related guides

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

-   [### Workday Date Calculated Fields: Increment or Decrement Date and Date Difference Configure Date Difference, Increment or Decrement Date, Format Date, Build Date, and Lookup Value as of Date in Workday. Prevent blank-date errors, negative tenure numbers, and year-end YYYY mask bugs.](https://kiweely.com/guides/workday-calculated-field-date-difference-increment)
-   [### Workday CCW: how Core Connector: Worker change detection decides which workers land in the file With the Transaction Log on, Core Connector: Worker (CCW) puts a worker in the change file only after a subscribed transaction, an eligibility pass, a newly entered or effective change in the launch window, and a changed output field.](https://kiweely.com/guides/workday-core-connector-worker-change-detection)
-   [### Preparing for Workday 2027 R1 With a Small Team: The Timeline, What to Test in Sandbox Preview, and Who Does What Workday’s 2027 R1 feature release reaches Production in March 2027, with Sandbox Preview about five weeks earlier. Here is what Workday publishes when, a week-by-week test plan for a small team, and where AI testing fits.](https://kiweely.com/guides/workday-release-preparation-audit-checklist)
-   [### Why a Workday report returns no rows, or the wrong rows It’s rarely one cause. Test the data source alone first, then work through report filters, prompts, related objects, security and indexing in order.](https://kiweely.com/guides/workday-report-no-rows)

### More guides on Integrations and APIs

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

-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)
-   [How to change job profile and compensation in one Change Job SOAP request](https://kiweely.com/guides/workday-change-job-soap-profile-compensation)
-   [Why the Workday REST /workers endpoint leaves out terminated workers](https://kiweely.com/guides/workday-rest-api-workers-terminated)
-   [How to get the instance ID back after a POST to the Workday REST API](https://kiweely.com/guides/workday-rest-api-instance-id-after-post)
-   [How the Workday REST API batch protocol works](https://kiweely.com/guides/workday-rest-api-batch-protocol)
-   [Workday Studio XPath 2.0 and XSLT 2.0/3.0 Performance and Memory Streaming](https://kiweely.com/guides/workday-studio-xslt-xpath-streaming-memory)
-   [Workday Integration SFTP, PGP Encryption, and SSH Key Rotation Errors](https://kiweely.com/guides/workday-integration-sftp-pgp-ssh-errors)

### From the blog on Integrations and APIs

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

-   [Why Most Workday Studio Integrations Ship Without Tests](https://kiweely.com/blog/workday-studio-integrations-without-tests)
-   [The Slow Change Cycle in Workday Studio (and How to Break It)](https://kiweely.com/blog/workday-studio-slow-change-cycle)
-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)

## 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.
