Employer of Record (EOR) Poland: A 2026 Guide for Foreign Employers (After the B2B Reform)

If your company sits in Berlin, London, Stockholm, Amsterdam, or San Francisco and you want to hire a Polish developer this year, you have a hiring decision in front of you that wasn't on the table 18 months ago. The path most foreign employers default to — a B2B contract with a Polish self-employed developer — is about to get materially riskier. Starting 8 July 2026, the Polish Labour Inspectorate (PIP) gains administrative power to reclassify B2B contracts as employment relationships by inspector decision. An Employer of Record (EOR) is the structurally safer alternative, and it is the route most foreign companies should take a fresh look at right now.

This guide is for foreign founders, CTOs, and heads of talent in companies that don't have a Polish entity but want to hire a Polish IT specialist remotely. I walk through what an EOR is, why it matters more after July 2026, how the mechanics work in Poland specifically, what it costs, how it compares to B2B and to opening your own Polish entity, how to pick a vendor, and the gotchas that bite.

Table of contents8 sections

1. 01What is an EOR in Poland?
2. 02Why EOR matters more in 2026
3. 03How EOR works step by step
4. 04How much does EOR cost?
5. 05EOR vs B2B vs own entity
6. 06How to pick an EOR vendor
7. 07Gotchas to watch for
8. 08Where to go from here

What is an Employer of Record (EOR) in Poland?

The EOR signs the Polish employment contract with the developer. The EOR runs monthly payroll. The EOR files ZUS (Polish social security) contributions and withholds PIT (Polish income tax). The EOR administers statutory benefits — paid leave, sick pay, occupational health and safety. The EOR manages the formal terminations, the contract amendments, and any interaction with Polish labor authorities.

You manage the developer's work. You pick what they build, how they build it, when they pair, how you run reviews. The EOR has no view into the technical work and no say in performance management beyond the formal HR mechanics.

The financial relationship is simple: you pay the EOR a single monthly invoice. That invoice rolls up the developer's gross salary, the employer-side social contributions, statutory benefits, and the EOR's platform fee into one number. You don't run Polish payroll. You don't file with ZUS. You don't deal with the Polish tax office directly.

This is fundamentally different from a B2B contract, where the developer is a self-employed sole proprietor (a JDG, in Polish), invoices you monthly, and handles their own ZUS and PIT. EOR is employment. B2B is a service contract between two businesses.

Why does Employer of Record matter more in 2026?

For most of the past decade, the dominant model for senior Polish IT contractors was B2B. The math favored the developer (lower social contributions on the JDG side, flat-rate or lump-sum tax options), the contract was fast to set up, and foreign companies liked the simplicity of paying a monthly invoice without payroll machinery. The catch — present long before this reform — was always reclassification: if the relationship looked like employment in practice, courts could rule that it was, and order backdated contributions.

What the April 2026 reform changes is who decides and how fast. Until now, reclassification ran through Polish courts: slow, contested, expensive on both sides. After 8 July 2026, the regional labour inspector at PIP can establish an employment relationship by administrative decision. The bar for what counts as employment-in-practice is the same factual test — fixed hours, direct supervision, employer-provided equipment, single client, embedded in the org structure — but the path to enforcement gets shorter and the inspector has the standing to act on their own assessment.

The financial exposure if you're caught on the wrong side of the test is significant. Sources from Polish legal firms (Dudkowiak & Putyra, Wozniak Legal, Accace) describe the exposure as: backdated ZUS contributions for up to three years, employer-side PIT advances retroactively due, tax-regime shift from flat-rate to progressive PIT for the worker, fines up to PLN 90,000 per violation, and administrative fines up to EUR 15,000 per contract. VAT on prior B2B invoices may also need correction on both sides.

For a foreign company hiring one or two Polish developers on dedicated, full-time, EU-hours work, the reform pushes the risk-adjusted cost calculation toward EOR. The B2B model still works for genuinely independent contractors — multiple clients, project-based engagements, the developer setting their own hours and using their own equipment — but it requires deliberate structuring and ideally a legal review of the contract.

EOR sidesteps this entire question. The EOR is the formal employer, the developer is on a Polish employment contract, and there is nothing to reclassify.

How does an EOR work in Poland step by step?

The flow looks like this:

1. Offer and contract preparation. You sign a service agreement with the EOR. The EOR sends the developer a Polish employment contract using their standard template (Polish-language original, English translation usually provided alongside). You agree the terms — gross salary, role, working time, start date, any contractual benefits beyond the statutory minimum.
2. Pre-employment medical assessment. Polish law requires the developer to pass an occupational health check before signing. The EOR books this with a partner clinic. Allow 2-3 days from booking to the medical certificate. This step surprises a lot of foreign founders because there's no Western European equivalent.
3. Contract signing and ZUS registration. Once the medical certificate is in hand, the developer signs the Polish employment contract. The EOR registers the employment with ZUS (Polish social security) and the relevant tax office. This is administrative, runs in parallel with the rest.
4. Day-one onboarding. On the first working day, the developer completes mandatory occupational health and safety (OHS) training — short, EOR-administered, often online. Bank account and tax form details are confirmed.
5. Payroll cycle starts. The EOR runs monthly payroll, files ZUS contributions and PIT withholdings, and sends you the consolidated monthly invoice. The developer gets a Polish payslip.

After day one, the EOR is the formal counterparty for everything employment-related. You direct the developer's work the same way you would direct any team member; the EOR handles paid leave requests, sick leave, HR administration, and any required statutory notices. If the contract ends, the EOR manages the termination process under Polish law, including notice periods (2 weeks under 6 months tenure, 1 month at 6 months plus, 3 months after 3 years) and any final settlements.

How much does Employer of Record in Poland cost in 2026?

The components, from largest to smallest:

Gross salary. Whatever you and the developer agreed. Polish IT salaries vary widely by stack and seniority. For a sanity check on senior backend, DevOps, or full-stack hires for a foreign company, public Polish IT job boards (Bulldogjob, NoFluffJobs, JustJoinIT) publish live salary widelets per role and seniority. Western European employers consistently pay 35-50% less for equivalent quality compared to local DACH or UK rates, while still landing in the upper Polish market range.

Employer-side ZUS (social security contributions). Roughly 19-21% of gross salary, paid by the employer on top of the gross. Made up of pension (~9.76%), disability (~6.50%), accident insurance (~1.67%, varies 0.67-3.33% by sector), the Labor Fund (~2.45%), and the Guaranteed Employee Benefits Fund (~0.10%). Rates have been stable; what changes year-over-year is the contribution base as gross salaries rise.

EOR platform fee. This is the EOR provider's monthly margin. Headline ranges as of May 2026:

Some providers add a country surcharge (USD 50-150 per month) for markets they classify as complex. Always ask whether Poland sits in standard or complex tier for the provider you're talking to.

Mandatory and contractual benefits. Statutory paid leave, sick pay, and any benefits the EOR includes by default (private medical, sport pass, life insurance — many Polish EOR templates include these). Some providers package benefits in the platform fee; others itemize them.

A working illustrative total monthly cost for a senior developer hired through an EOR in Poland looks something like this:

• Gross salary: EUR 6,000
• Employer ZUS at ~20%: EUR 1,200
• EOR platform fee: EUR 500
• Mandatory and standard benefits: EUR 100-300

Approximate total cost of employment: EUR 7,800 - 8,000 per month for that example. The exact mix depends on your provider, the developer's specific role, sector accident insurance rate, and benefits package. Always ask the EOR for an itemized breakdown before signing — the fee comparison only makes sense once you can compare like-for-like.

EOR vs B2B vs your own Polish entity: which fits a foreign company?

The decision matrix:

Decision shortcuts post-July 2026:

• You want a dedicated, full-time worker on your team, working EU hours, using your equipment, embedded in your org. That's employment in factual substance. Use EOR. B2B in this scenario carries the reclassification risk PIP is now empowered to enforce.
• The developer has multiple clients, runs their own JDG with autonomy over hours and tooling, and you're engaging them on a project or specific deliverables. That's a genuine contractor relationship. B2B still works, but get a Polish employment lawyer to review the contract before signing — the structure has to match the substance.
• You're hiring 5+ Polish developers and the relationship is long-term. Start evaluating your own Polish entity. EOR fees compound; entity setup pays off in headcount.

How do you pick an EOR vendor for Poland?

A working evaluation checklist when you're talking to vendors:

• Ask for an itemized monthly breakdown for a hypothetical hire at the salary band you're targeting. Gross, employer ZUS, platform fee, benefits, sector accident rate, any country surcharge, and any pass-through fees should all be lines in the breakdown. If a provider can only quote a rolled-up total, that's a transparency signal.
• Ask how they handle the medical check and OHS training. Both are mandatory in Poland and both are common foreign-employer surprises. A provider with their own clinic partnerships and online OHS course will save you 2-3 days at onboarding versus one that bounces it back to you.
• Ask about IP assignment language in their employment template. Polish employment law has specific rules around copyright assignment and works made in employment. The EOR template should explicitly assign IP rights to the foreign client and align with EU intellectual property frameworks. Get the contract template and have your counsel review it before you sign the master agreement.
• Ask about the exit path — what happens if you set up your own Polish entity, what the cost is, and how the worker's tenure transfers. EORs that treat the exit as a feature and not a friction point are the ones to lean toward.
• Ask for references from foreign employers in your stage hiring 1-3 Polish developers. Ask the references about onboarding speed, payroll accuracy, responsiveness when things go wrong, and surprise costs.
• Check for Polish labor-law depth, not just global breadth. Global EORs operating across 50+ countries are convenient, but for a Polish hire you want a vendor who can answer questions about ZUS edge cases, sector accident rates, sick-pay calculations, and OHS in plain language without escalating internally.

The right vendor for a 100-country scale-up may not be the right vendor for a five-person foreign startup making its first Polish hire. Match the vendor's center of gravity to your shape of need.

What gotchas should foreign employers watch for?

The mandatory medical check. Polish law requires an occupational health certificate before the employee starts work. There is no equivalent in most Western European employment, so it surprises foreign founders. The check is short and routine, but it adds 2-3 days to onboarding and you can't skip it.

OHS training on day one. Occupational health and safety training is mandatory and has to happen on the first day of work. Most EORs handle this with a short online module, but confirm with your provider that this is included and completed before the developer starts billable work.

IP assignment specifics in employment vs B2B. Polish copyright law has a specific regime for works created within employment relationships, and the assignment language in the contract has to match. Don't assume the EOR's default template aligns with your contracting and IP framework — review it with counsel, especially if the developer will produce significant patentable or proprietary work.

Sector accident insurance variation. Employer-side accident insurance is not a flat rate — it varies between roughly 0.67% and 3.33% of gross salary depending on sector classification and headcount. For IT it's typically near the lower end, but the EOR should confirm the specific rate they're charging you and explain why.

The EF English Proficiency Index puts Poland at #15 globally and #13 of 35 European countries in 2025, with a national score of 600 — comfortably in the "high proficiency" tier. Polish IT specialists rank at the top of that pool. Daily standups, code reviews, design discussions, and async writing run fluidly in English with the senior segment of the Polish IT market. Screen for English level on the first call as a sanity check, especially for client-facing or staff-plus engineering roles, but it's rarely the blocker.

Time zone is a quiet feature, not a friction. Poland is on Central European Time, which means a Berlin or Stockholm team gets full overlap, a London team is one hour off in summer, and a US East Coast team gets four to five hours of working overlap before lunch. That's enough for daily standups, real-time pairing, incident response, and synchronous design sessions.

Where do you go from here?

For the full comparison of contract paths, including B2B and your own Polish entity, the operational mechanics of each, real costs, time-to-start, and the candidate-preference dynamics that often decide the pick, see the founder's guide to hiring Polish IT specialists in 2026. For sourcing — where you actually post the role and reach Polish IT specialists — see where to post tech jobs for Polish developers in 2026.

If you've decided EOR is the path, the immediate next steps are tight: (1) shortlist three providers with strong Polish coverage, (2) ask each for an itemized monthly cost breakdown for your specific role and salary band, (3) ask for the employment contract template to share with counsel, (4) ask for two references from foreign employers in your stage, and (5) lock the vendor before mid-June 2026 if you want to be operating under EOR terms when the PIP reform takes effect on 8 July.

The reform isn't a reason to panic. It's a reason to do the structural review you should have done anyway. For foreign companies that genuinely want a dedicated, embedded Polish team member, EOR was always the cleaner option — the new PIP authority just makes the math obvious.