Fee Assessment Routine and Trace - FINJ3500

This process updates the database
Subsystem	Student Finance
Purpose	To assess or reassess the fees (and where applicable, tax) due from students or potential students for a particular fee period. Fee assessment is the central process of the Student Finance subsystem. This is one of two methods of running the fee assessment routine. The current job and the job that has as input the Student To Do entries (FINJ3001) are different 'front ends' to the same process. The present job can be run in batch or immediately, allows great flexibility in parameter selection, can provide a detailed 'trace' report of the processing steps and outcomes for each student and fee, and can be run in test mode without updating the database.
Normally Run By	A fees administrator
Anticipated Frequency	As required
Update Process(es)	Creates transactions reflecting either initial assessments or adjustments to previous assessments for each of the fees for which an applicant/student is liable, as determined by the relevant structures created in the Student Finance subsystem.
Parameter Sample
Reports	Fee Trace Report
Report Sample
Related/Dependent Jobs	The fee assessment routine is the initial process in a fee period cycle. All other fee processes are consequent upon it. It may be run with FINJ6111 (the job to create students' individual payment schedules) as a dependent job. To do so, however, has certain ramifications - see Dependent Jobs below. The job FINJ3002 provides the facility to reproduce a full trace for a previous run of the current job, where this has been run with parameters specifying an abridged trace. This job can also be run online from the Course Attempt screen of the enrolments form ENRF3000, and for predictive assessments directly from the Admissions form ADMF3660 and from ADVF4200.

Update Process	This section gives a brief outline, in sequence, of the main processing involved in fee assessment as an aid to reading the Fee Trace Report. It assumes a good understanding both of the general approach taken in the subsystem and of the data structures for fee types, fee categories and liabilities, triggers, calculation data and retention schedules. (Please refer to Understanding Student Finance and the Specialist Overview.) For commencing students, the system may use a student’s course commencement date as the effective date when processing a Student Course Attempt (SCA). See notes on Commencing students only, below. The fee assessment routine: Checks the validity of parameter values at the parameter effective date given for running the routine - all subsequent steps described here take parameters into account to narrow selections For each financial period specified by parameter. For each fee category with a fee period valid at the parameter effective date (and in the financial period, if specified). For Enrolment Fee Assessments as specified by activating the check box. For Advanced Standing Fee Assessments as specified by activating the check box. Note: One or both of the process advanced standing fee assessments and process enrolment fee assessments indicators must be set. Checks today is not past the retro date of the fee period Finds student course attempts with a fee assessable status on the effective date (currently Course Attempt Statuses of DISCONTIN, ENROLLED, COMPLETED, INACTIVE and INTERMIT are fee assessable) Students with a status of DISCONTIN, COMPLETED or INTERMIT may have been enrolled during some part of the fee period. The date on which a student discontinued enrolment is checked to verify this, while a completed enrolment is fee assessable if the census date of its teaching period falls within the fee period. For predictive assessments only, UNCONFIRMed course attempts are also considered.
	For each ACTIVE fee liability in the category and fee period: Checks for a match between a student course attempt and/or unit set attempt and/or unit attempt and a trigger For a unit trigger (including a unit within a trigger group), checks that the student's unit attempt is fee assessable (Unit Attempt Status of DISCONTIN, ENROLLED, COMPLETED or INVALID) For a unit set trigger (including a unit set within a trigger group), checks that the effective date for the student’s course attempt is either the same as, or after, the student unit set attempt Selection Date and not after either the End Date or Completion Date (where set) Determines the appropriate load calendar For each unit for which load is incurred: If a HECS fee, checks that it is not an industrial experience unit (and therefore exempt from HECS) Determines the value of the charge elements represented by the unit in terms of the charge method for the fee, and keeps a running total of charge elements across units Additionally, for HECS, the EFTSU for a unit is split by discipline group (Fee assessable statuses for student unit attempts are ENROLLED, INVALID, DISCONTIN and COMPLETED) Calculates the assessed amount for the fee, taking into account that the rate may be determined by - - different course attributes (course code, version number, location code, attendance type, attendance mode) or payment options (government HECS payment option as at census date, HECS contribution band) - element range values - a contract agreement with the student For HECS, the calculation is based on the rate for each relevant contribution band if students are liable for differential HECS. Discipline groups match to particular contribution bands, and a running total of the student's HECS fee across different bands is kept Or, for predictive assessments without unit attempts: Calculates the charge elements from the applicant's nominated attendance type for a course attempt (see ADMF3660) before the rate is determined as above.
	For each fee liability assessed: Writes an assessment transaction record (representing the student's liability for this fee) to the database if this is a first time assessment Or, if assessments already exist for the fee liability: Checks the student's current debt situation: if a more recent assessment exists, the student's record is not updated. Otherwise, the effective date for the student’s course attempt is written to the database. This ensures that the correct enrolment details are accessed for statements produced after this run If the last assessment was a manual fee assessment no further assessment transaction updates are made for this fee. Otherwise - if the current assessment is different from the previous one, a negative or positive adjustment is made and an assessment transaction record written to the database if the adjustment is negative (i.e. the student's debt has been reduced) the retention schedule is accessed to determine if an amount over and above the new assessment should be retained, and a retention transaction record is written to the database if required. Where applicable, after any fee liability assessment, adjustment or retention (including those manually assessed): Checks whether tax applies. If so: calculates the tax due on the total assessment amount now stored, including any retention amount (rather than calculating on the individual transaction) if this tax balance differs from the previous one stored, a negative or positive tax transaction is written to the database. NOTES The transaction records created by this process can be seen in the form Manual Fee Assessment (FINF3610) or the inquiry form FINF9120, accessed via FINF9100 or FINF9200. are the basis for ascertaining a student's assessed debt wherever used in the subsystem. Commencing Students only Students are generally enrolled in units before the start of their course. For these students, fees may need to be assessed and collected before the course commencement date. As long as these students are due for assessment in a current fee period, the system will substitute the student’s course commencement date for the effective date of the course attempt (SCA) if the effective date entered by parameter falls before the commencement date. This ensures that correct enrolment details are recorded for these students and used by subsequent finance jobs. In this scenario, the following applies: · Assessment is based on units with an enrolled date on or before the new effective date (the commencement date). Units recorded with an enrolled date later than this are not assessed. · For students enrolled in more than one course, the latest of the course commencement dates in the fee period is used. · For institution fees, the latest of a student’s SCA commencement dates in a relevant fee period is used. A relevant fee period is one where the institution fee is a liability. · When discontinuing units before commencement, the system ensures that students are only liable for retention amounts appropriate to the schedule in effect at the parameter effective date (if any). · Once an SCA commencement date is past, it is not possible to retrospectively assess a student’s relevant fee liabilities before that date.

Run Details

Method This job can be run immediately, in batch mode through the Job Control & Scheduling subsystem, directly from the Course Attempt screen of the enrolment form ENRF3000, from ADMF3660 for predictive fee assessments or from ADVF4200 for advanced standing. For information on running in immediate mode, see the documentation on reports. Note that the facility to run the Fee Trace Report directly to file is not currently available, but that running in immediate mode affords the opportunity to print screen output to file (through the Previewer) specifying a postscript printer, and then use third party software to view and distribute it electronically. Dependent Jobs The job may be set up to run with the Maintain Person Payment Schedules (FINJ6111) as a dependent job. However, note that FINJ6111 sets the dates by which individual students should make payment of fees. It is therefore necessary to produce statements (Statements of Account and Sponsor Summary Statements) in a timely manner after running FINJ6111. Refer to documentation about creating person payment schedules for more information. NOTE: It is strongly recommended that extensive testing of the data structures set up by an institution in this subsystem should be undertaken against a comprehensive sampling of student records before committing to a live run. The current job allows for test runs to be undertaken without updating the database, and the Fee Trace Report shows in detail the data structures that are accessed in determining assessments for a student.

Job Parameters

NOTES: Data values that have been closed will not appear in the list of values and cannot be typed in, but will be included where relevant if the 'all' option is selected. Parameters Set an effective date, which must be after the start date (date alias) recorded for the required fee period, and normally not later than the current date (the default). The effective date can only fall within the start and end dates for the fee period. (See the documentation on fee periods for more information on dates, and the notes on the situation for commencing students.) For predictive assessment only, the effective date can be after the current date. It is recommended that it not be set later than the Course Start Date Alias instance recorded for the related Admissions period. This is so that, if applicants subsequently do not confirm enrolment in a course attempt, their predictive assessments for that course can be removed. Optionally: Enter a person ID if the job is to be run to create or update a single student's fee assessment Enter a course code, if required, to select matching student course attempts Select or type in a fee category to assess only those students included in a particular category Select a financial period and/or fee assessment period Select or type in a fee type to assess only those students liable for a particular fee. Set the Predictive Assessment indicator to Yes to include unconfirmed student course attempts. This allows for assessments to be made for applicants pre-enrolled during the Admissions process.

The final parameters, which can be used in combination, specify processing requirements: Set First Time Assessments to Yes to confine processing to students not hitherto assessed in the fee period. This shortens processing time because re-evaluation of students for possible reassessment is avoided. Running the process from the front-end job accessing the Student To Do entries is a more efficient way to re-assess those students whose enrolments have changed. The Trace On parameter is set to Yes to produce the trace report in full or abridged version. It is recommended that, in batch mode, the full trace be run only for individuals or small groups of students. Set the Display/Warnings Only parameter to Yes (with Trace On parameter also set to Yes) to produce the abridged trace, reporting only those messages designed as WARN or ERROR messages. This abridged trace is useful to alert staff to a problem with a particular student's assessment in an extensive run, though little context information is given. Set Test Run to Yes to run the process without updating the database. Activate the Process Enrolment Fee Assessment check box to include these fees in this run. Activate the Process Advanced Standing Fee Assessment check box to include these fees in this run.

Report(s)

The Fee Trace Report

The full version of the Fee Trace report (when the parameter Trace On is set to Y, and Display/Warnings Only to N) gives extensive detail of the data used and decisions taken in arriving at a fee assessment or reassessment for a student. Report length The full report is at minimum approximately a page for each fee liability for each student. It can run to seven pages for a single student with two fee liabilities. It is therefore recommended that the full trace be run only for an individual or a small group of students when in batch mode. Layout Though complex, the trace is fully internally documented and follows this pattern: financial period (if selected by parameter) and fee period information is displayed for each student, details of their course attempt in the fee category are given (with a summary at the top of each page thereafter) next, a fee liability for the student is given, together with its associated data followed by the details of the processing for that fee as outlined in steps in the Update Process section.

Last Modified on 26 February, 2003.