Lithuania tightens its Pay Transparency Directive draft: what the revised version really signals
From policy intent to operationalised data analysis, Lithuania is building a whole new system to deal with the PTD paradigm.
Lithuania has revised its draft legislation implementing the EU Pay Transparency Directive, with the Government approving an updated version on 18 March 2026.
Lithuania was one of the first to publish a draft about a year ago. I spoke to Jovita Valatkaite about that draft. That episode is still well worth a listen. Much of that draft still holds. This latest draft is not a significant change in direction.
But it is a SIGNIFICANT change in architecture.
Lithuania is refining how pay data will be structured, processed, and transmitted through state systems once the Directive is operationalised.
At this stage of implementation, the real question is no longer what transparency means in principle. It is what the system can reliably compute, standardise, and reproduce at scale.
That shift matters more than most of the headline policy language suggests.
The core thesis: pay transparency is becoming a data engineering exercise
The revised Lithuanian draft does not materially reframe the earlier proposal.
Instead, it sharpens execution around four things:
Standardised, machine-readable pay metrics
Centralised data processing through state institutions
Reduced employer discretion in reporting design
Greater reliance on administrative datasets rather than employer constructs
This is the important point.
The EU Pay Transparency Directive is not just a disclosure framework. In Lithuanian implementation, it is becoming a structured data system.
Or more bluntly:
Pay transparency is turning into a question of what the reporting infrastructure can actually compute without ambiguity.
Most commentary still treats the PTD as a legal evolution. But Lithuania is treating it as a systems engineering problem.
From flexible pay concepts to strict, comparable metrics
One of the most consequential changes in the revised draft is the move away from broad remuneration concepts toward tightly defined, segmented metrics.
Earlier drafts relied more heavily on general terms such as “remuneration” and “average salary”.
The revised text replaces this with structured outputs, including:
Annual salary
Monthly average hourly wage
Annual average hourly wage
This is not cosmetic precision.
It is enforcement design.
Why this matters under the EU Pay Transparency Directive
The Directive requires pay comparability across roles, genders, and job categories. That becomes difficult when employers can define pay internally in ways that reflect organisational complexity rather than statistical consistency.
Lithuania’s shift does three things:
Removes interpretive flexibility from employers
Improves cross-employer comparability
Enables automated aggregation of pay data
Once metrics are this tightly defined, internal pay narratives matter less than system outputs.
At that point, employers are not explaining pay structures. They are conforming to a reporting schema.
Scope is shifting from employment headcount to administrative population data
Another important adjustment is how organisational scope is defined.
The revised draft replaces “average number of employees” with “number of insured persons” under social insurance rules.
This is a quiet but structural change.
It moves the system from employer-reported workforce figures to state-validated administrative datasets.
What changes in practice
Scope becomes more consistent across employers
Reporting thresholds are less susceptible to definitional variation - the government will know definitively who is covered and who isn’t
Non-standard employment arrangements are captured more systematically
This is the kind of change that rarely gets attention, but drives most of the downstream compliance reality.
Transparency works when everyone plays by the same rules. Lithuania seems to be going all out to make sure that happens.
Alongside this, exclusions have been clarified and expanded:
Temporary agency workers remain outside employer reporting scope
Public officials and statutory civil servants are excluded
Individuals covered by civil service secrecy provisions are explicitly removed from reporting
This reinforces a clearer institutional boundary between public sector confidentiality regimes and private sector transparency obligations under the EU Pay Transparency Directive.
Data flows are being centralised, not distributed
Perhaps the most structurally significant change is in how data moves through the system.
Under the revised model:
Employers submit data to the State Social Insurance Fund Board
The Board becomes the central processing hub
Data is transmitted onward to:
The State Labour Inspectorate
The Equal Opportunities Ombudsperson
This is not administrative tidying.
It is system design.
Why centralisation matters
This removes variability in reporting logic at the employer-regulator interface and replaces it with a single computation layer.
That has three consequences:
Consistency increases because one institution standardises outputs
Employer burden shifts from interpretation to structured submission
Methodology risk concentrates in one administrative system
Voluntary publication by employers has also been removed entirely.
That is not a minor adjustment. It signals a clear preference for institutional control over narrative disclosure.
Or more bluntly: transparency is no longer something employers curate.
It is something the system generates.
Multi-dimensional pay outputs replace single gap figures
The revised draft also expands the output structure required from the central authority.
Instead of a single aggregated pay gap figure, the system will produce multiple metrics, including:
Monthly average hourly pay
Annual average hourly pay
Job-group and gender disaggregation
This reflects a broader shift in EU Pay Transparency Directive implementation.
The policy objective is no longer just visibility of disparities.
It is dimensional visibility of pay structures.
That has a subtle but important effect. Once pay is expressed across multiple time-based and structural axes, single headline figures lose explanatory dominance.
Or in practical terms: the system becomes harder to summarise, but easier to interrogate.
Employer discretion is narrowing across the board
Several revisions collectively reduce employer flexibility in how transparency is operationalised.
1. Removal of voluntary publication
Earlier drafts allowed employers to publish selected pay data independently. That option has been removed.
This consolidates communication of pay information within official channels.
Voluntary narrative framing has effectively exited the system.
2. Reduction of historic reporting burden
The proposed four-year retrospective reporting requirement has been removed.
Historical reconstruction now sits more clearly with central authorities rather than employers.
This reduces burden but increases reliance on state data continuity.
3. Extended response timelines
Deadlines for providing employee-facing information have been extended from two weeks to one month.
A modest adjustment, but directionally consistent with operational realism.
Rulemaking authority is being consolidated at ministerial level
The revised draft also centralises secondary rulemaking authority with the Minister for Social Security and Labour.
This includes responsibility for:
Data collection procedures
Calculation methodologies
Submission formats
Publication rules
This matters because most of the EU Pay Transparency Directive’s practical impact will sit in secondary regulation, not primary law.
Centralising this authority does two things:
It increases consistency in implementation design
It concentrates interpretive power at national level
In other words, the Directive may be EU-wide, but its operational meaning will still be locally engineered.
Key takeaways from Lithuania’s revised implementation
Standardisation is replacing interpretive flexibility
Pay metrics are becoming fixed computational outputs rather than definitional constructs.
Administrative datasets are becoming the source of truth
Scope and workforce definition are shifting away from employer self-reporting.
Centralisation is the dominant design pattern
A single institutional hub now sits between employers and regulators.
Transparency is becoming system-generated rather than employer-curated
Voluntary disclosure mechanisms have been removed from the model.
Pay gap reporting is evolving into multi-dimensional pay analytics
Single headline figures are being replaced with structured, comparable outputs.
Closing: is the Pay Transparency Directive becoming a systems problem to be solved?
Lithuania’s revised draft does not alter the trajectory of EU pay transparency implementation.
It clarifies it.
Across Member States, a consistent pattern is emerging. The most significant divergences are not about whether transparency exists, but how deterministic the underlying reporting systems become.
That is the real shift.
The EU Pay Transparency Directive is no longer just about disclosure obligations.
It is about building administrative systems capable of producing comparable pay data at scale, without interpretation.
Once you see it that way, Lithuania stops looking like a legal update.
It starts looking like infrastructure design.