Institutions can choose to expire pending transactions for students by award year through a import file. Users with appropriate access can import the file by going to Admin>Expire Transactions. Expired transactions do not create any tasks for students, are not visible to students and are made view only for school users.


The import file must be a csv file that includes the following 4 columns for each transaction to be expired. A similar process can be used to "unexpire" or reactivate transactions that were previously expired. The file does not include a header row. 


  • First Column (SSN) – numeric only with no dashes
  • Second Column (Award Year) – single digit number. Use the last digit of the award year range similar to the ISIR file (e.g. 2017-2018 = "8", 2018-2019 = "9", etc.)
  • Third column (transaction type) – single digit number. “1” for Verification transactions, “2” for SAP Appeal transactions, "3" for Dependency Appeal transactions, "4" for EFC Appeal transactions, and "5" for Other Docs transactions
  • Fourth column (Action) – “Expire” or “Unexpire”


Example file



Note: The file may be created in an excel file and then saved as a csv file.


Expire Transaction Process


Once the expire transaction file has been created, the admin user navigates to the expire transaction screen in the admin menu > Expire Transactions.



Select the Import Button



Select the expire transaction file that was created from the location it was saved on the user's computer.



The file uploads and processes in StudentForms. 



Once the file processes, the results display.  Selecting the number in the successful or failed columns shows the specific students for that result.



The successful expired transactions hide the tasks for the expired transaction when the student logs into StudentForms.