Joint and several PAYE liability turned supply-chain due diligence into an operations problem
An agency can now be pursued by HMRC for PAYE that an umbrella company in its supply chain deducted and failed to remit. Policy documents describe the risk. This page is about the operational evidence.
From 6 April 2026, where an umbrella company sits in a labour supply chain, the umbrella and a relevant party are jointly and severally liable for amounts payable under PAYE. Where an agency supplies the worker, that relevant party is the agency; where no agency is involved, it is the end client. Joint and several means HMRC can pursue the full amount from any single party in the chain and leave that party to recover contributions from the others through civil proceedings (Grant Thornton, Deloitte).
This is not tax advice, and it is not a page about how to structure a supply chain. Take that advice from your accountant and your lawyer. What follows is the part that lands on the operations team: the reform converts a commercial relationship into a continuous evidence obligation, and evidence obligations are workflow problems.
What changes in day-to-day operations
- Umbrella status becomes a monitored attribute, not a one-off check. A due diligence pack signed at onboarding says nothing about whether remittance is happening this month.
- Per-worker, per-period reconciliation matters. The question you may have to answer is not "is this umbrella compliant" but "for this worker, in this period, what did we pay, what was deducted, and what evidence do we hold."
- Chain visibility has to be enforced at booking. If a worker can be placed through an unapproved intermediary because a coordinator was in a hurry, the control does not exist.
- Records have to survive people leaving. Institutional memory in a coordinator's inbox is not an audit trail.
The evidence an agency wants on file, automatically
| Evidence | Why it matters under joint liability |
|---|---|
| Approved-intermediary register, enforced at placement | Prevents off-register placements rather than discovering them at audit |
| Per-assignment payment trail | Links each worker, shift, rate and payment to the entity that paid it |
| Reconciliation of what you paid against what was reported | The mismatch is the early warning that a chain party is not remitting |
| Timestamped due-diligence artefacts | Shows a continuing process, not a filing-cabinet exercise |
| Exception and escalation log | Demonstrates that anomalies were seen and acted on, with dates |
The overlap with margin work is the point. Every item above is a by-product of a closed attendance-to-payroll loop. An operator who automates that loop to cut leakage gets the liability evidence for free — the same build, two returns. That is a considerably easier business case than a compliance project with no operational upside.
Where automation genuinely helps, and where it does not
It helps with continuity: checks that run every cycle rather than every renewal, reconciliations that flag a variance the week it appears, and logs that assemble themselves. It does not help with the commercial decision about which intermediaries you work with, or with the legal question of how your contracts allocate recovery between chain parties. Software cannot make an unsound supply chain sound; it can stop a sound one from drifting quietly.
ShiftMargin builds operations software. Nothing here is tax or legal advice, and the rules summarised above should be confirmed with your advisers against your own supply chain.
Questions operators ask
Which party does HMRC pursue first?
Guidance indicates HMRC starts with the party directly above the defaulting umbrella in the chain — in agency-supplied labour, that is typically the agency. Because liability is joint and several, the full amount can be sought from one party, who must then recover from others civilly. Confirm the specifics with your advisers.
Does this apply if we only use one long-standing umbrella?
The liability attaches to the arrangement, not to how long the relationship has run. A single trusted provider concentrates rather than removes the exposure, which is why continuous reconciliation matters more than provider count.
What does automation actually change here?
It changes frequency and completeness. Per-worker payment trails, variance checks between what you paid and what was reported, and self-assembling exception logs move due diligence from an annual document exercise to a monthly control.
Is this a compliance product?
No. It is the evidence by-product of automating attendance, payroll and invoicing from a single reconciled record. We sell cost-to-serve reduction; the audit trail comes with it.
If the evidence lives in inboxes, that is an operations problem.
A two-week Ops Audit maps where your placement, payment and reconciliation records actually sit, and what it would take to make the trail assemble itself.
Request a free 30-minute teardown →