FINF2222 - Maintain Course Fee Trigger

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

Finance

Normally Run By Finance Specialist
Anticipated Frequency As required
Structure  Blocks Fee Category Fee Liability (from FINF2100)
Course Fee Trigger
Button Back

  

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 (bottom right) and then selecting the Course Triggers button (middle button, bottom left).

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.

Scenario 1

For Course A700, version 2 was 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 2

A 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 contains:

  • Calendar Type
  • Start Date
  • End Date
  • Fee Type
  • Fee Category
  • Change Method

The Course Fee Trigger block contains:

  • Course Code
  • Version Number
  • Title
  • Trigger Group
  • Include Deleted Triggers check box
  • Calendar Type
  • Location Code
  • Attendance Mode
  • Attendance Type
  • Creation Date
  • Deletion Date

Rule/Notes:

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.

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 Fields

The 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.

  • The Version Number, if selected, effectively sets the trigger at Course Version level.
  • Calendar Type, if selected, effectively sets the trigger at Course Offering level.
  • Location Code and/or Attendance Mode and/or Attendance Type effectively sets the trigger at Course Offering Option level.

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.

Rules/Notes:

Only courses with a System Course Status of ACTIVE or PLANNED can be entered here.

The Trigger Group list of values presents all groups recorded for the liability except those with a Deletion Date.

Open Calendars with a System Calendar Category of ACADEMIC can be selected in the Calendar Type field.

Only Locations with a System Location Type of CAMPUS are shown in the LOV.

Setting the 'Include deleted triggers' check box 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.

The Creation Date of a record is automatically supplied by the System.

 

Last Modified on 9 December, 2003