Portage Salarial for SAP Consultants — Insurance Against Reclassification, Not a Payroll Trick

A French SAP analytics consultant going independent picks a legal vehicle before picking a client, and the choice is usually made on the wrong criterion — take-home percentage — when the criterion that actually matters is classification risk. Portage salarial exists mainly to solve the second problem, and it is worth understanding as insurance rather than as a payroll trick.

What portage salarial actually is

A three-party arrangement. You find the client and negotiate the rate; a portage company employs you on a salaried contract; the client contracts with the portage company, which invoices, collects, deducts its commission and social charges, and pays you a salary. You keep commercial autonomy — the client, the scope, the rate are yours — and you gain employee status: payslips, unemployment-insurance rights, a pension record, and the legal position of an employee rather than a contractor.

The trade is straightforward and should be stated plainly: you take home less than you would through your own company, and in exchange somebody else carries the employer obligations, the invoicing and the classification exposure.

Why classification is the real reason to consider it

Worker misclassification is the single largest legal exposure a solo freelancer carries in France, and the consequence is not a commercial dispute — it is URSSAF reopening history. Under Article L.8221-6 and URSSAF case law, the lien de subordination test asks whether you take orders on how and when to work, keep fixed hours mirroring employees, use only client-provided equipment, serve one client for an extended period, and sit inside the client's hierarchy. If the answer is yes, URSSAF can recharacterise the relationship and recover up to five years of unpaid employer social charges — roughly forty-five percent of gross billings — plus penalties, with travail dissimulé available as a criminal charge in aggravated cases.

Long SAP engagements are exactly the shape that triggers this. A Datasphere or BW/4HANA migration is measured in quarters, the consultant sits with the client's team, uses the client's VPN and laptop because security policy demands it, and appears in the project org chart. Every one of those is a red flag, and none of them is avoidable on that kind of engagement.

Portage salarial removes the question. If you are an employee of the portage company, there is no independent status for URSSAF to recharacterise.

The three vehicles, and when each fits

Portage salarial — long single-client engagements, first year of independence, anyone whose engagements structurally look like employment. Lower take-home, employee protections, classification risk transferred.

EURL / SASU — your own company. Highest take-home, full control of your remuneration structure, and you carry the classification exposure yourself. It fits a consultant with several clients, real commercial infrastructure and a mission profile that does not read as disguised employment.

Micro-entreprise — simplest to start and revenue-capped. Almost always the wrong vehicle for SAP analytics day rates, which reach the ceiling quickly.

What to check before signing, in writing

The commission rate and exactly what it covers. The corpus of consultants' experience here varies widely between companies and this page will not quote a percentage — get it in writing, with the full arithmetic from gross client invoice to net salary, before comparing offers.

Then: professional liability insurance and its limits; how expenses are handled; the payment delay between client settlement and your salary; and whether the company holds the garantie financière the regime requires. A portage company that cannot answer those in writing is answering them.

Pitfalls

Choosing on headline take-home. It compares the one number that is easy and ignores the exposure that is expensive.

Assuming portage removes the need for a real contract. The client contract still defines scope, IP and liability; portage changes who signs it, not what it says.

Staying in portage by inertia. Once several clients and real infrastructure exist, the classification argument weakens and the cost of portage stops buying much.

Treating the UK as the same problem. IR35 shifted status determination to the end client after the 2021 private-sector reform, and an "inside IR35" determination cuts effective take-home by roughly a quarter to a third of the headline day rate. It is a different regime with a different owner — do not carry French reasoning across the Channel.

Why it matters

• URSSAF can recover up to five years of employer charges — roughly 45 % of gross billings — plus penalties. That is the exposure the take-home comparison quietly leaves out.

Key points

• Portage salarial is a three-party arrangement: you win the client and set the rate, a portage company employs you, the client contracts with the portage company.
• You keep commercial autonomy and gain employee status — payslips, unemployment rights, pension record, and an employee's legal position.
• The trade, stated plainly: lower take-home in exchange for someone else carrying employer obligations, invoicing and classification exposure.
• 🔴 The real reason to consider it is reclassification, not payroll. URSSAF can recover up to FIVE YEARS of employer charges — ~45 % of gross billings — plus penalties.
• The French test is the lien de subordination (Art. L.8221-6): orders on how/when, fixed hours, client-only equipment, one client for long periods, place in the hierarchy.
• Long SAP engagements trip every one of those structurally — a migration runs for quarters, on the client's VPN, inside the project org chart.
• Employee of the portage company ⇒ no independent status remains for URSSAF to recharacterise.
• EURL/SASU gives the highest take-home and keeps the exposure with you — it fits several clients and real commercial infrastructure.
• Micro-entreprise is revenue-capped and almost always wrong at SAP analytics day rates.
• The UK is a DIFFERENT regime: since the 2021 reform the end client issues the Status Determination; "inside IR35" cuts effective take-home by roughly a quarter to a third.

Common pitfalls

• Choosing on headline take-home — Signal: The comparison is a single net percentage. Fix: Price the reclassification exposure into the comparison — five years of employer charges is the number being ignored.
• Portage assumed to replace the contract — Signal: Nobody has read the scope, IP and liability clauses. Fix: Portage changes who signs the client contract, not what it says.
• Staying in portage by inertia — Signal: Three clients, own laptop, still paying portage commission. Fix: Re-run the decision — the classification argument, and therefore the value, has weakened.
• French reasoning applied to a UK engagement — Signal: IR35 treated as the client's problem or as the same test. Fix: Since 2021 the end client issues the Status Determination Statement; inside IR35 costs roughly a quarter to a third of the headline rate.
• Commission quoted without the full arithmetic — Signal: A percentage with no gross-invoice-to-net-salary worked example. Fix: Ask for it in writing. A company that will not put it in writing has told you something.

Decision framework

Sources

1. service-public.fr — statuts d'indépendant et portage salarial
2. URSSAF — employer contributions and recharacterisation
3. HMRC — off-payroll working rules (IR35)
4. SAP Help — SAP Datasphere documentation (engagement context)
5. SAP Help — SAP BW/4HANA documentation (engagement context)
6. DSAG — German-speaking SAP user group
7. BARC — independent analyst research