HMRC’s new Inheritance Tax pension rules: What the May 11 technical note means for pensions operations - A Business Analyst's take.
Less than 11 months out from go-live, Inheritance Tax-on-pensions is no longer a policy problem. It's a process, data, and architecture problem.
On Monday last week, HMRC quietly published the technical note that pensions operations teams have been waiting eighteen months for. It covers scope, valuations, information-sharing requirements, withholding, the new Pensions Direct Payment Scheme, and the interaction with Income Tax on death benefits. In other words, the operational manual for a regime that goes live on 6 April 2027.
If you missed it amid the Pension Schemes Act 2026 noise, here’s what’s now locked in: from 6 April 2027, most unused pension funds and pension death benefits will be brought within the value of a deceased person’s estate for Inheritance Tax. Finance Act 2026 received Royal Assent on 18 March 2026, so the primary legislation is done. The plumbing isn’t.
That matters because final guidance and supporting materials are not expected until spring 2027, just weeks before the first cases arise. Time is limited and running out for HMRC to give schemes the detailed information which they will need to implement a new system which starts in less than a year’s time.
From a business architecture standpoint, this is the most operationally invasive pensions-tax change since pension freedoms in 2015.
The policy in 90 seconds
Five anchor points:
Effective date. Deaths on or after 6 April 2027. If the member dies before that date, current rules apply even if benefits are paid afterwards.
Liability has flipped. After consultation pushback, Personal Representatives, not Pension Scheme Administrators, are liable for reporting and paying IHT on pensions from 6 April 2027. PSAs have new duties under a PR-led process.
What’s out of scope. Spouses, civil partners, and registered charities remain exempt. Death-in-service benefits, dependants’ scheme pensions, and joint life annuities purchased with the member’s lifetime annuity are excluded benefits.
The numbers. Of 213,000 estates with pension funds potentially in scope in 2027/28, 49,000 estates will be affected, 10,500 with a new IHT liability, the remainder with an increased one. The average additional bill is around £34,000.
The Exchequer take. The Government calculates additional IHT receipts of £5.46 billion across the four years from 2027/28 to 2030/31, against one-off industry costs estimated at £65 million.
Why this is a BA problem, not a tax problem
Tax changes are simple to explain. They’re hard to operationalise. The technical note layers three new operational primitives onto every in-scope scheme:
A 28-day valuation SLA on a date-of-death basis, with an estimated value mandatory if a final figure isn’t available.
A withholding notice; a brand-new payment-suspension state, capped at 50% of a beneficiary’s entitlement, with a 15-month maximum lifespan from end of month of death.
A Pensions Direct Payment Scheme ; a 35-day, tax-paid-from-scheme channel routed through the Managing Pension Schemes service.
None of these exist in current scheme architectures. All three need to land before April 2027.
Six items I’d put on every scheme’s IHT roadmap right now
1. Redesign the death-event process end-to-end. Today, schemes can largely wait until trustees exercise discretion and probate is granted. From 2027, you must respond to a Personal Representative’s information request within 28 days and acknowledge a withholding notice within 14. Crucially, identity verification must happen before probate, including for “prospective” PRs in intestate cases, evidenced through wills, death certificates, signed declarations, or solicitor correspondence. The “wait for grant” pattern breaks.
2. Build the notional pension property calculation as a discrete service. The note splits the calculation between money purchase and DB arrangements: for DC, pot value plus reasonably-expected augmentations; for DB, lump sums plus expected augmentations plus continuing scheme/annuity payments under guarantee provisions, calculated on the assumption that the maximum lump sum is paid. Excluded benefits, death-in-service, dependants’ scheme pensions, joint life annuities, certain trivial commutations, must be netted off. Most admin platforms today don’t surface this distinction as a single computable field.
3. Stand up withholding as a first-class entitlement state. This isn’t a freeze. It’s a portion-based cap: up to 50% of each beneficiary’s entitlement, calculated on a “just and reasonable” basis where there are multiple beneficiaries, with the remaining 50% payable promptly. If pre-notice payments have already exceeded the 50% threshold for one beneficiary, no further payments to that beneficiary, but the second beneficiary’s cap is calculated independently. That’s a non-trivial state machine, and the apportionment logic will need actuarial sign-off.
4. Integrate with the Managing Pension Schemes service for direct payment. Where a valid payment notice arrives, the scheme has 35 days to pay HMRC and confirm payment back to the PR and beneficiary, quoting an HMRC-issued reference number. Missing that window transfers IHT liability onto the scheme administrator jointly. This is a hard regulatory SLA, not best-efforts.
5. Solve the PR identity problem. This is the single biggest design hazard. Schemes must accept “reasonable” evidence of prospective PR status from individuals without legal authority yet, and once accepted, that evidence must hold for all subsequent stages. Get this wrong and the scheme is exposed to fraud risk; get it too strict and you breach the 28-day SLA. A defensible evidence matrix, audit trail, and exception-handling path are non-negotiable.
6. Upgrade the data exchange model. Each scheme must surface on request: valuation, split between exempt and non-exempt beneficiaries, beneficiary names, addresses, NI numbers where known, and the value attributable to each beneficiary. For schemes that store death benefit allocations as case notes rather than structured data, this is a data model upgrade, not a report.
The hidden problem: data quality
HMRC has committed £52 million to digitalise the IHT service from the 2027 to 2028 tax year onwards. The pensions-side data feeding into it is patchier than most boards realise. Membership records for deferred members, expression-of-wishes forms, beneficiary NI numbers, the same data points that pensions dashboards have been quietly exposing as weak. April 2027 will surface those weaknesses again, with statutory SLAs and joint-and-several tax liability attached.
There’s also a quietly significant tax-stack issue. The technical note’s mechanism for reducing taxable pension income by the IHT “burden” suffered (section 8.2) is elegant on paper, but it will land in pension scheme communications, member journeys, and beneficiary correspondence. That’s a comms architecture problem as much as a tax one.
What I’d do in the next 60 days
Run a structured impact assessment now, not in Q3. Third-party admin platform changes, annuity provider interfaces, and Managing Pension Schemes service integration all have lead times measured in quarters.
Build your as-is death-event journey before HMRC publishes draft information-sharing regulations this spring, so you’re ready to diff to-be when they land.
Map your scheme’s product taxonomy against the excluded-benefits list. Cash balance arrangements, augmentation powers, and guarantee periods are where misclassification will be costliest.
Engage the actuarial function on the “just and reasonable” apportionment logic early. That phrase is doing a lot of work in this legislation.
Don’t wait for spring 2027 guidance to start the member communications work. Unmarried partners, who lose the most under the new regime, deserve to know their nominations may no longer achieve what the member intended.
The IHT reform isn’t headline-grabbing in the way dashboards have been. But for any scheme actually operating in this market, it’s a bigger architectural intervention than dashboards were. Schemes that treat it as a tax change will be ready in April 2027 with paperwork. Schemes that treat it as a process and data change will be ready with systems.
The 11-month clock started from today.
If this was useful, subscribe for more on business analysis, business architecture, and the pensions sector. I publish weekly.
References
HM Revenue & Customs (2026) Technical note: Inheritance Tax on pensions, 11 May 2026. https://www.gov.uk/government/publications/inheritance-tax-on-pensions-technical-note/technical-note-inheritance-tax-on-pensions
Finance Act 2026, c. 8 — inserting s. 150A, s. 226A and s. 226B into the Inheritance Tax Act 1984.
House of Lords Economic Affairs Committee (2025) Inheritance tax measures: unused pension funds and agricultural and business property reliefs. https://publications.parliament.uk/pa/ld5901/ldselect/ldeconaf/250/25006.htm
Pensions Age (2026) ‘HMRC publishes pensions IHT update; final guidance not expected until spring 2027’. https://www.pensionsage.com/pa/HMRC-running-out-of-time-on-pensions-IHT-changes-LCP.php
Burges Salmon (2026) ‘Who will bear the burden of implementing IHT changes for pension scheme benefits?’, 5 February 2026. https://www.burges-salmon.com/articles/102lw2f/