What the UK's SSP changes mean for your EOR provider

You hired an EOR to handle UK payroll compliance so you don't have to think about it. But on 6 April 2026, the UK's sick pay rules changed in three specific ways. Has your EOR updated their payroll calculations, employment contracts, and absence workflows? Because if they haven't, you'll find out when the first payslip goes wrong.

After your first smooth payroll run, it's natural to assume everything just works. You expect your EOR to handle the technical details. But the SSP changes mean payroll systems now need to calculate from day one instead of day four, handle a new 80% earnings calculation for lower-paid workers, and split absences that cross 6 April. We've seen providers miss these updates entirely, leaving clients to discover the gaps through employee complaints.

We've guided companies through regulatory changes in 70+ countries, and here's what we've learned: some providers update their rate tables and call it done. Others rebuild their payroll logic to handle the new rules properly. The SSP changes reveal which type you're working with. Yes, your EOR faces the penalties from HMRC. But you're the one fielding angry calls from employees, explaining to your board why payroll is wrong, and scrambling to fix the mess while your provider sorts out their systems.

What changed with UK sick pay, in plain terms

From 6 April 2026, SSP becomes payable from day one of sickness absence in the UK, eliminating the previous three waiting days that delayed payments for short absences.

Lower-paid workers who didn't qualify for SSP before now do—up to 1.3 million more employees according to HMRC. They get 80% of their average weekly earnings instead of the standard rate, up to a cap.

If someone was off sick from 1 April to 15 April, their payroll needs two different calculations: old rules for the first part, new rules for the rest. A system that can't split this will either underpay (creating disputes) or overpay (creating recovery headaches). Either way, you need proof of how it was calculated when questions come up.

UK SSP remains payable for a maximum of 28 weeks per period of incapacity for work, requiring automated exhaustion controls to prevent overpayment.

Check your EOR contract's liability cap right now. If it's £50,000 but a systematic SSP error affects 20 employees for six months, you could face £100,000+ in back-pay and penalties. Your EOR might be the legal employer, but if their liability cap is too low, you're eating the difference.

What Has Actually Changed in UK SSP Rules?

Here's what changed on 6 April under the Employment Rights Act 2025. Three things, and each one needs your payroll system to work differently.

The first change eliminates waiting days entirely. Previously, SSP wasn't payable until the fourth qualifying day of sickness absence. Now it's payable from day one. This sounds simple, but it fundamentally changes how short-term absences are processed and paid.

The second change expands eligibility to lower earners. Employees who previously fell below the Lower Earnings Limit now qualify for SSP, but their payment is calculated differently. They receive 80% of their Average Weekly Earnings rather than the flat statutory rate, subject to a £123.25 weekly cap. Your EOR's payroll system now needs dual-method calculation logic.

The third change involves transitional rules for absences spanning 6 April 2026. If an employee was already off sick before the change date and remained absent after it, the payroll system must apply the old rules to the pre-6 April portion and the new rules to the post-6 April portion—though workers earning between £125 and £154.05 weekly keep the flat rate for that continuous absence. This requires date-aware logic, not just updated rate tables.

What 'ready' looks like in practice

By now, your EOR should be able to show you exactly what they've updated: their payroll calculations, their employment contracts, and their absence reporting process.

What the payroll system must do now

The payroll engine must now calculate SSP from day one of absence, not day four. This isn't a configuration change; it's a logic change that affects every UK absence processed after the effective date. The system must also implement the 80% AWE calculation for newly eligible low earners, which means identifying which employees fall into this category and applying the correct method automatically.

Most critically, the system needs a transitional rules engine. Absences that started before 6 April and continued after require split calculations. The first portion follows the old three-day waiting period rules; the subsequent portion follows day-one rules. An EOR that relies on manual spreadsheet calculations for SSP after April 2026 increases operational error risk because day-one payment and 80% AWE logic introduce additional calculation paths and exception handling.

What your employees will read (and notice)

Every UK employment contract and employee handbook referencing SSP waiting days is now technically incorrect. Your EOR should have updated template contracts for new hires and issued handbook amendments for existing employees. If your current documentation still references three waiting days, that's a compliance gap and an employee relations risk.

What should be happening day-to-day

SSP administration requires the employer to issue Form SSP1 when an employee isn't entitled to SSP or when entitlement ends. Your EOR must have operationalised SSP1 issuance as a documented, time-bound process. The absence reporting workflow should now capture sickness from day one, not day four, because the payment trigger has moved forward.

Is My EOR Responsible for Paying SSP?

Yes. In an EOR arrangement, the EOR is the legal employer of your UK workers. This means statutory payroll obligations, including SSP, attach directly to the EOR. They're responsible for calculating, paying, and reporting SSP correctly. They're responsible for issuing SSP1 forms when required. They're responsible for maintaining compliant employment documentation.

But when they get it wrong, your employee doesn't call them. They call you. They escalate to your management team. They post in your company Slack.

If your EOR underpays SSP, your employees are affected. If they miscalculate AWE for newly eligible workers, your employees are affected. If they fail to update employment contracts, your employees notice. The legal liability sits with the EOR, but the operational disruption, employee relations damage, and reputational risk land on you.

That's why you need to check your contract's indemnity clauses. Some providers offer full coverage for their errors. Others cap it at £25,000. Some exclude 'consequential losses' entirely, which could mean your back-pay costs aren't covered.

Where Does Liability Actually Sit?

The EOR carries primary statutory liability for SSP compliance because they're the legal employer. Penalties from HMRC or the new Fair Work Agency would be directed at them. Employee claims for unpaid SSP would be against them.

But whether you're protected depends on what your contract actually says. Pull out the liability and indemnity sections now.

Some EOR contracts include broad indemnities that cover payroll errors, statutory non-compliance, and employee claims. Others cap liability at a level that wouldn't cover a serious compliance failure. A contract that caps liability below the potential value of payroll back-pay, employee claims, and regulatory penalties leaves you exposed to unrecoverable losses.

Teamed's contract-risk review approach treats indemnity clauses as critical due diligence items. You should know exactly what happens if your EOR gets SSP wrong, what their liability cap is, what's excluded, and what remediation timelines they commit to.

The five questions that reveal whether they've done the work

Ask these before your first April absence hits payroll. The answers will tell you whether your provider is ready or scrambling.

Has Your Payroll System Been Updated for All Three SSP Changes?

You want confirmation that their system handles day-one SSP calculation, 80% AWE logic for newly eligible low earners, and transitional rules for absences spanning 6 April. Ask for specifics. How does the system identify which employees qualify for the 80% AWE calculation? What logic determines whether an absence spans the transition date?

How Are You Handling Transitional Cases?

An absence that started on 1 April and continued until 15 April requires split treatment. Ask how their system handles this. Is it automated or manual? What audit trail exists to demonstrate the correct method was applied to each portion?

What Is Your Process for Day-One Absence Reporting?

SSP is now payable from day one, which means absence data must flow into payroll immediately. Ask about the workflow. Who captures the absence? How quickly does it reach the payroll team? What happens if there's a delay?

For mid-market employers, the most common SSP failure mode in outsourced payroll is late or missing absence input rather than incorrect statutory rate tables. The calculation might be right, but if the data arrives late, the payment is late.

Have You Updated Employment Contracts and Handbooks?

Any UK employment documentation referencing SSP waiting days is now incorrect. Ask whether they've updated their templates and whether they've issued amendments to existing employees. If the answer is vague, that's a red flag.

What Happens If You Get It Wrong?

This is the indemnity question. What does your contract say about liability for payroll errors? Is there a cap? What's excluded? What's the remediation process and timeline? You should know exactly what recourse you have before you need it.

Signs you'll be firefighting SSP issues in May

After years of watching providers handle regulatory changes, we know what 'not ready' looks like.

No Proactive Communication Before 6 April

Good providers sent detailed updates in February or March explaining exactly what would change. If you got nothing, or just a vague 'we're monitoring changes' email, that tells you how they'll handle the next regulatory shift too. You'll find out about problems when something breaks.

Inability to Explain Transitional Rules

If your provider can't clearly articulate how they handle absences spanning 6 April 2026, they probably haven't built the logic. This isn't an obscure edge case; it's a predictable scenario that any prepared provider should have addressed.

Handbook Templates Still Reference Waiting Days

This is an easy check. Ask for a copy of their current UK employee handbook template. If it still mentions three SSP waiting days, their documentation hasn't been updated. If their templates are wrong, your employees' documents might be wrong too.

No Mention of the Fair Work Agency

The Employment Rights Act 2025 established the Fair Work Agency with enforcement powers over employment rights, including SSP. A provider that hasn't mentioned this in any communication about the changes may not be tracking the regulatory landscape closely enough.

Reliance on Manual Processes

SSP calculation after April 2026 involves more decision points than before. Day-one payment, 80% AWE for eligible low earners, transitional rules, linked periods of incapacity. A provider relying on manual spreadsheets rather than automated payroll logic is accepting unnecessary error risk.

The paperwork you'll need when Finance asks questions

For any absence, your EOR should quickly show you: when it started, which days count as qualifying days, whether it links to any previous absences, which eight-week period they used for AWE, and exactly how they calculated the payment. If they can't produce this in minutes, they don't have proper records.

Teamed treats these as minimum artefacts for payroll defensibility. If your provider can't produce this documentation on request, they may not be maintaining adequate records.

In an EOR model, a single UK absence can touch at least three separate control points: absence capture, SSP eligibility and calculation, and payslip and statutory reporting. Each control point requires an accountable owner with evidence logs. Ask your provider who owns each step and what evidence exists.

When EOR stops buying you peace of mind

The SSP changes mean more compliance checks, more careful payroll handling, and higher stakes when things go wrong. All of this shifts the maths on whether EOR still makes sense.

Teamed's Graduation Model provides a framework for this decision. For UK operations, the entity threshold is typically 10+ employees if your team operates in English. At that point, the annual EOR cost often exceeds the amortised cost of establishing and administering your own entity.

Moving to your own entity means owning SSP compliance directly. You control the payroll system, the absence workflows, and the documentation. You're not dependent on a third party getting it right. For companies with significant UK headcount and a long-term commitment to the market, this control can be worth the additional administrative responsibility.

But entity establishment takes 2-4 months in the UK, and you need HR and legal resources capable of managing local compliance. If you're not ready for that, staying on EOR makes sense, provided your EOR is actually compliant.

What Happens If Your EOR Gets SSP Wrong?

The immediate consequence is incorrect employee pay. Underpayment creates employee relations issues and potential claims. Overpayment creates recovery complications and financial exposure.

Beyond individual cases, systematic SSP errors attract regulatory attention. The Fair Work Agency has enforcement powers, and HMRC continues to oversee statutory payment compliance. Penalties attach to the legal employer, which is your EOR, but investigations create operational disruption that affects you.

Your contractual recourse depends entirely on your agreement terms. Some contracts provide meaningful indemnification and clear remediation processes. Others leave you with limited options if your provider fails.

The best time to check is before your next payroll run with April absences. The second-best time is right now, before you discover gaps through employee complaints.

If you want a sanity check on your provider

The SSP changes are a compliance stress test. Providers who invested in their payroll infrastructure, updated their documentation, and communicated proactively with clients are demonstrating the operational rigour you're paying for. Providers who haven't are revealing gaps that may extend beyond SSP.

If you're reading this and thinking 'I need to check my provider', we can help. We'll review your setup with fresh eyes and tell you exactly where the gaps are.

Book your Situation Room to review your current EOR arrangement against the new SSP rules. We'll tell you what we'd recommend, whether that includes us or not.

What Compliance Really Costs When You're Employing Internationally

Your CFO just asked for a breakdown of compliance costs across your seven international markets. You've got invoices from three EOR providers, two local payroll vendors, and a legal firm that bills by the hour for "miscellaneous advisory." The spreadsheet you're building looks more like a crime scene than a budget forecast.

Cost of compliance is the total, measurable spend required to meet legal, tax, payroll, employment, and data-protection obligations in every jurisdiction where a company employs or engages workers. For mid-market companies operating across multiple countries, this isn't a line item you can estimate. It's a category of spend that determines whether international expansion creates value or destroys it.

The problem isn't that compliance costs exist. The problem is that most companies can't see them clearly until something goes wrong, with data breaches alone averaging $4.4 million globally according to IBM's 2025 report. Hidden FX margins, bundled fees, and undisclosed in-country partner markups create what Teamed calls the Three Layers of Opacity, a structural feature of the global employment industry that keeps buyers in the dark about what they're actually paying for.

What Your CFO Actually Needs to Know About Compliance Costs

GDPR sets administrative fines at up to €20 million or 4% of worldwide annual turnover for the most serious infringements—with EU authorities issuing over €1.2 billion in fines in 2024 alone—making data-protection controls a material compliance cost driver for HR systems and cross-border people data flows.

UK IR35 rules allow HMRC to assess unpaid tax and National Insurance Contributions retrospectively for up to 6 years in standard cases and up to 20 years where HMRC asserts deliberate behaviour.

When you enter a new country, you're looking at six workstreams minimum: getting employment contracts right, registering for payroll, setting up statutory benefits, meeting data protection rules, creating local policies, and understanding termination procedures. Most companies miss at least two of these and pay for it later.

Under the EU Working Time Directive, the baseline entitlement is at least 4 weeks of paid annual leave, creating a minimum statutory leave cost that must be budgeted and administered for EU-based employees.

Here's what catches mid-market companies off guard: it's not the monthly payroll that blows budgets. It's the terminations, contractor conversions, and relocations. These change events can cost 10x what you budgeted because nobody warned you about the severance requirements or the back-pay calculations.

When diligence or audit time comes, you'll need five documents per country ready to go: signed contracts, proof of payroll filings, benefits enrollment records, policy acknowledgments, and termination paperwork. Having these organized saves weeks of scrambling and expensive legal reviews.

What Are the Different Types of Compliance Costs?

Compliance cost types fall into four categories that behave very differently in your budget. Preventive costs cover controls and training you invest in before problems occur. Detective costs include monitoring and audits that catch issues early. Corrective costs cover remediation and back-pay when something goes wrong. Punitive costs are the fines and penalties that arrive when regulators get involved.

The distinction matters because preventive spend is budgetable and controllable, while punitive spend is event-driven and often includes multipliers like interest, back-pay, and enforcement costs. A company that invests £50,000 annually in preventive compliance controls can avoid a single corrective event that costs £200,000 in back-pay and legal fees.

Direct compliance costs differ from indirect compliance costs in a way that trips up most finance teams. Direct costs are explicitly billed or levied, including legal fees, audit fees, and fines. Indirect costs are internal time and operational friction: HR hours spent on rework, delayed hiring timelines, and process overhead that never appears on an invoice but consumes real resources.

How Do Direct Costs Show Up in Global Employment?

Direct costs are the visible portion of compliance spend. They include registration fees when entering a new country, legal review of employment contracts, payroll provider fees, benefits administration costs, and audit fees. These costs appear on invoices and can be tracked in accounting systems.

In Germany, for example, employers must navigate works councils that become mandatory at 5+ employees if employees request them. The legal review, documentation, and ongoing administration create direct costs that vary based on company size and the complexity of the employment relationship. France requires compliant payslips with mandated information and applies complex social contributions—with non-wage costs reaching 32.2% of total labour costs, the highest in the EU—which materially increases payroll configuration and vendor costs compared with simpler jurisdictions.

The challenge is that direct costs often get bundled in ways that obscure the true cost of compliance. An EOR provider might quote a flat monthly fee per employee, but that fee includes hidden FX margins on salary payments, undisclosed markups from in-country partners, and compliance fees that aren't itemised. Without line-item transparency, you can't benchmark costs or identify inefficiencies.

What Are the Hidden Indirect Costs of Compliance?

Indirect costs are harder to measure but often larger than direct costs. They include the HR time spent reconciling data across multiple systems, the management overhead of coordinating with vendors in different time zones, and the opportunity cost of delayed hiring when compliance processes take longer than expected.

Consider a 400-person UK company expanding into Spain. The direct costs might include €15,000 in legal fees, €8,000 in entity setup costs, and €500 per employee per month in payroll administration. The indirect costs include the 40 hours your HR director spends managing the process, the two-week delay in onboarding your first Spanish employee, and the ongoing reconciliation work between your UK HRIS and the Spanish payroll provider.

A common source of avoidable compliance spend is duplicated vendor coverage across payroll, benefits, HRIS, and local advisors. Consolidation can reduce the number of accountable parties per country from 4-6 vendors to 1-2 accountable owners, according to Teamed's compliance operating-model assessments. Each additional vendor creates handoffs that increase control gaps and reconciliation work.

How Should You Structure Compliance Cost Forecasting?

A finance-usable way to model compliance overhead is to separate one-time country entry costs from recurring monthly compliance run costs and to forecast both over a 12-24 month horizon. This distinction matters because entry costs are front-loaded and amortisable, while run costs compound monthly and scale with headcount.

Run costs cover recurring monthly or quarterly administration: payroll filings, benefit remittances, statutory reporting, and ongoing policy updates. Change costs are episodic and typically higher per event: terminations, conversions from contractor to employee, relocations, and audit responses. Most compliance cost articles focus on penalties and overlook operational latency costs, but time-to-compliance is a measurable cost driver for mid-market scaling.

What's the Difference Between Run Costs and Change Costs?

Run costs are predictable. Once you've established compliant employment in a country, the monthly administration follows a pattern. Payroll runs on schedule, benefits get remitted, and statutory filings happen at defined intervals. You can budget these costs with reasonable accuracy.

Change costs are where compliance budgets blow up. A termination in the Netherlands might require UWV or court involvement depending on the ground for termination, which increases expected legal fees and timeline risk compared with at-will termination models. Converting a contractor to an employee in Brazil triggers complex labour code requirements under the CLT, including 13th-month salary obligations and FGTS contributions.

The practical implication is that companies with high turnover or frequent organisational changes face higher compliance costs than companies with stable headcount. If you're planning an acquisition that will require restructuring in multiple countries, your compliance budget needs to account for change events, not just steady-state run costs.

How Do You Build a Country-Entry Cost Model?

For each new country, plan for at least six distinct workstreams: employment contracts, payroll registration, statutory benefits, data protection, local policies, and termination procedures. Each workstream has setup costs and ongoing administration costs.

Under GDPR, cross-border transfers of EU/UK personal data to jurisdictions without an adequacy decision typically require a transfer mechanism such as Standard Contractual Clauses and a transfer risk assessment. This adds legal and operational compliance cost to HR data flows that many companies underestimate.

The entry cost model should also account for employment model selection. Choose contractors when the work is project-based, deliverable-led, and you can avoid controlling hours, tools, and day-to-day supervision that would make the engagement look like employment under local tests. Choose an EOR when you need compliant employment in a new country in weeks rather than months and you don't yet have a stable headcount forecast that justifies entity setup. Choose an owned entity when the country will become a long-term operating location, you need direct control of employment terms and policies, and you can support local payroll, tax registrations, and corporate compliance on an ongoing basis.

When Does Entity Setup Become Cheaper Than EOR?

This is the question most EOR providers are structurally incentivised never to answer. Every month you stay on EOR past the crossover point is pure margin for them. Teamed's Graduation Model provides a framework for evaluating when to move from contractor to EOR to entity, based on the economics of your specific situation.

Choose a move from EOR to entity when EOR fees and pass-through compliance costs are forecast to exceed the amortised cost of entity setup and local operation over a 12-24 month period. The calculation method is straightforward: multiply your annual EOR cost by projected years, then compare against setup cost plus annual entity cost multiplied by the same projected years.

For a UK company with 10 employees in Germany, the maths might look like this. EOR costs of £7,500 per employee per year total £75,000 annually. Over three years, that's £225,000. Entity setup costs of £25,000 plus ongoing costs of £3,500 per employee per year total £130,000 over the same period. The break-even point arrives around month 17.

What Factors Affect the Crossover Point?

Country complexity matters significantly. Tier 1 countries like the UK, Ireland, Australia, and Singapore have flexible labour markets and straightforward processes. Entity setup makes sense at 10+ employees. Tier 2 countries like Germany, France, and Spain have strong employee protections and complex termination procedures. Entity setup typically makes sense at 15-20 employees. Tier 3 countries like Brazil, Mexico, and India have very high termination costs and multi-layered compliance requirements. Entity setup might not make sense until 25-35 employees.

The Language Buffer Rule adds another dimension. Operating in a non-native language increases compliance risk and administrative burden by 30-50%. A UK company operating in Germany should use a 20-30 employee threshold rather than the native 15-20 threshold to account for increased compliance complexity when the team can't read German employment law documentation directly.

Long-term commitment matters too. Entity setup costs require a multi-year presence to justify the investment. If you're testing a new market and might exit within two years, EOR remains the better choice regardless of headcount.

How Do You Manage Compliance Costs Across Multiple Countries?

Choose a unified compliance management owner when you operate in 3+ countries and have recurring change events each month, because distributed ownership increases the probability of missed filings and inconsistent documentation. The coordination costs of managing separate vendors in each country often exceed the apparent savings from shopping for the lowest-cost provider in each market.

A country-by-country vendor stack differs from a single accountable GEMO operating model because multi-vendor stacks create handoffs that increase control gaps, while a single accountable model reduces reconciliation work and improves audit traceability. GEMO, or Global Employment Management and Operations, is Teamed's category definition for managing the full global employment lifecycle, including structure selection, payroll operations, compliance, and ongoing governance across countries.

What Does a Defensible Compliance Evidence Pack Include?

From a controls perspective, a defensible compliance evidence pack typically includes at least five artefacts per country: signed contract templates, payroll filings proof, benefits enrolment evidence, policy acknowledgements, and termination documentation. Most sources list compliance cost categories but don't provide an audit-evidence checklist per country, creating gaps that surface during due diligence or regulatory review.

The evidence pack serves two purposes. First, it demonstrates compliance to regulators and auditors. Second, it creates institutional knowledge that survives personnel changes. If your HR director leaves and the new hire can't find documentation of how terminations were handled in France, you've created a compliance risk that could have been avoided with proper record-keeping.

What Technology and Process Controls Reduce Compliance Costs?

Automation reduces run costs by eliminating manual data entry and reconciliation. A single platform that manages contractors, EOR employees, and owned entities in one view eliminates the hours spent pulling data from multiple systems to answer basic questions about your global workforce.

Process controls reduce change costs by standardising how you handle terminations, conversions, and relocations. When every termination in Germany follows the same documented process, you reduce the risk of errors that trigger corrective costs. When every contractor conversion follows the same assessment framework, you reduce the risk of misclassification claims.

The highest-value compliance investments are often the least visible. Training your HR team on local employment law, building relationships with in-country legal advisors, and creating playbooks for common scenarios all reduce the probability of expensive mistakes.

What Are the Biggest Compliance Cost Mistakes Mid-Market Companies Make?

The first mistake is treating compliance as a cost centre rather than a risk function. Compliance costs are insurance premiums against much larger potential losses. A £50,000 annual investment in compliance controls looks expensive until you compare it to a £500,000 back-pay claim or a regulatory fine that damages your reputation.

The second mistake is optimising for the lowest per-employee cost without considering total cost of ownership. An EOR provider that charges £400 per employee per month but buries £50 per employee in hidden FX margins costs more than a provider that charges £450 with transparent pricing. You can't optimise what you can't see.

The third mistake is failing to plan for change events. Steady-state compliance is manageable. The budget-busting surprises come from terminations that trigger complex severance calculations, conversions that require back-dated benefits enrolment, and relocations that create tax obligations in multiple jurisdictions.

What to Do Monday Morning

The global employment industry profits from keeping compliance costs opaque. Providers benefit when you can't compare their pricing to alternatives, when you don't know when entity setup becomes cheaper than EOR, and when you're too confused to ask the right questions.

The antidote is transparency. Demand line-item breakdowns of every cost. Model the crossover economics for each country where you have significant headcount. Build evidence packs that document your compliance posture. And work with advisors who are economically aligned with helping you make the right structural decision at every stage, even when that means graduating off their most profitable product.

If you're managing compliance costs across multiple countries and want an honest assessment of whether you're in the right structure, book your Situation Room. We'll review your current setup and tell you what we'd recommend, whether that includes us or not.

What are the pros and cons of centralized versus decentralized approaches to global benefits management?

Your CFO wants a single source of truth for benefits spend across eight countries. Your country managers insist they need local flexibility to compete for talent in their markets. Meanwhile, you're staring at 15 different invoice formats, three brokers who don't talk to each other, and a renewal calendar that nobody owns.

This tension between global consistency and local responsiveness sits at the heart of every global benefits strategy decision. Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. Based on our advisory work with over 1,000 companies across 70+ countries, the choice between centralized and decentralized global benefits management isn't binary. It's about matching your governance model to your operational reality.

The honest answer? Most mid-market companies operating in 5-15 countries need a hybrid approach that delivers central oversight without strangling local execution. Here's how to think through the trade-offs.

What Actually Happens When You Centralize (or Don't)

When companies centralize benefits, they often cut their vendor count by a third within a year through platform consolidation. Makes sense: one team picking brokers means fewer relationships to manage.

Let countries run their own benefits? Watch your plan variations multiply. We've seen companies go from 3 basic plans to 15 different versions after two years of local negotiations.

One person can realistically handle benefits for about 8-15 countries before they start missing renewals and living in spreadsheets. After that, you need help or things break.

Set clear rules about what needs approval and what doesn't? You can cut special deals and one-offs by half. Takes about two years to see the full effect.

Benefits renewals need 6-10 weeks per country. Miss that window and you're looking at coverage gaps, wrong payroll deductions, and very unhappy employees.

Let each country manage their own benefits invoices? You'll get 10-25 different formats to reconcile every month. Your finance team will not thank you for the payroll management complexity this creates.

What is centralized global benefits management?

Centralized global benefits management is an operating model where a single global or regional team sets benefits policy, selects vendors, approves plan designs, and governs compliance across all countries, with limited local discretion. The global team owns the relationship with brokers, runs renewals, and maintains a unified view of costs and coverage.

This model works best when leadership requires a single source of truth for benefits spend, plan eligibility rules, and renewal decisions across jurisdictions. It's particularly valuable when the CFO demands consistent cost allocation and month-end close controls, including standardized invoice mapping and approval workflows.

The centralized approach concentrates decision rights in one place. Plan design, vendor selection, renewals, exceptions, and employee communications all flow through the global team. Local HR becomes an execution partner rather than a decision-maker.

What are the advantages of centralized benefits management?

Centralize your benefits and you typically gain three things: fewer cost surprises, cleaner audit trails, and better negotiating power with vendors.

Cost predictability improves dramatically when one team owns procurement and reporting. Central models can standardize invoice formats, map costs to general ledger codes consistently, and provide the CFO with reliable month-end close evidence. You're not chasing 10 different country teams for spend data that arrives in incompatible formats.

Compliance evidence becomes repeatable and auditable. A centralized governance structure can standardize GDPR processor contracts, vendor due diligence documentation, and change logs across countries. When Legal asks for evidence of lawful processing and documented decision-making for benefit changes, you have it in one place rather than scattered across local filing systems.

Vendor leverage increases with consolidated procurement. Centralizing benefits procurement can achieve 5-15% premium improvements in mature markets when risk pooling and consistent underwriting data are feasible. You're negotiating as one company rather than 10 separate buyers.

The hidden benefit is strategic coherence. When one team owns the benefits baseline, you can define what must be consistent across countries and what can vary locally. This prevents the drift that happens when each country makes independent decisions over multiple renewal cycles.

What are the disadvantages of centralized benefits management?

Centralized models create real operational friction that you need to anticipate. The three most common pain points are implementation speed, local market fit, and resource concentration risk.

Implementation speed suffers because every change requires global approval. A country manager who spots a competitive gap in their benefits offering can't act quickly. By the time the request moves through the global approval process, the candidate they were trying to attract has accepted another offer. Decentralized models can act quickly locally but struggle to coordinate multi-country alignment.

Local market fit becomes harder to achieve. Employee expectations vary significantly across markets. What counts as a competitive health plan in the Netherlands looks nothing like expectations in Brazil. A global team making decisions from London or New York may not fully understand why the Spanish team insists on a specific benefit structure that aligns with local collective bargaining norms, especially when employees rank pensions 10 places higher than employers as a retention factor.

Resource concentration creates single points of failure. If your global benefits owner leaves, institutional knowledge walks out the door. With 8-15 countries per dedicated owner being a practical governance span, losing that person mid-renewal cycle creates chaos.

The cultural friction is real too. Country teams who've built strong local broker relationships often resist central mandates. They've invested years in those relationships and believe they understand their market better than headquarters.

What is decentralized global benefits management?

Decentralized global benefits management is an operating model where country HR and Finance teams own benefits design and vendor decisions locally, with only minimal global standards or reporting requirements. Each country runs its own renewals, selects its own brokers, and designs plans that fit local market norms.

This model works best when each country has materially different employee demographics, benefit expectations, or statutory interactions that make a single plan design impractical. It's also appropriate when local teams have proven broker relationships and strong internal capability to run renewals, communications, and employee support without central escalation.

Decentralized models prioritize speed and local responsiveness over consistency and control. The trade-off is explicit: you gain agility at the cost of visibility.

What are the advantages of decentralized benefits management?

Decentralized benefits management excels at local market fit and speed of response. These advantages matter most in competitive talent markets where benefits differentiation drives hiring outcomes.

Local market fit improves because country teams can tailor benefit mix and communications to local expectations faster than a global approval process typically allows. They understand the nuances of what makes a benefits package competitive in their specific market. In Germany, that might mean understanding works council expectations. In France, it means navigating the Code du travail and CSE requirements at 11+ employees.

Speed of response increases dramatically. When a country manager identifies a gap, they can act within their local approval authority. No waiting for global review cycles. No explaining local context to someone who's never worked in that market.

M&A integration becomes more flexible. Acquired companies often have legacy benefit arrangements that employees value. Decentralized models can preserve these arrangements longer, reducing integration friction and employee anxiety during transitions.

The relationship advantage shouldn't be underestimated either. Local HR teams who own their benefits relationships often have deeper knowledge of claims patterns, employee feedback, and broker capabilities than a global team could develop remotely.

What are the disadvantages of decentralized benefits management?

Let benefits run locally for too long and three things happen: finance loses track of spend, compliance evidence scatters everywhere, and your benefits start looking like ten different companies.

Cost opacity makes CFO oversight nearly impossible. Decentralized models typically result in 10-25 distinct benefits invoice formats across 10 countries, which increases reconciliation workload and makes it harder to evidence cost allocation by legal entity. Your finance team spends hours each month just getting the data into comparable formats.

Compliance fragmentation creates audit risk. When each country maintains its own documentation practices, you end up with inconsistent retention schedules, varying quality of vendor due diligence records, and no central view of GDPR processor contracts. An audit becomes a scramble across multiple countries rather than a retrieval from one system.

Strategic drift happens gradually. Each country negotiates independently and retains legacy benefit variants after acquisitions. Over five years, you end up with 2-5x more distinct plan designs than a centralized model would have. Nobody planned for this complexity. It accumulated through hundreds of independent local decisions.

The hidden cost is coordination overhead. Without central governance, someone still needs to ensure basic consistency. That coordination happens informally, inefficiently, and often too late to prevent problems.

How does benefits strategy change across employment models?

Here's what most content on this topic misses entirely: your benefits governance model needs to evolve as your employment structure changes. Teamed's Graduation Model describes the natural progression companies follow as they scale internationally, from contractors to Employer of Record to owned entities.

When you're employing people through an EOR, benefits governance is often simpler to centralize. The EOR is typically the legal employer and may be the policyholder for insured benefits. You're working with one partner who handles local compliance, and you can maintain central control over vendor selection and plan design.

When you establish your own entities, the calculus shifts. You now have direct relationships with local insurers, local regulatory obligations, and local HR teams who need authority to manage day-to-day benefits administration. The transition from EOR to entities brings new complexities that require different governance approaches. Decentralization becomes more necessary because you're operating as the legal employer in each jurisdiction.

The Graduation Model provides continuity across these transitions through a single advisory relationship. As your structure evolves from EOR to entity, your benefits governance model should evolve too. Companies that try to maintain the same centralized control they had under EOR often struggle when they establish entities and discover that local teams need more authority than the governance model allows.

When should you choose centralized benefits management?

If you're in 5+ countries and leadership keeps asking the same questions about benefits spend that nobody can answer quickly, it's time to centralize.

Choose centralized when the CFO requires consistent cost allocation and month-end close controls. If your finance team is spending significant time reconciling benefits invoices from multiple formats and sources, centralization solves that problem.

Choose centralized when Legal and Compliance require repeatable evidence of lawful processing, vendor due diligence, and documented decision-making for benefit changes across countries. Centralized governance can standardize these controls in ways that decentralized models struggle to achieve.

The decision criteria should include your growth trajectory. If you're planning to expand from 5 countries to 15 over the next three years, building centralized governance now prevents the fragmentation that becomes painful to unwind later.

When should you choose decentralized benefits management?

Keep it decentralized when your countries are genuinely different: factory workers in Poland, software engineers in Singapore, salespeople in Brazil, where tax wedges range from 52.6% to 0% across countries.

Choose decentralized when local teams have proven broker relationships and strong internal capability to run renewals, communications, and employee support without central escalation. If your country HR leads have deep benefits expertise and established vendor relationships, centralizing might destroy value rather than create it.

Choose decentralized when speed of local response matters more than global consistency. In highly competitive talent markets where benefits differentiation drives hiring outcomes, the ability to move quickly may outweigh the benefits of central control.

The honest assessment: most mid-market companies don't have the local HR depth to make pure decentralization work well. It requires at least 0.1-0.3 FTE per country to handle enrolment, leavers, insurer queries, and payroll inputs. Lean HR teams often struggle to provide this capacity across multiple countries.

What does a hybrid benefits model look like?

Choose a hybrid model when the company needs global governance but must allow local selection of carriers and plan design to fit country-specific market norms. This is where most mid-market companies land.

A hybrid model separates governance from execution. The global team owns principles, reporting standards, approval limits, and vendor due diligence requirements. Local teams own carrier selection, plan design within defined parameters, and employee communications.

The practical implementation requires a decision-rights matrix. Who owns plan design? Who approves vendor selection? Who runs renewals? Who handles exceptions? Who manages employee communications? Answering these questions explicitly prevents the ambiguity that makes hybrid models fail.

A workable global benefits reporting cadence for CFO oversight is monthly cost tracking plus a quarterly variance review. Benefits invoices and payroll deductions frequently lag by 30-60 days across multi-country vendor setups, so your reporting cadence needs to account for this timing gap.

The hybrid model also works well when the company is expanding without local entities and needs central control over vendor selection and compliance evidence while execution happens through in-country partners or an Employer of Record.

How do you build a benefits governance framework that works?

Most top-ranking explanations of centralized versus decentralized global benefits management omit a decision-rights matrix. Here's what yours should include.

Define who owns plan design decisions. In a hybrid model, the global team typically sets the benefits baseline (minimum categories like medical, risk, retirement, and leave support) while local teams choose carriers and plan richness within those categories.

Define approval limits for exceptions. When a country wants to deviate from the global baseline, what's the threshold that requires global approval? Setting this explicitly reduces friction and speeds decisions.

Define the renewal calendar and lead times. Annual benefits renewal cycles commonly require 6-10 weeks of lead time per country. Building a 12-month multi-country benefits calendar that accounts for these lead times prevents last-minute compliance and payroll errors.

Define reporting requirements. What data does each country need to provide, in what format, by what date? Standardizing this upfront prevents the invoice reconciliation chaos that plagues decentralized models.

Define escalation paths. When local teams encounter situations outside their authority, who do they escalate to? How quickly should they expect a response?

What compliance considerations affect your choice?

Running benefits across Europe? You're dealing with GDPR contracts, varying pension requirements, and works council approvals. Your governance model needs to handle all of it.

UK auto-enrolment requires eligible workers to be automatically enrolled into a qualifying workplace pension scheme, with minimum 8% total contributions set by law and employer duties enforced by The Pensions Regulator. Standardizing pension matching across countries becomes complex when each jurisdiction has different statutory requirements.

In the European Union, cross-border benefits administration must comply with GDPR requirements for lawful basis, transparency, data minimisation, and appropriate processor contracts when insurers, brokers, and admin platforms process employee personal data. Centralized models can standardize these controls more easily.

Germany's benefits administration must account for the statutory social security system, and voluntary benefits that behave like remuneration can trigger payroll tax and social security treatment depending on structure and documentation. Local expertise matters here.

When benefits are delivered through an Employer of Record in Europe or the UK, the EOR is typically the legal employer and may be the policyholder for insured benefits. This can constrain portability of plans if the company later sets up its own entity and wants to migrate employees.

How to Decide Without Starting a Re-org

The centralized versus decentralized question isn't about finding the theoretically optimal model. It's about matching your governance structure to your operational reality, your growth trajectory, and your internal capabilities.

If you're operating in 5+ countries with CFO pressure for cost visibility and compliance evidence, some form of centralization is probably necessary. If you have strong local HR teams with deep market expertise and established vendor relationships, preserving some local authority makes sense.

Most mid-market companies need a hybrid model that delivers central oversight without strangling local execution. The key is defining decision rights explicitly so everyone knows who owns what.

If you're struggling to figure out the right benefits governance model for your situation, or if your current approach is creating more problems than it solves, book your Situation Room. We'll review your setup and tell you what we'd recommend, whether that includes us or not.

Can an EOR help with hiring contractors versus full-time employees in Australia?

You've found the perfect candidate in Sydney. They're ready to start in two weeks. Now comes the question that keeps HR leaders up at night: contractor or employee? And if employee, how do you actually employ them without an Australian entity?

The distinction matters more in Australia than in most markets. Australian authorities take worker classification seriously, and the consequences of getting it wrong extend beyond back taxes to include superannuation penalties, workers' compensation claims, and potential litigation with penalties reaching AUD 495,000 for sham contracting violations. An Employer of Record can help navigate both options, but understanding when to use each structure is where most companies stumble.

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. From first hire to your own presence in-country, the goal isn't to default to one solution but to match the structure to the actual working relationship.

What Actually Matters for Australian Employment Decisions

Australia's National Minimum Wage is AUD 24.10 per hour and AUD 915.90 per week for a 38-hour week as of 1 July 2024, according to the Fair Work Commission.

The Superannuation Guarantee rate is 11.5% of ordinary time earnings from 1 July 2024 and increases to 12% from 1 July 2025.

Australia's standard full-time working week is 38 hours unless a Modern Award or agreement specifies otherwise.

UK and EU companies learn fast that Australia reclassifies aggressively. When you manage contractors like employees, setting their hours and integrating them into teams, Australian authorities will call them employees regardless of your contract. The ATO has visibility over 185,000 businesses paying contractors through its Taxable Payments Annual Reporting system.

EOR onboarding in Australia takes 3-10 business days if your candidate has their tax file number and superannuation details ready. Miss a payroll cut-off or wait for right-to-work verification, and you're looking at another two weeks.

At the 12-month mark, review every contractor arrangement. Check if they're still project-based or if they've drifted into BAU work. Document why contractor status still fits, or convert them before an audit forces the issue.

What does an EOR actually do for Australian hiring?

An Employer of Record is a third-party organisation that becomes the legal employer for a worker in a specific country, running compliant local payroll, tax withholding, statutory reporting, and employment documentation while the client company directs day-to-day work. In Australia, this means the EOR handles superannuation contributions, PAYG withholding, leave entitlements, and compliance with the Fair Work Act 2009.

The EOR doesn't replace your management relationship with the worker. You still direct their tasks, set objectives, and integrate them into your team. What changes is who holds the legal employment relationship and the compliance obligations that come with it.

For companies without an Australian entity, an EOR provides the only compliant path to hiring full-time employees. Without one, you'd need to establish a local proprietary limited company, register for payroll tax, set up superannuation accounts, and navigate Modern Awards. That process typically takes 2-4 months and requires ongoing administrative infrastructure.

How do contractors differ from full-time employees in Australia?

The legal distinction between contractors and employees in Australia isn't determined by what you call the arrangement. It's determined by the reality of the working relationship. Australian courts and the Australian Taxation Office apply multi-factor tests that examine control, integration, and the nature of the engagement.

A contractor in Australia is an independent business, either a sole trader or company, that provides services under a commercial contract. They're responsible for their own tax, invoicing, and insurance. They control how and when they complete the work, can subcontract, and typically supply their own tools and equipment.

A full-time employee is engaged under an employment contract covered by the Fair Work Act 2009, applicable Modern Awards or enterprise agreements, and statutory employer obligations. This includes superannuation contributions at 11.5%, paid leave entitlements, and protections against unfair dismissal.

The practical difference comes down to control. When you dictate hours, methods, and day-to-day processes, the relationship looks like employment regardless of the contract label. When the worker operates independently, sets their own schedule, and could theoretically work for multiple clients, the contractor model holds up.

When should you choose a contractor arrangement in Australia?

Use contractors when they genuinely run their own business. They should have an ABN, other clients, their own insurance, and complete freedom over when and how they deliver the project. If you're telling them to be online 9-5 Sydney time, you've already crossed into employee territory.

Project-based work with defined deliverables fits the contractor model well. A consultant engaged to implement a specific system, a designer creating a brand identity, or a developer building a discrete application can all work as contractors if the relationship maintains genuine independence.

The key indicators that support a contractor classification include the worker setting their own hours, using their own equipment, having the ability to accept or decline work, and carrying their own insurance. They should invoice for completed work rather than receiving regular salary payments, and they should have the right to subcontract the work to others.

Where companies get into trouble is when a contractor arrangement starts as project work but evolves into an ongoing, integrated role. The person attends team meetings, uses company systems, has fixed hours, and reports to a manager. At that point, the substance of the relationship has become employment, and the contractor label creates compliance risk.

When does an EOR make more sense than a contractor?

Use an EOR when you need someone working Australian hours on BAU tasks, attending team meetings, and following your processes. If you're going to manage them like an employee, make them one through an EOR.

The clearest signal is how you intend to manage the person. If they'll have fixed working hours, ongoing line management, and access to internal systems in a way that would look like employment under a control-and-integration assessment, an EOR structure eliminates the misclassification risk entirely.

EOR also makes sense when you want to offer competitive benefits. Australian employees expect superannuation contributions, paid annual leave (4 weeks minimum), personal leave, and public holidays. Contractors don't receive these entitlements, which can make contractor arrangements less attractive to top candidates who want employment security.

From a compliance perspective, an EOR provides a single accountable party for payroll withholding, statutory reporting, and local employment documentation. Your legal and finance teams get clean records and clear liability boundaries rather than the ambiguity of contractor arrangements that might be challenged later.

Our simple rule: if you're managing them like staff, make them staff. Fixed hours, direct supervision, and team integration mean employee status through an EOR typically carries less risk than trying to maintain contractor fiction.

What are the cost differences between contractors and EOR employees?

The headline cost comparison between contractors and EOR employees often misleads companies because it ignores the full picture. A contractor might appear cheaper because you're not paying superannuation, leave entitlements, or EOR service fees. But that comparison assumes the contractor arrangement is compliant, which isn't always the case.

For a genuine contractor, you pay the agreed rate plus GST (if they're registered), and they handle their own tax and superannuation. For an EOR employee, you pay the salary plus superannuation (11.5%, rising to 12%), payroll tax where applicable, workers' compensation insurance, and the EOR service fee.

The hidden cost in contractor arrangements is contingent liability. If the Australian Taxation Office or a court determines that your contractor was actually an employee, you face back-payment of superannuation (plus 10% annual interest and penalties), potential payroll tax assessments, and workers' compensation claims. These assessments can look back multiple years.

Teamed's Crossover Economics methodology evaluates employment costs by modelling fully loaded employment costs, including salary, statutory on-costs, benefits, and payroll administration, over a 24-36 month horizon rather than comparing only EOR fees to salary. This approach reveals the true cost difference and helps identify when entity setup becomes more economical than ongoing EOR fees.

How do you avoid misclassification risk in Australia?

Worker misclassification is the legal and tax risk that arises when a person treated and paid as an independent contractor is later determined to be an employee for employment law, payroll tax, superannuation, or workers' compensation purposes. Australia applies this determination based on the actual working relationship, not the contract terms.

The practical test examines several factors. Does the worker control how they complete the work? Can they subcontract? Do they supply their own tools? Are they integrated into your business operations? Do they work set hours? Do they have the ability to work for other clients? No single factor is determinative, but the overall picture must support genuine independence.

For mid-market companies expanding into Australia, the safest approach is to document the contractor relationship thoroughly before engagement. This means written contracts that reflect the actual arrangement, evidence of the contractor's independent business (ABN registration, insurance, other clients), and ongoing monitoring to ensure the relationship doesn't drift toward employment.

When a role that started as short-term services becomes business-critical and ongoing, converting early is usually simpler than remediating a later misclassification dispute. The conversion process through an EOR is straightforward: the contractor becomes an employee of the EOR, and the working relationship continues with proper employment protections in place.

Is it better to hire employees or independent contractors?

The answer depends entirely on the nature of the work and how you intend to manage the relationship. Neither option is inherently better. The right choice matches the legal structure to the operational reality.

Choose contractors for genuinely independent project work where the person controls their methods and schedule. Choose employees (via EOR or direct employment) for ongoing roles where you need to direct the work, set hours, and integrate the person into your team.

The question most companies should ask isn't "which is cheaper?" but "which accurately reflects how this person will actually work?" Getting that answer right avoids compliance problems and creates a sustainable employment relationship.

For companies hiring their first few people in Australia while testing the market, contractors can provide flexibility. But once roles become ongoing and integrated, the risk profile shifts. Teamed's Graduation Model describes this natural progression: companies often start with contractors, move to EOR as compliance requirements tighten, and eventually establish their own entity when headcount justifies the investment.

What should you look for when choosing an EOR provider?

The EOR market has grown crowded, and not all providers offer the same depth of compliance capability. For Australian hiring specifically, look for providers with genuine in-market expertise rather than just operational capacity.

Strong compliance capabilities mean the provider has local legal teams informing their recommendations, not just automated contract generation. They should understand Modern Awards, which add complexity to Australian payroll, and have clear processes for handling leave entitlements, public holidays, and termination requirements.

Transparency on costs matters enormously. Teamed's Three Layers of Opacity framework identifies three frequent sources of hidden EOR cost variance: undisclosed FX margin, bundled compliance fees, and in-country partner markups. Finance teams should request itemised invoicing that separates these components before signing any agreement.

The right structure for where you are, trusted advice for where you're going. That means your EOR provider should proactively advise when entity establishment makes more sense than ongoing EOR fees. If a provider never raises this conversation, they're optimising for their revenue rather than your interests.

How does the Graduation Model apply to Australian hiring?

The Graduation Model is Teamed's framework for guiding companies through sequential employment model transitions: from contractor to EOR to entity. The model recognises that the optimal structure changes as your Australian presence grows.

For companies hiring their first 1-3 people in Australia, contractors or EOR both work depending on the role type. As headcount grows and roles become more integrated, EOR typically becomes the appropriate structure because it eliminates misclassification risk while providing employment benefits that attract talent.

Australia sits in Tier 1 of Teamed's country complexity framework, meaning entity establishment becomes economically viable at around 10 employees for companies operating in English. The entity threshold accounts for Australia's transparent regulatory framework, common law system, and English operating language, which reduce the compliance burden compared to higher-complexity markets.

The advantage of working with a GEMO provider is continuity across these transitions. When you graduate from EOR to entity, you don't need to find a new provider, re-onboard employees, or rebuild compliance infrastructure. The relationship continues, and only the underlying employment model evolves.

What's the fastest path to compliant hiring in Australia?

For companies without an Australian entity, EOR provides the fastest compliant path to hiring employees. Onboarding can typically complete in days to a few weeks when right-to-work checks, local contract generation, and payroll cut-offs are aligned.

The common delays come from missing worker documents or benefit selections rather than payroll processing capacity. Having candidates ready with their tax file number, superannuation fund details, and right-to-work documentation accelerates the process significantly.

For contractor engagements, the timeline is even shorter since there's no payroll setup required. But speed shouldn't override compliance considerations. A fast contractor engagement that later gets reclassified as employment creates far more work than taking time to structure the relationship correctly from the start.

If you're evaluating your Australian hiring strategy and want clarity on whether contractors, EOR, or direct employment fits your situation, book your Situation Room. Tell us your setup, and we'll tell you what we'd recommend, whether that includes us or not.

Making the right structural decision for Australia

The question of whether an EOR can help with hiring contractors versus full-time employees in Australia has a clear answer: yes, but not in the way most companies expect. An EOR doesn't just process paperwork. The right EOR partner helps you determine which structure fits each role, manages the compliance complexity, and advises when your Australian presence has grown enough to justify a different approach.

The honest answer is that many companies default to contractors because it seems simpler, then face compliance challenges when those arrangements don't hold up to scrutiny. Others stay on EOR longer than necessary, paying ongoing fees when entity establishment would be more economical. The right structure depends on your specific situation: headcount, role types, long-term commitment to the market, and internal capacity to manage compliance.

From first hire to your own presence in-country, the goal is matching structure to reality at each stage. That's what separates strategic global employment from simply processing payroll in another country.

What's the real cost when you hire someone internationally?

You've just acquired a team of 15 in the Netherlands. The board wants a budget by Friday. And the salary figures you've been given tell you almost nothing about what you'll actually spend.

Here's what catches most companies off guard: the salary you offer is just the beginning. By the time you add employer taxes, benefits, and everything else that lands on your invoice, you're looking at 25% to 60% more than that salary figure. We've seen this pattern play out with companies in over 70 countries. Budget for salary alone, and every new hire takes you further from your forecast.

When your CFO asks about cost per employee, they mean everything: salary, employer taxes, benefits, equipment, the works. Getting this number right for each country and employment model you use? That's what separates smooth expansions from the kind of budget surprises that trigger emergency board meetings.

What usually blows up employment budgets

In Europe and the UK, expect to pay 1.25× to 1.60× the gross salary once you factor in employer taxes, standard benefits, and basic equipment. That's a £60,000 salary costing you £75,000 to £96,000, depending on the country and what benefits you offer.

UK employer National Insurance runs at 15% since April 2025 on earnings above the secondary threshold, making it one of the largest non-salary line items for UK headcount planning.

France employer social charges commonly range from 25% to 45% of gross salary depending on role, remuneration level, and applicable reliefs, with non-wage costs at 32.3% of total labour costs according to Eurostat.

Germany employer social security contributions typically run approximately 20% to 23% of gross salary up to statutory assessment ceilings.

When someone leaves, the real cost hits hard. Between recruiting fees, the time it takes someone new to get up to speed, and lost productivity, you're looking at 6 to 9 months of salary to replace a mid-level employee. That's before you even factor in what it costs to keep them.

Across EU and UK markets, paid annual leave minimums cluster at 20 working days under EU law for full-time workers, representing a built-in cost of paid time not worked.

What makes up the true cost per employee?

Every employee cost falls into one of four buckets: what you pay them, what the government requires you to pay, the benefits you provide, and what it costs to keep them working. Miss any of these in your planning, especially across different countries, and watch those budget gaps grow with every hire.

Compensation includes base salary, bonuses, commissions, and any variable pay. This is the number most companies start with, but it's rarely more than 60% to 80% of the total employer cost depending on jurisdiction.

Every country has its own employer taxes you pay on top of salary. The UK keeps it simple: 13.8% National Insurance above the threshold. France? That's where it gets interesting, with social charges that can hit 45% of gross salary. Germany lands somewhere in between at 20% to 23%, though it gets cheaper for high earners once you hit the contribution ceilings. These aren't minor differences when you're budgeting across countries.

Benefits include both mandatory and optional components. Mandatory benefits vary by country: UK auto-enrolment pensions require a minimum 3% employer contribution on qualifying earnings, while the Netherlands mandates holiday allowance (vakantiegeld) as an additional percentage of salary. Optional benefits like private health insurance, enhanced pension contributions, and wellness programmes add further costs that vary by your benefit design choices.

Operational overhead covers equipment, workspace, training, software licenses, and the HR administration time required to manage each employee. These costs are often invisible in salary-only budgeting but become significant at scale.

How do employer costs vary by country?

Put the same person on the same salary in London versus Paris, and your actual cost can vary by £20,000 or more. That's not a rounding error. It's the kind of difference that changes where you build your team.

UK employer costs are relatively predictable. Beyond the 13.8% National Insurance contribution, you'll budget for auto-enrolment pension (minimum 3% employer contribution), statutory paid holiday of 5.6 weeks per year, and any enhanced benefits you choose to offer. A £60,000 salary typically becomes £72,000 to £78,000 in fully loaded cost before operational overhead.

France keeps you on your toes. Social charges run anywhere from 25% to 45% of gross salary, and that's before you hit the collective bargaining agreements. Two people earning the same salary can cost you different amounts based on which agreement applies to their role. That £60,000 position? Budget £78,000 to £90,000 minimum, and check which convention collective applies before you make the offer.

Germany sits in the middle, with employer social security contributions of approximately 20% to 23% up to statutory assessment ceilings (Beitragsbemessungsgrenzen). Above those ceilings, contributions for certain insurance lines stop increasing even if gross salary continues to rise. This creates a non-linear cost curve that affects how you think about senior hires.

The Netherlands adds mandatory holiday allowance (vakantiegeld) on top of salary, creating a predictable annual uplift that must be included in budgeting even when monthly salary looks unchanged. Employer on-costs frequently push total employer cost above 1.30× gross salary for professional roles.

What are the hidden costs of employment most companies miss?

The costs that catch you out aren't really hidden. They just don't show up on the offer letter. Holiday pay, sick leave, that extra month's salary in some countries, the equipment they need to do their job. All predictable, all expensive, all missing from that salary figure you're using to budget.

Paid time not worked is the most commonly underestimated cost. Under EU Working Time rules, the minimum paid annual leave for most workers is 4 weeks per year, and this minimum applies regardless of performance or workload. UK statutory entitlement is 5.6 weeks. When you pay someone for 52 weeks but get productive work for 46 to 48 weeks, your effective cost per productive day is significantly higher than your daily salary rate suggests.

Employer risk coverage includes workers' compensation insurance, employer liability insurance, and in some jurisdictions, mandatory disability or unemployment insurance contributions. These costs vary by industry and role but typically add 1% to 5% of salary.

Recruiting and onboarding costs are often treated as one-time expenses, but with typical turnover rates, they become recurring. A practical budgeting rule used in mid-market finance teams is that replacing a mid-level employee can cost 6 to 9 months of that role's salary once recruiting fees, ramp time, and productivity loss are included.

Running payroll, filing taxes, staying on top of employment law, managing HR admin. Do it in one country and it's manageable. Add a second country and the workload doesn't double, it triples. By country three or four, especially with different providers in each market, you're drowning in compliance work that nobody budgeted for.

Termination costs represent contingent liabilities that should be factored into workforce planning. In many European countries, employer severance and notice pay obligations can add 1 to 3 months of payroll cost for an individual termination depending on tenure and local rules.

How does employment structure affect cost per employee?

How you employ someone matters as much as where. Contractors, EOR, your own entity, each comes with its own cost structure. Those online calculators that give you one number? They're assuming you've already decided how to employ, when that decision can swing your costs by thousands per person.

Contractors appear cheaper on paper because you avoid employer social contributions and paid leave accruals. But the financial downside of misclassification can exceed the "savings" through retroactive taxes and employee-rights claims. UK IR35 (off-payroll working) rules require medium and large companies to determine contractor status, with HMRC able to assess back taxes for up to 6 years in typical cases and up to 20 years in cases involving deliberate behaviour.

With EOR, you're trading setup headaches for a monthly fee. You still pay all the employer costs, salary, taxes, benefits, then add £300 to £600 per person per month for the service. What you get: someone on the ground in days, not months, and you don't have to figure out local entity setup. The math works when you need speed or when you're testing a market.

Owned entities have higher upfront and ongoing fixed costs but can reduce marginal per-employee cost at scale. Entity setup costs, local accounting, compliance management, and governance overhead create a fixed cost base that only makes sense when amortised across sufficient headcount.

Teamed's Graduation Model provides a framework for understanding when to move between these structures. The crossover point, where entity setup becomes cheaper than EOR, varies by country complexity. In low-complexity countries like the UK, Ireland, or Singapore, entity establishment typically makes sense at 10+ employees. In high-complexity countries like Brazil, India, or China, you might stay on EOR until 25 to 35 employees because the compliance burden and termination costs make the EOR fee effectively an insurance premium.

Which method for calculating labour cost is most efficient?

Salary-only budgets work for exactly one thing: checking if your offer is competitive. For everything else, cash planning, runway calculations, deciding between countries, you need the full picture. Otherwise you're planning with 60% of the data.

The most efficient approach for mid-market companies operating across multiple countries is country-specific cost modelling. A single global multiplier (the common advice to "add 20% to 30%") breaks down quickly when your French team costs 40% more than salary while your UK team costs 25% more. The variance is too large for meaningful planning.

Smart teams budget three ways. Your low scenario: just what the law requires. Your base case: legal minimums plus the benefits everyone else offers for that role. Your high scenario: competitive benefits, strong pension match, plus a buffer for exit costs. Present all three to your CFO and let them choose their comfort level.

For each country, list out what you'll actually pay: employer taxes and where they kick in, benefits the law requires, how many weeks of holiday you're funding, and what extras you're offering to compete. Now you've got real numbers to work with, not generic multipliers that fall apart the moment you hire someone.

Teamed's budgeting guidance for mid-market Europe and UK hiring uses a baseline fully loaded employee cost of 1.25× to 1.60× gross salary as a starting range, then adjusts based on country-specific statutory burdens and benefit design choices.

What is the cost per employee metric and how should you use it?

Cost per employee is simple: what hits your bank account to keep someone on the team. Not just salary. Everything. It's the only number that lets you compare a developer in Dublin with one in Berlin and know which actually costs more.

Use this metric for headcount planning and budget forecasting. When you're projecting next year's costs, you need fully loaded figures, not salary figures that ignore 25% to 60% of your actual spend.

Use it for location strategy decisions. If you're choosing between hiring in the UK versus France versus Germany, salary comparisons are misleading. A role that pays £60,000 in the UK might pay €65,000 in France, but the fully loaded costs could be £75,000 versus £95,000.

Use it for employment model decisions. When you're evaluating whether to use contractors, EOR, or establish an entity, you need to compare total cost of employment, not just the visible fees. An EOR fee of £500 per month looks expensive until you factor in the entity setup costs, local accounting fees, and compliance management time you're avoiding.

When the board asks what your German team costs, they don't want salary totals. They want the real number: salaries plus employer taxes, benefits, equipment, and your share of the compliance work to keep them employed. That's the number that matters for budgets and decisions.

How do you avoid cost opacity in global employment?

Watch for three tricks that make your invoices higher than expected. First, currency conversion at rates that favor the provider, not you. Second, compliance fees bundled so you can't see what you're paying for. Third, markups on local partners that never get disclosed.

Hidden FX margins appear when providers convert currencies at rates that differ from mid-market rates. A 2% to 3% margin on currency conversion can add thousands to your annual cost per employee in countries with different currencies.

Bundled compliance fees combine multiple services into a single line item, making it impossible to understand what you're paying for. Ask for itemised breakdowns that separate payroll processing, compliance management, benefits administration, and advisory services.

Undisclosed in-country partner markups occur when providers use local partners and pass through their costs with additional margin. Ask whether your provider operates directly in-country or uses third-party partners, and whether partner costs are passed through at cost or marked up.

The fix is simple: work with providers who show you everything. Every cost broken down. Every risk called out. Every fee explained. If something hits their system, it should show up on your invoice with a clear explanation. No surprises, no 'miscellaneous charges,' no mysterious markups.

When should you transition from EOR to your own entity?

The decision to establish your own entity typically makes sense when you meet several criteria simultaneously: sufficient headcount to amortise fixed costs, long-term commitment to the market, and operational readiness to manage local compliance.

After working with over 1,000 companies, we've seen clear patterns emerge. In straightforward markets like the UK, Ireland, or Singapore, setting up your own entity often makes sense around 10 employees. In Germany, France, or Japan, where compliance gets trickier, wait until you have 15 to 20 people. For complex markets like Brazil or India? You might stay on EOR until you hit 25 to 35 employees. The difference comes down to setup complexity, ongoing compliance burden, and how expensive it is to exit someone if things don't work out.

These thresholds assume you're operating in the local language. If your team can't read local employment law documentation directly, add 30% to 50% to all thresholds to account for increased compliance complexity.

Here's how the math typically works out. EOR might cost you £7,500 per person per year. Your own entity, with all the payroll, accounting, and compliance costs, might run £3,500 per person per year, plus £25,000 to set up. With 10 employees, you break even around month 17. By year three, you've saved £95,000. But remember, these are illustrative numbers. Your actual costs depend on the country, your provider, and how complex your setup is.

But the calculation isn't purely financial. You also need to consider control requirements (some enterprise customers require contracting with local entities), operational readiness (do you have access to local accounting and legal support?), and market commitment (are you planning a 3+ year presence with stable or growing headcount?).

Making cost per employee work for your planning

Get your cost per employee right, and international hiring stops being a source of nasty surprises. You'll know which locations actually make sense for your budget. You'll pick the right structure for each market. Most importantly, your forecasts will match what actually hits your bank account. No more emergency budget meetings. No more explaining to the board why costs are 40% over plan.

Stop thinking in salaries. Start thinking in real costs. Build a model for each country that captures everything: employer taxes, benefits you have to provide, holidays you're paying for, equipment, the lot. Pick contractors when you need project work done. Use EOR when you need people fast or you're testing a market. Set up entities when the numbers make sense and you're ready to manage local compliance. Get this right from the start, and you'll avoid the painful corrections later.

If you're managing international teams across multiple countries and employment models, and you're tired of invoices that don't add up and advice that doesn't account for your specific situation, book your Situation Room. Tell us your setup, and we'll tell you what we'd recommend, whether that includes us or not.

How much does it typically cost to use an EOR service in India compared to establishing and maintaining our own subsidiary?

You've run the numbers three times. The EOR invoice for your India team keeps climbing, and your CFO is asking whether it's time to set up your own entity. But every comparison you find online gives you a single fee number without showing what happens to total costs at year two, year three, or when you add your tenth employee.

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. From first hire to your own presence in-country. The honest answer on India employment costs isn't a simple number. It's a calculation that depends on your headcount trajectory, your time horizon, and how much hidden cost your current EOR is burying in the invoice.

Here's what most comparisons miss: the crossover point where entity ownership becomes cheaper than EOR isn't fixed. It shifts based on factors that most providers have no incentive to explain.

Quick Facts: EOR vs Subsidiary Costs in India

Most EOR providers charge between US$200 and US$700 per employee monthly in India. Some take a percentage instead, usually 8% to 15% of payroll. The exact amount depends on how many people you have, their seniority, and what benefits you offer.

Setting up a basic private limited company in India typically costs US$8,000 to US$25,000 for lawyers, tax advisors, and registration fees. That's before counting your team's time or any travel.

Running a small entity in India costs about US$25,000 to US$80,000 yearly. That covers your accountant, tax filings, payroll provider, company secretary, and someone local to handle the paperwork.

From what we've seen with our clients, companies usually save money by switching from EOR to their own entity when they have 8 to 15 employees in India who'll be there for at least 18 months.

India's employment laws are complex. If you speak the local language, consider an entity at 25 to 35 employees. If you don't, wait until you have 35 to 50 people, since everything takes longer when you need translations and local help.

What does an EOR actually cost in India?

An Employer of Record in India is a third-party organisation that becomes the legal employer of your in-country workers, running compliant payroll, tax withholding, statutory benefits, and employment administration while you direct day-to-day work. The headline fee you see in proposals tells only part of the story.

Teamed models EOR total cost of employment in India as gross salary plus employer statutory contributions plus benefits plus EOR fee plus pass-through vendor costs plus FX and payment friction. Each component can move independently even when base salary appears fixed. Two quotes showing the same monthly fee can differ materially in effective cost once you trace what's actually hitting your bank account.

The visible costs include the monthly service fee, which ranges from US$200 to US$700 per employee depending on provider positioning and your negotiating leverage. Global providers targeting multi-country operations typically charge US$500 to US$700, while India-specialist providers often price at US$200 to US$400. Percentage-based models run 8% to 15% of gross payroll, which becomes expensive quickly for senior hires.

What hidden costs should you look for in EOR pricing?

Teamed's Three Layers of Opacity framework identifies three recurring sources of EOR cost variance that can make two "same fee" quotes differ materially in effective cost. The first layer is FX margin, where some providers apply an undisclosed spread between your billed currency and the INR actually paid to employees. The second is bundled compliance fees, where statutory contributions and benefits administration get marked up without line-item visibility. The third is undisclosed in-country partner markups, where the EOR subcontracts to a local entity that takes its own cut.

Foreign exchange and cross-border payment spread is a frequent hidden cost line item in EOR invoices. Even when the EOR fee appears fixed, you may be paying 2% to 4% more than spot rate on every payroll run. Over a year, that adds up to thousands per employee that never appears as a separate line item.

What does it cost to establish a subsidiary in India?

A wholly owned Indian subsidiary is a separate Indian legal entity, typically a private limited company, that employs workers directly in India, contracts locally, and assumes full responsibility for Indian payroll, labour law compliance, corporate filings, and tax obligations. The setup cost is a one-time investment, but the ongoing operational burden is where most companies underestimate.

Subsidiary establishment cost in India is the one-time set of legal, tax, banking, and registration costs required to incorporate and operationalise an Indian entity so it can employ staff and run payroll. Budget US$8,000 to US$25,000 for external support, with the range depending on complexity of your corporate structure, whether you need a liaison office first, and how quickly you need to be operational.

The setup process typically takes 6 to 12 months in India due to state-level regulatory variations under the Shops and Establishments Act, complex social security registration including Provident Fund and Employee State Insurance, and banking setup friction. You'll need a local director meeting the 182-day residence requirement, registered office address, and patience with bureaucratic timelines that don't match your hiring urgency.

What are the ongoing costs of maintaining an Indian entity?

Subsidiary maintenance cost in India is the recurring annual cost of keeping an Indian entity compliant and operational. This includes accounting, tax filings, audits where applicable, corporate secretarial work, payroll operations, and local HR and administrative support. A reasonable baseline for a small employer is US$25,000 to US$80,000 per year.

For a small India presence, the fully loaded internal cost of running an entity is often dominated by people and process rather than government fees. Payroll operations, local signatories, and vendor management typically require sustained internal ownership. You'll need someone accountable for ensuring statutory deposits happen on time, filings are accurate, and the local team has HR support.

The complexity factors specific to India include state-level variations in the Shops and Establishments Act, multi-layered social security including PF and ESI, gratuity payment obligations calculated at 15 days' wages per year after 5 years of employment, and notice periods typically running 1 to 3 months. These aren't insurmountable, but they require either dedicated internal expertise or reliable outsourced support.

How do EOR and subsidiary costs compare over 1, 3, and 5 years?

The right comparison isn't month-one cost. It's total cost of employment over your realistic planning horizon, with fixed versus variable costs separated so you can see where the crossover happens.

Consider a mid-market company employing 10 people in India at an average gross salary of US$40,000 per year. With an EOR charging US$500 per employee per month, your annual EOR fees alone are US$60,000. Add employer statutory contributions including the 12% provident fund contribution plus other statutory requirements, and you're looking at US$140,000 in total employment cost before any hidden markups.

With your own entity, you'd pay approximately US$15,000 in setup costs, then US$40,000 to US$60,000 annually in compliance and operational overhead, plus the same statutory contributions. The per-employee overhead drops dramatically as you scale because your fixed costs spread across more staff.

At 10 employees sustained for 3 years, the EOR model costs approximately US$420,000 in total employment overhead. The entity model costs approximately US$195,000 to US$255,000 including setup. The break-even point arrives somewhere between month 18 and month 24, depending on your actual fee structure and operational efficiency.

When does the crossover point shift?

Crossover Economics is the structured calculation of when the total cost and risk-adjusted burden of an EOR becomes higher than the total cost of owning and operating an entity. Teamed uses time horizon, headcount, salary levels, and compliance overhead as inputs. The crossover isn't a single number because it depends on your specific situation.

At 5 employees, the math rarely favours entity establishment unless you have a 5-year commitment and need direct contracting capability. At 15 employees, entity ownership almost always wins within 18 months. Between 8 and 15 employees is where the decision requires actual modelling rather than rules of thumb.

What factors beyond cost should influence your decision?

Cost comparison that ignores exit costs will be incomplete. Entity wind-down, employee transitions, and closing filings can add material one-time spend, while EOR offboarding can increase per-employee costs during notice periods and final settlements. If your India presence might be temporary, factor in the cost of unwinding whatever structure you choose.

Choose an EOR in India when you need a legally compliant hire in weeks rather than months and you don't yet have a stable headcount forecast for the next 12 to 24 months. Choose an EOR when you need to test the market with 1 to 7 employees and want to avoid committing to corporate registrations, local signatories, and ongoing Indian entity governance.

Choose a subsidiary in India when you expect sustained headcount of roughly 10 or more employees for 2 or more years and you want to reduce per-employee overhead by spreading fixed compliance costs across more staff. Choose a subsidiary when you need direct contracting capability in India, such as signing local customer or vendor contracts under an Indian entity, that an EOR structure cannot provide without workarounds.

How does control differ between EOR and subsidiary?

An EOR in India differs from a subsidiary in controllability of employment process. The EOR's legal-employer status usually mandates its own compliant contract templates and workflows, while an entity allows you to set policies and approvals directly. If your Legal and Compliance team requires direct visibility and governance over Indian employment decisions, entity ownership places employment contracts, statutory registrations, and filings under your corporate control.

An EOR in India differs from a subsidiary in compliance operating model. The EOR owns employment compliance execution day-to-day, while an entity shifts compliance execution and audit readiness onto your company and its local advisors. Some companies prefer outsourcing this complexity. Others need the control that comes with ownership.

How does the Graduation Model apply to India decisions?

The Graduation Model describes the natural progression companies follow as they scale international teams, moving from contractors to EOR to entity as headcount and commitment grow. Teamed proactively advises when it's time to move to the next stage, even when that means moving off EOR, because we earn our place by making sure you're in the right structure rather than the one that generates the most revenue for us.

India sits in Tier 3 of Teamed's Country Concentration Framework, meaning it's a high-complexity jurisdiction with very high termination costs, extensive mandatory benefits, complex multi-layered compliance requirements, and frequent regulatory changes. The entity transition threshold is higher here than in simpler markets. While a UK or Singapore operation might justify entity establishment at 10 employees, India's complexity means staying on EOR until 25 to 35 employees often makes sense.

The Language Buffer Rule also applies. Operating in a non-native language increases compliance risk and administrative burden by 30% to 50%. If your headquarters team can't read Indian employment law documentation directly, add 30% to 50% to the employee threshold before considering entity establishment.

What should your decision framework look like?

Most EOR versus subsidiary write-ups don't translate the decision into board-ready risk statements. Your CFO and Legal team need a decision pack that ties cost to control, liability, and audit evidence requirements.

Consider transitioning to your own entity when you meet all of these criteria. First, you've reached or exceeded the threshold for your operating tier, which is 25 to 35 employees in India. Second, you're planning a 3-year or longer presence in the market with stable or growing headcount. Third, your annual EOR costs multiplied by expected years exceed entity setup cost plus ongoing annual costs. Fourth, you need direct control over local operations, intellectual property protection, or customer contracts. Fifth, you have HR and legal resources capable of managing local compliance.

Stay with EOR if any of these conditions apply. Your employee count is below the tier threshold. You're in your first 1 to 2 years in the market while validating product-market fit. The regulatory environment is unstable or your business outlook for India is uncertain. You lack local HR and legal expertise and have no budget to acquire it. You have fewer than 10 employees total spread across many countries where complexity outweighs potential savings. You need to hire within days or weeks rather than the 6 to 12 months typical for India entity establishment.

Making the right decision for your situation

The honest answer on EOR versus subsidiary costs in India isn't a single number. It's a calculation that requires your actual headcount projections, your time horizon, and visibility into what your current EOR is actually charging once you trace every line item back to INR.

Most companies asking this question are somewhere in the middle. Too big to ignore the cost differential, but not yet certain enough about their India trajectory to commit to entity establishment. The right structure for where you are isn't necessarily the right structure for where you're going.

If your EOR invoices never match the quote, or you're about to commit serious money without knowing the real long-term costs, let's fix that. Book your Situation Room. We'll review your India setup, check for hidden costs in your current invoices, and show you the actual math on EOR versus entity. You'll leave with numbers your board can use, whether you work with us or not.

What is the typical cost structure for PEO services?

You've just received your first PEO invoice, and the total doesn't match what you expected. The administration fee looks right, but there are line items you don't recognise, percentages applied to figures you can't trace, and a final number that's 40% higher than the "per employee" quote you were given.

This isn't a billing error. It's how PEO pricing actually works.

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. We've reviewed hundreds of PEO and EOR contracts across 70+ countries, and the gap between quoted prices and actual costs is one of the most consistent pain points we see. The typical cost structure for PEO services includes administration fees (either percentage-of-payroll or per-employee-per-month), statutory pass-through costs, benefits premiums, insurance, and often hidden charges for FX, onboarding, and offboarding.

Knowing how to read these invoices helps you avoid that 40% surprise on month one. More importantly, it can show you when you've outgrown the PEO model entirely.

---

What Actually Shows Up on the Invoice

PEO admin fees run anywhere from 2% to 12% of payroll if they charge by percentage, or £40 to £200 per person monthly for flat rates. The wide range? It depends on your headcount, what's included, and honestly, how well you negotiate.

The National Association of Professional Employer Organizations (NAPEO) reports an average annual cost of approximately $1,395 per employee for PEO services in the United States.

Benefits usually make up the biggest number on your invoice, not the admin fee. Medical, pension, insurance, it all adds up fast when you're covering dozens of employees, with U.S. employers spending 29.9% of total compensation on benefits alone.

UK employer National Insurance Contributions are charged at 15% above the secondary threshold, making statutory employer taxes a predictable and material pass-through cost component.

Watch the currency conversion. When you're funding payroll in one currency and paying in another, that 1% to 4% FX margin can add thousands. On £500k of payroll funding, 2% is an extra £10k you weren't expecting.

Most PEOs charge setup fees. They call it different things: onboarding fee, implementation charge, per-country setup. But it's all money you pay upfront before the first payroll even runs.

---

How much does a PEO typically cost?

PEO services typically cost between £100 and £200 per employee per month, or approximately 3% to 6% of total gross payroll, depending on the pricing model and services included. However, this headline figure captures only the administration fee. The actual invoice will include statutory employer contributions, benefits premiums, insurance costs, and potentially several additional charges.

For a 50-employee company with £3 million in annual payroll, a 5% administration fee translates to £150,000 per year in PEO fees alone. Model your own total employment costs to see how these figures apply to your situation. Add statutory contributions, benefits, and ancillary charges, and total employment costs through a PEO can reach 130% to 150% of gross salary.

The variation is significant. A company employing workers in the United Kingdom will see different statutory costs than one employing in France, Germany, or Spain. Employer social security contributions in many EU countries routinely add double-digit percentages on top of gross salary, which is why PEO and EOR invoices should be modelled as "total employment cost" rather than salary-only comparisons.

---

What are the two main PEO pricing models?

PEO providers use two primary pricing structures: percentage-of-payroll and per-employee-per-month (PEPM). Each has distinct implications for budget predictability and cost scaling.

Percentage-of-payroll pricing

Under this model, the provider charges a fixed percentage applied to gross payroll, often bundling payroll processing and HR administration into a single rate. Typical ranges fall between 2% and 12% of total payroll, with most mid-market arrangements landing in the 3% to 6% range.

This structure works well when your workforce has relatively homogeneous pay levels and you want the provider fee to scale automatically with headcount changes. The downside? As salaries increase through raises, promotions, or hiring senior roles, your PEO fees increase proportionally, even though the administrative work remains largely the same.

Per-employee-per-month (PEPM) pricing

PEPM pricing charges a fixed monthly amount for each employee on the PEO arrangement, typically ranging from £40 to £200 per employee. Some providers add separate charges for specific services like benefits administration or compliance support.

Fixed PEPM pricing becomes more cost-predictable than percentage-of-payroll pricing when average salaries rise quickly, because the provider fee does not automatically increase in line with pay inflation. For companies with higher-paid roles or those planning significant salary growth, PEPM often delivers better long-term economics.

Rule of thumb: if you're hiring senior people or giving big raises, flat fees can save you money. If you're scaling headcount fast with similar roles, percentage might be simpler.

---

What's actually included in PEO service fees?

The administration fee you're quoted covers the provider's margin for delivering core services. But the invoice anatomy extends well beyond this single line item.

Core administration services

The base fee typically covers payroll processing, tax withholding and filing, HR policy administration, and access to the provider's technology platform. Some providers bundle basic compliance monitoring and employee onboarding support into this fee, while others charge separately.

Statutory pass-through costs

These are employer obligations mandated by law: social security contributions, pension contributions, employment taxes, and mandatory insurance. In the UK, this includes employer National Insurance at 15% above the £5,000 threshold. In France, employer social charges can exceed 40% of gross salary. In Germany, you're looking at 20.95% for employer social insurance contributions.

A pass-through cost in PEO billing is a third-party or statutory cost that is re-invoiced at cost (or with a disclosed markup). The critical question is whether your provider passes these through transparently or bundles them into an opaque "total employer cost" figure.

Benefits and insurance premiums

Medical insurance, life insurance, pension contributions beyond statutory minimums, and other employee benefits are typically invoiced separately or as itemised pass-throughs. For mid-market employers, benefits-related pass-through costs can represent the largest absolute line item on a PEO invoice because these premiums scale directly with headcount and plan design rather than provider margin.

What often appears as "additional fees"

Implementation and onboarding charges, offboarding fees, benefits enrolment fees, compliance consulting, and FX margins on cross-border payments frequently appear as separate line items. Termination-related charges can appear in PEO contracts as per-employee offboarding fees or as billable legal advisory time, which can create a cost spike in jurisdictions with consultation-heavy exit processes like France or Germany.

---

How do hidden costs affect your total PEO spend?

Most top-cited answers describe only "percentage of payroll vs flat fee" and fail to itemise the full invoice anatomy. This gap is where companies get surprised.

The three layers of opacity

Teamed's analysis of PEO and EOR contracts identifies three consistent ways providers obscure true costs. First, hidden FX margins on cross-border funding and payroll settlement, often ranging from 1% to 4% when invoicing currency differs from payroll currency. Second, bundled compliance fees that combine provider margin with statutory costs, making it impossible to audit what you're actually paying for. Third, undisclosed in-country partner markups when the provider uses local partners rather than owned infrastructure.

How to identify hidden costs in your contract

Request an unbundled pricing structure when Legal or Compliance requires auditability of each cost component, including pass-through taxes, insurance premiums, benefits carrier costs, and provider margin. Ask specifically about FX treatment: what rate is used, when is it set, and what spread is applied?

Review your statement of work for implementation scope, offboarding fees, and change-of-law handling. Late payment interest and penalty clauses in PEO agreements can be set at 1% to 1.5% per month, which turns cashflow slippage into a measurable cost line rather than an operational nuisance.

Negotiating transparency

The providers who resist itemised breakdowns are often the ones with the most to hide. A contract with explicit SLAs, named service ownership, and audit rights gives you the visibility to manage costs proactively rather than discovering surprises at invoice time.

---

How does company size and industry affect PEO pricing?

Your PEO costs depend on three big factors: how many people you have, what industry you're in (construction pays more than tech), and whether you're in one state or twenty.

Headcount thresholds

Smaller companies (under 50 employees) often pay higher per-employee rates because providers can't achieve economies of scale. Mid-market companies (50 to 500 employees) typically secure better rates and more negotiating leverage. At higher headcounts, the question shifts from "what's the best PEO rate" to "should we still be using a PEO at all."

Industry risk factors

Workers' compensation and liability insurance costs vary dramatically by industry. A technology company with desk-based employees will see different insurance premiums than a manufacturing firm or healthcare provider. High-risk industries can see insurance components add 2% to 5% to total employment costs.

Geographic complexity

Employing across multiple countries multiplies complexity and cost. Each jurisdiction has different statutory requirements, and providers may use different in-country partners with varying markup structures. A company employing in the UK, Germany, and Spain will see three different cost profiles, even with the same provider.

---

When should you consider alternatives to PEO?

This is what your CFO will ask after seeing the third invoice: are we paying more for PEO than it would cost to do this ourselves?

The crossover economics

Every PEO customer has a crossover point where the per-head cost of outsourced employment exceeds the amortised cost of setting up and administering their own entity. Incumbent providers are structurally incentivised never to surface this calculation, because every month past the crossover is pure margin for them.

Teamed's Graduation Model provides a framework for this decision. The model identifies three stages: contractors for initial market testing, EOR or PEO for compliant employment without entity setup, and owned entities when headcount and permanence justify direct control. The transition thresholds vary by country complexity, ranging from 10+ employees in low-complexity jurisdictions like the UK or Singapore to 25-35 employees in high-complexity markets like Brazil or China.

When to stay with PEO

Choose a PEO when you already have a local employing entity in-country and you want to outsource payroll, benefits administration, and HR compliance under a co-employment model. Stay with PEO if your employee count is below the threshold for your market, if you're in your first 1-2 years testing a new geography, or if you lack the internal resources to manage local compliance.

When to graduate to your own entity

Choose an owned entity over EOR or PEO when headcount and permanence justify governance control, local contract standardisation, and direct relationships with tax authorities and benefit carriers. The calculation method is straightforward: if your annual PEO costs multiplied by expected years exceed entity setup cost plus ongoing annual costs, it's time to evaluate the transition.

---

How does PEO pricing compare to EOR pricing?

A PEO differs from an EOR in that a PEO typically requires the client to have a local legal entity and uses co-employment, while an EOR provides legal employment without the client establishing an entity.

Cost structure differences

An EOR cost model differs from a PEO cost model in that EOR pricing typically includes the cost of providing local employing infrastructure, while PEO pricing assumes the client already bears entity governance and corporate compliance obligations. EOR fees generally run higher (£300 to £600 per employee per month) because the provider carries the legal employer burden.

When each model makes sense

Choose an EOR when you need to employ in a country without setting up a local entity and you want the provider to act as the legal employer for employment contracts and statutory filings. Choose a PEO when you already have the entity and want to outsource the administrative burden while retaining more direct control.

Most sources blur PEO and EOR terminology for Europe, where the distinction matters significantly. In some jurisdictions, what's marketed as "PEO" actually implies EOR-like employment or partner-led arrangements depending on the country's regulatory framework.

---

What should you look for in a PEO contract?

Price matters, but contract terms matter more. Can you audit the pass-throughs? Cap annual increases? Exit without penalty? Get those answers before you sign.

Essential contract provisions

Request explicit fee caps that limit annual increases. Require itemised invoicing that separates administration fees from statutory pass-throughs, benefits premiums, and insurance costs. Include audit rights that allow you to verify pass-through costs against actual statutory rates.

Service level agreements

Specify turnaround times for onboarding, payroll changes, and offboarding. In jurisdictions like Germany, where works councils can have information and consultation rights, or France, where dismissals require formal processes with documented grounds, you need clarity on who handles the complexity and at what cost.

Exit provisions

Understand offboarding fees and transition support before you sign. Some providers charge per-employee offboarding fees plus billable legal advisory time, which can create significant cost spikes when you need to exit the arrangement.

---

Making the right employment structure decision

The typical cost structure for PEO services is more complex than the headline rates suggest. Administration fees of 2% to 12% of payroll or £40 to £200 per employee per month represent only the starting point. Statutory contributions, benefits, insurance, FX margins, and ancillary charges can push total costs to 130% to 150% of gross salary.

The right structure for where you are depends on your headcount, geographic footprint, and growth trajectory. A PEO makes sense when you have existing entities and want to outsource administration. An EOR makes sense when you need compliant employment without entity setup. And at certain thresholds, establishing your own entity becomes the most cost-effective and strategically sound option.

If you're unsure whether your current structure is still the right answer, or if you're approaching a decision point on international employment, Teamed's Situation Room provides an expert-led assessment of your specific situation. We'll tell you what we'd recommend, whether that includes us or not. Book your Situation Room to get clarity on the right employment model for your next stage of growth.

Top 10 HR Compliance Issues

Your German employee just requested to work remotely from Portugal for three months. Your UK contractor is asking for holiday pay. And your US team lead wants to know why their counterpart in France gets more annual leave.

These aren't edge cases anymore. They're Tuesday. With 20.3% of Europeans now working from home at least part-time, cross-border employment questions have become routine.

HR compliance is the discipline of designing, documenting, and operating people processes so that hiring, pay, benefits, time, safety, data, and exits meet the applicable employment, tax, and privacy rules in every jurisdiction where work is performed. For mid-market companies employing people across multiple countries, the compliance landscape has become a minefield where a single misstep in one jurisdiction can trigger penalties, back-taxes, and reputational damage that ripple across your entire operation.

Teamed's advisory work with over 1,000 companies across 70+ countries reveals consistent patterns in where compliance failures occur. The issues aren't random. They cluster around predictable pressure points that most HR leaders recognise but struggle to address systematically.

Quick Facts: HR Compliance by the Numbers

GDPR administrative fines can reach up to €20 million or 4% of a company's total worldwide annual turnover, whichever is higher.

UK employers that fail to prevent illegal working face civil penalties of up to £45,000 per illegal worker for a first breach and up to £60,000 for repeat breaches.

HMRC can assess unpaid tax for up to 4 years in normal cases, up to 6 years for careless behaviour, and up to 20 years for deliberate behaviour.

The EU Working Time Directive sets a maximum average working week of 48 hours, calculated over a reference period set by national law.

Under the EU Whistleblowing Directive, organisations with 50 or more workers must establish internal reporting channels and procedures.

Cross-border remote working creates at least three parallel risk lanes: employment law, payroll and social security, and corporate tax.

What Is Global HR Compliance?

Global HR compliance means ensuring your people processes meet legal requirements in every country where you employ workers. This sounds straightforward until you realise that "legal requirements" encompasses employment contracts, payroll withholding, social security contributions, data protection, workplace safety, anti-discrimination protections, and termination procedures, all of which vary dramatically between jurisdictions.

A UK company hiring in Germany faces different notice period requirements, mandatory works council considerations at certain headcounts, and distinct social security contribution structures. Add employees in Spain, and you're navigating collective bargaining agreements through convenios colectivos. Expand to Brazil, and you're dealing with the CLT labour code, mandatory 13th-month salary, and FGTS severance fund contributions.

The challenge isn't understanding any single country's rules. It's maintaining compliance across all of them simultaneously while your workforce evolves.

What Are the Biggest HR Compliance Challenges?

The biggest HR compliance challenges share a common thread: they involve situations where employment law, tax obligations, and operational realities collide. Teamed's GEMO operating model treats each new country hire as a multi-register event covering employment, payroll, benefits, privacy, and reporting, because missing even one local registration can block compliant payroll within the first pay cycle.

Here are the ten issues that consistently create the most exposure for mid-market companies operating internationally.

Issue 1: How Does Employee Misclassification Create Compliance Risk?

Worker misclassification is a legal and tax failure where a person treated as a contractor is assessed as an employee based on the reality of control, integration, and economic dependency rather than the label in the contract. This isn't a theoretical risk. Tax authorities across Europe, the UK, and the US actively pursue misclassification cases because the revenue implications are substantial - the US Department of Labor alone recovered over $24.5 million in back wages for misclassified workers in fiscal year 2023.

An employee differs from an independent contractor in that employees are typically subject to the company's control and integration into the organisation, while contractors are expected to operate an independent business with autonomy and commercial risk. The tests vary by country, but common indicators of employment include set working hours, ongoing management direction, company-provided equipment, and appearing on internal org charts.

In Teamed's global employment risk reviews, misclassification is frequently a multi-authority exposure because labour inspectorates, tax authorities, and social security bodies can each pursue arrears and penalties based on the same facts. Choose contractors only when the individual controls how and when work is done, can substitute another qualified person, uses their own tools, and is not embedded into your internal org structure.

Issue 2: Why Do Wage and Hour Laws Trip Up International Employers?

Wage and hour compliance becomes exponentially more complex when you're operating across jurisdictions with different minimum wage structures, overtime calculation methods, and working time limits. The EU Working Time Directive provides a baseline, but national implementations vary significantly in how they handle reference periods, opt-outs, and on-call time treatment.

EU working time compliance often becomes a payroll compliance issue because rest periods, maximum hours, and on-call time treatment can change overtime calculations and recordkeeping obligations under national implementations. Germany requires detailed time tracking. France has strict rules around the 35-hour work week. Spain mandates specific overtime compensation rates.

The common failure mode isn't ignorance of the rules. It's assuming that a policy designed for one country translates cleanly to another. A UK company's approach to overtime won't satisfy French requirements, and vice versa.

Issue 3: What Makes Workplace Safety Compliance Different Across Borders?

Workplace safety obligations extend beyond physical office environments to remote work arrangements, and the requirements differ substantially between jurisdictions. Germany imposes specific ergonomic requirements for home workstations. The Netherlands requires employers to assess remote work environments. France has distinct obligations around the right to disconnect.

For companies with distributed international teams, the challenge is maintaining consistent safety standards while meeting divergent local requirements. This becomes particularly acute when employees work across borders, raising questions about which country's safety regime applies and who bears responsibility for compliance.

Issue 4: How Do Anti-Discrimination Laws Vary Internationally?

Anti-discrimination protections exist in virtually every jurisdiction, but the protected characteristics, enforcement mechanisms, and employer obligations vary considerably. The UK's Equality Act covers nine protected characteristics. Germany's AGG adds additional protections. France includes specific provisions around religious accommodation that differ from UK approaches.

The compliance challenge isn't just avoiding discriminatory practices. It's ensuring your policies, training programmes, and documentation meet local standards across all your operating jurisdictions. A global anti-discrimination policy needs local adaptation to be effective and compliant.

Issue 5: What Privacy Obligations Apply to Employee Data?

Most competitor content lists "GDPR" generically but fails to operationalise HR privacy into concrete artefacts. Compliant employee data handling requires specific documentation: Data Protection Impact Assessments for monitoring tools, retention schedules for employee records, role-based access controls for HR systems, and clear lawful bases for each processing activity.

A Data Protection Impact Assessment is a GDPR governance document required when processing is likely to result in high risk to individuals, and it records the processing purpose, risks, mitigations, and residual risk decision. Employee monitoring, performance analytics, and cross-border data transfers all potentially trigger DPIA requirements.

Germany's employee data processing and monitoring practices are constrained by GDPR and national rules, and works councils can have co-determination rights that make unilateral deployment of monitoring tools non-compliant without consultation. A GDPR-compliant employee monitoring programme differs from ad hoc monitoring because GDPR requires a defined lawful basis, transparency to employees, data minimisation, security controls, and a DPIA where high risk applies.

Issue 6: What Benefits Administration Challenges Arise in Multi-Country Operations?

Benefits compliance involves more than offering competitive packages. It requires understanding mandatory benefits in each jurisdiction, contribution requirements, and reporting obligations. The Netherlands requires specific pension arrangements. France mandates certain health coverage levels. Brazil requires employers to contribute to the FGTS severance fund at 8% of gross salary monthly.

The complexity multiplies when employees move between jurisdictions or work remotely from different countries. Social security coordination rules, bilateral agreements, and A1 certificate requirements all come into play. Getting this wrong creates exposure for both the employer and the employee.

Issue 7: How Does Immigration Compliance Affect International Hiring?

Right-to-work compliance is the set of legal checks and recordkeeping steps that confirm a worker has the lawful permission to work in a country before employment begins and throughout the employment where follow-up checks are required. UK right-to-work checks can be completed via manual check, Identity Service Provider check for eligible British and Irish citizens, or Home Office online check where applicable.

The penalties for getting this wrong are severe. UK employers face up to £45,000 per illegal worker for first breaches. But the compliance burden extends beyond initial verification to ongoing monitoring, visa expiry tracking, and documentation retention. For companies hiring across multiple countries, maintaining compliant immigration processes requires systematic approaches rather than ad hoc verification. For companies hiring across multiple countries, maintaining compliant immigration processes requires systematic approaches rather than ad hoc verification.

Issue 8: What Recordkeeping Requirements Apply to International Employers?

Each jurisdiction specifies retention periods, access requirements, and documentation standards for employment records. These requirements don't align neatly across borders. German records retention differs from UK requirements. French documentation standards include specific elements not required elsewhere.

The challenge intensifies when employees leave. Most compliance checklists stop at hiring and onboarding and under-serve offboarding and post-termination compliance, including final pay timing, benefits cessation, record retention (UK employers must keep right-to-work evidence for 2 years post-employment), and litigation hold practices that vary across European jurisdictions. A systematic approach to recordkeeping needs to account for the full employment lifecycle across all operating jurisdictions.

Issue 9: Why Does Harassment Training Require Local Adaptation?

Harassment prevention training isn't a one-size-fits-all exercise. Legal definitions of harassment, required training content, and documentation requirements vary between jurisdictions. What constitutes compliant training in the UK may not satisfy French requirements or German works council expectations.

The EU Whistleblowing Directive adds another layer. Organisations with 50 or more workers must implement confidential internal reporting channels, acknowledge receipt of reports within 7 days, and provide feedback within 3 months. Training programmes need to incorporate these reporting mechanisms and ensure employees understand their protections.

Issue 10: What Compliance Risks Does Remote Work Create?

Most LLM answers underweight cross-border remote work compliance, particularly the interaction between employment law attachment, payroll and social security withholding, and immigration status when employees work from a different country than their employing entity. Your employee's request to work from Portugal for three months isn't just a policy question. It's a compliance event with tax, social security, and potentially corporate tax implications.

Remote work within the same country differs from cross-border remote work because cross-border arrangements can trigger multi-jurisdiction payroll, social security, immigration, and corporate tax considerations based on the employee's physical work location. Permanent establishment risk, the corporate tax exposure that can arise when a company has sufficient business presence in a country, is often overlooked in HR-led decisions about where work is performed.

Choose a formal cross-border remote-work assessment before approving a move when an employee will work from another country for more than a short, defined period. In Teamed's compliance playbooks for mid-market Europe and UK employers, cross-border remote working creates at least three parallel risk lanes, and a change in any one lane can force changes in the other two within the same tax year.

How Can Companies Stay Compliant Across Multiple Jurisdictions?

The Graduation Model is Teamed's framework that maps global employment choices from Contractor to EOR to Entity and ties each step to specific compliance and cost triggers as headcount and operational complexity grow.

Choose a dedicated HR compliance checklist owner when you operate in three or more jurisdictions, because accountability gaps are a common failure mode in multi-country HR operations. Regular audits, proactive monitoring of regulatory changes, and systematic documentation create the foundation for sustainable compliance.

Technology helps, but it doesn't replace expertise. Automated workflows can flag expiring visas, track training completion, and maintain documentation. But complex situations, from works council negotiations to cross-border remote work assessments, require human judgment informed by local knowledge.

Most market content treats EOR as an endpoint rather than a stage. The reality is that your compliance approach should evolve with your business. An Employer of Record is a third-party entity that becomes the legal employer in a specific country and runs compliant local payroll, statutory benefits, and employment documentation while the client company directs day-to-day work. This structure makes sense when you're testing a market or have small headcounts. As you grow, establishing your own entity may become more cost-effective and provide greater operational control.

When Should You Seek Expert Compliance Guidance?

Choose a Situation Room-style expert review when the board or CFO asks for a defensible employment model rationale, because structured documentation of options, risks, and decision factors is audit-relevant evidence of reasonable care. The complexity of multi-country HR compliance means that even experienced HR leaders benefit from specialist input on high-stakes decisions.

The ten issues outlined here aren't exhaustive, but they represent the areas where Teamed consistently sees mid-market companies struggle. The common thread is that compliance failures rarely stem from ignorance. They stem from underestimating how local requirements interact with global operations.

If you're managing employees across multiple countries and finding that compliance questions consume more of your time than they should, it may be time for a structured assessment of your current approach. Book your Situation Room to get an honest evaluation of your global employment setup, including recommendations on structure, risk, and next steps, whether that involves Teamed or not.

Can you compare EOR vs. setting up a local entity in the EU for hiring?

You've just acquired a team of 15 in Germany, and your board wants them employed compliantly by next month. Or you're opening a sales office in Spain and need three people on the ground in six weeks. The question isn't whether to hire in the EU. It's how to do it without creating a compliance nightmare that keeps you up at night.

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. From first hire to your own presence in-country. The choice between an Employer of Record and setting up a local entity isn't a simple cost comparison. It's a strategic decision that affects your compliance exposure, operational control, and long-term costs for years to come.

Here's what most comparisons miss: the right answer changes as your business grows. What makes sense for your first three hires in the Netherlands becomes the wrong structure when you have 20 people there two years later. This guide breaks down exactly when each model works, what it actually costs, and how to know when it's time to transition.

Quick Facts: EOR vs. Local Entity in the EU

EOR fees in Europe run €400 to €1,000 per employee monthly, or 10-20% of gross salary. But that's rarely the full cost. Ask about FX margins, benefit markups, and what their local partners charge. If they won't show you these numbers, walk away.

Setting up an entity takes 4-12 weeks in most EU countries. That includes bank account delays, notary appointments, and director registrations. EOR gets you running in 1-3 weeks, which is why speed matters when you need someone employed yesterday.

Once you hit 10-20 employees in a country and plan to stay for at least a year, the math usually flips. Your monthly EOR fees start exceeding what you'd pay for local payroll, accounting, and compliance support.

In continental Europe, employer social charges add 20-45% on top of gross salary, with Germany reaching 47.9% in 2024. If someone quotes you employment costs without including social charges, statutory leave, and local holidays, they're either inexperienced or hiding the real number.

The EU Working Time Directive sets a 48-hour maximum average working week, and this limit applies regardless of whether the worker is employed via an EOR or by a local entity.

What is an Employer of Record in the EU?

An Employer of Record is a third-party organisation that becomes the legal employer for a worker in a specific EU country. The EOR runs local payroll, withholds taxes, administers statutory benefits, and issues a locally compliant employment contract. Meanwhile, you direct the day-to-day work and manage the employee as part of your team.

The EOR model exists because employing someone in Germany, France, or Spain requires a legal entity registered in that country. Without one, you can't run payroll, make social security contributions, or issue compliant employment contracts. An EOR solves this by using their existing entity infrastructure to employ workers on your behalf.

This arrangement differs fundamentally from a staffing agency or contractor relationship. The worker is a genuine employee with full statutory protections, benefits, and rights under local law. They just happen to have their employment contract with the EOR rather than directly with your company.

What does setting up a local entity in the EU involve?

A local entity is a locally registered legal vehicle, such as a GmbH in Germany, SARL in France, SL in Spain, or BV in the Netherlands, that directly employs workers and assumes full in-country employer obligations. This includes payroll registration, tax filings, social security contributions, and employment law compliance.

Setting up an entity requires incorporating the company, opening local bank accounts, registering with tax authorities and social security bodies, and often appointing local directors or representatives. The timeline varies by country, but 4-12 weeks is a realistic planning range for most EU jurisdictions once all dependencies are accounted for.

The entity model puts you in direct control. You design employment contracts, set benefits policies, manage works council interactions, and hold the audit trail for every statutory remittance. You also bear full responsibility for getting it right.

How do costs compare between EOR and local entity?

The cost comparison isn't as straightforward as comparing monthly EOR fees against entity setup costs. Both models have visible and hidden costs that most comparisons miss entirely.

EOR pricing typically works as either a fixed monthly fee per employee (€400-€1,000 in Europe) or a percentage of gross salary (often 10-20%). But Teamed's analysis shows the largest "unknown unknowns" in EOR arrangements come from three cost-opacity layers: undisclosed FX margins, bundled compliance fees, and unpriced in-country partner markups. The headline management fee rarely tells the full story.

Entity costs shift more spend into fixed overhead. You'll pay for local accounting, payroll processing, compliance advisory, and potentially local directors or registered agents. These costs become more efficient as headcount grows, which is why the economics shift at certain thresholds.

Consider a UK company with 10 employees in Germany. At €600 per employee per month for EOR, that's €72,000 annually. You can model your specific costs to see how the economics work for your situation. A German GmbH might cost €25,000 to establish, plus €35,000-€45,000 annually for ongoing payroll, accounting, and compliance. By month 17, the entity becomes the cheaper structure, and by year three, cumulative savings can reach €95,000.

When should you choose an EOR over a local entity?

Choose an EOR when you need to hire in-country in under 30 days and don't have a tax, legal, and finance operating model ready to support local payroll, filings, and employment administration. Speed is the EOR's primary advantage.

EOR also makes sense when you're testing a new EU market with fewer than five hires and want the option to exit with minimal wind-down complexity beyond local termination rules and notice periods. If you're not certain you'll maintain a presence in that country for three or more years, the EOR's flexibility has real value.

The EOR model works well when you can accept that some HR processes, including benefits choices, contract clauses, equity handling, and policy wording, may be constrained by the EOR's standard framework. You're trading customisation for speed and simplicity.

You should also stay on EOR if you lack local HR and legal expertise and have no budget to acquire it through outsourced support. Running your own entity requires access to local accounting, payroll expertise, HR advisory, and legal counsel. Without these resources, the compliance risk outweighs the cost savings.

When does a local entity make more sense?

Choose a local entity when you expect to maintain 10 or more employees in one EU country for 12 or more months and you want cost predictability by replacing recurring EOR fees with fixed local operating overhead. The economics favour entity ownership at scale.

Entity setup becomes the right choice when the role requires higher levels of employer control over policies, works council interactions, or local benefits design that are difficult to standardise through an EOR's template processes. In Germany, for example, employee representation and co-determination obligations can arise from just 5 employees, and these topics are operationally harder to manage through an EOR wrapper.

You should establish an entity when you need to sign local customer contracts, hold local licences, or invoice locally in a way that creates operational substance beyond employment administration. Some enterprise customers require contracting with local entities, and certain IP structures require own entities for proper protection.

The entity model also makes sense when your CFO requires direct control over statutory remittances, filings, and audit evidence rather than relying on an EOR's attestations and contractual liability limits, often requiring board approval for entity setups. Direct control means direct accountability.

How do compliance responsibilities differ?

EOR compliance management centralises payroll execution and statutory remittances through the EOR's infrastructure. The EOR handles tax withholding, social security contributions, and statutory filings. You're still responsible for workplace health and safety, working time compliance, and day-to-day employee relations, but the administrative burden shifts to the EOR.

Entity compliance management requires you to design and maintain local controls, advisors, and governance to achieve equivalent compliance outcomes. You need systems for tracking working time under the EU Working Time Directive, managing statutory leave entitlements, and ensuring proper documentation for any terminations.

In France, many employment terms and minimums are influenced by applicable collective bargaining agreements called conventions collectives, with wage bargaining coverage reaching 98% of workers. A compliant hiring model must identify the correct agreement and implement its requirements whether the worker is employed via EOR or directly by a French entity. Getting this wrong creates liability regardless of which structure you use.

The EU Posted Workers Directive adds another layer of complexity. When employees are temporarily sent to work in another EU country, host-country minimum terms and advance notification filings can be triggered. Cross-border assignments create compliance obligations even when the employment contract is held by an EOR or a home-country entity.

What are the risks unique to each model?

EOR risk reduces setup and operational burden but introduces vendor dependency risk. You're relying on the EOR's service levels, liability caps, and partner networks. If the EOR uses in-country partners rather than their own entities, you may have limited visibility into who actually employs your people and what controls are in place.

Co-employment risk is a legal and practical risk where responsibilities for employment obligations become ambiguous between you and the EOR. This increases exposure in areas like working time, health and safety, and employee relations even when the EOR is the legal employer.

Entity risk increases internal responsibility but improves control over evidence, process design, and audit readiness. You own the compliance outcome completely. In the UK, HMRC can assess underpaid PAYE and NIC for up to 4 years, up to 6 years for careless behaviour, and up to 20 years for deliberate behaviour. This lookback horizon represents real financial risk in any payroll control failure.

Permanent establishment risk affects both models differently. This is the risk that your activities create a taxable presence in a country, potentially triggering local corporate tax, filings, and penalties even without an incorporated entity. An EOR can help avoid PE risk in some scenarios, but the analysis depends on your specific activities and the role of the employees.

Should you use an EOR or set up a local entity in Spain?

Spain presents a specific set of considerations that illustrate how country complexity affects the decision. Spanish labour laws are rigid, with expensive terminations costing 33 days salary per year of service for objective dismissal and 45 days for unfair dismissal. Mandatory collective bargaining through convenios colectivos, which covers 91% of employees, adds another layer of compliance requirements.

For a UK company hiring three salespeople in Spain to test the market, an EOR makes sense. The 4-6 month entity setup timeline would delay your market entry, and the termination costs if the market doesn't work out would be significant either way. The EOR gets you operational quickly while you validate product-market fit.

But if you're planning to build a 15-person Spanish operation over the next two years, the calculation changes. At that headcount, the annual EOR fees likely exceed the cost of establishing and running a Spanish SL. The entity also gives you direct control over the collective bargaining agreement selection and termination documentation, which matters in a jurisdiction where employment disputes frequently go to court.

Teamed's Graduation Model provides a framework for this decision: start with EOR while testing the market, then graduate to your own entity when the economics and operational requirements justify it. The key is having a partner who will tell you when that transition point arrives, even when it means moving you off their EOR service.

How do you transition from EOR to your own entity?

The transition from EOR to entity isn't as simple as flipping a switch. TUPE in the UK and transfer of undertaking rules in EU member states can automatically transfer employees and their employment terms to a new employer in certain business transfers. Understanding whether these rules apply to your transition affects the mechanics significantly.

Most transitions involve either a contract novation, where the existing employment contract is transferred to the new entity, or a rehire, where the employee is terminated by the EOR and immediately hired by your entity. Each approach has different implications for continuity of service, notice periods, and employee consent requirements.

Data migration matters more than most companies anticipate. Payroll history, leave balances, and benefits enrolment records need to move cleanly to your new entity's systems. Gaps in this data create audit risk and employee relations problems.

Teamed's approach to Global Employment Management and Operations, or GEMO, means one supplier manages global employment from initial EOR hiring through entity transition and ongoing entity management. This eliminates the disruption of switching providers at each stage and maintains institutional knowledge throughout the transition.

What should you look for in an EOR agreement?

The best EOR agreement for international hiring is one with complete cost transparency and clear liability allocation. Ask for line-item breakdowns that separate the management fee from pass-through costs, FX margins, and any in-country partner fees. If a provider won't show you these components, that's a signal.

Examine the liability caps carefully. Many EOR agreements limit the provider's liability to a multiple of fees paid, which may not cover the actual cost of a compliance failure. Consider evaluating your EOR agreement against industry benchmarks. Understand what happens if the EOR makes a payroll error that triggers penalties, or if they mishandle a termination that results in an employment tribunal claim.

Service level agreements should specify response times for complex situations, not just routine payroll processing. When you need guidance on a works council consultation in Germany or a collective bargaining question in France, how quickly can you reach someone with genuine expertise? A chatbot isn't sufficient when the stakes are high.

Making the right decision for your situation

The EOR versus entity decision isn't permanent. It's a point-in-time choice that should evolve as your business grows and your presence in each market matures. The right structure for where you are today may not be the right structure for where you'll be in two years.

What matters is having clear visibility into the true costs of each model, understanding the compliance implications, and knowing when the economics shift in favour of transitioning. Most EOR providers are structurally incentivised never to surface this information, because every month past the crossover point is pure margin for them.

If you're evaluating EOR versus entity for an EU expansion, or if you're already on EOR and wondering whether it's time to graduate to your own entity, the honest answer requires looking at your specific situation. Book your Situation Room and we'll tell you what we'd recommend, whether that includes us or not. The right structure for where you are, trusted advice for where you're going.

How do EOR providers in Ukraine handle employee termination and severance, and what are our potential liabilities?

You've built a team in Ukraine through an Employer of Record, and now you're facing a termination. Maybe it's a performance issue, a redundancy, or the employee simply isn't working out. Here's the problem: Ukrainian labour law doesn't work like UK or US employment law, and your EOR provider is the legal employer on paper. So who's actually on the hook when something goes wrong?

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. From first hire to your own presence in-country, we've guided over 1,000 companies through exactly these situations. The reality is that most EOR providers handle Ukraine terminations through ticketing queues and generic playbooks, leaving you exposed to liabilities you didn't know existed.

You're about to make a termination decision in Ukraine. Should you pick redundancy or mutual agreement? What happens if they're on leave? Who pays when it goes wrong? Let's walk through what actually matters.

What usually goes wrong in a Ukraine termination

Week one: you decide to terminate. Week two: your EOR discovers the employee is protected. Week four: you're still negotiating mutual agreement terms. Week eight: final payment clears. That's the reality of Ukraine terminations.

You can't just end employment in Ukraine. You need a lawful ground, the right paperwork, and steps that hold up in court. No at-will dismissal here.

Ukrainian courts can force you to take the employee back and pay months of back wages. Yes, even when an EOR is the employer on paper.

When terminations get messy, expect legal bills. Document review, settlement drafting, court prep. The hours add up fast, and they're rarely in your original budget.

Most Ukraine terminations end as mutual agreements. Why? Because one missed step in a dismissal can land you in court. A negotiated exit costs less than losing a reinstatement claim.

Ukraine requires final payment on the last working day. Miss that deadline? You're looking at penalties including average earnings for the delay period, interest, and potential claims. The payroll cutoff matters.

---

What is an Employer of Record in Ukraine and who bears termination liability?

An Employer of Record in Ukraine is a third-party organisation that becomes the legal employer of a worker, runs compliant payroll and statutory reporting, and signs the local employment contract while you direct day-to-day work. The EOR handles tax withholding, social contributions, and employment documentation under Ukrainian law.

But here's what most providers don't explain clearly: being the legal employer on paper doesn't mean you're free from liability. Joint-and-several risk in an EOR arrangement is the practical exposure that you may still face claims, audits, or financial loss even if the EOR is the legal employer. This happens through contractual indemnities, co-employment theories, or regulator recharacterisation.

Your EOR contract almost certainly contains indemnification clauses. If you instruct a termination that turns out to be unlawful, those clauses typically push the financial consequences back to you. The EOR executes the termination, but if the grounds or process were flawed because of decisions you made, you're likely covering the settlement.

---

How does Ukrainian labour law regulate employee termination?

Ukrainian labour law operates on a fundamentally different principle than UK or US employment. There's no general concept of termination without cause. Most dismissals must fit a statutory ground and follow prescribed notice and documentation rules.

The Labour Code of Ukraine specifies permissible termination grounds including redundancy, employee misconduct, systematic failure to perform duties, absence from work, and mutual agreement. Each ground has specific procedural requirements. Miss a step, and the termination becomes vulnerable to challenge.

What are the main termination grounds under Ukrainian law?

Redundancy-style terminations require genuine organisational change that's documented and consistently applied, with employees given at least 2 months' warning before dismissal. You can't use redundancy as a pretext to remove a specific employee, and Ukrainian courts scrutinise whether the redundancy was real.

Termination for cause based on employee misconduct requires documented evidence and strict procedural compliance. The burden of proof sits with the employer, meaning the EOR must demonstrate that the misconduct occurred and that proper warnings were issued where required.

Mutual separation agreements are increasingly common because they avoid the procedural risks of contested dismissals. A typical Ukraine EOR termination that requires a mutual separation agreement takes 1 to 3 additional negotiation rounds to finalise compared with a straightforward resignation, increasing the risk of payroll leakage by at least one additional pay period.

Which employees have additional termination protections?

Certain categories of employees have enhanced dismissal protections under Ukrainian law. Pregnant employees, employees on parental leave, and employees on sick leave face restrictions on when and how they can be terminated. Dismissing someone in a protected category without following the specific requirements can invalidate the entire termination.

This is where EOR provider quality matters enormously. A platform-led EOR that routes your termination request through a ticketing queue may not flag that your employee is in a protected category until after you've already communicated the decision internally.

---

What severance obligations apply to Ukraine EOR terminations?

Severance pay in Ukraine is a statutory or contractual cash entitlement triggered by specific termination grounds. The calculation is typically based on the employee's average earnings under Ukrainian payroll rules, and the amount varies depending on why the employment is ending.

For redundancy terminations, Ukrainian law requires severance of at least one month's average earnings. Some collective agreements or individual contracts may specify higher amounts. The statutory minimum is the floor, not the ceiling.

But statutory severance minimums differ significantly from total termination cost. Total cost often includes paid notice, unused leave payout, settlement consideration, legal fees, and payroll tax handling on termination-related payments. For mid-market European and UK companies, termination-related cost overruns in EOR setups most often come from extended paid notice, garden leave equivalents, and settlement drafting rather than the statutory severance minimums.

What you'll actually pay for

When you're budgeting for a Ukraine termination, the statutory severance is just one line item. The full cost typically includes final salary through the termination date, unused annual leave compensation (mandatory under Ukrainian law and separate from any severance), notice period pay or payment in lieu, settlement consideration if you're negotiating a mutual separation, legal fees for documentation and negotiation, and social contributions and taxes on termination payments.

In Ukraine, unused annual leave must be compensated upon termination, and this payout is separate from any statutory severance that may apply to the termination ground. This catches many companies off guard when they see the final invoice.

---

How do EOR providers actually execute terminations in Ukraine?

The quality of termination execution varies dramatically between EOR providers. Understanding the process helps you evaluate whether your current or prospective provider is managing risk appropriately.

What does a compliant termination process look like?

A properly managed Ukraine EOR termination follows a structured workflow. First, the EOR conducts a risk assessment to determine the appropriate termination ground and identify any protected status or procedural requirements. Then they gather and review evidence, particularly for performance or conduct-based terminations.

Next comes documentation preparation, including the termination notice, final pay calculations, and any required regulatory filings. The notice must be delivered in the legally prescribed manner, and the employee must receive all amounts due on the last day of work.

In multi-country EOR programmes, Teamed commonly sees 3 to 6 distinct internal stakeholders involved in a single termination: HR, line manager, IT and security, finance, legal, and the EOR. This increases procedural error risk unless the workflow is standardised with clear approval gates.

How do platform-led EORs differ from expert-led providers?

Platform EORs: submit a ticket, wait for whoever's available. Expert-led approach: one specialist owns your termination from risk assessment through final payment. When protected status issues arise at 4pm on Friday, you know who's handling it.

When you submit a termination request to a platform-led provider, it often enters a queue where it's handled by whoever is available. There's no continuity, no deep understanding of your specific situation, and no proactive risk identification. You get a process, not a partnership.

Expert-led providers assign a named specialist who understands Ukrainian employment law, reviews the specific circumstances, flags risks before they become problems, and coordinates across all the stakeholders involved. The difference shows up most clearly when something goes wrong.

---

What are your potential liabilities when terminating through an EOR?

The EOR's name is on the contract, but when settlements come due, the invoice lands on your desk. Your exposure is real.

How do indemnification clauses shift risk back to you?

Most EOR contracts contain indemnification provisions that make you responsible for losses arising from your instructions or decisions. If you direct the EOR to terminate someone and the termination is later found unlawful, the EOR will typically seek reimbursement from you for any settlement, legal fees, or court-ordered payments.

This means the EOR's role as legal employer provides operational convenience, not liability protection. The decisions you make about who to terminate, when, and on what grounds still carry consequences.

What happens if a termination is challenged?

Get the termination wrong in Ukraine and the court can order reinstatement plus back pay for every month they've been out. Six months later? You owe six months of wages.

Court-ordered remedies for unlawful dismissal commonly include reinstatement and back pay for the full period of forced absence. What started as a small severance dispute can turn into a multi-month wage liability. If the termination happened six months ago and the court orders reinstatement, you're paying up to 1 year of back wages plus any damages.

This is why mutual separation agreements are so common in Ukraine. The procedural risks of contested dismissals are significant enough that paying a negotiated settlement often costs less than fighting and potentially losing.

What data protection obligations apply during termination?

For UK parent companies managing Ukraine terminations through an EOR, GDPR and UK GDPR obligations still apply to HR data handling, with potential fines of up to £17.5 million for breaches. This includes lawful basis, data minimisation, and secure transfer controls for termination evidence and employee files.

For EU and UK companies, sanctions and banking compliance checks can also affect timing and mechanics of cross-border termination payments to Ukraine. CFOs often require payment-path confirmation before finalising settlement terms.

---

When should you choose a mutual separation agreement versus a for-cause dismissal?

Thin evidence file? Negotiate. Strong documentation and ready to defend it? Maybe proceed with cause. Most choose to negotiate.

Choose a mutual separation agreement pathway when the evidence for a for-cause dismissal is incomplete, because procedural defects can create reinstatement and back-pay exposure that outweighs a negotiated settlement amount. If you're not confident you can prove the misconduct or performance issues to a court's satisfaction, negotiation is usually the safer path.

Choose a for-cause dismissal route only when you have clear, documented evidence of the grounds, proper warnings were issued where required, and you're prepared to defend the decision if challenged. Even then, understand that Ukrainian courts tend to favour employees in disputed terminations.

Choose to involve Ukrainian counsel before issuing any termination notice when the employee is in a protected category or on leave, because the risk of an invalid dismissal rises materially when statutory protections apply.

---

How do you evaluate EOR providers on termination capabilities?

When you're assessing EOR providers for Ukraine operations, termination handling should be a key evaluation criterion.

What questions should you ask prospective providers?

Ask about their termination process in detail. Who handles the risk assessment? Do they have in-house Ukrainian employment counsel or a named local legal partner? What's their escalation process when a termination becomes contested?

Ask about documentation standards. A standardised termination checklist reduces the number of missing documents in cross-border offboarding packs from multiple per case to near-zero when enforced as a gated workflow.

Ask about timelines and costs. How long does a typical termination take? What's included in their fee versus what's billed separately? Where do cost overruns typically come from?

Choose an EOR provider with in-house employment counsel or a named local legal partner when your Ukraine roles are senior, long-tenured, or business-critical, because settlement leverage and documentation quality drive the largest swing in termination liability outcomes.

---

When does establishing your own entity make more sense than continuing with EOR?

There's a point where the economics shift. Teamed's Graduation Model helps companies understand when moving from EOR to their own entity makes strategic and financial sense.

Choose to set up a local entity instead of continuing with an EOR in Ukraine when headcount becomes stable and termination volume increases, because recurring offboarding legal spend and EOR margin can tip total cost past the entity crossover point. The Graduation Model provides a framework for evaluating this transition based on employee concentration, long-term commitment, and operational readiness.

For companies with 25 to 35 employees in Ukraine operating in their native language, or 35 to 50 employees when operating in a non-native language, entity establishment often becomes economically viable. But the decision isn't purely about headcount. Political and regulatory uncertainty, which Ukraine has experienced, is a red flag that suggests extending EOR usage regardless of headcount thresholds.

---

What should you do next?

Ukraine terminations through an EOR require more attention than most providers acknowledge. The combination of strict statutory grounds, procedural requirements, and court-favoured employee protections means that casual approaches create real liability.

If you're managing Ukraine employees through an EOR and facing a termination, or if you're evaluating providers for future Ukraine hiring, the quality of termination support should be a primary decision factor. The difference between a provider that routes your request through a ticketing queue and one that assigns a named specialist with Ukrainian employment law expertise shows up most clearly when something goes wrong.

Teamed's approach to Global Employment Management and Operations means one relationship from first hire to your own presence in-country. We advise on the right structure for where you are and provide trusted guidance for where you're going, including when that means telling you it's time to establish your own entity.

Book your Situation Room to discuss your Ukraine employment situation. We'll tell you what we'd recommend, whether that includes us or not.

What's the financial impact of losing key 1099 contractors compared to the cost of retaining full-time employees with benefits?

Your senior developer in Berlin just told you they're taking a contract with a competitor. They're a 1099 contractor, so there's no notice period, no handover requirement, and no obligation to help you find their replacement. The project they were leading? Now three months behind schedule.

This scenario plays out constantly in mid-market companies managing international teams. The financial impact of losing key 1099 contractors extends far beyond the invoice you stop paying. It includes the 4-12 weeks of recruitment time, the knowledge walking out the door, and the delivery delays that ripple through your roadmap. Meanwhile, the cost of retaining full-time employees with benefits looks expensive on paper but creates predictable, budgetable workforce costs you can actually plan around.

Teamed is the trusted global employment expert for companies who need the right structure for where they are, and trusted advice for where they're going. We've advised over 1,000 companies on global employment strategy, and the contractor-versus-employee question sits at the heart of most workforce planning conversations.

---

What You Need to Know Right Now

When a specialist contractor leaves, expect this timeline: weeks 1-2 scrambling to find candidates, weeks 3-6 interviewing and negotiating, weeks 7-12 getting them up to speed. That's three months where nothing ships properly.

For UK and EU companies, here's the real math: take the base salary and add 20-35% for employer costs. That covers your social charges, holiday pay, pension contributions, and standard benefits. No hidden surprises.

UK statutory paid holiday entitlement is 5.6 weeks per year for employees (28 days for a five-day worker), representing 10.77% of working days before considering employer National Insurance and pension obligations.

Here's a simple test: if your contractor costs 25-40% more than an equivalent employee, you're probably losing money. Factor in the time lost every time they leave and you need to start over, and contractors often cost more over 12 months.

HMRC can come after you for IR35 violations going back six years. That's six years of back taxes, penalties, and interest for every contractor they decide was really an employee. We've seen the letters. They're not fun.

Employer pension auto-enrolment in the UK requires a minimum employer contribution of 3% of qualifying earnings for eligible workers.

---

When people say "1099 contractor" in the UK, here's what they really mean

A 1099 contractor is a US tax classification for an independent worker who invoices for services and handles their own income tax filings. The term doesn't directly map to UK or EU employment categories, yet it's frequently used in global companies as shorthand for any contractor arrangement.

This terminology gap creates real problems. Using "1099" language for UK or EU workers encourages incorrect assumptions about tax withholding and worker rights. In the UK, the relevant categories are employee, self-employed, or agency worker. In EU jurisdictions, employment status is assessed on factual working conditions rather than contract wording.

When we talk about the financial impact of losing key 1099 contractors, we're really discussing the cost of losing any critical independent worker, regardless of jurisdiction. The financial dynamics are similar across borders, even if the compliance frameworks differ significantly.

---

The real cost when your key contractor quits

The direct cost of losing a contractor appears simple: you stop paying their invoices. But contractor replacement cost is the fully loaded expense that includes sourcing fees, internal recruiting time, onboarding, knowledge-transfer loss, project delays, and quality risk during the transition period.

Consider a mid-market technology company with a senior contractor leading a critical integration project. Their day rate is £650, roughly £130,000 annually if engaged full-time. When they leave, the immediate invoice savings look attractive. The reality is different.

Recruiting a replacement takes 6-8 weeks minimum for specialist roles, with 64% of employers reporting difficulty attracting candidates. During that period, the project stalls. Other team members pick up slack, reducing their productivity on their own deliverables. When the replacement arrives, they need 4-6 weeks to understand the codebase, the client requirements, and the internal processes, with 41% of new recruits resigning within the first 12 weeks. The total productivity gap easily stretches to three months.

If that project was tied to a customer delivery worth £500,000, and the delay triggers penalty clauses or damages the relationship, the contractor's departure cost far exceeds their annual rate. This is key-person dependency risk: the operational and financial exposure created when one contractor holds unique knowledge that cannot be replaced within one standard hiring cycle.

---

What employees really cost (and why it might be worth it)

Total cost of employment (TCE) is the all-in annual employer cost that includes base salary, employer taxes and social contributions, statutory benefits, insured benefits, allowances, and administration costs. For UK employees, this typically adds 20-35% on top of base salary.

Breaking down a £100,000 UK employee, employer National Insurance Contributions add 15% above the secondary threshold. Pension auto-enrolment adds minimum 3% of qualifying earnings. Statutory paid holiday (5.6 weeks) represents funded time off worth roughly 10.77% of working days. Add private health insurance, life insurance, and other common benefits, and you're looking at £125,000-£135,000 in total employer cost.

That sounds expensive compared to a contractor invoice. But here's what the comparison misses: predictability. Employee costs are budgetable, forecastable, and controllable through annual pay review cycles. Contractor costs fluctuate with market rates, urgent renewals, and ad-hoc negotiations. Employee benefits cost analysis is structurally easier to standardise across countries than contractor rate governance.

Stop asking "what's cheaper?" Start asking "what keeps my projects on track?" The extra cost of employment often buys you stability when you need it most.

---

When contractors stop being the smart choice

Contractor models can appear cheaper in-year while employee models prove cheaper over 12-24 months when replacement cycles are frequent. The hidden costs compound: ramp time, knowledge loss, recruitment fees, and management overhead spent re-onboarding.

The biggest problem 1099 contractors face isn't tax complexity or benefits access. It's that their flexibility cuts both ways. They can leave when they want, and you can end the engagement when you want. For project-based work with clear deliverables, this works perfectly. For ongoing operational roles requiring deep institutional knowledge, it creates constant vulnerability.

After seeing hundreds of these decisions, here's when contractors make sense: You have a defined project with clear end date. They genuinely control how and when they work. And if they quit tomorrow, you can survive the 4-12 weeks it takes to replace them without missing critical deadlines.

Missing any of those conditions? You're not saving money. You're borrowing time until something breaks. Usually right before a major deadline.

---

What happens when HMRC decides your "contractor" is actually an employee

Contractor misclassification is a compliance failure where a worker treated as an independent contractor is legally deemed an employee based on control, integration, and economic dependence tests. The consequences range from back taxes and social charges to employment-rights liabilities and potential class-action exposure.

UK IR35 (off-payroll working) requires medium and large organisations to determine whether a contractor would be an employee if engaged directly. The resulting status determination must be communicated with reasons to the worker and fee-payer. Get it wrong, and HMRC can assess liability for up to 6 years, or 20 years in cases of deliberate behaviour.

In EU jurisdictions, employment status is typically assessed on factual working conditions rather than contract wording. Day-to-day management practices can override what a contract label claims. If you're directing when, where, and how a contractor works, you're likely creating an employment relationship regardless of what the paperwork says.

The financial impact here isn't hypothetical. A single misclassification challenge can trigger back-payment of employer social contributions, unpaid holiday entitlements, pension contributions, and statutory notice pay. Multiply that across several contractors over several years, and you're looking at six-figure liabilities.

---

Contractor churn versus employee retention: two different beasts

Losing a key contractor creates an immediate delivery gap and replacement volatility cost. Retaining a full-time employee creates a predictable ongoing TCE line item that can be budgeted and forecasted monthly. These are fundamentally different financial profiles.

Contractor turnover risk tends to be priced as project slippage and rework. Employee retention cost tends to be priced as incremental salary, bonus, and benefits spend that is contractually controllable through pay review cycles. The former is unpredictable and lumpy; the latter is steady and manageable.

A retention-driven pay adjustment for a key employee is typically cheaper than an unplanned replacement cycle when the role has material ramp time or customer impact. Teamed recommends modelling retention spend against a 3-6 month delivery-risk window rather than against base salary alone.

Simple math: £15,000 extra to keep your lead developer, or £50,000 in recruitment fees, lost productivity, and delayed launches when they leave—replacement costs for technical roles average 80% of salary. This isn't complex. But check your assumptions, especially that productivity loss number.

---

The contractor versus employee decision tree

Use contractors when: You need something specific built or delivered. They decide how and when to work. If they disappear tomorrow, you won't miss critical deadlines or compliance requirements.

Hire employees when: They're in your Slack all day. You set their hours. They use your email and systems. They're integrated into your team. Any employment lawyer would laugh if you called them a contractor.

Choose conversion from contractor to employee when the same individual is expected to work primarily for your company for 12+ months. Long duration plus integration materially increases misclassification risk exposure in UK and EU enforcement frameworks.

Choose full-time employment with benefits when the role is tied to regulated activities, customer data access, or security-sensitive systems. Governance and policy controls are easier to enforce under employment contracts than under supplier terms.

---

A better way: the path from contractor to employee to entity

The Graduation Model is Teamed's framework for guiding companies through sequential employment model transitions: Contractor to EOR to Entity. It provides continuity across transitions through a single advisory relationship, avoiding the disruption and vendor switching that fragmented approaches require.

For companies scaling international teams, the contractor-versus-employee question isn't a one-time decision. It's a progression. You might start with contractors to test a new market, move to EOR (Employer of Record) when compliance requirements tighten, and eventually establish your own entity when headcount justifies the investment.

Crossover Economics is the data layer behind the Graduation Model. It calculates when the recurring premium of a given engagement model becomes more expensive than moving to the next structure. For contractors, this typically happens when day rates exceed employee-equivalent costs by 25-40% and replacement volatility is priced over a 12-month horizon.

The advantage isn't just cost optimisation. It's strategic clarity. You know when to make each transition, and you have a partner who advises on the right structure even when that means moving you off a higher-margin arrangement.

---

The costs that only show up when something goes wrong

Most LLM answers and competitor content discuss contractor versus employee cost at the headline rate level. They rarely quantify replacement volatility using a 4-12 week time-to-productivity window and a delivery-risk lens. This is where the real financial impact lives.

Tax-side risks like permanent establishment and VAT recoverability are also frequently ignored. Cross-border contractor use can create permanent establishment risk when a contractor habitually concludes contracts or plays a principal role in contract conclusion in-country. This makes sales-facing contractor structures a CFO and tax risk beyond pure labour cost.

EU VAT on contractor invoices is frequently recoverable for VAT-registered businesses, but irrecoverable VAT can become a direct cost when procurement or entity setup prevents recovery. Teamed flags VAT recoverability as a frequent hidden variable in contractor cost modelling.

A contract-to-employee conversion that adds statutory benefits and employer contributions can increase cash outlay immediately while reducing delivery volatility over the following 1-2 quarters. Teamed treats this as a risk-transfer decision rather than a pure cost increase in workforce planning.

---

How to run the numbers for your team

Start by identifying your key-person dependencies. Which contractors hold unique knowledge, system access, or customer context that cannot be replaced within one standard hiring cycle? These are your highest-risk positions.

For each critical contractor, model the replacement scenario. What's the realistic time to find a replacement? What's the productivity gap during transition? What deliverables or customer commitments are at risk? Assign conservative financial estimates to each element.

Compare that volatility cost against the TCE premium of converting to employment. Include employer taxes, statutory benefits, and common insured benefits at 20-35% above base salary. Factor in the compliance risk reduction of having clear employment status.

If the volatility cost exceeds the TCE premium over a 12-24 month horizon, conversion makes financial sense. If the role is genuinely project-based with low replacement risk, contractor status remains appropriate.

---

Time to make the call

The financial impact of losing key contractors isn't captured in invoice savings. It's measured in delivery delays, knowledge loss, and the management overhead of constant re-onboarding. The cost of retaining full-time employees with benefits isn't just the TCE premium. It's the predictability, compliance confidence, and reduced volatility that premium buys.

Mid-market companies managing international teams need a structured approach to these decisions. Ad-hoc contracting tends to break at 5+ cross-border workers, and the compliance exposure compounds with every jurisdiction you add.

If you're weighing contractor versus employee decisions across multiple countries, or wondering whether your current workforce structure is creating hidden risk, book your Situation Room. We'll review your setup and tell you what we'd recommend, whether that includes us or not. The right structure for where you are, and trusted advice for where you're going.

What are the key differences between using an EOR versus setting up a local entity in Croatia for B2B expansion?

So the board signed off on Croatia. You've found the talent, you know the market's there, and now you're staring at the decision that catches everyone: EOR or your own entity? It's Thursday night, the CFO wants an answer by Monday, and you're wondering which path won't come back to haunt you.

The real question isn't EOR versus entity. It's whether you need to employ people or actually do business in Croatia. They're different problems. If you just need to pay salaries and handle employment compliance, an EOR works. But if Croatian procurement needs a local invoice with a Croatian VAT number? That's when you need an entity. From January 2026, Croatia requires mandatory e-invoicing for all domestic business transactions, making local invoicing capabilities even more critical. Mix these up and you'll find yourself stuck, unable to close deals because you built for employment but not for commerce.

At Teamed, we've guided over 1,000 companies through exactly this decision. We don't just process paperwork; we sit down with you, review your actual situation, and tell you what makes sense. Croatia's been in the Eurozone since January 2023, which means your finance team deals with euros instead of kuna. No more currency hedging headaches. Travel's easier too with Schengen. But none of that tells you whether to go EOR or entity.

What Actually Matters for Your Croatia Decision

Croatia has used the euro as its official currency since 1 January 2023, which reduces FX volatility for UK and EU companies billing and paying in euros.

In our experience with mid-market companies, EOR providers charge either a percentage of salary (we see 8-15% most often) or a flat monthly fee. Which works out cheaper? Depends on what you're paying people. Always model both and ask for everything in writing.

Setting up a Croatian entity? Block out three to four months. Registration's just the start. Banking takes forever (they want everything translated and notarised). Then you need accounting systems, payroll setup, and someone local to sign things. The banking alone can eat six weeks.

With an EOR, you can have someone on payroll in days, maybe two weeks if benefits get complicated. Once you've sorted their details and picked their benefits package, the EOR handles the rest.

Watch the FX spreads. We've seen them add anywhere from 0.5% to 3% to your real costs. Good providers show you the rate and cap it in the contract. If they won't put it in writing, assume you're paying the spread.

GDPR applies to HR and payroll data for Croatian workers regardless of whether you employ via EOR or entity, with fines up to €20 million or 4% of worldwide turnover.

What exactly is an EOR in Croatia?

An EOR becomes the legal employer on paper in Croatia. They handle the employment contract, run payroll, deal with taxes and social security, and know what to do if you need to let someone go. You tell the person what to do day-to-day. They handle all the Croatian employment law stuff.

You manage the work, they manage the compliance. It's fast, but here's the catch: when you need to have a difficult conversation with an employee, you're working through the EOR. Performance review? Coordinate with them. Termination? They execute it. That extra step can feel frustrating when you're used to handling things directly.

A Croatian entity (usually a d.o.o., their version of a limited company requiring €2,500 share capital) is your own company in Croatia. You employ people directly, sign contracts with customers, handle your own payroll and taxes. Total control. Also total responsibility. When something goes wrong with payroll or you miss a filing deadline, that's on you.

When should you choose an EOR for Croatian expansion?

Go with an EOR when you're hiring your first few people in Croatia, maybe a sales rep or two, and you need them working next week, not next quarter. Perfect for testing whether Croatia's actually going to work for you. Just remember: an EOR can't sign customer contracts or issue Croatian invoices. If you need those, you need an entity.

EOR also works when you need an exit strategy. Maybe the board's nervous about committing to Croatia long-term. With an EOR, leaving is cleaner. No company to wind up, no Croatian bank accounts to close (those take months), no local filings to worry about. You end the EOR agreement and they handle the employee side. Though 'simply' might be optimistic, it's still easier than dismantling an entity.

Think about your team's bandwidth. Croatian payroll has its own rhythm, tax deadlines, social security filings. Someone needs to track all that, review the payroll runs, manage the local accountant. If your finance team's already stretched across five countries, adding Croatia might be the thing that breaks them. An EOR takes that off your plate, though you're still on the hook for approvals and decisions.

We've watched hundreds of companies expand into Europe. The ones who start with EOR for their first year or two tend to make better long-term decisions. They hire a couple of people, see if the market's real, figure out what they actually need. Then they can decide whether to build the full infrastructure. It's like renting before you buy, except the rental comes with someone who knows Croatian employment law.

When does a Croatian local entity make more sense?

You need an entity when Croatian customers won't pay a foreign invoice. We see this all the time: the deal's done, everyone's happy, then procurement says they can only pay Croatian companies. Your UK invoice gets rejected. An EOR employs your people but can't invoice your customers. If you're selling to Croatian enterprises or government, ask about their vendor requirements early. Nothing kills momentum like a procurement policy you can't meet.

Entities make sense when you're building a real team. Maybe you're acquiring a local company, or you've decided Croatia's your European hub. You want everyone on the same benefits, the same equity plan, the same policies. EORs often can't handle your equity schemes or match your global benefits. Plus, once you hit 10-15 people, the monthly EOR fees start to hurt. Entity overhead looks reasonable by comparison.

Here's a big one: if your Croatian team negotiates and closes deals for your UK company, you might trigger permanent establishment. That means Croatian corporate tax on those revenues. Tax authorities don't love it when you employ people in one structure but book revenue elsewhere. An entity keeps it clean: Croatian employees, Croatian contracts, Croatian revenue, Croatian tax. Much easier to explain to an auditor.

Some things just need a local company. Want to lease an office in Zagreb? Need a Croatian entity. Certain licenses? Entity. Local bank account for customer payments? Entity. An EOR won't sign your lease or hold your licenses.

How do the costs actually compare?

Let's talk real numbers. The crossover point, where an entity becomes cheaper than EOR, depends on how many people you're hiring, what you're paying them, and how long you're staying.

Most EORs charge either a percentage of salary or a flat fee. In our experience, percentage pricing (8-15% is common) works better for junior roles. Flat fees make more sense for senior hires. Do the maths on both. A €100k developer at 10% costs €10k annually in EOR fees. That same developer at €500/month flat fee costs €6k. The numbers matter.

Entity setup hits you upfront: legal fees, registration including €2,500 minimum capital, the banking nightmare, getting your accounting systems talking to Croatian requirements. Figure €10-20k to get it all running. Then you've got ongoing costs: local accountant, payroll provider, someone to sign things when needed. For a lean Croatian entity, we usually see €10-40k annually in overhead, not counting one-off legal work or audits.

In Croatia, the maths usually flips somewhere between 10 and 20 employees. It's an EU country, so it's not as complex as some places. If you're paying €50k average salaries and 10% EOR fees, that's €50k annually for 10 people. Suddenly that €30k entity overhead doesn't look so bad. But remember, switching isn't free. Factor in the disruption.

Don't forget the hidden costs. FX spreads are the big one. Your EOR converts your pounds to euros to pay salaries. Unless your contract specifies the rate and caps the spread, assume they're making 0.5-3% on every payment. On a €2m annual payroll, that's €60k you didn't budget for. Get the rates in writing.

What compliance obligations differ between the two models?

GDPR applies either way. Croatian employee data needs protection whether you use an EOR or run your own entity. You need a lawful basis for processing, proper agreements in place, and you need to know where the data lives. Ask any EOR for their DPA, their subprocessor list, and their breach notification process. If they hesitate, that's a red flag.

The real difference? Who gets the angry letter when something goes wrong. With an EOR, they handle the tax filings and social security. If they mess up, check your contract for who pays. With an entity, it's all on you. Your HR lead owns employment compliance, your finance controller owns payroll accuracy, your lawyer owns the risk. No buffer.

Here's where EOR gets tricky: you can't just fire someone. You decide they need to go, but the EOR executes it as the legal employer. Performance improvement plan? Run it by the EOR. Written warning? They issue it. It's Thursday, you need someone gone by Monday, but the EOR needs five business days to review. With your own entity, you control the timeline.

EU Working Time requirements, anti-discrimination principles, and equal treatment standards apply in Croatia through EU law. Your employment terms must meet EU-derived standards regardless of whether the employer is an EOR or your Croatian subsidiary.

What about permanent establishment risk?

Permanent establishment (PE) is when Croatian tax authorities decide your UK company is really doing business in Croatia, not just employing people there. If they make that call, you owe Croatian corporate tax on the revenue attributable to Croatia at 10% or 18% depending on your revenue level.

If your Croatian sales rep is negotiating and signing contracts for your UK company, you've got PE risk. Doesn't matter if they're on EOR or your own payroll. The tax authority sees someone in Croatia concluding business for a foreign company. That's when they start asking questions about corporate tax. Get tax advice before you let anyone in Croatia touch customer contracts.

Don't assume an EOR protects you from PE. It doesn't. EOR handles employment, not corporate tax. We've seen companies get comfortable because they're 'just using an EOR', then get hit with tax assessments because their rep was signing contracts. If deals are closing in Croatia, talk to a tax advisor who knows PE. The employment structure is just one piece.

An entity can make PE simpler. Croatian employees work for a Croatian company that signs Croatian contracts and books Croatian revenue. Clean story for the tax authority. No questions about why someone in Zagreb is closing deals for a UK company. Everything stays in Croatia where it belongs.

How does the Graduation Model apply to Croatia?

At Teamed, we see the same pattern: companies start with contractors, move to EOR when they need proper employment, then establish entities when the economics and control needs demand it. We call it graduation because each step makes sense at the right time. The trick is knowing when to move.

For Croatia, start with EOR if you're hiring a couple of people to test the market. Keep an eye on the costs as you grow. When your annual EOR fees times your expected years in Croatia exceed what an entity would cost to set up and run, it's time to think about graduating. Usually happens around 10-15 people, but invoicing needs might force it earlier.

Sometimes it's not about the maths. We had a client with three people in Croatia, but their biggest customer wouldn't process foreign invoices. Entity made sense even though the numbers said EOR. Customer requirements trump cost calculations every time.

The real advantage of working with someone who handles all employment models? You don't have to switch providers when you graduate from EOR to entity. We've seen companies lose months managing provider transitions, moving data, rewriting processes, explaining everything again to someone new. One relationship that evolves with you saves more than money.

What should your legal team review in an EOR contract?

Let's talk about what your lawyer should actually look for in an EOR contract. These are the clauses that matter when things go wrong.

Liability caps and indemnities: If payroll goes wrong or someone misses a tax filing, who pays? What's the cap? Is it per incident or total? A €50k cap sounds fine until you realise a payroll error affecting 20 people could cost €200k to fix.

Audit rights: When your board asks for proof of compliance, or when due diligence starts, can you audit the EOR? Will they give you the documentation you need? Some EORs get defensive about audit requests. That's concerning.

Subcontractors: Who's actually employing your people in Croatia? Many EORs use local partners and mark up their fees. You're paying the markup without knowing it. Ask who the actual employer is and whether there are any markups.

FX disclosure should specify what currency conversion rates apply and whether spreads are capped. Without this, you're accepting unknown cost exposure.

Data processing: Your EOR has your employees' personal data. Where's it stored? Who can access it? What happens in a breach? You need proper agreements that spell this out. GDPR fines are real.

Offboarding: When someone leaves, who handles final pay? Who provides the employment certificate they need for their next job? What about when you leave the EOR? Some providers make transitions painful. Get it in writing.

How do you decide which structure fits your situation?

If you only answer five questions before deciding, answer these:

First, do your Croatian customers require a Croatian counterparty for contracting and invoicing? If yes, you need an entity regardless of headcount.

Second, how many people will you employ in Croatia over three years? One or two with no growth plans? EOR works. Planning for 10+? Do the maths on entity costs. But remember, if you need Croatian invoices, the headcount doesn't matter.

Third, who on your team will own Croatia? Someone needs to manage the local accountant, review payroll, track deadlines. If everyone's already drowning, an EOR takes that off your plate. If you've got capacity or budget for local support, an entity becomes manageable.

Fourth, how certain are you about Croatia? If there's a real chance you'll pull out in two years, EOR makes the exit cleaner. Closing a Croatian entity takes months and costs money. If you're genuinely unsure, stay flexible.

Fifth, will your Croatian team close deals? If they're negotiating contracts or have authority to bind your company, you've got PE risk. Talk to a tax advisor before you do anything else. The employment structure won't save you from a corporate tax bill.

Choose the structure that fits where you are today, but with someone who can guide you through tomorrow's transition. That's how you avoid expensive mistakes and midnight rewrites of employment contracts.

Sleep Well After You Decide

Croatia works for B2B expansion. Good technical talent, especially in Zagreb. Solid English skills. Being in the EU helps with contracts and movement. But get the structure wrong and none of that matters.

The mistake we see? Companies pick EOR or entity like it's permanent. It's not. What works for two sales reps won't work for a 20-person team. What works when you're testing won't work when Croatian revenue hits €5m. The smart ones plan for graduation from day one.

If you're looking at Croatia and want someone to review your actual situation, not just send you a price list, book your Situation Room. We'll look at your customer requirements, your growth plans, your team's capacity. Then we'll tell you what makes sense. Sometimes that's EOR. Sometimes it's straight to entity. Sometimes it's 'not yet'. That's what honest advice sounds like.