SSAS Connected Party HMRC Rules | Complete 2025 Guide

SSAS Connected Party HMRC Rules: A Comprehensive Overview

HMRC's rules for SSAS connected party transactions are set out primarily in the Finance Act 2004 and the associated Registered Pension Schemes regulations. Understanding these rules in detail is essential for any SSAS trustee or sponsoring employer considering a connected party transaction. This guide provides a comprehensive overview of the legislation, the penalties for non-compliance, and the practical steps to stay on the right side of HMRC.

The Legislative Framework

The principal legislation governing SSAS connected party transactions includes:

Finance Act 2004, Part 4: The primary legislation establishing the registered pension scheme framework, including the investment restrictions and the unauthorised payments regime
The Registered Pension Schemes (Prescribed Manner of Determining Amount of Annuity) Regulations 2006: Governing certain scheme calculations
HMRC Pension Tax Manual: HMRC's operational guidance on the application of the legislation, including detailed guidance on connected party transactions (available at HMRC's website)

The key concept within this framework is the distinction between "authorised" and "unauthorised" payments from a registered pension scheme.

Authorised vs Unauthorised Payments

Authorised Payments

An authorised payment is one that is specifically permitted by the Finance Act 2004. The main categories of authorised payments relevant to SSAS include:

Pension income payments to members in drawdown
Lump sum payments within defined limits (tax-free cash, serious ill health lump sums, etc.)
Payments to purchase scheme benefits
Authorised loanbacks to the sponsoring employer (subject to conditions)

Unauthorised Payments

Any payment from a registered pension scheme that is not an authorised payment is an unauthorised payment. In the context of connected party transactions, unauthorised payments arise when the SSAS effectively provides a benefit to members or connected parties that has not been taxed appropriately. Examples include:

Purchasing property from a connected party at above-market price
Leasing property to a connected party at below-market rent
Providing loans to individual members (as opposed to the sponsoring employer)
Investing in assets that provide a direct personal benefit to members

The Unauthorised Payment Charge

When HMRC determines that an unauthorised payment has been made from a SSAS, the tax consequences are severe:

Member Charge

The member (or the individual who received the benefit) is subject to an unauthorised payment charge of 40% on the amount of the unauthorised payment. This is in addition to any other income tax that may be payable.

Unauthorised Payment Surcharge

Where the total unauthorised payments made to or in respect of a member during a twelve-month period exceed 25% of the fund value, an additional surcharge of 15% applies. This can bring the total charge to 55% of the payment value.

Scheme Sanction Charge

In addition to the member charge, the scheme itself faces a scheme sanction charge of between 15% and 40% of the unauthorised payment, depending on whether the scheme can recover the member charge from the member.

"The combined impact of the unauthorised payment charge, surcharge, and scheme sanction charge can exceed 70% of the payment value in the most serious cases. This is not a theoretical risk — HMRC does investigate and does apply these charges." — Matt Lenzie, Former Banker & Corporate Finance Partner

Reporting Requirements

SSAS administrators are required to report to HMRC annually via the Event Report. Unauthorised payments must be reported to HMRC within 3 months of the end of the tax quarter in which they occurred. Failure to report known unauthorised payments is itself a compliance failure that can result in additional penalties.

HMRC also requires SSAS administrators to maintain scheme records and to provide HMRC with information on request. The scheme must be able to demonstrate, through contemporaneous records, that all transactions were arm's length and compliant.

Specific Rules for Property Transactions

HMRC provides specific guidance on connected party property transactions in the Pension Tax Manual. Key rules include:

The Market Value Rule

When a SSAS acquires an asset from a connected party, it must pay no more than market value. When it disposes of an asset to a connected party, it must receive no less than market value. HMRC uses the statutory definition of market value from the Taxation of Chargeable Gains Act 1992.

The Market Rent Rule

When a SSAS leases property to a connected party, the rent must reflect market rent at all times. As discussed in our guide to SSAS market rent requirements, this must be supported by independent valuation evidence and maintained through proper rent review provisions.

The Taxable Property Rules

SSAS schemes are subject to additional tax charges if they invest in "taxable property" — which includes residential property and certain tangible moveable property (e.g. artwork, classic cars, fine wines). Residential property held by a SSAS, even indirectly through a company, attracts a special tax charge. This is entirely separate from the unauthorised payment regime but equally severe.

HMRC's Approach to Investigation

HMRC monitors registered pension schemes through a combination of annual returns, event reports, and targeted investigations. Schemes that consistently file accurate returns and have good administrative records are less likely to be investigated than those with irregularities or gaps in their reporting.

HMRC can and does conduct compliance reviews of SSAS schemes, particularly where a scheme has large connected party transactions. These reviews typically involve requesting scheme records, valuation evidence, lease documentation, and trustee minutes. The scheme administrator and professional trustee will typically manage the correspondence, but individual member-trustees may also be contacted.

Correcting Historic Non-Compliance

If you discover that a past connected party transaction was not fully compliant — perhaps the rent was below market rate for a period, or a rent review was missed — it is important to take corrective action promptly. HMRC has a formal process for correcting historic non-compliance, which may mitigate penalties if addressed proactively rather than waiting to be investigated.

Take specialist advice before approaching HMRC — the way in which historic non-compliance is disclosed can affect the level of charges and penalties that HMRC applies.

Staying Compliant: A Summary

All connected party transactions must be at arm's length, supported by independent valuations
Leases must be at market rent, with formal rent review provisions implemented at the correct dates
Unauthorised payments must be reported to HMRC within the required timeframe
Comprehensive scheme records must be maintained throughout the scheme's life
Historic non-compliance should be addressed proactively with specialist advice

Key Takeaways

HMRC's unauthorised payment regime can result in charges exceeding 70% of the payment value
The Finance Act 2004 and HMRC Pension Tax Manual set out the detailed rules
Both the member and the scheme are subject to tax charges for unauthorised payments
HMRC can investigate schemes at any time and requires comprehensive records
Proactive correction of historic non-compliance is preferable to waiting for investigation

Get Expert SSAS Compliance Advice

Our team works with SSAS schemes to ensure connected party transactions are fully compliant with HMRC's requirements. We also assist with historic compliance reviews where previous arrangements may not have met the required standards.

SSAS Connected Party HMRC Rules: The Definitive Guide