EU Pay Transparency: Is Your HR Document Evidence Ready for Employee Requests and Pay Assessments?

A pay-transparency response needs more than a number from payroll. HR must be able to explain the job category, pay criteria, calculation, approval, and information released. Those records often sit across recruiting, HR, payroll, analytics, and document systems.

Build the workflow around three outcomes: preserve approved pay criteria, answer worker requests consistently, and reproduce reports and assessment decisions. Keep payroll and HR systems authoritative for the facts they own.

Start with the applicable rules

Directive (EU) 2023/970 set a national transposition deadline of June 7, 2026. For each legal entity and country, confirm the implementing rules, effective dates, reporting scope, and responsible owner before configuring deadlines or responses.

The Commission’s pay-transparency explanation covers recruitment pay information, worker access to pay information, reporting, and assessments. Worker-request rights and reporting thresholds are separate parts of the framework; a reporting threshold should not become a blanket rule for rejecting a worker’s request.

Scope reviewed: November 9, 2026. This guide explains the EU framework and its evidence needs. The organization’s HR and legal owners approve the applicable national rules and workflow configuration.

Connect each workflow to the evidence it needs

1. Preserve approved criteria and recruitment material

Version job descriptions, categories, pay ranges, and evaluation criteria. Link them to the legal entity, country, role, and effective period. Keep the basis for category changes rather than rewriting the historical explanation.

The EU framework provides for applicants to receive starting-pay or range information before the interview, including through the vacancy notice, and prohibits asking about pay history. Preserve the approved material and delivery evidence, and check templates, recruiter packs, and integrations for obsolete salary-history fields.

Use the Commission’s gender-neutral job-evaluation resources when designing the process. Record the factors, evidence, reviewers, and resulting category. If analytics or AI assists, retain the relevant inputs, rule or model version, and human decision; an automated score is not proof of objective treatment.

2. Handle worker requests as controlled cases

The framework gives workers access to their individual pay level and average pay levels, broken down by sex, for categories doing the same work or work of equal value. Article 7 sets a response window of no more than two months. Apply the applicable national deadline and record when the request was made.

1. Register: identify the requester or authorized representative, entity, scope, owner, and due date.
2. Calculate: retrieve approved source data and record the category definition and calculation version.
3. Review: check accuracy, required information, privacy, accessibility, and approval.
4. Deliver: issue the approved response through the permitted channel and retain correspondence and delivery results.

Small groups can reveal another worker’s pay. Article 12 allows national safeguards involving designated representatives or authorities. Apply the lawful disclosure route; do not silently replace the worker’s entitlement with an invented group-size threshold or blanket refusal.

3. Make reports and follow-up decisions reproducible

For each period, retain the source extract identifiers, category mappings, transformations, calculation settings, quality checks, final report, and approval. Store raw compensation data separately from employee-facing or public outputs, with access limited to the people who need it.

For employers subject to reporting, Article 10 requires a joint assessment when all three conditions are met: a reported category gap of at least 5%, no objective gender-neutral justification, and no remedy within six months after report submission. Record each condition and involve workers’ representatives as required; a 5% dashboard alert alone is insufficient.

Open a follow-up case for the analysis, consultation, approved action, owner, deadline, and outcome. Link corrections to the issued report without overwriting the earlier evidence.

Example: the job category changes during a request

1. Capture the basis for the response

   A worker’s request is assigned a due date. The case records the relevant entity, category definition, pay data, and calculation rules.

2. Review a proposed category change

   HR approves a new job-evaluation model while the request is open. The responsible reviewer determines which definition applies to the response and records why. The calculation does not silently switch to the latest mapping.

3. Approve and retain the response

   The final package links the chosen definition, calculation, privacy decision, and approval. A later clarification can be answered from that evidence while preserving the original request date and correspondence.

Protect the evidence and test the process

Apply access controls to both records and exports. Retain only the compensation data needed for the approved purpose, with class-specific retention and applicable holds. Closing a request should not erase evidence needed for a dispute, and a dispute should not make every compensation record permanent.

• Change a pay range or category definition. Show which version supported an earlier decision or response.
• Submit a worker request for an entity below a reporting threshold. Show that request handling uses the applicable rules independently.
• Test a small category with re-identification risk. Show the authorized review and disclosure route.
• Correct a report and attempt an unauthorized raw-data export. Show preserved history and enforced permissions.