A recruiter has a vacancy ready to publish, a manager wants flexibility on salary, and payroll holds different records for staff employed across several countries. HR must decide which pay range to disclose, which employees count towards reporting thresholds and who will answer a worker's request for pay information.
The EU pay transparency directive makes those questions connected. For distributed employers, compliance starts with identifying the legal employer and applicable national law, not by adding a salary band to a global advert.
What the pay transparency directive requires, and by when
7 June 2026 was the deadline for national transposition, and that date has now passed. For HR teams, the practical question is which national implementing laws are in force in each country where they employ people, and what each one demands.
Take a business whose EU workforce sits across several subsidiaries. A consolidated headcount alone will not establish its obligations. Each legal employer must be assessed against the counting rules in the country whose law applies to it, the same way payroll registration is assessed entity by entity rather than at group level.
Pay transparency directive key dates
The EU Pay Transparency Directive, Directive (EU) 2023/970 was signed on 10 May 2023, entered into force on 6 June 2023, and sets the transposition deadline plus the staged reporting timetable below.
| Date | What the directive requires | Who it affects |
|---|---|---|
| 7 June 2026 | Deadline for member states to transpose the directive into national law | All employers in EU member states, subject to the scope of each obligation |
| 7 June 2027 | First annual gender pay gap report due | Employers with 250 or more workers |
| 7 June 2027 | First three-yearly gender pay gap report due | Employers with 150–249 workers |
| 7 June 2031 | First three-yearly gender pay gap report due | Employers with 100–149 workers |
Reporting is the last obligation to arrive. The directive establishes a framework for equal pay for equal work or work of equal value, covering salary and complementary or variable pay, and its hiring-stage disclosure and worker information duties apply well below the reporting thresholds. An employer with 80 workers in a member state has no report to file, but still owes candidates and staff the pay information the national law requires.
Scoping rule: Start with the legal employer, then apply the counting rules in the national law that governs it. A group total and a country total each leave the question unanswered.
For distributed teams, that means counting workers per employing entity under each applicable law. Splitting one employer's workforce into separate country totals understates headcount; merging subsidiaries that share a parent overstates it.
This quarter, HR should fix a working headcount snapshot date and record each worker's legal employer, work country and applicable legislation. Where two national counting methods differ, retain both calculations rather than forcing them into a single global total, because the entity that triggers a 2027 report in one country may sit under the threshold in another.
Running pay transparency compliance across countries
A worker may live in one country, report to a manager in another and be employed through an Employer of Record in a third. The manager's location alone doesn't settle which employment rules apply.
The European Commission's response on national implementation explains that the directive sets minimum standards, while national laws may add requirements and use different penalties or procedures. A global job advert therefore needs a country-specific review, even when every applicant sees the same vacancy.
Reporting regimes for multi-country employers
| Jurisdiction | Employer threshold | Reporting timing | Publication deadline |
|---|---|---|---|
| European Union, under national law | 100 or more workers | Annual for 250 or more; every three years for 150–249 and 100–149 | Set nationally, with transposition due 7 June 2026 |
| United Kingdom, England, Scotland and Wales | 250 or more employees | Snapshot 31 March for most public authorities; 5 April for other employers | Within one year: 30 March for most public authorities; 4 April for other employers |
| Australia, Workplace Gender Equality Act 2012 | 100 or more employees | Reporting period 1 April to 31 March | Lodge between 1 April and 31 May |
For a group with British subsidiaries, the UK government's reporting guidance applies the 250-employee threshold separately to each legal entity, using the snapshot dates and deadlines shown above. A parent company's consolidated report doesn't replace that assessment.
Covered UK employers must publish their results online, allowing candidates and staff to compare outcomes, under the UK guidance on when to report. This is a separate regime, not an extension of EU reporting.
Australia's Workplace Gender Equality Agency reporting rules generally cover private-sector and Commonwealth public-sector organisations with 100 or more employees, using the reporting period and submission window shown above. Previously reporting employers remain within scope when they employ 80 or more people.
Build a country operating matrix
A practical global employment assessment should record:
- Recruitment rules: Advert wording, permitted pay questions and disclosure timing.
- Worker rights: Request routes, response ownership and escalation contacts.
- Reporting controls: Thresholds, counting methods, data ownership and submission responsibility.
For Employer of Record arrangements, contracts should identify who keeps pay records, answers requests and submits reports. Contractual allocation doesn't override legislation: the EOR's legal obligations and the client's duties must both be checked.
Pay information employers must share during hiring
- Disclose the initial pay or range. Provide it before the relevant interview, or in the advert where applicable national law requires that.
- Remove pay-history questions. Check application forms, recruiter scripts and agency instructions, not just vacancy text.
- Match the range to the grade. This is an operational control that helps explain the offer, rather than a separate disclosure rule.
- Keep the candidate-facing record. Save the advert version, range and any subsequent explanation communicated to the applicant.
The distinction matters: disclosure and the pay-history prohibition are legal requirements under the framework. Grade alignment and record retention are practical ways to demonstrate a consistent process.

When an offer falls outside the range
Consider a hypothetical vacancy advertised at EUR 48,000 to EUR 56,000. After informally asking about previous salary, the recruiter offers EUR 60,000.
The pay-history question is the immediate compliance problem. The higher offer also needs an explanation: has the role changed level, or is there an objectively supported skills premium?
A higher offer isn't automatically unlawful because it exceeds the advertised range. However, an undocumented exception makes it harder to explain why comparable candidates or employees receive different treatment.
An exception needs a reason that can be applied consistently, not merely a manager's approval.
Recruiters should pause an out-of-range offer, confirm the role's scope and record the relevant factors. If the job has changed materially, the candidate-facing information should be corrected rather than leaving an obsolete range in circulation.
For practical context on communicating salary expectations, hiring insights from Filta provide a recruitment perspective. That perspective complements, but doesn't replace, checking national advert requirements and penalties.
Before a hiring team posts a remote job, its vacancy checklist should capture eligible countries, employing entity, approved band, disclosure timing, application questions and the person authorised to approve exceptions. A single-page sign-off can connect the advert to the offer without turning every hire into a legal project.
How workers can request their pay information
Workers can request written information about their individual pay level and average pay levels, broken down by sex, for workers doing the same work or work of equal value; employers must respond within two months, as described in the OECD's Pay transparency in progress.
The request is like asking to see a building's drawings rather than only its finished frontage. A salary figure shows the outcome; the underlying job structure explains how the employer reached it.
What makes the explanation defensible
A usable pay structure needs more than a list of titles. HR should be able to connect each employee's work to:
- Role families and levels: Consistent descriptions of responsibility and scope.
- Work-value factors: Skills, effort, responsibility and working conditions.
- Progression rules: The criteria for moving through a range or into another level.
- Comparison populations: The workers included and the reason for their inclusion.
Say engineers in different countries perform comparable work, but one receives a location-related market premium. The employer should retain the premium's basis, approval and review criteria, then check whether equivalent cases receive equivalent treatment.
Location isn't an automatic justification just because it appears in a spreadsheet. The explanation needs to show what the premium addresses and why the employer considers it relevant under applicable law.
Titles aren't the test
Matching titles can hide different responsibilities, while different titles can describe work of equal value. A designer and a technical specialist may require a work-value assessment even though they sit in different departments.
Performance, scarcity, tenure and negotiated terms also need scrutiny. Recording a reason doesn't establish that it is objective or lawful, and prior salary shouldn't become an unexplained anchor for current pay.
HR should map roles to levels before requests arrive, with supporting rationale held alongside the pay records. A named request owner should then coordinate payroll, compensation and legal input, rather than assembling a comparison group hurriedly after receiving an email.
Gender pay gap reporting and the 5% trigger
Now that 7 June 2026 has passed, treat the trigger as live rather than pending, and scope it per legal entity and per country. EU national implementing rules can sit alongside separate UK and Australian reporting routes, so a group may be inside one regime and outside another.
The European Commission's explanation of the reporting framework sets a joint pay assessment where an unjustified gender pay difference of at least 5% in average pay within a worker category remains uncorrected for six months. The assessment must involve worker representatives.
Treat 5% like an alarm threshold: reaching it starts a formal check. In a hypothetical category of 40 analysts where women earn 6.2% less on average, with no objective, gender-neutral explanation, the employer should investigate and correct the difference inside the remediation window. If the conditions remain met, the joint assessment follows.

Calculate more than a headline gap
A reporting workflow should calculate:
- Overall mean and median gaps: Different views of the distribution of pay.
- Representation by pay quartile: The distribution of female and male workers across pay bands.
- Variable-pay participation: Who receives bonuses or other variable compensation.
- Category-level differences: Comparisons within equal-work or equal-value groups.
The organisation-wide gap and unequal pay answer different questions. A wide headline gap may reflect who holds senior roles, while a category result can expose differences between comparable workers. Keep both readings: one points to progression and access to higher-paid work, the other to pay treatment inside comparable populations.
Make every calculation reproducible
Payroll and HR should agree the denominator, snapshot date, worker categories, exclusions and treatment of variable pay before running the calculation. Changing those definitions between reports can make apparent progress impossible to interpret.
Audit check: Another analyst should be able to reproduce the result from the saved dataset and calculation rules.
A global payroll review should cover data definitions and entity boundaries as well as whether payments reach employees correctly. Local-currency values, conversion methods and reporting groupings should remain traceable, especially where the same group reports under more than one national regime.
A documented explanation should be tested before it is accepted. If an employer cites performance, HR should check the assessment method and consistent application; if it cites a premium, the review should examine who qualifies and why.
Publication is the output. The remedy sits in recorded pay-review decisions, corrective adjustments, named owners and recurring audits that show whether the last cycle's action worked.
Practical compliance steps for global hiring teams
The sequence matters because recruitment controls and reporting calculations both depend on a consistent job structure. A spreadsheet of salaries won't compensate for unclear role definitions.

Put the controls in order
Map role families and levels across countries. Use a shared architecture, with local detail where necessary. Separate national grading systems become a problem when nobody can explain how they compare.
Set ranges by role and location. Record the rationale for differences and the approval route for exceptions. Regional discretion without supporting records makes later reviews difficult.
Update adverts and application forms together. Use consistent job descriptions and remove previous-salary fields from the applicant tracking system. Updating only the visible advert leaves an avoidable gap.
Train recruiters and hiring managers. Cover disclosure timing, prohibited questions and escalation. Refresh the guidance when national requirements change rather than treating training as a completed task.
Build a traceable pay dataset. Preserve local-currency values, normalised comparisons, snapshot dates and headcount by legal entity. Don't merge entities to make a dashboard easier to read.
Run an internal gap review annually. This is a recommended control, separate from statutory reporting frequency. Document category-level concerns and keep the calculation method stable.
Assign country-level ownership. Name the data owner, request handler and escalation contact. Shared inboxes need tracked deadlines, not an assumption that somebody else has replied.
A useful readiness test is whether a recruiter can explain an offer from its approved range and supporting rationale within a minute.
That test isn't a legal standard. It shows whether the underlying decisions are clear enough for the people who must communicate them.
Confirm your position before the 2027 reporting date
Before the first reporting milestone, HR should confirm the legal entities, countries and headcount bands in scope. The review should also establish which national implementing laws are effective, rather than treating the transposition deadline as proof that every country completed implementation identically.
Separate legal responsibility from administration
In-house employment, an Employer of Record arrangement and a global payroll partner serve different purposes. A payroll provider may administer records without becoming the employer; an EOR arrangement requires a different allocation of responsibilities.
Record who holds the data, who answers worker requests and who reports in each country. A company-wide provider decision won't settle every local obligation.
We Are Distributed advises 600+ employers on employing staff compliantly wherever they live. Its advice is vendor-neutral and recommends the route that fits, not whichever provider pays the most commission; providers pay We Are Distributed a referral fee when an advised company signs with them.
This week, HR should list headcount by country and legal entity, identify which employer holds each staff group, and send that register to its legal or advisory contact for review. That concrete scope check should come before approving another global compliance plan.
