Under the EU Pay Transparency Directive, an employer may not ask a candidate how much they earn, and has to tell them what the job pays. What the rules say, where the problem hides and how to fix it.
Open your company's job application form, the one a candidate fills in on your website or in your recruitment software. Scroll through the fields: personal details, education, experience, availability. If one of them says "current salary", "current package" or "last salary", that field is asking for something EU law now says an employer shall not ask.
It is one of the few compliance obligations that can be checked in a minute and fixed in an hour. It is also recent: a form set up before June 2026 may well not reflect it.
Directive (EU) 2023/970 on pay transparency, which Member States had to transpose by 7 June 2026, contains a whole article on the stage before hiring. Article 5 sets three rules.
The ban. "An employer shall not ask applicants about their pay history during their current or previous employment relationships" (Article 5(2)). The recitals go further in explaining the intent: employers "should not be allowed to enquire or proactively try to obtain information about the current pay or prior pay history of an applicant for employment" (recital 33).
The duty to say what the job pays. Applicants have the right to receive, from the prospective employer, information about "the initial pay or its range, based on objective, gender-neutral criteria, to be attributed for the position concerned" and, where applicable, the relevant provisions of the collective agreement. The information must be provided "in a manner such as to ensure an informed and transparent negotiation on pay, such as in a published job vacancy notice, prior to the job interview or otherwise" (Article 5(1)).
Neutrality. Employers must ensure that "job vacancy notices and job titles are gender-neutral and that recruitment processes are led in a non-discriminatory manner" (Article 5(3)).
The Directive applies to employers in the public and private sectors, and, for the purposes of Article 5, to applicants for employment (Article 2). The size thresholds in the Directive concern other obligations, such as reporting on the gender pay gap, not Article 5.
One practical note. As a rule, a directive does not impose obligations on private employers directly: the obligations reach them through each country's implementing law, and the details can differ. Italy is an example of a country that has spelled things out more precisely. Its implementing decree, Legislative Decree 96/2026, in force since 7 June 2026, requires the pay information to appear in the job advertisement itself, and states that pay history cannot be obtained "even indirectly", through those to whom the employer has entrusted selection or hiring (our translation). Wherever you hire, it is worth checking how the national law reads.
The reasoning is set out in the recitals of the Directive. The first reason is an imbalance: "The lack of information on the envisaged pay range of a position creates an information asymmetry which limits the bargaining power of applicants for employment" (recital 32). The second is subtler. A past salary carries all the gaps of the past with it: if someone was paid less in a previous job, starting the offer from that number carries the imbalance into the new relationship. Hence the Directive's aim to "disrupt the perpetuation of the gender pay gap affecting individual workers over time" (recital 33).
The point matters even more when software is involved. A figure entered in a form does not sit still: it can become a filter, a sorting criterion, an element of a score. What would be a single question in an interview becomes, in an automated system, a rule applied to every application.
The ban is simple to state. The hard part is finding it, because the forbidden question is rarely written in a document anyone rereads. It usually lives in three places.
The form and the recruitment software. Some fields in an application form may come pre-set by the software vendor, or may have been configured years ago and never looked at again. The wording of Article 5(2) does not distinguish between mandatory and optional fields: it says the employer shall not ask. A "current salary" field, even an optional one, is a question put to the candidate.
The recruitment agency. If you hand a search to an agency or a headhunter, their forms, candidate profiles and interview habits are part of the picture. Recital 33 speaks of employers not trying to "obtain" this information, and some national laws, such as Italy's, name intermediaries expressly.
The interview. "What are you earning now?" is the most natural question in a negotiation, and it is exactly the one that is banned. The same goes for asking to see a recent payslip, which is another way of obtaining the same information.
One clarification, to avoid the opposite mistake: Article 5(2) concerns pay history in current or previous employment. A candidate's expected salary is a different piece of information, and the text does not mention it. It should still be handled with care, so that it does not become an indirect route to the same figure.
The ban takes a piece of information away from the employer; Article 5(1) gives one to the candidate. Applicants must be told the initial pay or its range, set on objective, gender-neutral criteria, together with the relevant collective agreement provisions where applicable. For many companies this is a bigger change of habit than the first: removing a field is not enough, a range has to be decided for each position and justified.
Here too the point is not just formal. A range set in advance, on stated criteria, is the best defence if a difference in treatment is later challenged. Pay decided case by case, starting from what each candidate used to earn, is the opposite.
The Directive leaves the penalties to national law, but it sets the framework Member States have to follow.
Burden of proof. Member States must ensure that, in administrative or court proceedings on alleged pay discrimination, "where an employer has not implemented the pay transparency obligations set out in Articles 5, 6, 7, 9 and 10, it is for the employer to prove that there has been no such discrimination" (Article 18(2)). The rule does not apply where the employer proves that the infringement was "manifestly unintentional and of a minor character".
Compensation. Workers who have suffered damage as a result of an infringement of a right or obligation relating to equal pay must be able to obtain "full compensation or reparation", which "shall not be restricted by the fixing of a prior upper limit" (Article 16).
Penalties. Member States must lay down "effective, proportionate and dissuasive penalties", which "shall include fines" (Article 23). According to the recitals, such fines could be based on the employer's gross annual turnover or total payroll (recital 55).
How this translates into national law varies from country to country. Italy, for instance, did not introduce a specific fine for breaches of the pre-employment rules in its implementing decree, and relies on its existing equal opportunities code, which already penalises, for example, job advertisements that state a required sex. That is exactly why the question is not "what is the fine for a wrong field?" but "what does that field say about us if someone challenges a hiring decision?". A form that asked for current salary is hard to explain at that moment.
These are small changes, and almost all of them cost nothing. But they have one feature that sets them apart from many other compliance tasks: they are visible. An application form is public, and anyone, including someone who might one day challenge you, can open it and read it.
Probum AI, based in Italy, reviews what a company asks candidates, what its software collects and what stays documented, as part of a signed compliance dossier.
Write to us