B2B with One Client in Poland: Is It Legal? Tax Risks Explained

The majority of Polish IT contractors work primarily or exclusively with one client. This is the reality of the market — most B2B arrangements involve a contractor embedded in one company's development team, billing a single entity every month.

Is this legal? Yes. Is there risk? Yes. How much, and how do you manage it? This guide answers those questions.

Is Single-Client B2B Legal in Poland?

Yes — there is no law prohibiting a JDG contractor from working exclusively with one client. Polish law does not require freelancers to have multiple clients.

However, having a single client is one of many factors that can lead to your B2B arrangement being reclassified as employment by ZUS or a labour court. It is a risk factor, not an automatic violation.

The critical question is not how many clients you have — it is whether your working relationship looks like employment.

Understanding "Hidden Employment" (Ukryte Zatrudnienie / Pozorowane Samozatrudnienie)

Polish labour law recognizes a concept called pozorowanie stosunku pracy (simulating an employment relationship) or ukryte zatrudnienie (hidden employment). When a B2B relationship is found to be employment in substance, it can be reclassified regardless of what the contract says.

The Polish Labour Code (Art. 22 §1) states: if work is performed:

• For the benefit of one entity (employer)
• Under that entity's supervision and management
• At a place and time determined by the employer
• For remuneration

...then an employment relationship exists, and cannot be replaced by a civil law contract.

What triggers reclassification risk?

Courts and ZUS inspectors look at the totality of circumstances. Red flags include:

The more of these factors are present, the higher the risk of reclassification.

ZUS Rules on Single-Client B2B

ZUS has enforcement authority to inspect B2B arrangements and reclassify them as employment. Consequences of reclassification:

1. Back-payment of all employer ZUS contributions — the client (your former "partner") owes the employer share of contributions for the entire period
2. Employee share recalculated — the reclassified salary is recalculated to determine what the employee contributions should have been
3. Interest on all unpaid contributions — accrues from when each contribution should have been paid
4. Penalties — ZUS can impose additional fines
5. Income tax adjustments — if contributions were deducted and the reclassification changes them

The financial exposure can be very large — potentially hundreds of thousands of PLN for a multi-year arrangement.

In practice, ZUS inspections of individual contractors are not common — ZUS focuses enforcement on the employer side, not the contractor side. However, the risk is real and the consequences severe.

The "Former Employer" Rule — More Concrete Risk

There is a specific and clear legal restriction:

If you were employed by a company and then switch to B2B with that same company, providing the same type of services — you cannot use ryczałt tax for income from that company in the current and following tax year.

This is not a reclassification risk — it is a specific rule in the Polish lump-sum tax act. The consequence is purely tax-related: you must use flat tax 19% for that client's income, not ryczałt 12%.

This rule applies:

• When you had an employment contract with the client in the current or prior tax year
• And you now provide the same type of services under B2B as you did under employment

Practical example: You worked as a Java developer at Company X in 2025 (employment). In 2026, you register a JDG and invoice Company X for Java development services. For Company X's invoices in 2026, you cannot use ryczałt — you must use flat tax 19%.

In 2027, the restriction lifts (assuming no further employment at Company X in 2026).

What Percentage of Income from One Client Is "Risky"?

There is no legal threshold — Polish law does not say "60% from one client is fine, 80% is risky." Courts assess the totality of circumstances.

That said, having 100% of income from one source is a signal that courts and ZUS inspectors note. Combined with employment-like working conditions, it increases reclassification probability.

In practice:

• Single-client B2B is extremely common in Polish IT — the risk is real but not universally enforced
• Risk is much higher when the arrangement clearly mimics employment (fixed hours, supervision, client equipment)
• Risk is much lower when the contractor genuinely operates as an independent business

How to Protect Yourself

1. Structure your contract correctly

Your service agreement should:

• Define deliverables, not time spent
• Explicitly state you can work for other clients
• Specify that you determine how and where work is performed
• Avoid language about "working hours," "schedule," or "workplace"
• Include liability clauses (you bear liability for your deliverables)

2. Operate like a business

• Maintain your own work equipment (or at least have your own alongside the client's)
• Work from your own premises at least part of the time
• Set your own working hours (flexible schedule, no mandatory 9-5)
• Make business decisions independently — choose your approach to delivering the work

3. Invoice for results, not time

While hourly billing is common and not illegal, framing invoices around deliverables reduces the employment indicator. At minimum, use neutral language: "IT services for project in month" rather than "160 hours of work."

4. Consider acquiring at least one other client

Even a small secondary client (another day of work per month) significantly changes the risk profile and signals genuine independence. It also provides income diversification.

5. Keep documentation of independence

• Correspondence showing you proposed solutions rather than just executing instructions
• Evidence of working outside the client's office
• Records of turning down some client requests or negotiating terms

6. Get professional advice if your situation is complex

If you're considering B2B with your current employer, or if your arrangement is genuinely indistinguishable from employment, consult a Polish labor law attorney or a tax advisor experienced in JDG issues.

The Real Risk Profile: Who Gets Caught?

Mass reclassification campaigns are rare in Poland. The most common scenarios where reclassification actually occurs:

1. Labour court cases initiated by the contractor — ironically, contractors who feel mistreated sometimes sue to have their arrangement reclassified as employment to access employment protections (paid leave, sick pay, reinstatement rights)
2. ZUS audit of the client's payroll — during audit, inspector notices suspicious B2B arrangements
3. Competitor complaints — less common
4. High-profile enforcement campaigns — occasionally ZUS runs targeted inspections in certain industries

For the typical IT contractor with a clear service agreement, working on software deliverables, with some degree of schedule flexibility — the practical risk is low, though not zero.

Should You Get a Second Client?

Having a second client is genuinely valuable for three reasons:

1. Reduces reclassification risk (marginal improvement)
2. Provides income diversification — if Client 1 terminates, you have Client 2 revenue
3. Strengthens your negotiating position with Client 1

Even a small project (1–2 days per month for another client) is meaningful. Options:

• Weekend or evening freelance projects
• Open source contributions that lead to paid consulting
• Local startup projects at reduced rate
• Subcontracting via a contractor agency

Summary

For the complete B2B setup guide, see freelancing as a developer in Poland. To check if B2B makes financial sense for you, use our B2B vs Employment Calculator.

This article is for informational purposes only and does not constitute legal advice. Consult a Polish labor law attorney for advice specific to your situation.