An umbrella company in your supply chain deducts PAYE from a worker's wage and never sends it to HMRC. Under the rules that took effect on 6 April 2026, HMRC does not chase the umbrella for that money first. It comes to your agency, for the whole amount.
That is not a reading of the legislation. It is how HMRC describes its own approach: joint and several liability "will allow HMRC to pursue an agency in the first instance for any payroll taxes that a non-compliant umbrella company fails to remit to HMRC on their behalf."1
HMRC's live guidance for agencies, updated in June once the rules were in force, puts it in one sentence with no hedging: "If we find an umbrella company has not paid the correct amount of PAYE to us, we'll recover it from you."3
Most of what has been written about this reform was written for accountants, and most of it landed before the rules were live. Five months in, the question for an operator is narrower. What do you need to be able to see, and how fast, to avoid learning about a default from a determination notice.
What actually changed on 6 April
The Finance Bill 2025-26 added a new Chapter 11 to Part 2 of the Income Tax (Earnings and Pensions) Act 2003. Where an umbrella company sits in a labour supply chain, the umbrella and a "relevant party" are jointly and severally liable for the PAYE due on payments to the worker.2
The relevant party is the employment agency that contracts with the end client. Where there is no agency in the chain, it is the end client instead. Joint and several means HMRC can take the entire amount from one party and leave that party to chase the others through the civil courts. The mechanism is a Regulation 80 determination, and it is addressed to you.2 HMRC sets out how the amount itself is worked out in its own manual.4
You are not the backstop in this arrangement. You are the first door HMRC knocks on.
Why "our umbrella has always been fine" stopped being a position
Around 700,000 people in the UK are paid through umbrella companies.1 HMRC forecasts this measure will bring in between £155 million and £715 million a year, which is a reasonable proxy for the size of the leak it was written to close.1 That money is not going missing at the margins.
The reform did not make umbrella companies riskier than they were in March. It moved who pays when one of them fails. And the exposure does not fall with the number of providers you use. An agency running everything through one long-standing umbrella has concentrated the risk rather than reduced it, because a single default now lands whole, on one balance sheet, with no one else in the chain to share it.
What due diligence still buys you, and what it never will again
This is the part worth reading twice. Chapter 11 works on a strict liability basis. In Deloitte's analysis of the drafting, "a relevant party cannot discharge the liability through a reasonable excuse or care taken in prevention," which is a deliberate departure from the reasonable-care test that operators are used to under Chapter 10 and IR35.2
Read plainly: the due-diligence pack you signed at onboarding does not reduce what HMRC can collect from you by a single pound. It never will. That does not make checks worthless, but it does change what they are for.
What checks still buy you
- Warning in the pay cycle a variance appears, not at the annual review
- Grounds to stop placing through a provider while the exposure is still small
- A per-worker payment trail to support civil recovery from other chain parties
- A dated record of when you knew and what you did about it
What they no longer buy you
- A statutory defence, because there is not one
- Any reduction in what HMRC can pursue from your agency
- Protection earned by a provider being sound for six years
- Comfort from an onboarding pack signed once and filed
The four checks, ordered by how fast they pay off
None of these need new software to start. The first one can be run this month against exports you already hold.
- Reconcile what you paid against what was reported, per worker, per period
This is the only check that can surface a default in the cycle it happens rather than a year later. The question is not whether a provider is compliant in the abstract. It is whether, for this worker and this week, the money you paid out matches what the intermediary reported. It is the same reconciliation that surfaces ghost workers on your own payroll, run against a different list.
- Turn the approved-intermediary list into a block at the point of booking
A register that a coordinator can place around is a document, not a control. If an unapproved umbrella can receive a placement at 7am because a shift needed filling, you will find out at audit.
- Put a date on everything
Because there is no reasonable-care defence, your records are not there to excuse the liability. They are there to prove when you spotted a problem and what you did next, which is what a recovery claim against another chain party will turn on. The artefacts worth retaining are listed separately.
- Run the reconciliation on a schedule nobody controls
A monthly job that fires whether or not anyone remembers, with the output going to someone outside the branch being reconciled. A check the reconciled party can quietly skip is not a check.
The full evidence model, including which artefacts to retain and why each one matters under joint liability, is set out on our UK umbrella reform page. This post is about the speed of detection. That page is about the records. The build that produces both is the attendance-to-payroll loop, because a per-worker payment trail is a by-product of reconciling attendance once rather than retyping it. HMRC also publishes its own labour supply chain assurance guidance, which is worth reading alongside your own controls.5
Where it broke
The first version of the intermediary control we built was a warning rather than a block. A coordinator filling a shift at seven in the morning could read the dialog, click past it and place the worker through an unapproved umbrella, and several did, because the shift in front of them mattered more than a dialog about a supply chain. The register was accurate and useless at the same time. It only became a control when it started refusing the booking outright, which the branch hated for about a week and then stopped noticing.
What this looks like if you do nothing
Nothing happens, for a while. Umbrella defaults are not announced. The worker is paid, the deduction appears on their payslip, and the gap between what was deducted and what was remitted sits somewhere you are not looking. The reform did not create that gap. It decided who pays for it, and it chose you.
None of this is tax or legal advice, and your own supply chain is the thing that matters rather than the general shape of the rules. Take the legal position from your advisers. The operational position is simpler: the sooner you can see a mismatch, the more choices you still have.
If you operate outside the UK as well, this is one of several dated obligations pulling in the same direction. We track them on the compliance page, including the EU Platform Work Directive and Dutch Wet DBA enforcement, both of which ask for the same thing this reform asks for: records that show what actually happened to a worker and a payment.
You cannot audit your way out of this one. You can only find out early enough to still have a choice.The rule, in one line
Bring one pay cycle and your list of umbrellas.
We will show you how many worker-periods you can currently reconcile against what the intermediary reported, and how many you cannot. The second number is your exposure, and it usually takes about thirty minutes to find.
Request a free 30-minute teardown →Sources
- HM Revenue & Customs, Umbrella company market: changes to Income Tax rules to tackle non-compliance: approximately 700,000 individuals work through umbrella companies; "Joint and several liability will allow HMRC to pursue an agency in the first instance for any payroll taxes that a non-compliant umbrella company fails to remit to HMRC on their behalf"; measure takes effect from 6 April 2026; forecast exchequer impact of £155 million to £715 million a year.
- Deloitte, Umbrella company legislative change: a new era of joint and several liability: new Chapter 11 of Part 2 ITEPA 2003 via Finance Bill 2025-26; the relevant party is the employment agency contracting with the end client, or the end client where there is no agency; "a relevant party cannot discharge the liability through a reasonable excuse or care taken in prevention", in contrast to Chapter 10; HMRC pursues the relevant party by Regulation 80 determination.
- HM Revenue & Customs, PAYE rules for labour supply chains that include umbrella companies from 6 April 2026, guidance updated 19 June 2026: "If we find an umbrella company has not paid the correct amount of PAYE to us, we'll recover it from you."
- HM Revenue & Customs, Employment Status Manual: ESM2420 on Chapter 11 joint and several liability, and ESM2430 on quantifying the liability.
- HM Revenue & Customs, Help with labour supply chain assurance (GfC12): HMRC's guidelines for compliance on assuring a labour supply chain.
- ShiftMargin, UK umbrella reform and the evidence it expects: the operational records implied by joint and several liability, and where automation genuinely helps.