u/TraditionalTrading

global payroll director, 14 country footprint within the EU. with the directive becoming enforceable in june, i'm 60% of the way through the salary band reconciliation work and the gaps i'm hitting are larger than i expected.

specific problems:

1. our compensation levels (P1-P7 global scale) don't map cleanly to country-specific job classifications. germany requires statutory job classification, france uses convention collective categories, italy uses contract levels. each has different equal-pay-comparator definitions.

2. cross-country comparisons in EUR require currency normalization, but the 'real' pay is still in local currency and historical levels need adjustment for inflation. we're doing manual currency normalization right now, which feels error-prone.

3. the directive requires gender pay reporting at 'category of worker' level, but our categories from a global perspective vs from each country's labor authority view aren't the same. we'll likely need to publish 14 different reports with slightly different categorizations.

4. our hr partners in each country are flagging that even with the reconciled bands, employee questions about their position in the band require a level of communication infrastructure we don't have today.

who's actually done this work for a multi-country EU footprint? specifically interested in real implementations (not consulting decks). how did you handle the band-to-classification mapping? what did you publish vs hold back?

i've been a global payroll director for 8 years and the job in 2026 doesn't look anything like the job in 2018.

specifically, what's now sitting under one title:

1. payroll operations (the original job): run cycles, statutory compliance, exception handling. still 30-40% of the role.

2. payroll integrations (newer): we own the data pipeline from HRIS to payroll providers to accounting. when a country's ID format changes, the pipeline breaks. when finance wants new cost-center splits, the pipeline changes. this is more devops than payroll.

3. payroll strategy (newest): which providers per region, when to consolidate, when to switch, vendor governance. used to be a CFO conversation. now it's mine.

the job ad still says 'global payroll director'. but 3 of these 3 are different skill stacks. anyone else managing this split internally? curious how peer companies are organizing it.

we're 5 weeks out from going live with workday + sdworx in 4 new countries (NL, DE, IT, ES) and the parallel run is killing us.

the test cycle on paper looked clean. workday pushes the input file, sdworx runs the gross to net, we compare against the legacy provider's output. easy. in reality, every cycle we hit 30 to 60 mismatches that we have to chase, and 80 percent of them are not workday or sdworx errors. they're mapping ghosts. an absence type that maps to one statutory bucket in legacy and a different one in the new flow. a benefit in kind valued by the legacy provider's local rules but recalculated by sdworx using their own rules. NL pension contributions flowing through 2 different gross to net engines that round in different places. all defensible. all painful to reconcile.

what's making me lose sleep is that none of this surfaces in workday testing. workday's outputs look fine because workday is doing what we told it to do. the variance lives between the input file and the local engine, which is exactly the layer that doesn't have a single owner. our implementation partner says it's a config issue. sdworx says it's our HRIS data quality. we're the ones holding the bag.

curious how others handle this. how many UAT cycles did you actually run before you trusted the parallel? did you bring in a third party to do the reconciliation, or did your in house team eat it? and at what point did you say good enough and flip the switch.

side note, the people in r/employerofthefuture have been having the same conversation about provider fragmentation more broadly, might be worth a look if you're knee deep in this.

our workday to local payroll connector broke twice last quarter. once because sdworx changed their import schema for belgium without warning anyone, once because a workday update silently renamed a custom field our mapping layer was reading from. both times we caught it the day before pay run. fun.

the thing is, this is not a workday problem or an sdworx problem. every multi country payroll setup is a stack of small custom bridges between systems that were never designed to talk to each other. somebody built each bridge 2 or 3 years ago, that person left, and now the bridge is documented in a confluence page from 2024 that nobody trusts.

curious how others are handling this. do you have one person who owns the integration layer end to end, or is it spread across the payroll team and IT? and how often does something break in a quarter for you? we're at roughly once a month across 18 countries and it feels high but i have no benchmark.

we run payroll for 12 countries through Workday with custom connectors to 5 local providers. realizing how coupled we are. if the roadmap goes somewhere we can't follow, those provider integrations are the first thing that breaks, and rebuilding them outside Workday is a 2-year project we don't have the budget for.

the real risk is how much of our infrastructure quietly assumes Workday will keep being Workday.

we run payroll for 12 countries through Workday with custom connectors to 5 local providers. realizing how coupled we are. if the roadmap goes somewhere we can't follow, those provider integrations are the first thing that breaks, and rebuilding them outside Workday is a 2-year project we don't have the budget for.

the real risk is how much of our infrastructure quietly assumes Workday will keep being Workday.

The EC dropped a compliance toolkit last week. job evaluation methodologies, gender-neutral pay structure guidance, the whole package. 7 weeks before the June 7 transposition deadline.

But Netherlands, Sweden, and France have all signaled they won't transpose on time. the EC confirmed there's no extension. so now Germany and Ireland are expecting full transparency infrastructure live by June while France is still circulating draft legislation.

If you're running payroll across 10+ EU countries your compliance timeline just forked.

The part quietly killing us is the data. the directive's work of equal value assessment assumes you can pull unified role classifications and comp data across every jurisdiction into one view, but we can't.

Gross-to-net sits in 4 different regional providers. comp bands stored in the HRIS with different job architecture per country. half our entities don't even use the same pay cycle cadence. the toolkit doesn't solve that. nothing solves that in 7 weeks.

Building for Germany first because that's where we have the most headcount and the clearest transposition path. everywhere else is a holding pattern.

Honestly not sure if that's strategic or just triage.