Workday 2026R2: what HCM and integration teams should check now

Based on Workday's release summaries as reported by partners and universities, read in November 2026. I did not have access to the official release notes for every item, so check each point in the Workday Release Center before you act on it.

Workday's 2026R2 feature release went into production on 19 September 2026. Most write-ups agree on the headline: hundreds of enhancements across HCM and Finance, many of them switched on automatically. Here is what I would look at if I ran an HCM tenant with integrations attached to it.

HCM changes that can reach your integrations

Change Job. The legacy Change Job experience is being retired. Partner summaries describe an enhanced experience built on Change Job templates, with a conversion that migrates existing templates and creates new ones for Change Job, Request Transfer, Change Location and Change Contingent Worker Details. One source gives 19 September as the date from which templates become required. If you have not yet checked your tenant, do it now. Business processes and security that someone built around the old screens may behave differently.

Mass Job Change. An opt-in feature that replaces mass action worksheets with Mass Job Change tables, reported at up to 5,000 changes in one go. Useful for reorganisations. It also means one person can now trigger thousands of events at once. Any integration that reacts to hire or job change events will see that as a spike. Decide in advance how your downstream systems handle it.

Worker addresses can be purged. A new purgeable data type lets administrators permanently remove home and work addresses for active and terminated workers, with validations that block or warn when a purge would affect pay or benefits. That helps with GDPR requests. It also means an integration that depends on an address must handle the case where the address is gone.

Time zones. Reporting, events and date-driven warnings are reported to use the local time zone of the processing user instead of Pacific Time. One source says the opt-out ends in 2027R1. If you have reports or integration schedules that use "today" or a cut-off time, test them. A shift of a few hours can move a record into the next day's file.

Smaller items. Redesigned Change Personal Information flows, effective dating for service dates and for dependents, and a redesigned worker profile.

Integration and API changes

The sources I could read were light on detail here, so treat this as a list of things to verify:

  • Get Workers (REST) is reported to gain a filter and to return pre-hire records. If you consume it, check whether pre-hires now appear where they did not before. That is a classic cause of duplicate records.
  • Time Tracking v7 (REST) is reported to add a "Date Time Zone" field. REST consumers should look at it; SOAP is reported as unaffected.
  • Graph API exposes more job profile data to apps built on Workday Extend.
  • Recruiting integrations (Kenexa and Unistaff) can secure the documents they generate.
  • Passkeys are available as a sign-in option.

I found no notice in the sources I read about changes to Studio, EIB or Core Connectors in this release. Absence of evidence is not proof, so read the "What's New" notes for Integration Cloud yourself.

Agents and AI: read it as direction, not as a to-do

Workday is positioning an Agent System of Record to govern AI agents, and has bought Sana, Flowise and Pipedream to build and connect them. Reports also describe tools that let agents reach HR and Finance data under the same role and organisation rules as human users. The practical question for an integration team is not the product names. It is who is allowed to read what, through which identity, and how that is logged. Those are the same questions you already answer for integrations.

A short test list for your integrations

  1. Run the Integration Exception Audit in production, as one partner guide suggests, and fix what it finds before the next release.
  2. Replay your key events in the sandbox: hire, job change, termination, personal data change. Compare the output files with production.
  3. Test one bulk change with a Mass Job Change and watch what your payroll, identity and ticketing integrations receive.
  4. Check anything date-driven against the time zone change.
  5. Check REST consumers of Get Workers and Time Tracking for the new behaviour.
  6. Write down who owns each integration and who gets the failure alert.

What comes next

Workday ships two feature releases a year, normally in March and September, with a sandbox preview about five weeks before production. By that pattern 2027R1 should reach production in March 2027. I could not find a published date, so confirm it in the Release Center and put the preview window in your calendar now.

If you want help reviewing your integrations against a release, send me a message.

Sources

Have a Workday problem that needs an owner?

Book 30 minutes. If I cannot help, I will say so and point you to someone who can.

Book a 30-min intro call