Introduction

StudentForms has different transaction types to allow a school to use StudentForms to collect documentation from a student for multiple purposes. Most of the transaction types in StudentForms move through the different transaction statuses with the exception of Other Documents, this transaction remains open.

The available transaction types in StudentForms are:

Verification

The verification transaction type is used for completing verification review, resolution of c codes, and reject codes. This transaction type may also be used for other student eligibility requirements that may require an ISIR correction.


For more information about the tasks that populate in the verification transaction type please review the following:

Student Actionable Comment Codes (student receives task when account created or logs in after ISIR imported)

School Actionable Comment Codes (these do not have a global task associated with them, the school would need to develop custom triggers to request documentation for these comment codes)

For more information on the documents available in Request Information please review: Request Additional Documentation 


Note: It is not recommended that a school request a task/document be added to this transaction type that is not required as part of verification or c code/reject code resolution. i.e. loan request documents, student information forms, etc.  Schools should add these as part of the Other Documents transaction type, detailed below.


SAP Appeal

StudentForms has a global satisfactory academic progress (SAP) appeal transaction available for a school to allow their students to appeal for reinstatement of federal student aid eligibility after failing to meet SAP. The global SAP appeal transaction type consists of a web form for the student to provide their signed statement detailing the extenuating circumstance that caused them to fail to meet sap, and what has changed to allow them to meet sap in the future. The appeal allows the student to upload supporting documentation. This appeal type does not have the ability to make ISIR corrections.


For information on updating the appeal instructions and settings please review Appeal Configuration.


PJ EFC Appeal

The PJ EFC Appeal transaction may be used by a school to make income and other adjustments to the student's ISIR that result in a recalculation of the student's EFC.  The global PJ EFC appeal transaction type consists of a web form for the student to provide a signed statement to support the circumstance selected as the reason for their appeal. 


When using the PJ EFC transaction type, if the school approves the appeal an ISIR correction file is always generated in StudentForms to update the Professional Judgment ISIR field to 1(EFC adjustment processed), even if no other changes were made.  The school should only use the PJ EFC appeal transaction type when they are setting the Professional Judgment field to 1, other appeals that do not result in the Professional Judgement field being set to 1 should not be completed using the PJ EFC Appeal Type. For appeals that are not related to an EFC adjustment, other appeal options are available in StudentForms.


For information on updating the appeal instructions and settings please review Appeal Configuration.


PJ Dependency Override Appeal

The PJ Dependency Override Appeal transaction may be used when the FAA is making a determination to make the override from a dependent to an independent student. The global PJ Dependency Override appeal transaction type consists of a web form for the student to provide a signed statement to support the circumstance selected as the reason for their appeal. 


When using the PJ Dependency Override transaction type, if a school approves the dependency override, an ISIR correction file is always generated in StudentForms to update the Dependency Override ISIR field to a value of 1(FAA override from dependent to independent). The value of 1 is the only value StudentForms will correct this ISIR field to, other values are not available to update through StudentForms. If a school is making a Homeless Youth Determination (Dependency Override ISIR field value 4) this should not be done using the Dependency Override transaction.


For information on updating the appeal instructions and settings please review Appeal Configuration.


COA Appeal

The COA Appeal transaction type in StudentForms may be used for a student to appeal extra expenses they may have that are above the allowances in the school's cost of attendance. The global form provides the student the ability to select a reason for the appeal, provide the expense amount, and a signed statement to provide an explanation of why the additional expense was necessary. No ISIR corrections may be made from this appeal type.


For information on updating the appeal instructions and settings please review Appeal Configuration.


EFC Appeal

The EFA Appeal transaction type in StudentForms may be used for generic emergency fund application. The global form provides the student with the ability to provide a signed statement to detail the need for emergency funds. No ISIR corrections may be made from this appeal type.


For information on updating the appeal instructions and settings please review Appeal Configuration.


Other Documents

The Other Documents transaction type in StudentForms may be used to collect documentation from the student that is not part of verification, c code, reject code resolution, and is not part of any other type of appeal in StudentForms. The other documents transaction is the only one that the transaction cannot be completed (closed, moved to verified). ISIR corrections may not be made from Other Documents.


Custom Appeal Transactions

If a school is unable to use the global appeals in StudentForms, a custom appeal transaction may be requested. These appeal types may take longer to develop and the school should plan accordingly. Custom Appeal transactions do not have the ability to make ISIR corrections.