Issue
When creating a new funding estimate for a student with a future start date (typically September or later), the system populates an award year that does not match the student's enrollment period. The most common symptom is a September 2026 start date generating a July award year instead of the expected 2026–2027 award year.
Why This Happens
The award year on a funding estimate is derived from the ISIR currently active on the student's file and the enrollment start date entered in the FE. If the ISIR on file is tied to a different award year than the one expected for the upcoming enrollment, the system will populate accordingly. This can also occur when a student's program start date falls near an award year boundary and the system defaults to the prior year's ISIR.
Steps to Resolve
- Verify which ISIR is currently active on the student's file in Campus Ivy. Confirm that the ISIR award year matches the intended enrollment period.
- If the wrong ISIR is active, check whether the correct award year ISIR has been received and processed. If not, the school's FA office may need to re-pull the student's ISIR for the correct award year via StudentAid.gov.
- If the correct ISIR is on file but the FE still populates the wrong award year, do not manually edit the FE. Submit a support ticket to CI Customer Care including:
- Student name and ID
- Expected award year
- Enrollment start date
- The FE number that was created incorrectly (if applicable)
- A screenshot showing the award year mismatch
- The Portico support team will correct the award year association on the FE or void the incorrect FE and assist with creating a replacement.
Important Notes
- Do not submit the incorrect FE to a batch before the award year is corrected. Disbursing against the wrong award year can create COD reporting errors that are difficult to unwind.
- If multiple students at the same school have this issue for the same cohort start date, include all affected student IDs in a single ticket so the team can investigate whether there is a school-level ISIR or configuration issue.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article