For years, pay reporting meant submitting a number once a year and moving on. The EU Pay Transparency Directive (2023/970) changes this fundamentally. It shifts the burden of proof onto the employer. If a worker raises a pay discrimination claim and you cannot show documented, gender-neutral criteria behind every pay decision, you lose by default.
That is not a compliance hurdle. That is an operational transformation — one that requires HR, payroll, and finance to work from the same source of truth, with defensible data and documented processes at every layer.
This article walks through what the Directive requires, where the real risk sits, and how enterprise leaders can build the operational capability to meet it — starting now.
Section 1: Get your foundations right
Role architecture and pay criteria
Everything in the Directive runs on one foundational layer: consistent, documented job architecture. If your job categories are not standardized across countries, and your pay criteria are not written down, you cannot produce a defensible report — and you cannot respond to an employee information request without exposing the business.
The Directive requires reporting “by category of workers.” Those categories must exist, be applied consistently, and survive legal scrutiny. In multi-country enterprises where a role called “Senior Engineer” in Berlin is classified differently to “Software Engineer III” in Dublin, producing a legally defensible gender pay gap report becomes impossible before you even run the numbers.
Without consistent role categories across your workforce, your pay gap report can be challenged on methodology alone — before anyone looks at the numbers. Under Article 18, the burden of proof in a discrimination claim shifts to the employer if documented, gender-neutral criteria cannot be shown.
4–8 job families covering every role across every entity — employees, EOR workers, and contingent workers where in scope.
4–6 levels per family with documented scope, autonomy, and impact markers.
A written pay philosophy mapping every criterion to the Directive’s four legal standards: skills, effort, responsibility, and working conditions.
Compensation bands (min, midpoint, max) per family and level — with documented regional adjustments and sign-off from legal counsel.
Pay structure confirmed to cover all worker types in scope: part-time, fixed-term, agency, and contingent workers.
Papaya’s workforce data model is built for blended global workforces — employees, EOR workers, and contractors in one system. When you align your job architecture across geographies, the underlying data layer can support it, with in-country experts reviewing classification consistency against local labor law. → Explore Papaya’s workforce platform
Section 2: Pre-hire rules kick in first
Salary transparency in job postings
From 7 June 2026, every job posting must include a salary range or a reference to the applicable pay scale. This applies to all EU-based roles regardless of company size. The implication is significant: you need documented compensation bands to source those ranges from. Organizations operating with informal pay practices or market-rate adjustments decided case-by-case no longer have cover. The band must exist before the posting goes live.
Beyond job postings, candidates also have the right to ask about pay prior to the first interview. That means your talent acquisition teams need training and a consistent script — one that draws from the same documented band structure, not manager discretion.
“Market rate” and “manager judgement” are not sufficient on their own. The Directive names four criteria the courts will apply: skills, effort, responsibility, working conditions.
What the hiring process must change
Employers are also prohibited from asking candidates about their current or previous salary history. This is a material change to many recruitment processes. Your ATS workflows, interview guides, and recruiter training all need to be updated to reflect this — and the update must be documented.
Salary history questions in the hiring process are now illegal under the Directive. A single recruiter asking the wrong question creates documented evidence of non-compliance. Retrain your teams and update your ATS workflows before the first posting goes live.
Section 3: Employee information rights
Article 7 — the right to compare pay
Article 7 gives every employee the right to request information on their individual pay level and the average pay levels, broken down by gender, for categories of workers doing the same work or work of equal value. They can exercise this right once a year, and you must respond within two months — in writing, substantiated, and consistently across the company.
This is where most enterprise HR teams are underprepared. The risk is not just the request itself. Inconsistent responses between employees — even unintentionally — become evidence of unequal treatment. You need a formal intake process, templated responses, and a full audit log kept for four years.
1. One owner, one intake channel — not five different inboxes across regions.
2. Three response templates covering: basic pay info, comparative pay info, and edge cases with privacy considerations.
3. Full audit log of every request, dates, and who responded — kept for the 4-year lookback period.
4. Internal SLA of 4 weeks against the 8-week legal limit, to leave room for legal review.
5. Anti-victimization language in your HR policy — workers exercising these rights must be protected from adverse treatment, including dismissal.
Papaya’s worker portal gives each employee a transparent view of their total compensation — base, variable, allowances, and statutory components — across whatever country they work in. For many employees, proactive visibility answers the question before they need to file a formal request, reducing volume and consistency risk on the HR side. → See the employee portal
Section 4: Reporting readiness
Your first annual report is due 7 June 2027
For companies with 250 or more employees, the first gender pay gap report must be submitted by 7 June 2027 and will use 2026 data. That sounds like time. It is not. Getting the underlying data layer right takes six to twelve months. If you are only starting in 2026, you are already late.
The report requires seven specific metrics under Article 9(1). These are not qualitative statements — they are precise calculations that require clean, queryable HR and payroll data, broken down by gender and by category of worker. If that data currently lives across disconnected local payroll systems, regional spreadsheets, and ad-hoc exports, you have a data problem before you have a reporting problem.
An incomplete or inaccurate report is a compliance breach. Article 9(6) makes management sign-off personally accountable. Both management sign-off and worker representative consultation are legally required before submission — build them into your governance calendar as fixed events, not last-minute approvals.
The Directive also requires four years of historical pay data to be accessible and audit ready. Monitoring bodies and employees can request data going back that far. If your data lives in disconnected local payroll systems, retrieving it on demand becomes a multi-week project — and inaccuracies in the historical view become a compliance issue.
Papaya consolidates payroll, pay component breakdowns, worker classification, and country-level data into one system across 180+ countries. Your reporting draws from the same data that runs your payroll account, not a manual reconciliation exercise across local providers. For finance leaders signing off on the report, this is the difference between defensible and exposed. → Talk to our compliance team
Section 5: When the gap exceeds 5%
Mandatory joint pay assessment
If your report reveals a mean gender pay gap exceeding 5% in any category of workers that cannot be justified by objective, gender-neutral criteria, you are required under Article 10 to conduct a joint pay assessment — in cooperation with worker representatives.
This is one of the most operationally demanding parts of the Directive. The assessment requires identifying which roles contain the gap, establishing whether the difference is explained by legitimate criteria, and — where it is not — agreeing a remediation plan with a defined timeline.
The practical implication is that by the time your first report is due, you need to have already run your numbers internally, know where your gaps are, and have a plan ready. Discovering a material gap for the first time in a public report, without a remediation plan, is a reputational and legal problem at the same time.
The organizations that will navigate this well are those that have already run their own numbers — and built a plan before the report is submitted.
Section 6: The Directive is a floor, not a ceiling
Member state variation adds complexity
The EU Directive sets minimum requirements. Several member states are already layering stricter obligations on top — and the burden of tracking falls to employers operating across multiple jurisdictions.
Ireland already requires pay gap reporting from companies with 50 or more employees. Spain has stricter justification thresholds. Italy, France, and Germany have published or signaled additional obligations. The Directive floor is not your actual obligation in any given country — your obligation is whatever is strictest in each jurisdiction where you employ people.
This makes multi-country compliance a moving target. It requires a monitoring function, not just a one-time readiness exercise. Regulatory changes need to reach your HR and legal teams as they happen — not when an audit surfaces them.
Papaya’s in-country expert pods track regulatory changes across 180+ jurisdictions as a core part of the platform. When a member state moves on transposition, your account team is notified directly — not the other way around. → Learn about Papaya’s compliance network
Where to start: a practical sequence
Given the scope of what the Directive requires, the question most leadership teams are asking is not “what do we need to do?” but “what do we do first?” The answer depends on your starting point, but most enterprises have the same foundational gaps.
The organizations that treat this as an operating capability — not a compliance checkbox — will be better positioned not just for June 2026, but for the ongoing cadence of reporting, remediation, and regulatory evolution that follows.
Papaya Global’s EU Pay Transparency Readiness Checklist covers all 22 actions required under the Directive — with detail on what good looks like at each step, and where your operational risk sits. → Review the complete checklist here
This article is for informational purposes only and does not constitute legal advice. Pay transparency obligations vary by member state and are evolving as national legislation is finalized. Consult qualified legal counsel for jurisdiction-specific guidance. Content is current as of May 2026.
