Undeclared work in subcontracting: the line not to cross with a non-EU freelancer

A non-EU tech freelancer can be excellent, available and already part of your sourcing. The trouble starts when you have to contract them cleanly into a French subcontracting chain.

For an IT services firm, this isn't just administrative. It touches on the risk of undeclared work, supplier compliance, reclassification, invoicing, internal control and liability towards the end client.

A provider based in Dubai, Bali or elsewhere outside the EU can be perfectly legitimate. But if the relationship is poorly structured, it can become hard to justify in an audit, an inspection or a contractual incident.

The issue is therefore simple: turn a technically possible mission into a legally readable, documented service compatible with your compliance requirements.

Undeclared work: why the topic concerns IT services firms

Undeclared work mainly targets two situations:

• concealment of activity;
• concealment of salaried employment.

In a firm's chain, the risk appears when the actual service doesn't match the contractual form on display.

A freelancer is presented as independent but works in conditions close to an employee's. A foreign supplier invoices with no real operational substance. A mission is carried out in France with no clear framework. Compliance documents are missing. The relationship then becomes fragile.

For a firm, the risk isn't only criminal or social-security related. It's also commercial.

An end client can ask for supporting documents. A procurement department can block a referencing. A legal department can refuse a non-EU supplier. An internal audit can detect an inconsistency between the contract, the invoice, the deliverables and the operational reality.

Undeclared work is therefore addressed upstream, when structuring the subcontracting.

The sensitive case of the non-EU freelancer

The non-EU freelancer concentrates several frictions.

They don't always have a structure equivalent to a European company. They don't provide the documents French procurement expects. Their invoice may not fit your usual accounting circuits. Their tax residence may be legitimate but hard to demonstrate. Their relationship with the firm can be perceived as too direct.

It's not a competence problem. It's a problem of proof and qualification.

A firm must be able to demonstrate that the mission is a genuine provision of services, carried out by an identified supplier, within a consistent contractual framework, with deliverables, traceable invoicing and the absence of any relationship of subordination.

Without that, the non-EU freelancer becomes an "unsignable" supplier, even if the mission is sound operationally.

A freelancer who is a genuine non-EU tax resident isn't a problem in principle. The risk arises when reality doesn't match the arrangement presented: fictitious residence, organised presence in France, shell entity, absence of deliverables, oversight like an in-house employee.

Undeclared work and subcontracting: the points of attention

In a subcontracting relationship, form isn't enough. The contract must match the reality of the mission.

Several signals must be examined.

1. A mission framed as plain staffing

When the freelancer is integrated as an interchangeable resource, managed hour by hour, with no deliverables or responsibility of their own, the relationship becomes harder to defend.

A sound service must be described by a scope, objectives, deliverables, acceptance criteria and governance.

The day rate can remain an economic mode. But it must not be the only structuring element of the relationship.

2. Excessive operational dependence

The reclassification risk rises when the provider receives permanent direct orders, uses the same circuits as employees, has no organisational autonomy and bears no economic risk.

The goal isn't to remove all oversight. A firm must obviously monitor the service. But the monitoring must stay compatible with a relationship between independent professionals.

3. An incomplete contractual chain

Subcontracting must be documented back-to-back.

The purchase order, the contract, the client order, the deliverables and the invoicing must tell the same story.

If the firm sells a structured service to its end client but actually buys an unframed individual capacity, the gap creates a risk.

4. Insufficient supplier documentation

For a French supplier, procurement departments often request standard elements: legal identification, certificates, insurance, compliant invoices, VAT, bank details, contractual clauses.

For a non-EU freelancer, these documents can be absent, non-equivalent or hard to verify.

The firm then ends up carrying a disproportionate compliance burden for a sometimes urgent mission.

5. A poorly controlled presence in France

A freelancer genuinely based outside the EU can work remotely for a French firm. That's a possible configuration.

It becomes sensitive if the freelancer in practice works from France, intervenes regularly on site, has a stable organisation in France or presents a foreign tax residence that doesn't match reality.

The principle to keep in mind is that of reality: effective residence, consistent physical presence, an activity genuinely carried out remotely, no organised set-up in France.

Sound configuration vs abusive configuration

The difference between compliant subcontracting and a risky arrangement often comes down to the consistency of the facts.

Sound configuration

A tech freelancer genuinely resides outside the EU. They carry out their activity remotely. They have professional autonomy. The mission is contracted as an outcome-based service. The deliverables are defined. The invoicing is traceable. The contractual chain is consistent. No organised presence in France is set up.

In this configuration, the main issue is to make the relationship compatible with French supplier-compliance requirements.

Abusive configuration

A freelancer claims to be a non-EU resident but actually works from France. A foreign entity with no substance invoices the mission. The provider is managed like an employee. Deliverables don't exist. The direct relationship bypasses procurement procedures. The stated tax setup doesn't match reality.

This configuration exposes the firm to social-security, tax, contractual and reputational risks.

StelarWork does not sell tax optimisation. The fact that a freelancer is in a country with a different tax regime relates to their pre-existing situation, provided it's genuine: effective residence, presence outside France, an activity genuinely carried out remotely. A shell entity or a fictitious residence is an abusive scheme to be ruled out.

Reclassification: the risk behind a poorly framed relationship

The reclassification risk appears when the independence on display doesn't match reality.

The criteria observed can include:

• the existence of a relationship of subordination;
• the absence of autonomy in organising the work;
• integration into an internal team like an employee;
• the absence of a client base or an economic risk of one's own;
• exclusive use of the client's tools, hours and processes;
• direct, permanent instructions with no outcome responsibility.

For a firm, the risk is heightened when the freelancer is presented to the end client as a mere individual resource, with no clear contractual framing.

Good practice is to maintain a service relationship: scope, deliverables, governance, responsibility, invoicing and documentation.

Due diligence: what the firm must be able to demonstrate

Supplier due diligence isn't limited to collecting documents. It consists in being able to demonstrate that the firm took reasonable precautions before and during the relationship.

In the case of a non-EU freelancer, this notably involves verifying:

• the provider's identity;
• their professional status;
• their country of effective residence;
• the consistency between the mission and its place of execution;
• the compliance of the invoices;
• the subcontracting clauses;
• confidentiality and security;
• intellectual property obligations;
• the absence of an organised presence in France when the model relies on remote work;
• the consistency between the client contract and the supplier contract.

The goal isn't to obtain absolute security. It doesn't exist. The goal is to reduce grey areas and make the relationship defensible.

Why procurement circuits often refuse non-EU freelancers

Many firms know how to work with French independent contractors. The trouble starts when the supplier no longer fits the boxes.

A non-EU freelancer can trigger several blocks:

• no company registration number or readable equivalent for internal teams;
• inability to provide certain French certificates;
• non-standard invoices;
• VAT or reverse-charge uncertainty depending on the case;
• contractual clauses that are hard to get accepted;
• difficulty proving residence and place of execution;
• concern about intellectual property;
• a perceived reclassification risk;
• the end client's refusal to have a direct foreign link in the chain.

These blocks don't mean the mission is impossible. They mean the relationship must be structured differently.

StelarWork's role in the subcontracting chain

StelarWork acts as a French supplier between the firm and the tech freelancer based outside the EU.

StelarWork contracts in its own name with the firm. It invoices the firm. It contracts separately with the freelancer. It carries the compliance framework, the supplier documentation and the consistency of the contractual chain.

The goal is to let the firm work with non-EU talent without contracting directly with a supplier that's hard to reference.

The freelancer remains an independent provider. The relationship is structured as a service, with a scope, deliverables and professional obligations.

StelarWork does not present itself as the freelancer's representative in France. It doesn't conclude any contract in the freelancer's name. It acts as a contracting party in its own name, in a French-supplier logic.

This distinction matters. It aims in particular to avoid ambiguities relating to permanent establishment, contractual representation and the chain of liability.

The value for the firm isn't to "bypass" a procurement procedure. It's to replace an uncertain direct relationship with a more readable supplier chain that is documented and compatible with French compliance requirements.

What StelarWork brings to a firm

StelarWork answers a specific difficulty: making a non-EU tech freelancer contractable when they aren't within your usual circuits.

Concretely, the model aims to bring:

• an identifiable French supplier;
• French invoicing;
• a structured contractual chain;
• a service framed by deliverables;
• compliance documentation;
• a clear separation between the firm and the freelancer;
• better traceability of flows;
• consistency between contract, order, invoice and execution;
• reduced procurement, legal and accounting friction.

StelarWork does not turn an abusive situation into a compliant one. If the freelancer's residence is fictitious, if the mission is carried out in France under cover of a foreign status, or if the relationship actually corresponds to salaried employment, the topic must be ruled out or restructured.

The key point: outcome-based service, not labour supply

To limit the risks, the mission must be built as a service.

That means the contract must concern an expected outcome, not a mere presence.

The useful elements are notably:

• a mission scope;
• identified deliverables;
• milestones;
• validation terms;
• governance;
• responsibilities;
• acceptance conditions;
• confidentiality rules;
• security obligations;
• intellectual property clauses.

This approach protects the readability of the relationship.

It also lets the firm demonstrate that the supplier is involved to produce a service, not to supply a person placed under the client's daily authority.

Reverse charge, invoicing and accounting compliance

International missions often raise questions of VAT, reverse charge and accounting treatment.

With a non-EU freelancer directly, the firm must analyse the applicable regime, check the invoice, handle the mandatory statements and document the flow.

With a French supplier, the circuit is more readable for internal teams. The firm receives an invoice issued by a French company, according to the standards its processes expect.

This doesn't remove the control obligations. But it reduces the friction linked to an individual foreign supplier.

On tax matters, you must stay strict: the freelancer's residence must match reality. The remote work must be genuine. The presence in France must not be organised on a stable basis. A foreign structure with no substance isn't a sound basis.

Permanent establishment: why the contractual wording matters

Another sensitive topic concerns permanent establishment.

The risk can appear when a person or an entity acts in France as a dependent representative of a foreign provider, notably by concluding contracts for them or organising a stable activity in France.

That's why the contractual chain must be carefully worded.

StelarWork contracts in its own name. It doesn't sign in the freelancer's name. It doesn't present itself as their representative in France. It sells a service to the firm and contracts separately with the non-EU provider.

This separation helps clarify roles and reduce ambiguities.

Common mistakes to avoid

Contracting directly without sufficient documentation

A mere email exchange, a foreign invoice and a day rate aren't enough to secure a relationship.

Subcontracting must be documented.

Confusing a remote freelancer with an internal resource

An independent provider must not be treated as a remote employee.

They can take part in project rituals if that's necessary for the service. But their autonomy, their scope and their deliverables must remain identifiable.

Accepting an undemonstrated tax residence

Tax residence is not declared. It is established.

The consistency between the place of living, the place of activity and the documents provided must be examined.

Using a foreign entity with no substance

A company created solely to invoice, with no real activity or substance, creates a significant risk.

This type of configuration must be avoided.

Neglecting the end-client contract

The firm must check that the envisaged subcontracting is compatible with its own commitments towards the end client.

Some clauses require prior authorisation, transparency on subcontractors or location constraints.

A simple decision grid

Before engaging a non-EU freelancer, a firm can ask five questions.

1. Is the freelancer genuinely established outside the EU?

Residence must be consistent with the facts. Work must be carried out remotely from the declared country, save for a controlled occasional exception.

2. Is the mission an identifiable service?

The contract must provide for more than availability. It must describe an objective, deliverables and responsibilities.

3. Is the contractual chain consistent?

The client contract, the firm's purchase order, the supplier contract and the invoice must be aligned.

4. Are the supplier documents acceptable?

The firm must be able to archive the elements needed for its internal controls.

5. Does the model withstand an audit?

The question isn't only: "does the mission work?" The real question is: "can the relationship be explained cleanly in six months?"

When StelarWork is relevant

StelarWork is relevant when the firm has identified a competent non-EU tech freelancer, but direct contracting creates too much friction.

This is typically the case when:

• the freelancer is based in Dubai, Bali or another non-EU country;
• the firm wants to avoid an insufficiently documented direct relationship;
• procurement refuses an individual foreign supplier;
• the end client requires a French or better-framed subcontracting chain;
• the mission can be framed as a service with deliverables;
• the freelancer genuinely works remotely;
• the residence and operational organisation are consistent.

StelarWork isn't meant to validate artificial arrangements. The model is designed to structure sound situations that fail for administrative, contractual or compliance reasons.

When to give up or review the arrangement

Some situations must raise a flag.

If the freelancer actually works from France, the topic must be analysed differently. If the end client requires a regular on-site presence, the non-EU remote model becomes questionable. If the mission consists solely of filling an internal position with no deliverables, the risk rises. If the tax residence is uncertain, it must be clarified before contracting. If the foreign entity has no substance, it must not serve as an artificial vehicle.

In these cases, the point isn't to find a cleverer wording. The point is to bring the operational reality back in line with the contractual framework.

Undeclared work: the right approach for a firm

The right reflex isn't to systematically rule out non-EU freelancers.

The right reflex is to distinguish sound situations from fragile ones.

A freelancer genuinely established outside the EU, working remotely, within a documented service, can fit into a compliant subcontracting chain.

But the firm must avoid grey areas: an undocumented direct relationship, oversight like an employee, absence of deliverables, fictitious residence, opaque invoicing, inconsistency between the contract and reality.

StelarWork positions itself on this exact point: letting the firm contract with a French supplier, in a more readable chain, while framing the relationship with the non-EU freelancer.

Legal and tax disclaimer

This article is general information for IT services firms. It does not constitute personalised legal, tax or social advice.

International subcontracting situations must be analysed on the facts: the freelancer's country of genuine residence, place of execution, contractual clauses, the parties' roles, oversight terms, end-client obligations and available documentation.

For a specific situation, you should seek the appropriate professional advice.

FAQ

Does undeclared work concern a firm working with a non-EU freelancer?

Yes, the topic can concern the firm if the relationship is poorly structured. The risk doesn't come from the freelancer being non-EU, but from any gap between the contractual form and reality: absence of autonomy, a mission with no deliverables, fictitious residence, opaque invoicing or integration as an employee.

Can a freelancer in Dubai or Bali work for a French firm?

Yes, if the situation is genuine and documented. The freelancer must effectively be a non-EU resident, genuinely work remotely, have no organised presence in France and work within a structured service.

Is the non-EU freelancer's tax status a StelarWork product?

No. StelarWork does not sell tax avoidance. If a freelancer is already a genuine non-EU tax resident, that's a pre-existing situation. StelarWork steps in to reduce an administrative and contractual friction, not to create an artificial tax advantage.

What distinguishes a compliant service from a risky relationship?

A compliant service rests on a scope, deliverables, professional autonomy, consistent invoicing and a documented contractual chain. A risky relationship looks like disguised salaried employment or invoicing with no real substance.

Does StelarWork sign in the freelancer's name?

No. StelarWork contracts in its own name with the firm. It doesn't conclude any contract in the freelancer's name and doesn't present itself as their representative in France. The relationship with the freelancer is contracted separately.

Does StelarWork remove the risk of undeclared work?

No serious arrangement can promise the total absence of risk. StelarWork is designed to reduce grey areas by structuring the relationship as a service, with a more readable contractual chain and suitable compliance documentation.

Is a day-rate mission incompatible with an outcome-based service?

No. The day rate can be an economic calculation method. The important point is that the mission isn't reduced to a mere presence. It must remain attached to a scope, deliverables and identifiable objectives.

What must a firm check before working with a non-EU freelancer?

The firm must check the reality of the residence, the place of execution, the provider's autonomy, the consistency of the documents, compatibility with the end-client contract, the invoicing and the contractual structure of the subcontracting.