Top of FIN | Index | Table of Contents | Feedback |
FINF1720 - Maintain Charge Method Apportion
Purpose |
To make a link between Fee Calendars and Load Calendars that is used by the Fee Assessment Routine in determining a student's Fee Liability. |
|
SubSystem |
Finance |
|
Normally Run By | Finance Specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Fee Calendar Instance |
Charge Method Apportion | ||
Button | Back |
For each fee, this form makes a link between a Fee Calendar Instance and one Load Calendar Instance (Note: 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:
Fee Calculations are discussed in the Specialist Overview. Levels (The 'Levels' concept is explained in Special Topics) Charge Method Apportionment is specified as either:
Student Contribution Amounts and institution Fees must have their Apportionment data specified at FTCI level. Level Access This form is accessed:
The FTCI Charge Mthd Apportnmt 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. Other examples are: A Student Contribution amount 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 contains:
The Charge Method Apportion block contains:
|
Rule/Notes: The Fee Calendar Instance block identifies the Fee Period and level for which the Apportionment is relevant. If the Fee Category field is left 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. |
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 |
Rules/Notes: The instance in Load Calendar Type is selected from Calendars with a System Calendar Category of LOAD, and a Calendar Status of ACTIVE. Fees with a System Fee Type of COMSUPPORT (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 10 January, 2005