Skip to main content
Agency Growth1 September 2026 · 9 min read

Umbrella, PAYE and IR35: A Recruiter’s Guide to Contractor Pay Models

Temp and contract recruiters have to navigate a maze of pay models — agency PAYE, umbrella companies, and the inside/outside IR35 question — each with different admin, margin, and liability implications. This is a plain-English guide to what each model actually means for your desk, and how your CRM should handle the timesheet-to-invoice chain and pay transparency that go with them.

By The ATSpro Team

If you run a temp or contract desk, how your workers get paid is not a back-office detail — it shapes your admin, your margin, your compliance exposure, and what you must disclose to the worker up front. Yet the terminology (PAYE, umbrella, inside/outside IR35) is a genuine source of confusion, and getting the model wrong or misrepresenting it can create real liability. Here is the plain-English version.

This is practical guidance, not tax or legal advice — the off-payroll rules in particular are nuanced and status determinations should be made carefully, with advice where needed.

The three ways a contractor typically gets paid

1. Agency PAYE

The worker is paid through your agency's payroll as a PAYE worker. You deduct income tax and National Insurance at source and pay them net, handling holiday pay and employer obligations. Simplest for the worker to understand; most administrative responsibility on you.

2. Umbrella company

The worker becomes an employee of a third-party umbrella company. The umbrella receives the assignment rate from your agency, runs the worker's payroll, and handles their tax and NI. This shifts payroll admin off your desk, but introduces a party whose deductions the worker needs to understand — and whose conduct you should be comfortable with, since a non-compliant umbrella can create reputational and, increasingly, legal exposure for the agencies that use them.

3. The worker’s own limited company (PSC)

The contractor operates through their own personal service company. This is where IR35 / off-payroll working rules come squarely into play, because the question becomes whether the engagement is genuinely one of self-employment or is really disguised employment.

IR35 / off-payroll: inside vs outside

IR35 exists to stop people who are, in substance, employees from paying less tax by working through a company. The core question for each engagement is its status determination:

  • Outside IR35 — the engagement is genuine self-employment. The contractor's company is paid gross and handles its own tax.
  • Inside IR35 — the engagement is, in substance, employment. Employment taxes must be deducted, and the tax treatment looks much more like payroll.

Under the off-payroll rules, for many engagements the responsibility for determining status — and often the tax liability if it is got wrong — has shifted onto the client and/or the agency in the chain rather than the contractor. That makes it your business to understand, because "the contractor said they were outside" is not a defence if the determination was unreasonable.

The Key Information Document connection

This is where pay models meet compliance. The Key Information Document must show the worker who pays them, the deductions they will face, and a representative gross-to-net example. If a worker is going via an umbrella, the KID must reflect the umbrella's deductions honestly. Pay-model transparency is not a nicety — it is a documented obligation, and the KID is where it lands.

The admin chain: timesheet to invoice to margin

Whatever the model, the money has to flow: the worker submits hours, those hours are approved, you invoice the client, the worker (or umbrella) is paid, and you need to know your margin on the deal. Each pay model routes that flow slightly differently — different pay recipients, different deductions, different margin arithmetic. Doing this across models by hand, per contractor, per week, is where errors and lost margin creep in.

The takeaway

Pay models are not just the worker's concern — they determine your admin, your margin, your disclosure obligations, and increasingly your liability. Know which model applies, be able to explain its effect on take-home clearly, get IR35 status determinations right, and let your CRM carry the timesheet-to-margin arithmetic so nothing leaks. For the documentation side, see our Reg 15/17 guide; for the workers themselves, Right to Work.

Frequently asked questions

What is the difference between PAYE and umbrella for contractors?
Under agency PAYE, the worker is paid through the agency's own payroll with tax and National Insurance deducted at source, and the agency handles holiday pay and employer obligations. Under an umbrella model, the worker becomes an employee of a third-party umbrella company that receives the assignment rate and runs the worker's payroll. Umbrella shifts payroll admin off the agency but introduces a third party whose deductions the worker must understand and whose compliance the agency should be comfortable with.
What does inside and outside IR35 mean?
IR35 (off-payroll working) determines whether a contractor working through their own limited company is genuinely self-employed or is, in substance, an employee. Outside IR35 means the engagement is genuine self-employment and the contractor's company is paid gross. Inside IR35 means the engagement is effectively employment, so employment taxes must be deducted. Under the off-payroll rules, responsibility for the status determination and often the tax liability has shifted onto the client and/or agency for many engagements.
How does the pay model affect the Key Information Document?
The Key Information Document must show who pays the worker, the deductions they will face, and a representative gross-to-net pay example. If the worker is engaged via an umbrella company, the KID must honestly reflect the umbrella's deductions. The pay model therefore directly determines what the KID must disclose, making pay-model transparency a documented legal obligation rather than an optional courtesy.
Does a recruitment CRM need to handle different contractor pay models?
Yes. Each pay model routes the timesheet-to-invoice flow differently — different pay recipients, deductions, and margin arithmetic — so doing it by hand per contractor per week invites errors and lost margin. A CRM should run the timesheet-to-invoice chain and compute margin per placement accounting for the pay route, and generate a Key Information Document with an accurate gross-to-net example for the model in use. ATSpro does both as standard.

Keep reading

UK ComplianceReg 15 and Reg 17 Explained: A Plain-English Guide for UK AgenciesWhat Regulation 15 (Assignment Confirmation) and Regulation 17 (Key Information Document) actually require under the Conduct Regulations — when they apply, what must be in each, and how your CRM should generate them automatically.UK ComplianceRight to Work Checks in 2026: What UK Recruitment Agencies Must Get RightA practical guide to Right to Work checks for UK recruitment agencies in 2026 — manual, digital identity (IDVT), and Home Office online share-code checks, who is liable, penalties, and how your CRM should track it all.Agency GrowthBusiness Development Outreach for Recruiters That Actually Gets RepliesA practical guide to BD outreach for recruitment agencies — how to find the right decision-makers, write cold emails that get answered, and run multi-touch sequences without sounding like every other recruiter in their inbox.

See ATSpro on your own data

A UK recruitment CRM at £49/user/month — AI assistant, 14 background agents, full UK compliance, free migration. Book a 20-minute demo with the founder.

14-day free trial · No credit card required · Cancel anytime