EU Pay Transparency Directive 2023/970/EU: What Every Employer and HR Software Must Do by June 7, 2026

Post #1013 in the sota.io EU Compliance Series

June 7, 2026 is 25 days away. That is the transposition deadline for Directive 2023/970/EU — the EU Pay Transparency Directive. Every EU member state must have enacted implementing legislation by that date, and every employer operating in the EU must be ready to comply.

Unlike many EU directives that primarily affect large multinationals, the Pay Transparency Directive catches almost every EU employer with at least 100 employees — and some obligations (salary ranges in job ads, pay information rights) apply regardless of headcount. If your HR stack runs on US-based software, you face a second risk layer: the CLOUD Act means your employees' salary and compensation data sits in US jurisdiction even if it is processed on EU servers.

This guide breaks down the five core compliance requirements, the reporting timeline, and which HR software choices create versus eliminate that double risk.

Background: Why This Directive Exists

The EU gender pay gap stands at approximately 13% across the Union (Eurostat, 2024). For decades, opaque pay structures have made it nearly impossible for employees to detect pay discrimination — you cannot challenge what you cannot see. Directive 2023/970/EU changes that by mandating transparency at both the hiring stage (what the job pays) and the employment stage (how your pay compares to peers).

Published in the Official Journal of the European Union on 17 May 2023 (OJ L 149), the directive entered into force on 7 June 2023. Member states have three years to transpose it into national law. That window closes on 7 June 2026.

The directive amends Directive 2006/54/EC on equal pay and adds hard enforcement teeth: sanctions for non-compliance, a reversed burden of proof, and mandatory remediation procedures.

The Five Core Requirements

1. Pay Transparency in Job Postings

What it requires: Before the start of employment, employers must provide job applicants — whether through a job posting or through other means prior to the interview — with information about the initial pay or the pay range for the position.

Scope: Applies to ALL employers regardless of size.

Practical implication for HR software:

• Job requisition workflows must include a mandatory salary band field
• ATS (Applicant Tracking Systems) must enforce the salary range before a job goes live
• The information must be accessible enough for applicants to negotiate informed — posting "competitive salary" is insufficient under the directive's intent

What employers cannot do: Article 10 of the directive explicitly prohibits employers from asking candidates about their pay history. The salary information flow goes one direction: employer → candidate.

2. Right to Information for Current Employees

What it requires: Upon request, employees have the right to receive written information about:

• Their individual pay level
• The average pay levels, broken down by sex, for categories of workers doing the same work or work of equal value

Scope: All employers, all employee headcounts.

Practical implication:

• HR systems must be able to generate per-employee and per-category pay reports on demand
• The report must be deliverable in writing within a reasonable timeframe (directive guidance suggests 30 days)
• HR software that cannot produce gender-segmented pay comparisons by job category fails this requirement

Critical CLOUD Act note: This data is precisely the category of personal data — salary, gender, job category — that US authorities can compel a US parent company to produce under 18 U.S.C. § 2713. An employee exercising their pay information right under EU law may be filing into a system accessible to US law enforcement by separate authority.

3. Gender Pay Gap Reporting Obligations

This is the headline requirement with the most detailed implementation timeline.

Thresholds and deadlines:

What must be reported:

1. The gender pay gap (mean and median)
2. The median gender pay gap in complementary or variable components of pay (bonuses, commissions)
3. The proportion of female and male workers receiving complementary or variable components of pay
4. The proportion of female and male workers in each quartile pay band
5. The gender pay gap between workers by categories of workers, broken down by ordinary basic wage or salary and complementary or variable components

This data must be submitted to a designated national authority and made publicly available. The European Labour Authority receives aggregated EU-level data.

Practical implication for HR software: Your HRIS or payroll platform must be capable of producing all five data categories in a structured, reportable format. If your vendor does not yet support EU pay gap reporting exports, you have less than 12 months to either pressure them or switch platforms for the 250+ cohort.

4. Joint Pay Assessment for Persistent Gaps

What it requires: If the pay reporting reveals an unjustified gender pay gap of 5% or more in any category of workers, employers with 100+ employees must conduct a joint pay assessment in cooperation with workers' representatives.

Scope: Employers with 100+ employees who show a ≥5% gap that cannot be justified by objective, gender-neutral criteria.

Practical implication: This turns pay gap reporting from a passive disclosure into a remediation trigger. HR software must support gap analysis workflows and generate the structured data needed for the joint assessment process (which involves audit trails, documented justifications, and corrective action plans).

5. Burden of Proof Reversal and Enforcement

Article 17 reverses the burden of proof in equal pay disputes. Under current law (Directive 2006/54/EC), employees who allege pay discrimination must prove it. Under the new directive, once an employee demonstrates facts from which discrimination may be presumed — including using pay information obtained under Requirement 2 above — the employer must prove that no breach occurred.

Combined with: Member states must ensure effective, proportionate, and dissuasive sanctions. The directive calls for:

• Compensation including full back pay, related bonuses, and benefits
• Reimbursement of legal costs
• Financial penalties

The directive also introduces a 3-year limitation period that starts running only when the employee becomes aware of the pay discrimination — not when it began. Historical pay gaps can therefore generate claims going back years.

The CLOUD Act Double Risk for HR Software

What US-Based HR Platforms Mean for Pay Transparency Compliance

The directive requires employers to collect, store, and report highly sensitive personal data: individual pay, gender, seniority level, job category, bonus data. This is squarely within GDPR's definition of personal data subject to the strictest processing obligations.

US-based HR and payroll platforms — regardless of their EU data center locations — are subject to the CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 18 U.S.C. § 2713). Under that statute, US government agencies can compel US companies to produce data stored anywhere in the world, including EU data centers, without involving EU authorities.

The five major US HR platforms and their CLOUD Act status:

The critical point: the data you collect to comply with the EU Pay Transparency Directive — gender-segmented salary data, pay quartile distributions, bonus breakdowns — is the exact dataset that US authorities find most investigatively valuable in unrelated contexts (sanctions enforcement, securities investigations, tax matters). You are creating a rich dataset, and if it sits with a US corporate entity, it is accessible under US law.

GDPR Article 48 prohibits EU personal data transfers to foreign courts, tribunals, and authorities unless covered by an EU adequacy decision, a derogation, or an international agreement. The CLOUD Act is not covered by any of those exceptions. This creates a structural tension that the European Data Protection Board has flagged repeatedly without resolving.

EU-Native HR Software That Supports Pay Transparency Compliance

The following platforms have EU corporate structures that eliminate CLOUD Act exposure:

Personio (Munich, Germany)

Corporate structure: Personio SE & Co. KG — German partnership, Rechtsform SE & Co. KG. Investors include Kleiner Perkins, Accel, Index (US VCs as investors do not create US corporate jurisdiction). No US subsidiary with operational control over data.

Pay Transparency features: Personio's Compensation module supports salary band definition, pay range visibility in job ads, and gender pay gap reporting exports. The platform's EU data residency is structural rather than contractual — the operating entity is German.

Gap to watch: Personio's pay gap reporting is developing; verify your specific version supports the five EU reporting categories before the June 2027 deadline.

Factorial (Barcelona, Spain)

Corporate structure: Factorial HR, S.L. — Spanish limited liability company, regulated by Spain's AEPD data protection authority. Primary investors: CRV, Tiger Global (US), Creandum (EU) — investor jurisdiction does not determine corporate jurisdiction.

Pay Transparency features: Factorial supports compensation management, pay band configuration, and has been adding EU pay transparency features throughout 2025-2026 in anticipation of the directive. The job posting module supports salary range fields.

Note: Factorial uses AWS Ireland (eu-west-1) as primary infrastructure. AWS Ireland is a subsidiary of Amazon.com, Inc. (Delaware). Contractual EU data processing agreement is in place, but the CLOUD Act applies to Amazon at the US parent level. This is a better position than Workday/ADP (no US HR entity) but not fully CLOUD Act-free.

Kenjo (Berlin, Germany)

Corporate structure: Kenjo GmbH — German GmbH, Berlin. Small-to-mid market HR platform purpose-built for DACH/EU compliance. BayLDA (Bavaria) is the lead supervisory authority.

Pay Transparency features: Kenjo focuses on SME compliance and has EU salary band management and basic pay reporting. Better fit for the 100–249 employee tier that faces the 2031 reporting deadline.

Lucca (Paris, France)

Corporate structure: Lucca SAS — French simplified joint-stock company, Paris. Fully French ownership, no US parent, CNIL under French GDPR framework.

Pay Transparency features: Lucca's Poplee Compensation module specifically targets EU pay equity compliance. The platform handles pay band visualization, equity analysis, and is building out the reporting outputs aligned with the directive's five categories. Strong for French-market compliance, expanding EU coverage.

Quinyx (Stockholm, Sweden)

Corporate structure: Quinyx AB — Swedish aktiebolag, Stockholm. Nordic workforce management platform with full EU data residency (Swedish IMY supervision). Better fit for workforce scheduling with pay transparency overlays than full HRIS replacement.

HR Software Compliance Checklist for June 7, 2026

Use this to assess your current HR software stack:

Before June 7, 2026 (Transposition Deadline)

• Job posting module enforces mandatory salary range field — no "competitive" or blank entries
• Job posting module prevents collection of pay history from candidates (Article 10 prohibition)
• Employees can submit a written pay information request through the HR system
• HR system can generate per-employee pay level + peer category average (by gender) within 30 days
• Data retention policy covers pay equity data for at least 3 years (limitation period extension)

Before June 7, 2027 (First Reporting Deadline — 250+ Employees)

• Gender pay gap report: mean and median gap by category
• Bonus and variable pay component gap analysis
• Pay quartile distribution by gender
• Export format compatible with national reporting authority requirements
• Audit trail documenting pay decisions (needed if 5% gap triggers joint assessment)

Continuous (Ongoing)

• Annual gap monitoring against the 5% threshold
• Joint assessment workflow ready to trigger if threshold breached
• Data processor agreements updated to reflect directive's new data category (pay + gender + category combined)
• CLOUD Act risk assessment if US-based HR vendor — consider structural separation or EU-native migration

What Happens If You Miss the June 7 Deadline?

The directive requires member states to set sanctions that are "effective, proportionate and dissuasive." Most member states have implemented or are implementing:

1. Administrative fines — in the range of GDPR-style fines based on turnover (exact amounts vary by member state)
2. Presumption of discrimination — failure to comply with information obligations creates an automatic presumption in favour of the employee in any subsequent pay dispute
3. Reversed burden of proof — employers who failed to post salary ranges cannot argue that a hired employee's salary was market-standard without producing the evidence they were supposed to provide at hiring
4. Back pay liability — the 3-year rolling limitation period means non-disclosure during 2026 creates three years of back-pay exposure

The practical risk for non-compliant employers after June 7: every pay dispute filed after that date will include a pay transparency non-compliance allegation as a procedural weapon, regardless of whether pay discrimination actually occurred. Compliance protects you from the allegation, not just the outcome.

The Intersection with Existing EU Payroll Obligations

The Pay Transparency Directive does not replace other EU pay-related obligations — it stacks on top of them:

• GDPR (2016/679): The gender + pay + category dataset you create for reporting is sensitive personal data. Article 9 applies if gender is processed (special category). Article 35 DPIA likely required for systematic pay gap reporting.
• Works Council Consultation (national law): Most EU member states require works council or employee representative consultation before implementing pay band systems. This needs to happen before the software goes live.
• Equal Pay Act equivalents: Germany (Entgelttransparenzgesetz, 2017), France (Index Égalité Professionnelle), Netherlands (Wet gelijke behandeling) — these existing national frameworks must be cross-checked against the new directive requirements.

Summary: The June 7 Action Plan

The EU Pay Transparency Directive is not optional, and it is not only for large corporations. If you have 100+ employees in the EU, the June 7 reporting preparation clock starts now. For the job posting and pay information rights, every EU employer is in scope.

For HR software decision-makers: Audit your current platform against the five requirements above. If your vendor cannot demonstrate a compliant salary range enforcement in job ads, a gender-segmented pay information output, and a reportable pay gap dataset — you need to either demand a product roadmap or plan a migration.

For compliance officers: Build the CLOUD Act risk assessment into your GDPR Article 30 records now, before the first pay gap report forces you to document what entity holds the data and under what legal framework.

For EU-native HR platform evaluations: Personio, Factorial, and Lucca have the strongest EU-native credentials. Kenjo is the SME-tier option. Quinyx covers workforce management but not full HRIS. The June 7, 2026 deadline is the final nudge many EU employers needed to move off US-platform dependence for their most sensitive employee data.

sota.io is an EU-native managed PaaS deployed on Hetzner, Germany. No US parent company, no CLOUD Act exposure. If you are building or hosting HR applications that process pay equity data under the directive, start here.