Employer of Record UK: How It Works & When You Need One

What an employer of record actually is

An Employer of Record (EOR) is a third-party organization that legally employs a worker on a company's behalf in a country where that company has no registered entity. The EOR holds the employment contract, runs payroll, and files the required tax and benefits paperwork, while the client company directs the person's actual day-to-day work.

Most HR leaders treat UK hiring as a payroll logistics problem: get someone paid, get them into a pension scheme, move on to the next req. That framing skips over what's actually happening underneath. Someone has to legally hold the employment relationship, answer to HMRC, and carry the liability if a dismissal goes wrong or a filing is late, and the whole point of an EOR is deciding who that someone is going to be.

The advantages of using an EOR mostly come down to speed, agility, and compliance, and all three exist for the same reason: the EOR, not the client company, is the party legally on the hook. That's a different question than "how do we get this person paid," and it's the one that actually determines whether hiring in the UK takes two weeks or six months.

The difference between an EOR and running your own UK payroll

Running your own UK payroll means your company has registered as an employer with HMRC, opened a PAYE scheme, and accepted direct legal responsibility for that worker. Using an employer of record UK means a licensed third party takes on that registration and liability instead, so your company never needs a UK entity at all.

The practical difference shows up the moment something goes wrong. If a payroll filing is late or a dismissal is mishandled under your own registration, your company answers for it directly. Under an EOR arrangement, the provider is contractually and legally the employer, which is the entire reason the structure exists rather than being a workaround.

Why companies without a UK entity can't just 'add someone to payroll'

That liability question starts with a basic legal fact: a company can't put a UK-based worker on payroll without a UK entity registered with HMRC and an open PAYE scheme. Without that registration, there's no lawful way to withhold income tax or deduct National Insurance, and that's the exact gap an employer of record UK is built to close.

This isn't a matter of preference or process maturity. Without a UK entity, a company has no way to:

• Register as an employer with HMRC
• Open and operate a PAYE scheme
• Deduct National Insurance contributions lawfully
• Issue compliant payslips and year-end tax forms

This is precisely the role an employer of record fills.

An EOR in the UK legally employs workers on behalf of another company, which means it, not the client business, handles payroll, taxes, and the compliance obligations that come with having staff on the ground.

The practical effect is that a foreign company can have someone working full-time in London, drawing a UK salary, and accruing UK statutory benefits, without that company ever registering with HMRC itself. The EOR's existing registration and infrastructure cover it.

What an EOR is legally responsible for once someone is hired

Closing that gap is only step one. Once an EOR hires someone in the UK, it takes on responsibility for running PAYE payroll, filing reports with HMRC, and guaranteeing every statutory entitlement the law requires, from paid leave to pension enrollment. The client company stops holding the tax and benefits risk, the EOR holds it instead.

In practice, that means managing PAYE payroll reporting with HMRC: calculating income tax, deducting National Insurance, submitting Real Time Information reports on or before each payday, and issuing tax forms such as the P60 at year-end. The client company never registers for UK payroll tax at all, because the EOR's own registration already covers it.

Payroll mechanics are only part of the job, though. UK employment law sets a floor of statutory rights that apply regardless of who signs the paycheck, and the EOR has to administer every one of them correctly.

UK employees are entitled to statutory rights that don't change based on who employs them, including:

• 5.6 weeks of paid annual leave
• National Minimum Wage compliance
• Statutory sick pay
• Maternity and paternity leave
• Itemized payslips
• Workplace pension auto-enrollment with employer contributions

Getting any one of those wrong is what turns a routine hire into a tribunal claim, which is why "compliant" means something specific and checkable rather than a vague reassurance.

Key terms you'll run into when evaluating a UK EOR

Those responsibilities come wrapped in specific terminology, and comparing providers is hard if you don't already know what each term means. The words below show up in almost every EOR contract and HMRC filing tied to UK employment.

• PAYE (Pay As You Earn): the UK system for collecting income tax and National Insurance directly from wages before the employee is paid.
• RTI (Real Time Information): HMRC's requirement that employers report pay and deductions on or before each payday, rather than after the fact.
• P60: the end-of-year certificate showing total pay and tax deducted, which every UK employee must receive from their employer.
• Statutory sick pay (SSP): the minimum amount an employer must pay an eligible employee who is off sick, set by law rather than company policy.
• Auto-enrollment: the legal requirement to automatically place eligible workers into a workplace pension and contribute to it, unless the worker actively opts out.
• Entity: a registered legal business presence in a country, such as a subsidiary or branch, that gives a company standing to employ people directly and take on local tax obligations.

None of these terms are optional extras. Each one is a specific legal obligation that either the client company or the EOR has to own, and an employer of record UK exists precisely so the client company doesn't have to build the infrastructure to own it directly.

When an EOR is the right call versus opening your own entity

Everything above feeds into one practical decision: when does it make sense to use an EOR instead of opening a UK entity yourself? An EOR makes sense when you need someone employed quickly and don't yet know whether the market justifies a permanent legal presence, while opening an entity fits once you're confident you'll have a sizeable, lasting UK team and want direct control over local benefits design and tax structuring.

EOR services enable rapid market entry, letting a company test a new territory and scale its presence without committing to entity establishment first. That distinction matters most when a strong candidate has a competing offer today and a UK subsidiary would take months of legal work to stand up.

An EOR tends to be the right call when:

• You have one or a handful of UK hires, not a full office
• You're not yet sure the market will pan out
• A candidate needs to start within weeks, not quarters
• You want to avoid holding UK employment liability directly

An entity starts to make more sense once headcount climbs into the dozens, you need bespoke equity or benefits structures, or the UK becomes a strategic hub rather than a single hire.

Hiring through an Employer of Record is a strong option for businesses that have never hired outside their home country, and the same holds for multinationals with years of international hiring experience, who often keep using EOR arrangements for exactly this kind of test-and-decide hiring rather than incorporating in every market they touch.

What using an EOR actually saves you, and where the savings come from

Once an EOR is the right call, the value case for finance or leadership comes down to what you don't have to build: no UK entity registration, no local legal counsel on retainer, no in-house HR administration for a single hire, and no wind-down cost if the market doesn't work out. Those avoided costs, not a lower hourly rate, are where the actual business case lives.

Opening a legal entity is expensive, and closing one down if the market doesn't work out is often even more expensive. An EOR lets a company test a hire, or a market, at lower costs, then decide later whether a permanent entity is worth the investment.

This is roughly how Papaya Global structures its EOR offering: the client company keeps direction over the hire's day-to-day work, while the provider absorbs the registration, payroll, and legal liability that would otherwise require standing up a UK entity from scratch.

Put the avoided costs side by side and the case is straightforward:

• Entity incorporation and ongoing UK filings
• Local employment counsel for contracts and terminations
• Payroll software and HR administration overhead
• Wind-down costs if the hire or the market doesn't work out

Each of those line items has a real dollar figure attached in a legal or finance budget, which is why the EOR conversation lands better with a CFO when it's framed as avoided spend rather than a vendor fee.

How to vet an EOR so a fast hire doesn't become a compliance liability

Savings only matter if the provider actually delivers on compliance, so vetting comes down to one question: does this provider genuinely absorb employment liability in the UK, or does it just process payroll and quietly leave the compliance risk with you? Ask about entity ownership, onboarding timelines, visa handling, and the exit process before signing anything.

Before committing to a provider, get clear answers on:

• Does the provider own or lease its UK entity, or subcontract to a local partner you've never vetted?
• How many days does onboarding actually take, in the contract, not in a sales deck?
• Who handles visa sponsorship and immigration paperwork if the hire needs it?
• What's the contract term and exit process if the role or the market changes?
• Who is contractually liable if a tax filing is late or a dismissal is handled badly?

Budget providers often win on price and lose on onboarding. Visa delays, contract rigidity, and support that disappears once the contract is signed are the most common failure points, and those failures cost far more than the provider's fee once a hire's start date slips or a dispute ends up in front of an employment tribunal. A provider that can quote a fast turnaround but can't say who owns the UK entity behind it is a red flag, not a selling point.

Putting it together: your next step for hiring in the UK without an entity

Weigh the savings against the vetting risks and the decision comes down to one question: does this hire justify the cost and time of a UK entity, or is it faster and cheaper to have a licensed third party hold the employment relationship instead? Setting up a UK entity means registering with Companies House, opening a local bank account, running payroll through HMRC, and maintaining ongoing filings, all before the first paycheck goes out. For a single hire, or a market you're still testing, an employer of record UK almost always wins on speed and lower upfront cost, since the entity-setup timeline and legal fees don't apply.

That said, the choice isn't purely about speed. Providers vary widely in how much liability they actually absorb and how fast they can onboard someone compliantly. Some hold only partial responsibility for tax and employment compliance, leaving the hiring company exposed if something goes wrong with contracts, statutory benefits, or termination procedures. Others take on the full employer liability, which changes who's on the hook if HMRC or an employment tribunal comes asking questions later.

For a closer look at what to compare across providers, this guide to employer of record services walks through the evaluation criteria in more depth, and it's worth reading before signing anything longer than a few pages. Papaya Global's own model is built around absorbing the full liability rather than partial compliance, which is a reasonable benchmark to check any other provider against when comparing contracts side by side.

Whichever route you choose, the underlying question doesn't change: someone has to legally hold that UK employment relationship, and it's worth knowing exactly who before the offer letter goes out. Getting that answer wrong doesn't just cost money later, it can mean redoing the hire entirely under a different structure.