Where the provider integration now lives

Workday launched Total Benefits on September 24, and the component that changes how an HR systems team spends its week is Workday Wellness. The Workday announcement describes it as connecting a customer's benefit providers directly to Workday, with real-time visibility into benefit usage, program performance and cost direction. It sits inside Workday HCM alongside Benefits Guidance delivered through Self-Service Agent, Life and Money Solutions, and Benefits Administration Services delivered by partners.

The number to hold on to is 75 percent. Workday says early adopter customers saw a reduction of that size in the time spent onboarding a new benefit provider. That is a claim about integration effort rather than about employee outcomes, which makes it the most interesting figure in the release for whoever owns the tenant.

Workday does not say how many early adopters there were, who they were, or what the onboarding work involved before. Read it as a direction rather than a line for a business case.

A configured connection is less work than an integration you own

Anyone who has stood up a benefit provider feed knows that work. Somebody agrees a file layout, builds the eligibility extract, decides what happens when a mid-month hire arrives, schedules the run, and writes alerting so a failed transmission reaches a person. Then it needs an owner for as long as the provider relationship lasts.

A vendor-managed connection removes most of that. Transport, mapping and retry behaviour belong to Workday and the partner, while the customer configures which providers are connected and who is eligible. A 75 percent cut is believable on that basis, because most of the elapsed time goes to specification and testing rather than to code.

We have written before about the difference between a connector and an integration. A connector is a supported path between two systems. An integration is a commitment about data, timing and failure that somebody in your organisation has to honour. Total Benefits changes who holds the first one. The second stays with you, because eligibility rules and the data leaving your tenant are still yours to defend.

The provider list is maintained by somebody else now

Workday names the partners. Wellness includes Bright Horizons, Care.com, EyeMed, Maven Clinic, Morgan Stanley at Work, Multiply, Oura Ring, SmithRx, WEX and When, with Aon named as a broker and advisor partner. Life and Money Solutions names OnePay, EarnIn, PayPal, Cash App, Chime, DailyPay, The Work Number by Equifax, Experian and Checkr. Strada and Benefit Harbor deliver Benefits Administration Services.

That is a strong list and it will get longer. It is also a list your organisation does not control. If the provider your benefits team signed last year sits outside it, you are worse off than you were the day before the launch, because the standard answer in the team quietly becomes picking a partner who is already connected.

Integration capability fades when it stops being exercised. A team that has not built a provider feed in three years will be slower at the next one, and the people who knew the eligibility logic will have moved on. Our piece on where Workday Extend integration boundaries sit covers the same trade elsewhere. For most employers it is still the right trade. Take the managed path for the common case and keep one person who knows the custom path.

Two October dates decide this quarter's planning

The availability detail is unusually precise. Workday Wellness, Life and Money Solutions and Benefits Administration Services are generally available to United States customers now. Benefits Guidance through Self-Service Agent is expected to reach general availability in October 2026. The Experian and Checkr income-verification integrations are expected in late October 2026, and The Work Number by Equifax is already live.

A team that relies on a single income-verification route today has a choice arriving within weeks. That belongs in this quarter's plan rather than on a roadmap slide, and the review work has to start before the feature does. Put the flow on the integration map that should exist before the roadmap now.

Income verification is a privacy review before it is a configuration

Adding an income-verification provider moves employment and earnings data about named individuals to a third party. In most organisations that means a data protection assessment, a contract review, a retention decision, and a clear answer on who may trigger a verification and on what grounds.

The configuration screen asks none of it. Turning on a second verification route takes minutes, and the review behind it takes weeks at a regulated employer. If late October matters to you, start the review now, because the switch will be ready long before the sign-off is.

There is a governance gain here too. Requests flowing through a connection Workday manages leave a record in one place rather than in a provider portal. That record also becomes evidence, so decide who reads it.

Surfacing benefits or reporting on them

David Wachtel, General Manager of Core HR Products at Workday, said in the release: "Benefits have become incredibly complicated for organizations to manage and too difficult for employees to understand, leaving many unaware of the support available to them." The problem he describes is real and well documented.

Tanner Brunsdale, Director of Benefits and Mobility at Lyft, said: "Employees don't lack benefits, they lack a way to find and use what's already offered to them." He added: "Workday Wellness helps us close the gap between what we're paying for and what people actually use, by surfacing the right benefit to the right person at exactly the moment they need it."

The open question is whether surfacing moves take-up or moves the reporting on take-up. Real-time visibility into usage and cost direction hands a benefits team a number it did not have, and a number shifts budget conversations even when behaviour has not shifted. For two quarters both outcomes look the same on a chart.

Before you move an existing provider onto a managed connection, put one question to the people signing it off. If this partnership ends, what do we rebuild, who here has built it before, and how long does that take. If nobody can answer, run the current integration in parallel through one enrolment cycle.