Most global payroll integrations look functional from the outside. These four questions reveal what's actually happening underneath.
If you're running Workday for HR and using a separate provider for global payroll, your integration is probably doing less than you think it is.
That's not a guess. It's what we hear in nearly every discovery conversation with Workday customers evaluating their global payroll setup. The integration was sold as seamless. The reality involves exports, re-entry, manual reconciliation, and at least one person on the team whose unofficial job is making sure data gets from Workday to global payroll and back again every cycle.
The problem is that most teams don't have a framework for evaluating what their integration is actually doing versus what it should be doing. These four questions give you one. They work whether you're assessing your current provider or evaluating a new one.
Question 1: When someone is hired, changed, or terminated in Workday, does that event reach global payroll automatically?
This is the most fundamental test. You made a change in Workday — does it flow to global payroll without someone triggering, exporting, or verifying it?
If the answer involves running a report, reformatting a file, uploading it somewhere, or logging into a second system to confirm it arrived, you don't have an automated integration. You have a process that depends on a human doing the right thing at the right time every cycle.
What "yes" looks like: you complete the action in Workday, and the global payroll system reflects it. No export. No second step.
What "no" looks like: someone on your team owns the handoff. They may have systematized it, they may be fast at it, but it's still a manual dependency in a process that runs on a deadline.
Question 2: When an employee needs to provide country-specific payroll information, does that happen inside Workday?
Global payroll requires data that Workday doesn't hold by default — tax elections, local bank details, statutory declarations. That data has to come from the employee. The question is where.
If employees are being sent to a separate portal to provide this information, you've introduced a second system into their experience and a tracking problem into yours. HR is now chasing completion in a platform that isn't Workday, and the process of collecting that data doesn't show up in any Workday workflow or dashboard.
What "yes" looks like: the employee provides everything inside Workday. No separate login, no second portal, no tracking spreadsheet.
What "no" looks like: there's a separate system, and someone is responsible for making sure every employee completes their information in it before the global payroll cycle closes.
Question 3: After global payroll runs, do the results come back into Workday automatically?
Global payroll runs. Payslips are generated. Cost data is produced. GL entries need to be posted. Where does all of that end up?
If the results live in the provider's system and someone has to retrieve them — downloading reports, reformatting data for the GL, uploading payslips somewhere employees can find them — then the integration only works in one direction. Workday sent the data out, but what came back was a manual process.
This is the gap that hits Finance hardest. If global payroll results don't flow back into Workday automatically, Finance is reconciling from a source outside the system of record, and the "single source of truth" has a hole in it exactly where the most sensitive cost data should be.
What "yes" looks like: global payroll results, payslips, and cost data appear in Workday at the end of each cycle. Finance can see consolidated costs without leaving Workday. Employees find their payslips in the same place they find everything else.
What "no" looks like: someone retrieves the results and routes them manually, or Finance works from a parallel data source entirely.
Question 4: When something goes wrong in a specific country, is there one team with direct authority to fix it?
This question isn't about the integration — it's about what's behind it. When a calculation is wrong in France, when a statutory filing is late in Germany, when a compliance question comes up in Brazil, who do you call?
If your provider outsources global payroll operations to local subcontractors, the escalation path runs through at least two organizations before anyone with authority over the problem hears about it. Your provider calls their partner, their partner investigates, and your team waits. The time to resolution is longer, the accountability is blurred, and the compliance exposure sits with you regardless of who caused the error.
What "yes" looks like: one team, with in-house global payroll expertise in that country, who can diagnose and resolve the issue directly.
What "no" looks like: an escalation chain that passes through a subcontractor before anyone can act.
What your answers tell you
If you answered "yes" to all four, your integration is genuinely closing the gap between Workday and global payroll. That's rare, and worth protecting.
If you answered "no" to any of them, each "no" is a manual step your team is absorbing every cycle. And each one compounds as you add countries, headcount, or complexity. One "no" is a workaround. Two or three means the integration isn't doing the job it was supposed to do.
None of these are unsolvable. They're mostly a byproduct of how global payroll integrations were built years ago, and the bar for what a Workday integration should do has moved a long way since then.
