EU Pay Transparency Directive: HRTech Build Plan for 2026

On 7 June 2026, all 27 EU member states must have transposed Directive (EU) 2023/970, the Pay Transparency Directive, into national law. The directive obligates employers to report gender pay gap data, publish pay ranges in job postings, end pay history questions, and run joint pay assessments where unjustified gaps exceed 5%. The HRIS sitting behind a 250-plus-employee customer on transposition day either produces a compliant report or it does not. The first reference year is 2026; the first reports are due in 2027.

HRTech and payroll vendors that have not yet shipped pay equity capabilities are now running out of runway. This post is for HR product managers, payroll architects, and HRIS buyers scoping the pay transparency feature work for 2026 and 2027. It focuses on the directive’s concrete data requirements, the workflow obligations, and the build-versus-buy choices for vendors and customers alike.

What the directive actually requires (and what it does not)

Directive (EU) 2023/970 entered into force on 6 June 2023. The transposition deadline is 7 June 2026. The directive itself does not directly bind employers; member-state law does. But the directive sets a floor that all 27 transpositions must meet:

• Pay range disclosure in job postings or before interview. Employers must inform applicants of the initial pay or pay range for the position, either in the job posting or before the first interview.
• Prohibition on pay history questions. Employers cannot ask candidates about their pay history with previous employers.
• Right to information. Workers have a right to request information on their individual pay level and the average pay level, broken down by sex, for categories of workers performing the same work or work of equal value.
• Gender pay gap reporting. Employers with 250 or more workers must report annually starting in 2027 for reference year 2026; employers with 150 to 249 every three years (first report 2027); employers with 100 to 149 every three years starting 2031; employers under 100 are not required to report but may opt in or be required by national law.
• Joint pay assessment when reporting shows an unjustified pay gap of more than 5% in any category of worker and the employer cannot justify or close it within 6 months.
• Burden of proof reversed in equal pay litigation: the employer must prove that pay differences are not discriminatory.
• Sanctions must be effective, proportionate, and dissuasive; the directive lets member states define specific penalties.

The directive does not require pay equality. It requires transparency and joint remediation when unjustified gaps appear. The distinction matters: an employer can have a measurable pay gap and still be compliant, as long as the gap is justified by objective, gender-neutral criteria and the methodology is documented.

The 6 data points your HRIS must already be capturing

The gender pay gap report has six core data points that must be calculable from the HRIS and payroll data:

1. Gender pay gap overall (mean and median).
2. Gender pay gap in complementary or variable components (bonus, commission, equity).
3. Median gender pay gap.
4. Proportion of female and male workers receiving complementary or variable components.
5. Proportion of female and male workers in each quartile of the pay distribution.
6. Gender pay gap by category of workers performing the same work or work of equal value (this is the breakdown that triggers the joint pay assessment obligation).

The first five are derivable from payroll data and a binary gender field. The sixth (category of workers performing equal work or work of equal value) is the hard one. It requires a job evaluation methodology that classifies workers into categories using objective, gender-neutral criteria covering skills, effort, responsibility, and working conditions.

An HRIS that captures gender (or self-identified sex, as some member states permit), pay by component, and a job classification framework can produce the first five reports. The sixth requires explicit job evaluation work, either through a vendor (Korn Ferry, Mercer, Willis Towers Watson, Hay job evaluation), through a structured internal framework, or through an HRIS-native evaluation module.

For HRTech vendors targeting 250-plus customers, the realistic 2026 product scope includes:

• A configurable job evaluation framework supporting Hay-style, point-factor, or grade-based methodologies.
• Per-country gender field handling, with self-identified options where national law permits.
• A pay component model that distinguishes base, variable, equity, and benefits with consistent currency and time normalization.
• Quartile distribution computation.
• A category-of-worker view that supports both employer-defined categories and a default derivation from the job evaluation framework.

Job categorization for equal work: the methodology trap

The category-of-worker breakdown is where most pay transparency projects stall. The directive requires categorization based on objective criteria. National transpositions are clarifying what those criteria look like, but the operative test is: do the categories group together workers performing the same work or work of equal value, based on skills, effort, responsibility, and working conditions?

Three traps that catch first-build implementations:

1. Job title as a proxy for category. Job titles are inconsistent within and across organizations. Two workers with the same title can do materially different work; two workers with different titles can do equivalent work. Title-based categorization does not survive a joint pay assessment.
2. Pay band as a proxy for category. Pay bands embed the very thing the directive is trying to surface (whether equally-valued work is equally paid). Categorizing by pay band is circular.
3. Free-form job evaluation without traceability. A manager-driven evaluation without documented methodology is challengeable. The evaluation framework must be documented, applied consistently, and auditable.

The structurally sound pattern is a documented job evaluation framework with a small number of categories (typically 20 to 80 for a 250-employee organization), each defined by explicit criteria, with workers placed in categories based on those criteria. The categories are independent of pay; pay is then analyzed within each category.

Vendors like Syndio, Trusaic, and PayAnalytics built their products around exactly this workflow. HRIS vendors (Workday, SAP SuccessFactors, HiBob, Personio, BambooHR, Hibob, Sage People) are racing to add native job evaluation modules. The build-or-buy decision for customers depends on portfolio complexity; a single-country employer with simple job structure can often configure the HRIS-native module, while a multi-country employer with complex grading often benefits from a specialist.

Reporting pipeline: from payroll source of truth to NCA submission

The pay gap report is not a one-off computation. It is an annual workflow that produces a reproducible report from a versioned dataset.

A working reporting pipeline has these stages:

1. Snapshot the source data at the reference year close. Payroll data, HRIS data, gender data, job evaluation results. Immutable.
2. Apply normalization (full-time-equivalent adjustments, currency conversion at a defined date, treatment of leavers and joiners per the national transposition’s rules).
3. Compute the six required metrics plus any national-specific extensions.
4. Generate the structured report in the format required by the national competent authority (some authorities will define XBRL schemas; others will accept CSV or PDF).
5. Submit to the NCA through the national portal.
6. Archive everything with full reproducibility. If the auditor or worker representative comes back in 18 months and asks “how was this 4.2% gap calculated for the operations category”, the answer is the archived computation, not a re-run.

The pipeline must be deterministic. Re-running the same source data with the same parameters must produce the same report. This is harder than it sounds: payroll systems often have retrospective corrections (back-pay, expense reclassifications) that change historical numbers. The reporting layer must distinguish between “as at the reference date” and “as known at report generation date” and pick one consistently.

Pay-band publication in ATS and job-board feeds

Pay range publication in job postings is the user-facing change that customers notice first. The directive requires either the initial pay or the pay range for the position, communicated in the posting itself or in writing before the first interview.

The HRTech work this implies:

• ATS (Applicant Tracking System) integration with pay band data. Greenhouse, Workday Recruiting, SAP SuccessFactors Recruiting, Lever, BambooHR Hiring, Personio, Pinpoint, and others all need a pay range field that can be optionally published.
• Job board syndication with pay range carried through to LinkedIn, Indeed, StepStone, XING, Welcome to the Jungle, and regional boards. Most major boards already support pay range fields; the integration layer must populate them consistently.
• Internal mobility postings must follow the same rules. Internal job boards exposed by the HRIS need pay range publication too.

For 2026, the realistic vendor scope is to expose a pay-range field at requisition level, default it to publish for jurisdictions where required, and propagate it to all connected boards. Mid-2026 is also when most major customers will retrain their hiring managers on what the field actually means and how to set it.

Workflow for the mandatory joint pay assessment

When the annual report shows an unjustified pay gap above 5% in any category of worker, and the employer cannot justify or close it within 6 months, the employer must conduct a joint pay assessment with workers’ representatives. The assessment is collaborative, structured, and time-bound.

The HRIS support this requires:

• A pay-gap dashboard showing per-category gaps with statistical significance and confidence intervals.
• A justification log capturing the employer’s documented justification for each gap (objective criteria, structural reasons, prior pay actions in progress).
• A remediation tracking workflow showing what actions the employer is taking, with timelines and owners.
• A collaboration surface that includes workers’ representatives in the assessment, with structured data access scoped to what the directive requires.

This is workflow software, not analytics software. The vendors that approach pay equity purely as a dashboard miss the operational part: pay equity is an ongoing remediation function, not a once-a-year metric.

Build, buy, or bolt-on for HRIS customers

For mid-market and enterprise employers picking their compliance stack for 2026 to 2027:

• HRIS-native modules (Workday Pay Equity, SAP SuccessFactors Pay Equity, HiBob compensation, Personio compensation) are improving fast in 2026. They work well for employers with simple structures and a single HRIS as the system of record.
• Specialist platforms (Syndio, Trusaic, PayAnalytics, gapsquare from XpertHR) are deeper on methodology, statistical rigor, and remediation workflows. They typically integrate with the HRIS rather than replace it.
• Bolt-on builds on top of the HRIS data warehouse are tractable for organizations with strong people-analytics teams, but the build cost typically matches or exceeds a specialist vendor for the first 18 months.

The realistic recommendation for most 250 to 5,000 employee organizations: extend the HRIS-native module for the first reporting cycle, evaluate a specialist if the gap structure or remediation workflow proves too complex for the native tooling, and avoid a bolt-on build unless the people-analytics team has clear capacity.

For HRTech and payroll vendors, the strategic implication is clearer: customers will expect pay equity capability as table stakes by mid-2026. Vendors that ship credible features (real methodology, real statistics, real workflow) earn renewals; those that ship a dashboard alone will lose market share to specialists who fill the gap.

The transposition variance trap

The directive sets a floor. National transpositions vary above it. Germany expanded the existing Entgelttransparenzgesetz to align with the directive but added stricter information-rights provisions. France retained its existing Index Égalité Professionnelle with additional categories. Spain extended its existing transparency obligations. Ireland already had a pay gap reporting regime and is adapting it. Member states with no pre-existing scheme (most of Eastern Europe, parts of the Nordics) are building from scratch.

The HRTech implication is per-jurisdiction configuration: a single employer operating in five member states will need five different report variants. Vendors that build a configurable reporting engine win; those that hardcode the directive baseline get bug reports for years.

The shape of a transposition variance configuration:

• Reporting frequency by employer size (some member states are stricter than the directive floor).
• Reference period definition (calendar year vs payroll year, FTE conversion rules).
• Category-of-worker minimum granularity.
• Justification thresholds and joint pay assessment triggers.
• Submission format and channel per NCA.

This is configuration, not code. A vendor that treats it as code will spend 2027 and 2028 in continuous patch releases. One that treats it as configuration ships once and updates a YAML when a member state amends its transposition.

The lesson for 2026 is straightforward: the directive is not abstract any more. It is a feature gate for any HRIS serving employers above 100 workers in the EU. Vendors that ship credible pay equity capabilities by Q3 2026 will pass that gate. Vendors that wait for customer pull will lose deals to those that did not.