Bulgaria’s Pay Transparency Directive draft is out. And it goes further than advertised.
"Minimum implementation"? Not quite. Implementation? 7 June.
Bulgaria has now published its draft legislation implementing the EU Pay Transparency Directive (“PTD”), alongside a substantial package of supporting documents explaining the government’s rationale, objectives, and impact assessment.
For anyone tracking the broader EU Pay Transparency Directive Bulgaria debate, the government’s message is remarkably consistent:
this is intended to be a minimum implementation exercise.
The accompanying ministerial report, motives document, and impact assessment repeatedly emphasise that Bulgaria does not intend to go beyond the Directive’s requirements or create unnecessary burdens for employers.
And, to be fair, in several major areas Bulgaria does follow the PTD framework quite closely. The reporting thresholds mirror the Directive almost exactly. Employers with fewer than 100 employees remain outside the formal reporting regime. The phased introduction broadly follows the EU timetable.
But once you move beyond the headline positioning, the picture becomes more interesting.
Because while Bulgaria describes its approach as minimalist, the draft legislation contains a number of provisions that, in practice, go further than the PTD strictly requires. Some are relatively technical. Others could materially affect how employers manage compliance, pay governance, and remediation exercises.
The result feels less like “pure minimum transposition” and more like a fairly rigid procedural system built around the PTD.
And the kicker is this: they’re planning to implement on time for 7 June.
Bulgaria’s overall approach to the PTD
The government has chosen to implement most of the Directive through amendments to Bulgaria’s anti-discrimination framework rather than embedding everything directly into the Labour Code.
That is not accidental.
The explanatory documents repeatedly stress that the PTD is, fundamentally, an anti-discrimination instrument rather than simply an employment transparency law. Pay transparency is framed as the mechanism, while gender equality enforcement is framed as the objective.
That legislative philosophy matters because it shapes the overall tone of the draft.
Rather than positioning the reforms primarily as an HR reporting exercise, the Bulgarian approach places the Commission for Protection against Discrimination (“CPD”) at the centre of enforcement and monitoring. The draft significantly expands the CPD’s role beyond reactive complaint handling into proactive oversight, methodology development, technical guidance, monitoring, and data aggregation.
The CPD is clearly being prepared for a much bigger role than it historically had.
The government thinks Bulgaria has a structural transparency problem
The accompanying documents are unusually candid about the government’s view of the current legal framework.
Existing equal pay protections are described as largely “declarative” in nature. The government’s position is essentially that Bulgaria already prohibits discrimination formally, but lacks the mechanisms necessary to detect or challenge it effectively in practice.
Several themes appear repeatedly throughout the impact assessment:
lack of proactive pay transparency;
lack of comparative pay information rights;
weak institutional monitoring;
widespread pay confidentiality practices;
low employer readiness for PTD compliance.
One particularly striking point is the government’s reliance on a consultancy assessment suggesting Bulgarian companies currently score only 1.06 out of 3 for readiness to comply with the Directive’s requirements.
That number quietly explains quite a lot about the draft’s structure.
The legislation repeatedly tries to reduce ambiguity by introducing concrete deadlines, formal procedural obligations, and specified response periods. Bulgaria appears less interested in flexibility than in making sure the machinery actually works.
The practical PTD questions Bulgarian employers are likely to focus on first
For many employers, the most important issues are not actually the reporting thresholds or the drafting philosophy.
They are the operational questions sitting underneath the Directive itself.
And several of those questions remain only partially answered by the Bulgarian draft.
Will salary ranges need to appear in job adverts?
The Bulgarian draft follows the PTD requirement that candidates must receive information about the initial pay level or pay range before interview and before pay discussions take place.
But, like the Directive itself, the draft does not appear to expressly require salary ranges to be physically included inside the job advertisement itself.
That distinction matters.
In practice, there is a major operational difference between:
“the salary must appear in the advert”, and
“the salary must be provided before interview”.
Those are not the same compliance model.
The Bulgarian wording currently appears closer to the second approach.
What counts as “pay” and “pay level”?
One of the most important PTD issues across Europe is that the Directive uses concepts like:
“pay”
“pay level”
“categories of workers”
“average pay levels”
That matters because the meaning can shift depending on the obligation involved.
For example:
the “pay range” disclosed pre-interview may not necessarily be constructed identically to reportable remuneration calculations;
equal pay comparisons may involve broader remuneration analysis than recruitment disclosures;
reporting metrics may require inclusion of additional remuneration elements that are not operationally relevant in hiring discussions.
The Bulgarian draft largely mirrors the PTD architecture here rather than materially redefining these concepts domestically.
So a lot of these arguments will probably end up being fought through guidance, litigation, and eventually CJEU interpretation.
Will the ban on pay secrecy clauses actually change much?
Potentially yes, particularly because the Bulgarian government explicitly identifies pay confidentiality clauses as widespread practice.
The draft prohibits contractual restrictions preventing employees from discussing pay and reinforces this prohibition in both the anti-discrimination legislation and the Labour Code.
Importantly, the Labour Code wording goes further than simply banning clauses in employment contracts. It extends the prohibition across:
collective agreements;
internal remuneration rules;
employer acts more broadly.
In theory, many employers could deal with this relatively quickly by issuing communications confirming that existing secrecy provisions will no longer be enforced.
But the harder issue is usually cultural rather than contractual. Just because people can talk about pay, it doesn’t mean that they will.
How will “equal value” work in practice?
The PTD requires employers to assess work based on objective criteria such as:
skills;
effort;
responsibility;
working conditions.
The Bulgarian draft broadly follows the Directive’s structure here rather than introducing a new approach. No surprises here.
How will employee representatives work under the Bulgarian system?
The Bulgarian draft appears designed to integrate the PTD into existing worker representation structures rather than creating an entirely new representative regime specifically for pay transparency.
In practice, trade unions and existing employee representation mechanisms will probably absorb much of the representative function.
That matters because the effectiveness of PTD processes often depends heavily on how developed employee representation structures already are. In countries with strong works council traditions, the PTD may slot into existing governance relatively smoothly. Elsewhere, it may be much messier.
A lot of employers across Europe still do not actually know who their eventual PTD representatives will be in practice.
Will the pay history ban matter in Bulgaria?
Potentially quite a lot.
The PTD prohibits employers from asking candidates about prior pay history. The practical effect is often larger than it first sounds because salary history has historically functioned as an anchoring mechanism in negotiations.
For many employers (not just in Bulgaria), the real change is behavioural:
recruiter habits;
hiring manager conversations;
negotiation culture;
application form design.
In some businesses, those practices are deeply embedded.
How will Bulgarian pay gap reporting actually work?
One important practical question is whether Bulgaria intends to centralise reporting infrastructure (like in Lithuania) or leave calculation and publication obligations primarily with employers themselves.
The Bulgarian draft currently appears closer to a more employer-driven model.
Employers themselves appear responsible for:
calculating the required indicators;
submitting reporting data;
retaining supporting information;
preparing mandatory justifications where gaps exceed 5%.
Reports must be submitted by 7 June of the relevant reporting year.
The reports are submitted to the CPD rather than simply published informally on a company website.
Which enforcement bodies will actually enforce the PTD in Bulgaria?
The key enforcement actor appears to be the Commission for Protection against Discrimination (CPD). The Bulgarian draft significantly expands its role.
The CPD is not positioned merely as a complaints body. The legislation gives it a nice set of new teeth: broader monitoring, methodological, assistance, and oversight functions.
That includes:
monitoring compliance;
collecting and publishing information;
developing methodological tools;
supporting employers;
aggregating complaint data;
overseeing aspects of reporting and justification processes.
The draft also provides for financial sanctions, including increased penalties for repeat or continuing violations.
Whether the CPD ultimately has sufficiently strong teeth will probably depend less on the legislation itself and more on:
resourcing;
staffing;
technical expertise;
enforcement appetite;
political backing.
The most important areas where Bulgaria goes beyond the PTD minimum
The Bulgarian government insists the draft does not go beyond the Directive unnecessarily.
But here’s where the advertised product doesn’t quite match up with what’s in the box.
Several provisions almost certainly do.
No exemption for employers with fewer than 50 employees
Under Article 6(2) PTD, Member States are allowed to exempt employers with fewer than 50 employees from obligations relating to pay progression criteria.
Bulgaria has chosen not to use that exemption.
This is probably the clearest substantive example of Bulgaria going beyond the minimum PTD baseline.
For smaller employers, this could become more operationally significant than the government’s impact assessment suggests. Many smaller businesses simply do not currently have formalised progression structures capable of easy disclosure.
Mandatory justification for any 5% pay gap
This may end up mattering more in practice than the reporting thresholds themselves.
Under the PTD itself, employers may attach explanations to reported gender pay gaps. The Directive does not automatically require formal justification every time a threshold is exceeded.
The Bulgarian draft takes a much harder line.
Where reporting identifies a pay gap of 5% or more, employers must prepare and submit a justification to the CPD.
Automatically.
Even where the gap may ultimately prove objectively justified.
That shifts the compliance burden forward considerably. Instead of waiting for escalation into a joint assessment process, employers may effectively need defensible explanations prepared from the moment reporting is produced.
Many employers will discover the difficult part is not reporting. It is discovering whether their pay systems can survive scrutiny once explanations become mandatory.
Bulgaria likes hard deadlines
One recurring feature of the draft is its preference for fixed dates and defined response periods where the PTD itself is more flexible.
Examples include:
annual employee notification of pay information rights by 31 January each year (get this on your post Christmas “to do” list now);
pay reporting submissions by 7 June (the PTD’s birthday);
14-day deadlines for clarification responses (VERY short);
mandatory correction of unjustified pay differences within one year following joint assessment.
The PTD itself often uses softer language such as “reasonable period”.
Bulgaria generally does not. It likes things nice and clear.
From a legal certainty perspective, employers may actually welcome this. Ambiguity creates litigation risk. Clear deadlines at least create operational clarity.
But the trade-off is reduced flexibility.
The four-year data retention requirement
The draft introduces a minimum four-year retention obligation for category-level pay data.
That sounds technical. It probably will not stay technical for long.
Once employers begin retaining detailed remuneration data for extended periods, questions around GDPR governance, audit trails, data integrity, and evidential consistency become much more important.
Additional collective bargaining disclosure obligations
The draft also inserts additional transparency obligations into Bulgaria’s collective bargaining framework.
Employers engaged in collective bargaining will need to provide unions with information about:
average pay levels by job level;
rules governing basic remuneration;
additional remuneration structures.
That goes beyond the PTD’s minimum transparency framework and reinforces the broader Bulgarian approach of embedding pay transparency into existing labour relations structures rather than treating it as a standalone exercise.
One area where Bulgaria may actually be more restrictive than the PTD
Interestingly, the Bulgarian draft is not uniformly stricter.
Under one Labour Code provision, additional salary information requests appear limited to once per year (like in Italy).
The PTD itself does not expressly impose such a cap.
That said, the practical significance may ultimately be limited because the broader right under the anti-discrimination legislation appears not to contain the same restriction.
Still, the coexistence of two partially overlapping information-right regimes could create confusion in practice, particularly in the early stages of implementation.
The government is trying very hard to reassure employers
A recurring theme across all the supporting documents is reassurance.
The government repeatedly emphasises that:
obligations are proportionate;
implementation is phased;
burdens on SMEs are limited;
technical assistance will be available;
costs are manageable.
The impact assessment estimates compliance costs for smaller employers at below approximately €132 annually per enterprise, drawing on Eurofound comparator data.
Which, frankly, is ludicrous. The burden is much heavier than that.
Whether employers agree with those assumptions once implementation begins is another question entirely.
Particularly because some of the hardest PTD work is not reporting itself. It is the upstream governance exercise employers often discover they need first:
job architecture;
grading consistency;
documentation quality;
pay rationale defensibility;
historical anomaly remediation.
Those exercises are rarely quick and cheap, even where reporting obligations themselves appear administratively modest.
What Bulgarian employers should probably focus on now
At this stage, the Bulgarian draft still remains draft legislation. The text may evolve during the legislative process.
But several themes already look relatively clear.
1. Bulgaria is building quite a rigid compliance system
Even where Bulgaria stays broadly within PTD boundaries, the draft consistently prefers concrete obligations, procedural specificity, and institutional oversight.
2. Smaller employers are not entirely escaping transparency obligations
Even employers outside formal reporting thresholds may still face significant obligations around pay criteria transparency, recruitment transparency, and information rights.
3. Documentation quality is going to matter
The mandatory justification requirement for 5% pay gaps significantly increases the importance of defensible pay rationale documentation.
For many organisations, the difficult question will not be:
“Do we have a gap?”
It will be:
“Can we explain it coherently under scrutiny?”
4. The CPD is becoming a much more important actor
The draft transforms the CPD from a largely reactive discrimination body into a proactive monitoring and guidance institution.
That institutional shift may end up being one of the most important long-term consequences of the Bulgarian implementation model.
Final thought
Bulgaria’s draft PTD legislation is interesting precisely because of the contrast between its messaging and its mechanics.
Politically and rhetorically, the government presents itself as pursuing restrained, minimum-compliance transposition.
Operationally, though, the draft often chooses precision over flexibility, procedural structure over discretion, and institutional oversight over employer autonomy.
Some of that is probably sensible.
The government clearly believes the existing Bulgarian framework lacks the mechanisms necessary to detect and challenge unequal pay effectively. It’s being unusually clear about its equal pay failings.
From that perspective, tightly specified procedural obligations are not accidental overreach. They are the implementation strategy.
The more important question now is probably not whether Bulgaria has technically gold plated certain provisions.
It is whether employers, regulators, courts, and the CPD can make this framework work in practice, particularly in a market the government itself believes is only marginally prepared for the Directive’s arrival.
And that may ultimately matter far more than whether the legislation is labelled “minimum transposition” or not.