TL;DR

A Status Determination Statement (SDS) is a written document issued by an end client under the off-payroll working rules (Chapter 10, ITEPA 2003) that sets out whether a contractor engaged through a personal service company (PSC) is inside or outside IR35. End clients who qualify as medium or large businesses must issue an SDS before any payment is made under the engagement. The SDS must state the determination and give reasons. Failure to issue a valid SDS means liability for any unpaid PAYE and NICs passes to the end client rather than the fee payer.

What This Means in Practice

The SDS is the legal mechanism by which IR35 liability is triggered and assigned in a supply chain. Without a valid SDS, the end client retains responsibility for any PAYE and NICs that arise from the engagement. This creates a strong incentive for clients to issue SDSs before engagements begin and to ensure the determination is properly reasoned. An SDS that states a conclusion without explaining the reasoning behind it does not satisfy the legislative requirements under Regulation 13C of the PAYE Regulations.

The SDS must include three things: the determination (inside IR35 or outside IR35), the reasons for that determination, and the date by which the determination was made. The reasons requirement is substantive - it means the client must document which employment status tests were applied, what evidence was considered, and why the tests pointed to the conclusion reached. An SDS that says "considered all relevant factors and determined outside IR35" without more is legally deficient and will not transfer liability to the fee payer if challenged.

Once issued, the SDS must be passed down the supply chain to every party in it. In a typical arrangement - end client, staffing agency, contractor's PSC - the client sends the SDS to the agency, and the agency passes it to the PSC. The contractor must receive the SDS before the first payment is made. If the agency fails to pass the SDS to the contractor, the agency assumes the client's position as the party holding undischarged liability.

The contractor has the right to challenge the SDS if they disagree with the determination. The challenge must go to the end client, which then has 45 days to consider the challenge and issue a response. If the client does not respond within 45 days, the off-payroll rules treat the SDS as having been withdrawn, and the client becomes the liable party for any PAYE and NICs arising until a new SDS is issued. The agency must also be notified of any updated SDS.

At the end of an engagement, if no replacement SDS is issued for a renewed contract, the original SDS remains in force. However, if the nature of the work, the working practices, or the contract terms change materially, the existing SDS no longer applies and a new one must be issued. Many agencies and clients treat contract renewals as a trigger for automatic SDS review.

Why Recruitment Agencies Need to Know This

Agencies sitting in the payment chain as the fee payer need the SDS to know whether to operate PAYE. An agency that pays a PSC invoice without holding a valid SDS is exposed: if the engagement is inside IR35 and no SDS was issued or received, HMRC can assess the agency for unpaid PAYE and NICs on all payments made. The fact that the client failed to issue the SDS does not automatically relieve the agency - the agency has its own obligation to request the SDS before making payment.

For agencies with large PSC contractor books, maintaining an SDS register is a compliance necessity. Each engagement requires a logged SDS, a date received, and a confirmation that it was passed to the contractor's PSC. Some agencies build this into their onboarding workflow as a gating condition: no first payment until SDS received and logged. This approach reduces HMRC exposure significantly because the liability transfer mechanism in Chapter 10 ITEPA 2003 operates cleanly only when the SDS exists and has been properly communicated.

Agencies also carry a business risk where clients issue blanket outside-IR35 determinations - a practice HMRC has challenged in multiple investigations. If the client issues outside-IR35 SDSs for an entire category of contractors (for example, all IT developers) without individual assessments, and HMRC subsequently determines that some or all of those engagements were inside IR35, the client carries the primary liability. But the agency, as the party that relied on and actioned those SDSs without question, may face scrutiny about whether it exercised reasonable care. Agencies should maintain documented evidence that they did not blindly accept blanket determinations without flag-checking them.

In Practice

A specialist finance staffing agency manages a book of 65 PSC contractors placed with a large investment bank. The bank issues SDSs in March ahead of the new tax year. Forty-one are determined inside IR35; twenty-four are determined outside. The agency receives all 65 SDSs via email, logs them in its compliance register against each contractor's file, and sends each contractor their individual SDS by the end of the same week.

Three contractors challenge their inside-IR35 determinations, arguing that their substitution rights are genuine. The agency forwards each challenge to the bank's procurement and tax team. Within 20 days, the bank responds to all three challenges with revised reasoning that confirms the original inside determination in each case. The bank sends updated SDSs to the agency; the agency sends them to the contractors. PAYE continues on all inside-IR35 arrangements from April 6.

Four months later, the bank extends 12 of the outside-IR35 engagements but changes the scope of work materially - the contractors are now embedded in day-to-day project delivery rather than advisory work. The agency flags to the bank that new SDSs are required for the 12 engagements. The bank re-runs the assessment and finds six of the twelve are now inside IR35. The agency begins operating PAYE on those six from the contract change date. The compliance register is updated.

Quick Reference