Purpose |
To create and maintain a link between a fee liability and a course or courses, in order that only students in the course(s) specified should be considered for the fee liability To include a course as a member of a trigger group |
|||
Subsystem |
Student Finance |
|||
Structure |
Two blocks |
Fee Category Fee Liability (context) |
||
|
Back navigation button: |
Return to:
|
||
Image |
|
Course fee triggers enable the fee assessment routine (FINJ3500, FINJ3001) to match course related fees to corresponding student course attempts, as discussed in the Specialist Overview. If a course trigger recorded against a fee liability matches a student course attempt, the student is eligible for assessment. If triggers are recorded in this form, distinctions can be made between course versions, and within versions at the course offering and offering option level. This is in contrast to the much broader groupings at course version level which are possible when triggers are recorded in the Maintain Course Group Fee Trigger form (FINF2221) and the Maintain Course Type Fee Trigger form (FINF2220). This form is most useful in setting up a small number of courses with fees particular to the course, or to a specific method of studying the course. Fees applying to a large number of courses are better set up within course groups or course types, and distinguishing between course attributes in that case is discussed in the documentation for the relevant forms, FINF2221 and FINF2220. When used for a fee liability with a COMPOSITE category, a course recorded here can be included as part of a trigger group. Trigger groups are established in FINF2224. The form is accessed from Maintain Fee Categories (FINF2800), using the Fee Liabilities button and then selecting the Course Triggers button. Course attributes . The courses that act as triggers are recorded in the Course Fee Trigger block. Distinctions within courses are made depending on the values recorded in optional fields, as indicated below.Deletion . Logical deletion, described below, allows for a trigger to be 'removed' while still enabling transaction reversals to be made for those transactions that have already been created as a result of the trigger. |
Examples |
Scenario 1For course A700, version 2 is established in 1995. With a postgraduate tuition fee trigger set only for this version, the fee could be restricted to students enrolling in the course in or after 1995. Scenario 2A course where a materials delivery fee is levied only for off-campus students studying through the Warrnambool campus could be represented in this form by recording an off-campus attendance mode and the Warrnambool location code, but leaving all other optional fields blank. The fee would apply to all off-campus students studying through Warrnambool, both full-time and part-time. The fee would also apply to course attempts of any course version and under any academic calendar. |
The Fee Category Fee Liability block shows the fee liability (fee within a category in a fee period) and charge method for which triggers are recorded in the following block. |
Rules and Notes:
|
Use this form to record, maintain or view the courses, and the combinations of criteria for courses, which determine the scope of the fee liability selected. The course code entered here as a required field is matched by the fee assessment routine to the course attempts of eligible students. Optional fieldsThe recording of values in any of the fields indicated below allows for many permutations in the application of fees to courses. Where location code, attendance mode and/or attendance type have been selected, the fee assessment routine matches the values given here to values held against the student's course attempt.
For fee liabilities with a COMPOSITE trigger category, a course recorded here can be included as a member of a trigger group by selecting a trigger group number. There is a limit of one course per trigger group. The same course can be used as a member of more than one trigger group for the same fee liability, if required. To logically delete triggers, select and delete the record as normal. No Save is necessary - confirmation is requested before an automatic logical deletion is performed. A deletion date is supplied by the system. |
|
Last Modified 11 February 2000