EU Pay Transparency Directive 2026: What Recruitment Agencies Must Know Before June

On June 7, 2026, EU Directive 2023/970 on pay transparency becomes enforceable. Every member state must have transposed it into national law by then. If you're a recruitment agency placing candidates in EU markets, this isn't abstract policy — it changes how you write job ads, negotiate fees, and manage candidate data.

Most agencies haven't prepared. A Mercer survey from late 2025 found that only 28% of European employers had started adjusting their recruitment processes for the directive. For agencies, the number is likely lower — because many assume it's "the employer's problem." It's not. Here's why.

What the directive actually requires

The core principle is straightforward: candidates have the right to know the pay range before they apply. Article 5 of the directive states that employers — or their agents, including recruitment agencies — must provide information about the initial pay level or range "in the job vacancy notice or otherwise prior to the job interview."

That second part matters. "Otherwise prior to the job interview" gives some flexibility, but most national implementations are interpreting this as requiring salary ranges in the job advertisement itself. Germany's draft implementation (BMAS) requires it in the posting. France's implementation follows the same path.

For recruitment agencies, this means every job ad you publish on behalf of a client needs a salary range. No more "competitive salary" or "dependent on experience" without a number. If your client won't give you a range, you can't legally publish the ad in most EU jurisdictions after June 2026.

Reporting obligations that hit agencies indirectly

Companies with 100+ employees must report gender pay gaps to national authorities. Where do they get that data? From their HR systems and, increasingly, from the recruitment pipeline. If your ATS or CRM doesn't track compensation data in a structured way, your clients will need that data from you — and they'll prefer agencies whose systems can provide it.

The European Commission estimates that the directive will affect over 73 million workers across the EU. The compliance infrastructure needs to match that scale.

Three ways this changes agency operations

1. Job ad templates need salary fields

If your current workflow involves copy-pasting client job descriptions without salary information, that workflow breaks in June. Every ad needs a range. Not a point estimate — a range. The directive explicitly protects against "artificially narrow ranges" too, so listing "€50,000–€51,000" won't fly.

Practical minimum: your ATS needs a mandatory salary range field in the job creation workflow. If it's optional, recruiters will skip it. If it doesn't exist, you'll need workarounds that add friction to every posting.

2. Candidate data handling gets more complex

Article 6 prohibits employers from asking candidates about their current or historical pay. This is already law in some US states, but it's new across much of Europe. For agencies that use current salary as a negotiation data point — which is most agencies — this changes the conversation fundamentally.

You can still discuss salary expectations. But you can't ask "What do you earn now?" and use that to anchor the offer. Your CRM needs to distinguish between "candidate's salary expectation" (legal to collect) and "candidate's current salary" (prohibited to ask). If your database has a single "salary" field, you've got a compliance gap.

3. Fee structures may need adjustment

Many contingency agencies calculate fees as a percentage of first-year salary. With salary ranges published in job ads, candidates know the range before they walk in. Negotiation dynamics change. The 20-25% fee on a transparently-published salary becomes more visible to candidates and hiring managers alike. Some agencies will need to articulate their value differently.

What your ATS needs to handle

Not every ATS is built for pay transparency compliance. Here's what to check:

• Mandatory salary range fields — Not optional. Configurable per market (because different countries will have different thresholds and formats).
• Compensation data separation — Distinct fields for "expected salary" vs. historical salary data, with the latter flagged or removed for EU roles.
• Audit trail — When regulators ask how you handled pay data, you need logs. Which recruiter accessed what compensation data, when.
• Multi-jurisdiction support — The directive sets a floor, but national implementations vary. An agency operating across Germany, France, and the Netherlands needs to handle three sets of rules.

Yena is built for multi-market recruiting with GDPR compliance at its core. The structured candidate profiles, CRM data separation, and audit logging cover the data handling requirements. For agencies placing executive talent across EU borders, these aren't nice-to-haves anymore — they're legal requirements.

Country-by-country implementation status

As of March 2026, implementation progress varies significantly:

The Nordic countries are an interesting case. Sweden's Discrimination Act already required pay surveys. Denmark's Equal Pay Act mandated gender-split pay statistics for companies with 35+ employees. For agencies operating in Scandinavia, the directive is mostly business as usual. For those in Germany or Poland, it's a fundamental shift.

What happens if you don't comply

The directive requires "effective, proportionate and dissuasive" penalties. Article 23 shifts the burden of proof: if a candidate claims pay discrimination, the employer (or their agent) must prove there was none. That's a reversal of the default legal position in most jurisdictions.

For recruitment agencies, the practical risk is reputational as much as legal. Clients will increasingly require compliance certifications from their agency partners. If your systems can't demonstrate pay transparency compliance, you'll lose mandates to agencies that can.

Preparing now vs. scrambling in June

Three months isn't much time. But the preparation is manageable if you start with the operational changes rather than trying to overhaul everything at once.

First, audit your job ad templates. Do they have salary range fields? Are those fields mandatory? If not, fix that now. Second, review your candidate data collection. Remove or flag any "current salary" fields for EU roles. Third, talk to your clients. Many haven't thought about this either, and the agency that proactively brings compliance solutions earns trust.

The GDPR compliance guide we published covers the data handling fundamentals. Pay transparency adds a layer, but if your GDPR house is in order, the incremental effort is manageable. If it isn't — well, June is going to be interesting.