Top of FIN | Index | Table of Contents | Feedback | ![]() |
FINJ6240 - Process Student Loan Scheme
Purpose |
This job identifies if students are eligible for a Government Loan, their payment activity, and any sponsor payment activity |
|
SubSystem |
Finance |
|
Normally Run By | Fee Specialist | |
Anticipated Frequency | As required, based on major Payment Due Dates | |
Structure | Block | Process Student Loan Schemes |
Tab | Parameters | |
Buttons | Calendar | |
Find Person (ADMF1211) | ||
Find Course (ADMF1220) |
Introduction HEPs are required to assess a student’s Loan Amount and any associated Loan Fee for student’s who have a HECS-HELP or FEE-HELP liability as at the Census Date for a unit. Currently there is a job in Callista that is used for assessing a Student’s Loan Amount (FINJ6235 – Create Loan Draw-Down Entries). From 2005, HEP’s need to report to DEST, the correct Student Unit Attempt (SUA) Student Status for all students. Currently there is a job in Callista that is used to snapshot a Loan Scheme Student Status for a Student Course Attempt (SCA) (FINJ6231 – Process Student HECS Payment Options, which is currently also used to defer HECS). FINJ6235 and FINJ6231 are normally run sequentially. Callista is enhanced to combine the assessment of a Student Loan Amount and calculation of a Loan Fee (if applicable) with the Student Status Snapshot for a SUA. If the system is configured not to transfer sponsor debt to the loan customer (see FINF1R00), then any outstanding sponsored debt, will not be transferred to the loan customer via a loan transaction. For example, if the student is 100% sponsored, and the institution selects the Maintain Sponsor Debt indicator in FINF1R00, then a loan transaction will not be inserted by this job. If this student was partially sponsored (i.e. 50%), then a loan transaction will only be created for the student's unpaid debt - not the sponsor's component. Process Student Loan Scheme This function identifies if a student is eligible for a Government Loan based on their Student Status for a unit, their payment activity and the payment activity of any sponsor. When analysing the payment activity, Government discounts are to be considered. This function uses the Census Date for a unit when assessing a student’s Loan Amount. If run more than once this function considers any later payments from a student or a sponsor. A Loan cannot be used to pay off Retention Fees. In addition to a Loan Amount, a Loan Fee for FEE-HELP loans for Undergraduate Courses is calculated as per the new Loan Fee rule. This function applies the Loan Fee rule and record the Loan Fee amount in the Fee Assessment table. This function also snapshots the Loan Scheme Student Status for a Student Unit Attempt (SUA) as at the Unit Census Date. The declared Student Status for a unit, as at the Unit Census Date, are derived from the Override SUA Student Status (if one exists) or the Student Course Attempt (SCA) Student Status. This function compares the declared Student Status to any Unit Payment amount received at the time of running the snapshot. Each Student Status Snapshot value is based on the Student Status Snapshot Mapping. A Student Status snapshot is not recorded for a student if a TFN (or a TFCN) and/or an active or provisional CHESSN is required but has not been recorded. It is possible to Snapshot all Student Status’s for a selected Loan Scheme and it is possible to draw down a Loan Amount for all appropriate Loan Schemes or just an individual Loan Scheme. Where a student is enrolled in Units with different Census Dates, it is possible to specify which units to include in the Student Status snapshot and Loan Draw Down by entering the Unit Census Date into the parameter form. The Loan Scheme LOV will not display Loan Schemes that have a System Transaction Type of OSHELPLOAN, BOTPLSLOAN or PELSLOAN. Note: This job will not process future Census Dates. This form is accessed via the main menu. |
The Process Student Loan Schemes block contains: Parameter Tab
Select either ...
Or a combination of the following parameters ... |
Rule/Notes: The following fields are Mandatory:
Validations include:
|
When the report is run, the Total Students for Fee Category appears at the end of each Fee Category (before the next Fee Category starts). The Total Student Exceptions reported appear at the end of the report. An example of a Process Student Loan Scheme Report is shown below. |
Rule/Notes: The Effective Date parameter provides the ability to select/change the Effective Date within this job. See the title 'Effective Date Examples' below for further details. Fees are now unit based, so all fee processing and snapshots are completed for a specific Unit Offering Option. When a Census Date parameter is selected, only the students with a Unit Offering Option with a Teaching Period Census Date equal to the parameter selected are shown. If no Census Date input parameter is populated, then the job processes all past Census Dates in the Fee Period and does NOT process future Census Dates in the Fee Period. If a Teaching Period has multiple Census Dates, then the job only utilises the Census Date with the earliest absolute value. When determining the correct Student Unit Student Status Record to snapshot, it is the one active as at Census Date for the Unit. All payments received (up until the run of the job) should be taken into consideration, even if after the Census Date. All errors, warnings and information messages are inserted into the log table. When the Exception Report is run it will only extract the appropriate errors or messages as required by the Report Level Parameter. A summary of the total count for all types of messages (error, warning, information) is displayed at the end of the report. If the Log Creation parameter is entered, all other parameters are ignored. In this scenario the Loan Draw Down and snapshot process does not occur. However the report will run extracting records for the specified Log Creation Date. If the Loan Scheme has a System Transaction Type of ‘HCSHLPLOAN’ then the reported Student Status should be determined for each combination of Student Course Attempt and Census Date. Multiple Units can have the same Census Date. The Teaching Calendar of the Unit Offering Option is used to determine the Census Date. Units with the same Census Date will be considered as a group and the same Student Status will be reported for each of the Units in that group. If the student has not paid in full for any one unit in the group then the Student Status will be reported as deferred. If the student has paid each unit in full then the Student Status will be reported as upfront. If the Loan Scheme does not have a System Transaction Type of ‘HCSHLPLOAN’ then the Student Status is determined for each unit separately. If the student has two courses then the two courses must be treated individually when determining the Student Status. |
CALLISTA Process Student Loan Schemes Exception Report |
|||||
Creation Date: | Effective Date: | ||||
Fee Assessment Period: | |||||
Error: | |||||
Fee Category : | |||||
Person
ID
|
Name
|
Census
Date
|
Course
|
Loan Scheme
|
Message
|
Total Students for Fee Category : | |||||
Total Student Exceptions Reported: |
Effective Date Examples
If the process is required to run on a daily basis with the Effective Date set to the date of the job run then the Effective Date should be set to NULL in which case the process will use the date that the process is executed on. This method will work effectively until the End Date (End Date Alias) is reached. At this point the process will be unable to process students, since Fee Assessment transactions with a Transaction Category of ‘DEBT’ cannot be recorded after the End Date. At this point, the standing request should be replaced by a new request that sets the Effective Date to be equivalent to the End Date Alias date. Processing will then be able to occur for each student..
Fee Period |
Unit Code |
Effective Date |
Transaction Type |
Transaction Amount $ |
SEM1 |
ABC101 |
01/03/2006 |
ASSESSMENT |
1000.00 |
SEM1 |
ABC101 |
02/09/2006 |
PAYMENT |
500.00 |
SEM1 |
ABC101 |
02/09/2006 |
HCSHLPLN-D |
125.00 |
Semester 1, fee period has the following date aliases:
FEE-ASS-ST = 01/01/2006
FEE-ASS-EN = 30/06/2006
FEE-RETRO = 31/12/2007
SCENARIO 1
The job is run for an Effective Date = 01/02/2006.
The job will not work in this instance as the Effective Date is not equal or greater than the maximum effective date for debt transaction(s).
SCENARIO 2
The job is run for an Effective Date = 01/03/2006.
The job will work in this instance as the Effective Date is equal or greater than the maximum effective date for the debt transaction(s).
The job will determine that:
The Total Debt = $1000.00
And Total Paid + Discount = $625.00
Therefore Loan transaction amount = $375.00
Note: This job will still insert loan transactions if the Effective Date is prior to the maximum effective date of the Payment or Loan Discount transactions. It will only look for maximum Effective Date of Debt Transactions, like Manual Assessment, Manual Adjustment, Write-off etc.
SCENARIO 3
The job is run for an Effective Date = 01/09/2006.
The job will not work in this instance as the Effective Date does not fall inside the FEE-ASS-ST and FEE-ASS-EN.
Last Modified on 12 April, 2006