If your agency has been operating under "we'll figure it out if it ever comes up", 2026 is the year you'll figure it out the expensive way.
Three EU-wide regulatory shifts are now live or in implementation. Each one has direct consequences for agencies placing non-EU workers in Europe. We're seeing all three trigger actions against partner agencies that did not adapt.
1. The recruitment fee ban, properly enforced
The principle that workers should not pay for their own recruitment is not new. What's new is enforcement. Germany's Federal Employment Agency now actively cross-checks candidate-paid amounts against employer-paid placement fees, and discrepancies trigger withdrawal of ZAV authorisations. The Netherlands has tightened its Waadi licensing for recruiters. Ireland enforces the Employment Permits Act fee rule via labour inspectors.
What this means in practice:
- Charging the candidate "agency processing fees" on top of the employer fee is a regulatory red flag. Pick a side.
- "Document translation fees" that don't match the actual translator invoice are also flagged. Pass-through with receipts only.
- Refund obligations now bite. If a candidate cancels and you've collected fees, most jurisdictions now require a documented refund timeline (typically 14–30 days).
Workium's Zero Deposit programme removes this surface entirely — the candidate pays nothing, ever, and the agency invoices Workium at milestones. Agencies that cannot operate without candidate-side deposits should be reviewing their model now, not later.
2. Equal pay for posted workers (the second wave)
Posted-worker rules (Directive 2018/957/EU) require posted workers to be paid no less than the host country's collectively agreed wage. The first wave hit construction and HORECA. The 2026 second wave extends enforcement to logistics, warehousing, manufacturing, and care.
The trap: agencies sub-contracting through cheaper home-country employment vehicles to undercut host-country wages. This is now actively prosecuted in Germany (Mindestlohngesetz + AEntG), Belgium (Limosa cross-checks), and Finland (occupational safety + tax authority).
Audit your placement contracts: does the wage paid to the candidate, in the host country, match or exceed the host country's collective agreement for the role? If not, your placement is non-compliant regardless of what the candidate signed.
3. AML scope widens to cover migration agencies
The 6th Anti-Money-Laundering Directive (6AMLD) plus the new EU AML Authority (AMLA) has made "obliged entity" status much harder to escape for migration agencies. If you handle candidate funds (deposits, travel costs, document fees) above €10,000 in aggregate per transaction chain, you are now in scope in most member states.
That means:
- Customer due diligence (CDD) on every candidate — passport ID + source of funds.
- Politically-Exposed-Person (PEP) screening.
- Suspicious-Activity Report (SAR) filing within statutory windows.
- Record retention for 5 years.
Most non-EU agencies operating placement programmes are caught by this without knowing. Banks have started closing accounts of agencies that can't provide AML evidence. We've seen three partners lose their primary banking relationship in the last six months — all of them survivable, all of them avoidable.
What we recommend agencies do this quarter
- Run a fee-flow audit. For every active placement, can you produce a paper trail showing every euro the candidate paid and what it was for? If not, you have an enforcement risk.
- Pull your placement contracts and verify that the host-country wage paid matches the host-country collective minimum for the role. Document the source.
- Get an AML opinion from a local lawyer in your primary country of operation. It's a 2-hour engagement and it tells you exactly where you stand.
- Move to milestone-paid models where possible. They solve fee compliance, refund obligations, and AML transparency in a single architectural change.
Compliance in 2026 isn't a project. It's an operating constraint. The agencies that survive the next five years are the ones who built that constraint into their software, their contracts, and their pricing — not the ones who treat it as a quarterly headache.
Found this useful?
Get our next insight first — straight to your inbox.