ComplianceAug 14, 20267 min read

The EU Pay Transparency Deadline Passed in June. 23 of 27 Member States Missed It. Here's What Actually Applies to Hiring Right Now

Only 4 of 27 EU states met the 7 June 2026 transposition deadline for the Pay Transparency Directive. Here's what already applies to hiring — including for non-EU employers with EU-based hires — and why the patchwork rollout is riskier to ignore than a single hard date.

#EU Pay Transparency Directive #Pay Transparency #HR Compliance #Hiring Regulation #Salary Transparency #Remote Hiring #EU Employment Law
Ad

On 7 June 2026, EU member states were supposed to have finished transposing the Pay Transparency Directive — Directive (EU) 2023/970 — into national law. Two months later, most of them hadn’t. Only four of the twenty-seven, Slovakia, Italy, Lithuania and Malta, had national implementing legislation in force by the deadline, a status confirmed by multiple employment-law firms tracking the rollout, including Ogletree Deakins and Morgan Lewis. The Netherlands, Sweden, the Czech Republic and Denmark have confirmed they’ll implement by 1 January 2027 instead. France’s labour minister is targeting a bill passed by the end of 2026, with the law itself not entering into force until 1 January 2028. Austria hadn’t published draft legislation at all as of the deadline.

If you run hiring for a company with any EU footprint, the instinct here is obvious and wrong: no national law yet, so nothing to do yet. The European Commission has been explicit that this isn’t how the timeline works.

There is “no pause, no extension and no carve-out” through any future simplification package — the European Commission’s confirmed position, as reported by Ogletree Deakins.

The directive’s substance was decided years ago; what’s missing in 23 countries is only the local statute that will enforce it. That gap is a compliance-risk window, not a compliance-free one — and it’s the kind of gap that gets closed retroactively once national law does land.

What the directive actually requires — and where it starts

Strip away the commentary and the directive does four concrete things to the hiring process, corroborated consistently across the employment-law sources we reviewed (Ogletree, Morgan Lewis, Jackson Lewis, and the recruitment-ops guides at Ravio and figures.hr):

  1. Pay information has to reach the candidate before the interview, not after an offer. Employers must disclose the initial pay or pay range for a role either in the job posting itself or before the first interview. “We’ll discuss compensation once we know you’re a fit” — the default order of operations at most companies — is the exact sequencing the directive reverses.
  2. Salary-history questions are off the table entirely. Employers may not ask what a candidate currently earns or previously earned, at any stage from first contact through offer. This closes the loop that lets a low starting salary compound across a career.
  3. Gender pay gap reporting scales with headcount. Employers with 250 or more employees report annually; employers with 100–249 report once every three years. Employers under 100 sit outside the reporting duty, though not outside the salary-range and salary-history rules above, which apply regardless of size.
  4. A pay gap over 5% in a job category triggers a process, not a fine. If an employer can’t justify the gap on objective, gender-neutral grounds, it gets six months to remedy it. Only if the gap is still unjustified after that window does a joint pay assessment with worker representatives become mandatory — a root-cause analysis and action plan shared with employees and the relevant national authority. The 5% figure is a trigger for that process, not a legal tolerance; a smaller, unjustified gap is still a violation under Article 9(10), it just doesn’t force the formal joint assessment.

None of this is exotic by global standards — Colorado, California, New York and Washington have all run some version of “salary range on the posting” for a few years, and the EU version reads like a harder-edged synthesis of state-level US rules plus a structural reporting duty most US states don’t have. What’s new for a lot of employers outside the EU is rule two applying to them.

The part that catches non-EU employers off guard: it travels with the employee, not the employer

The directive applies based on where the worker is, not where the company is headquartered. A hiring platform, an HR team, or a staffing agency based in Hong Kong, Tokyo or anywhere else that recruits for a role an employee will perform from inside an EU member state is in scope once that member state’s law is live — subsidiary, branch, or a single remote hire working from an apartment in Lisbon, per the reading laid out by Gibson Dunn and echoed by remote-employment platforms tracking the same rule. For a company that has never opened an EU office but has said yes to one remote candidate in Berlin or Warsaw, that’s a bigger scope expansion than “an EU regulation” usually implies. We’d flag this as the detail most likely to be missed by a hiring team scanning the news for “does this apply to us” and stopping at the company’s own registered address.

What we’d actually do with a fragmented rollout, not a finished one

We build hiring infrastructure for a living — job postings, structured pipelines, the plumbing that carries a role from draft to offer — so we watch rules that change what a job posting is allowed to say more closely than most. Two observations from that vantage point, both our own reading rather than settled law:

A patchwork rollout is worse for compliance than a single hard date, not better. When every member state moves on 7 June, a hiring team ships one policy change on one day. When four states are live, four more are targeted for January 2027, France is aiming for 2028, and the rest are unscheduled, a global hiring process now has to know which country’s clock a given req is running on — and update as each new transposition lands. The “wait until it’s actually the law here” strategy that looks cautious with one country becomes a rolling maintenance burden across two dozen jurisdictions with different effective dates. The lower-effort path is the one that looks more aggressive on paper: build to the directive’s substance now, everywhere you hire in the EU, and let each country’s formal transposition date be a non-event when it arrives instead of a scramble.

Treat the salary-history ban as the one with the shortest fuse. Range disclosure is a job-posting edit. Reporting thresholds and the 5% trigger are annual or triennial processes with a six-month remediation runway built in — there’s time to build toward them properly. The salary-history question, by contrast, is something a recruiter can still be asking on a screening call this week out of habit, with no system flagging it, because it was never illegal at the company’s home address. That’s the rule most likely to be broken by inertia rather than by a decision, which makes it the one worth checking first — in application forms, in ATS screening-call scripts, and in whatever a recruiter is trained to ask when a candidate volunteers a number unprompted.

The practical list

For any hiring team with EU-based candidates or employees, regardless of where the company itself is incorporated:

  1. Map where your candidates and remote employees actually sit, not where your entity is registered. That map, not your HQ address, is what determines exposure as each country’s transposition lands.
  2. Audit job postings and interview scripts for salary-history questions now. This is the rule with no grace period built into its logic — it’s binary, and it’s the easiest one to still be breaking by habit.
  3. Add pay ranges to postings for EU-facing roles ahead of the local deadline, not at it. A range that’s already standard practice on the day a country’s law takes effect requires no scramble; a range added the week the law bites is a visible, dated compliance reaction.
  4. Track transposition status by country, not as a single EU date. The four countries live now, the cluster targeting January 2027, and France’s 2028 timeline are each a separate switch to flip, and the schedule will keep shifting as more countries confirm dates.
  5. If your headcount clears 100 EU employees, start the pay-gap analysis internally before a national law forces the clock. The six-month remediation window before a joint assessment becomes mandatory is generous only if you start counting from when you find the gap, not from when a regulator does.

The directive was never going to be a single day. 7 June 2026 was the date the substance stopped being optional in theory and started being optional only by geography and by how long a given country takes to pass a bill. That’s a smaller gap than “not yet EU-wide law” sounds like, and it’s closing on twenty-three different clocks at once.

Sources consulted for this piece: transposition status and the “no pause, no extension” Commission position via Ogletree Deakins; post-deadline analysis via Morgan Lewis; directive requirements via Ravio and figures.hr; non-EU employer scope via Gibson Dunn.

Ad

Ready to transform your hiring?

See how NiceHire's AI-powered hiring platform works for your team.

Get Started

Share this article

Ad

About the Author

NT

NiceHire Team

HR Tech Writer

Ad
Back to all articles
Ad
Support