Purpose |
To create and maintain a fee assessment rate or set of rates applying to a fee. |
|
Subsystem |
Student Finance |
|
Structure |
Two blocks |
Fee
Calendar Instance (context) |
Navigation
buttons: Back
Cohort
Details button Unit Details button |
Return to either Unit Fee Assessment Rate pop-up form |
|
See Also | Valid System Values for Fee Types | |
Image |
The
rates shown in this form are used by the fee assessment
routine (FINF3500, FINJ3001) in the basic 'number of elements * rate'
calculation to arrive at a student's liability for a particular fee.
A rate is always a rate per element. A
discussion of rates as a component of fee calculation in the assessment
routine is given in the Calculations section of the Specialist Overview. Additional information
and examples are given in the Rates section
of Special Topics. Levels. (See Levels in
Special Topics for background information.) Assessment
rate data can be attached at either FTCI level, with the rate(s) for
a fee applying irrespective of category, or at FCFL level, in which
case the rate or rates apply to the fee only within the category selected.
Some fees must be specified only at FTCI level. These are:
Other
than these, rates can exist at either level, but not at both levels
for the same fee type. Level
access. The form is accessed
The
FTCI Assessment Rate button is displayed when apportionment data is
already entered at FTCI level. The form can still be accessed from FCFL
level, but only to display the existing data. Multiple rates. Within a level, multiple charge rates can be set up for a single fee depending on various course attempt attributes (course, course version, location, attendance type, attendance mode), unit attempt attributes (unit, unit version, unit location, class), cohort,or government payment classifications. For instance, the rate of a general service fee may depend on the location at which a student is studying, while HECS rates applying after the introduction of differential HECS vary according to government contribution bands. Care needs to be taken when setting up these attributes and payment characteristics that the circumstances of all students due to pay the fee are covered by one or other of the permutations. This is documented in more detail in the Rates section of Special Topics. |
The
Fee Calendar Instance block identifies the fee period
and level for which the rate or rates are relevant for the selected
fee. If the Fee Category field is blank, the rate data is operating
at FTCI level, but with a category shown, the data operates at FCFL
level. The
currency is displayed if available in the calling form. If not
shown, the local currency applies to any rate recorded here, and can
be found in the Maintain International Currency Codes form, FINF1410. The charge method indicated the kind of element involved in the calculation. For example, if the charge method is CRPOINT, the rate applies per credit point. |
Rules
and Notes:
|
One
or more rates can be recorded in the Fee Assessment
Rate block. A different rate number is assigned by the system
to each rate for the fee. Cycle through existing rates by using the
up and down arrow keys, or the Next and Previous Record buttons or menu
commands. The
charge rate defined in this form is the rate per element used
in the calculation whose rule is given in the calling form. An element
may be a credit point, a unit, or an EFTSU value, depending on the charge
method stipulated for the fee. For fees with a charge method of FLATRATE,
the element value is always 1. Fees
with a system fee type of TUITION or OTHER may have rates
that vary according to permutations of course code, version
number, location code, attendance type, attendance
mode, cohort code, unit, unit version, unit location and class.
When any of these attributes are used to define a rate, and the attributes
are not mutually exclusive, an order of precedence must be given
- a rate with the precedence number 1 will be used in preference to
one with the precedence number 2, where both might apply. Unit assessment
rates must have a higher order of precedence than course rates. Fees
with a system fee type of HECS or TUITION may vary by
government HECS payment option, and HECS fees may vary by government
HECS contribution band within a payment option. A
TUITION rate can combine elements from both course attributes
or HECS payment characteristics. Where
a record with identical criteria but a different rate is required for
use against an element range (see FINF2852), the rate for use against a range should have an
order of precedence of lower priority than the corresponding normal
rate. Rates specifically for element range use are usually flat rates.
For
a discussion of the implications of using these course attributes, unit
attributes, cohorts and government classifications, see the Rates section in Special Topics.
The
Cohort Details button is only displayed when a rate has been defined
for a cohort of students. The Cohort Description pop-up form gives the
rule and the explanation for the cohort code that is defined. See GENF1000
for cohort rules. The
Unit Details button is dynamic and it will only be displayed when the
system fee trigger category is UNIT. The button will display [+] when
a rate has been defined for a unit and/or unit version, unit location
and/or class in the Unit Fee Assessment pop-up form. Rates can be logically deleted. If they are, any dependent element range rates are also logically deleted. A deletion date is supplied by the system. To see rates that have been logically deleted, select the Include deleted rates indicator and re-query. |
|
Last
Modified on 9
January, 2003.