Every UK higher education institution files a HESA staff return once a year, and most leaders log it as compliance and move on. The real cost sits elsewhere. It shows up in the weeks your HR, finance and IT teams lose pulling the same sensitive data into spreadsheets, reconciling it by hand, and watching one validation failure trigger the next. The deadline reads July. In practice, the work starts in January.

The difficulty isn’t effort, it’s that the return is unforgiving by design. Around 60 fields, each with its own rules, drawn from data scattered across your ERP. A rigid XML hierarchy where one structural break makes HESA reject the entire file. Roughly 300 cross-validation rules that check your data against itself, so an FTE of 1.0 on a part-time contract fails every time. And nothing you store goes in as-is. Every value has to become a HESA code first, where a HESA “Contract” is what Oracle calls an “Assignment”. Then the rules move. HESA revises fields and valid values every year, and some systems can only overwrite last year’s mapping rather than version it, so teams end up rebuilding from scratch each cycle.

We built a tool around the return itself, rather than adapting something else to fit. You configure your field mapping and valid-value translations once, synced straight from HESA and editable in Excel if that suits your team. You upload your four source files (Institution, Person and Governor, Contract, Activity) and the tool maps, merges and previews the whole submission in seconds, flagging every unmapped value before it becomes a problem. You override what needs overriding, with each change logged to a timestamped audit trail, and generate compliant XML in under a minute. The following year you copy this year’s submitted version and change only what moved. The hard mapping work happens once, then gets reused.

We don’t hand over software and walk away. We have run this return ourselves, we know the edge cases and the points where institutions reliably get stuck, and we stay alongside you through preparation, validation and submission. If you want to see whether this fits your year, the simplest place to start is a short review of where you stand today and what your return actually needs. No commitment.

Download the full perspective to see the tool in detail, the four-file workflow, and how version control carries your mapping from one year to the next. Or book a short HESA readiness review with Fusion Practices: a focused look at where your return stands today and what it needs, with no commitment.