Update Aid Eligibility Configuration

When the workbooks are updated for the new award year, update your SFA configuration. For more information, see How do I manage configuration workbooks?

REGULATORY_DEADLINES

Review and update:

Award_Year
FAFSA_Start_Date
FAFSA_End_Date
ISIR_Correction_Start_Date
ISIR_Correction_End_Date
ISIR_Verification_Start_Date
ISIR_Verification_End_Date
Days_from_Student_Enrollment
ISIR_Award_Year_Start_Date
ISIR_Award_Year_End_Date

Each year a new row will be added for the award year and the dates will be prepopulated with default logic based on the Department of Education's (ED) published dates.

Award year will be prepopulated for the new award year.
FAFSA Start Date will be prepopulated based on the date ED opens FAFSAs for students (that is, 10/1/YY) and is used when determining when FAFSA notifications will be created on the Student Self-Service portal.
FAFSA End Date Date will be prepopulated with the date ED closes FAFSAs (ie. 06/30/YY+1). Open pending FAFSA notifications will be closed on this date.
ISIR_Award_Year_Start_Date will be prepopulated based on the date ED opens FAFSAs for students (that is, 10/1/YY) and controls when ISIR processing will begin in SFA (dependent on the file format and SAIG integration being enabled).
ISIR_Award_Year_End_Date will be prepopulated with the date ED requires the FAFSA/ISIR to be valid (example: 9/20/YY+1) and will update all pending ISIRs to invalid and close associated document requests and tasks.
ISIR_Correction_Start_Date will be prepopulatedwith the date ED begins processing ISIR corrections (that is, 10/1/YY) and controls when corrections will be generated in SFA (these will not be sent until the file format and SAIG integration is enabled).
ISIR_Correction_End_Date will be prepopulated with the date ED will no longer accept ISIR corrections (that is, 9/13/YY+1) and controls when corrections will no longer be generated in SFA.
ISIR_Verification_Start_Date will be prepopulated with the date ED opens FAFSAs for students (that is, 10/1/YY) and controls when verification worksheet and documents are requested.
ISIR_Verification_End_Date will be prepopulated with the date ED requires the FAFSA/ISIR to be Valid (that is, 9/20/YY+1) and will close associated verification document requests and verification tasks.
Days_from_Student_Enrollment will be prepopulated to 120 and controls the number of days after the student's enrollment that the ISIR Verification Process must be completed by (dependent on Valid_ISIR_Deadline_for_Non_Withdrawn_Students and R2T4_Deadline in SCHOOL.csv).

If you're updating these dates, ensure that the FAFSA Start Date, ISIR_Award_Year_Start_Date, ISIR_Correction_Start_Date, and ISIR_Verification_Start_Date dates match.

For more information:

See Federal Register's award year deadline dates for an example of what’s published each year by the Department of Education. These dates are used to set prepopulated data. Use the configuration workbook to set the dates and not the Regulatory Management page.
Look up the Regulatory Deadlines workbook in Oracle Help Center.

SCHOOL

Review and update: ISIR_Matching_Criteria_Combination

This doesn't usually change year to year unless the Department of Education updates or adds ISIR fields that can be used to match and the ISIR to a student (that is, when FAFSA_UUID, PERSON_UUID, and MIDDLE_NAME were added with 24/25).

Baseline configuration should be used as a possible guide as institutional specific policies should be configured.

For more information, look up the School Guide workbook in Oracle Help Center.

ISIR_MGMT

Review and update:

Use_Subsequent_ISIR
ISIR_Used_in_Packaging
Aid_Year

Baseline configuration should be used as a possible guide as institutional specific policies can be configured.

Within baseline configuration, a new row will be created per award year. Generally you'll copy the Material Changes Groovy script and the ISIR Used in Packaging script from the prior award year unless there are new ISIR fields that you want to use in this determination.

For more information, look up the ISIR Management workbook in Oracle Help Center.

ISIR_C_CODES

Review and update: All columns per Comment Code and award year

Each year a new row will be added for each comment code included in the award year and will be prepopulated with the comment code number based on the Department of Education's specifications.

Note that the Auto_Code_Clearing_Logic that’s included in the prepopulated data all point to a Groovy script that returns true. However, this script is only used by SFA if you update it to return false and to define the student follow up indicator. If you update the comment code clearing within Auto_Code_Clearing_Logic to return true and the hardcoded value is set to return false, while the configuration will load, SFP will continue to use the hardcoded values based on the Department of Education specifications.

You should review baseline configuration to see what updates were made to the prepopulated data within Auto_Code_Clearing_Logic (including student follow up indicator), Documents_Required, Additional_Notification_Message, and Future_Auto_Clear columns for each code. You should also review your logic from prior years to see if you want to use that same logic or update to match baseline configuration.

For more information, look up the ISIR C Codes workbook in Oracle Help Center.

ISIR_C_CODES_TO_FIELDS

Review and update: All columns per Comment Code and award year

Note:

You shouldn't update this configuration, but you can review baseline configuration if any discrepancies are found.

Each year a new row will be added for each comment code included in the award year and will be prepopulated with the code and ISIR field enum used by SFA based on the Department of Education's specifications. These ISIR field enum values are also listed within the Configuration Scripting API IsirField method.

For more information, look up the ISIR C Codes to Fields workbook in Oracle Help Center.

ISIR_VERIFICATION_CODES

Review and update: All columns per Verification Code and award year

There's no data that will be prepopulated, but you should copy what’s included in baseline configuration which will be based on the Department of Education's specifications.

Verification_Status_Code and Effective_Date should remain blank for Verified for all groups, unless verification has been waived for any of the verification groups.

For more information:

Look up the ISIR Verification Codes workbook in Oracle Help Center.
See What are the 2025-2026 ISIR document request rules and code clearing logic for Verification?

ISIR_REJECT_CODES

Review and update: All columns per Reject Code and award year

Each year a new row will be added for each reject code included in the award year and will be prepopulated with the reject code number based on the Department of Education's specifications.

Note that the Auto_Code_Clearing_Logic that's included in the prepopulated data all point to a Groovy script that returns true. However, SFP uses this script only if you update it to return false and to define the student follow up indicator. If you update the comment code clearing within Auto_Code_Clearing_Logic to return true and the hardcoded value is set to return false, while the configuration will load, SFA will continue to use the hardcoded values based on the Department of Education's specifications.

You should review baseline configuration to see what updates were made to the prepopulated data within Auto_Code_Clearing_Logic (including student follow up indicator), Documents_Required, and Additional_Notification_Message columns for each code. You should also review your logic from prior years to see if you want to use that same logic or update to match baseline configuration.

For more information, look up the ISIR Reject Codes workbook in Oracle Help Center.

ISIR_REJECT_TO_C_CODES

Review and update: All columns per Reject Code per award year that are associated with a Comment Code

There's no data that will be prepopulated, but you should copy what’s included in baseline configuration which will be based on the Department of Education's specifications.

For more information, look up the ISIR Reject to C-Codes workbook in Oracle Help Center.

ISIR_REJECT_CODES_TO_FIELDS

Review and update: All columns per ISIR Review and update per award year that are associated with a Reject Code

Note:

You shouldn’t update this configuration, but you can review baseline configuration if any discrepancies are found.

Each year a new row will be added for each reject code included in the award year and will be prepopulated with the code and associated ISIR field enum used by SFA based on the Department of Education's specifications. These ISIR field enum values are also listed within the Configuration Scripting API IsirField method.

For more information, look up the ISIR Reject Codes to Fields workbook in Oracle Help Center.

ISIR_DISCREP

Review and update: All columns per ISIR Review and update per award year that require discrepancy evaluation.

There’s no data that will be prepopulated for current award years, but you should copy what’s included in baseline configuration which will be based on the Department of Education's specifications.

Note that ISIR_Field should use the ISIR_field enum defined by SFA based on the Department of Education's specifications. These ISIR field enum values are listed within the Configuration Scripting API IsirField method.

For more information, look up this information in Oracle Help Center:

ISIR Discrepancy workbook
2025-2026 configured ISIR discrepancy rules

ISIR_HIGHLIGHT

Review and update: All columns per ISIR Review and update associated with the Highlight and award year

Each year a new row will be added for each ISIR field associated with a highlight included in the award year and will be prepopulated with the ISIR field enum used by SFA, resolution and flag index based on the Department of Education's specifications.

Note that the Auto_Code_Clearing_Logic that’s included in the prepopulated data all point to a Groovy script that returns true. However, SFA uses this script only if you update it to return false and to define the student follow up indicator. If you update the comment code clearing within Auto_Code_Clearing_Logic to return true and the hardcoded value is set to return false, while the configuration will load, SFA will continue to use the hardcoded values based on the Department of Education's specifications.

You should review baseline configuration to see what updates were made to the prepopulated data within Auto_Code_Clearing_Logic (including student follow up indicator), Documents_Required, Additional_Notification_Message columns for each code. You shouldn't update the ISIR_Field_Name, Resolution, or Flag_Index. You should also review your logic from prior years to see if you want to use that same logic or update to match baseline configuration.

For more information, look up the ISIR Highlights workbook in Oracle Help Center.

ISIR_ASSUMPT

Review and update: All columns per ISIR Review and update associated with the Assumption and award year

ISIR Assumption are only applicable to the 2023-2024 and prior award years. As such, there will be data prepopulated for older award years only.

If ISIR assumptions are included for the new award year, a new row will be added with data prepopulated to include default logic based on the Department of Education's published specifications.

For more information, look up the ISIR Assumptions workbook in Oracle Help Center.

PJ

Review and update: All columns per Professional Judgement Type and award year

There’s no data that will be prepopulated, but you should review baseline configuration which will be based on the Department of Education's specifications. Additional PJ types should be added based on your institutional policy.

For more information, look up the Professional Judgment workbook in Oracle Help Center.

DOCUMENTS

Review and update: All columns per Document and award year (if award year specific)

There’s no data that will be prepopulated, but you should review baseline configuration which will be based on the Department of Education's specifications.

Documents should be added based on your institutional policy and those leveraged in your ISIR configuration. Ensure you have added a new row for any award year documents that are still pertinent for the new award year.

For more information, look up this information in Oracle Help Center:

Documents workbook
What’s the 2025-2026 baseline configuration for Student Financial Aid Documents?

DOCMETADATA

Review and update: All columns per Document Metadata attribute and award year (if award year specific)

There’s no data that will be prepopulated, but you should review baseline configuration which will be based on the documents and required data leveraged within ISIR configuration.

Document metadata should be added based on your institutional policy and those leveraged in your ISIR configuration. Ensure you have added a new row for any award year document metadata that are still pertinent for the new award year.

For more information, look up this information in Oracle Help Center:

Doc Metadata workbook
What's the 2025-2026 baseline configuration for Student Financial Aid Doc Metadata?