Pay Transparency is HR's new leadership task

The EU's Pay Transparency Directive will be one of the most significant changes in HR's framework conditions in the coming years. The directive places new demands on transparency, gender pay gap reporting, and access to information, but in practice, the implications reach far beyond compliance. Pay transparency will only succeed if the organization manages to link legislation, HR practice, and leadership in a way that builds trust and a perception of fairness among employees.

In working with organizations that are already actively preparing for the directive, we see a clear pattern: those companies that succeed do not treat pay transparency as a reporting project, but as a new leadership discipline – supported by solid data, clear structures, and distinct principles for pay determination.

We don't know all the details yet – but we know the direction

The directive generally consists of two key elements: Article 7 on employees' right to information and Article 9 on reporting. However, the Danish implementation has not yet been enacted, and important nuances still need to be clarified. This includes, among other things, which specific salary components must be included, what to do in small groups of employees, and whether the reporting obligation is determined at group or company level.

A common misunderstanding is that Article 7 gives employees access to everyone else's salary. It does not. Employees have the right to request information about their own individual pay level and the average pay levels, broken down by sex, for categories of workers performing the same work or work of equal value. However, the directive has not yet determined whether these averages should be based on a snapshot or a longer period – a nuance that organizations should address now, as it affects both data handling and expectation management.

Similarly, there is uncertainty regarding Article 9. Many believe that the reporting obligation is calculated in FTEs, or that employees covered by collective bargaining agreements are exempt. However, the EU's definition is based on the number of employees – "heads" – and employees covered by collective agreements will also be included, because the remuneration package in practice often consists of more than just basic salary.

Even though all the details are not yet in place, the direction is clear: organizations must be able to categorize employees into comparable groups and establish an overview of the total remuneration package.

Data is the foundation – but rarely ready

A pay analysis is never better than the data it is based on. In practice, pay data is often fragmented and difficult to analyze. Payroll systems contain hundreds – often thousands – of wage codes, where some are pensionable or holiday-qualifying, others are not, and where hourly-paid, part-time, and full-time employees cannot be easily compared.

Therefore, simply extracting numbers directly from the payroll system is rarely sufficient. Before pay can be compared, it must be normalized to create a fair and accurate foundation. This requires clear decisions on which pay components are included and how they are calculated. For example, overtime or night shift premiums are not in themselves expressions of discrimination, whereas personal allowances and bonuses can be problematic if they cannot be explained based on objective and gender-neutral criteria.

Job architecture: from compliance to leadership tool

All organizations will need to categorize employees within a job architecture if they want to meet the directive's requirements. Without a clear job architecture, you simply do not know which jobs are comparable.

Working with job architecture often reveals more than just the organizational chart. When organizations begin to align job levels and clarify responsibility and complexity, it becomes visible where there have historically been variations in titles, roles, and pay practices. It is not unusual for the same title to cover vastly different responsibilities across locations or units – and this makes comparing and explaining salaries difficult.

This is often where things go wrong if job placement is based too narrowly on department or title. Job architecture is about evaluating the job itself – the "chair" – not the person sitting in it. Only when this foundation is in place does it become possible to explain pay differences in a way that is experienced as fair by both managers and employees. At the same time, the structure creates a common language that can be used more broadly within the organization – for example, in connection with career paths, competency development, and internal mobility.

Pay transparency is a leadership task

Pay transparency truly becomes a leadership task when it is operationalized in everyday life. Many organizations find that even after pay differences have been addressed, they appear again unless clear pay bands, pay policies, and governance are introduced at the same time.

Managers must be able to explain why an employee is positioned where they are – and why salary increases are given or not given. In a more transparent reality, it is not enough to just refer to the market or individual negotiation skills. Decisions must be explainable using data and objective criteria.

This places new demands on leadership competencies. Making data-driven decisions requires both clear frameworks and access to valid data. When data is made available in a structured format, it changes character from a control tool to a dialogue tool: managers get a better overview of their employees, can identify discrepancies, and support more consistent decisions across the organization.

Human reactions and organizational maturity

Salary is still a taboo subject in many organizations, and work with pay transparency is often met with both uncertainty and distrust. Employees do not necessarily speak about the same "pay" – some focus on base salary, while others include pension and supplemental pay components.

Experience shows that open and honest communication is essential. Organizations do not need to have all the answers from day one, but they must be clear that pay transparency is a process. When a shared reference framework is created for how salary is determined – based on skills, effort, responsibility, and working conditions – greater security and trust gradually emerge.

At the same time, it is important to demystify the complexity. Pay transparency is not rocket science and does not require advanced statistical models. Most organizations can start with relatively simple tools and an open discussion about which values should underpin pay determination: seniority, location, education, performance – and how these parameters are applied objectively.

What should organizations do now?

Even though all the details of the legislation are not yet in place, there are a number of steps that organizations can take with advantage right now:

1. Create an overview of pay data and decide which pay components are included – and how they are calculated.

2. Build or clarify a job architecture where all employees are placed in comparable groups.

3. Involve managers early and prepare them for the task – both in job placement and pay dialogue.

4. Establish clear principles for pay determination, pay bands, and the necessary governance.

5. Communicate openly about the process and the purpose – also about what you do not know yet.

6. View pay transparency as a business-wide task, not just an HR task.

Pay transparency will only succeed if the organization manages to link legislation, HR practice, and leadership in a way that builds trust and a perception of fairness among employees.

Conclusion

In the end, pay transparency is not just about complying with a directive. It is about what kind of organization you want to be – and whether you want to be able to stand by the principle of equal pay for equal work.