Blog

Payrolling a benefit for an assignee: a voluntary choice still needs a cited basis

Reporting expenses and benefits through payroll is voluntary, but it is not free of conditions, and the guidance page that describes the service is not the same text as the obligation it sits under. This post separates the two, walks the registration timing an employer has to read before the tax year starts, and states plainly what the published material leaves open for an assignee who arrives or leaves mid-year.

The getax team · 5 min read

A thin card hovers above a thick slab of the same shape, linked by a slim pin, casting a soft shadow.

The choice is real, and so is the paperwork behind it

An employer may choose to report the taxable value of expenses and benefits through payroll rather than on a year-end return. HMRC publishes guidance describing that service, how to register for it, and what happens to the employee's tax code once benefits are taxed in real time.

That guidance is a description of a service. It is not, by itself, the authority for the employer's reporting obligation, the valuation of the benefit, or the National Insurance charge the employer still carries. When an adviser signs an employer position, those are separate texts, and they should be cited separately.

The distinction matters most where it is easiest to lose: an inbound or outbound assignee, part of a year here, a benefit that starts or stops with the assignment, and a payroll that may be operated by someone other than the legal employer.

What the service guidance actually tells you

Read the guidance page for what it does say. It tells you the service exists, that registration is done in advance of the tax year in which you want to payroll, which categories of benefit can and cannot be reported this way, and that employees must be told what is being payrolled and what the cash equivalent is.

It also tells you that registering is not retroactive. An employer who misses the registration window for a tax year reports for that year the old way, whatever the payroll system is already configured to do.

Those are operational facts. They set the timing of the decision. They do not establish the amount of the benefit, and they do not remove the year-end obligation on the employer-side National Insurance charge, which continues to run on its own schedule.

The obligation underneath it

Behind the service sits the statutory duty to report earnings and benefits, the rules that fix the cash equivalent of each kind of benefit, and the employer's National Insurance charge on benefits that are not payrolled for that purpose.

An adviser defending a position needs both references in the file: the guidance that says the voluntary route is open and how it is entered, and the provision that says what must be reported and at what value. One text explains the mechanism; the other explains why the number is the number.

This is what a source walk is for. Open two or three key figures with the client and show where each lives: the cash equivalent in the charging provision, the registration condition in the guidance, the National Insurance charge in its own place. Three different texts, three different pages, one employer position.

Timing changes cash flow, not just admin

Payrolling moves the employee's tax on a benefit from a later code adjustment into the pay periods of the year in which the benefit is provided. For a settled employee, that is usually a smoother outcome. For an assignee, it can be the opposite.

Where a tax equalisation or protection arrangement applies, tax taken in real time changes what the employer funds and when, and it changes the gross-up conversation during the assignment rather than after it. Where the assignee is paid partly from a home-country payroll, real-time reporting can split a single benefit across two reporting streams.

None of that makes the choice wrong. It makes it a decision with a date attached, which has to be taken before the tax year begins rather than discovered at year end.

What the published material leaves open

Absence is information. Here is what the guidance, read on its own, does not settle for assignee populations:

Mid-year arrivals. The guidance addresses registration ahead of a tax year, not the treatment of a benefit that first becomes taxable here partway through one, for someone who was not on the payroll when registration was made.

Mid-year departures. Where a benefit continues after the assignee leaves the payroll, the guidance does not state how the remaining cash equivalent is reported once there are no further pay periods to carry it.

Split payrolls and host-employer arrangements. Where the entity operating the payroll is not the entity providing the benefit, the guidance does not resolve which of them registers, or whose record the payrolled amount belongs to.

Interaction with residence and treaty positions. Real-time taxation of a benefit does not decide whether the benefit is taxable here at all. That question is answered elsewhere, and the service guidance does not pretend otherwise.

We state these as gaps because they are gaps. An adviser can still reach a defensible answer on each, but the answer will come from other texts, and the file should show which.

How we would work this in practice

Start with the obligation, not the service. Establish whether the benefit is taxable here, for this person, for this part of the year. Then ask whether the voluntary route is open and whether entering it serves the employer.

Fix the date of the decision before anything else. Registration ahead of the tax year is a hard condition; everything downstream, including the assignee's code and the employer's funding, follows from meeting it or not.

Keep the National Insurance position separate in the file. It runs on its own text and its own deadline, and an employer who assumes payrolling swept it up has an exposure that will not show until year end.

The judgment stays human throughout. Our part is that the reviewer spends the time on the judgment rather than on finding the provisions.

Our own numbers, published

We publish our worst number next to our best, dated, every quarter, including the quarters where the worst number is bad. The current published range reads: "From 24% to 98%".

Alongside it we publish the counts we stand behind: 4,790+ as of September 2026, and 870+ as of September 2026.

If a figure in this post, or in any report we deliver, cannot be traced to the official text that says so, treat it as unverified. That standard is the only one worth holding us to.

All posts