Why the EU Pay Transparency Directive will change how companies hire through Employers of Record
Introduction:
For years, many companies treated Employer of Record hiring as the fast lane into Europe.
No entity? No problem. Need to hire in Germany, France, Spain, the Netherlands, Poland, or another European market? Sign with an EOR, let the provider issue the employment contract, run the payroll locally, handle statutory obligations, and move on.
That model is not going away. But it is entering a new compliance era.
The EU Pay Transparency Directive must be transposed into national law by 7 June 2026. On the surface, this may look like another HR compliance topic: salary ranges, equal pay, gender pay gap reporting, candidate transparency. Important, but manageable.
That would be the comfortable interpretation.
The rebellious interpretation is different: the Directive will expose one of the most uncomfortable questions in the EOR model.
If the EOR is the formal employer, but the client company defines the role, salary, budget, seniority, candidate profile, hiring manager, and hiring decision — who is truly accountable for pay transparency compliance?
The answer is not convenient.
Both are.
The EOR may sign the employment contract. But the client usually controls the economic reality. The EOR may run payroll. But the client usually decides what the role is worth. The EOR may be the legal employer. But the client often owns the job architecture, internal equity logic, performance expectations, and commercial budget.
The EU Pay Transparency Directive will force both sides to stop hiding behind the structure and start documenting the logic behind pay.
Welcome to Europe’s next EOR compliance trapdoor.
The Directive in one sentence
The EU Pay Transparency Directive is designed to strengthen the principle of equal pay for equal work or work of equal value between men and women by introducing transparency, information rights, reporting obligations, enforcement mechanisms, and stronger remedies.
That sounds simple. But the practical consequences are significant.
The Directive affects recruitment, job advertisements, pay ranges, employment contracts, pay structures, employee information rights, reporting, pay-gap analysis, and remediation. It also challenges companies to explain how compensation decisions are made.
Not vaguely. Not through “market benchmark” language alone. Not through “this is what the candidate asked for.” But through objective, gender-neutral criteria.
This is a direct hit to informal hiring practices.
And EOR hiring is often full of informal practices.
A business unit wants a worker in Europe. The hiring manager defines the role loosely. Talent acquisition benchmarks the salary casually. Finance approves a budget. The preferred candidate negotiates. The EOR is then asked to employ the person at the agreed salary. The employment contract appears. Payroll begins.
Everyone moves quickly.
But after the Directive, speed needs structure.
The salary range must be explainable. The role level must be defensible. The hiring process must avoid prohibited questions. The data must be retrievable. The division of responsibilities between EOR and client must be clear.
The old EOR model was built around access.
The new European EOR model will need to be built around evidence.
Salary range transparency: the end of “we’ll decide later”
One of the Directive’s most important recruitment obligations is that applicants must receive information about the initial pay or pay range for the role. That information must be provided early enough to support an informed and transparent pay negotiation.
For EOR hiring, this changes the workflow.
A client company should not treat the salary range as something to be decided at the end of the process, after the best candidate has been identified. The range should exist before the hiring process moves too far — ideally before the role is advertised or before candidate conversations become substantive.
That means the EOR hiring sequence must become more disciplined.
The role must be defined. The country must be selected. The job level must be mapped. The proposed salary range must be documented. Local rules, statutory requirements, collective bargaining implications, payroll costs, and benefits must be checked. The EOR must confirm local feasibility. The candidate-facing pay range must be aligned. Recruiters and hiring managers must know what they can and cannot say.
That is a very different operating model from opportunistic international hiring.
The real danger is inconsistent pay-setting. One EOR employee in Spain may be paid based on negotiation power. Another in Germany may be paid based on global internal equity. Another in France may be paid based on a local market survey. Another in the Netherlands may be paid based on urgency. None of these approaches is automatically illegal. But if the company cannot explain the logic, the compliance position becomes fragile.
The Directive does not eliminate salary flexibility.
It does, however, punish compensation chaos.
Whose salary band is it — the EOR’s or the client’s?
This is the question many companies will need to answer quickly.
In an EOR setup, the salary band should not be treated as either purely the EOR’s band or purely the client’s band. It should be a jointly validated compensation range.
The client should lead the salary band because the client defines the role, seniority, required skills, business value, reporting line, budget, and job architecture. In practice, the client usually decides what the role is worth to the business.
But the EOR must validate the range locally because the EOR is the formal employer. That means checking whether the proposed range is compliant with local employment law, statutory minimums, collective bargaining agreements, payroll and social security requirements, mandatory benefits, and national pay-transparency rules.
The right process should be simple:
Client proposes the salary band.
EOR validates local compliance.
Both agree on the candidate-facing range.
The rationale is documented.
This matters because a client-imposed global salary band may be commercially convenient but locally difficult to justify. It may ignore local mandatory benefits, statutory pay rules, collective agreements, working-time assumptions, or national pay expectations. Equally, an EOR-generated generic local band may not reflect the client’s actual job level, internal equity, responsibilities, or performance expectations.
The salary band must therefore sit at the intersection of two realities: the client’s business logic and the EOR’s local employment compliance obligations.
This is where many EOR relationships will need to mature. A good provider should not simply ask, “What salary do you want to pay?” A good client should not simply say, “This is our global band; please issue the contract.”
Under the Directive, the range needs to be objective, gender-neutral, explainable, and locally defensible. In EOR hiring, that requires both parties to contribute evidence.
No salary history questions: a small rule with big operational consequences
The Directive also restricts employers from asking applicants about their pay history in current or previous employment.
This sounds easy to comply with. In reality, it requires process control.
Who is speaking to the candidate? The client’s recruiter? A hiring manager? An external search firm? The EOR? A local recruitment partner? A regional HR lead? A future line manager sitting in another country?
If anyone in the process asks, “What are you currently earning?” the hiring process may become non-compliant under the new national rules implementing the Directive.
This is especially relevant in EOR hiring because responsibilities are often split. The EOR may technically employ the worker, but the client usually runs the interview process. If the client’s hiring manager asks prohibited questions, the EOR cannot magically cure the mistake later by issuing a compliant employment contract.
This means EOR clients need interview rules, hiring manager training, recruiter scripts, and documentation. EOR providers also need to educate clients on what they must not do.
The old EOR message was: “We handle employment compliance.”
The new message must be more precise: “We handle formal employment compliance, but you must run a compliant hiring process.”
That distinction matters.
Equal pay evidence: the role must be more than a job title
The Directive is not only about publishing or communicating salary ranges. It is about equal pay for equal work or work of equal value. That requires employers to think more seriously about role comparison.
For EOR hiring, this creates a difficult question: what is the relevant comparator group?
Is the EOR employee compared with other employees of the EOR? Other employees assigned to the same client? Direct employees of the client doing similar work? Workers in the same country? Workers performing equivalent roles across borders? Workers under the same job architecture?
National implementation will determine much of this. But companies should not wait for perfect clarity. They should start building a defensible approach now.
A role should be mapped using objective criteria such as skills, effort, responsibility, working conditions, seniority, decision-making authority, complexity, and required experience.
This is particularly important in Europe because job titles are often unreliable.
A “Marketing Manager” in Germany may not be equivalent to a “Marketing Manager” in Spain. A “Senior Developer” in Poland may not be equivalent to a “Senior Developer” in France. A contractor converted into an EOR employee may sit outside the company’s normal job architecture. A remote role may be priced differently from an office-based role. A country premium may be defensible in one case but arbitrary in another.
If the role is poorly defined, the pay range will be poorly defended.
EOR hiring therefore needs job architecture. Not necessarily a massive corporate grading system, but at least a documented logic for role level, compensation band, country benchmark, and internal consistency.
The rebel lesson is simple: in Europe, “we negotiated the salary” will become a weak defense.
Reporting obligations: whose headcount is it anyway?
The Directive introduces pay reporting obligations for employers, with phased requirements depending on workforce size. Larger employers will face earlier and more frequent reporting obligations, while smaller employers may have more time or lighter requirements depending on national implementation.
For EOR models, this raises a structural question: are EOR employees counted under the EOR’s reporting obligations, the client’s workforce reporting, or both in some form?
The answer may vary by country. But the question cannot be ignored.
If the EOR is the formal employer, it may carry certain statutory reporting obligations. But if the client controls the role, salary, performance expectations, bonus logic, career progression, and day-to-day management, the client may still need the data for internal pay equity, ESG reporting, workforce governance, investor scrutiny, or legal risk management.
This creates an immediate operational requirement: data readiness.
Companies using EORs should know whether their provider can produce pay data by gender, role, country, job level, contractual arrangement, and client assignment. They should also know whether the EOR can support employee information requests and explain pay-setting criteria.
A provider that can run payroll but cannot support pay transparency reporting is not ready for the next European compliance cycle.
Payroll execution is not enough. The future requirement is pay evidence.
The EOR agreement must change
Many EOR agreements focus on employment contracts, payroll, benefits, tax, social security, termination support, indemnities, intellectual property, confidentiality, service levels, and data protection.
Pay transparency now needs its own section.
The agreement should clearly define who is responsible for salary range preparation, candidate pay disclosures, job advertisement wording, pay-history question controls, role classification, pay-setting criteria, employee information requests, pay data extraction, gender pay analysis, reporting support, documentation of objective criteria, remediation of unjustified gaps, and updates after national transposition.
Without this, both parties may assume the other is responsible.
The EOR may say: “The client decided the salary.”
The client may say: “The EOR is the employer.”
The regulator may say: “We do not care about your internal blame game.”
That is the compliance trapdoor.
The EOR agreement should also make clear how disputes are handled if the client wants to offer a salary that the EOR considers risky. Can the EOR reject the range? Must the client provide a written justification? Who owns remediation if an employee later challenges the pay structure? Who pays for additional legal review? Who responds to employee information requests?
These are not theoretical issues. They are the operational questions that will decide whether EOR hiring can remain both fast and compliant.
Why local implementation will matter
The Directive sets the European framework, but Member States must transpose it into national law. That means the details will vary. Some countries may go beyond the Directive’s minimum requirements. Others may integrate the rules into existing pay transparency, equality, labour, or reporting frameworks.
This matters because EOR hiring is country-specific.
A company hiring one EOR employee in Germany, five in France, three in Spain, and two in the Netherlands may face different disclosure rules, reporting expectations, enforcement procedures, employee information rights, and collective consultation dynamics.
Even if the Directive is European, the compliance execution will be local.
That is exactly why Europe is never “one market, one rulebook.”
The Directive will also interact with existing national rules on equal treatment, collective bargaining, works councils, payroll records, data protection, and discrimination claims. In some markets, employee representatives may become important stakeholders in pay transparency discussions. In others, litigation risk may drive more conservative pay-setting practices.
EOR providers need country-level legal monitoring. Clients need to demand it.
A generic EU-wide policy will not be enough.
Why this is not just an EOR provider problem
It is tempting for companies to believe the EOR will solve the issue. After all, the EOR is the legal employer. The EOR signs the contract. The EOR runs payroll. The EOR administers statutory employment obligations.
But pay transparency reaches into decisions the EOR does not fully control.
The client defines the business need. The client sets the budget. The client decides whether the role is junior, mid-level, senior, strategic, specialist, or leadership. The client chooses the candidate. The client often negotiates compensation. The client determines performance expectations, progression opportunities, bonus eligibility, and sometimes redundancy decisions.
That means the client is not just a passive beneficiary of the employment relationship. It is the architect of much of the pay decision.
Therefore, the client must own part of the compliance framework.
This is the same uncomfortable truth that applies across EOR compliance generally. An EOR can employ the worker, but it cannot make a non-compliant operating model compliant if the client’s behaviour creates the risk.
Pay transparency will expose this more clearly.
What buyers should demand from EOR providers
From 2026 onwards, EOR due diligence in Europe should include pay transparency readiness.
Buyers should ask whether the provider can support country-specific guidance on pay transparency implementation. They should ask whether the provider can support salary range disclosure before interviews or before contract conclusion. They should ask whether the provider can help validate pay ranges using objective, gender-neutral criteria.
They should also ask whether the EOR can confirm what pay-history questions are prohibited in each country, support employee requests for pay information, report pay data by role and gender, explain how EOR employees are treated for national pay reporting thresholds, and provide audit trails for compensation decisions.
Most importantly, buyers should ask what happens when the client’s preferred salary range is inconsistent with local compliance expectations.
Will the EOR challenge the client? Will it document the risk? Will it refuse to employ under an indefensible range? Or will it simply process the hire?
That question reveals the maturity of the provider.
The best EOR providers will not simply say, “We comply with local law.” They will show the operating model, documentation, controls, and data capabilities that make compliance visible.
What client companies should do now
Companies using EORs in Europe should prepare before June 2026. Waiting for all national laws to be finalized is risky because the operational work takes time.
First, map all EOR workers in the EU. Identify country, role, gender, salary, contract type, job level, hiring manager, and hiring process.
Second, review salary-setting practices. Determine whether pay ranges are documented before recruitment starts.
Third, standardize role classification. Build a simple but defensible job-level framework for EOR roles.
Fourth, clarify salary-band ownership. The client should define the business and job-architecture logic; the EOR should validate local employment compliance; both should document the final candidate-facing range.
Fifth, stop salary-history questions. Train hiring managers, recruiters, interviewers, and external search partners.
Sixth, update EOR agreements. Add pay transparency responsibilities, data support obligations, employee information request procedures, and escalation rules.
Seventh, test reporting readiness. Ask whether the EOR can provide the data required for information requests and reporting.
Eighth, compare EOR pay with internal pay where relevant. If EOR employees perform similar work to direct employees, inconsistent pay logic may create risk.
Ninth, document everything.
The future of compliance is evidence.
The board-level implication
The EU Pay Transparency Directive is not only an HR policy change. It is a governance issue.
It touches recruitment, compensation, legal, payroll, procurement, ESG, data, finance, and workforce planning.
For EOR hiring, it also forces companies to rethink accountability. Procurement may select the provider. HR may run the process. Legal may review the agreement. Finance may approve the budget. The EOR may issue the employment contract. The hiring manager may negotiate pay.
If no one owns the end-to-end process, everyone owns the risk.
This is why pay transparency belongs in the EOR selection process. Buyers should not evaluate EOR providers only on country coverage, pricing, onboarding speed, or platform experience. They should evaluate whether the provider can support employer compliance in the real world: pay ranges, equal pay evidence, reporting, data, documentation, local legal updates, and client-side hiring discipline.
Compliance is no longer just about hiring legally.
It is about proving that the hiring model is fair, explainable, and defensible.
Final Rebel Take
The EU Pay Transparency Directive will not kill EOR hiring in Europe.
But it will punish lazy EOR hiring.
Companies will no longer be able to treat the EOR as a black box for employment obligations while keeping all real pay decisions informal. The client and the EOR will need a shared compliance model. The salary range must be explainable. The role level must be documented. The hiring process must avoid prohibited questions. The data must be available. The pay logic must survive scrutiny.
The key question is not whether the EOR is the formal employer.
The key question is whether the entire employment model can prove compliance.
In the old EOR world, speed was the headline.
In the new European EOR world, speed without evidence is risk.
The companies that understand this will use EORs more intelligently. The companies that ignore it will discover that pay transparency is not just a reporting rule.
It is a mirror held up to the entire workforce model.
Legal Framing:
The legal framing is based on Directive (EU) 2023/970, which requires Member States to transpose pay-transparency rules by 7 June 2026 and strengthens equal pay for equal work or work of equal value through transparency and enforcement mechanisms.
About the IEC Rebel’s Digest
We write for the ones breaking molds, building cross-border teams, and reshaping global work. No buzzwords. Just truths, tools, and tactics for the new era of employment.
IEC Rebel’s Digest— The IEC Group can help you audit your global employment setup by identifying labor leasing risks, verifying licensing requirements, and ensuring your EOR partners meet every compliance standard—before regulators come knocking.
Last but not Least: If you’re facing challenges and wondering how others are managing similar issues, why not join The Leadership Collective Community? It’s a peer group and webcast platform designed for leaders to exchange insights and experiences.
Introducing the IEC Knowledge Network Free Membership – Your Gateway to Seamless Access!
We are thrilled to present a new service that goes beyond the ordinary download experience. In addition to offering you the ability to download the things you love, we are delighted to introduce the IEC Knowledge Network Free Membership.
The Free Membership option grants you access to our library of articles and videos, without the need for tedious registrations for each piece of content.
The publication serves as a trusted resource to support executives in their pursuit of sustainable and successful global expansion. In addition the IEC Practitioners are available to discuss your specific challenge in more detail and to give you clear advise..
Take advantage of this valuable resource to accelerate your global expansion journey
