EU Pay Transparency Directive: What It Means for Payroll Infrastructure

What the Directive Requires

Directive (EU) 2023/970 rests on four pillars. Each one creates a distinct data obligation for payroll infrastructure.

1. Salary range transparency

Employers must disclose the salary range — or at least the initial pay level — for every open position. This information must be provided in the job posting or communicated to the candidate before the first interview. Critically, the directive prohibits employers from asking candidates about their current or historical salary. The asymmetry is intentional: the employer discloses ranges, the candidate is not required to disclose current pay.

For payroll infrastructure, this means the system must maintain structured compensation band data that can be exported for job posting workflows. If salary ranges live only in spreadsheets or HR heads, the disclosure requirement becomes a manual burden that scales poorly across multi-country operations.

2. Employee right to pay information

Any employee can request the average pay levels for workers performing the same work or work of equal value, broken down by gender. The employer must respond within two months. The information must be accurate, based on actual payroll data, and disaggregated by gender.

This is the first pillar that directly touches the payroll engine. The system must be able to identify employees performing “equal work,” aggregate their compensation, and produce a gender-disaggregated average — on demand, within the statutory response window.

3. Gender pay gap reporting

Companies with 150 or more employees must submit their first gender pay gap report by 7 June 2027, covering 2026 data. Companies with 100–149 employees follow by 7 June 2031. The reports must include:

• Mean and median gender pay gap (overall and by component)
• Mean and median gap in complementary or variable components
• Proportion of male and female workers in each pay quartile
• Breakdown between base, variable, and complementary compensation

The reporting cadence is annual for companies with 250+ employees, every three years for 150–249 employees.

4. Joint pay assessment

When the gender pay gap exceeds 5% and cannot be justified by objective, gender-neutral criteria, the employer must conduct a joint pay assessment together with worker representatives. The assessment must identify the causes of the gap, develop remedial measures, and monitor their effectiveness. This is not optional — it’s triggered automatically by the reporting results.

The Payroll Data Problem

The directive assumes payroll systems can produce data they were never designed to produce. Most payroll systems calculate gross-to-net. They don’t categorize employees by “work of equal value,” don’t track variable versus complementary pay components separately, and don’t aggregate by gender across pay quartiles.

The reporting requirements demand:

• Compensation broken down by component type (base, variable, complementary)
• Gender-disaggregated aggregation across the entire workforce
• Pay quartile distribution by gender
• Historical comparison (year-over-year gap trends)
• Cross-entity consistency for multi-company providers

For most payroll platforms, producing this data requires an analytics project: extract payroll results to a data warehouse, classify wage types post-hoc, add gender data from HR, build custom reports. The result is a fragile pipeline where the “report number” and the “payroll number” are connected by ETL, not by architecture.

The gap isn’t a feature request — it’s a structural mismatch. The directive requires analytical capabilities on top of transactional payroll data. Systems that were built to process one employee at a time, one period at a time, now need to aggregate across all employees, all periods, all components, and all entities — with gender as a first-class dimension.

How Payroll Engine Addresses This

Payroll Engine’s architecture maps to the directive’s requirements through five existing capabilities.

1. Case/CaseField model

Employee gender, compensation components, and job classification are all case fields. The regulation defines what data exists. Adding directive-required fields — job category, equal-work classification, compensation band assignment — is a regulation extension, not a platform change. The case model already supports structured, typed, time-tracked employee data. The transparency directive adds new fields to that model; it doesn’t require a new model.

2. Wage type structure

PE’s wage types already separate base salary, variable components (bonuses, commissions), and complementary benefits (car allowance, pension employer contribution). Collector groups tag wage types by category — a “Base,” “Variable,” or “Complementary” group can be defined per regulation without touching the wage type logic itself. The consolidation wage types (WT 7000–7030) provide a uniform interface across countries, so the same report can aggregate German, French, and Dutch results using consistent component categories.

3. Reporting layer

Server-side report scripts (ReportEndFunction) can query payrun results across periods, employees, and tenants. A Pay Transparency Report can aggregate by gender, by component, by quartile — using the same data the payslip is based on. No separate data warehouse required. The report queries the same tables that store the legal payrun results. The “report number” and the “payroll number” are identical by construction.

4. Multi-tenant consolidation

For providers running hundreds of companies, the regional consolidation repos (DACH, Benelux, Iberia) already aggregate across tenants via ExecuteConsolidatedQuery. The pay transparency report follows the same pattern: query across tenants, aggregate by gender and quartile, produce the consolidated view the directive requires. A provider operating 200 companies doesn’t need 200 separate reports — the consolidation layer produces one report across all entities.

5. Audit trail

The directive requires that pay structures be based on “objective, gender-neutral criteria.” PE’s audit trail and calculation traceability demonstrate exactly how each employee’s pay was calculated — which wage types applied, which lookups were used, which case field values determined the result. This is the infrastructure for the “justification” the directive demands when gaps exceed 5%. Instead of explaining pay differences in prose, the provider can show the calculation chain.

Transposition Status: Where EU Countries Stand

As of May 2026, no member state has fully completed nationwide transposition of the Pay Transparency Directive. The European Commission has confirmed that no extension will be granted — the 7 June 2026 deadline stands. The practical reality is that most countries are in various stages of drafting, consultation, or partial adoption.

Beyond the PE-covered countries: Sweden has suspended implementation pending further review. Estonia has publicly stated it would rather pay Commission fines than transpose on schedule. Denmark targets January 2027. Ireland and Italy are in advanced drafting stages but unlikely to meet the June deadline.

What Providers Should Do Now

The first gender pay gap reports (for companies with 150+ employees) are due 7 June 2027, covering 2026 calendar year data. That means the payroll system must be capturing the right data now — not after transposition is complete. Five practical steps:

1. Audit your data model

Does your payroll system capture gender, job classification, and compensation component types as structured fields? In PE, this means checking the Case/CaseField model for each country regulation. The directive requires gender as a first-class attribute on every employee record, and job classification as the basis for “equal work” grouping. If these fields don’t exist in the regulation, they need to be added as a regulation extension.

2. Map wage types to directive categories

Identify which wage types are “base” (regular salary), which are “variable” (bonuses, commissions, performance pay), and which are “complementary” (benefits in kind, company car, pension employer contribution). PE’s collector groups can tag wage types for reporting purposes without changing their calculation logic. A TransparencyBase, TransparencyVariable, and TransparencyComplementary collector group per regulation creates the classification layer the directive requires.

3. Build the report

A Pay Transparency Report following the ReportEndFunction pattern, querying across periods and employees. The report should produce the exact data structure the directive requires: mean/median gap by component, pay quartile distribution by gender, year-over-year comparison. The reporting infrastructure already supports cross-period, cross-employee queries — the transparency report is a specific configuration of that capability.

4. Test with real data

Run the report against historical payrun results. PE’s forecast jobs can simulate scenarios to understand the impact before the first official report is due. What does the gender pay gap look like for your clients today? Where does the 5% threshold trigger a mandatory joint assessment? Testing with actual data surfaces structural issues before they become compliance failures.

5. Prepare for the joint pay assessment

If the report shows a gap exceeding 5%, the directive requires a joint assessment with worker representatives. The payroll infrastructure must provide the detailed breakdown that makes this assessment productive — not just “the gap is 7%,” but “the gap in variable components for mid-level technical roles is 12%, driven by bonus allocation patterns.” The granularity of PE’s result data supports this level of analysis without requiring a separate analytics investment.