Every year, Purpose-Built Student Accommodation operators in Ireland are required to submit detailed occupancy and student demographic data to the Higher Education Authority. The submission covers the academic year just completed — and the data it asks for is specific enough that most operators cannot produce it without a significant manual effort.
For operators running their student accommodation on spreadsheets or general property management tools, HEA reporting season typically means two to three weeks of data gathering, reconciliation, and manual calculation. For operators with a purpose-built student accommodation system, it means clicking generate.
This guide covers what the HEA requires, what data you need to have captured during the year, and how to make the reporting process a by-product of your normal operations rather than a separate annual scramble.
Who is required to report
The HEA reporting obligation applies to registered PBSA operators — both those operating under licence and those with planning permissions granted under the 2017 Student Accommodation Guidelines. If your development was built as student accommodation and is marketed as such, you are in scope.
The obligation covers both academic-year tenancies and short-stay summer lets, with different data requirements for each type.
What the HEA submission requires
The annual submission is structured around the following data categories. Each requires accurate, verifiable figures — not estimates.
| Data Category | What You Need | Verification Source |
|---|---|---|
| Total Bed Capacity | Number of beds available by room type | Room register |
| Occupancy Rate | Beds occupied per week, averaged over the academic year | Tenancy records |
| Student Status | Split: full-time / part-time / postgraduate | Application data |
| Institution Affiliation | Which HEI each student attends | Application / enrolment proof |
| Student Allocation % | Proportion of beds ring-fenced for HEA-linked institutions | Allocation agreements |
| Weekly Rent | Average weekly rent charged, by room type | Tenancy records |
| HEA Rent Cap Compliance | Confirmation rent is at or below the applicable HEA cap | Finance records |
| Nationality / Domicile | Irish / EU / non-EU student split | Application data |
The HEA rent cap — and why it matters for reporting
One of the most consequential parts of the HEA return is the rent cap compliance section. PBSA operators who receive HEA designation or who have planning conditions tied to affordable student rents are required to charge at or below the HEA-prescribed cap for the relevant academic year.
In 2025–2026, the caps range from approximately €185 per week for standard en-suite rooms to €210 per week for studios, depending on location and development type. Operators must be able to show that every bed in scope was rented at or below the applicable cap — not on average, but for each individual tenancy.
2025–2026 HEA Rent Cap Reference
Caps are indicative based on 2025–2026 guidance. Confirm applicable cap with HEA for your development.
The reporting timeline
The HEA annual return window typically opens in September and closes in late October, covering the academic year just ended (September to August). Operators who miss the deadline or submit incomplete data risk losing their HEA designation status, which has downstream consequences for eligibility for planning approvals on future developments.
The practical timeline for operators who want to avoid a last-minute scramble:
- Throughout the academic year: Capture student institution, study status, and nationality at the application stage. Do not wait until September to try to reconstruct this from memory or incomplete records.
- End of academic year (August): Lock down occupancy records and final rent figures for all tenancies.
- September: Run the HEA report from your system. Verify the figures against source records. Submit.
What goes wrong without a purpose-built system
The data the HEA requires is not difficult to collect — if you collect it at the right time. The problem is that general-purpose property management tools are not designed to capture student-specific fields like institution affiliation, study type, or HEA allocation status. Operators end up storing this data in separate spreadsheets, which then need to be reconciled with the tenancy system at year end.
The reconciliation process is where the problems emerge. Students who left mid-year. Rooms that changed occupants. Rents that were reviewed in February. Each exception requires manual investigation. In a 200-bed development, there are dozens of exceptions.
A purpose-built student accommodation system captures HEA-required fields at application stage, tracks all changes throughout the year, and generates the annual return directly from the tenancy data. The report is an output of normal operations, not a separate exercise.