Importing ISIRs

Before you begin, you must first download your institution's ISIRs from your institutional SAIG mailbox.

To import ISIRs, click the Import Process in the Processes bar of your Dashboard and for process type select Import ISIR.

If you do not see the Import ISIRs process on your Dashboard, your user roles are not set up to allow you access to this process. If you believe you should have access to this process, contact your system administrator.


Browse to the location of the file containing the ISIRs to be imported and then click on the Import icon.

When ISIRs are imported in bulk (i.e., YTD ISIR - all ISIR's for a student for a given FAY) – and no ISIR's have been previously imported for the student – the entire set of ISIR's is processed at once and the highest transaction based upon the ISIR source will be set as active: 'Department' or 'School' sources or 'Applicant' source (when no 'D' or 'S' sources exist). An ISIR with a blank source will only be set as active when there are no additional ISIRs for the student for that FAY.

When subsequent ISIRs (those with higher transaction numbers) are received, the subsequent ISIR with the highest transaction number is set as the Active ISIR unless the ISIR was initiated as a result of an 'Applicant' action which did not resolve a reject condition or the subsequent ISIR contains a change selecting the student for verification or moving the student to a different verification group.

If the subsequent ISIR was initiated as an applicant action and the subsequent ISIR did not clear a reject condition, then a task should be initiated for staff to manually review the ISIR record.

When subsequent ISIRs (those with higher transaction numbers) are received, the subsequent ISIR with the highest transaction number is set at as the Active ISIR unless the ISIR was initiated as a result of an applicant action which resulted in the student being selected for verification. If the subsequent ISIR was initiated as an applicant action and the subsequent ISIR resulted in the student being selected for verification, then a task should be initiated for staff to manually review the ISIR record. If the subsequent ISIR was initiated as a result of applicant action, and the subsequent ISIR clears any SAR C, the subsequent ISIR with the highest transaction number is set at as the Active ISIR.

If you want to create records for students being imported who do not already exist in Regent Award, select the "Create Student if he/she doesn't exist" option, select Institution and Campus, and then click on the Import icon.


In the Process Log, you can check the status of the file as it is loaded. If the file is large, the process may take a while to complete.
When an ISIR file is delivered by the institution through the sFTP process to be imported into Regent Award, it should be placed in the ISIRLoad_FW sFTP file folder.


Note: Any student records that fail to load will be included in the process log (See the section on Process Log for more information). Click on the student tab for the appropriate file in the process log to see the reasons the student record failed to load.


There are four scenarios in which an ISIR will fail to load because it is identified as a duplicate. The validation messages and corresponding criteria for identification of the duplicate ISIR are shown in the table below.

Validation MessageIdentification Criteria
This record is a duplicate of another ISIR already loaded for this student for all matched Institutions (via the Federal School Codes).Same Name ID, Social Security Number, Institution ID, Federal Award Year, AND Transaction Number as an ISIR that has already been imported and linked to a non-deleted student. 
This record is a duplicate of another ISIR loaded by the current import for the student for transaction ##.

Same Name ID, Social Security Number, Institution ID, Federal Award Year, AND Transaction Number as an ISIR in the same file/process when the student has not yet been matched.

For each set of duplicates found, the ISIR with the MAX isirRecordDataId is the one that is processed.

This record is a duplicate of another ISIR loaded by the current import for student [{externalId1}|internal #####] and transaction ##.

Same Name ID, Social Security Number, Institution ID, Federal Award Year, AND Transaction Number as an ISIR in the same file/process when the student has been matched.

For each set of duplicates found, the ISIR with the MAX isirRecordDataId is the one that is processed.

This record is a duplicate of another ISIR loaded by the current import for student [{externalId1}|internal #####] and transaction ##.

Same Name ID, Social Security Number, Institution ID, Federal Award Year, AND Transaction Number as an ISIR in a prior file/process where the student has been matched.