The P11D is being retired. Here’s what that actually means for your payroll, your people, and your next submission deadline.
I was speaking to an HR director at a mid-sized manufacturer last autumn who had no idea the P11D was effectively being abolished. She’d been running payroll the same way for eleven years and had assumed this was one of those HMRC consultations that gets quietly shelved. It wasn’t. April is real, it’s live, and if your business hasn’t prepared, the implications are more disruptive than most people realise.
From 6 April 2027, employers in the UK are legally required to report most employee benefits in kind, reporting them through Real Time Information (RTI) submissions rather than separately on an annual P11D form. The P11D isn’t dead everywhere yet, but for the vast majority of benefits, it’s done. And the adjustment required isn’t just administrative; it changes how your employees see their tax, how your payroll software runs, and how your year-end process looks.
This is your complete guide to what’s changing, what it means in practice, and how to make sure you’re compliant without losing your mind in the process.
What are payrolling benefits in kind, exactly?
A benefit in kind (BIK) is anything of value you provide to an employee that isn’t part of their salary, such as company cars, private medical insurance, interest-free loans, gym memberships, or living accommodation. Historically, you reported these annually via P11D forms submitted to HMRC after the tax year ended, and employees paid the resulting income tax through an adjustment to their tax code the following year.
Payrolling means you move that reporting into your regular payroll cycle. Instead of HMRC adjusting someone’s tax code retrospectively, the taxable value of their benefit is added to their gross pay each pay period, and the correct tax is deducted in real time. Simpler in theory. Marginally more complex to set up in practice.
The key shift employers need to understand is this: the tax liability isn’t changing. Employees aren’t paying more or less. The difference is purely in when and how it’s calculated. But that timing change has knock-on effects across your payroll software, your employee communications, and your month-end reconciliation.
- Mandatory — from 6 April 2027 — All qualifying benefits
- P11D abolished for — Most BIKs — Some exceptions remain
- Registration deadline — 5 April 2027 — Via HMRC online
- P11D(b) remains — Class 1A NIC — Employer NI is still reported
Why is HMRC doing this?
The honest answer is that the P11D system was always a workaround. It was designed for a world with paper-based payroll and annual processing cycles. The RTI infrastructure HMRC built from 2013 onwards makes real-time reporting the logical default, and benefits in kind were always the outlier that hadn’t been brought into line.
From HMRC’s perspective, mandatory payrolling closes a data gap, reduces end-of-year admin for their staff, and means employee tax codes are more accurate throughout the year rather than corrected retrospectively. It also removes the common situation where employees receive a tax code change in October and have no idea why their take-home pay suddenly dropped.
For employers, the stated benefit is a reduction in year-end workload. No more bulk P11D production. No more chasing benefit valuations in May for something that happened the previous summer. In practice, and I’ve seen this firsthand when working through the process with several employer clients, the upfront work of configuring your payroll system and training your team is significant. The year-end benefit arrives eventually. The transition pain is real.
What’s in scope, and what still uses P11D?
This is where most guidance gets vague. So let me be specific.
From April, the following benefits must be payrolled: company cars and vans, private medical and dental insurance, non-cash vouchers, and most other taxable benefits reported under Section 203 ITEPA 2003.
For employer-provided living accommodation (in most cases), interest-free or low-interest loans above £10,000, there is an option to either report it through P11D after the year-end or report through monthly payrolling.
HMRC has also confirmed that certain transitional arrangements apply for the first year, which your payroll provider should be flagging if they’re paying attention.
The P11D(b) form, the one used to report and pay Class 1A National Insurance on benefits, does not disappear. You still need to submit that and pay the associated employer NIC by 19 July (or 22 July if paying electronically) after the tax year ends. This catches a lot of people out who assume payrolling eliminates all end-of-year benefit reporting. It doesn’t. It just shifts the income tax side of it.
The thing most guides get wrong
Almost every article on this topic frames mandatory payrolling as purely an administrative change. It isn’t. It’s a cash flow change for employees, particularly those with high-value company cars or medical benefits. When the taxable value of a benefit is spread across twelve monthly pay packets instead of adjusted via a tax code change, some employees will see a noticeable reduction in their monthly take-home. Getting ahead of this with clear communication is not optional; it’s damage control.
The common mistakes employers are already making
After working through implementation with several UK businesses over the past year, the same errors keep appearing. Let me save you the trouble.
The first is assuming your payroll software is ready without checking. Most of the major platforms, Sage, Xero Payroll, BrightPay, and MHR, have updated their systems to handle payroll benefits, but the configuration is not automatic. You need to map each benefit type to the correct category, enter the taxable values, and test a payroll run before going live. I’ve seen businesses arrive in April with software that was technically capable but completely unconfigured.
The second mistake is leaving employee communication too late. If someone has a company car worth £8,000 in taxable benefit and they suddenly see an increase in their tax deduction from April, they will contact HR. Repeatedly. Having a one-page explanation ready of what’s changed, why their net pay looks different, and who to contact with questions prevents a significant volume of noise.
The third, and probably most technically consequential, is mishandling the mid-year valuation problem. Benefits that vary in value across the year, such as a car that changes in April, private medical cover that starts in September, need to be reflected accurately in each pay period. Getting that prorating right requires either excellent payroll software configuration or very careful manual oversight. Neither happens by accident.
Practical steps to get compliant
- Register with HMRC to receive payroll benefits via the employer’s PAYE Online account. This must be done before the start of the tax year you want to receive payroll benefits (so before 6 April 2027).
- Audit every benefit in kind your business currently provides. Create a complete list with taxable values, affected employees, and annual P11D figures. This is your baseline.
- Configure your payroll software. Enter benefit types, confirm the correct taxable value calculation method for each benefit category, and run a test payroll.
- Remove benefits from employee tax codes. Once you’re paying a benefit, HMRC should remove it from the relevant tax codes, but verify this has happened, especially for company car benefits, which are historically sticky.
- Communicate with affected employees before April. Explain the change, the impact on their payslip, and confirm their benefit details are accurate.
- Continue submitting P11D(b) after the year ends for Class 1A NIC. Payrolling doesn’t eliminate this obligation.
- Review your process after the first quarter. The first payroll run under the new system almost always surfaces configuration gaps; find them in May, not December.
“The businesses that navigate this smoothly aren’t the ones with the most sophisticated payroll teams. They’re the ones that started early and asked for help before the deadline, not after it.”
Where specialist support makes the difference
I’ll be direct here. For a business with a handful of employees and simple benefits, one or two company cars, and a group medical scheme, this is manageable with careful attention and a decent payroll platform. For businesses with complex benefit structures, variable valuations, internationally mobile employees, or a mix of PAYE schemes, this is genuinely difficult to get right without experienced payroll and tax support.
Firms like SKZ Accountants have been working through this transition with employer clients for the past twelve months. What that looks like in practice isn’t just ticking a compliance box; it’s auditing the existing benefit structure, identifying anything that’s been historically mis-categorised on P11Ds, configuring payroll correctly, and producing the employee communications that prevent post-April confusion.
The value of working with a firm that understands both the payroll mechanics and the tax implications is that you catch the edge cases. What happens when an employee returns a company car mid-year? How do you handle a benefit that was incorrectly reported on previous P11Ds? What if your payroll software vendor’s implementation of payroll benefits doesn’t align with how HMRC expects the figures to appear in RTI submissions? These are real questions that come up, and they’re not answered by reading HMRC’s guidance notes.
SKZ Accountants works specifically with UK employers navigating exactly this kind of compliance transition, payroll, BIK reporting, Class 1A NIC, and the advisory side of making sure your employee benefits structure is both compliant and tax-efficient going forward.
Final Words
Mandatory payrolling of benefits in kind is, in the long run, a sensible reform. The P11D system was clunky, the annual correction of tax codes was confusing for employees, and RTI is a far more rational infrastructure for this kind of reporting.
But the transition is real work. Businesses that assumed this was another deadline that would slip are now catching up under pressure. The ones that treated it as a proper project audited their benefits, configured their systems, talked to their employees, and are finding April much less stressful than they expected.
If you’re reading this and still haven’t registered with HMRC or configured your payroll software: do it this week. Not next month. The registration deadline is hard, the first RTI submission under the new rules is your proof of compliance, and HMRC’s tolerance for “we didn’t know” on mandatory obligations is, let’s say, limited.
Get the infrastructure right once, and you’ll genuinely find year-end easier from here. But you have to build it first.
If your business needs a review of its current benefit-in-kind setup, payroll configuration support, or help preparing employee communications ahead of the April transition, SKZ Accountants advises UK employers across all sectors on payroll compliance and benefits reporting. Worth a conversation before the deadline, not after it.
Contact us! For CFO Services, Payroll Bureau Services, Accountants in Croydon, Accountants in Essex, CIS Accountants, Accountants in Brentwood, Accountants in Central London, Accountants in Barking, Accountants in Canary Wharf, Accountants in Romford, Accountants in Stratford, Accountants in Ilford, Practical Accounting Training in UK, Accountants in Liverpool Street, Accountants in NewHam, and Accountants in Middlesbrough.