Relationship of subordination: the signals that get a service reclassified as employment

You've found the right tech freelancer, but your procurement department refuses to sign a non-EU supplier, or your legal team flags the relationship of subordination. The topic isn't theoretical. It can call into question the qualification of the relationship, weaken your subcontracting and expose the firm to a reclassification risk.

The key point is simple: a freelancer can be genuinely independent on paper, but treated as an employee in fact. It's that operational reality that counts.

Key takeaway The relationship of subordination doesn't depend on the contract's name. It depends on how the mission is carried out: orders, control, sanctions, hierarchical integration, absence of genuine autonomy.

Relationship of subordination: an operational definition for a firm

In French law, the relationship of subordination is classically defined as the performance of work under the authority of a person who has the power to give orders and instructions, to control their execution and to sanction failures.

This definition comes notably from the French Supreme Court's "Société Générale" case law, often cited in reclassification matters.

For an IT services firm, the topic appears as soon as a freelancer is managed like an internal staff member:

• hours imposed as on an employee;
• daily validation by a hierarchical manager;
• no clearly defined deliverables;
• activity reporting comparable to disciplinary control;
• full integration into the client's org chart;
• an internal email address and signature as a team member;
• participation in internal rituals with no role distinction;
• an obligation to exclusively use internal tools, methods and rules;
• practical impossibility of refusing an instruction;
• strong economic and operational dependence.

No single indicator is ever enough on its own. It's a body of indicators that allows the risk to be assessed.

A framing meeting isn't a relationship of subordination. A project committee isn't an employment contract. A quality requirement isn't a disciplinary sanction.

The risk appears when the relationship tips from an independent service into placement under authority.

Why the topic is sensitive for IT services firms

A firm buys skill, resells a service and must secure its contractual chain. When a tech freelancer based outside the EU works for a French end client, several layers of risk stack up.

The first risk is the reclassification of the relationship as an employment contract if the real conditions of execution reveal a relationship of subordination.

The second risk is disguised employment. It targets situations where the displayed independence doesn't match the reality of the mission.

The third risk concerns subcontracting. Sound subcontracting rests on a scope, deliverables, a qualified outcome or best-efforts responsibility, and sufficient execution autonomy. Fragile subcontracting looks like a mere supply of labour.

Finally, there's a supplier-compliance topic: KYC, contract, invoicing, taxation, VAT, international sanctions, the ability to pay the provider, documentation and traceability.

For a firm, the problem is therefore not just to "find a freelancer". The problem is to contract cleanly with a party who may be unreferenced, non-European, and misaligned with the end client's procurement requirements.

Reclassification: what triggers the alert

Reclassification consists in considering that a relationship presented as independent actually corresponds to salaried employment.

In a tech mission, the following signals must be watched.

The management is hierarchical

The freelancer receives direct orders daily. They don't discuss an objective or a deliverable. They execute instructions like a member of the salaried team.

The difference matters.

A client can express a need, define priorities, request corrections and check a deliverable's compliance. That's normal in a service.

By contrast, it shouldn't exercise disciplinary power or treat the freelancer as an employee placed under its authority.

The contract doesn't describe an outcome

A mission worded only in person-days, with no scope, no deliverables and no acceptance criteria, increases the vagueness.

The day rate is a market practice. It isn't prohibited in itself. But the day rate must not become the only economic object of the relationship.

A more robust service describes:

• the context;
• the objectives;
• the expected deliverables;
• the validation rules;
• each party's responsibilities;
• the provider's level of autonomy;
• the project-coordination terms.

The freelancer is integrated like an employee

The risk rises if the freelancer appears as a permanent member of the organisation.

Typical examples:

• inclusion in the internal org chart;
• management of salaried teams with no clear framework;
• blanket access to internal tools with no limits;
• an obligation to book leave;
• absence approvals like an employee;
• participation in HR interviews;
• an email address with no mention of their external status.

Operational integration is sometimes necessary for security or delivery reasons. It must remain proportionate and consistent with a supplier relationship.

The client controls time instead of controlling the service

It's legitimate to track a project's progress. It's riskier to control time like an employer.

The nuance is concrete.

A progress report is compatible with a service. Monitoring comparable to working-time surveillance can feed the body of indicators of subordination.

Sound subcontracting vs fragile subcontracting

Subcontracting isn't a problem in itself. It's a normal tool for a firm.

The risk comes from poorly structured subcontracting.

Sound subcontracting The provider works as an autonomous supplier. The contract describes a scope, deliverables, acceptance terms and a coordination framework. The exchanges serve to steer the service, not to exercise hierarchical authority.

Fragile subcontracting The provider is presented as a freelancer, but assigned like an internal resource. The deliverables are vague. The client gives direct orders. The control targets presence rather than output. The relationship looks like staff secondment.

For a firm, the line must be materialised in the contracts, the purchase orders, the operational exchanges and the evidence kept.

The contractual document isn't enough. The practices must follow.

The particular case of the non-EU tech freelancer

Firms increasingly work with freelancers based in Dubai, Bali, Mauritius, Morocco or elsewhere outside the EU. This type of relationship can be perfectly legitimate, but it demands stronger documentary discipline.

The tax point must be handled with caution.

Tax residence is not declared. It depends on reality: effective place of living, duration of presence, centre of personal and economic interests, local conditions, absence of an organised presence in France.

A sound configuration notably assumes:

• a freelancer genuinely a tax resident outside the EU;
• an activity genuinely carried out remotely;
• no habitual or organised presence in France;
• a local entity or status consistent with the activity;
• aligned invoices and supporting documents;
• a mission carried out without a permanent establishment in France.

Conversely, an abusive configuration would be, for example, a shell entity used to invoice from abroad while the activity is directed and carried out in France. This type of arrangement exposes you to tax and social-security risks and must not be pursued.

StelarWork does not sell tax optimisation. If a freelancer is already a genuine non-EU tax resident, with a consistent remote activity, StelarWork removes an administrative friction for the French firm by structuring the purchase of the service through a French supplier.

Compliance point The topic isn't to artificially turn a French situation into a foreign one. The topic is to document an existing international reality and make it contractually purchasable by a French firm.

Permanent establishment: another risk not to confuse

The relationship of subordination mainly concerns the social-security risk and the qualification of the work relationship.

Permanent establishment falls under a different register — tax. It can arise when a foreign activity has, in France, a presence or a representative capable of binding the business there.

In a relationship with a foreign freelancer, any confusion about the French intermediary's role must be avoided.

StelarWork contracts in its own name. StelarWork doesn't act as the freelancer's representative in France and doesn't conclude contracts in the freelancer's name. The firm has an identified French supplier, with its own contract and its own invoicing.

This structuring aims to clarify the contractual chain, without artificially creating a French presence for the freelancer.

How to reduce the subordination risk

The risk isn't handled in a clause alone. It's managed before, during and after the mission.

1. Formalise a service, not a presence

The purchase order must describe what's expected.

To prefer:

• a technical work package;
• an audit;
• development of a module;
• a migration;
• fixing of an identified scope;
• documentation;
• acceptance testing;
• support on qualified incidents;
• architecture guidance with deliverables.

To avoid:

• a wording that only describes availability;
• a generic assignment with no objective;
• a role interchangeable with an employee's;
• a mission with no end and no exit criteria.

2. Frame the operational oversight

Coordination is normal. A hierarchical relationship isn't.

The right reflexes:

• appoint a project contact, not an HR manager;
• frame meetings as progress points;
• check deliverables, not the person;
• document the validations;
• avoid disciplinary-style wording;
• don't manage leave like an employee's.

3. Protect the freelancer's autonomy

A freelancer must retain organisational autonomy compatible with the mission.

That doesn't mean they work without constraints. A tech project often imposes security, scheduling, environment and quality constraints.

But the organisation must remain that of an independent provider: responsibility for their execution, no disciplinary power for the client, freedom of organisation within the agreed framework.

4. Align the contract and the practices

Many risks arise from a gap between the contract and reality.

A contract can speak of deliverables. If, in fact, the freelancer receives daily orders, asks permission to be away and appears as the end client's employee, the contract loses its probative force.

Compliance plays out in the evidence:

• purchase orders;
• specifications;
• validation reports;
• deliverables;
• invoices;
• framing exchanges;
• proof of residence or status where relevant;
• KYC documentation;
• subcontracting and confidentiality clauses.

Where StelarWork fits in the firm-freelancer chain

StelarWork steps onto the contract between a French firm and a tech freelancer based outside the EU when the firm can't, or won't, sign this supplier directly.

Concretely, StelarWork becomes the firm's French supplier for a defined service. The firm issues a purchase order to StelarWork. StelarWork invoices the firm, contracts in its own name with the foreign freelancer and pays them under the agreed conditions.

The goal is to make the relationship purchasable and documented for the firm:

• a French supplier;
• a contract under French law on the firm's side;
• invoicing compatible with procurement circuits;
• documentary checks;
• a service framework;
• back-to-back alignment;
• traceability of the flows;
• reduced friction linked to non-EU suppliers.

This model doesn't turn the freelancer into an employee. It doesn't rest on an employment contract. It doesn't consist in domiciling the freelancer or acting as their representative in France.

StelarWork structures a service relationship between professionals, with a contractual framework designed to reduce non-compliance risks.

What the firm must keep in mind

Even with a contractual intermediary, the execution of the mission remains decisive.

If the end client manages the freelancer like an employee, the risk doesn't magically disappear. It must be handled in the framing, the governance and the operational practices.

The right approach is to align four levels:

1. the firm-supplier contract;
2. the supplier-freelancer contract;
3. the purchase order and the deliverables;
4. the daily oversight practices.

The relationship of subordination is a risk of reality. It's therefore reduced by a consistent reality.

Clause, process, evidence: the compliance triptych

For a firm, compliance must not be an isolated document. It must be a simple system.

The clause sets the framework. The process organises the execution. The evidence demonstrates the consistency.

A well-structured mission must allow you to answer these questions clearly:

• Who is the firm's contractual supplier?
• Which service is ordered?
• Which deliverables are expected?
• Who validates the result?
• How are the exchanges documented?
• Does the freelancer have genuine autonomy?
• Are the freelancer's residence and status consistent with the invoicing?
• Does the end client avoid practices comparable to employee management?

This level of rigour is especially useful when the freelancer is technically excellent but hard to reference directly: a foreign company, a non-EU bank account, the absence of documentation expected by procurement, VAT uncertainty or internal compliance requirements.

FAQ

What is a relationship of subordination?

The relationship of subordination corresponds to a situation in which a person works under the authority of another, who can give them orders, control their work and sanction their failures.

In a freelance relationship, the risk appears if the client acts like an employer rather than like a client ordering a service.

Can a freelancer work in a staffing set-up without risk?

The term "staffing" ("régie") is often used in IT services firms, but it must be handled with caution. The risk rises when the mission looks like a mere assignment of personnel, with no deliverables or autonomy.

A day-rate service can be framed cleanly if it describes a scope, objectives, responsibilities and validation terms.

Does the day rate automatically create a relationship of subordination?

No. The day rate is an economic pricing method. It doesn't automatically create a relationship of subordination.

The risk mostly depends on the real conditions of execution: autonomy, oversight, deliverables, the absence of disciplinary power, a clear distinction from employees.

Does disguised employment also concern non-EU freelancers?

Yes, the topic can arise when the reality of the relationship looks like salaried employment. The analysis nonetheless depends on the facts, the contracts, the place of execution, the applicable law and the practices.

Tax consistency must also be checked: genuine residence, effective remote activity, no organised presence in France and no artificial arrangement.

Can a firm sign directly with a freelancer based in Dubai or Bali?

It's sometimes possible, but often complex in practice. The blocks come from procurement, compliance, taxation, invoicing, KYC checks or the risk of an unreferenced supplier.

StelarWork answers this friction by acting as the firm's French supplier for a defined service, without substituting for a personalised legal or tax analysis.

Does StelarWork remove all reclassification risk?

No. No serious contractual arrangement should promise the total absence of risk.

StelarWork is designed to reduce friction and structure the relationship within a compliant service framework. The operational reality remains essential: no employee-style management, no disciplinary power, no confusion with internal teams.

What's the difference between project coordination and a relationship of subordination?

Project coordination consists in tracking progress, validating deliverables, organising dependencies and ensuring quality.

The relationship of subordination appears when the client exercises authority comparable to an employer's: hierarchical orders, individual control, sanctions, time management and integration as an employee.

Should you seek legal advice before structuring this type of mission?

For sensitive situations, yes. Reclassification, international taxation, subcontracting and permanent establishment depend heavily on the facts.

This article is intended as general information. It does not constitute personalised legal, tax or social advice. A suitable analysis must be carried out with your usual advisers when the situation warrants it.