Non-Federal Fund Management
Automated packaging of Non-Federal funds is managed using system configuration.
Overview
Eligibility for Non-Federal Funds and Student Resources is based on school configuration. Once eligibility is determined, the application calculates the award amount to be disbursed.
Federal Title IV Grant Funds and Federal Title IV Loan Funds can also be configured and managed.
Campus Funds: What the Application Does Automatically
The application automatically does the following things for Campus Funds.
Non-Federal Funds
The following sections discuss what the application does automatically for Non-Federal funds.
Provides a Non-Federal Funds Workflow
The application provides a workflow to help the user in making the final determination whether a student is eligible for a state grant and the amount the student is eligible to receive.
Determines Non-Federal Funds periods
The application displays the Non-Federal Funds periods and more detailed information in the Non-Federal Funds workflow based on the period start and end dates to determine how much to award the student during the period.
A list of all periods is displayed and the application automatically determines the period start and end dates (based on configuration) in the fund configuration engine. The maximum number of consecutive days the student is on a break within the Non-Federal Funds period start and end dates, excluding institutional breaks and exemptions made by the institution because of inclement weather or an administrative error are also displayed.
Awards or Estimates an amount per period
The application automatically calculates the student's Non-Federal Fund period award amount (if configured) or allows a user to manually set the award amount so that the packaging engine can package the Non-Federal Fund. The application allows the user to manually modify the Non-Federal Fund period award amount and updates the status to Estimated or Awarded.
Adds Non-Federal Funds to the academic year
Once a user determines the student is eligible for the fund, the application adds the fund to the appropriate academic year within the student's package.
The application determines which Borrower-Based Academic Year (BBAY) to package the award is based on the Non-Federal Fund period start date. If the user is changing a Non-Federal Fund, the application verifies the fund is added to the appropriate academic year again. The application sets the maximum projected award amount for each academic year being Estimated or Awarded by completing a summation of all Non-Federal Fund period award amounts within the academic year.
If the fund has an associated configured fund allocation, the application makes sure there are enough funds before adding the award to the student's package.
The application disburses the Non-Federal Fund as one disbursement equal to the maximum Non-Federal Fund projected award amount and sets or updates the disbursement dates for each Non-Federal Fund period being awarded. If the fund has already been disbursed, the application doesn't update the disbursement dates.
The Application Creates a Re-Evaluate NFF Fund Task
The application creates a Re-Evaluate NFF Fund task at various points in the financial aid process that requires a user to review the student's award. A separate alert is created for each Non-Federal Fund that has been reduced by the packaging engine due to an over award situation and when the fund amount accepted doesn't equal the maximum projected award up to packaging limit.
The Application Creates a Process an NFF Document task
When a Non-Federal Fund document with a configured document code is received for a student that requires review for Non-Federal Fund to be packaged, the application creates a Process an NFF Document task and requires a user to review the document. When the document/document code is received it's required to complete the Financial Aid Documentation Collection process. Once it has completed the document collection process, the application creates a new Process an NFF Document task for each configured Non-Federal Fund document received for the student.
Student Resources
The following sections discuss what the application does automatically for Student Resources.
Determines which academic year to apply Student Resources
The application determines how to associate a fund from the student resource tag in the Student Academic and Financial Information (SAFI) message by the academic year associated with the course the student resource is tied to. If the student resource fund isn't tied to a course, the application uses the academic year found in the ledger posting date.
If the application is unable to associate a student resource fund to the student's academic year or the correct fund configuration isn't in place in the fund configuration engine, the application use the exception handling process.
Sets the fund amount and fund status
The application sets the actual fund amount and fund status after the fund is associated with an academic year. The actual fund amount is equal to the student resource amount and the fund status is updated to Awarded. If a SAFI message is received for a student and it contains more than one student resource that shares the same fund code, these student resources are listed as separate entries in the student's package.
Triggers a repackage if Student Resources affect the package
The application determines whether the addition of a student resource fund (or updated information) affects the student's current package for the associated academic year and automatically repackages the student with the updated information upon receiving a new student resource.
Configurable Attributes
Configure Fund Attributes
The institution can configure certain attributes in order for funds to be awarded properly.
Configure Student Resource Funds
The application can account for funding that has been provided to the student outside of the application through the student resource tag within the SAFI Message. to ensure that the application understands how to handle the received fund amount, the fund must be configured in the Fund Configuration Engine. Configuration for the fund within the Fund Configuration Engine allows the application to understand what Borrower Based academic year (BBAY) to place the fund in, if the fund goes toward funding up to the COA, and other such items that help the application on the packaging and advisory side.
It should be noted that any received fund amounts through the student resource tag should not be adjusted by the application in the student's package, even if the fund is lower in priority than a Title IV fund. (for example, if the application is packaging a student up to COA and they've hit COA without accounting for the student resource fund, the Packaging Engine reduces the funds that are higher in priority within the Fund Configuration Engine to account for all the student resource funds).
If the fund is unknown to the application because it isn't configured via the Fund Configuration Engine, the application doesn't process the fund and the fund goes through the application exception handling process.
Required Role Permissions
The user must have a role with this General Permission through Roles Management to view the following information:
- Student
See Set General Permissions Matrix for more information.
Navigation to the Application UI Functionality
To view the packaged funds> Student > Financial Information > Packaging