Multi-Entity Structures for EUPTD Compliance - PayAlign Blog

Multi-Entity Structures for EUPTD Compliance

← Blog

The EU Pay Transparency Directive attaches its duties to the individual legal entity, not to the corporate group that owns it. That one fact turns pay transparency into a question mark for any business that runs through more than one registered employer.

A parent organisation with several regional operating entities faces this question. A cross-border multinational with subsidiaries across a dozen member states faces a harder version of the same problem. Directive 2023/970 does not treat the consolidated group as the reporting unit. So a group of twelve entities can end up filing twelve separate pay reports, each one judged against a different national transposition. The distance between how a group is structured and how it must report is precisely where cost, legal exposure and delay accumulate.

The Legal Entity Dilemma

The friction sits between how these groups are run and how they must now report. Group HR is usually pooled into a single HRIS. This accounts for one data model built for scale across the whole business. The Directive demands the opposite. It requires legal entity isolation.

Reporting cadence is set per entity by headcount:

  • Entities of 250 or more employees report every year.
  • Those of 150 to 249 and 100 to 149 report on staggered multi-year cycles.

An entity that sits below its national threshold can fall out of scope while its sister entity reports in full. This is not only a large-enterprise concern. A mid-market parent that has grown through acquisition often holds several operating entities that each cross a national threshold. As a result, it inherits an enterprise-grade reporting burden without the centralised function to carry it.

The harder problem is comparability. The Directive requires each employer to group its employees by work of equal value, measured across skills, effort, responsibility and working conditions. That comparison only holds when every entity uses the same job evaluation method. If entities were to grade roles individually, the same job lands at a different level from one entity to the next. The group then cannot show whether a senior analyst in Dublin and a senior analyst in Madrid are doing work of equal value. As a result, each entity defends its own numbers in isolation. No single, consistent view of the group exists.

Three Operating Models

Three operating models are emerging. Two of them fail at scale.

  • The centralised model: This routes every entity's data through the parent head office. It gives consistency but bottlenecks execution. One central team cannot absorb the transposition divergence between member states, where deadlines, thresholds and enforcement all differ. It also struggles to adapt to entity-specific detail in time, so local nuance is lost and reports arrive late.
  • The decentralised model: This hands each subsidiary its own reporting. It respects local detail but produces isolated outputs, inconsistent job architecture and no group view. When one entity publishes a gap it cannot defend, the reputational damage still lands on the parent brand.
  • The federated governance model: This resolves the tension. The corporate parent owns the job evaluation framework, the shared method and the standard for work of equal value. Each entity then runs its own reporting against that common architecture. Corporate parent governance sets the rules and the legal entity aggregation happens on one foundation. For multi-entity groups and large multinationals alike, this is the premier scalable approach. It gives the corporate parent one defensible methodology while leaving each entity accountable for its own filing, which is the balance regulators and auditors expect to see.

The Infrastructure Imperative

Federated compliance architectures are only as strong as the software beneath them. A multi-entity reporting engine has to deliver four things:

  • A unified data model that pulls in the group HRIS while keeping strict legal entity isolation, so each report stays discrete and defensible.
  • Localised rule mapping that applies to each member state's transposed thresholds and cadence on its own.
  • A shared job evaluation layer that keeps work of equal value consistent across entities without erasing real local difference.
  • A real-time audit trail that can answer an Article 7 information request at entity level inside the statutory window.

Spreadsheets cannot carry this weight. Governance without the infrastructure to enforce it is an intention, not a control. Under audit, that gap between intent and control is what decides the outcome. This is the layer PayAlign is built for. It is one governed framework, isolated entity reporting and audit-ready trails across every entity in the group.

Govern once, report per entity

PayAlign gives multi-entity groups one governed job evaluation framework, isolated entity-level reporting and audit-ready trails across every legal entity in the group.

Book a demo

Frequently Asked Questions

Does a parent company report EUPTD metrics as a consolidated group or per legal entity?

Per legal entity. The Directive attaches obligations to each registered employer, not to the consolidated corporate group. A parent that operates through multiple entities files separately for each one that meets its national threshold, under that entity's transposed rules. There is no group-level report that discharges the obligation.

How do multi-entity organisations handle employees shared across distinct subsidiaries or dual-contract arrangements?

Each employment relationship follows the legal entity that holds the contract. A worker on a dual contract counts within every entity that employs them, against that entity's headcount and pay data. Shared or seconded staff are allocated by the entity of legal employment rather than by where they physically sit, which makes clean entity tagging in the HRIS essential.

What is the primary operational risk of relying on a purely centralised compliance strategy across multiple entities?

Bottlenecking. A single central team cannot track transposition divergence across every member state or absorb entity-level detail at the required cadence. The result is missed deadlines, one-size-fits-all reporting that misstates individual entities and a fragile process that buckles under audit or a surge of Article 7 requests.