Pay transparency regulation has moved faster than most HR functions anticipated. The EU Pay Transparency Directive set a 2026 transposition deadline for member states, with substantive reporting and disclosure obligations following shortly after. A growing list of US state jurisdictions has introduced pay-range disclosure and reporting requirements over the past three years, with several more under active legislative consideration. Comparable rules have appeared in parts of Canada, the UK, and the Asia-Pacific region.
The cumulative effect is that an HR function operating across multiple jurisdictions now faces a transparency regulatory perimeter that did not exist three years ago. The compliance work is substantial, the structural work underneath it is more substantial still, and most HR functions did not budget for either at the scale the rules are now demanding.
What the rules actually require
The visible part of pay transparency regulation is the disclosure side. Job postings in covered jurisdictions need salary ranges. Internal candidates need access to range information for roles they apply to. Employees need information about their own pay relative to defined comparator groups. These are the requirements that have received most public attention because they are the parts that immediately affect candidate and employee experience.
The less visible part is the structural work the disclosure requirements imply. To publish accurate salary ranges, an organisation needs defined pay structures with clear band boundaries, consistent role architecture across the workforce, and pay decisions documented well enough to withstand challenge if a disparity is identified. To respond to employee information requests about pay comparators, the organisation needs role-level comparator groupings that hold up under scrutiny. To produce the reporting that most of the new rules require, the organisation needs data infrastructure capable of producing accurate workforce-level pay-equity analysis at defined intervals.
Many HR functions have done parts of this work, particularly the larger and more sophisticated ones. Few have done all of it across all the jurisdictions they operate in, and the pace at which the rules are now demanding it is faster than the typical comp programme refresh cycle would deliver.
The band design problem
The most operationally demanding piece of work for most HR functions is the band design layer. Salary ranges that get published need to be defensible. They need to reflect a coherent view of how the organisation values different roles, and they need to be consistent enough across similar roles to avoid producing transparency-driven internal disputes that the organisation cannot defend.
Most comp programmes have had bands of some kind for years, but the quality and discipline of band design varies considerably. Bands that were maintained loosely, with substantial overlap, ad hoc exceptions, and inconsistent role mapping, have generally worked acceptably when pay information was confidential. They work much less well when ranges are public and employees can compare them against their own pay and against advertised ranges for similar roles.
The work to tighten band design is not glamorous. It involves auditing role mappings, reviewing band structures for internal consistency, reconciling historical pay decisions that may not fit cleanly into the tightened structure, and producing documented decision logic for the boundary cases. It is also the work that most comp teams are now doing under time pressure, with regulatory deadlines that do not allow the multi-year refresh cycle that this work would normally take.
The audit-trail problem
The second structural piece is documentation and audit infrastructure. The EU Pay Transparency Directive in particular contains employee information rights that allow individuals to request information about pay levels for their comparator group, and reporting obligations that require workforce-level gender pay-gap disclosure with explanations and remediation commitments for gaps above defined thresholds.
This requires the underlying pay data to be in a state that supports those obligations. Pay decisions need to be traceable to documented logic, including a job evaluation, a market benchmark, a performance differentiation, or a defined exception process, rather than recorded as opaque outcomes. Comparator groups need to be defined consistently. Historical pay decisions need to be reconcilable with the current pay structure.
The work to bring legacy pay data into this state is also substantial, and it is not work that comp technology vendors can fully solve. The vendor tools have improved significantly over the past three years, with stronger pay-equity analysis capabilities, better band-management interfaces, and clearer reporting outputs. But the underlying decisions about role mapping, band structure, and exception governance still need to be made by the HR function, and the data quality work to support those decisions still needs to be done.
What the budget gap looks like in practice
The combination of band design work, audit-trail work, and ongoing reporting work has produced a comp programme workload that is materially larger than most HR functions planned for. The visible signs are familiar across the market.
Comp team headcount has increased in most large organisations operating across affected jurisdictions, but typically by less than the workload increase would suggest. The gap is being absorbed through external consultancy support, internal redirection of HR resources from other priorities, and a meaningful amount of senior comp practitioner time spent on programme-level work rather than the strategic and analytical work the role used to focus on.
The technology budget picture is similar. Comp technology spend has grown substantially, but most of the spend is being absorbed by reporting and disclosure infrastructure rather than the higher-value analytical capabilities the same tools also offer. HR functions that wanted to invest in pay-for-performance analytics, total rewards optimisation, or comp-related workforce planning are finding that their comp technology budget is being consumed by compliance work first.
Where the function is heading
The HR functions that are managing this transition best have generally treated it as a multi-year programme rather than a series of jurisdictional compliance projects. They have used the regulatory pressure to drive a band design refresh that they would have done anyway, more slowly, over a longer cycle. They have invested in pay-equity analytics capabilities that produce regulatory reporting as a by-product of doing better comp analysis generally. They have built the audit-trail discipline into their normal pay decision processes rather than as a parallel compliance track.
Organisations that have approached pay transparency as a narrow compliance exercise have generally found themselves repeating substantial work for each new jurisdiction. The cumulative cost has been higher than the programme approach, the resulting pay infrastructure has been weaker, and the HR function has had less to show for the investment when the dust settles.
The broader observation is that pay transparency regulation is doing something to the comp function that comp leadership has often wanted to do anyway. It is forcing investment in band discipline, role architecture, and pay-decision documentation that the function has historically struggled to fund. Whether that proves to be a net benefit depends largely on whether HR functions can capture the broader value of that work rather than treating it as pure regulatory overhead. The regulatory perimeter is likely to keep expanding, and the comp programmes that have already absorbed the structural work will find each new jurisdiction meaningfully easier to add than the first one was.
