Maintain Course Type Fee Trigger - FINF2220

Purpose

To create and maintain a link between a fee liability and the set of courses constituting a course type, in order that only students in the courses specified should be considered for the fee liability

Subsystem

Student Finance

Structure

Two blocks

Fee Category Fee Liability (context)
Course Type Fee Trigger

 

Back navigation button:

Return to:

Image

 

 

Triggers are used by the fee assessment routine (FINJ3500, FINJ3001) to decide whether a fee applies for a particular course a student is studying, 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.

Three forms are used to record course triggers. FINF2222 is used to specify individual courses. The current form and FINF2221 (dealing with course groups) allow a single trigger to operate for a particular grouping of a range of courses, as set up in the Course Structure and Planning subsystem.

This form matches course types to fee liabilities, and is probably the form that will be used most often in allocating fee triggers. The courses (and versions thereof) which form a course type follow government classifications, as explained in the documentation for the form Maintain Course Types, CRSF1110 in the Course Structure and Planning subsystem. Course types are assigned to course versions in CRSF1210.

These are examples of the government course types to which institution defined course types are allocated within the system:

1 Higher Doctorate
8 Bachelor's Graduate Entry
60 Open Learning Studies

Fees with a system fee type of HECS will commonly be set up with triggers for all award course types which in turn map to government course types. TUITION fees may also have course type triggers.

The form is accessed from Maintain Fee Categories (FINF2800), using the Fee Liabilities button and then selecting the Course Type Triggers button.

Course attributes. The form does not cater for different attributes of the courses in question, but only for the course versions established as being of a particular course type. Where only some attributes of the courses are to invoke fee assessment, this must be handled by setting up rates only for those attributes in the Define Fee Assessment Rates form, FINF2853. (For example, in that form there may be just one rate, which applies for an attendance type of full time. Effectively, this prevents an assessment being made against the selected fee type for student course attempts with any other attendance type.)

Deletion. Logical deletion, described below, allows for a trigger to be 'removed' from further use while still enabling transaction reversals to be made for those transactions that have already been created as a result of the trigger.

 

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 course types liable for the fee shown in the context block.

The course type entered here as a required field acts as a trigger used by the fee assessment routine to match course versions of the appropriate type to course attempts of eligible students, in order to levy the selected fee.

It is not possible to distinguish between different course offerings using this form

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. 

 

  • Course types are allocated to course versions in the Maintain Basic Course Details form, CRSF1210. Each course version is required to have a course type.
  • Only open course types can be selected here.
  • The creation date of a record is automatically supplied by the system.
  • Setting the 'Include deleted triggers' indicator allows the display of all triggers, including those that have been logically deleted, when the form is queried. It has NO effect on functionality in the fee assessment routine.

 Last Modified on 11 February 2000