UK Benefits in Kind and the 2027 Mandatory Payrolling Shift

The UK benefits in kind landscape is shifting in a way that raises the stakes for payroll software companies. HMRC has confirmed a phased rollout for mandatory payrolling, moving reporting to real-time payroll RTI submissions. Phase 1 takes effect on 6 April 2027 for core benefits (company cars, vans, fuel, and private medical/dental insurance). Phase 2 follows on 6 April 2028 for most remaining benefits, though beneficial loans and accommodation remain excluded for now. For payroll software companies, this is not a configuration update. It's a structural change to how benefits must be integrated with the payroll calculation engine. Under this emerging mandatory payrolling model, benefits in kind will generally affect PAYE, National Insurance, OpRA valuations, and RTI reporting in every pay run.

Common Benefits and Their Valuation Mechanics

Company cars: The taxable benefit is calculated using the vehicle’s original list price multiplied by an HMRC percentage based on CO2 emissions and fuel type, updated annually. Fully electric vehicles are currently taxed at 4%, increasing gradually each year, while petrol and diesel cars attract higher rates based on emissions. Fuel benefit is calculated separately using a fixed HMRC multiplier (£29,200 for 2026/2027), not the car’s value.

To calculate this correctly, the system must store and update per-vehicle variables including CO2 band, fuel type, list price, availability dates, and whether private fuel benefit applies. Mid-year vehicle changes require precise proration based on actual availability dates. A system that stores only a flat annual BIK value cannot accurately handle proration, mid-year vehicle changes, or maintain the precise car data fields required for real-time FPS submissions to HMRC.

Beneficial loans occur when an employer lends money to an employee at below HMRC's official rate of interest (currently 3.75% for 2026/7). The taxable benefit is generally calculated as the difference between interest paid and interest at HMRC’s official rate, using either HMRC’s average balance method (default) or the precise daily balance method (opted in by employee or required by HMRC). There's a de minimis exemption: if all outstanding loans from the employer to the employee total £10,000 or less throughout the tax year, no taxable benefit arises, but the threshold is per employee across all loans combined.

Medical benefits: Employer-paid private medical insurance and most employer-funded medical treatment are taxable unless a specific exemption applies. Overseas medical treatment for employees working abroad can be exempt; domestic treatment provided under a group scheme is taxable at the cost to the employer.

Living accommodation carries its own distinct rules. Where the property's annual value (broadly, its rateable value or rental equivalent) is used as the basic charge, an additional benefit arises for properties that cost the employer more than £75,000, calculated as the excess over £75,000 multiplied by HMRC's official interest rate. Job-related accommodation may be fully exempt, but the exemption conditions are specific — the accommodation must be necessary for the duties of the employment, customary and better-enabling performance, or security reasons — and must be assessed per employee.

The NIC class problem

National Insurance treatment is where many BIK implementations break in non-obvious ways. The class of NIC that applies depends on the nature of the benefit and how it's provided. Getting it wrong affects both the employer's liability and the correct fields in RTI submissions.

Most benefits in kind attract Class 1A NIC, paid by the employer at 15% of the taxable value. This applies to company cars, fuel benefit, private medical insurance, beneficial loans, and most other non-cash benefits. Class 1A is reported annually on the P11D(b) and paid by 22 July following the tax year end or, under mandatory payrolling from April 2027, collected monthly through payroll.

Class 1 NIC applies instead where a benefit is readily convertible to cash — for example, non-cash vouchers that can be exchanged for cash or traded on a market, or certain share-related awards. Class 1 NIC is calculated on the same basis as earnings, with both employee and employer contributions, and must run through the payroll calculation rather than being handled at year end.

Class 1B NIC applies to benefits and expenses covered under a PAYE Settlement Agreement, where the employer settles the tax on behalf of employees by arrangement with HMRC.

A system that applies Class 1A to all benefits regardless of type, or fails to route readily-convertible-asset benefits through the Class 1 NIC calculation, will produce incorrect NIC figures and incorrect P11D(b) liabilities. The determination needs to be made per benefit type, with the result feeding into the appropriate NIC calculation path.

OpRA: the "higher of" rule and why it matters for salary sacrifice schemes

Optional Remuneration Arrangements (salary sacrifice schemes where an employee exchanges cash salary for a benefit) have been subject to special rules since April 2017. Under the pre-2017 model, salary sacrifice for benefits could produce significant income tax and NIC savings by reducing both taxable pay and earnings subject to NIC. The 2017 changes largely closed that route by introducing the "higher of" rule.

Under OpRA, the taxable benefit value is the higher of the benefit's normal cash equivalent value and the amount of cash salary the employee has forfeited. If an employee sacrifices £600 per month for private medical insurance that has a normal taxable value of £400 per month, the taxable benefit is £600 — the foregone cash — not £400. This means salary sacrifice for most benefits produces no income tax saving over and above what the employee would pay if the benefit were provided outside sacrifice.

The OpRA rules don't apply to certain exempt benefits: pension contributions, employer-provided childcare, cycle-to-work schemes, and ultra-low emission vehicles (defined as vehicles with CO2 emissions below a threshold, currently cars with emissions at or below 75g/km). For these benefits, the normal cash equivalent value applies even where salary has been sacrificed, which is why electric vehicle salary sacrifice schemes remain commercially attractive in a way that medical insurance sacrifice no longer is.

Following the expiration of all legacy pre-2017 grandfathering provisions, all non-exempt salary sacrifice benefit schemes must now be evaluated under the standard OpRA 'higher of' test.

A system without per-arrangement effective dating, or one that applies the "higher of" rule universally without the ULEV and other exemptions, will produce incorrect taxable benefit values for any employer running salary sacrifice.

The mandatory payrolling transition and what it means for platform architecture

The shift from P11D-based annual reporting to real-time payrolled benefits is the most significant structural change to UK BIK compliance since the introduction of RTI. Understanding what it actually requires from a payroll engine matters.

Under the current P11D model, BIK values don't enter most payroll calculations at all. Income tax is collected through an adjustment to the employee's PAYE tax code issued by HMRC; the payroll engine applies the code and doesn't need to know the underlying benefit. Class 1A NIC is an annual lump sum payment by the employer.

Under mandatory payrolling from April 2027, this changes entirely. The annual cash equivalent of each benefit is divided across the remaining pay periods in the tax year and added to the employee's taxable pay for PAYE purposes each period. If the benefit value changes mid-year (the employee gets a new car, the loan balance changes), the revised annual cash equivalent is prorated across the remaining periods. This requires the payroll engine to hold the underlying benefit values, know how many pay periods remain in the tax year for each employee, and recalculate correctly on any change.

Class 1A NIC also moves from an annual lump sum to real-time calculation and collection through payroll. The P11D(b) is retained for record-keeping in the mandatory model, but Class 1A is collected in real time through the payroll.

Two categories of benefit are excluded from mandatory payrolling: employer-provided loans and living accommodation. These can be voluntarily payrolled with HMRC registration, but P11D reporting remains available for them after the mandate. Everything else — company cars, medical insurance, fuel benefit, mobile phones outside the exemption, and all other taxable benefits — must flow through the payroll from April 2027 or 2028 depending on the Phase.

For payroll software companies, the architectural implication is that benefit values can no longer live only in a separate HR or benefits system and flow to payroll annually. They need to be available to the payroll calculation engine every pay period, with the proration logic and mid-year adjustment handling built into the calculation pipeline. Platforms that have built BIK as a year-end reporting module will need to rearchitect that integration before the mandate takes effect.

What Intermezzo handles at the API layer

Intermezzo's BIK module is built as part of the core payroll calculation engine, not as a separate year-end reporting function. For payroll software companies building on our API, this means benefit valuation, NIC class determination, OpRA calculations, and payrolled benefit distribution are all handled within the same pipeline run that calculates PAYE and NI.

Benefit type catalogue covers all HMRC-recognised benefit types from CWG5, with the correct tax treatment, NIC class determination, and P11D section mapping for each. Company car calculations use CO2-based percentage tables with annual updates applied in configuration, availability period proration, and fuel benefit calculations as a separate component. Beneficial loans apply the official interest rate to average loan balances with the £10,000 de minimis check across all loans per employee. Living accommodation handles both the basic annual value calculation and the additional charge for properties exceeding £75,000, with job-related accommodation exemption testing.

OpRA support is fully implemented for both Type A (salary sacrifice) and Type B (cash alternative) arrangements. The "higher of" comparison is automated, with correct identification of exempt benefits (pension contributions, childcare, cycle-to-work, and ULEVs) that fall outside the OpRA rules. 

Payrolling of benefits is supported for both voluntary and mandatory models. For payrolled benefits, the annual cash equivalent is distributed across remaining pay periods, added to taxable pay in the correct position in the calculation pipeline (before PAYE runs, not as a post-tax adjustment), and excluded from P11D generation. Mid-year benefit changes trigger recalculation of the per-period amount across the remaining periods in the tax year. Benefits not registered for payrolling flow to P11D generation at year end.

Class 1A and Class 1 routing is determined per benefit type. Readily-convertible-asset benefits route through the Class 1 NIC calculation. Standard benefits in kind route through Class 1A. The correct fields are populated in both the payroll register and the RTI FPS output.

P11D and P11D(b) generation is automated, with correct section mapping for each benefit type, exclusion of payrolled benefits from P11D output, Class 1A NIC calculation for P11D(b), and electronic submission capability.

Compliance updates are held in configuration rather than code so CO2 emission band percentages, the official interest rate for beneficial loans, the fuel benefit multiplier, and other annually-updated figures update without a deployment.

The window before the mandate closes

2026/27 is the final tax year before mandatory payrolling takes effect in April 2027, and HMRC has indicated a "soft touch" approach in the first mandatory year. That window is narrower than it appears — HMRC has published technical notes, but detailed implementation guidance for software developers continues to evolve ahead of the April 2027 deadline, leaving limited time for development, testing, and rollout.

For payroll software companies, the practical question is whether your current BIK architecture can support real-time payrolling natively or whether it requires significant rearchitecting to meet the mandate.

Powering BIK compliance through Intermezzo's API means that the architecture is already in place, and the mandatory payrolling transition sits on our roadmap, not yours. To discuss UK BIK coverage or explore the API, book a demo with us below.