the art of being legal

Bogus Self-Employment in Tech Teams: Signs, Real Costs and How to Protect Your Freelance Hiring

Puesto de desarrollador en una oficina tecnológica con dos pantallas de código y un contrato de servicios

In a product team, the line between a contractor and an employee can be crossed without anyone signing anything new. The developer came on board as a freelancer for a sprint, has been invoicing the same amount every month for fourteen months, joins the daily standup, has access to the repository, and requests holiday via Slack. As far as the company is concerned, they are still an invoice. As far as the Labour Inspectorate is concerned, they very probably are not. And the difference is not determined by the contract the parties signed, it is determined by how the work is actually performed in practice.

This article explains exactly what the Inspectorate looks at when examining a technical team, how an economically dependent self-employed worker differs from a bogus self-employed worker, and what a reclassification costs when it arrives. If what you need to resolve involves international hiring, the analysis is different, we cover that in the guide on hiring remote talent.

When is a freelancer, in legal terms, an employee?

Article 1.1 of the Workers' Statute defines an employment relationship by four criteria that must all be present simultaneously: the work is performed voluntarily, it is remunerated, it is performed on behalf of another party, and it takes place within the organisational and managerial sphere of another person. The last two are the ones that determine the outcome in almost every case: alienation of output and subordination.

There is also a rule that shifts the starting point of any dispute. Article 8.1 of the same statute establishes that an employment contract is presumed to exist between a person who provides a service within another party's organisational and managerial sphere and the party who receives that service in exchange for remuneration. It is not for the authorities to prove that an employment relationship exists: it is for the company to demonstrate that it does not. A well-drafted commercial contract does not neutralise that presumption, it merely documents it.

This leads to the conclusion that tends to cause most discomfort in a management meeting: the classification does not depend on what the parties signed. It depends on how work is organised day to day.

The indicators that carry weight in a technical team

The classic indicators of an employment relationship were originally formulated with factories and offices in mind. Applied to a remote engineering team, they translate as follows.

1. Integration into the organisation

The individual appears in the org chart, in internal communication channels, and on distribution lists. They take part in the daily stand-up, sprint planning, and retrospectives. Their work is assigned through tickets on the same board as the rest of the team. They are not delivering an agreed output, they are contributing their time within someone else's process.

2. Subordination in the direction of work

Someone at the company decides what gets done, in what order, and with what priority. There is code review with rejection authority, reporting to a manager, and performance evaluation. In practice, the ability to decline a task is non-existent.

3. Use of the company's means of production

Corporate laptop, software licences, access to environments, an email account on the company's domain. A genuinely self-employed worker supplies their own infrastructure and bears its cost. When the client provides all the means of production, the indicator of economic dependency is significantly reinforced.

4. Fixed, recurring remuneration

The invoice is for the same amount every month, calculated on hours worked or availability, not on a deliverable. The individual bears no financial risk: they are paid the same whether the project succeeds or is cancelled. The absence of any financial risk and reward is one of the most significant factors.

5. De facto exclusivity

An exclusivity clause is not required for exclusivity to exist in practice. A forty-hour working week creates it on its own: there is simply no time left for other clients. Having a single client for years is itself a telling indicator.

6. Adherence to a set schedule and calendar

Agreed availability hours, on-call rotas, attendance monitoring, and above all, having to ask permission to be absent. The moment a freelancer requests holiday rather than simply notifying the client of their unavailability, the relationship is already behaving like an employment one.

No single indicator is conclusive on its own. What matters is the overall picture. In tech teams, the accumulation of these indicators is common, because agile working methods tend, by design, to draw everyone into the same workflow.

An economically dependent self-employed worker (TRADE) is not a bogus freelancer

This is the most common source of confusion, and it is worth clearing up, because this legal category exists and is perfectly lawful. Article 11 of the Self-Employed Workers' Statute defines the economically dependent self-employed employee (known in Spain as a TRADE) as a person who carries out their activity on a regular, personal, direct and predominantly exclusive basis for a single client, from whom they receive at least 75% of their total income.

This status requires several conditions to be met simultaneously, including not having any employees and not subcontracting the work, except in the specific cases expressly provided for by law. Economic dependence on a single client does not, therefore, make someone a bogus freelancer. What makes someone a bogus freelancer is organisational dependence: working within another party's sphere of direction and control. These are two distinct forms of dependence, yet they are routinely confused.

That said, TRADE status requires a registered contract and is governed by its own specific legal framework. Claiming TRADE status retrospectively, once an inspection has already been opened, does not remedy the situation.

The cost of reclassification, person by person

The real cost rarely matches what the company expects, for three reasons that compound one another.

Unpaid contributions, going back in time. If the relationship is reclassified, the company should have registered the individual and paid Social Security contributions on their behalf. Article 24 of the General Social Security Act sets a four-year limitation period for assessing and recovering those contribution debts, and for imposing penalties. Four years of contributions for a senior technical profile is not a negligible sum.

The fine, which multiplies for each individual. Article 22.2 of the Law on Infringements and Sanctions in the Social Order classifies failure to register workers entering the company's service as a serious infringement, and specifies that each affected worker constitutes a separate infringement. Under Article 40.1.b), serious infringements carry fines ranging from €751 to €1,500 at the minimum level, €1,501 to €3,750 at the intermediate level, and €3,751 to €7,500 at the maximum level. A team with six freelancers in the same situation does not receive one fine, it receives six.

And what follows. Reclassification converts the relationship into an open-ended employment relationship. From that point on, ending it is no longer a matter of terminating a services contract, it becomes a dismissal, with its associated compensation and risk of a finding of unfairness. That consequence typically weighs more heavily than the fine itself, and we cover it in detail on our dismissals page.

Checklist before signing with a tech freelancer

  • The engagement is defined by deliverables and acceptance criteria, not by hours of availability.
  • The professional organises their own time. There are milestones and progress meetings, not fixed schedules or attendance monitoring.
  • They use their own tools and resources, or where the company's resources are used for security reasons, the contract explains why and access is limited to what is strictly necessary.
  • Invoiced amounts vary with the work actually carried out, and there is an identifiable sharing of risk.
  • They work for other clients, and the agreed workload leaves a realistic margin to do so.
  • They do not take part in team management rituals as though they were staff: no performance reviews, no career development plans, no approval required for absences.
  • Where economic dependence exceeds 75 per cent, a TRADE contract (economically dependent self-employed worker) with the corresponding registration is considered, rather than leaving the situation unclassified.
  • The arrangement is reviewed every six months. Bogus self-employment rarely starts that way, it tends to develop over time.

Frequently asked questions about bogus self-employment in tech teams

Does it make any difference if the contract expressly states that the relationship is commercial in nature?

It serves as evidence of the parties' intention, and nothing more. Against the presumption set out in Article 8.1 of the Workers' Statute, what is examined is how the service is actually delivered. A contract that precisely describes an assignment based on deliverables is helpful; a contract that labels as commercial something that functions as employment is not.

The freelancer invoices through their own company. Does that change anything?

It changes the appearance, not the substance. If the service is personal and is provided within the company's organisational and managerial framework, interposing a company does not neutralise the analysis. It does, however, add a tax discussion concerning the company itself.

Who can initiate proceedings?

The Labour Inspectorate, acting on its own initiative or as part of a targeted campaign, and also the individual themselves, who may seek formal recognition of the employment relationship. In practice, many cases are opened when the working arrangement ends badly.

Can you regularise the situation before the Inspectorate arrives?

Yes, and it is almost always the cheaper option. Regularising on your own initiative allows you to put the registration in order, negotiate terms with the person concerned, and prevent a file from being opened with a separate infringement for each employee. Doing so requires you to assess in advance the length of service to be recognised and the knock-on effect on the rest of the team.

Does it make a difference if the freelancer works from another country?

Yes. The law applicable to the contract, the competent Social Security system, and the risk of permanent establishment all come into play. This calls for a separate analysis, which we cover in our guide to hiring remote talent.

Do you have freelancers embedded in your team? Review the arrangement before someone else does

A review of your collaboration agreements and actual working practices will tell you which profiles are at risk, how much it would cost to regularise them, and in what order it makes sense to do so. It is a focused piece of work, and it is far more straightforward to carry out before any formal proceedings are under way. At employment law advisory, we support companies through that analysis and through the regularisation process where appropriate. Tell us about your situation.

CONTACTAR

Date published: 20 November 2026

Last updated: 21 November 2026

Article written by

Josep Conesa Sagrera

Employment and insolvency lawyer

Josep Conesa is a Spanish and English-speaking labour lawyer who holds a master’s degree in European law and Fundamental Rights. Over 25 years of experience. We’d be delighted to legally help you too, in your language whenever possible.

View professional profile

Published on Updated on