The March 2026 readiness gap: what European employers actually have in place for EU pay transparency

Every company we spoke with knows the EU Pay Transparency Directive is coming. Not one denied it applies to them. But knowing and doing are different things, and the gap between the two is wider than most HR leaders would publicly admit.

The majority of companies in our study are in what we call a pre-activation phase: aware of the directive, partially prepared, but waiting for national transposition before committing to major operational changes. This wait-and-see posture feels rational until you consider what must happen before the first report is due in June 2027. Building compliant pay structures and connecting performance data to compensation decisions alone takes quarters, not weeks. Add reporting infrastructure on top, and the timeline gets uncomfortable fast.

The directive doesn't just require companies to disclose pay gaps. It requires them to explain those gaps using documented, objective, gender-neutral criteria. For most organizations, that explanation doesn't exist yet.

This study maps where European employers actually stand, what they're worried about, and what "compliance" means to them in practice. The picture is honest, uncomfortable in places, and more useful than any checklist. (For readers new to the directive, our EU Pay Transparency resource center covers the full regulatory framework.)

The directive's transposition deadline is June 7, 2026. The first pay gap reports are due by June 2027 for companies with 150+ employees and by 2031 for those with 100-149 employees. (Full breakdown in our guide to EU Pay Transparency Directive requirements.) Every organization we interviewed knows this is coming and accepts it applies to them. Awareness is universal. Urgency is a different story.

Across the companies surveyed, we identified four distinct postures toward the June 2026 deadline:

The "wait and see" group. These companies are aware but have postponed major initiatives until their country finalizes national legislation. The reasoning is straightforward: why invest in structural changes when the specific local requirements might differ from the directive's baseline? This was the most common posture. It is also the riskiest.

The cautious movers. A smaller group has begun preliminary steps, driven primarily by legal and reputational risk concerns. They're not overhauling their pay systems yet, but they've started internal assessments and conversations with legal counsel. For these organizations, compliance is a risk management exercise.

The "natural evolution" group. Some companies, particularly those with mature people and culture functions, view pay transparency as an extension of work already underway. They don't treat the directive as a separate compliance project. It's folded into broader HR transformation and employer branding initiatives.

The still strategizing. These organizations are aware and have had internal conversations about the directive, but haven't yet moved from discussion to execution. They're evaluating options, comparing tools, and waiting for clearer signals before committing resources. Budget conversations have started but haven't landed. The directive is on the agenda, but it's competing with other priorities.

The pattern across all four groups is the same: awareness runs ahead of action by a significant margin. With first reports due by June 2027, that leaves twelve months to build compliant pay structures, clean data, connect systems, and produce auditable reports.

Article 4 requires that pay structures be built on objective, gender-neutral criteria: formal job classification, documented grading, and salary bands that connect roles to pay ranges in a way an auditor can follow. Can you explain how pay is determined for any given role in your organization? For roughly half the companies in our study, the honest answer is no.

The divide is clear. Some organizations have invested in formal job grading and classification systems. They've worked with compensation consultancies, defined role levels, and built salary bands that connect job families to pay ranges. These companies have a foundation to build on, even if it needs updating to meet directive compliance requirements.

The other half operates differently. Their salary structures are informal, partially defined, or not documented at all. Pay decisions were made over the years through individual negotiations, manager discretion, market pressure at the time of hiring, or simply by matching a previous employee's earnings. The result is a pay structure shaped more by history than by design.

Several HR leaders acknowledged a specific vulnerability: they cannot currently explain why two people in equivalent roles earn different amounts. The gap may be justifiable. It may reflect different experience levels, performance records, or scope of responsibility. But the justification was never written down, and the criteria were never formalized.

Under Article 7, employees can request information about pay levels for categories of workers doing the same work or work of equal value. If the criteria aren't documented, the employer has no defensible answer.

When a pay gap report reveals a difference of 5% or more between men and women in the same job category, the directive doesn't stop at disclosure. Article 10 triggers a joint pay assessment: the employer must work with employee representatives to analyze the causes of that gap and show that it can be explained by objective criteria. Performance, experience, and scope of responsibility—these are the kinds of evidence regulators will expect. But that evidence only works if it's been documented and connected to the actual pay decision. (We explored this connection in depth in our analysis of how performance data shapes compliance.)

In the majority of companies we surveyed, performance evaluation and compensation decisions operate independently. Performance reviews happen on one cadence, managed by one team, stored in one system. Pay decisions happen on a different cadence, driven by budget cycles and manager recommendations, tracked in payroll. The two processes run in parallel without a documented connection between them.

This separation persists even in organizations with mature performance management practices. The issue isn't that companies don't evaluate performance. Many do, and do it well. The issue is that performance outcomes are not formally linked to pay decisions in a way that produces an auditable trail.

For companies operating as part of international groups, the fragmentation compounds. Local HR teams manage performance. Headquarters manages payroll and compensation frameworks. The performance standards applied in one country may differ from those applied in another, even for equivalent roles. Producing a consistent, group-wide picture of performance-linked pay is a data engineering problem before it is a compliance one.

The directive doesn't use the words "performance management." But its requirements make performance data essential.

Compliance reporting requires data from across the organization, including compensation, job classifications, headcount by gender, and performance records to justify gaps above 5%. For companies with 250+ employees, this is annual; for those with 100-249 employees, every three years. (Our compliance timeline and checklist maps every deadline.) The data needed exists within most organizations. The problem is where it lives and how it connects.

We surveyed companies across automotive, IT, HR, legal, banking, consulting, manufacturing, and more. For more than 27% of them, payroll, HR, and performance data live in entirely separate systems. For companies within international groups, the picture gets worse: these systems are often split between local offices and headquarters, sometimes across different countries, platforms, and reporting standards.

None of these systems talk to each other by default. Producing a compliance report that correlates pay levels with job categories, performance ratings, and objective criteria requires manual extraction from multiple sources, reconciliation of different data formats, and assembly into something a regulator would accept. That's a multi-week project.

Companies with international group structures face an additional layer. Several respondents described a split between local and headquarters systems: HR and performance were managed locally, while compensation frameworks and payroll were managed centrally. The data is available, but it's distributed across organizational boundaries, sometimes across different platforms, languages, and reporting standards.

Smaller organizations have the opposite challenge. Their data is simpler, often concentrated in fewer systems or even managed in spreadsheets. But they lack automated reporting capability. Compliance for a 120-person company might mean an HR manager manually assembling pay gap data in Excel, cross-referencing it with a separate performance tracking sheet, and producing a report that meets regulatory standards they're still learning.

Several companies told us they have the information needed for a pay equity analysis but have never actually run one. No simulation, no gap analysis, no preview of what a regulatory report would reveal. A manual, multi-system extraction process might be feasible once. Sustaining it as a recurring annual or triennial obligation is where the model breaks down.

We asked HR leaders what concerns them most about implementing pay transparency. The answers were revealing, not for what ranked highest, but for what didn't. (Our directive requirements guide covers the enforcement and remedies framework in detail.)

Regulatory fines are not the primary fear. They're mentioned, acknowledged as real, and then set aside. The risk that dominates leadership conversations is more immediate and more personal: what happens when employees start comparing?

Employee reactions. This was the most frequently cited concern across the study. HR leaders worry that salary transparency will trigger comparisons, internal conflicts, and formal grievances. The fear isn't abstract. Several respondents described specific scenarios they're anticipating: employees discovering that a colleague in an equivalent role earns more, teams learning that historical pay decisions created gaps that have no documented justification, and managers being asked to explain decisions they inherited from predecessors.

Cost exposure. When pay gaps become visible and can't be explained by objective criteria, the most likely outcome is a salary adjustment. Bringing underpaid employees up to equitable levels is the right thing to do, but it hits payroll budgets. Several companies flagged this as a budgeting challenge they haven't yet quantified.

Legal and financial penalties. The directive introduces meaningful enforcement mechanisms: financial penalties set by member states, a reversed burden of proof (the employer must demonstrate no discrimination occurred), uncapped compensation for affected workers, and potential exclusion from public procurement. Companies are aware of these consequences, but they feel distant compared to the internal concerns.

Historical incoherence. Some HR leaders expressed a specific anxiety: pay decisions made years ago, under different leadership, following different logic, with no documentation. Those decisions created the current pay landscape. The directive asks them to explain a structure they didn't design and can't fully reconstruct.

Relative confidence. A minority of companies, particularly those with established people and culture frameworks, reported minimal anxiety. For them, transparency is consistent with how they already operate. They see the directive as validation of what they already do.

We asked every respondent the same question: what does successful compliance look like for your organization? The answers were consistent and telling.

Not a single respondent defined success in aspirational terms. No one said "becoming a more transparent employer", "building a fairer compensation culture", or "using pay equity as an employer brand differentiator." The definitions were entirely defensive:

• Be legally compliant. Meet the requirements. Check the boxes.
• Avoid fines. Stay below the regulatory threshold.
• Have documented procedures. Policies and processes that can withstand scrutiny if audited.
• Be able to explain pay decisions. When asked why a gap exists, have a defensible answer.
• Avoid internal conflicts. Prevent employee grievances triggered by pay disclosure.
• Minimize salary adjustments. Close unjustified gaps without significant payroll cost increases.

The language of success across our respondents is the language of risk reduction. Control. Clarity. The absence of negative outcomes. HR leaders are not buying into a vision of workplace transformation. They want tools and guidance that reduce their exposure, and confidence that when the first report is due, they'll be ready. The emotional job to be done is relief.

But if every competitor approaches pay transparency as a compliance burden, the organizations that move first and treat it as a structural advantage will stand apart. Transparent pay structures attract talent. Defensible compensation decisions reduce turnover. Proactive equity analysis prevents the costly adjustments that reactive compliance produces. The companies in our study aren't thinking this way yet.

This study is part of Mirro's EU Pay Transparency resource center.