What "disguised employment" actually means
Picture a cloud engineer who has been billing the same client for eighteen months. She attends every stand-up, works on a company-issued laptop, requests time off through the client's manager and appears on the team org chart. Her contract says "independent contractor". Her working life says "employee". That gap has a name — disguised employment — and regulators across Europe are increasingly willing to close it by reclassifying the relationship, with painful consequences for both sides.
The core principle is the same everywhere: labour courts and social security inspectors look past the label on the contract and examine how the relationship operates in practice. France's social security authorities, the UK's off-payroll rules and Luxembourg's labour courts all apply variations of the same logic. For IT contractors — developers, data specialists, cloud and security engineers — the exposure is structural: long engagements, embedded agile teams, on-site presence and deep access to the client's systems all pull the relationship towards something that looks exactly like employment.
The subordination test: what inspectors look for
Reclassification hinges on proving subordination — that the client directs, controls and can sanction the contractor the way an employer would. In practice, assessors weigh a bundle of indicators:
- Direction and control — does the client set your hours, require on-site presence or approve your holidays as it would for staff?
- Integration — an internal email address, a badge, a fixed desk, participation in team rituals and internal performance reviews.
- Economic dependence — one client accounting for virtually all of your revenue over a long period.
- Power to sanction — can the client discipline you, cut your pay or remove you the way it would remove an employee?
- Lack of technical autonomy — you execute detailed task-level instructions instead of delivering an outcome defined in the contract.
No single indicator is decisive; it is the accumulation that tips a case. A developer embedded in a squad five days a week, with no other client for two years, whose tickets and working hours are assigned by the client's tech lead, already ticks most of the boxes.
What is at stake — for you and for your client
The client's exposure
- back payment of employer social contributions over several years, plus surcharges and penalties;
- liability for concealed employment, which can carry heavy financial and, in serious cases, criminal sanctions;
- retroactive employee entitlements: paid leave, bonuses, overtime, severance;
- reputational damage and potential exclusion from certain tenders.
The contractor's exposure
Reclassification is rarely a windfall for the contractor. The proceedings are long and uncertain, and they destroy the commercial relationship. Your legal structure and your past invoicing can be challenged, with tax and social security consequences cascading backwards over several years. Most importantly, sophisticated clients now screen for this risk before signing anything: procurement departments at large accounts increasingly refuse contracting setups they could not defend in front of an inspector. An ambiguous status does not just threaten your current engagement — it quietly shrinks your future pipeline.
How umbrella employment removes the ambiguity
Umbrella employment — portage salarial in the French-speaking market — attacks the problem at its root by making your status unambiguous. The relationship becomes triangular: you sign a genuine employment contract with the umbrella company, and the umbrella company signs a commercial services agreement with your client. France locked this model into law in 2015 and gave it a dedicated collective bargaining agreement; comparable mechanisms exist in Luxembourg and across Europe for consultants working in cross-border environments.
This architecture changes the legal analysis entirely:
- You are already an employee — of the umbrella company. A real employment contract, real payslips, contributions actually paid: there is nothing left to reclassify in your relationship with the client.
- The client buys a service, not a role. The commercial contract defines scope, deliverables and price — not a job description.
- Your autonomy is built into the framework. You negotiate your own daily rate, choose your engagements and organise your work as you see fit.
- The umbrella company acts as a safeguard, reviewing sensitive clauses before signature and flagging any drift towards excessive integration during the engagement.
This protection comes at a known and predictable cost: management fees typically run between 5 and 10% of billings, on top of employer contributions of roughly 42% and employee contributions of around 22%, plus a financial reserve of about 10%. Net pay usually lands between 47 and 55% of revenue — in exchange for full social protection and a status no inspector can question. To see the exact numbers for your own situation, run them through our salary calculator.
| Criterion | Direct contracting | Umbrella employment |
|---|---|---|
| Legal status | Must be defended if audited | Employee of the umbrella company |
| Reclassification risk | Real on long single-client missions | Neutralised by the employment contract |
| Social protection | Limited, self-funded | Full coverage: healthcare, pension, unemployment |
| Contract review | You negotiate alone | Reviewed and secured by the umbrella company |
Five habits that keep your engagement clean
- Contract for outcomes, not hours. The agreement should describe a deliverable, milestones and a scope — never a work schedule.
- Own your methods. Following the client's technical standards is normal; taking detailed instructions on every task is not.
- Avoid de facto exclusivity. Keep prospecting and diversify your references — browsing open IT missions regularly is simply good professional hygiene.
- Document your autonomy. Outcome-focused status reports and technical proposals issued under your own name carry real weight if an inspection ever comes.
- Have every amendment reviewed. Extensions and scope changes are where relationships quietly drift; that review is exactly what your umbrella company is there for.
Secure your status without giving up your margin
Reclassification risk concentrates precisely where IT contracting lives: long missions, single clients, embedded delivery teams. Umbrella employment lets you keep the commercial freedom of independent work while making your legal status effectively unchallengeable. Before you negotiate your next engagement, make sure your rate actually funds that protection: our daily rate calculator helps you set a fee consistent with the net income you are targeting.
