1. How do I process new award year updates?
  2. Enable Award Year-Based File Formats for Student Eligibility

Enable Award Year-Based File Formats for Student Eligibility

Here’s the list of file formats you should enable in Oracle Student Financial Aid Cloud Service once features are delivered within the Student Eligibility new award year releases.

To enable the related file formats, go to Administration > FAS Management > DOE File Management. See How do I enable or disable file formats for award year processing?

When reviewing award year–based file names, keep in mind:

  • XX in the file name shows the award year (for example, “26” for 2025–26).

  • IN files are sent from schools to ED (for example, origination submissions).
  • OP files are sent from ED to schools as responses, acknowledgments, or error reports.

Award-Year Based File Formats for Student Eligibility

File Description Notes
IDAPXXOP Daily Electronic Application ISIRs: Processed ISIR (Institutional Student Information Record) sent to schools and agencies listed on a student’s FAFSA. These files are used by financial aid administrators to review processed FAFSA and correction information for students who listed their institution. The file contains the student's complete eligibility and application data and is used for packaging aid. It's recommended that you enable all ISIR files received by ED with the new award year. All ISIR file types will trigger the same ISIR processing within SFA regardless of why the file type was sent.
IDSAXXOP Daily ISIRs (Automatic/Secondary): ISIRs issued to schools/agencies that didn't generate the underlying transaction but are included in the student’s application (for example, when another school submitted the transaction or when ED initiates changes). Used to ensure all interested parties are informed of changes in student records and required to monitor/compare to previous ISIRs for eligibility changes. It's recommended that you enable all ISIR files received by ED with the new award year. All ISIR file types will trigger the same ISIR processing within SFA regardless of why the file type was sent.
IGSGXXOP FPS Pushed System-Generated ISIRs: Automatically distributed ISIR files created due to system-generated transactions (for example, new DHS or NSLDS match data, reprocessing). Used by schools to identify students whose eligibility or status changed after initial processing, requiring possible follow-up or updating of aid packages. Typically not initiated by school action, but by changes from a matching agency or internal federal system update. It's recommended that you enable all ISIR files received by ED with the new award year. All ISIR file types will trigger the same ISIR processing within SFA regardless of why the file type was sent.
IGSAXXOP FPS Pushed ISIRs to Other Schools in Record: Similar to IGSGXXOP, but specifically sent to schools that are listed on a transaction where a change (such as a correction made by another school, or eligibility change) might affect them. Used to notify all schools listed for that student about important changes, requiring a review of student records. It's recommended that you enable all ISIR files received by ED with the new award year. All ISIR file types will trigger the same ISIR processing within SFA regardless of why the file type was sent.
CORRXXIN Electronic Correction Data Submission: File created and sent by a school or agency to the CPS (Central Processing System), containing corrections or updated data for students’ FAFSAs. This file follows strict formatting and is used by institutions to update a student’s FAFSA info, dependency, or financial changes electronically. It triggers recalculation of aid eligibility and generates new ISIRs if accepted. Don't enable this file format until ED can support receiving batch correction files.
IGCOXXOP ISIRs Generated by Institutional Corrections: Daily message sent to schools and servicers that have submitted electronic corrections to student records. The ISIR contains the most up-to-date data after the correction and is imported by financial aid offices to update student files and repackage aid as needed. It's recommended that you enable all ISIR files received by ED with the new award year. All ISIR file types will trigger the same ISIR processing within SFA regardless of why the file type was sent.
COREXXOP Electronic Correction Error Reports: Error file created when a correction file (CORRXXIN) submitted by a school contains one or more records that fail technical or business edits (for example, missing fields, data out of range). Used by technical/administrative staff to identify what records need correction and resubmission. Each error report lists the rejected records and the related error messages. Errors from this report are available in reporting and should be included in your monitoring process. You don't need to enable this file until ED can support receiving batch correction files.
EAPRXXOP Electronic Application Error Reports: Error report file generated when an application (FAFSA) data file sent by a school is rejected by the CPS for format, data, or edit errors (for example, invalid values, required field missing). Used internally by aid offices or IT to review why student applications didn’t process, so errors can be corrected and files resubmitted for successful processing. Note that the related FAFSA Electronic Applications Record (EAPSXXIN) file that would be used to submit a FAFSA is currently not supported.
SIGAXXOP Signature Record Error Reports: Error report for electronic signature files (used to resolve rejected transactions or signature holds). Sent when a signature record fails edits or doesn't match an outstanding transaction. Used to resolve issues related to missing or invalid applicant/parent signatures needed for FAFSA processing. Note that the related Signature Record Export Record (SIGSXXIN) file used to send in required signatures with a FAFSA is currently not supported.