How much does payroll processing cost?

You've just expanded into Germany, hired three people in Spain, and now your CFO wants a forecast for global payroll costs over the next 18 months. You pull up your current provider's invoice and realise you can't actually tell what you're paying for. The base fee is there, but what about the FX margin? The per-country charges? The off-cycle run fees that appeared last month?

This is the reality for most mid-market companies scaling headcount across countries without entity setup. Payroll processing costs aren't a single number. They're a stack of fees, margins, and pass-through charges that vary dramatically by country, provider, and employment model. Getting the forecast wrong doesn't just blow your budget. It undermines every hiring decision you make.

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 mapped payroll costs across 180 countries and consistently find that the stated processing fee is rarely the full picture. Here's what you actually need to know.

What payroll really costs when you add countries

UK payroll bureaus charge £3 to £8 per payslip for monthly runs. But watch out for the £500 setup fee and those year-end RTI charges that show up in April.

European payroll runs €15 to €40 per employee per country each month. That's before they charge you for actually sending the payments or connecting to your HR system.

Got employees in five European countries? You're paying five separate base fees every month. Most providers don't care that it's the same company.

That 'competitive exchange rate' your provider mentions? It's usually marked up 0.5% to 3.0%. On a €2.5M monthly payroll, that's more than your processing fees.

For a 500-employee company, a 1.0% FX spread on €2.5M monthly payroll funding equals €25,000 per month in implicit cost.

Setting up payroll in a new country? Block out 6 to 12 weeks. You'll spend most of it chasing historical data, running test payrolls, and waiting for local registrations.

What does payroll processing actually include?

Payroll processing is an operational and compliance function that calculates gross-to-net pay, applies statutory deductions, issues payments, and produces the reports needed for tax and employment law compliance in a specific country. That's the core service. Everything else is an add-on that affects your total cost.

The baseline processing fee covers salary calculations, tax withholdings, and payslip generation. But most mid-market companies also need direct deposit execution, tax filing submissions, year-end reporting, and employee self-service portals. Each of these can be priced separately or bundled, and the bundling is where costs become opaque.

UK payroll compliance requires Real Time Information submissions to HMRC on or before each pay date, so every payroll run has a corresponding statutory reporting event. France payroll processing requires detailed payslip content and consistent handling of social contributions, with employer contributions reaching 26.7% of labour costs, the highest among OECD countries. Germany's recordkeeping requirements include retention expectations tied to tax and social security documentation, with employer social security contributions alone equalling 16.8% of labour costs. These aren't optional extras. They're compliance requirements that should be explicitly covered in your provider's scope.

How do providers structure payroll service pricing?

Payroll service pricing typically combines three elements: a base fee, per-employee fees, and pass-through costs. The structure you choose affects how your costs scale as you add headcount and countries.

Per-employee-per-month pricing

Per-employee-per-month pricing charges a fixed amount for each active worker on payroll each month, regardless of how many payroll runs occur. This model makes forecasting straightforward because costs scale linearly with headcount. If you're paying €25 per employee per month and you add 20 people in the Netherlands, your monthly cost increases by €500.

Choose this model when your workforce size is predictable and you want cost forecasting that scales linearly across months. The downside is that you pay the same whether you run one payroll or four, which can feel expensive for monthly-only payroll schedules.

Per-payroll-run pricing

Per-payroll-run pricing charges each time a payroll is executed, often with an additional per-employee charge layered on top. This model can be cheaper for companies with low payroll frequency and minimal off-cycle payments. But off-cycle runs for bonuses, corrections, or terminations can materially increase costs.

A monthly payroll with time-and-attendance inputs typically generates more exceptions than a fixed-salary population. Exception volume drives additional fees through off-cycle run and adjustment charges. If your workforce includes hourly employees, contractors converting to full-time, or frequent mid-month changes, per-run pricing can become unpredictable.

Flat-fee pricing

Some providers offer flat monthly fees that include unlimited payroll runs and a set number of employees. This model provides cost certainty but often comes with headcount caps and overage charges. It works well for stable, single-country operations but becomes complicated when you're scaling across multiple jurisdictions.

What are the real cost drivers beyond the processing fee?

The stated processing fee is typically the smallest component of your total payroll cost. The real cost drivers sit in three categories that most providers don't break out clearly.

FX margins on payroll funding

When you fund payroll in a currency different from your home currency, providers convert your payment at an exchange rate that includes their margin. According to Teamed's Three Layers of Opacity framework, FX spread is one of the most material drivers of unexpected payroll cost variance in multi-country payroll.

A 1.0% FX margin might sound small, but on a €2.5M monthly payroll funding requirement, that's €25,000 per month in implicit cost. Many providers quote FX margins in the 0.5% to 3.0% range, and this cost is frequently larger than the stated processing fee line item. Ask for explicit FX margin disclosure before signing any contract.

Payment rail charges

International payroll payment delivery via urgent bank transfers can add €10 to €40 per payment in bank fees depending on the corridor and bank, though EU instant payment charges cannot exceed regular transfer fees under current regulations. These fees are frequently passed through at cost rather than included in processing fees. For a 200-person workforce paid monthly across five countries, payment rail charges alone can add €2,000 to €8,000 per month.

Per-country base fees

Most global payroll providers price per country, not per global headcount. A mid-market company running payroll in five European countries incurs five separate base fees per month. These base fees typically range from €200 to €1,000 per country per month before any per-employee charges are added.

This structure means your payroll costs don't just scale with headcount. They scale with geographic footprint. Adding one employee in a new country can cost more than adding ten employees in an existing country.

How does payroll cost differ by employment structure?

Your employment structure determines not just your payroll processing fees but your total cost of employment. Understanding this connection is critical for CFO forecasting.

Payroll-only services

Payroll-only services assume you already have a local employing entity. You handle employment contracts, benefits administration, and compliance. The provider runs payroll calculations, tax filings, and payment execution. This is typically the lowest-cost option per employee but requires you to bear the fixed costs of entity setup and ongoing corporate compliance.

Choose local entity payroll when you already have, or are ready to set up, an employing entity and you want direct control over employment contracts, benefits design, and statutory filings under your own corporate registrations.

EOR payroll

Employer of Record payroll is a structure where the EOR becomes the legal employer and runs payroll, remits taxes, and holds employment compliance liability in-country while you direct day-to-day work. The EOR bundles payroll, statutory benefits, and employment compliance under their entity.

EOR costs are higher per employee than payroll-only services because you're paying for the compliance infrastructure and liability transfer. But you avoid entity setup costs, which can range from £15,000 to £50,000 per country depending on jurisdiction complexity.

When does entity payroll become cheaper than EOR?

Entity-based employment differs from EOR employment in cost structure because entity setups introduce fixed legal, accounting, and corporate compliance costs that become cheaper per employee beyond a headcount threshold. EOR costs remain largely variable per employee.

Teamed's Graduation Model provides a framework for this decision. The crossover point varies by country complexity. In Tier 1 countries like the UK, Ireland, and Singapore, entity setup typically becomes economically favourable at 10 or more employees. In Tier 2 countries like Germany, France, and Spain, the threshold rises to 15 to 20 employees. In Tier 3 countries like Brazil, India, and China, staying on EOR often makes sense until you reach 25 to 35 employees.

The Graduation Model enables companies to move from contractor to EOR to entity through a single advisory relationship, avoiding the disruption and re-onboarding that fragmented approaches require. This continuity matters because provider transition costs typically run £15,000 to £30,000 per country in management overhead, knowledge transfer, and process recreation.

What hidden fees should you watch for?

Most generic payroll guides omit the contract terms that drive total cost. Based on Teamed's analysis of mid-market vendor contracts, here are the fees that most commonly surprise buyers.

Implementation and change costs

Payroll implementation projects for multi-country rollouts typically take 6 to 12 weeks per country. Delays are most often driven by incomplete historical pay data and benefits mapping. Implementation fees can range from one to three months of ongoing service fees per country.

Change costs accumulate through off-cycle runs, mid-year amendments, and year-end adjustments. A single off-cycle run to process a termination payment might cost €50 to €200 depending on your contract. If you're processing 20 terminations per year across five countries, that's €1,000 to €4,000 in fees that weren't in your original forecast.

Subprocessor markups

Many global payroll providers don't run payroll directly in every country. They subcontract to local bureaus and mark up the cost. These undisclosed in-country partner markups can add 15% to 40% to your per-employee costs without appearing as a separate line item.

Ask them straight up: 'Do you run payroll directly in Poland, or do you use a local partner? And what's your markup?' A good provider will tell you exactly.

Liability caps and SLA remedies

Liability caps determine your exposure when something goes wrong. Many providers cap their liability at the fees paid over the previous 12 months. If a compliance error costs you €100,000 in penalties but you've only paid €20,000 in fees, you're absorbing €80,000 of the loss.

SLA remedies should specify what happens when deadlines are missed. A payroll that runs late in Germany doesn't just create employee frustration. It triggers compliance reporting obligations. Your contract should specify remediation processes and financial remedies for missed deadlines.

How can you reduce global payroll costs?

You've got three ways to cut payroll costs: pick the right employment structure, reduce manual work, and negotiate better terms. Most companies only try the third one.

Consolidate providers

Coordinating separate EOR providers, entity formation specialists, local payroll vendors, and compliance consultants creates significant overhead. For mid-market companies operating in 5 to 15 countries, Teamed's GEMO framework shows that coordination costs alone often reach £50,000 to £150,000 annually.

A single supplier with Global Employment Management and Operations capability eliminates this fragmentation. You get one advisory relationship, one invoice, and one point of accountability across all employment models.

Time your entity transitions

Every month past the crossover point where entity setup becomes cheaper than EOR is pure margin for your provider. Most EOR providers are structurally incentivised never to surface this because it reduces their revenue.

Run a three-year cost comparison for each country where you're approaching headcount thresholds. Include your actual EOR fees, estimated entity setup costs, and ongoing entity costs. If you're switching providers as part of the transition, add £15,000 to £30,000 per country in transition costs.

Negotiate FX transparency

FX margins are negotiable. Ask for explicit margin disclosure and compare against mid-market rates. A reduction from 2.0% to 0.5% on a €1M monthly payroll saves €15,000 per month. Over three years, that's €540,000 in savings from a single contract term.

What should your payroll cost forecast include?

Your real payroll cost includes what you pay them, what it costs your team to manage them, and what you spend fixing their mistakes. Most companies only track the first one.

In-house payroll resourcing for a multi-country footprint commonly requires at least 0.2 to 0.5 FTE per additional country for governance, vendor management, and exception handling even when processing is outsourced. This internal cost is often excluded from forecasts but can exceed external provider fees for complex operations.

Build your forecast by country, not by global headcount, factoring in the true total hiring cost by country. Include base fees, per-employee charges, estimated FX costs at current exchange rates plus margin, payment rail charges, and a contingency for off-cycle runs and amendments. Then add internal time costs for payroll governance and exception management.

Getting clarity on your global payroll costs

The global employment industry profits from keeping costs opaque. Providers benefit when you can't tell whether you're overpaying, when you don't know the crossover point for entity setup, and when switching feels too complicated to attempt.

You deserve better than that. You deserve a forecast you can actually defend to your CFO, a contract with transparent FX margins, and an advisor who tells you when EOR stops being the right structure for your German team.

If you're scaling headcount across countries and want clarity on what you're actually paying, book your Situation Room. We'll review your current setup and 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 you compare EOR vs. PEO services for expanding into Japan?

You've landed a major opportunity in Japan. Maybe it's an acquisition with Tokyo-based engineers, a sales push into APAC, or a key hire who won't relocate. Now comes the question that trips up even experienced global employers: should you use an Employer of Record or a Professional Employer Organization to get people on payroll?

Here's the thing most comparison guides won't tell you upfront: the EOR vs PEO distinction works differently in Japan than in markets like the United States or United Kingdom. A PEO model in Japan generally assumes you already have a Japanese employing entity. If you don't have one, and you're not ready to establish one, the PEO option isn't actually available to you. This single fact eliminates confusion that derails many expansion timelines.

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 help mid-market companies navigate exactly this decision across 180 countries, including Japan's uniquely complex employment landscape.

What actually matters for Japan (skip the fluff)

Japan's statutory standard working time is 8 hours per day and 40 hours per week under the Labour Standards Act, with overtime premiums of at least 25% beyond statutory hours.

An EOR signs the employment contracts in Japan. They handle payroll, social insurance, all the filings. You manage the actual work. They carry the employer liability, you keep operational control.

A PEO in Japan helps with HR admin, but you need your own Japanese entity first. Without one, they can't help you hire anyone.

Annual paid leave in Japan starts at 10 days after 6 months of continuous employment with at least 80% attendance, increasing with tenure.

For UK and EU companies expanding without triggering permanent establishment risks, the Japan cost surprises aren't in base salary. They're in social insurance (health insurance rates vary by prefecture from 9.44% to 10.78% plus an 18.3% pension rate), overtime calculations that catch everyone off guard, and mandatory bonuses nobody mentioned.

Setting up a Japan entity takes 4-6 months. That's incorporation, getting a bank account (harder than it sounds), tax registrations including salary office notification within 1 month, and moving employees over. Japan's not the hardest country, but it's not the easiest either.

The real Japan question: Do you have an entity or not?

An Employer of Record is a third-party organisation that becomes the legal employer of your worker in Japan. The EOR runs local payroll, withholds income tax, administers statutory benefits like Shakai Hoken (health and pension insurance), and holds primary employment-law responsibility. You direct the day-to-day work while the EOR carries the legal employer obligations.

A Professional Employer Organization operates differently. A PEO provides HR administration support, but the client company remains the legal employer in-country. In Japan, this means you need a Japanese employing entity, whether a subsidiary, branch, or other registered company, that can sign Japanese employment contracts, register for social insurance, and act as the statutory employer.

The core distinction comes down to who holds legal employer status. With an EOR, the provider is the employer. With a PEO arrangement, you are the employer, and the PEO supports your HR administration. This isn't a subtle difference. It determines your compliance exposure, your setup requirements, and your timeline to first hire.

EOR invoices in Japan commonly combine a fixed monthly service fee with pass-through employment costs. Invoice variance risk increases when FX spreads, local partner markups, or bundled compliance fees aren't explicitly itemised. Teamed's Three Layers of Opacity framework identifies these as the three ways the EOR industry obscures costs: hidden FX margins, bundled compliance fees, and undisclosed in-country partner markups.

Why does Japan require a local entity for PEO arrangements?

Japan's employment law framework creates a clear requirement: someone must be the registered employer for each worker. That employer must enrol eligible employees in Shakai Hoken and Rōdō Hoken (labour insurance covering workers' accident compensation and employment insurance), maintain time records that must be kept for 5 years, and execute compliant employment contracts.

A PEO cannot perform these functions on your behalf in Japan unless you have an entity that serves as the legal employer. The PEO can manage payroll processing, benefits administration, and HR tasks, but the employment relationship, contracts, and statutory registrations sit with your Japanese entity.

This differs from the United States, where co-employment models allow PEOs to share employer responsibilities without the client establishing a separate entity. Japan doesn't recognise co-employment in the same way. The party with the local employing entity remains the legal employer for labour-law purposes.

A common failure mode in Japan expansion is assuming a PEO can employ workers without a Japanese entity. This misunderstanding frequently causes timeline slippage in multi-country rollouts, according to Teamed's Situation Room intake patterns. Companies budget for PEO costs and timelines, then discover they need entity establishment first, adding months and significant expense.

When should you choose an EOR for Japan?

Use an EOR when you need to hire now and don't have a Japan entity. They become the employer, handle the contracts, run payroll, do all the government filings.

Speed-to-first-hire often drives this decision. If your internal Legal and Finance teams aren't resourced to create and maintain Japanese payroll, tax withholding, and social insurance registrations immediately, an EOR lets you hire within days rather than months. The practical time-to-hire difference between EOR and entity-based hiring in Japan is often dominated by how quickly the employer can complete payroll and social-insurance registrations rather than candidate availability.

EOR makes sense when you're testing the Japanese market. If you're in your first 1-2 years validating product-market fit, committing to entity establishment carries risk. An EOR lets you hire, operate, and evaluate the market before making a larger structural investment.

Choose an EOR when you need a single provider accountable for statutory benefits administration and compliant offboarding processes. Japan's employment terminations are higher-risk than in many EU or UK contexts. Dismissals without objectively reasonable grounds and social acceptability can be challenged, so compliant performance management documentation is a key control. An EOR carries this compliance burden rather than your team.

When does a PEO approach make sense for Japan?

Go PEO when you have a Japan entity and want to keep everything in-house: employment contracts, IP ownership, payroll control. You run it, they support it.

This approach works when you require bespoke benefits design, internal HR policy alignment, or tighter control over employment terms and approvals that may be constrained by an EOR's standardised contract templates. Some enterprise customers require contracting with local entities. Certain IP structures require own entities. Direct bank account control may be needed.

A PEO approach suits companies where the CFO requires cost predictability through direct vendor contracting and you're prepared to manage Japanese accounting, payroll, and annual employer compliance obligations. Entity-plus-PEO costs are usually spread across separately contracted local vendors, making cost components more visible than bundled EOR invoices.

For UK-based groups expanding into Japan, any model that uses a Japanese entity must also plan for Japanese corporate governance steps. You'll need to appoint a Representative Director (代表取締役) with signing authority before employment contracts can be executed in practice.

How do EOR and PEO compare on compliance in Japan?

EOR vs PEO Japan differs most in liability allocation. An EOR contract usually places primary employment-law compliance execution on the EOR. A PEO arrangement leaves the client entity carrying the employer-of-record legal exposure.

Japan's Labour Standards Act sets baseline rules for working time, overtime premiums, and paid leave. Non-compliance commonly creates back-pay exposure because wage claims often turn on time-records and pay slips. Employers must pay at least a 25% premium for overtime beyond statutory hours, at least 35% for work on statutory holidays, and at least 25% for late-night work between 22:00 and 05:00. Some scenarios stack these premiums.

With an EOR, the provider manages time-record governance and overtime calculations. Time-record integrity is one of the most common audit artifacts requested during Japanese labour disputes. With a PEO arrangement, your entity carries responsibility for maintaining compliant records, even if the PEO processes payroll.

EOR vs PEO Japan differs operationally in payroll ownership. EOR payroll runs under the EOR's registrations and processes. PEO support typically sits alongside the client's payroll registrations and statutory accounts. This affects audit trails, regulatory interactions, and where liability sits when something goes wrong.

What are the cost considerations for EOR vs PEO in Japan?

For many mid-market expansions, the decision point arrives when recurring EOR fees exceed the amortised cost of entity setup plus ongoing accounting, payroll, and compliance administration. Teamed's Crossover Economics methodology recommends modelling this comparison over a 12-24 month horizon.

Japan sits in Tier 2 of Teamed's Country Concentration Framework, meaning moderate complexity with strong employee protections, consensus-based dismissal expectations, and extensive documentation requirements that mid-market firms must navigate.

The Graduation Model, Teamed's proprietary framework for guiding companies through sequential employment model transitions, provides a structured approach to this decision. The model covers three stages: Contractor, EOR, and Entity. Teamed proactively advises when it's time to move to the next stage, even when that means moving the client off EOR. This continuity through a single advisory relationship avoids the disruption, re-onboarding, and vendor switching that fragmented approaches require.

EOR vs PEO Japan differs in transition complexity. Moving from EOR to an owned Japanese entity typically requires an employment transfer and re-registration processes. PEO-to-entity is often a vendor change rather than a change of legal employer. For EU and UK companies transferring employees from EOR to their own Japanese entity, the process must be treated as a change of employer requiring updated contracts and statutory registrations, scheduled to avoid payroll cutover and benefits coverage gaps.

How do you evaluate EOR contracts and service levels before signing?

Start with cost transparency. Request line-item breakdowns that separate the service fee from pass-through employment costs. Ask explicitly about FX margins, local partner markups, and bundled compliance fees. If the provider can't or won't itemise these components, that opacity will compound over time.

Examine the liability allocation clauses. Where does compliance responsibility sit when something goes wrong? What happens if the EOR misses a tax obligation or mishandles an offboarding? Liability caps that don't cover real risk are a warning sign.

Assess the support model. Japan's employment complexity means you'll encounter edge cases, whether it's overtime premium stacking scenarios, works council equivalents, or termination documentation requirements. Ask whether you get a named specialist who understands your business, or a chatbot and an offshore queue when situations get complex.

Review the transition provisions. What happens when you're ready to establish your own entity? Some EOR contracts create friction around graduation, whether through notice periods, data handover processes, or unclear employee transfer procedures. The right provider should be economically aligned with helping you make the right structural decision, not keeping you on EOR indefinitely.

What are the EOR companies operating in Japan?

Several global EOR providers operate in Japan, including Deel, Remote, Oyster, Velocity Global, Globalization Partners (G-P), Papaya Global, Atlas, Safeguard Global, Multiplier, and Boundless. Each has different service models, pricing structures, and local partner arrangements.

The differentiator isn't which providers have Japan coverage. Most do. The differentiator is how they handle Japan's specific complexity: overtime premium calculations, social insurance administration, termination documentation, and the eventual transition to your own entity.

Look for providers with genuine in-market expertise rather than just operational capabilities. Japan's cultural expectations around employment stability, extensive documentation requirements, and judicial scrutiny of terminations require advisors who understand the nuances, not just a platform that processes payroll.

Teamed operates in 180 countries including Japan, combining expert advisory with operational infrastructure. We advise companies on the right employment structure for each market, whether that's contractors, EOR, or owned entities, then execute it. As your strategy evolves, we evolve with you, maintaining one relationship across every transition.

Making the right decision for your Japan expansion

Here's your Japan decision tree: Do you have an entity? No? Then it's EOR. How fast do you need to hire? This month? EOR. Planning to stay for years with 20+ people? Start thinking entity.

If you don't have a Japanese entity and need to hire quickly, EOR is your path. If you have an entity and want HR administration support while maintaining employer control, a PEO approach works. If you're planning significant headcount growth in Japan over 3+ years, modelling the crossover point between EOR costs and entity establishment becomes essential.

The right structure for where you are, and trusted advice for where you're going. That's what separates a strategic Japan expansion from one that creates compliance exposure and cost surprises.

If you're evaluating EOR vs PEO for Japan, or trying to determine when entity establishment makes sense, book your Situation Room. Tell us your setup, and we'll tell you what we'd recommend, whether that includes us or not.

What EOR really costs: The invoice reality check

You've just been told the board approved expanding into Germany. Or maybe you've inherited 15 employees in the Netherlands after an acquisition. Either way, you're now searching for EOR pricing and finding numbers that range from $99 to $2,000 per employee per month.

That spread tells you nothing. Here's what actually happens: You see £400 per employee on the sales deck. Your first invoice arrives at £750. The provider acts surprised when you call. We've watched this scene play out hundreds of times, and it's always the same hidden costs driving the difference.

We've reviewed thousands of EOR invoices. Sat through the awkward calls when finance discovers the real cost. Helped companies untangle contracts designed to confuse. After advising companies across 70+ countries, we know exactly where providers bury the costs and why your CFO keeps asking uncomfortable questions about that growing EOR line item.

What shows up on real EOR invoices

In Europe and the UK, you'll see EOR admin fees between £300 and £900 per employee monthly. That's before salary, before the 20-35% employer taxes, before benefits. The number that matters for your budget? Double whatever they quote.

Percentage pricing runs 8% to 15% of payroll in Europe. Sounds simple until you discover some providers calculate that percentage on salary plus employer taxes plus benefits. Your 8% just became 11%.

That first invoice shock? It's the employer taxes. Western Europe adds 20% to 35% on top of gross salary. Nobody mentions this during the sales pitch. Your £100k developer in France actually costs £135k before you even add the EOR fee.

Here's a fun discovery: that FX conversion hiding on page 3 of your invoice? A 2% spread on currency conversion costs you an extra month of EOR fees every year. They count on you not checking the rate.

Setup fees range from zero to £2,500 per country. The providers charging zero make it up elsewhere. The ones charging £2,500 better have someone spectacular running your account.

When your invoice swings 2% to 6% every month, something's buried in there. Could be FX games, off-cycle payment fees, or benefit adjustments. Ask for every line item. If they hesitate, you've found the problem.

What is an Employer of Record and what does the fee cover?

An Employer of Record is a third-party entity that becomes the legal employer of your workers in a specific country. The EOR runs local payroll, handles statutory taxes, manages mandatory benefits, and maintains employment compliance while you direct the day-to-day work.

The EOR fee itself is the administration charge for this service. It covers contract generation, payroll processing, tax filings, benefits administration, and compliance monitoring. What it doesn't cover is the actual cost of employing someone, which includes their salary, employer social contributions, mandatory benefits, and any country-specific payments like 13th month salary or holiday allowances.

This distinction matters because many providers quote only the administration fee. When your first invoice arrives with employer contributions adding 20% to 35% on top of gross salary in Western European countries, the total looks nothing like what you expected.

How do EOR providers structure their pricing?

EOR providers offer two pricing models. Pick wrong and you'll overpay every month. The trap is that neither model tells the whole truth about your costs.

What's the difference between flat-fee and percentage-of-payroll pricing?

A flat-fee EOR model charges a fixed amount per employee per month regardless of salary. If you're paying £500 PEPM, that fee stays constant whether the employee earns £40,000 or £120,000 annually. Statutory employer costs still pass through at actuals, but your administration fee remains predictable.

A percentage-of-payroll model charges a fixed percentage of gross payroll, typically 8% to 15% in European markets. The critical detail is what that percentage applies to. Some providers calculate it on gross salary alone. Others apply it to gross salary plus employer taxes, which can increase the effective fee base by roughly 20% to 35% in many EU countries.

Choose a flat-fee model when you have wide salary variation across roles and want predictable administration costs that don't scale automatically with compensation increases or variable pay. Choose a percentage model when headcount is low, salaries are relatively uniform, and you want the fee to scale with payroll size rather than pay a high fixed minimum per employee.

What additional fees appear on EOR invoices?

Beyond the headline administration fee, several charges commonly appear on invoices. One-off implementation fees at onboarding typically range from £0 to £2,500 per country depending on documentation and benefit setup complexity. Urgent off-cycle payroll runs are commonly priced at €50 to €250 per run per employee when they fall outside standard payroll calendars.

Termination processing fees, benefits administration charges, and amendment fees for contract changes can add up quickly. The providers that advertise the lowest monthly rates often recover margin through these ancillary charges. Ask for a complete rate card before signing, and specifically request examples of what a typical invoice looks like for a company with your profile.

What are the hidden costs in EOR pricing?

The EOR industry relies on what Teamed calls the Three Layers of Opacity: hidden FX margins, bundled compliance fees, and undisclosed in-country partner markups. Understanding these helps you identify where your money actually goes.

How do FX margins affect your total cost?

FX margin in EOR billing is the markup between the interbank exchange rate and the rate applied to convert your invoice currency into the payroll currency. A 1.0% to 3.0% spread on payroll conversions can add the equivalent of 0.3 to 1.0 months of EOR admin fees per year for EUR-to-non-EUR payroll corridors at mid-market volumes.

Most providers don't disclose their FX spread. To detect it, compare the rate on your invoice to the interbank rate on the same date. If you're funding payroll in a single currency and the provider converts to local currencies, you're likely paying a margin on every payroll cycle. Ask for spread disclosure clauses in your contract, or negotiate local-currency funding if your treasury can support it.

Why does your invoice vary month to month?

Invoice variance of 2% to 6% month-to-month is a common red flag for hidden variable charges. These include FX fluctuations, off-cycle payroll runs, benefit true-ups, and retroactive adjustments for items like tax corrections or social security recalculations.

In Spain, for example, employment contracts and payroll commonly require clear classification of salary components and statutory contributions. Retroactive corrections can trigger payroll recalculations that show up as true-ups on your EOR invoice months later. In the Netherlands, employers must typically pay at least 70% of salary during sickness for up to 104 weeks, which materially affects absence cost planning for EOR-employed workers.

If your invoices swing unpredictably, request line-item breakdowns that separate employee gross pay, employer on-costs, EOR administration fees, one-off charges, and FX costs. A provider that can't or won't provide this level of transparency is hiding something.

How do EOR costs vary by region?

Why does Spain cost more than Poland? Two reasons: employer taxes and compliance complexity. Spain hits you with 30% employer contributions and enough red tape to wallpaper your office.

What drives cost differences between European countries?

Western European countries typically carry employer on-costs in the 20% to 35% band of gross salary. France sits at the higher end with extensive social charges, while the UK falls lower. These statutory costs are separate from EOR fees but are invoiced together, which obscures the true administration cost.

Germany adds complexity through works councils, which become mandatory at 5+ employees if employees request them. France requires CSE (Social and Economic Committee) at 11+ employees. These requirements don't directly increase EOR fees, but they increase the compliance burden and the likelihood of issues that require human intervention rather than automated processing.

Countries with rigid labour laws and expensive terminations, like Spain with 33 days salary per year of service for objective dismissal, carry higher implicit risk. The EOR fee in these markets effectively includes insurance against compliance errors and labour court battles.

Why do Asia-Pacific and Latin American markets cost more?

High-complexity countries like Brazil, India, and the Philippines have very high termination costs, extensive mandatory benefits, and frequent regulatory changes. Brazil's labour code requires 13th-month salary, 8% monthly FGTS contributions, and 40% FGTS penalty on termination without cause. Total termination costs can exceed six months' salary.

The EOR fee in these markets reflects the administrative burden and litigation risk. While base salaries may be lower than Western Europe, the hidden cost of compliance is high. Teamed's analysis across 70+ countries shows that mid-market companies often underestimate total employment cost in these markets by 15% to 25% when they focus only on the quoted EOR fee.

Is an EOR expensive compared to alternatives?

Whether EOR is expensive depends entirely on your situation. For a company with 25 employees in a single country, EOR is almost certainly more expensive than owning your own entity.

When does EOR make financial sense?

Choose an EOR when you need to employ in a new European country in under 4 to 8 weeks without incorporating locally and you can accept a per-employee administration fee in exchange for speed and compliance infrastructure. EOR also makes sense when you're testing a market in your first 1 to 2 years, when headcount is below threshold for entity viability, or when employees are dispersed across many countries with fewer than 10 total.

The speed advantage is real. Entity establishment in Tier 1 countries like the UK, Ireland, or Singapore typically requires 2 to 4 months. Tier 2 countries like Germany, France, or Spain require 4 to 6 months. Tier 3 countries like Brazil, India, or China require 6 to 12 months. EOR gets people on payroll in days.

When should you consider establishing your own entity?

Time for your own entity? When you hit 10+ permanent employees in one country. When you need control over benefits and employment terms. When the EOR markup starts feeling like a tax on your success. Yes, entities mean more work. They also mean you stop paying someone else's margin.

Teamed's Graduation Model provides a framework for this decision. The optimal transition point varies by country complexity. Low-complexity countries like the UK, Singapore, or the Netherlands justify entity setup at 10+ employees. Moderate-complexity countries like Germany, France, or Spain warrant transition at 15 to 20 employees. High-complexity countries like Brazil, India, or China may justify staying on EOR until 25 to 35 employees.

The Crossover Economics calculation compares your annual EOR cost multiplied by expected years against entity setup cost plus ongoing annual entity costs. For a UK team of 10 employees, EOR at £7,500 per employee per year totals £225,000 over three years. An entity with £25,000 setup cost and £3,500 per employee per year totals £130,000 over the same period. The break-even point is around month 17.

What should you look for in EOR contract terms?

Contract terms matter as much as pricing. A low monthly fee means nothing if the contract allows unilateral fee changes, applies the admin fee to employer taxes, or limits liability to an amount below three months of fees.

Which contract clauses create cost surprises?

Watch for fee base definitions. A provider charging 10% on gross payroll plus employer taxes costs significantly more than one charging 12% on gross payroll alone in countries with high social contributions. Request explicit confirmation of what the percentage applies to.

Fee change clauses that allow unilateral increases with 30 days notice create unpredictable costs. Negotiate for annual price locks or caps on increases. Data retention clauses that limit access to payroll records after termination materially increase audit cost if you need historical data for compliance purposes.

What liability protection should you expect?

Liability caps tied to a few months of fees provide inadequate risk coverage for mid-market employers. If your EOR makes a compliance error that results in a six-figure tax penalty, a liability cap of £10,000 leaves you exposed.

Ask about audit rights, sub-processor disclosure, and fee change controls. Request the sub-processor list for any country where you'll have employees, particularly if data leaves the UK or EEA. GDPR requires a defined controller-processor allocation and a data processing agreement for HR and payroll data.

How do you reduce EOR costs without sacrificing compliance?

Cost reduction starts with understanding your actual spend. Most companies don't know their true cost per employee because invoices bundle administration fees, employer contributions, benefits, and pass-through costs without clear separation.

What questions should you ask your current provider?

Request a standardised breakdown that distinguishes fees charged on gross payroll versus payroll plus employer taxes versus payroll plus benefits. Ask for explicit FX spread disclosure. Demand line-item invoices that separate each cost component.

If your provider can't or won't provide this transparency, that's a signal. The providers who profit from opacity resist transparency. The providers who compete on value welcome it.

When should you switch providers or graduate to an entity?

Consider renegotiating or switching when the contract allows unilateral fee changes, applies the admin fee to employer taxes, or limits liability to an amount below three months of fees. These terms create predictable cost surprise and inadequate risk coverage.

Consider graduating to an entity when you've reached the employee threshold for your country tier, you're planning a 3+ year presence with stable or growing headcount, and you have HR and legal resources capable of managing local compliance. The Graduation Model provides continuity through a single advisory relationship, avoiding the disruption and re-onboarding that fragmented approaches require.

Making the right structural decision

Forget the monthly fee for a moment. What matters is whether EOR fits where you are today and whether your provider will tell you when it's time to graduate. The right structure at the right time, that's what actually saves money.

Most EOR cost guides quote a single fee and leave you to discover the hidden costs through painful invoice surprises. The Three Layers of Opacity, including FX margins, bundled compliance fees, and undisclosed partner markups, mean your actual cost is often 15% to 30% higher than the quoted rate.

The right structure for where you are. Trusted advice for where you're going. That's what separates a vendor from an advisor. If you're unsure whether EOR is still the right answer for your German team, or whether it's time to graduate to your own entity, book your Situation Room. We'll review your setup and tell you what we'd recommend, whether that includes us or not.

What are the estimated costs or time savings of outsourcing payroll in France versus in-house processing?

Outsourcing payroll in France typically costs €20–€45 per employee per month and reduces internal payroll cycle time by 30–60% compared to in-house processing. For a mid-market company with 50 employees, this translates to roughly €12,000–€27,000 annually in outsourcing fees versus 0.3–0.8 FTE of dedicated payroll staff for in-house operations. The right choice depends on your headcount, compliance confidence, and whether you have access to French payroll expertise internally.

Here's the reality most HR leaders discover too late: French payroll isn't just complex, it's a moving target. The Code du travail, DSN reporting requirements, prélèvement à la source withholding, and collective bargaining agreements create a compliance environment where mistakes carry real consequences—late DSN filings trigger penalties of €60 per employee per month. Teamed's payroll operations benchmarking shows that the cost inflection point typically occurs around 80–150 employees, where in-house processing becomes competitive only if you already have experienced French payroll expertise on staff.

We'll walk through the real costs and time commitments of both options, plus the decision points that matter. You'll have what you need to defend your choice in a finance review.

What teams actually spend and where the time goes

Most providers charge between €20 to €45 per employee per month for standard French payroll and DSN reporting. That's before any setup fees, and assumes you're running a single entity with monthly payroll and no complex variables.

Once you've got a stable process running, expect your payroll specialist to spend 15 to 45 minutes per employee each month. That's for a straightforward setup: single entity, monthly cycle, standard deductions.

With an outsourced provider, your team spends about 3 to 10 minutes per employee each month. You're sending over changes, checking the draft payroll, approving it, and dealing with the occasional outlier.

For 50 employees in France, you'll need someone spending two to four days a week on payroll. At 200 employees, that becomes one to two full-time people, especially when you're dealing with DSN, PAS, absences, and monthly variable pay.

One-off payroll implementation or migration costs in France commonly range from €1,500 to €10,000 depending on headcount and data complexity.

When you outsource, your internal payroll time can drop by 30% to 60%. Your provider handles the calculations, keeps up with regulatory changes, and produces the DSN. Your team handles the inputs and approvals.

When regulations change or you update policies, expect to spend an extra 5% to 15% of your time fixing errors. That means recalculating pay, correcting DSN submissions, and handling employee queries about why their payslip looks different.

How much does in-house payroll processing cost in France?

In-house payroll costs in France are dominated by fixed expenses: staff salaries, software licensing, and ongoing compliance maintenance. Unlike outsourcing, where costs scale predictably with headcount, in-house operations require upfront investment regardless of team size.

For a company with 50 France-based employees, you're looking at 0.3–0.8 FTE of dedicated payroll staff. At 200 employees, that figure rises to 1.0–2.0 FTE. These aren't arbitrary ranges. They reflect the reality that French payroll requires someone who understands DSN declarations, PAS withholding logic, collective agreement calculations, and the quarterly regulatory updates that affect gross-to-net calculations.

Software adds another layer. In-house payroll tooling for France commonly costs €5–€15 per employee per month in licensing fees. That's on top of your staff costs, not instead of them. You'll also need to budget for implementation, which can run €5,000–€15,000 depending on your pay structure complexity and integration requirements with existing HR systems.

The hidden cost most companies underestimate is compliance maintenance. France requires monthly DSN reporting, and the technical specifications change regularly. Someone on your team needs to monitor these changes, update your payroll software configuration, and verify that each month's submission aligns with current requirements. During periods of regulatory change, Teamed's payroll risk assessment framework shows that error remediation commonly adds 5–15% time overhead to in-house operations.

What does payroll outsourcing cost in France?

Outsourcing converts most of your payroll cost from fixed headcount to variable service fees. French payroll outsourcing typically prices at €20–€45 per employee per month for core payroll processing, DSN preparation, and standard reporting. This range reflects single-entity, single-country scope without complex HR administration add-ons.

One-off setup costs matter too. Implementation or migration projects commonly run €1,500–€10,000 depending on your headcount, number of pay elements, and data cleansing requirements. If you're moving from another provider or from in-house, expect the higher end of that range.

What's often missing from competitor comparisons is the hidden cost drivers that create budget variance. Per-off-cycle payroll runs, retroactive pay recalculations, DSN correction events, and interface fees with your HRIS can add 10–20% to your baseline outsourcing costs if your pay policies generate frequent exceptions. Before signing a contract, ask your provider explicitly how these scenarios are priced.

The trade-off is straightforward: outsourcing gives you predictable unit economics and shifts compliance burden to specialists, while in-house gives you control and potentially lower per-employee costs at scale. The question is where your company falls on that scale.

How much time does each model require from internal teams?

Time investment is where the outsourcing case becomes clearest for most mid-market companies. The difference isn't marginal. It's structural.

In-house payroll processing in France typically requires 15–45 minutes of payroll-specialist time per employee per pay cycle once the process is stable. That's just the calculation and submission work. Add variable data collection, absence reconciliation, and validation, and you're looking at 3–5 business days of cycle time for a monthly payroll run.

Outsourced payroll oversight requires 3–10 minutes of internal HR/Finance time per employee per pay cycle. Your team focuses on inputs review, approvals, and exception handling rather than calculations and DSN production. The provider absorbs the regulatory monitoring, software updates, and technical submission work.

For a 100-person French operation, that's the difference between roughly 25–75 hours of internal payroll work per month versus 5–17 hours. The time savings compound when you factor in the cognitive load of staying current with French employment law changes, collective agreement updates, and DSN technical specifications.

Teamed's operating model comparisons show that payroll outsourcing typically reduces internal payroll cycle time by 30–60% for mid-market employers. The freed capacity either reduces headcount requirements or redirects HR resources toward strategic work that actually moves the business forward.

What are the compliance implications of each approach?

France's payroll compliance requirements aren't optional, and the penalties for getting them wrong aren't trivial. The Déclaration Sociale Nominative is France's mandatory monthly digital payroll reporting file that transmits payroll and social contribution data to multiple French administrations through a single submission. Get it wrong, and you're dealing with URSSAF queries, employee complaints, and potential penalties.

In-house payroll places compliance responsibility entirely on your team. You need someone who can interpret the Code du travail, track collective bargaining agreement changes, and implement DSN technical updates as they're released. For companies without existing French payroll expertise, this creates single-point-of-failure risk. If your payroll specialist leaves, you're exposed until you can hire and train a replacement.

Outsourcing shifts compliance burden to the provider, but it doesn't eliminate your accountability. Your contract should explicitly define who is responsible for DSN submission, PAS withholding logic, and year-end reconciliations. Teamed's payroll governance benchmarks show that the most common compliance gaps occur when responsibilities are assumed rather than documented.

French employers must provide a compliant bulletin de paie to employees each pay period, including mandatory legal mentions and contribution breakdowns—failure to issue one can lead to fines of up to €450 per payslip. Whether you process in-house or outsource, the payslip must meet legal requirements. The difference is whether you're maintaining that compliance expertise internally or relying on a provider's specialisation.

For cross-border employers with France-based employees, payroll processing must align with local employment terms and statutory requirements even when corporate HR policies are defined outside France. This is where outsourcing often proves its value. Providers with French specialisation understand the nuances that trip up headquarters-driven payroll teams.

When should you choose payroll outsourcing in France?

Choose payroll outsourcing when you have fewer than 100 France-based employees and cannot justify hiring or retaining a dedicated French payroll specialist with DSN and PAS expertise. The economics simply don't work for maintaining in-house capability at that scale.

Outsourcing also makes sense when your organisation has frequent variable-pay changes, absences, or multiple collective bargaining considerations that would otherwise require continuous in-house regulatory monitoring. If your pay structure generates complexity, you're paying for that complexity either way. The question is whether you're paying for it through staff time or through provider fees.

CFOs who need predictable unit economics often prefer outsourcing because a PEPM contract converts a large portion of payroll cost from fixed headcount to variable service fees. You know what you're paying per employee, and that figure scales linearly with your French headcount.

Legal and Compliance teams frequently drive outsourcing decisions when they require documented controls, audit trails, and SLA-backed accountability for DSN/PAS preparation and payroll legislative updates. After a compliance scare, the value of having a provider on the hook for regulatory accuracy becomes much clearer.

When does in-house payroll processing make sense?

Choose in-house payroll processing when you have 150–300+ employees in France and can keep payroll policies stable enough to amortise specialist salaries and system costs across a larger headcount. At that scale, the per-employee cost of in-house processing can drop below outsourcing fees.

In-house also makes sense when payroll is tightly coupled with complex internal time and attendance, job costing, or bespoke bonus calculations that are difficult to standardise with an external provider. If your payroll inputs require constant interpretation and judgement calls, an external provider may struggle to deliver the accuracy you need without significant back-and-forth.

The hybrid model deserves consideration too. Some companies outsource payroll calculation and DSN production while keeping internal control of HR administration inputs like contracts, absences, and variable pay. This reduces data latency and exceptions while still offloading the technical compliance work.

Teamed's payroll TCO sensitivity analysis shows that the cost inflection point typically occurs around 80–150 employees in France. Below that range, outsourcing usually wins on economics. Above it, in-house becomes competitive, but only if you have the expertise to execute it.

What hidden costs should you factor into your decision?

Most payroll comparisons fail because they compare headline rates without accounting for the full cost picture. Here's what actually drives total cost of ownership.

For in-house operations, factor in recruitment and retention costs for French payroll specialists, ongoing training to maintain regulatory currency, software licensing and upgrade costs, and the productivity impact of payroll errors during policy changes or statutory updates. Don't forget the opportunity cost of HR leadership time spent managing payroll operations rather than strategic initiatives.

For outsourcing, look beyond the PEPM rate. Ask about pricing for off-cycle payroll runs, retroactive calculations, DSN corrections, and HRIS interface maintenance. Understand what's included in the base fee versus what triggers additional charges. Implementation costs can vary significantly based on your data quality and pay structure complexity.

Both models carry transition costs. Switching from one provider to another or moving from in-house to outsourced requires parallel runs, data migration, and process documentation. Budget 2–3 months of overlap and expect some efficiency loss during the transition period.

The graduation model that Teamed uses with clients recognises that the right payroll structure changes as your French operation grows. A company with 20 employees in France has different needs than one with 200. The best approach isn't static. It evolves with your headcount, complexity, and strategic priorities.

How do you make the right decision for your company?

Start with your current state: how many employees do you have in France, what's your payroll complexity, and do you have French payroll expertise on staff? If you're below 80 employees and don't have a dedicated French payroll specialist, outsourcing is almost certainly the right answer.

If you're in the 80–150 employee range, run the numbers. Calculate your actual in-house costs including staff time, software, and compliance maintenance against outsourcing quotes. Include the hidden cost drivers on both sides. The answer may not be obvious, and it may depend on factors specific to your organisation.

Above 150 employees, in-house becomes viable, but only with the right expertise. If you're considering in-house at scale, make sure you have access to French payroll specialists who can maintain compliance through regulatory changes and collective agreement updates—after January 2024's SMIC revaluation alone, 105 branches became non-compliant, affecting nearly 6.9 million employees.

For mid-market companies managing France as part of a broader European or global footprint, the payroll decision often connects to larger questions about employment structure. Teamed's GEMO approach, which stands for Global Employment Management and Operations, helps companies think through these decisions holistically rather than country by country.

If you're weighing your options and want a clear-eyed assessment of what makes sense for your specific situation, book your Situation Room. We'll review your current setup and tell you what we'd recommend, whether that includes us or not.

A simple rule of thumb (and when it breaks)

The outsourcing versus in-house question doesn't have a universal answer. It depends on your headcount, your access to French payroll expertise, your tolerance for compliance risk, and your CFO's preference for fixed versus variable cost structures.

What's clear is that French payroll complexity isn't going away—employers in France pay 26.7% of labour costs in social contributions, the highest share in the OECD. The DSN requirements, PAS withholding, collective agreement calculations, and quarterly regulatory updates create an environment where expertise matters. Whether you build that expertise internally or buy it from a provider, the cost of getting it wrong exceeds the cost of getting it right.

For most mid-market companies with fewer than 100 employees in France, outsourcing delivers better economics, lower risk, and freed HR capacity. Above 150 employees, in-house becomes competitive if you have the right people. In between, run the numbers and make the decision based on your specific situation rather than generic advice.

Local Entity vs EOR Costs: Finding Your Crossover Point

Author: Tom Price-DanielReading time: 11 minCategory: Global employment

This article is for informational purposes only and does not constitute legal, tax, or compliance advice. Always consult a qualified professional before acting on any information provided.

When does it make sense to set up your own entity instead of using an EOR?

You've just acquired a team of 15 in Germany, and your CFO wants a board-ready answer by Friday: should you set up a GmbH or use an EOR? The spreadsheet you've been building has more assumptions than facts, and the quotes you're getting from providers don't seem to include the same cost components.

Here's what most comparison articles won't tell you. The EOR versus entity decision isn't a one-time calculation. It's a moving target that changes as your headcount grows, your market commitment solidifies, and your operational capacity evolves. The right structure for where you are today won't be the right structure in 18 months.

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 their own presence in-country.

The question isn't which option costs less today. It's when the economics shift in favour of an entity, and whether your provider will actually tell you when that happens.

Quick facts: EOR vs entity cost comparison

Most EOR providers in Europe charge €300 to €900 per employee per month. That's before extras for senior hires, union environments, or complex benefit packages.

Employer social costs in Europe add 15 to 35% on top of salary. When you compare EOR to entity costs, you need the total employment cost, not just the service fee.

Entity setup in Tier 1 countries like the UK typically runs £20,000 to £30,000 all-in: legal formation, banking, and initial tax registration. In Tier 2 countries like Germany or France, it's £30,000 to £60,000. Setup takes 4 to 12 weeks if nothing goes wrong, and banking is usually the bottleneck. In Germany, a business account can take eight weeks on its own.

The Crossover Point is country-specific, not universal. In Tier 1 markets, the economics only start to favour entity ownership at 15 to 20 employees with a 3+ year commitment. In Tier 2, 20 to 30. In Tier 3, 30 to 40.

And the maths is only one of five conditions that need to hold: headcount concentration, long-term commitment, economic viability, control requirements, and operational readiness. Miss any one of them, and EOR is still the right answer. We walk through all five below.

What does setting up a local entity actually cost?

A local entity is a legally registered company presence in a specific country (for example a UK Ltd, German GmbH, or French SAS) that enables direct employment, local payroll registration, and in-country tax and statutory reporting under the employer's own name.

The costs fall into two categories that most comparison articles conflate: one-time setup costs and ongoing operational expenses. Mixing these together produces misleading conclusions.

One-time setup costs

Entity incorporation fees vary dramatically by jurisdiction. A UK Ltd costs roughly £2,000 to £5,000 in legal and filing fees, while a German GmbH requires €25,000 minimum share capital plus €3,000 to €8,000 in notary and registration costs.

Beyond incorporation, you'll need local banking (often the slowest step, taking 4 to 8 weeks in Germany), tax registration with multiple authorities, employer registration for social security, and initial accounting setup. Budget £15,000 to £30,000 total for a straightforward Tier 1 country like the UK or Netherlands, and £30,000 to £60,000 for Tier 2 countries like Germany or France with more complex requirements.

Ongoing operational expenses

This is where most cost comparisons fall apart. Your ongoing costs include local accounting and statutory filings (£500 to £2,000 monthly depending on complexity), payroll processing (£50 to £150 per employee monthly), HR administration and compliance monitoring, director responsibilities and corporate governance, and VAT registration and indirect tax compliance.

After advising over 1,000 companies, we've found that running an entity costs £3,000 to £5,000 per employee per year for accounting, payroll, compliance, and admin. That's the invoice figure. The fully-loaded figure, including a realistic share of internal finance, HR, and legal time, is usually closer to £5,000 to £7,000 per employee per year in a Tier 1 country. Neither figure includes salary or benefits.

What does EOR actually cost when you include everything?

An Employer of Record is a third-party organisation that becomes the legal employer of a worker in a specific country. The EOR runs payroll, statutory withholdings, and local employment compliance while the client company directs day-to-day work.

The headline EOR fee you see in proposals rarely tells the full story. The Three Layers of Opacity framework identifies three common sources of hidden EOR spend that can cause the invoiced cost to diverge significantly from the quoted price.

Where the extra costs hide

First, FX margins on payroll funding. When you fund payroll in GBP for employees paid in EUR, the conversion rate applied often includes a 1 to 3% markup that never appears as a line item. On a €100,000 annual salary, that's €1,000 to €3,000 in hidden costs per employee.

Second, bundled compliance fees. Setup fees, offboarding fees, contract amendment fees, and "compliance management" charges get added throughout the relationship. These can add 10 to 20% to your effective per-employee cost.

Third, undisclosed in-country partner markups. Many EOR providers don't operate their own entities in every country. They use local partners who add their own margin, which gets passed through to you without transparency.

The real all-in EOR cost

When you account for all three layers, the true cost of EOR employment in Europe typically runs €8,000 to €15,000 per employee annually, on top of their compensation. For a team of 10 in Germany, that's €80,000 to €150,000 per year in EOR costs alone.

This is why CFOs who've been through the experience often describe EOR invoices as "never adding up." The quoted €500 per month somehow becomes €900 when you reconcile actual spend.

At 10 employees paying €500 each per month, EOR becomes a €60,000 per year line item. That's when finance teams typically start modelling alternatives. It's not necessarily when they should switch. The spend is visible. That's different from the economics being right.

When does entity setup become more cost-effective than EOR?

Crossover Economics is how we calculate when an entity becomes cheaper than EOR. It's the point where setup costs plus ongoing entity expenses drop below your total EOR spend.

The calculation isn't complicated, but it requires honest numbers on both sides. The formula: (Annual EOR cost × projected years) compared against (Setup cost + (annual entity cost × projected years)).

A concrete example: UK operations

Take a UK company with 10 employees in the UK. Compare EOR at £7,500 per employee annually against entity ownership at a fully-loaded £5,750 per employee annually, plus £25,000 setup.

The £5,750 figure includes outsourced accounting and statutory filings, payroll processing, HR admin, compliance monitoring, director support, and a realistic share of internal finance and legal time. The £3,000 to £5,000 range some providers quote usually excludes internal time. That understates the true cost.

Over three years, the EOR model costs £225,000 (10 × £7,500 × 3). The entity model costs £197,500 (£25,000 setup, plus 10 × £5,750 × 3). The Crossover Point sits at around 17 months, and cumulative savings by year three are £27,500.

That's a real saving. It's also £27,500 set against operational and governance risk you're now carrying directly. At 10 employees, the decision is genuinely close. Many companies are better off waiting until 15 to 20 employees before graduating, where annual savings move closer to £60,000 and the economics stop being marginal.

This is why we calculate the Crossover Point country by country, not as a universal rule. A blanket "10 employees equals entity" threshold, which you'll see in some comparison articles, usually overstates the case.

Country complexity changes the thresholds

The Crossover Point varies by country complexity. The Country Concentration Framework sets three tiers based on regulatory burden, termination cost, and administrative complexity.

Tier 1 countries (UK, Ireland, Singapore, Netherlands): consider entity formation from 10 employees, but the economics usually only become compelling at 15 to 20 with a 3+ year commitment. Below that, the annual saving is often too small to justify the operational overhead.

Tier 2 countries (Germany, France, Spain, Italy): wait until 20 to 30 employees. Works council thresholds in Germany (from 5 employees), the 35-hour workweek in France, and collective agreement complexity across southern Europe all add ongoing cost that's not captured in the per-head entity figure.

Tier 3 countries (Brazil, China, India, Indonesia): stay on EOR until 30 to 40 employees. The compliance risk and administrative burden make the EOR fee an effective insurance premium against problems that cost far more than the service.

These are starting points, not rules. A provider that applies them as hard thresholds without reviewing your specific situation isn't advising, they're automating.

What strategic factors matter beyond the cost calculation?

Cost is necessary but not sufficient for this decision. Several strategic considerations can override pure economics.

Speed to hire

EOR onboarding can happen in as little as 24 hours. Entity establishment takes 2 to 6 months depending on jurisdiction. If you need people on payroll in France next month, EOR is your only compliant option regardless of cost.

Market commitment uncertainty

If you're testing a new market and exit probability exceeds 30%, stay on EOR. Winding down an entity requires ongoing filings and formal closure processes even after staff exit. EOR exit is limited to employment termination steps and account offboarding.

When you need direct control

Some enterprise customers require contracting with local entities. Certain IP structures require your own entity for proper protection. Direct bank account control may be necessary for treasury management. If any of these apply, entity establishment becomes a strategic requirement rather than a cost optimisation.

Do you have the team to run it?

Do you have HR and legal resources capable of managing local compliance? In Germany, dismissals can be challenged in labour courts, with strict procedural requirements and potential reinstatement risk. In France, the statutory 35-hour workweek framework requires local policy design and documentation discipline. Without the internal capacity to manage these requirements, the EOR fee buys you expertise you'd otherwise need to build.

How should you approach the EOR vs entity decision for your situation?

The Graduation Model shows the natural progression most companies follow: start with contractors, move to EOR as you need more control, then establish an entity once you're committed to the market. Each stage has clear triggers based on headcount and business needs. One relationship throughout.

When to stay on EOR

Stay on EOR when you need a compliant employee on payroll in 24 hours to a few weeks, and you cannot justify the 4 to 12 week lead time of entity formation. The speed advantage alone can be worth more than any cost saving.

Stay on EOR when headcount in a country is likely to stay below the Tier 1, 2, or 3 threshold above. Below those numbers, entity economics usually lose to EOR once you price internal time honestly.

Stay on EOR when market commitment is uncertain. If the probability of winding the market down inside three years is meaningful, the exit cost of a dormant or closed entity will wipe out any in-life savings.

Stay on EOR when your internal HR, legal, and finance capacity isn't ready to run a local entity. Without that capacity, the EOR fee buys you expertise you'd otherwise need to build.

Stay on EOR when you're testing, not committing. The Graduation Model exists so you don't have to decide early. Contractor to EOR to entity, one relationship throughout. You graduate when the evidence is clear, not when a spreadsheet says you could.

When to choose entity establishment

Choose a local entity when you expect a stable footprint of 15+ employees in a Tier 1 country for 12+ months and you want to reduce recurring per-employee EOR fees through scale economics.

Choose entity when you need direct control over employment terms, benefits design, works council engagement, or local policies that are difficult to standardise through an EOR template.

Choose entity when procurement or finance policy requires direct contracting with local benefit providers rather than relying on an intermediary's master policies.

When to use a hybrid approach

Choose a hybrid model when you're entering multiple European countries at once, using EOR for initial hires while setting up entities only in the 1 to 3 countries that show sustained hiring velocity. This approach requires effective platform consolidation to manage both models efficiently. This is where the Graduation Model provides its greatest value: EOR for speed and flexibility, graduating to entity ownership as the economics and operational readiness align.

What do most cost comparisons get wrong?

Most comparisons look at EOR fees versus incorporation costs and call it done. But CFOs need the full picture: employer taxes shown separately from service fees, benefits broken out from markups, FX margins visible as their own line. Without that detail, you can't make an informed decision.

The result: companies either overpay for EOR far past the Crossover Point, or establish entities prematurely before they have the operational capacity to manage them. Both mistakes are expensive.

Your EOR doesn't want you to leave

Here's what most providers won't tell you. Incumbent EOR providers are structurally incentivised never to surface the Crossover Point, because every month past that threshold is pure margin for them. A systematic evaluation of your EOR can reveal whether you're past it. Nobody models the crossover for the customer. Nobody flags it. Nobody builds migration tools.

This is why our approach differs. When a customer graduates from EOR to entity management, they don't leave teamed. They move to a product with lower per-head fees but dramatically higher lifetime value. We're economically aligned with having the conversation about when entity setup makes sense, even when that means advising you to change. Thinking ahead is the service.

The exit cost blind spot

Most sources overlook exit costs entirely. A differentiated analysis must model the full lifecycle cost, including redundancy and notice exposure, entity dormancy costs, and the time-to-close burden when a market experiment fails.

In the Netherlands, employers must typically continue paying wages during employee sickness for up to 104 weeks. In Spain, employment contracts and termination documentation are highly formalised and commonly require local-language compliant templates. These aren't just compliance details. They're material cost factors that affect your total cost of ownership.

How do you build a board-ready cost comparison?

A country-by-country model comparison is typically more accurate than a single global rule, because employer costs, termination risk, and entity admin burden vary sharply across Europe. We recommend doing the crossover calculation at the jurisdiction level rather than averaging across countries.

How you know you're ready to run an entity

After guiding over 1,000 companies through this decision, we've found five criteria that matter. You need all five before making the switch.

First, employee concentration: have you reached or exceeded the threshold for your operating tier in that country (15 to 20 for Tier 1, 20 to 30 for Tier 2, 30 to 40 for Tier 3)?

Second, long-term commitment: are you planning a 3+ year presence in the market with stable or growing headcount?

Third, economic viability: do your annual EOR costs multiplied by expected years exceed entity setup cost plus ongoing annual costs, with internal time priced in?

Fourth, control requirements: do you need direct control over local operations, intellectual property protection, or customer contracts?

Fifth, operational readiness: do you have HR and legal resources capable of managing local compliance?

Missing even one? Stay on EOR. The headaches aren't worth it.

What this means for your next board meeting

The EOR versus entity decision isn't about finding the cheapest option. It's about finding the right structure for where you are, with trusted advice for where you're going.

Most mid-market companies will use both models at different stages and in different countries. The question is whether anyone is proactively advising you on when to transition, or whether you're left to figure it out yourself while your current provider profits from your uncertainty.

If you're approaching a Crossover Point, or you're not sure whether you've already passed it, we can help. Tell us your setup, and we'll tell you what we'd recommend, whether that includes us or not. Talk to an expert for a clear-eyed assessment of your global employment structure and the economics of your options.

‍

Top 10 Challenges in HR Payroll Management in 2025 & Solutions

Your payroll just failed in Germany. The tax filing was late, the employee's social insurance contribution was miscalculated, and now you're staring at a compliance notice you don't fully understand. Your provider's response? A chatbot.

This is the reality for mid-market companies managing global payroll in 2025. You're running 3-8 distinct payroll providers across countries, reconciling data manually between systems, and making six-figure employment decisions with incomplete information. The challenges aren't new, but they're intensifying as regulatory complexity accelerates and workforce distribution expands.

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 seen these payroll challenges destroy careers and derail expansions. Here's what's actually breaking in 2025 and how to fix it.

Quick Facts: HR Payroll Challenges in 2025

UK employers must retain PAYE payroll records for at least 3 years from the end of the tax year, creating minimum audit trail requirements that many global systems fail to meet.

GDPR allows administrative fines up to €20 million or 4% of annual worldwide turnover for payroll data breaches, making security failures potentially material financial risks.

Mid-market companies expanding internationally commonly end up running 3-8 distinct payroll providers across countries, increasing reconciliation workload exponentially.

The most frequent root cause of cross-border payroll errors is upstream data change failures (joiners, leavers, salary changes) rather than gross-to-net calculation engines.

Payroll consolidation programmes typically take 8-16 weeks for first-country go-live when HRIS and finance integrations are in scope.

A practical payroll variance-control baseline requires finance sign-off when total employer cost moves more than 1-2% month-on-month without explained headcount change.

What Are the Top Payroll Challenges in 2025?

The payroll challenges hitting hardest in 2025 fall into five categories: regulatory compliance across jurisdictions, technology integration failures, data security vulnerabilities, remote workforce complexity, and cost management opacity. Each challenge compounds the others, creating cascading failures that surface at the worst possible moments.

What makes 2025 different is the convergence of accelerating regulatory change, distributed workforce models becoming permanent, and AI tools being deployed without proper payroll-grade controls. Companies that solved payroll five years ago are discovering their solutions no longer work.

How Does Global Regulatory Compliance Create Payroll Failures?

Global payroll compliance fails when companies treat multi-country operations as a single-country problem scaled up, with 57% of payroll professionals citing local compliance as their biggest global payroll challenge. Each jurisdiction requires specific statutory filings, social security contributions, and payment timing that cannot be standardised without local expertise.

Germany requires employers to run payroll with statutory social insurance reporting and wage tax withholding aligned to German health insurance fund data. France payroll requires careful handling of social contributions and DSN reporting obligations. The UK's Real Time Information system requires Full Payment Submission on or before each pay date. Miss any of these, and you're facing penalties, employee coverage gaps, or both.

Why Do Most Providers Miss Compliance Requirements?

Most payroll providers sell simplicity that hides real complexity. When complex cases arrive, they route you to a chatbot or an offshore queue. The provider that promised expertise delivers a platform, and you discover the gap when HMRC or the Finanzamt sends a notice.

UK IR35 rules require medium and large organisations to make and document status determinations for contractor engagements. HMRC can pursue unpaid tax with assessment windows extending back multiple years. This isn't a feature you can automate without genuine in-market legal expertise backing every determination.

The solution isn't more technology. It's having real people with local knowledge who pick up the phone when it matters. Choose a provider that carries local employment compliance obligations rather than passing them back to you in the fine print.

Why Does Technology Integration Fail for Global Payroll?

Payroll automation fails when deployed without a stable payroll data model. Most 2025 payroll content lists AI and automation as solutions but doesn't specify the payroll-grade controls that make automation auditable for CFO and legal sign-off.

A payroll data model is a defined set of fields, formats, and validation rules that enables consistent payroll calculations across systems and countries. Without this foundation, automation accelerates errors rather than reducing them. You're not fixing problems faster; you're creating them faster.

What Controls Make Payroll Automation Actually Work?

Payroll controls are documented, repeatable checks that reduce error, fraud, and non-compliance risk. The three essential controls are maker-checker approvals, variance thresholds, and reconciliations. Every payroll run should require two reconciliations: gross-to-net to payment file, and payroll to general ledger.

Choose payroll automation when you can define standard data fields and approval points. If your current setup requires more than two manual handoffs between HR, finance, and local providers, each handoff is a control break that increases error and audit risk. Provider consolidation becomes the prerequisite for successful automation, not the other way around.

How Do Data Security Failures Create Payroll Risk?

GDPR treats payroll data as personal data requiring lawful basis, security, and data minimisation controls. Payroll datasets contain bank details, national identifiers, and salary information that require stricter access segmentation than general HR systems, particularly given the 12,412 data breaches reported to the UK ICO in 2024/25. Most guidance on payroll security doesn't distinguish between payroll systems and broader HR systems, even though payroll contains payment instructions that demand separate incident-response playbooks.

Role-based access and data retention schedules become core payroll compliance requirements across Europe. In the UK, National Minimum Wage records must be kept for at least 6 years, meaning payroll retention policies often need to exceed PAYE's three-year minimum when hourly pay or salary-sacrifice arrangements exist.

What Security Architecture Protects Payroll Data?

Separate your payroll system access from general HRIS access. The person who updates employee addresses shouldn't automatically have access to bank account details. Implement audit trails that capture who accessed what data and when, because regulators will ask.

Cloud payroll differs from on-prem payroll in that cloud typically supports continuous vendor updates for statutory changes. On-prem payroll relies on internal patching cycles that can lag regulatory change windows. For most mid-market companies, cloud payroll with proper access controls provides better security than on-prem systems they can't adequately maintain.

What Makes Remote Workforce Payroll So Difficult?

Most guidance on remote-work payroll focuses on paying people in multiple countries but omits operational reality. Parallel runs, bank payment testing, and statutory registration lead times are the actual timeline drivers for payroll consolidation. You can't just add a country to your payroll system and start paying people next week.

The EU Working Time rules require accurate tracking of working time for many worker categories. Payroll accuracy depends on time and absence data being captured in a way that can be evidenced in audits and disputes. When employees work across time zones with flexible schedules, this tracking becomes exponentially more complex, especially as 65.57% of EU enterprises now provide remote access to business applications.

How Do You Build Payroll Infrastructure for Distributed Teams?

Start by accepting that payroll consolidation takes 8-16 weeks for first-country go-live when integrations are in scope. The critical path runs through parallel runs, statutory registration timing, and bank payment testing. Rushing this process creates the compliance failures you're trying to avoid.

Choose an Employer of Record when you need to employ workers in a new country in under 6-8 weeks without setting up a local entity. An EOR becomes the legal employer, handling payroll, statutory taxes, and employment compliance while you direct day-to-day work. This buys you time to build proper infrastructure while maintaining compliance from day one.

Why Does Payroll Cost Management Fail?

Cost management fails because most providers mark up pass-through costs, bury FX margins, and don't provide line-item breakdowns, while 38% of organizations don't track payroll performance at all. You never know the true cost of employment. This is one of the three layers of opacity the EOR industry relies on: hidden FX margins, bundled compliance fees, and undisclosed in-country partner markups.

When your CFO asks why payroll costs increased 15% this quarter, you should be able to answer with specific line items. If you can't, your provider is profiting from your confusion.

How Do You Gain Visibility Into True Payroll Costs?

Require itemised invoices that separate base salary, employer contributions, provider fees, and currency conversion costs. A practical variance-control baseline requires finance sign-off when total employer cost moves more than 1-2% month-on-month without explained headcount change. Unexplained variance is a leading indicator of data or compliance issues.

Choose provider consolidation when payroll requires more than two manual handoffs between HR, finance, and local providers. Most sources talk about consolidation without quantifying governance artifacts: single payroll calendar, standardised data model, and two-step reconciliations to bank and general ledger. These are the practical checkpoints that create audit readiness.

When Should You Transition From EOR to Your Own Entity?

The Graduation Model describes the natural progression companies follow as they scale international teams: contractor to EOR to entity. Teamed proactively advises when to move to the next stage, even when it means moving off EOR. Most providers never have this conversation because every month past the crossover point is pure margin for them.

Choose a local entity when you expect sustained in-country hiring, need direct control over benefits and policies, or your CFO requires long-term cost optimisation beyond EOR per-employee fees. The crossover point typically arrives at 10-30 employees depending on jurisdiction complexity.

What Signals Indicate You've Outgrown Your Current Structure?

Your employment structure needs evaluation when headcount in a single country approaches 10-15 employees, when you're planning a 3+ year presence in that market, or when your annual EOR costs multiplied by expected years exceed entity setup cost plus ongoing annual costs.

Choose a contractor-to-EOR-to-entity roadmap when headcount in a country is expected to grow over time. This approach, which Teamed calls Global Employment Management and Operations (GEMO), maintains one advisory relationship across every transition rather than forcing you to find new providers at each stage.

Which HR Software Works Best for Global Payroll?

The best HR software for global payroll depends on your company size, geographic footprint, and employment model complexity. For mid-market companies managing contractors, EOR employees, and owned entities across multiple countries, the priority should be unified global employment operations rather than adding another point solution.

Global payroll differs from multi-currency payroll in that global payroll must meet local statutory filing and employment-law requirements country-by-country. Multi-currency payroll can still be a single-country payroll that simply pays in different currencies. Don't confuse the two when evaluating solutions.

An EOR differs from a payroll bureau in that an EOR is the legal employer and owns employment compliance. A payroll bureau processes pay calculations for your legal entity but doesn't replace your employer obligations. Understanding this distinction prevents costly misalignments between what you need and what you're buying.

What Are the Four Types of Payroll Systems?

The four payroll system types are in-house payroll, outsourced payroll bureau, Employer of Record, and global payroll consolidation platforms. Each serves different company stages and complexity levels.

In-house payroll works when you have dedicated expertise and operate in few jurisdictions. Outsourced payroll bureaus handle calculations but leave compliance obligations with you. EOR providers become the legal employer and carry compliance responsibility. Global payroll consolidation platforms attempt to standardise processing across countries while you maintain employer status.

Choose contractors only when the role can be delivered with genuine independence: control over how work is done, ability to substitute, and no integration into employee-only processes. Contractor-like payroll convenience doesn't offset misclassification exposure.

How Do You Build a Payroll Consolidation Roadmap?

Payroll consolidation is the process of reducing provider numbers and standardising data, approvals, and reporting so you can run payroll with fewer handoffs and more consistent controls. Start by mapping your current state: how many systems, what employment models in each country, and where the visibility gaps exist.

Companies with more than 2 countries of employment should assume payroll month-end close requires at least two reconciliations. Each missed reconciliation increases risk of undetected overpayments or incorrect employer tax accruals. Build these checkpoints into your consolidation plan from day one.

The consolidation timeline depends on integration scope. With HRIS and finance integrations, expect 8-16 weeks for first-country go-live. Without integrations, you can move faster but sacrifice the automation benefits that justify consolidation in the first place.

Moving Forward With Payroll Confidence

The payroll challenges of 2025 aren't going away. Regulatory complexity will increase. Workforce distribution will expand. The providers who profit from confusion will continue obscuring costs and routing you to chatbots when you need expertise.

The solution isn't more technology deployed without controls. It's having one advisory relationship across all markets and models, with real people who understand your specific situation and pick up the phone when it matters. It's knowing when your current structure no longer serves you and having a partner who tells you the truth about that, even when it means advising you to change.

If you're spending hours reconciling data across systems, making critical employment decisions with incomplete information, or piecing together advice from vendors with conflicting incentives, there's a better way. Book your Situation Room and tell us your setup. We'll tell you what we'd recommend, whether that includes us or not.

How do UK sick pay changes affect international employers?

Your company is headquartered in Singapore, but you've got eight employees working from London. On 6 April 2026, UK statutory sick pay rules changed significantly. Does that affect you?

Yes. UK employment law applies based on where your employees work, not where your company is registered. If you employ anyone in the UK through any structure, whether that's your own entity, an Employer of Record, or even contractors who might be misclassified, the April 2026 SSP reforms create new obligations and cost exposure you need to understand.

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. This guide explains exactly what the SSP changes mean for international employers and what you should do about them.

What changes on payroll Monday morning

If the work happens in London, the UK rules show up on your payslip run. Your Delaware incorporation won't change that.

From 6 April 2026, SSP is payable from the first day of sickness absence, eliminating the previous three waiting days.

The Lower Earnings Limit is gone. Your part-timers and low-hour roles now qualify for SSP when they didn't before.

Lower earners get 80% of their Average Weekly Earnings instead of the flat rate. Your payroll system needs to handle this calculation.

UK SSP can be paid for up to 28 weeks per period of sickness, creating a predictable cap even when entitlement triggers earlier.

This hits your payroll bill directly. No government reimbursement. If you use an EOR, they may pass it through on your invoice.

The Fair Work Agency handles enforcement. They look at where the work happens, not where you're based.

What changed on 6 April 2026?

Three changes hit on 6 April 2026: no waiting days, no earnings limit, new calculation for lower earners.

The first change eliminates waiting days entirely. Previously, employees had to be off sick for four consecutive days before SSP kicked in, with the first three days unpaid. Now SSP is payable from the first qualifying day of sickness. For international employers, this means any short-term absence now triggers a payment obligation where none existed before.

The second change removes the Lower Earnings Limit. Before April 2026, employees earning below £123 per week weren't entitled to SSP at all. That threshold is gone. Every employee on your UK payroll now qualifies, regardless of their earnings level, expanding eligibility to 1.3 million employees who were previously excluded. If you have part-time UK staff who previously fell below the LEL, they're now covered.

The third change introduces a new calculation method for lower earners. Employees earning below the flat SSP rate now receive 80% of their Average Weekly Earnings instead. This requires more complex payroll calculations than the previous flat-rate approach.

Do UK sick pay rules apply if my company isn't based in the UK?

UK employment law protections, including statutory sick pay rules, apply based on where the worker is employed and works. Your company's country of incorporation is irrelevant to this determination.

If you have employees working in the UK, UK statutory obligations attach to that employment relationship. A German company with five people in Manchester has the same SSP obligations as a UK company with five people in Manchester. The Fair Work Agency, which enforces employment rights, doesn't care where your headquarters are located.

This principle catches many international employers off guard. They assume that because they're not a UK company, UK employment law doesn't apply to them. That assumption is wrong and creates significant compliance risk.

How do SSP obligations differ by employment structure?

Your obligations under the new SSP rules depend entirely on how you've structured your UK employment. There are three common scenarios for international employers, and each carries different responsibilities and risks.

Scenario one: You have a UK entity and run payroll in-house

If you've established a UK subsidiary or branch and operate your own PAYE scheme, you are the legal employer. SSP obligations fall directly on your UK entity. You must ensure your payroll system can calculate statutory entitlement under the new rules, apply evidence requirements like fit notes where relevant, and document absence decisions for auditability.

UK employers must operate PAYE and submit payroll information to HMRC under Real Time Information rules. Penalties for late RTI submissions can be charged monthly, and repeated late filing creates accumulating compliance costs that are easy to overlook with small UK teams.

UK entity makes sense when you've got 10+ people, permanent presence plans, finance wants direct control, or you're setting up recurring UK benefits.

Scenario two: You use an EOR to employ UK staff

An Employer of Record becomes the legal employer for your UK workers, running local payroll, statutory deductions, and employment compliance while you direct day-to-day work. Under this structure, the EOR holds legal responsibility for SSP payments.

Using an EOR for UK hires shifts legal employer responsibility for statutory payments and payroll compliance to the EOR. However, you still carry operational and reputational risk if employee experience or statutory handling fails. If your EOR mishandles an SSP claim, your employee suffers the consequences and your company's reputation takes the hit.

EOR pricing for the UK is commonly structured as a recurring monthly fee per employee plus pass-through statutory costs. Teamed advises clients to confirm whether SSP is treated as pass-through or included in the fee to avoid invoice surprises when the new rules increase SSP frequency.

EOR works when you need speed, don't want UK entity overhead yet, and can accept the trade-off of indirect control for compliance simplicity.

Scenario three: You use contractors in the UK

Here's where many international employers get caught out. If you're engaging people in the UK as contractors but the relationship looks more like employment, you face misclassification risk. A reclassified worker can claim worker rights including paid holiday and statutory payments, in addition to tax authority actions.

Contractor-to-employee reclassification in the UK can create backdated liabilities covering taxes and National Insurance contributions. Teamed's compliance team advises modelling downside exposure over multiple prior tax years rather than a single quarter.

The April 2026 SSP changes increase the stakes of misclassification. Previously, if a contractor was reclassified, SSP exposure only applied after three waiting days and only if they earned above the LEL. Now, day-one entitlement and universal eligibility mean any misclassified contractor could trigger immediate SSP obligations for any sickness absence.

Contractors work when you need genuine independence: project-based work, clear deliverables, they control how and when they work, and can send someone else if needed.

What's the cost impact for a small UK team?

Here's a back-of-napkin calculation: US company, ten London employees at £45,000 each. What do the new rules cost?

Under the old rules, a two-day illness triggered no SSP payment because of the three waiting days. Under the new rules, that same two-day absence now costs approximately £49 in SSP (two days at the weekly rate of £123.25, pro-rated).

That sounds small. But multiply it across ten employees, each taking an average of 4.4 sick days per year, and you're looking at roughly £1,600 in additional annual SSP costs that didn't exist before April 2026.

The bigger impact comes from employees who previously earned below the Lower Earnings Limit. If you have part-time UK staff, they're now entitled to SSP where they weren't before. A part-time employee earning £100 per week who takes a week off sick now receives £80 in SSP (80% of AWE), whereas previously they received nothing.

For CFOs at international companies, the key insight is this: UK statutory payments aren't "handled in benefits." SSP is a payroll statutory item that must be processed through the legal employer's payroll. Even a five-person UK team can trigger employer obligations across PAYE, NICs, and statutory payments, and Teamed advises budgeting compliance overhead as a recurring operating cost rather than a one-time setup cost.

What enforcement risks do international employers face?

The Fair Work Agency enforces employment rights in the UK, including SSP compliance. Penalties apply to the legal employer, which means your UK entity if you have one, or your EOR if you're using that structure.

But enforcement risk isn't just about fines. HMRC can investigate payroll compliance, and weak recordkeeping increases risk during reviews or employment disputes. UK employers must retain payroll and statutory payment records for compliance purposes.

If you use an EOR, legal liability sits with them. But reputational risk sits with you. An employee who doesn't receive their statutory sick pay will blame your company, not your EOR. They'll tell their colleagues. They might post about it online. The employment relationship is with you in practice, even if the legal relationship is with the EOR.

For international employers, the practical enforcement risk is often less about government action and more about employee relations. Getting SSP wrong damages trust and retention in ways that compound over time.

What should international employers do now?

After watching too many SSP surprises land on finance desks, here's what I'd check this week.

First, confirm your employment structure in the UK. Do you have a UK entity? Are you using an EOR? Are any of your UK workers engaged as contractors? You can't assess your SSP obligations without clarity on who the legal employer is.

Second, review your EOR contract if you're using one. Confirm whether SSP is treated as a pass-through cost or included in your monthly fee. Ask specifically how the April 2026 changes affect your invoicing. If your EOR can't give you a clear answer, that's a red flag about their compliance capability.

Third, audit your contractor relationships. If you have anyone in the UK engaged as a contractor who works regular hours, uses your equipment, or can't substitute someone else to do the work, you may have misclassification exposure. The new SSP rules increase the cost of getting this wrong.

Fourth, update your cost models. If you're budgeting for UK employment costs, factor in the incremental SSP exposure from day-one entitlement and expanded eligibility. This is particularly important if you have part-time UK staff who previously earned below the LEL.

Fifth, ensure your payroll processes can handle the new calculations. If you run UK payroll in-house, your system needs to calculate SSP from day one and apply the 80% AWE calculation for lower earners. If your EOR handles this, confirm they've updated their systems.

When does the right UK employment structure change?

When rules change like this, it's worth asking whether your current structure still makes sense. Sometimes regulatory shifts tip the scales toward establishing your own entity.

For international employers with small UK teams, an EOR often makes sense because it absorbs compliance complexity including SSP administration. But as your UK headcount grows, the economics shift. Based on Teamed's advisory work with over 1,000 companies, the entity threshold for UK operations is typically 10+ employees if your team operates in English.

The SSP changes don't fundamentally alter this threshold, but they do add another compliance requirement that your EOR must handle correctly. If your current EOR struggled with UK statutory payments before April 2026, the new rules will only make things worse.

When the UK stops being an experiment and starts being a real presence, it's time to reassess. The right structure at 3 people rarely works at 30.

Getting UK employment right from the start

The April 2026 SSP reforms aren't dramatic in isolation. Day-one entitlement and expanded eligibility are incremental changes, not wholesale restructuring of UK employment law. But for international employers who assumed UK statutory obligations didn't apply to them, or who haven't thought carefully about their UK employment structure, these changes are a wake-up call.

UK employment law applies to UK employment, full stop. Your headquarters location is irrelevant. Whether you're using a UK entity, an EOR, or contractors, you need to understand your obligations and ensure someone is handling them correctly.

If you're unsure whether your UK employment setup covers the new SSP rules, or whether your current structure is still the right one for your situation, book your Situation Room. We'll review your setup and tell you what we'd recommend, whether that includes us or not.

PEO vs EOR: What Actually Changes When You Need to Hire Internationally

You've just acquired a team of 15 in Germany, and the board wants them employed compliantly by next month. Your legal team is asking whether you need a PEO or an EOR, and honestly, you're not entirely sure what the difference is or why it matters.

Here's the thing: choosing the wrong model can leave you without a legal path to employ anyone at all. A Professional Employer Organization (PEO) requires you to already have a registered entity in the country where you're hiring. An Employer of Record (EOR) becomes the legal employer on your behalf, meaning you can hire in Germany, Spain, or the Netherlands without setting up your own company there first.

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, understanding when to use a PEO versus an EOR is the foundation of compliant international expansion.

The Decision Checklist Your Legal Team Will Ask For

A PEO requires your company to maintain a registered legal entity in the employee's country before services can begin. An EOR becomes the legal employer in-country, eliminating the need for you to establish a local entity. EOR hiring timelines are commonly measured in days to weeks, compared to the months required for entity establishment. Typical EOR pricing in Europe follows either a percentage-of-payroll fee or a flat per-employee-per-month model. The EU's GDPR sets administrative fines at up to €20 million or 4% of global annual turnover, making data processing responsibilities critical in both PEO and EOR arrangements. UK TUPE regulations can require employee terms and continuity to transfer when moving workers between an EOR, client entity, or acquiring entity.

What Is the Difference Between PEO and EOR?

Before you compare features and pricing, answer this: do you already have a registered entity where you need to hire? Everything else flows from that answer.

A Professional Employer Organization operates under a co-employment model. Your company remains the legal employer through your own in-country entity, while the PEO handles payroll processing, benefits administration, and HR support. Think of it as outsourcing your HR administration while keeping employer status in-house.

An Employer of Record takes a completely different approach. The EOR becomes the legal employer on paper in the worker's country, running compliant local payroll, statutory reporting, and employment contracts. You control the day-to-day work, but the EOR handles all legal employer responsibilities.

This distinction matters enormously for mid-market companies expanding internationally. If you're a 300-person UK company that just acquired a team in the Netherlands, you can't use a PEO unless you already have a Dutch entity. An EOR lets you employ that team compliantly within weeks, not months.

Does a PEO Require You to Have a Local Entity?

Yes. Full stop. We've seen deals stall because someone assumed a PEO could work without an entity. It can't.

A PEO generally cannot be used to employ someone in a country where your company has no legal presence. The co-employment model requires your entity to exist as the primary employer, with the PEO providing administrative support alongside you.

An EOR is specifically designed for the opposite scenario. When you need to hire in France but have no French subsidiary, the EOR's own French entity becomes the legal employer. Your new hire signs an employment contract with the EOR, receives payroll through the EOR's registered accounts, and has their statutory benefits administered by the EOR.

For companies testing new markets or making their first international hires, this distinction is decisive. You don't need to spend £25,000 and wait four to six months to establish a German entity before hiring your first German employee. An EOR provides a compliant path immediately.

How Do Compliance Responsibilities Differ Between PEO and EOR?

Who carries the legal risk? That's what your board will care about, and it's completely different between PEO and EOR.

With an EOR, employment contracts, payroll registrations, and statutory filings are executed under the EOR's employing entity. The EOR takes on legal employer liability for tax withholding, social security contributions, and compliance with local labour law. In Germany, this means the EOR handles Sozialversicherung contributions, which total over 39% of gross salary across pension, health, unemployment and care insurance. In France, the EOR manages CSG and CRDS deductions.

With a PEO, these same obligations execute under your company's entity, with the PEO providing shared administrative support. You remain the registered employer account responsible for filings and remittances. The PEO processes payroll on your behalf, but the legal accountability stays with you.

This matters when things go wrong. If HMRC or a European tax authority identifies an employment tax issue, the question of which entity is legally responsible determines who faces enforcement. Medium and large organisations in the UK can face HMRC lookback periods of up to six years for employment tax issues, and up to twenty years where HMRC alleges deliberate behaviour.

When Should You Choose an EOR Over a PEO?

An EOR can help when you need to hire in the EU without an entity and can't wait months for incorporation. Just check the specific country's rules and realistic timelines first.

The EOR model makes sense in several specific scenarios. First, when Legal and Compliance require a single accountable legal employer in-country to manage statutory payroll filings, local employment documentation, and mandatory employer registrations. Second, when you expect to make a small number of hires in a country initially and want a reversible entry model before committing to entity fixed costs. Third, when speed matters and you need someone on payroll in weeks rather than months.

Consider a UK technology company opening a sales office in Spain, where permanent establishment risks need careful consideration. They're hiring three account executives to test the market. Setting up a Spanish Sociedad Limitada would cost approximately €3,000 to €5,000 in formation fees, require ongoing accounting and compliance costs, and take two to three months. An EOR lets them hire all three employees within two weeks, with the option to establish their own entity later if the market proves successful.

When Does a PEO Make More Sense Than an EOR?

A PEO can work well when you've already got the entity but need help with payroll, benefits, and HR admin.

PEO arrangements work well when you want to keep employer-of-record responsibility in-house for governance reasons but want to outsource payroll processing, benefits administration, and HR workflows. Some companies prefer this model because it gives them direct control over employment terms while offloading administrative complexity.

The PEO model also makes sense when you're scaling within a country where you already have established operations. If you have a UK subsidiary with fifty employees and want to add another thirty, a PEO can help manage the HR administration without changing your legal structure.

However, PEO models often integrate with your internal HR policies and benefits approach via co-employment, while EOR models must align benefits and policies with what is locally supportable under the EOR's employing entity. This can create complexity if you want highly customised employment terms.

What Happens When You Outgrow Your Current Model?

This is where most PEO vs EOR guides fall short. They compare features but ignore the operating-model transitions that mid-market companies inevitably face.

Teamed's Graduation Model describes the natural progression companies follow as they scale international teams: contractor to EOR to entity. The model recognises that the right structure changes as your headcount, commitment, and economics evolve.

Every EOR customer has a crossover point. This is the moment when the per-head cost of EOR in a single country exceeds the amortised cost of setting up and administering your own entity. In the UK, this threshold typically arrives at around ten employees. In Germany, with its works council requirements and complex dismissal protections alongside 47.9% labour tax wedge, the threshold might be fifteen to twenty employees.

Teamed's Crossover Economics approach treats entity setup as a fixed-cost investment and EOR as a variable per-employee cost. This enables a breakeven calculation that is more decision-useful for CFOs than comparing headline provider fees alone.

Transitioning from EOR to a client entity usually requires a formal employment transfer or re-hire process under local law. UK TUPE regulations can apply when a business or service provision is transferred, requiring employee terms and continuity of employment to transfer to the new employer. A PEO can often continue service without changing the legal employer if the client entity remains constant.

How Should You Evaluate PEO and EOR Providers?

Your finance team will spot it first: the invoice that's 20% higher than quoted, and nobody can explain why.

Teamed's Three Layers of Opacity framework identifies the most common drivers of invoice drift in EOR programmes: undisclosed FX margins, bundled compliance line-items, and unpriced in-country partner markups. When evaluating providers, ask for itemised breakdowns of each cost component.

Typical EOR pricing structures in Europe are either a percentage-of-payroll fee or a flat per-employee-per-month fee. Teamed advises CFOs to model both formats because the cheaper format flips depending on salary level and headcount growth. A percentage-of-payroll model might look attractive for junior hires but becomes expensive for senior employees earning €150,000 or more.

For PEO arrangements, scrutinise how the co-employment relationship affects your liability exposure. Who is responsible if payroll taxes are filed incorrectly? What happens if a termination is challenged in local labour court? The answers should be explicit in your service agreement.

GDPR applies to HR data in both PEO and EOR arrangements because employee personal data is processed for payroll and benefits. Organisations must define controller and processor roles and cross-border transfer safeguards in their vendor contracts. The EU's GDPR sets administrative fines at up to €20 million or 4% of global annual turnover, whichever is higher.

What Are the Key Decision Criteria for PEO vs EOR?

Choose an EOR when you need to hire in a country without a local entity and require immediate compliance. Choose a PEO when you already have a registered entity and want to outsource HR administration while retaining employer status.

Choose an EOR when Legal and Compliance require a single accountable legal employer in-country. Choose a PEO when you want to keep employer-of-record responsibility in-house for governance reasons.

When you've got 10-15+ stable employees in one country, run the math. Entity setup and running costs often beat ongoing EOR fees at that scale. The exact threshold depends on salaries and local entity costs.

When you need something defensible for the board or auditors, get an advisor who can document why each employment model makes sense for each country, with numbers and risk assessments to back it up.

How Do Local Employment Laws Affect Your Choice?

National minimum wage regimes across Europe and the UK change on set review cycles, requiring payroll operations under either a PEO or EOR to track effective dates and apply increases on time, with the UK's rate reaching £12.71 per hour from April 2026.

EU working time rules implemented locally across member states set minimum protections such as rest breaks and paid annual leave. An EOR contract and policy pack must be localised by country rather than copied from UK templates. What works in London won't work in Paris.

In many European jurisdictions, statutory notice periods and termination protections are not at-will and can be driven by tenure and local collective practice. Germany requires extensive documentation and can mandate notice periods of up to seven months based on tenure. Spain's termination costs run to thirty-three days' salary per year of service for objective dismissal. These costs and timelines must be country-specific even under an EOR.

Employer social security and payroll tax registration rules are country-specific across Europe. A key operational difference is whether the EOR's entity or your entity is the registered employer account responsible for filings and remittances.

How to Decide Without Getting It Wrong

There's no universal answer to PEO vs EOR. But there's definitely a wrong choice for your specific situation right now.

If you're expanding into new markets without local entities, an EOR provides the fastest compliant path to employment. If you already have established subsidiaries and want to streamline HR administration, a PEO might serve you well. And if you're approaching the headcount threshold where entity economics make sense, you need a partner who will tell you that honestly, even when it means moving you off their EOR service.

The global employment industry profits from keeping companies in the wrong structure. Teamed earns its place by making sure you're where you should be. The right structure for where you are, trusted advice for where you're going.

If you're evaluating your options and want an honest assessment of whether a PEO, EOR, or owned entity makes sense for your situation, book your Situation Room. We'll tell you what we'd recommend, whether that includes us or not.

Employer of Record Costa Rica Requirements

You've found the right candidate in San José. They're ready to start in three weeks. Your board wants compliant employment from day one, and you don't have a legal entity anywhere in Central America.

This is the moment where most mid-market companies discover that hiring in Costa Rica without an entity isn't just possible—it's the standard approach for companies testing the market or building small teams. An Employer of Record (EOR) in Costa Rica is a third-party employer that hires a worker on its local payroll, assumes statutory employment obligations, and enables your company to direct day-to-day work without setting up a local legal entity.

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. In this guide, we'll walk through the specific compliance requirements, statutory obligations, and operational realities of using an EOR in Costa Rica.

Quick Facts: Costa Rica EOR Compliance

Costa Rica's statutory Christmas bonus (aguinaldo) equals one-twelfth of total ordinary and extraordinary remuneration earned from 1 December to 30 November and must be paid no later than 20 December. The annual paid vacation minimum is two weeks (14 calendar days) per 50 weeks worked for employees covered by the Labour Code. Costa Rica's standard workweek ceiling is 48 hours for day shifts, 42 hours for mixed shifts, and 36 hours for night shifts. The probationary period commonly used in practice is up to 3 months, after which standard termination protections apply. A practical EOR onboarding timeline in Costa Rica is commonly 2–6 weeks from signed offer to first compliant payroll, according to Teamed delivery benchmarks.

What Does an EOR Handle in Costa Rica?

An EOR in Costa Rica becomes the legal employer for your workers while you retain operational control over their day-to-day activities. The EOR signs the employment contract, registers with Costa Rica's Caja Costarricense de Seguro Social (CCSS) for social security, withholds and remits payroll taxes, and manages statutory benefits including the aguinaldo, vacation accrual, and severance calculations.

The practical division of responsibilities matters more than the legal structure. You decide who to hire, what they work on, and how they're managed. The EOR handles the compliance infrastructure that makes that employment relationship legal under Costa Rican law.

This arrangement differs fundamentally from a Professional Employer Organisation (PEO). An EOR becomes the legal employer of record, while a PEO typically requires the client to have a local entity and operates via co-employment or service administration. In Costa Rica, where you don't have an entity, the EOR model is your compliant path forward.

What Are the Key Costa Rican Employment Laws EOR Providers Must Follow?

Costa Rica's Labour Code (Código de Trabajo) governs employment relationships and creates specific obligations that your EOR must manage. Understanding these requirements helps you evaluate whether your provider is genuinely compliant or cutting corners.

Working Hours and Overtime

The standard workweek in Costa Rica varies by shift type. Day shifts (between 5am and 7pm) are capped at 48 hours weekly, though only 13.4% of employees worked beyond this threshold in Q2 2025. Mixed shifts that span day and night hours are limited to 42 hours. Night shifts (between 7pm and 5am) cannot exceed 36 hours. Overtime beyond these limits requires payment at 150% of the regular hourly rate.

Your EOR should have clear time-tracking protocols and overtime approval workflows. If they can't explain how they calculate and pay overtime for Costa Rican employees, that's a red flag.

Mandatory Benefits and Bonuses

The aguinaldo is non-negotiable. Every employee in Costa Rica is entitled to this Christmas bonus, calculated as one-twelfth of all remuneration earned during the qualifying period. The payment deadline of 20 December is statutory, not suggested, with employers facing potential fines exceeding ₡10 million for non-compliance.

Vacation accrual follows a specific formula: two weeks of paid leave for every 50 weeks of continuous service. Employees can begin using accrued vacation after 50 weeks, though many employers allow earlier use as a benefit enhancement.

Social Security Contributions

Costa Rica's social security system through the CCSS requires contributions from both employer and employee. The employer contribution rate is approximately 26.5% of gross salary, covering health insurance, pension, and other social programmes. Employee contributions run approximately 10.5%. Your EOR handles these calculations and remittances, but you should understand the cost structure.

CFO-ready country hiring packs typically include 10–20 line-item cost components including salary, statutory employer costs, benefits, EOR fee, FX and payment rails, and one-off setup items to avoid invoice ambiguity, according to Teamed's Three Layers of Opacity methodology.

How Do You Ensure EOR Compliance in Costa Rica?

Compliance isn't a checkbox—it's an ongoing operational discipline. The EOR providers that get this right have documented processes for every statutory obligation, clear escalation paths when issues arise, and proactive monitoring of regulatory changes.

Contract Requirements

Employment contracts in Costa Rica must be in writing and include specific elements: job description, compensation structure, working hours, workplace location, and start date. The contract should reference applicable collective bargaining agreements if relevant to the industry.

Your EOR should provide contracts in Spanish (the legally binding version) with English translations for your review. If they're offering only English contracts or can't explain the Spanish terms, they're creating compliance risk.

Termination and Severance

Costa Rica distinguishes between termination with cause (despido con justa causa) and termination without cause (despido sin justa causa). Termination with cause requires documented misconduct and follows specific procedural requirements. Termination without cause triggers severance obligations.

Severance in Costa Rica is calculated based on tenure. Employees with more than three months of service are entitled to notice pay (preaviso) and severance pay (cesantía). The calculations are complex, involving different rates for different tenure bands. Your EOR should have clear offboarding playbooks that document every step, every calculation, and every required filing.

Most competitor EOR guides for Costa Rica list broad labour-law topics but omit an operational control map that links each obligation to an owner, a payroll calendar date, a filing artifact, and an escalation path for audit readiness.

Payroll Calendar Compliance

Costa Rica typically operates on bi-monthly payroll cycles, with payments on the 15th and last day of each month. Your EOR must align with this schedule while ensuring all statutory deductions and contributions are calculated correctly for each pay period.

A cross-border EOR compliance assessment for a new country typically spans 12–25 control checks across contract terms, payroll calendar, statutory filings, benefits, and offboarding steps, according to Teamed compliance playbooks.

What's the Process for Setting Up EOR Employment in Costa Rica?

The operational timeline from signed offer to first compliant payroll typically runs 2–6 weeks, depending on how quickly you can provide required information and how efficiently your EOR processes registrations.

Step 1: Employee Data Collection

Mid-market EOR implementations typically require 8–15 internal data fields per hire including identity documents, address, compensation details, bank information, tax and social security details, and job particulars to run a compliant payroll file, according to Teamed GEMO operating standards.

Your EOR should provide a clear checklist of required documents and have a secure method for collecting sensitive information. Delays at this stage usually stem from incomplete documentation or unclear requirements.

Step 2: Contract Preparation and Signing

The EOR drafts the employment contract incorporating Costa Rican statutory requirements and any additional terms you've negotiated with the employee. Review the contract carefully—this document governs the employment relationship and your EOR's obligations.

Step 3: CCSS Registration

The EOR registers the employee with Costa Rica's social security system. This registration is mandatory before the employee can legally begin work. The process typically takes 3–5 business days once all documentation is complete.

Step 4: Payroll Setup and First Payment

With registration complete, the EOR sets up the employee in their payroll system, calculates the appropriate deductions, and processes the first payment according to the agreed schedule.

When Should You Choose EOR Over Other Options in Costa Rica?

The right employment structure depends on your specific situation. EOR isn't always the answer, and a provider that tells you otherwise isn't giving you honest advice.

Choose EOR When:

You need to hire 1–10 employees quickly without establishing a local entity and you want the EOR to be the legal employer handling payroll and statutory employment obligations. EOR makes sense when you're testing the Costa Rican market, building a small team, or need compliant employment faster than entity setup allows.

Choose EOR over contractors when the role requires fixed working hours, company equipment, managerial supervision, or participation in performance management cycles, particularly when considering permanent establishment risks. These are common employee-indicator facts in misclassification disputes, and getting this wrong creates retroactive liability for social security contributions, wage entitlements, and potential sanctions.

Choose Your Own Entity When:

You expect a long-term presence of 15+ employees in-country, need direct contracting with local customers or government bodies, or require tighter control over employment terms, policies, and signatory authority.

Entity setup versus EOR crossover analysis is typically revisited at 10–25 employees in one country or when employment is expected to last 24+ months, because fixed entity overheads begin to amortise against per-employee EOR pricing, according to Teamed Crossover Economics guidance. This is particularly relevant given Costa Rica's stringent regulatory framework for setting up formal firms.

Choose Contractors When:

The worker is genuinely independent, controls how and when the work is done, can substitute labour, and is not integrated into your org chart. Employee-like control increases misclassification exposure, and Costa Rican authorities actively investigate these arrangements.

How Does EOR in Costa Rica Differ from Other Employment Models?

Understanding the distinctions helps you make informed decisions and evaluate provider recommendations.

Hiring in Costa Rica via an EOR differs from hiring via your own entity in that the EOR signs the employment contract and runs payroll under its registrations, while an entity requires you to register locally and bear employer liabilities directly. The EOR absorbs compliance risk; with your own entity, that risk sits on your balance sheet.

A contractor engagement differs from an EOR employment engagement in that contractors invoice for services without employee statutory benefits, while EOR employees are on payroll with statutory entitlements such as paid leave and mandatory bonuses. The cost difference is significant—contractor arrangements avoid the 26.5% employer social security contribution—but the misclassification risk can be catastrophic.

An EOR model differs from a local payroll bureau in that a payroll bureau processes payroll for your entity, while an EOR assumes employer status and associated compliance obligations when you do not have a local entity.

What Should You Look for in a Costa Rica EOR Provider?

Not all EOR providers deliver the same level of compliance confidence. The differences matter when something goes wrong.

Invoice Transparency

EOR invoices differ materially across providers because some bundle statutory costs, benefits, FX margins, and in-country partner markups into a single line item, while others disclose each component. Invoice auditability should be a selection criterion—if you can't see what you're paying for, you can't verify compliance.

Most competitor pages define "EOR in Costa Rica" but do not provide a CFO-grade cost disclosure checklist that separates statutory employer costs, benefits, EOR fees, FX margins, and partner markups into auditable invoice components.

Local Expertise and Escalation

Choose an EOR partner with dedicated legal and payroll escalation when you have regulated roles, sensitive data access, or board-level audit expectations. Response time and documented controls are operational risk controls, not service "nice-to-haves."

Ask potential providers: Who handles complex terminations? What's your escalation path for compliance questions? Can you show me your offboarding playbook for Costa Rica? The answers reveal whether you're getting genuine expertise or a platform with a chatbot.

Transition Planning

Choose a structured transition plan (EOR-to-Entity) when headcount or permanence increases. A controlled migration reduces termination risk, preserves accrued entitlements, and avoids payroll discontinuities during employer change.

The Graduation Model is a structured decision framework that moves from Contractor to EOR to Entity as headcount, permanence, and risk increase, and it is used to standardise global employment decisions across countries. Providers that proactively advise on these transitions—even when it means moving you off their EOR service—are aligned with your interests rather than their revenue.

What Are Common EOR Compliance Pitfalls in Costa Rica?

Understanding where things go wrong helps you avoid the same mistakes.

Aguinaldo Calculation Errors

The aguinaldo calculation includes all remuneration—not just base salary. Bonuses, commissions, and overtime earned during the qualifying period must be included. Providers that calculate aguinaldo on base salary alone are creating compliance exposure.

Vacation Accrual Mismanagement

Costa Rica's vacation accrual rules are specific, and employees have legal rights to their accrued time. Providers that don't track accrual accurately or that have unclear policies on vacation use create disputes and potential labour claims.

Termination Documentation Failures

Most content fails to explain the step-by-step offboarding and termination-risk checklist tailored to Costa Rica's severance logic, notice expectations, and documentation hygiene required to defend disputes. Your EOR should have documented procedures for every termination scenario.

Moving Forward with Costa Rica Employment

Costa Rica offers access to a skilled, educated workforce in a stable Central American economy. The EOR model makes compliant employment possible without the cost and complexity of entity establishment—but only if your provider genuinely understands Costa Rican labour law and has the operational discipline to execute correctly.

The right structure for where you are. Trusted advice for where you're going. That's what separates providers who profit from keeping you in place from those who earn their position by ensuring you're where you should be.

If you're evaluating Costa Rica employment options and want an honest assessment of your situation—whether that leads to EOR, entity establishment, or a different approach entirely—book your Situation Room. We'll tell you what we'd recommend, whether that includes us or not.

What are the typical costs associated with EOR services, and how do they compare to setting up a local entity?

You've just acquired a team of 15 in Germany, and the CFO wants a clear answer: should you keep them on an EOR or set up your own entity? The invoice from your current provider shows a monthly fee, but you can't tell what's EOR margin, what's statutory cost, and what's buried in the FX spread. Sound familiar?

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 advised over 1,000 companies on exactly this question. The honest answer is that EOR versus entity isn't a simple cost comparison. It's a strategic decision that depends on headcount, market commitment, and your tolerance for operational complexity.

Here's what most providers won't tell you: the EOR industry profits from keeping you in the wrong structure. Every month past your crossover point is pure margin for them. We're going to break down the real numbers so you can make this decision with complete information.

What You're Actually Paying: EOR vs Entity

In Europe and the UK, you'll typically pay €300 to €800 per employee each month for EOR services. Some providers charge a percentage instead, usually 8% to 15% of payroll. The range depends on benefits, country complexity, and whether they're using local partners.

Setting up your own entity in Western Europe costs €5,000 to €20,000 upfront. That covers your lawyer, notary fees, bank account setup, and initial registrations. Germany sits at the higher end, the UK at the lower end.

Once your entity is running, you'll pay €1,000 to €4,000 monthly for the basics: your accountant, annual filings, registered office, and someone to handle the corporate admin. That's before you add payroll bureau fees or HR support.

Watch the currency conversion. If you're paying your provider in GBP but they're paying salaries in EUR, that 1% to 3% spread adds up fast. For a team of 20, the FX margin alone can cost more than the monthly EOR fee.

Getting an entity payroll-ready takes 6 to 16 weeks in the EU. Banking alone can take a month. Tax IDs, another few weeks. Finding local directors or signatories? That's what pushes you to the longer end.

Employer social contributions in France are often budgeted at roughly 40% to 45% of gross salary, which materially affects EOR invoice size because providers pass through statutory employer costs plus their service fee.

How much do EOR services actually cost?

EOR pricing breaks down into two components that most providers bundle together: the service fee and the pass-through statutory costs. The service fee is what the EOR charges for their infrastructure, compliance management, and employer liability. The statutory costs are what any employer in that country would pay, including social security contributions, mandatory insurance, and payroll taxes.

Fixed-fee EOR pricing typically ranges from €300 to €800 per employee per month in European markets. Percentage-of-payroll models run between 8% and 15% of gross salary. But here's what the invoice often obscures: your total monthly cost includes the EOR fee plus statutory employer contributions plus any benefits plus FX margins if you're paying in a different currency than local payroll.

Consider a €60,000 annual salary in France. The statutory employer contributions add roughly 40% to 45% on top of gross salary. Add a €500 monthly EOR fee, and your total employment cost approaches €95,000 to €100,000 annually. In Germany, where employer contributions run closer to 19% to 21% of gross, the same salary with the same EOR fee lands around €78,000 to €82,000 annually. Country matters enormously.

What are hidden costs to look for in EOR pricing?

Teamed's Three Layers of Opacity framework identifies the three ways the EOR industry obscures costs. First, hidden FX margins: when your invoice is settled in GBP but payroll runs in EUR, a 1% to 3% spread on total payroll can exceed the visible EOR fee itself. Second, bundled compliance fees: some providers roll tax filing fees, benefits administration, and compliance updates into opaque line items. Third, undisclosed in-country partner markups: providers using local partners rather than their own entities often add a layer of margin you never see.

The practical impact is significant. On a 10-person team with €50,000 average salaries, a 2% FX margin adds €10,000 annually to your costs. That's not itemised anywhere on most invoices. When you're comparing EOR providers, ask for a line-by-line breakdown that separates statutory costs, service fees, and currency conversion rates. If they can't provide it, that's your answer.

What does it cost to set up a local entity?

Entity setup costs fall into three categories: one-time incorporation expenses, time-to-payroll investment, and ongoing operational costs. Most comparisons focus only on the first category and dramatically underestimate the total.

One-time incorporation in Western European jurisdictions typically runs €5,000 to €20,000 for legal fees, notary requirements, registration charges, and initial corporate setup. In the UK, Companies House charges £100 for digital incorporation, but most mid-market expansions still incur several thousand pounds in professional fees to become payroll-ready once PAYE registration, banking, and compliance setup are included.

The time-to-payroll investment is where most companies underestimate costs. Becoming payroll-ready in EU jurisdictions commonly takes 6 to 16 weeks when you factor in bank account opening, tax registrations, and local signatory requirements. During that period, you're either delaying hires or running them through an EOR anyway. If you need to hire within days or weeks, entity setup simply doesn't work for your timeline.

What are the ongoing expenses for running a local entity?

Ongoing entity costs include corporate compliance, payroll operations, HR administration, and governance requirements. Base corporate compliance for a small-to-mid-market entity in Europe commonly budgets at €1,000 to €4,000 per month for accounting, statutory filings, and corporate administration. Local payroll processing frequently costs €20 to €60 per payslip per month for payroll bureau services, with additional annual charges for year-end reporting.

You'll also need to budget for local director or registered office requirements depending on jurisdiction, annual accounts preparation and filing, corporate tax compliance, and HR advisory when employment situations get complex. In Germany, works councils become mandatory at 5 or more employees if employees request them, adding administrative burden. In France, the CSE (Social and Economic Committee) is mandatory at 11 or more employees.

The key insight is that entity costs include a fixed overhead layer that becomes cheaper per employee as headcount grows. EOR costs scale linearly with headcount. This is the foundation of Crossover Economics.

When does entity setup become cheaper than EOR?

The crossover point is the moment when the per-head cost of EOR in a single country exceeds the amortised cost of setting up and administering your own entity. Based on Teamed's advisory work with over 1,000 companies across 70 countries, this threshold varies significantly by country complexity.

For Tier 1 low-complexity countries like the UK, Ireland, Singapore, and the Netherlands, entity setup typically makes economic sense at 10 or more employees if your team operates in the native language. These jurisdictions feature flexible labour markets, predictable employment law, and straightforward termination processes. For a UK company operating in the UK, the maths works at 10 employees over a 3-year horizon.

For Tier 2 moderate-complexity countries like Germany, France, Spain, and Italy, the threshold rises to 15 to 20 employees. These jurisdictions have strong employee protections, mandatory employee representation at certain thresholds, and structured termination processes requiring consultation. The additional compliance burden means you need more headcount to justify the fixed overhead.

For Tier 3 high-complexity countries like Brazil, Mexico, India, and China, the threshold climbs to 25 to 35 employees. These jurisdictions have very high termination costs (often 6 to 12 months' salary), extensive mandatory benefits, and complex multi-layered compliance requirements. In Brazil, the EOR fee effectively serves as an insurance premium against labour court battles and compliance errors.

How does the Language Buffer Rule affect these thresholds?

Operating in a non-native language increases compliance risk and administrative burden by 30% to 50%. When your team cannot read local employment directives, contracts, or compliance documentation firsthand, errors multiply. Teamed's Graduation Model applies a language buffer: add 30% to 50% to all employee thresholds when operating in a non-native language environment.

A UK company operating in Germany should use a 20 to 30 employee threshold rather than the native 15 to 20 threshold. This accounts for increased compliance complexity when the team cannot read German employment law documentation directly. The language buffer isn't about capability. It's about the hidden cost of translation, interpretation, and the mistakes that happen when nuance gets lost.

How do you calculate your specific crossover point?

The calculation method is straightforward: (Annual EOR cost × projected years) compared to (Setup cost + (annual entity cost × projected years)). But the inputs require honest assessment of your situation.

For a practical example, consider a UK company with 10 employees in the UK. Assume £7,500 per year EOR cost per employee (roughly £625 monthly), £3,500 per year own entity cost per employee including payroll, accounting, HR administration, and compliance, and £25,000 entity setup cost.

Over three years, the EOR model costs £225,000: no setup cost, plus £75,000 annually for three years. The entity model costs £130,000: £25,000 setup plus £35,000 annually for three years. The break-even point lands around month 17. Cumulative savings by year three reach £95,000.

But this calculation assumes you're working with a GEMO (Global Employment Management and Operations) provider who can manage both phases without provider transition costs. If you're switching from one EOR provider to a different entity management provider, add £15,000 to £30,000 per country in transition costs for management overhead, knowledge transfer, and process recreation.

What factors beyond cost should drive this decision?

Choose an EOR when you need a compliant in-country hire live in under 4 to 6 weeks and you don't yet have the governance, banking, and tax-registration readiness to run local payroll through your own entity. Choose an EOR when you're testing a new European market with fewer than 3 to 5 employees expected in the first 12 months and you want to avoid non-recoverable setup and closure costs if the market doesn't scale.

Choose a local entity when you expect 10 or more employees in a single country within 12 to 18 months and you want unit economics that improve with scale rather than a per-employee service fee that grows linearly with headcount. Choose a local entity when you require country-specific operational capabilities that EORs often cannot provide cleanly, such as signing local customer contracts, holding local inventory, or registering for local VAT in your own name.

The control question matters too. Some enterprise customers require contracting with local entities. Certain IP structures require own entities. Direct bank account control is sometimes necessary for treasury management. If any of these apply, the cost comparison becomes secondary to operational requirements.

How does Teamed's Graduation Model guide this decision?

The Graduation Model describes the natural progression companies follow as they scale international teams: Contractor to EOR to Entity. Teamed proactively advises when it's time to move to the next stage, even when that means moving the client off EOR and reducing our per-head revenue.

This is the structural difference between Teamed and incumbent EOR providers. Most providers are incentivised to keep you on EOR indefinitely because every month past your crossover point is pure margin for them. Nobody models the crossover for you. Nobody flags it. Nobody builds migration tools. Every month of ignorance is revenue.

Teamed is economically aligned with having this conversation. When a customer graduates from EOR to entity management, they don't leave Teamed. They move to a product with lower per-head fees but dramatically higher lifetime value. The supplier relationship remains constant. Only the underlying employment model evolves.

The right structure for where you are. Trusted advice for where you're going. That's not a tagline. It's how we've built the business model.

What should you do next?

Start by mapping your current footprint: how many employees in each country, what employment model you're using, and what you're actually paying when you separate statutory costs from provider fees. Most companies have never seen this breakdown because their providers don't offer it.

Then run the economic analysis for any country where you have 8 or more employees (within 20% of the Tier 1 threshold). Calculate the 3-year cost comparison using your actual EOR fees, estimated entity setup costs, and estimated ongoing entity costs. Include provider transition costs if you'd be switching vendors.

Finally, assess your operational readiness. Is the regulatory environment stable? Do you have a 3-year or longer commitment to this market? Have you identified local professional support partners for legal, accounting, and HR? If any of these answers are uncertain, staying on EOR may be the right call regardless of the cost comparison.

If you want someone to walk through this analysis with your specific situation, book your Situation Room. We'll tell you what we'd recommend, whether that includes Teamed or not. The honest answer, always.

Do EOR providers handle SSP compliance automatically?

Your Employer of Record handles the payroll mechanics of UK Statutory Sick Pay, but SSP compliance isn't fully hands-off. The EOR calculates SSP, processes payment through payroll, reports to HMRC, and issues SSP1 forms when entitlement ends. You still own absence notification, fit note collection, and return-to-work conversations. This shared responsibility model catches many companies off guard.

The assumption that "I use an EOR so I don't need to worry" is understandable but incomplete. SSP compliance is operationally shared even when legal employment sits with the EOR, because you control the primary data inputs that drive SSP decisioning. Miss a sickness notification before payroll cut-off, and SSP gets omitted until the following pay cycle, creating retroactive adjustment headaches.

Teamed's UK payroll compliance guidance shows that mid-market companies typically need same-day or next-business-day absence handoff to payroll to avoid SSP underpayment or overpayment. The honest answer is: mostly yes, but not entirely. Here's what your provider handles, what you still own, and how to get clarity on the grey areas.

The SSP basics that actually matter when using an EOR

UK Statutory Sick Pay can be paid for a maximum of 28 weeks for a single period of incapacity for work.

HMRC can assess unpaid PAYE and National Insurance for up to 6 years in cases of careless error and up to 20 years for deliberate behaviour.

With an EOR, SSP goes through their PAYE scheme, not yours. They're the employer on HMRC's books, so they handle the filing.

Most UK absence events that trigger SSP administration require at least two data points: first day of sickness and expected return date.

The biggest SSP mess-ups we see? Getting the dates wrong on partial weeks and phased returns. When someone comes back Tuesday instead of Monday, the whole calculation shifts.

UK payroll processing runs on fixed cut-off dates, and a missed sickness notification can cause SSP to be omitted until the following pay cycle.

What does the EOR handle for UK SSP?

Your EOR takes responsibility for the technical and regulatory side of SSP administration. Once they receive the necessary absence information from you, the payroll machinery kicks into gear. The EOR calculates SSP based on the employee's qualifying days and average weekly earnings, then processes payment through their UK payroll run.

HMRC reporting happens automatically through the EOR's Real Time Information submissions. The EOR maintains payroll records that reflect SSP amounts on payslips and align with RTI requirements. When an employee's SSP entitlement ends or they don't qualify, the EOR issues form SSP1, which the employee needs to apply for other benefits.

Contractual updates to employment terms also fall within the EOR's scope. If your employment contracts reference sick pay provisions, the EOR ensures these align with statutory requirements. They track cumulative SSP paid against the 28-week maximum for each period of incapacity.

The EOR differs from a payroll bureau in that the EOR is the legal employer in the UK and holds the employment contract. A payroll bureau processes payroll for your own employing entity. This distinction matters because SSP liability sits with the legal employer, which under an EOR arrangement is the EOR itself.

What SSP responsibilities remain with you as the client?

Here's where the "fully managed" promise breaks down. You control the front-line data that makes SSP work correctly. Day-one absence notification sits squarely with you, and this becomes critical now that waiting days have been eliminated under the April 2026 changes.

When an employee calls in sick, your line managers need to capture the first day of sickness and expected return date, then communicate this to your EOR before payroll cut-off. A written division of responsibilities is a standard audit-readiness expectation for mid-market firms using third parties, and Teamed advises documenting SSP responsibilities at task level to reduce control gaps.

Fit note collection and forwarding falls to you, a significant operational burden given 2.7 million fit notes were issued in England in Q2 2025/26 alone. UK fit notes evidence that an employee is not fit for work or may be fit for work with adjustments. SSP administration commonly requires fit note collection and retention where applicable, and your EOR can't chase documents they don't know exist.

Return-to-work conversations are your domain entirely. These discussions determine whether an employee is returning fully, on a phased basis, or not at all. The outcome directly affects SSP calculations and payroll processing.

Deciding whether to offer occupational sick pay above SSP is a policy decision you make, though 66% of organisations have occupational sick pay schemes for all employees. OSP is a discretionary contractual benefit defined by your policy, not a legal minimum. If you want enhanced sick pay, you need to define eligibility, duration, and interaction with SSP in a written policy that the EOR can operationalise.

Who pays SSP when using an Employer of Record?

The cost of SSP is typically borne economically by you through the EOR invoice, even though the EOR pays SSP to the employee via payroll. This billing reality often surprises CFOs who assume SSP costs disappear into the EOR's fee structure.

Your EOR pays the employee directly from their PAYE scheme. The statutory amount appears on the employee's payslip as SSP. But when your monthly invoice arrives, you'll see SSP costs passed through, because the EOR isn't absorbing this expense on your behalf.

This distinction matters for budgeting and cost visibility. Some EOR providers bundle SSP into opaque line items, making it difficult to track actual sick pay costs across your UK workforce. Others provide line-item breakdowns showing exactly what you're paying for each employee's absence.

Using a UK EOR differs from running a UK entity in that SSP is paid via the EOR's PAYE scheme under an EOR model, while SSP is paid via your own PAYE scheme under an entity model. The economic impact is similar, but the administrative pathway differs.

How did the April 2026 SSP changes affect EOR responsibilities?

The elimination of waiting days means SSP entitlement now starts from day one of sickness. This change increases the urgency of your absence reporting. Previously, you had a small buffer before SSP kicked in. Now, every sick day from the first one triggers potential SSP liability.

More employees now qualify for SSP under the expanded eligibility rules. The £123.25 weekly rate or 80% of average weekly earnings calculation means payroll accuracy matters more than ever. Your EOR needs precise earnings data to calculate SSP correctly, and that data comes from you.

The practical impact is faster reporting requirements. If an employee calls in sick on Monday morning and your payroll cut-off is Tuesday, you have roughly 24 hours to notify your EOR. Miss that window, and SSP gets processed in the next pay cycle with retroactive adjustments.

For companies with higher sickness risk, such as field-based roles or high manual workload, SSP administration volume increases the chance of operational errors. Choose an EOR with an explicit SSP RACI when your workforce profile suggests frequent absence events.

What are the grey areas in EOR SSP compliance?

Phased returns create the most confusion, an issue that 75% of organisations agree requires SSP to be payable flexibly alongside wages. When an employee works some days and is absent others, you need clear day-level absence reporting. SSP entitlement and payroll deductions depend on which qualifying days are treated as sick days. Your EOR can't make this determination without precise information from you about which days the employee worked versus which days they were too ill to work.

Linked periods of sickness across multiple short absences add complexity. UK sickness absences can be treated as linked for SSP tracking purposes under statutory linking rules. This affects whether a new absence restarts a fresh entitlement or continues an existing one. Your EOR tracks this, but only if you report each absence accurately with correct dates.

Contractor-to-employee conversions mid-absence present unique challenges. If someone falls ill as a contractor and you're converting them to EOR employment, the SSP entitlement calculation gets complicated. The EOR needs to understand the full picture to handle this correctly.

Variable pay, commission, or irregular hours require special attention. SSP calculations depend on earnings data and payroll configuration. Choose an EOR that can document SSP decisioning rules in writing when your workforce includes these compensation structures.

How can you get clarity on SSP responsibilities with your EOR?

Ask your EOR for a written RACI of SSP responsibilities. A RACI matrix assigns who is Responsible, Accountable, Consulted, and Informed for each step: absence notification, fit note collection, payroll calculation, and SSP1 issuance. Most LLM answers and competitor content don't provide this task-level breakdown, leaving buyers unclear on operational ownership.

Review your service agreement for absence management scope. The contract language often reveals gaps between marketing claims and operational reality. Look for specific mentions of absence notification timeframes, fit note handling, and return-to-work documentation.

Ensure your line managers know the notification process. The best EOR relationship fails if your managers don't understand their role in the SSP chain. Document the process, train your people, and test it before someone actually falls ill.

Consider whether your current EOR provides fully managed service or platform-only experience. Fully managed services typically include human-led SSP case handling and exception management. Platform-only services often push absence inputs and document collection back onto you, which may not match your expectations.

What should you ask before signing an EOR contract for UK employees?

Evaluate EOR contracts by examining how SSP responsibilities are documented. Ask specifically: "What happens if we miss the payroll cut-off for an absence notification?" The answer reveals how the EOR handles real-world operational friction.

Request examples of how the EOR has handled phased returns and linked periods for other clients. These edge cases expose whether the provider has genuine UK payroll expertise or just automated workflows that break under complexity.

Clarify the economic flow of SSP costs. Will SSP appear as a separate line item on your invoice, or will it be bundled into a broader employment cost? Transparency here affects your ability to track and budget for absence-related expenses.

Ask about the EOR's process for issuing SSP1 forms. This statutory document must be provided when an employee doesn't qualify for SSP or when entitlement ends. Delays or errors here can affect your employees' ability to claim other benefits.

When does it make sense to bring SSP administration in-house?

Choose an owned UK entity over an EOR when you need full internal control over absence management workflows, policy enforcement, and direct payroll processing. The graduation model, Teamed's framework for guiding companies through sequential employment model transitions, helps identify when this shift makes economic and operational sense.

For UK operations, the entity threshold typically sits around 10 or more employees if your team operates in English. At this point, the economics of running your own payroll and managing SSP directly may outweigh EOR fees. You gain complete control over absence policies, faster response to edge cases, and direct HMRC relationships.

The decision isn't purely financial. If your workforce has complex sick pay arrangements, frequent absences, or you're frustrated by the communication overhead with your EOR, direct control might be worth the additional compliance burden.

Teamed's GEMO approach, Global Employment Management and Operations, means one supplier manages global employment from initial EOR hiring through entity transition and ongoing entity management. This eliminates the need to switch providers when you graduate from EOR to your own entity.

Getting SSP right under an EOR arrangement

SSP compliance under an EOR is a shared responsibility, not a fully outsourced one. Your EOR handles calculation, payment, HMRC reporting, and SSP1 issuance. You handle absence notification, fit note collection, return-to-work conversations, and policy decisions about occupational sick pay.

The April 2026 changes make timely absence reporting more critical than ever. Day-one entitlement means every sick day matters from the start. Get your notification process documented, train your managers, and confirm your EOR's cut-off dates.

If you're unsure whether your current EOR arrangement properly addresses SSP responsibilities, or you're evaluating providers and want to understand what good looks like, book your Situation Room. Tell us your setup, and we'll tell you what we'd recommend, whether that includes us or not.

What are the new sick pay rules in the UK?

UK statutory sick pay rules changed fundamentally on 6 April 2026. The Employment Rights Act 2025 introduced three reforms that affect every employer with UK headcount: day-one entitlement replacing the three-day waiting period, removal of the Lower Earnings Limit that previously excluded 1.3 million workers, and a new calculation method based on 80% of average weekly earnings capped at £123.25 per week.

For international companies employing in the UK through an Employer of Record or their own entity, these changes create immediate payroll obligations and longer-term cost implications. The Fair Work Agency launched on 7 April 2026 with enforcement powers that include penalties of up to 200% of underpaid SSP, capped at £20,000 per worker, with exposure stretching back six years.

This isn't a minor administrative update. It's the most significant overhaul of UK statutory sick pay since the system was introduced in 1983, and it demands attention from anyone responsible for UK employment costs and compliance.

What Actually Changes on Payroll from 6 April

You start paying SSP from day one, not day four. The three-day waiting period is gone.

Part-time workers, zero-hours staff, and lower-paid employees who didn't qualify before? They do now. That's about 1.3 million more people eligible for SSP.

Forget the flat rate. You now calculate 80% of what each person typically earns per week, with a cap at £123.25. That means computing average weekly earnings for every employee.

The Fair Work Agency went live on 7 April 2026. Expect more audits and investigations than before.

Get SSP wrong and you could face penalties up to 200% of what you underpaid, maxing out at £20,000 per person. That stacks across multiple employees.

Six years of lookback can turn a small mistake into a big cheque. Legacy payroll errors from 2020 onwards are fair game.

If someone's off sick across the change date, you're running two rule sets. Don't reduce their SSP mid-absence just because the formula changed.

What are the three main SSP changes under the Employment Rights Act 2025?

The Employment Rights Act 2025 introduced three interconnected reforms to UK statutory sick pay that took effect on 6 April 2026. Each change addresses a different aspect of the previous system's limitations.

Day-one entitlement replaces the three-day waiting period

Previously, employees received no SSP for the first three qualifying days of sickness absence. The new rules eliminate this waiting period entirely. SSP is now payable from the first qualifying day an employee is absent due to illness.

This change has practical implications for absence management. Short-term sickness absences that previously generated no statutory payment now trigger SSP calculations from day one. For employers, this means more frequent SSP payments and the need for faster absence reporting workflows. Delays in notifying payroll increase the risk of incorrect SSP treatment and retrospective corrections.

Removal of the Lower Earnings Limit extends coverage to 1.3 million workers

The Lower Earnings Limit was an earnings threshold that excluded employees whose average weekly earnings fell below a specified amount. Under the old rules, part-time workers, those on zero-hours contracts, and lower-paid employees often didn't qualify for SSP regardless of their employment status.

From 6 April 2026, the LEL no longer applies to SSP eligibility. Employees qualify based on their employment status and other SSP conditions, not their earnings level. This extends SSP coverage to approximately 1.3 million additional workers who were previously excluded solely by falling below the earnings threshold.

New 80% of average weekly earnings calculation with £123.25 cap

The previous SSP system paid a flat weekly rate to all eligible employees regardless of their earnings. The 2026 reforms introduce a calculation based on 80% of an employee's average weekly earnings, subject to a maximum cap of £123.25 per week.

This means SSP payments now vary by employee. Lower earners receive 80% of their average weekly earnings. Higher earners converge on the statutory maximum of £123.25 per week, even when 80% of their earnings would produce a higher amount. Payroll systems must now compute average weekly earnings for each employee rather than applying a single flat rate.

How do the transitional rules work for sickness spanning 6 April 2026?

Sickness absences that started before 6 April 2026 and continued on or after that date require careful handling. The transitional rules protect employees who were already receiving SSP under the previous system.

If an employee's sickness absence began before 6 April 2026, the old rules continue to apply for the portion of absence that occurred before that date. This includes the three-day waiting period if it hadn't already been served. For the portion of absence from 6 April 2026 onwards, the new rules apply.

The key protection is that employees already receiving SSP at the previous flat rate shouldn't be disadvantaged by the switch to the 80% calculation. If the new calculation would result in a lower payment than the previous flat rate, the employee continues receiving the higher amount for that period of sickness.

Employers should document the method used for handling transitional cases. This documentation becomes important for audit defensibility if the Fair Work Agency investigates SSP payments during the changeover period.

What enforcement powers does the Fair Work Agency have for SSP underpayments?

The Fair Work Agency launched on 7 April 2026 with a specific remit that includes SSP underpayment enforcement. This represents a significant increase in the likelihood of investigations compared to the previous enforcement landscape.

Financial penalties for SSP underpayment can reach 200% of the underpaid amount, capped at £20,000 per individual worker. These penalties apply on top of the requirement to pay arrears. An employer who underpaid SSP to ten workers over several years could face arrears plus penalties totalling hundreds of thousands of pounds.

The six-year exposure window for back liability creates material risk. SSP underpayments from 2020 onwards could theoretically be investigated and penalised under the new enforcement regime. This makes historical SSP compliance a governance issue, not just a forward-looking payroll concern.

Investigations can be triggered by worker complaints or by non-compliant payslip records. The Fair Work Agency has authority to request payroll documentation and absence records going back six years.

What does this mean for international employers with UK headcount?

International companies employing in the UK face specific considerations that domestic employers don't. Whether you're using an Employer of Record or running your own UK entity, the SSP reforms affect your cost base and compliance obligations.

Cost implications for UK employment budgets

Day-one SSP increases the probability that very short absences generate statutory pay. Under the old rules, a one-day or two-day sickness absence cost nothing in SSP terms. Now, every qualifying day of absence from day one triggers a payment, significant given that 70% of sickness absences last just 1-3 days.

Teamed's analysis of UK payroll patterns suggests this creates a predictable cost-base uplift that employers should model in absence-rate scenarios, aligned with government estimates that reforms will increase SSP costs by £420 million annually. For a company with 50 UK employees and typical absence rates, the additional SSP cost from eliminating the waiting period could add several thousand pounds annually to employment costs.

The removal of the Lower Earnings Limit also affects employers with part-time or variable-hours workers. Employees who previously fell outside SSP eligibility now qualify, expanding the population of workers who can claim statutory sick pay.

Questions to ask your EOR or payroll provider

If you're employing in the UK through an Employer of Record, the EOR is the legal employer responsible for SSP compliance and payment.

You should verify with your provider how they've implemented the 6 April 2026 changes. Specifically, ask about day-one SSP triggers in their payroll system, how they calculate average weekly earnings for the 80% calculation, and how they're handling transitional cases for sickness that spans the changeover date.

International companies employing in the UK via an EOR should also contractually verify who bears SSP arrears, penalty, and defence costs. Statutory liability may sit with the legal employer even when the client company controls absence processes. If your EOR gets SSP wrong, you need to understand your exposure.

For companies running their own UK entity, the questions shift to your payroll bureau or in-house team. Have they updated their systems for the new calculation method? Do they have documentation for the transitional handling approach? Can they provide audit-ready payslip records that demonstrate correct SSP treatment?

How SSP compliance connects to employment structure decisions

The SSP reforms add another layer to the decision about how to structure UK employment. For companies early in their UK presence, using an EOR transfers SSP compliance responsibility to a specialist provider. This can be valuable when you don't have in-house UK payroll expertise.

As UK headcount grows, the economics shift. Teamed's Graduation Model framework helps companies evaluate when the recurring costs of EOR exceed the costs of running their own UK entity.

A company with 10-15 UK employees typically reaches the threshold where entity establishment makes economic sense. At that point, SSP compliance becomes your direct responsibility rather than your EOR's. The 6 April 2026 changes make that responsibility more complex than it was before.

Do the new SSP rules apply to part-time workers?

Yes. The removal of the Lower Earnings Limit specifically addresses the previous exclusion of many part-time workers from SSP eligibility. Under the old rules, part-time employees whose average weekly earnings fell below the LEL threshold didn't qualify for SSP regardless of their employment status.

From 6 April 2026, part-time workers qualify for SSP based on the same criteria as full-time employees. They must be employees (not self-employed), be absent from work due to sickness, and meet the other SSP conditions. Their earnings level no longer determines eligibility, addressing the issue where previously 33% of part-time employees received neither SSP nor company sick pay during absences.

The 80% calculation applies to part-time workers based on their actual average weekly earnings. A part-time employee earning £150 per week would receive SSP of £120 per week (80% of £150). A part-time employee earning £200 per week would receive the capped amount of £123.25 per week.

What is the SSP rate for 2026-2027?

SSP for the 2026-2027 tax year is calculated as 80% of an employee's average weekly earnings, capped at £123.25 per week. This replaces the previous flat-rate system where all eligible employees received the same weekly amount regardless of their earnings.

The £123.25 cap functions as a hard ceiling. Employees whose 80% calculation exceeds this amount receive £123.25. Employees whose 80% calculation falls below this amount receive the calculated figure.

For example, an employee with average weekly earnings of £400 would have an 80% calculation of £320. Because this exceeds the cap, they receive £123.25 per week. An employee with average weekly earnings of £120 would have an 80% calculation of £96, which they receive in full because it falls below the cap.

Practical checklist for UK SSP compliance

Here's what I'd check this week if I owned UK payroll risk.

What to Check Before Your First April Payroll Run

The 6 April 2026 SSP reforms represent a significant shift in UK statutory sick pay obligations. Day-one entitlement, expanded eligibility, and the new calculation method all create operational changes for employers. The Fair Work Agency's enforcement powers add financial risk to compliance failures.

For international companies with UK headcount, these changes fit into the broader challenge of managing UK employment compliantly. Whether you're using an EOR, running your own entity, or evaluating which structure makes sense for your situation, SSP compliance is now more complex than it was before.

Not sure if your UK setup is handling these changes properly? Worried your EOR might have missed something? Let's talk through it. Book your Situation Room and we'll review your SSP approach, spot the gaps, and help you decide what needs fixing.