The EU Pay Transparency Directive, adopted in 2023 and requiring national transposition by EU member states by June 2026, is creating a compliance requirement that most enterprise HR technology stacks are not structurally equipped to meet. This is not primarily a payroll technology problem. It is a compensation data infrastructure problem — and the gap between what the Directive requires and what most organizations can currently do with their compensation data is larger than most HR leaders have internalized.
This piece is about that gap: what the Directive actually requires in terms of data flows, what the existing HR stack can and cannot handle, and why we backed Pave in 2025 as the company most likely to build the infrastructure layer that closes it for European enterprises.
What the Pay Transparency Directive Actually Requires
The EU Pay Transparency Directive has several distinct requirements that interact in ways that create compound data demands. Job applicants must be able to request information about the pay range for a role before or during the selection process. Employees must be able to request information about their individual pay level and average pay levels for colleagues performing equal or equivalent work, broken down by gender. Employers above certain size thresholds must publish pay gap reporting annually, with breakdowns by employee category.
The reporting requirement sounds straightforward until you look at what it requires in terms of data architecture. "Equal or equivalent work" is a legal concept defined by the Directive with reference to skills, effort, responsibility, and working conditions — not simply job title. An organization that has compensated people inconsistently across equivalent roles, or that does not have a robust job architecture that maps roles to compensable factors, cannot produce the required reporting accurately.
More practically: the Directive requires employers to be able to respond to individual employee information requests within specified timeframes. This means the data that produces the required comparison — individual pay, comparator average, the criteria used to determine pay levels and progressions — must be accessible in a structured, queryable form. For organizations whose compensation data lives in multiple systems, with inconsistent job architectures across business units acquired at different times, that accessibility is not a given.
The Job Architecture Problem
The foundational requirement for pay transparency compliance is a coherent job architecture: a framework that maps all roles in the organization to a consistent set of levels, compensable factors, and grade bands. Most large organizations have a job architecture in theory. In practice, most have a job architecture that was designed for the core organization and has been extended inconsistently as new business units, acquired companies, and remote workforce expansions have been absorbed.
The consequence is grade inconsistency: two employees with equivalent skills, responsibilities, and scope doing functionally similar work in different parts of the organization may be mapped to different grades and paid differently, in ways that are not defensible under a "skills, effort, responsibility, working conditions" comparability analysis. Before the Directive, this inconsistency was administratively inconvenient but legally manageable in most EU jurisdictions. After the Directive is transposed into national law, it becomes a reporting liability and potentially a legal exposure.
The work of cleaning up job architecture inconsistencies is significant, often politically sensitive within large organizations, and essentially must be completed before compliant reporting is possible. Organizations that have not started this work are going to find that the timeline is tighter than it appears — job architecture remediation for a 2,000-person company with multiple acquired entities typically takes 12–18 months if done thoughtfully, longer if done under compliance pressure with inadequate stakeholder alignment.
Market Benchmarking as a Compliance Input
An underappreciated dimension of pay transparency compliance is that it implicitly requires robust compensation benchmarking. When an employer sets a pay range for a posted role, or when they respond to an employee's request for comparator pay information, they need a defensible basis for the ranges they are using. That basis typically involves market data — what comparable roles pay in the relevant labor market — combined with the organization's own job architecture and pay philosophy.
The organizations that have invested in continuous compensation benchmarking — maintaining live market data connections rather than running annual compensation surveys — are in a meaningfully better position to produce defensible ranges than those that rely on annual consultant-produced reports. When an employee requests information about their pay relative to the market, or when a job posting needs to reflect a pay range that will survive scrutiny from candidates and regulators, the quality of the underlying market data matters.
This is part of the Pave thesis. The product's core value proposition is real-time compensation benchmarking — a continuously updated view of what roles pay across a community of participating employers, feeding into compensation bands that update as the market moves rather than aging between survey cycles. In a world without pay transparency requirements, this was a nice-to-have sophistication for compensation teams at forward-looking companies. In a world with mandatory pay range disclosure and employee information rights, it becomes closer to a compliance infrastructure requirement.
The HRIS Integration Gap
Even for organizations with coherent job architectures and good benchmarking data, there is a practical infrastructure gap: the connection between the compensation benchmarking system, the job architecture, and the HRIS that holds the authoritative employee compensation record is often indirect, manual, and insufficiently real-time for compliance purposes.
A typical workflow at an organization trying to respond to employee pay information requests under the Directive might involve: pulling current compensation data from the HRIS, cross-referencing with the job architecture to identify comparable roles, querying the benchmarking system for market comparators, and constructing a response that addresses the specific legal requirements. If any of these steps involves a manual extract, a spreadsheet, or a system that was not designed to support this query type, the workflow is slow, error-prone, and hard to audit.
We are not saying that every organization needs to replace their HRIS to comply with the Directive. We are saying that organizations that have not invested in clean data flows between their compensation intelligence tools and their HRIS are going to find compliance operationally expensive in a way that is avoidable with the right infrastructure investment.
The Timing Dynamic
Directive transposition deadlines vary by member state — some have already passed national implementing legislation, others are in progress. The compliance timeline is not uniform across the EU, which creates a tactical question for multinational European employers: do you build for the most stringent national implementation on your current footprint, or do you implement sequentially as each jurisdiction's deadline approaches?
Most of the large European enterprises we have spoken with are taking the first approach — building for the most stringent requirements across their footprint, typically driven by the jurisdictions where they have the largest employee populations and the most regulatory scrutiny. This approach has the advantage of producing a compliance infrastructure that is durable across future jurisdictions, at the cost of implementing faster and more comprehensively than a sequentialist approach would require.
For vendors in the compensation infrastructure space, this creates a well-defined commercial window. Organizations building for the most stringent standards need the infrastructure layer now, before their transposition deadline. The procurement conversations for this kind of compliance-driven infrastructure investment have a different character than discretionary HR tech procurement — the business case is clearer, the timeline is more constrained, and the stakeholder alignment is easier to achieve when legal and finance are co-sponsors rather than secondary approvers.
Beyond Compliance
The interesting longer-term thesis is that compliance-driven adoption of compensation intelligence infrastructure creates a data asset that is valuable well beyond the compliance use case. Organizations that implement robust compensation benchmarking, maintain clean job architectures, and build the HRIS integration that makes compensation data queryable will find that they can also do things they could not do before: model the cost and retention impact of compensation band adjustments before implementing them, identify populations at market-rate risk before they start churning, and make promotion decisions with clearer visibility into the compensation equity implications.
The compliance requirement is the forcing function that makes the infrastructure investment politically achievable. The ongoing value is in having compensation data that is clean, current, and structurally sound enough to support real workforce strategy. That is the bet embedded in the Pave investment, and it is the reason we think compensation intelligence is a durable category rather than a compliance-cycle opportunity.