Maintain Charge Method Apportion - FINF1720

Purpose

To make a link between fee calendars and load calendars which is used by the fee assessment routine in determining a student's fee liability

Subsystem

Student Finance

Structure

Two blocks

Fee Calendar Instance (context)
Charge Method Apportion

 

Back navigation button:

Return to either:

Image

 

 

For each fee, this form makes a link between a fee calendar instance and one load calendar instance (Note that while Charge Method Apportion is a multi-row block, only one load calendar should be linked to the context fee calendar). This link between a fee and a load period allows the fee assessment routine (FINJ3500, FINJ3001) to determine

  • firstly, by an examination of relevant student unit attempts for the load period, whether an assessment for an individual student should be made in the corresponding fee period, based on load incurred
  • and secondly, if an assessment is to be made, and the charge method is EFTSU, CRPOINT or PERUNIT, what the value is for the 'elements' used in the fee calculation.

Fee calculations are discussed in the Specialist Overview.

Levels. (The 'levels' concept is explained in Special Topics.)

Charge method apportionment is specified either

  • at FTCI level, in which case the link between fee and load periods relates to the selected fee irrespective of category, or
  • at FCFL level, in which case the link only applies to the fee within the category selected.

HECS and institution fees must have their apportionment data specified at FTCI level.

Level access. The form is accessed

  • at FTCI level via the Charge Method Apport button in the Fee Type Calendar Instance block of Maintain Fee Types (FINF2100)
  • at FCFL level via the Fee Calculations button and then the Chg Method Apportion button (or FTCI Chg Method Apportn button) in the Fee Category Fee Liability block of Maintain Fee Categories (FINF2800).

The FTCI Chg Method Apportn 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.

Which calendars? Only one load calendar instance should be linked to each fee calendar instance for a fee (despite Charge Method Apportion being a multi-row block). It is generally recommended that fee periods closely follow the structure of standard load calendars. However, it may be a requirement to create some fees with a fee period that spans several standard load calendars. In this case an aggregate load calendar corresponding to the fee period can be created to group the spanned standard load calendars. For example, a year long load calendar (say LOAD-CAL-Y) can be created to group load from first and second semester load calendars (say LOAD-CAL-1 & LOAD-CAL-2) for the purpose of assessing an annual fee in a year long fee period.

Examples

  • A HECS fee will always need to be assessed in accordance with the standard load calendar structure. This fee might be allocated a fee calendar type of FEE-SEM1 (first semester assessment) and linked in this form to a single load calendar, LOAD-CAL-1, which relates to the same semester.
  • However a general service fee, GSF, might be assessed only once yearly, and therefore allocated a fee calendar type of FEE-YR. For this fee, an aggregate load calendar LOAD-CAL-Y, superior to both LOAD-CAL-1 and LOAD-CAL-2, will be linked to FEE-YR, so that the student loads returned via the load calendars for both first and second semester are aggregated under LOAD-CAL-Y, and taken into account.

 

The Fee Calendar Instance block identifies the fee period and level for which the apportionment is relevant. If the Fee Category field is blank, apportionment 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.

Rules and Notes:

 

For each fee, use this form to record the load calendar instance that is related to the fee calendar instance shown in the context block.

Deletion of load calendar records is possible. However, it is strongly advised not to make changes once fee assessment has started for a fee period. 

  • The instance in Load Calendar Type is selected from calendars with a system calendar category LOAD, and a calendar status of ACTIVE.
  • Fees with a system fee type of HECS or a system fee trigger category of INSTITUTN must have apportionment specified at FTCI level.
  • Only one load calendar should be specified per fee calendar instance.

 

Last modified on 8 November 1999