.png)
What Does the EU Pay Transparency Directive Mean for Your India Team?
- Saransh Garg
- 17 hours ago
- 9 min read
Only four of the EU's 27 member states, Slovakia, Italy, Lithuania, and Malta, had fully transposed the EU Pay Transparency Directive into national law by the June deadline this year. The Netherlands, Sweden, Denmark, and the Czech Republic pushed their own rollout to January next year, and the European Commission has confirmed there will be no further extension.
What Is the EU Pay Transparency Directive and Why Does It Reach India Teams?
Directive (EU) 2023/970 was written to close the EU's gender pay gap, which has sat close to 12% for years. Most companies assume the law stops at the EU's border. It does not. It applies to any employer with employees working in the EU, and for many of our clients that includes India based teams reporting into an EU registered entity, or whose compensation decisions are made by an EU based HR or finance function.
We work with a mid sized Dutch fintech running a 40 person engineering pod out of Pune, hired entirely through an EOR arrangement tied to the Amsterdam parent company. Their HR director assumed the directive was irrelevant to India since no one physically works in the Netherlands. That is not how regulators are reading it. Where pay decisions and job architecture originate from an EU entity, and that entity's own employees are compared against roles that also exist offshore, the obligations tend to follow the corporate structure, not the location of the desk. That is the practical answer to what the EU pay transparency directive means for your India team, whether the office is in Amsterdam or Pune.
This changes three things for companies staffing India teams. Job postings for EU facing roles now need a stated salary range in many member states, and India based candidates can no longer be asked about salary history. Pay structuring across a global team has to survive an equal pay for equal value test, even across borders. And gender pay gap reporting, due to begin for large employers next year, will typically pull in headcount and pay data from any entity the EU parent controls, which for GCC heavy companies often means India payroll data ends up inside an EU compliance report.
How Ready Are EU Countries for Compliance Right Now?
Roughly a dozen member states are still working from draft legislation, and a handful, including Germany and Spain, have taken no substantive action yet. Belgium, Ireland, and Poland have partial transposition in force. Sweden has paused implementation entirely and is calling for the directive to be renegotiated, citing conflict with its own collective bargaining tradition.
The mistake we see most often is companies waiting for their client's country to finish transposition before touching India side hiring. That backfires twice. The underlying directive rights, the salary range disclosure, the right to request pay level data, the salary history ban, are EU wide minimum standards. National law can only add stricter requirements, never soften them. And when national law does land, it often arrives with almost no grace period, as it did in Slovakia, Italy, and Malta, all of which took effect within days of the deadline.
Contract Hiring vs Full-Time Hiring: What Actually Changes Under the Directive
This is where clients get confused, so it is worth separating clearly. Contract hiring means bringing on an India based engineer for a fixed term or project scope, usually through an EOR or staffing partner, without adding permanent headcount on either side. Full time hiring means the person becomes a permanent employee, either on an Indian entity's payroll or, less commonly, directly employed by the EU parent.
The salary range disclosure and salary history ban apply at the job posting and interview stage, so they cover contract and full time roles equally. Where the two diverge is on pay gap reporting. Full time headcount almost always gets pulled into group reporting. Contract engineers hired through a third party EOR sit in a greyer zone, and whether they are counted often depends on how much control the EU entity exercises over their day to day work and compensation. We tell clients not to rely on contract structuring as a way around the directive.
If the EU entity sets the pay band and interviews the candidate, transparency obligations generally follow the process, not the contract type.
Which Indian Cities Have Talent Ready for This Kind of Hiring?
Bengaluru and Pune see the most EU linked GCC and EOR hiring, largely because that is where the deepest bench of engineers with prior MNC exposure sits. Hyderabad carries strong SAP and enterprise data talent, which brings its own pay banding complexity since those roles in Germany and the Netherlands already sit inside collective bargaining scales. Chennai has become a strong source for QA and cloud infrastructure hires feeding UK and Irish clients, where similar transparency rules are arriving through parallel domestic legislation.
What most Indian engineers and recruiters lack is not technical skill, it is exposure to structured, banded compensation conversations. Most candidates have never been told a salary range as a starting point, and most India side HR teams have never had to justify an offer against a documented, gender neutral evaluation framework.
We test for this during client onboarding by running a mock compensation conversation and asking the hiring manager to explain, out loud, why one candidate would be paid more than another for the same role.
Build a Pay Band That Actually Meets EU Requirements
This is the section clients screenshot and keep in their hiring playbook.
Requirement | What It Means for an India Based Role Under an EU Entity | Who Owns It |
Salary range in job posting | Post a defensible min to max range before the first interview | Recruitment and HR |
No salary history questions | Interviewers cannot ask what a candidate currently earns | Hiring manager |
Objective job evaluation | Map each role to scope, complexity, autonomy, and impact, not title | HR and compensation |
Equal pay for equal value | Cross border comparisons must hold up if the work is similar | Finance and HR |
Right to request pay data | India employees under EU entities may gain a right to request comparable pay data | Legal |
Group pay gap reporting | Large employers report group wide gaps, which can include India headcount | Group HR and legal |
Recordkeeping | Job evaluation and band rationale must exist at offer time, not after | HR operations |
Equal value is not the same as equal title. A senior backend engineer in Amsterdam and one in Pune can legitimately earn different amounts if cost of living and market factors are written into policy and applied consistently, not decided case by case. And the paper trail has to exist at the moment the offer is made. Reconstructing it after a regulator or works council asks is itself treated as a warning sign.
Our Process, and What Almost Went Wrong Once
At AnjuSmriti Global, our process for clients hiring India talent into an EU linked structure starts with a compensation architecture review before the first job description goes live, usually a three to five day exercise mapping the client's EU pay bands against equivalent India role levels.
We ran this recently for a mid market German industrial software company building a data engineering pod in Hyderabad through an EOR structure. Their EU pay bands were solid, but their India offers had always been made on pure negotiation with no written rationale at all. Our first comparative job evaluation found two senior India based engineers doing nearly identical scope work to a Munich counterpart, at a pay ratio wider than anything defensible under an equal value test, even after cost of living adjustment.
Their works council had already started asking questions before we finished the rebanding exercise. We worked with their legal team to document the rationale, closed part of the gap over two review cycles, and had documentation in place before it escalated further. No formal complaint was filed, and their next twelve India hires went through the documented process from day one.
What Compliant Hiring Actually Costs
Using data engineering as a representative role family, a documented, directive compliant pay band across Germany and India typically looks like this.
Level | Germany (Munich, annual, EUR) | India (Hyderabad, contract, annual equivalent, EUR) |
Mid, 3 to 5 years | 58,000 to 68,000 | 19,000 to 24,000 |
Senior, 6 to 9 years | 72,000 to 88,000 | 26,000 to 33,000 |
Lead or staff | 95,000 to 115,000 | 38,000 to 46,000 |
Total cost of an India hire includes the contract or EOR salary, statutory employer contributions of roughly 12 to 14% under Indian EPF and gratuity rules, an EOR fee of 8 to 15% depending on volume, and a recruitment fee.
Clients running this through a recruitment process outsourcing model typically land at 35 to 45% of the equivalent Munich cost, even after the compliance work the directive now requires. Most reinvest that gap into pay equity audit tooling rather than pure headcount growth, since the compliance landscape keeps evolving.
Conclusion
Cloud and AI hiring demand is pulling more EU companies toward India GCC structures, which means more India roles are being pay banded against EU counterparts for the first time. AI assisted HR platforms are increasingly running job evaluation and pay equity checks automatically, which makes the required documentation easier to produce but also easier for regulators to request quickly.
At the same time, EU companies are shifting senior platform and DevOps hiring into India rather than treating it as a junior cost center, which raises the stakes on getting pay parity documentation right, since senior hires are the ones most likely to be compared directly against EU counterparts.
We expect gender pay gap reporting, due to begin next year, to be the point where most companies discover their India data is already inside an EU compliance report. In live mandates right now, EU clients are asking us to build job evaluation documentation for India roles before the requisition even opens, a sequencing shift we did not see this time last year.
If you are hiring into an EU linked structure and want your India pay bands reviewed before your next hire goes live, this is the fastest way to start: Request a pay band compliance review.
Interesting Reads:
FAQs
1.Does the EU pay transparency directive apply to India based employees who never work physically in the EU?
Yes, if the employing or controlling entity is registered in the EU. The obligations follow the corporate structure and pay decision process, not the physical location of the desk. If an India team reports into EU based management for compensation, the directive's core requirements usually reach that team, even before the local EU country finishes its own transposition into national law.
2.Which EU countries have finished implementing the pay transparency directive so far?
Slovakia, Italy, Lithuania, and Malta had comprehensive legislation in force by the deadline this year. Belgium, Ireland, and Poland have partial rules in place. The Netherlands, Sweden, Denmark, and the Czech Republic delayed to next year, and Sweden has paused its process entirely, formally calling for the directive to be renegotiated over concerns about its collective bargaining traditions.
3.Do we need to change India hiring if our EU client's country hasn't finished transposing the law yet?
Yes. The directive's core rights are EU wide minimum standards that apply regardless of a specific country's transposition timing. National law can only add stricter rules on top of that baseline, never remove it. Waiting for final legislation before adjusting India hiring usually means retrofitting compliance under pressure once the law lands with little advance notice.
4.Can we still ask India based candidates what they currently earn during interviews?
No, not for roles reporting into or paid by an EU entity covered by the directive. The salary history ban applies directly to the interview process itself, not just the final offer. We now build this into interview scripts for any client hiring India talent into EU facing roles, replacing salary history questions with a structured discussion of the posted range.
5.How does an EU gender pay gap report end up including our India GCC's data?
Reporting obligations typically apply at the group level, wherever the EU entity controls or significantly influences pay policy in an affiliated entity. For companies running a GCC in India under an EU parent, this often pulls India payroll and gender composition data into the group's consolidated report, even when the India entity has no independent Indian reporting requirement of its own.
6.Does hiring through an EOR shield our company from directive obligations?
No. An EOR manages payroll and local employment administration, but pay band design and equal value justification sit with whoever actually sets compensation policy, which is usually the client. We recommend confirming with your EOR provider exactly what pay documentation is retained at the group level, since that is what regulators or works councils typically request first during a review.
7.How do we justify a pay gap between an EU role and an equivalent India role?
Cost of living and local market differences are generally accepted as legitimate factors, but only if they are written into a consistent compensation policy and applied the same way across every comparable role. The real risk is not the existence of a gap between Munich and Hyderabad pay. It is the absence of a documented, consistently applied reason explaining its size.
8.Which roles carry the most compliance exposure under this directive right now?
Data engineering, DevOps, and SAP or enterprise roles carry the most immediate exposure, since these are most commonly staffed through GCC and EOR structures with a direct reporting line into an EU parent company. Roles hired through arm's length outsourcing contracts, with no direct EU compensation influence, carry somewhat lower exposure but should still be documented as a precaution against future scrutiny.
Comments