Introduction

The Transactions tab on the student profile contains a list of all existing transactions created for a student and allows the ability to manually request new ones, as needed.



Manage Transactions

The Transactions tab contains a list of all transactions created for a student. These are separated by transaction, award year, and tracking group (if multiple appeals per award year are allowed). By default this list is sorted by Last Status Update so that users see the most recent transactions with actions taken at the top.



The Transactions grid contains the following data:

  • Transaction: this name is a combination of the award year and transaction name
  • Award Year
  • Tracking Group: the tracking group/cohort name given to the transaction for additional tracking purposes. This is typically required when requesting an appeal transaction. If an transaction is requested by the student, then it will default to "Student Request 20xx-20xx". In other cases, like opening the Verification transaction, it may default to "School" if manually opened by an institutional user, or "System" if triggered to open.
  • Creation Date and Time
  • Status: This displays the current status of transaction
    • Collecting documents: the transaction is currently waiting for the student to complete all tasks assigned
    • Re-collecting documents: the transaction was submitted by the student, but the institution has either rejected a document provided or has requested additional info and is now waiting for the student to complete all tasks assigned again
    • Reviewing documents: the student has submitted all documentation and there are currently outstanding documents to review by the institution
    • Reviewing file: all documents have been reviewed and the transaction is awaiting completion of file review
    • Processing corrections: file review has been completed for the transaction and is currently waiting for a subsequent ISIR with the expected corrections to be processed
      • this status is only used by the Verification, PJ Family Contribution Appeals, and PJ Dependency Overrides transactions
    • Verified: file review has been completed
      • for Verification, PJ Family Contribution Appeals, and PJ Dependency Overrides transactions, this means either no corrections were required from file review and the transaction is now complete, or for transactions needing corrections the expected corrections came through a subsequent ISIR and completed the transaction
      • for appeal transactions, the institution has completed file review by approving or denying the transaction
    • Expired: the transaction has been expired, making it no longer needed. for Verification, PJ Family Contribution Appeals, and PJ Dependency Overrides transactions, these transactions will not be affected by subsequent ISIRs.
    • Ignored: the transaction has been ignored. This typically occurs by manually opening a Verification transaction that has no student actionable tasks. Institutions can ignore the transaction so that it does not appear on any workflows, but still has potential to reopen if a subsequent ISIR comes in with new c codes that may trigger tasks
  • Last Status Update: the date and time this transaction reached the current status
  • Review: closes the student profile modal and navigates to the file review page for the selected transaction


Please note that transactions are tied to specific user roles. For example, a user with only the SAP User role will only see SAP transactions to review. The only exception is for users with the Admin or School FAO roles - they have access to multiple transactions.



Create a Transaction

Institutions have the ability to manually request a new transaction as needed. There are several factors that limit whether or not a transaction can be requested.

  • Transactions are tied to user roles (i.e. a user with only the SAP User role may request a SAP transaction). The only exceptions are tied to users with the Admin or School FAO roles, which can access several transaction types.
  • Transactions are only available if they are within their current operational dates, managed by each award year
  • The PJ Dependency Override Appeal transaction is only available to request for students whose most recent award year ISIR indicate that they are a dependent student
  • Appeal transactions will not be available to select if they are currently disabled
  • Certain appeal transactions may not be available if an ISIR is not found for the award year, but this may be configurable
  • Certain appeal transactions may may not be requested more than once within the same award year, but this may be configurable


  • click the Add button to begin requesting a new transaction


The Request Transaction modal manages all of the options that a user can request. The modal reviews the award year selected, what roles a user has, what has already been created for the student, and whether or not transactions are currently available. It then displays what options the user is allowed to select.


  • select an Award Year
  • select the transaction or action to take (see subsections below for more details on each transaction/action)
  • complete the remaining details
  • click the Submit button to complete the request


Open Verification Transaction

This action creates the Verification transaction for the selected award year. Once the transaction has been created, whether by an institutional user, the student, or a custom trigger, this option is no longer available for the same award year. This option generates the Verification transaction as is - all tasks normally generated by ISIR student action codes and any custom triggers that the student meets the criteria for will immediately be implemented. If the student is not already selected for verification on their ISIR, the institution can still manually select a student for verification.


No additional details are required in order to submit the request. 


Request Other Document

This action adds a selected document/web form to the Other Documents transaction. Other Documents is a transaction that holds documents/web forms that don't relate to any of the other appeal transactions or the Verification transaction. If the Other Documents transaction has not already been created for the award year, the submission will open the transaction to place the document within.


When selecting Request Other Documents, users will need to select the document to request and provide a reason for the request. The reason will appear on the student side, within the task as an additional message. It is recommended to provide instructions and/or reason that will be understandable to the student.


After a request has been submit, the user will immediately be navigated to the file review page for the selected transaction. This page includes the document review library (for all documents submitted for this transaction), the file review section for ISIR transactions (Verification, PJ Dependency Override Appeals, and PJ EFC Appeals), and access to the student view to preview the transaction as the student sees it.


Select for Verification

This action will manually select a student for verification, based on the Verification Group selected. This option is only available if the student's most recent ISIR for the selected award year is not already selected for verification or has already been manually selected by the institution. Once submitted, the Verification transaction will be opened with verification tasks specific to the Verification Group selected, along with all tasks normally generated by ISIR student action codes or any tasks generated by custom triggers that the student meets the criteria for.


When selecting Select for Verification, users will need to select the Verification Group (V1, V4, or V5) and provide a reason for the request. The reason will appear on the student side, within the task as an additional message. It is recommended to provide instructions and/or reason that will be understandable to the student.


Professional Judgment: Dependency Override Appeal

This action will open the PJ Dependency Override Appeal transaction for a student who wish to appeal their dependent status list on the ISIR. This option is only available if the student's most recent ISIR for the selected award year indicates that they are a dependent student. Once submitted, the PJ Dependency Override Appeal transaction will be opened with the global PJ Dependency Override web form task and/or any tasks generated by custom triggers that the student meets the criteria for.


When selecting Professional Judgment: Dependency Override Appeal, users will need to provide a Tracking Group (by default the system will generated it as "PJ Dependency Override 20xx/20xx"), select the circumstance of the request (this list is managed in Settings > Appeals), and provide a reason for the request. The reason will appear on the student side, within the task as an additional message. It is recommended to provide instructions and/or reason that will be understandable to the student.


Professional Judgment: Family Contribution Appeal

This action will open the PJ EFC transaction for a student who wish to appeal their expected family contribution (EFC) reported on their ISIR. Once submitted, the PJ EFC transaction will be opened with the global PJ EFC web form task and/or any tasks generated by custom triggers that the student meets the criteria for.


When selecting Professional Judgment: Family Contribution Appeal, users will need to provide a Tracking Group (by default the system will generated it as "PJ EFC 20xx/20xx"), select the circumstance of the request (this list is managed in Settings > Appeals), and provide a reason for the request. The reason will appear on the student side, within the task as an additional message. It is recommended to provide instructions and/or reason that will be understandable to the student.


All Other Appeal Transactions

All other actions will open a transaction for the selected transaction type. This includes the following transactions:

  • Satisfactory Academic Progress (SAP) Appeal
  • Cost of Attendance Appeal
  • Emergency Fund Application
  • All custom institutional transactions

Once submitted, the selected transaction will be opened with any global web form task and/or any tasks generated by custom triggers that the student meets the criteria for.


When selecting any of these options, users will need to provide a Tracking Group and provide a reason for the request. The reason will appear on the student side, within the task as an additional message. It is recommended to provide instructions and/or reason that will be understandable to the student.