Are Your Platform Workers Actually Employees? Portugal's Article 12-A and the 2025 Supreme Court Wave

Picture a food-courier or a ride-hailing driver in Lisbon. They signed up through an app, they are labeled a self-employed provider, they invoice for their work, and everyone involved has treated them as a contractor for years. Now ask the question that Portuguese courts spent 2025 answering: is that person actually an employee? Since 2023, Portuguese law does not start from "no." It starts from "presumed yes," and it puts the burden on the platform to prove otherwise. For anyone running payroll or finance for a business that relies on app-organized labor, that shift in the starting assumption is what matters, because an employee comes with social-security contributions, the full Labour Code, and potentially years of unpaid back contributions and taxes.

Let me walk through what the law actually says, what the Supreme Court did with it across 2025, and what reclassification means once the numbers land on a payroll.

Article 12-A flipped the default

Lei 13/2023, the Agenda do Trabalho Digno, added Article 12-A to the Labour Code, effective May 2023. It creates a rebuttable presumption that an employment contract exists between a person and a digital platform when some of six characteristics are present in the relationship:

The platform sets the pay, or sets maximum and minimum limits for it. The platform directs the work, setting rules on how the provider presents themselves or behaves toward the customer. The platform controls or supervises the work, including in real time or through algorithmic management. The platform restricts the provider's autonomy over how they organize their work, such as choosing hours, accepting or refusing tasks, or using substitutes, backed by sanctions. The platform exercises employer-like powers, including discipline such as deactivating an account. The equipment and tools used belong to the platform.

Three details make this powerful. First, only "some" of the six need to be present, not all, so the bar to trigger the presumption is low. Second, it applies regardless of what the parties called the relationship, so labeling someone a contractor in the terms of service does not help. Third, it expressly covers ride-hailing (TVDE) platforms, not just delivery. The platform can rebut the presumption, but only by proving the provider genuinely works with real autonomy, free of the platform's control, direction, and discipline. And getting this wrong is not a quiet civil matter: disguised platform employment is classified as a very serious administrative offence, with repeat offenders facing loss of public subsidies and European funds and bans from public tenders for up to two years.

How the 2025 Supreme Court rulings applied the presumption

A law that sits on the books is one thing. What changed the risk profile is that over the course of 2025, Portugal's Supreme Court (STJ) issued a run of decisions applying Article 12-A to the biggest names in the sector, and it applied it in the platforms' disfavor.

In the Glovo case, the STJ held that where some of the Article 12-A characteristics are verified, specifically that the main work instrument belongs to the platform and the platform sets the maximum and minimum pay, an employment contract is presumed, and to escape it the platform must prove the courier genuinely works with effective autonomy. The Court reversed the appeal court's dismissal and sided with the public prosecutor's action to recognize the employment relationship. A later STJ ruling on Uber settled a point platforms had been leaning on: the presumption reaches relationships that began before May 2023, as long as the relevant characteristics continued after the provision came into effect. So "our drivers started before the law" is not an escape hatch. Individually each decision is persuasive rather than universally binding, but as a cluster they tell you exactly how the top court reads the statute, and the direction is one way.

What reclassification actually costs

Here is where it stops being a legal debate and becomes a payroll problem. When a platform worker is found to be an employee, the compatible parts of the full Labour Code apply: minimum monthly pay (€920 on the mainland for 2026), paid holidays, the holiday and Christmas payments that make up Portugal's 14-payment year, working-time limits, protection against dismissal without just cause, and work-accident coverage.

The largest cost, though, is contributions and tax. An employee's remuneration is subject to Social Security contributions, roughly 23.75 percent on the employer and 11 percent withheld from the worker, plus IRS income-tax withholding at source. On a reclassification, that liability does not begin on the date of the judgment; it can reach back over the period the relationship existed with those characteristics, which is why the temporal-reach holding matters so much. A platform that ran thousands of "autonomous" couriers is not looking at one corrected payslip, it is looking at back contributions and back tax across a workforce, plus the offence exposure on top.

One more group should be paying attention: this is not only a problem for the household-name apps. The law reaches any business whose model organizes individual work through an app under its own brand, and it explicitly extends the presumption through intermediaries, so routing workers through a labor intermediary does not move the risk off the books. The court decides who the employer is.

What this means if you run payroll in Portugal

In Portugal, the classification question that platforms once got to define is now tilted against them by default and enforced by the Supreme Court. If an employer sets pay, manages workers through an algorithm, disciplines them through the app, or supplies their tools, those workers are presumed to be employees, and continuing to treat them as contractors is misclassification. The consequence is a workforce that carries social-security contributions, income-tax withholding, and 14-payment obligations, potentially backdated.

That second half, the running of it, is the part Flux is built for. Once a worker is an employee, we handle them as one: the Social Security contribution base, the employer and worker rates, IRS withholding, the holiday and Christmas payments, and the minimum-wage floor, all applied correctly from the classification date the situation requires. We cannot make the classification call for a business; whether a given worker is an employee is a legal question about how that specific arrangement operates, decided by the facts and, ultimately, the courts. But once that call is made and the answer is "employee," Flux handles the payroll and contributions that follow, correctly and from the required date.