SSAS HMRC Reporting Requirements: A Trustee's Complete Reference Guide
Written by Matt Lenzie
Former Banker & Corporate Finance Partner

SSAS HMRC Reporting Requirements: Everything Trustees Need to Know
Running a SSAS pension scheme involves more than just making good investment decisions. Trustees and scheme administrators have ongoing reporting obligations to HMRC that must be met accurately and on time. Failure to comply can result in financial penalties, and in severe cases can jeopardise the scheme's registered status.
This guide provides a comprehensive reference to all the key HMRC reporting requirements that apply to SSAS schemes, covering what must be reported, when, and how.
Registration and the PSTR
Before any reporting obligations begin, the SSAS must be registered with HMRC and given a Pension Scheme Tax Reference (PSTR). All subsequent reporting is linked to this reference number.
Changes to the scheme that must be notified to HMRC include:
- Change of scheme administrator
- Addition or removal of employers
- Change of scheme name
- Change of scheme's registration category
- Winding up of the scheme
Notifications are made via HMRC's Pension Schemes Online service. Timely notification is required — typically within 30 days of the change occurring.
Event Reports
SSAS schemes must file event reports with HMRC within 90 days of certain specified events occurring. These events include:
- Benefit crystallisation events (BCEs): These occur when pension benefits are drawn — including pension commencement, taking tax-free cash, or entering drawdown. The BCE must be reported along with the amount crystallised
- Transfers in and out: Where funds are transferred into or out of the SSAS from another registered scheme, this must be reported
- Unauthorised payments: If an unauthorised payment has occurred, this must be reported promptly — waiting for the annual reporting cycle is not acceptable
- Wind-up of the scheme: When a SSAS is wound up, this must be reported along with how benefits were provided
- Employer insolvency or business cessation: Where the sponsoring employer becomes insolvent, this triggers reporting obligations
In our experience, the 90-day deadline for event reports is the reporting obligation most commonly missed by trustee members who are managing their own scheme. A good scheme administrator should prompt the trustees when an event report is required, but trustees should also maintain awareness of these obligations themselves.
Matt Lenzie notes: "The 90-day event report deadline can catch trustees by surprise, particularly around benefit crystallisation events at retirement. I always encourage clients to discuss any planned benefit drawings with their administrator well in advance so that the reporting is planned rather than reactive."
Accounting for Tax (AFT) Returns
The Accounting for Tax (AFT) return is used to report and pay tax liabilities that arise within the SSAS. These are submitted quarterly, for the periods ending 5 April, 5 July, 5 October, and 5 January. Returns are due 45 days after the end of the relevant quarter.
Situations that require an AFT return include:
- Unauthorised payment charges (40%) and surcharges (15%) arising from non-authorised payments
- Scheme sanction charges (40%) arising from scheme chargeable payments
- Annual allowance charges where the scheme is paying on behalf of a member (under scheme pays arrangements)
- Lifetime allowance charges (for historic events before the LTA was abolished in April 2024)
- Short service refund lump sum charges
An AFT return must be submitted even if the tax liability is nil, where the scheme has previously submitted an AFT return. Only schemes that have never had any reportable events can avoid submitting nil returns.
The Scheme Return
HMRC issues a scheme return to each registered pension scheme annually. The scheme return requires the scheme administrator to provide information about:
- The value of scheme assets
- The number and type of members
- Contributions paid during the year
- Benefits paid during the year
- Details of any transfers
- Information about investments held
The deadline for submitting the scheme return is typically 31 January following the end of the tax year for which the return relates. Late submission attracts an automatic fixed penalty, with additional daily penalties for extended delays.
Annual Accounts and Independent Review
While HMRC does not have a specific statutory requirement for SSAS accounts to be independently audited (for small schemes), best practice — and the expectation of most scheme administrators — is that annual accounts are prepared by a qualified professional and independently reviewed.
SSAS accounts should include:
- A fund account (income and expenditure statement)
- A net assets statement (showing assets and liabilities)
- Notes explaining significant transactions and accounting policies
- Details of all investments held, with market valuations
- Details of contributions received and benefits paid
These accounts are not submitted to HMRC as a matter of course but must be available for inspection. HMRC may request accounts during a compliance review, and well-prepared accounts are the best evidence that the scheme is being managed properly.
Self-Assessment Obligations for Members
In addition to scheme-level reporting, individual SSAS members have personal reporting obligations via self-assessment:
- Pension income received must be declared on the self-assessment return
- Tax-free lump sums must be reported (even though no tax is payable)
- Annual allowance charges must be declared and paid if the scheme is not paying on the member's behalf
- Any unauthorised payment charge must be declared and paid
- Pension death benefits received must be reported where they are taxable
Record-Keeping Requirements
HMRC requires that SSAS trustees and administrators maintain adequate records to substantiate all the information reported. Key records include:
- Trust deed and scheme rules
- Member records (joining dates, contributions, benefit entitlements)
- Investment records (purchase prices, valuations, sale proceeds)
- Correspondence with HMRC
- All scheme accounts and financial records
- Independent valuations supporting connected party transactions
- Board and trustee meeting minutes recording investment decisions
Records should generally be retained for at least six years from the end of the tax year to which they relate, with some records (particularly scheme establishment documents) to be retained indefinitely.
Penalties for Reporting Failures
HMRC applies a range of penalties for SSAS reporting failures:
- Late event reports: Fixed penalty of £300, plus daily penalty of £60 per day after 90 days
- Late or inaccurate AFT returns: Fixed penalties and percentage-based penalties on unpaid tax
- Late scheme return: Fixed penalty of £250 (£500 if more than 3 months late)
- Failure to maintain adequate records: Penalty of up to £3,000
- Deliberate inaccuracies: Penalty of up to 100% of the tax involved
Key Takeaways
- SSAS schemes have multiple, ongoing HMRC reporting obligations throughout the tax year
- Event reports must be filed within 90 days of qualifying events, including benefit crystallisation and unauthorised payments
- AFT returns are due quarterly and cover all scheme-level tax liabilities
- The annual scheme return provides HMRC with an overview of scheme membership, assets, and activities
- Annual accounts should be professionally prepared and maintained for HMRC inspection
- Penalties for non-compliance range from fixed amounts to percentage-based charges on unpaid tax
Ensure Your SSAS Meets All Reporting Obligations
Meeting HMRC's reporting requirements is one of the core responsibilities of SSAS trusteeship. Working with a professional scheme administrator is the most reliable way to ensure all obligations are met on time and accurately.
Contact our team to discuss SSAS compliance and reporting support, or explore our guides on SSAS HMRC compliance, unauthorised payments, and SSAS tax planning strategies.
About the Author
Matt Lenzie
Former Banker & Corporate Finance Partner
Matt Lenzie is a former banker and corporate finance partner with extensive experience in pension-backed property transactions. He founded SSAS Property Finance to help company directors and trustees navigate the complexities of commercial property acquisition through Small Self-Administered Schemes.


