Taupo Consulting All articles
Finance & Operations

The File Behind the Fee: A 45-Day Off-Payroll Evidence Review for UK Boards

Taupo Consulting
The File Behind the Fee: A 45-Day Off-Payroll Evidence Review for UK Boards

Photo by Photo by Winston Tjia on Unsplash on Unsplash

Off-payroll working is frequently debated as a question of status. For a board, the more useful question is evidential: can the company demonstrate how each determination was reached, and does the operating reality support it? HMRC enquiries rarely begin as a philosophical discussion about control and substitution. They begin with requests for contracts, status determination statements, agency correspondence, invoices, project records and evidence of how managers actually directed the work.

A 45-day evidence review is not a legal opinion and it does not replace specialist tax advice. It is a governance exercise. Its purpose is to establish whether the company could produce a coherent file if challenged, and to identify where that file is thin before the thinness becomes expensive.

The determination is a conclusion; the evidence is the case

A status determination statement, or SDS, is a conclusion. It records the client's view and the reasons for it. It is not, by itself, proof that the conclusion is right. Boards should therefore distinguish between three things: whether an SDS exists, whether it was properly communicated through the chain, and whether its reasoning is supported by the contract and by actual working practices.

In a medium or large private-sector client, responsibility for determining status sits with the client, not the agency or the contractor's personal service company. Where the chain is longer, the SDS must reach the party it concerns. Where a contractor disagrees, there should be a process for responding. These are not administrative niceties. They are the mechanics by which liability can shift or remain.

Days 1 to 10: scope the population and select a risk-based sample

The review should begin with a clean population. Finance, procurement and HR should combine contractor spend, purchase orders, agency placements, payroll records and PSC payment data into a single engagement list. Reconcile the list to the ledger. Contractors paid through accounts payable but absent from the contractor register are a warning sign in themselves.

Sampling should be risk-based rather than random. Prioritise engagements with high day rates, long duration, significant spend, agency intermediation, missing SDS documentation, recent role changes, or managers with a history of informal extensions. Include at least one engagement that appears straightforward. A sample that only finds problems in the obvious places may be too narrow.

For each engagement, record the role, business area, hiring manager, contract dates, agency chain, payment route, SDS date, renewal history and any known disagreement. Assign an owner for missing documents. The output of this phase is not an answer; it is a controlled list of questions.

Days 11 to 25: reconcile the chain

The second phase tests whether the paperwork connects. Start with the contract between the client and the agency, then follow the chain to the contractor's personal service company. Check that the role described in the contract matches the role actually performed. Check that the SDS identifies the correct party and was passed through the chain. Check that invoices, timesheets and purchase orders tell the same story about dates, rates and deliverables.

Agency chains are a common source of drift. A substitution clause may exist in the agency contract but never be mentioned to the client. An SDS may sit with the agency but never reach the contractor. A manager may extend an engagement without updating the contract. None of these facts automatically determines status, but each weakens the evidential file.

This is also the point to examine onboarding and administration. Was the contractor given a staff email address, included in the organisation chart, invited to staff-only events or enrolled in internal training? Was expense reimbursement handled like an employee's? These details are not decisive on their own, but they are the kind of contemporaneous evidence that shapes how a review is perceived.

Days 26 to 35: test the contract against working reality

The written contract matters, but it is not the whole picture. The review should compare the terms with how work is actually controlled. Who sets the hours, location and sequence of work? Who supervises the contractor day to day? Can the contractor send a substitute in practice, and is there a process for doing so? Does the contractor bear financial risk, provide equipment or carry insurance? Is the role embedded in the organisation, or is it a discrete piece of work with a defined outcome?

Interviews should be short and structured. Ask hiring managers what they control and what they do not. Ask contractors how work is assigned and reviewed. Keep notes. The aim is not to catch people out, but to establish whether the contract is an accurate description of the engagement. Where it is not, the board needs to know whether the gap is documentary, behavioural or both.

Days 36 to 45: classify, remediate and set governance

By the final phase, each sampled engagement should be placed into one of four categories: supported, inconsistent, unsupported or unknown. Supported engagements have a determination, a communicated SDS, consistent contracts and working practices that do not contradict the conclusion. Inconsistent engagements have gaps that can be corrected. Unsupported engagements have evidence that points the other way. Unknown engagements lack enough evidence to form a view.

Remediation should be proportionate. Actions may include obtaining missing SDS documentation, correcting contract terms, changing working practices, moving an engagement to payroll, or taking specialist advice on disclosure. The board does not need to resolve every technical question in the sprint. It does need to record decisions, owners and deadlines.

Governance should then be adjusted. Maintain a central contractor register. Require an SDS before payment is released. Review engagements at renewal and at any material change in role, rate or scope. Train hiring managers on the behaviours that undermine a determination. Sample the population annually. These controls are modest, but they turn a one-off review into a repeatable assurance process.

What the board should receive

A board paper should be short. It should state the population reviewed, the sample selected, the findings by risk category, an estimate of exposure where possible, and the remediation plan. It should identify decisions required: approve payroll conversion where evidence does not support off-payroll treatment, mandate contract remediation, or commission external advice. It should also state clearly what the review did not cover.

The liability is not created by looking. It is revealed by looking. A board that can produce a coherent file, explain its determinations and show that working practices match the contract is in a stronger position than one that cannot. Forty-five days is enough to find the gaps and put a system in place to close them.

All Articles

Related Articles

What One Company Owes Another: A 45-Day Board Review of Intercompany Recharges

What One Company Owes Another: A 45-Day Board Review of Intercompany Recharges

A Ledger With a Name Attached: Thirty Days to Reconcile Director Loans

A Ledger With a Name Attached: Thirty Days to Reconcile Director Loans

The Pledges Missing from the Pack: A 45-Day Guarantee Register for UK Boards

The Pledges Missing from the Pack: A 45-Day Guarantee Register for UK Boards