Pay transparency in Lithuania
-
Pay information requests Pending
Same employer-defined same/equal-value job group, sex-disaggregated monthly and annual metrics. Identification-risk data go only to representatives, VDI or LGKT, which inform worker about>=5%gap without exposing identifiable pay. Litigation common-source comparisons underDK26(4) are broader than routine requests.
-
Time to respond 1 month; supplementary explanations within 2 months of the original request
Every request starts a clock. Answering one needs pay structures and equal-value groupings that already exist.
-
Salary history questions are banned
Applicants learn the pay range before the interview, and employers may not ask what they earn today.
Lithuania has already adopted its pay transparency law, and it is partly in force. Most provisions of the amending Act began to operate on 7 June 2026. The changes to Labour Code articles 23 and 148 follow on 1 January 2027. The duties on employers are being phased in rather than switched on all at once.
The detail matters because the Lithuanian rules go further than the EU baseline in several places. Pay information requests get a one-month response window, and the state social insurance fund board (Sodra) calculates much of the pay data centrally. Employers have fixed dates between late 2026 and 2028 to plan around.
Salary publication in job advertisements and a ban on asking about salary history already apply nationwide. Treat those as live rules, and treat the rest as a staged timetable you can work backwards from.
The measure
- Law or measure
- Lietuvos Respublikos darbo kodekso 23, 26, 39, 40, 41, 42, 48, 51, 52, 65, 71, 79, 131, 140, 147, 148, 197, 217, 219, 226 straipsnių ir priedo pakeitimo įstatymas
- Core obligations start
- 7 Jun 2026
- Who is covered
- Labour Code employers and employees; related package extends aligned rules to specified public-sector employment/pay regimes.
What the law requires
- Pay range before the interview Source for: Pay range before the interview
- Salary history questions banned Source for: Salary history questions banned
- Gap reporting from 100 employees Source for: Gap reporting from 100 employees
- Joint pay assessment at a 5.0% gap Source for: Joint pay assessment at a 5.0% gap
1 further dimension is still being verified against official sources.
How Lithuania differs from the Directive
One-month initial information response versus EU two-month maximum; employer pay systems for all with below50 exemption only for increase criteria; central Sodra calculation plus agency self-calculation; monthly disclosure at8workers subject4persex; phased2027/2028 duties; detailed pay exclusions and averaging/annualisation formulas.
On at least one point the national rules go beyond the Directive minimum, so preparing to the EU baseline alone is not enough here.
What this means for employers
The first deadline is your pay system. By 31 December 2026 you need a pay system that covers all employees, including indexation. If you have 50 or more employees, it also needs criteria for pay increases. Employers below 50 are exempt only from the increase criteria.
Next comes data. The first monthly submission to Sodra covers January 2027 and is due by 28 February 2027. Workers can then ask for their own average hourly pay, and for pay broken down by sex in their job group, from 1 March 2027. Sodra’s first monthly outputs are due by 15 March 2027. Annual information for workers follows from 1 March 2028. You have one month to respond to a request, and supplementary explanations are due within two months of the original request.
Annual pay-gap reporting starts at 100 employees and uses the seven EU metrics only. Sodra does the central calculation, and temporary work agencies calculate their own temporary-worker figures. One timing point is unresolved: the Act says annual outputs by 1 March 2028, while an implementing order says 15 March 2028. The statute prevails, and the authorities still need to clarify. Plan for the earlier date.
- Pay system: review or adopt it before 31 December 2026, with indexation for everyone and increase criteria if you have 50 or more employees.
- January 2027 submission: prepare total pay, the additional-pay subset, paid hours and excluded components as separate items, with job group and work-time details in every submission.
- Data checks: validate the prefilled data from Sodra. Be ready to correct errors within two working days by resubmitting the full period.
- Request workflow: set up a process that meets the one-month deadline, with confidentiality routing. Data that could identify individuals goes only to representatives, the labour inspectorate (VDI) or the equality body.
- Temporary agencies: plan your own annual calculations, as these sit outside the monthly Sodra route.
This helps you prepare, but it is not a guarantee of compliance. Check the final wording with your legal adviser, especially where the timing conflict above applies.
Enforcement and open questions
- Competent authority
- Valstybinė darbo inspekcija (VDI); Valstybinio socialinio draudimo fondo valdyba (Sodra) administers pay-transparency data flows; labour disputes bodies/courts provide remedies.
- Equality body
- Lygių galimybių kontrolieriaus tarnyba
- Penalties
- Administrative liability applies for failures to provide required pay information; other Labour Code breaches remain subject to labour-law and administrative enforcement.
- What could still change
- Most ActXV-969 provisions operate7Jun2026, DK23/148 amendments1Jan2027; Fully in force was overstated. A1-433 permits requests1Mar2027/2028 and first monthly outputsby15Mar2027. Annual output timing conflicts: Act§23(8)by1Mar2028 versusA1-433§3.1.3by15Mar2028; statute prevails, clarification needed. Procurement, limitation interaction and independent standing remain limited. Broad e-Seimas discovery still incomplete; exact-body access is not full daily coverage.
Common questions
Is the EU Pay Transparency Directive in force in Lithuania?
Partly. Lithuania has adopted an Act amending the Labour Code, and most of its provisions began on 7 June 2026. The changes to articles 23 and 148 start on 1 January 2027, and the reporting duties are staged through 2028 and beyond.
When can Lithuanian employees request pay information?
From 1 March 2027, workers can request their own monthly average hourly pay and the average broken down by sex for their job group. The first data supplied in March 2027 is for January 2027. From 1 March 2028, workers can also obtain annual pay information. The data does not necessarily arrive on the first day a right begins.
How long do employers in Lithuania have to answer a pay information request?
The rules set one month for the initial response, which is shorter than the EU maximum of two months. Supplementary explanations are due within two months of the original request. Data that could identify individuals goes only to representatives, the VDI or the equality body, not to the worker directly.
Which Lithuanian employers must report their pay gap, and when?
Annual pay-gap reporting begins at 100 employees. For employers with 250 or more, Sodra's output for 2027 is due by 1 March 2028, with public disclosure by 1 April 2028. For employers with 100 to 149, the first output covers 2030 and is due by 1 March 2031. Sodra does the central calculation for most employers, and temporary agencies calculate their own figures.
Does Lithuania require salary ranges in job ads and ban salary history questions?
Yes to both. Salary publication in job advertisements was already required before the Directive and remains in the national framework. The salary-history restriction is also confirmed.
What happens if a Lithuanian employer fails to provide pay information?
Administrative liability applies for failures to provide the required pay information. Other Labour Code breaches remain subject to labour-law and administrative enforcement. The labour inspectorate (VDI) is the competent authority, and labour dispute bodies and courts provide remedies.
- Pay information request right Art. 7(1)
- Pending
- Response deadline Art. 7(4)
- 1 month; supplementary explanations within 2 months of the original request
- Salary range in recruitment Art. 5(1)
- Yes
- Salary history questions banned Art. 5(2)
- Yes
- Joint pay assessment trigger Art. 10(1)
- 5.0%
Same employer-defined same/equal-value job group, sex-disaggregated monthly and annual metrics. Identification-risk data go only to representatives, VDI or LGKT, which inform worker about>=5%gap without exposing identifiable pay. Litigation common-source comparisons underDK26(4) are broader than routine requests.
LT-LEGAL-DEEP-20261103173635: Legacy composite is Partial / conditional because the right is enacted but operational information is staged: monthly own/comparator information first from 1 Mar 2027 and separately staged annual information from 1 Mar 2028. Exact enacted Act and implementing-order bodies checked; preserve staged operation. No new amendment inferred.
Read the sourceThe employer must answer in writing within this period.
LT-LEGAL-DEEP-20261103173635: Authority requests under148(6): set deadline capped10workingdays. Statute controls over FAQ6.8's separate-request ambiguity. Exact enacted Act and implementing-order bodies checked; preserve staged operation. No new amendment inferred.
Read the sourceApplicants receive the pay or pay range before the interview, based on objective, gender-neutral criteria.
LT-LEGAL-DEEP-20261103173635: Salary publication in job advertisements remains required under the national framework. Exact enacted Act and implementing-order bodies checked; preserve staged operation. No new amendment inferred.
Read the sourceWhether employers are prohibited from asking applicants about their current or previous pay.
LT-LEGAL-DEEP-20261103173635: The implementation summary confirms the salary-history restriction. Exact enacted Act and implementing-order bodies checked; preserve staged operation. No new amendment inferred.
Read the sourceThe unjustified gap that obliges the employer and worker representatives to assess pay together.
LT-LEGAL-DEEP-20261103173635: JPA statutory clause enters1Jan2027, not7Jun2026. Reporting outputs and trigger mechanics staged;>=5% cumulative conditions retained. Exact enacted Act and implementing-order bodies checked; preserve staged operation. No new amendment inferred.
Read the source- Reporting threshold
- 100 employees
- Reporting model
- Hybrid / centralised Operational data-production and filing model for pay-gap reporting: employer-calculated, authority-calculated, hybrid, proposed, pre-existing or absent.
- First report, 250 or more employees
- By 1 Mar 2028, Sodra employer output for 2027; public disclosure by 1 Apr 2028
- First report, 100 to 149 employees
- By 1 Mar 2031, Sodra employer output for 2030; public disclosure by 1 Apr 2031
- Metrics required
- EU seven only Art. 9(1): Seven metrics: mean gap; variable-component gap; median gap; median variable gap; variable-pay participation by sex; quartile distribution by sex; category-level gap split basic and variable.
- Pre-existing regime
- Salary publication in job advertisements pre-dated the Directive; Sodra data and disclosure duties are staged from 2027/2028.
- Formal transposition stage
- Partly in force
- Scope
- Nationwide
Next milestone
Pay systems by31Dec2026; staged DK23/148 changes1Jan2027; JanuarySDUP by28Feb2027; requests from1Mar2027 and Sodra monthly outputsby15Mar2027. Annual150+ outputsby1Mar2028/public1Apr2028; seek clarification on conflicting annual15March wording.
Primary sources
- Lietuvos Respublikos darbo kodekso 23, 26, 39, 40, 41, 42, 48, 51, 52, 65, 71, 79, 131, 140, 147, 148, 197, 217, 219, 226 straipsnių ir priedo pakeitimo įstatymas Primary source, checked 4 November 2026
- Formal transposition stage Partly in force · in force · High confidence
- Core employer obligations Partly operational · in force · High confidence
- Transposition scope Nationwide · in force · High confidence
- Salary range in recruitment Yes · in force · High confidence
- Salary history questions banned Yes · in force · High confidence
- Pay information request right Partial / conditional · in force · High confidence
- Response deadline 1 month; supplementary explanations within 2 months of the original request · adopted future · High confidence
- Reporting threshold 100 · adopted future · High confidence
- First report, 250 or more employees By 1 Mar 2028, Sodra employer output for 2027; public disclosure by 1 Apr 2028 · adopted future · High confidence
- First report, 100 to 149 employees By 1 Mar 2031, Sodra employer output for 2030; public disclosure by 1 Apr 2031 · adopted future · High confidence
- Reporting model Hybrid / centralised · adopted future · High confidence
- Joint pay assessment trigger 5.0% · in force · High confidence
- Info reference period Multiple / mixed · in force · High confidence
- Info pay basis Actual remuneration paid / earned · in force · High confidence
- Info pay components scope Different / modified · in force · High confidence
- Info request frequency At any time / no stated limit · in force · High confidence
- Info employee reference period eligibility No general minimum-service condition identified in reviewed instruments. Worker access is to Sodra-supplied staged monthly/annual metrics; initial request rights1Mar2027/1Mar2028 do not mean outputs necessarily delivered that day. Temporary workers may ask agency or user undertaking. · in force · High confidence
- Info normalisation method Individual monthly/annual gross divided by corresponding paid hours. Sex/category hourly averages are sum of relevant remuneration divided by sum of corresponding paid hours. Category annual-pay means annualise using paid-month equivalents×12; partial paid months follow A1-433 formulas. · in force · High confidence
- Reporting reference period Previous calendar year · in force · High confidence
- Reporting pay basis Actual remuneration paid / earned · in force · High confidence
- Reporting pay components scope Different / modified · in force · High confidence
- Reporting population basis Monthly SDUP covers employees, including non-Lithuanian-social-insurance workers and termination month, except secret/status personnel and temporary-contract workers. Multiple/changed groups have separate rows. Temporary workers follow separate annual employer-calculated route; annual size thresholds use insured headcount on31December of prior year. · in force · High confidence
- Reporting normalisation method Previous-calendar-year accrued gross and paid-hours model. Category sex-specific hourly means divide aggregate pay by aggregate paid hours; annual-pay means use paid-month equivalents and×12. Median hourly gaps use ordered individual annual-hourly rates; quartile remainder allocationQ2,Q1,Q3. Follow full A1-433 formula set. · in force · High confidence
- Employer required input data SDUP: employer/month; employee identifiers/sex; monthly total gross, additional gross subset and paid hours. Job group, weekly work-time norm and regime initially/on change in EDAS; include each in every integrated submission. Separate rows per group/change; validate SAM/2-SD prefills. Correct within2workingdays with full period resubmission; agency annual metrics separate. · in force · High confidence
- First data period needed January2027 monthly SDUP due28Feb2027. Monthly request right from1Mar2027; Sodra first monthly output deadline15Mar2027. 2027annual data: A1-433 permits annual requests from1Mar2028, but output clause3.1.3 says15Mar2028 while superiorAct§23(8) saysby1Mar2028; conflict needs authority clarification. · in force · High confidence
- Own pay information Yes · in force · High confidence
- Comparator information Yes · in force · High confidence
- Comparator information start 1 Mar 2027 · in force · High confidence
- Annual average information start 1 Mar 2028 · in force · High confidence
Change history
Recent updates
Lithuania finalises binding monthly SDUP filing and correction rules
Sodra Order V-500 is in force and now sets the binding monthly population, pay-data, filing and correction mechanics for Lithuania’s staged SDUP process.
Lithuania publishes technical specification for 2027 SDUP pay-transparency filings
Sodra has published the official SDUP data-structure and JSON validation specification for Lithuania's staged pay-transparency reporting process.
This page is maintained by Evenpay from official primary sources and reviewed before publication. It is general information, not legal advice. Requirements vary by member state and change as national laws progress; figures described as proposed are subject to amendment.
Get notified when Lithuania moves
We verify every change against official sources before it reaches this tracker. Follow the countries that matter to you and the same updates land in your inbox.
Legislation updates only, no marketing. Unsubscribe any time.