- News and updates
- Admissions explained
- web-link and link guides
- Your courses
- Qualifications
- UCAS projects
- Events
- Training services
- Consultation groups
- Important dates
- HESA return
- Contacts
- Status reports
Why is the transaction delivered at the end of the cycle?
The UCAS Data for HESA transaction is delivered at the end of November each year. To ensure that all applications are included in the transaction it has to be built after the close of the application cycle (end of October each year).
Following the close of cycle, the final applications are processed into the database. This can take up to five days. Once all the applications have been processed the UCAS Data for HESA table is created (which can take an additional two days). Following the creation of the table the separate institution files are generated and final acceptance testing is performed. Once the testing is complete and signed off the transaction is made available to institutions.
UCAS Data for HESA
- What data does the UCAS Data for HESA transaction provide?
- What are the derived fields?
- Where do the unknown values come from?
- Why is the transaction delivered at the end of the cycle?
- Why do some of my applicants have no qualification data?
- How does QUALENT3 work?
- Can I find the data in the UCAS Data for HESA transaction elsewhere?