Define Fee Encumbrances - FINF2890

Purpose

To specify the date or dates at which particular types of encumbrance will apply if a fee is unpaid

Subsystem

Student Finance

Structure

Two blocks

Fee Calendar Instances (context)
Fee Encumbrance

 

Back navigation button:

Return to either:
  • Maintain Fee Types (FINF2100) or
  • Maintain Fee Categories (FINF2800)
    (two levels)

Image

 

 

An introduction to setting up and managing encumbrances and their effects is found in the section on encumbrances in the Enrolments subsystem. The place of encumbrances in the general processing cycle is outlined in Understanding Student Finance. Schedules, of which the fee encumbrance form is one, are introduced in the Specialist Overview.

Encumbrance schedules come into effect when the Process Overdue Payment Penalties job (FINJ6230) determines that a student has an unpaid debt for a fee after a payment due date. In this situation, the job consults the encumbrance schedule to discover which encumbrance should apply. It then creates a 'pending fee encumbrance' record which is confirmed or cancelled by a fees administrator in the form Authorise Fee Encumbrances (FINF6311).

Schedule entries. An encumbrance schedule consists of one or more records. Where there is more than one, the records can be set up to distinguish between

  • different dates after which the accumulated encumbrance effects up to that point will apply (effects of each succeeding entry will normally become more severe) and/or
  • different encumbrances that can apply depending on the amount still to be paid at a single date.

Setting up entries. Entries can represent dates in one of three ways:

  • with 'fixed dates' only. These are selected from instances of one or more date aliases which must already have been defined in the Calendar subsystem
  • as offsets signifying a number of days after the payment due date in a student's individual payment schedule (these can be seen in the Maintain Person Payment Schedules form, FINF3800)
  • with fixed dates and offsets used in combination in one entry. The recommendation in this case is that the date alias instances follow those in the payment schedule for the corresponding fee liability, with an offset of one or more days.

The applicable encumbrance is decided by comparing the entries in the schedule against the effective run date of the processing job, FINJ6230.

Levels and overrides. Encumbrance schedules can be specified at any of the three levels, with implications as discussed in the Levels section of Special Topics. But they can only be at two levels concurrently, as follows:

  • at FTCI level and FCCI level concurrently, in which case the schedule at the FTCI level overrides that at the FCCI level for the corresponding fee only
  • at FCCI level and FCFL level concurrently, in which case the schedule at the FCFL level overrides that at the FCCI level for the corresponding fee only.

In both these cases, fees without schedules at either FTCI or FCFL level will have encumbrances applied according to the category schedule at FCCI level, even if they are in a group with other fees where an override applies. However, note the important exception described under WARNING for HECS and institution fees.

Where a fee is not covered by a schedule at any level, encumbrance effects do not apply.

HECS and institution fees. For fees with a system fee type of HECS or a system fee trigger category of INSTITUTN, encumbrance schedules must be at FTCI level.

WARNING. For these two cases, the fee assessment routine takes no account of schedules at any other level. Lack of a schedule at the FTCI level is taken to mean that no schedule exists, and therefore that no encumbrance applies. This is so even where a category which includes the corresponding fees as liabilities has a schedule attached.

Level access. The form is accessed

  • at FTCI level via the Fee Type Calendars button and then the Fee Encumbrance button from Maintain Fee Types (FINF2100)
  • at FCCI level via the Fee Encumbrances button from Maintain Fee Categories (FINF2800)
  • at FCFL level via the Fee Liabilities button and then the Fee Encumbrances button (or FTCI Fee Encumbrance button) from Maintain Fee Categories (FINF2800).

The FTCI Fee Encumbrance button is displayed when a schedule exists at FTCI level. The form can still be accessed from FCFL level, but only to display the existing FTCI schedule.

Example

Scenario: A payment of $300 due 11/6/99 has an unpaid amount of $175.
Effective run date of the Process Overdue Payment Penalties job, FINJ6230 is 22/6/99.

 

Date alias instance
Offset days
(days overdue)
Minimum Overdue %
Minimum Overdue Amount
Encumbrance Type
1st entry
2nd entry
3rd entry

-
-
-

5
10
15

-
50

100
-
75

FEE-ENC1
FEE-ENC2
FEE-ENC3

The debt is 11 days overdue at the effective run date, so the routine enters the schedule at the second entry. For both the first and second entry, the conditions apply (1st entry, the debt is over $100; 2nd entry, the debt is over 50%) so both FEE-ENC1 and FEE-ENC2 are created as pending fee encumbrances. In this situation the more severe of the two pending fee encumbrances would normally be authorised in FINF6311, and the other one cancelled.

If the debt had been assessed at $100 and the unpaid amount had been $55, only FEE-ENC2 would apply, since the outstanding amount would not meet the condition set in the first entry.

If the effective run date had been 14/6/99, no encumbrances would apply since this is less than 5 days after the due date, and so no entries would take effect.

 

The Fee Calendar Instances block identifies the fee period and level for which the schedule is relevant. For a schedule at FTCI level, the fee category is blank. At FCCI level, the Fee Type is blank. At FCFL level, there are entries in both Fee Type and Fee Category fields.

The currency is displayed if available to the calling form.

Rules and Notes:

 

Use the Fee Encumbrance block to record one or more entries representing dates after which the corresponding pending encumbrance applies.

Records can be entered as

  • all based on date aliases, with or without offsets, or
  • all based on offset days from a date shown in the person payment schedule (FINF3800), with no date aliases.

For each entry an amount, below which an encumbrance will not apply for an overdue payment, can be specified as either

  • a proportion of the amount due using the minimum overdue percentage, or
  • a fixed amount, using the minimum overdue amount field.

Alternatively, the amount fields can be left blank. An encumbrance will then apply to any amount overdue.

Some encumbrance effects require that a student's enrolment is discontinued - these can be seen in the list of all encumbrance effects. For the appropriate encumbrances, set the Discontinue Enrolment indicator here, in order to alert staff authorising encumbrances in FINF6311 that this is so.

The Write Off Bad Debt indicator is provided in preparation for future functionality.

  • Schedules for fees with a system fee type of HECS or a system fee trigger category of INSTITUTN must be specified at FTCI level.
  • A date alias instance can be used more than once, as long as different overdue percentages or amounts are given. This allows encumbrances of different severity to be indicated for the same date, depending on the sum overdue.
  • Warning 'lamps' advising that exceptions exist at another level are shown at FCCI level if, for any fee in the category,
    • a schedule exists at any other level, overriding the FCCI schedule for that fee
    • a HECS or institution fee is included in the category (see HECS and institution fees above).

 Last Modified on 11 February 2000