Top of FIN | Index | Table of Contents | Feedback | ![]() |
FINJ6111 - Maintain Person Payment Schedules
Purpose |
To create an individual Payment Schedule for a newly assessed student or amend a student's existing schedule after re-assessment. |
|
SubSystem |
Finance |
|
Normally Run By | Fee Specialist | |
Anticipated Frequency | Weekly during the Fee Assessment cycle. | |
Structure | Block | Person Payment Schedules |
Tab | Parameters | |
Buttons | Find Person | |
Calendar Lookup |
Update Process This process assesses new transaction records created by the Fee Assessment Routine. Where the transaction represents an initial Fee Assessment for a student, this process creates one or more 'Person Payment Schedule' (PPS) records for each assessed fee for which the student is liable. This personal schedule for a Fee Liability includes:
Where
the transaction represents an adjustment to a student's debt for a fee,
the process amends the relevant amounts in the student's personal schedule.
For Govt. Loan Schemes (for example, FEE-HELP and HCS_HELP), when creating Person Payment Schedules the job also considers PPS Payment Due Dates that have been altered as these can influence payment matching. The process amends the Due Date details up until the last date configured to the expected payment in the Fee Payment Schedule. If a Fee Type has a Government System Loan Scheme type, then FINJ6111 derives and uses the last Fee Payment Schedule configured for the Fee Liability Calendar Instance (ordered by the Fee Payment Schedule Start Date). Run DetailsMethod This job can only run in batch mode, through the Job Control and Scheduling subsystem. It
can be set up to run as a dependent job of the Fee Assessment routine
either when run via FINJ3500
or FINJ3001.
Notable Effects Since this process creates records with actual dates for payment, it is important that statements containing these dates should be created and sent to students and sponsors as soon as possible after it runs. If there is a delay between running this job and creating or posting statements, a further job, Add Grace Period to Person Payment Schedules (FINJ6112) enables Payment Dates to be extended by a set number of days.
See diagrams below for description of 'Different Lowest Level', and 'Get Student Configured Sponsorship Details'. Job Error Handling This job allows processing to continue when an error (other than 'System' type errors as described below) is encountered . Run log details also display the following summary information:
The Run log will contain details like those shown below:
Note: 'System' type errors will still cause the job to fail. These might be technical errors relating to the management and operation of the database that would normally be dealt with by a DBA or Oracle - for example, errors that relate to size or a rollback segment, and any errors in the Oracle product itself. Note: The Generate XML File from System Log (GENJ1100) job can be utilised to access logged exceptions for FINJ6111. |
The Person Payment Schedules block contains: Parameters Tab
Buttons
|
Rules/Notes: May be run as a dependent job of the Fee Assessment Routine (FINJ3500 or FINJ3001). The Person Payment Schedule (PPS) represents expected payment amounts for loan schemes. In particular, the sponsor amount is the maximum amount the sponsor will be required to pay. The PPS Due Date is used as the initial means to determine which liabilities will be paid first when a payment is received, or if sponsorship is to be allocated. |
Parameter Details: Fee Assessment Period parameter: The
job must be run for each Fee Period in which it is required to create
or modify person Payment Schedules. Select the period from the list
of active Fee Assessment Periods presented in the first parameter.
Person ID, Fee Type and Fee Category parameters: The
next three parameters control the range of students for whom schedules
are created or updated. The % symbol indicates that all values should
be included for that parameter:
Notification Date, Days to Notification, Schedule Next Business Day parameters: The next three parameters specify data required for processing. Where
offsets are used in the 'template' Payment Schedule, actual dates for
payment are calculated from the Notification Date:
The final two parameters enable Person Payment Schedules (PPS) to be initialised for increased or decreased debt or both. Initialise Schedules on Increase in Debt parameter: Set this parameter to N when the Notification Date is altered and an extra PPS entry for a particular Fee Type is required in the PPS to indicate an increase in debt. Set this parameter to Y to initialise the PPS and create a new PPS entry for a particular Fee Type that includes the increase in debt. The original PPS entry for this Fee Type is then logically deleted. The result is a single PPS entry for this Fee Type that includes the debt increase. If the Notification Date is unchanged and this parameter is set to Y a new single entry is created that includes the increased debt amount. The original PPS entry for this Fee Type is logically deleted. If the parameter is set to N, the relevant PPS amounts are updated. Initialise Schedules on Decrease in Debt parameter: Set this parameter to N to decrease the assessed amount of the last entry in a set of PPS entries for a particular Fee Type. Multiple PPS entries are set up in the Payment Schedule template (FINF2860). The ratio originally defined in the Payment Schedule template between each entry in the set is not maintained. Set this parameter to Y to initialise the PPS and proportionally decrease the assessed amount of each entry of a multiple PPS entry set. The ratio originally defined in the Payment Schedule template between each entry in the set is maintained. Exceptions:
|
Rules/Notes: Fee Type job parameter is irrelevant to sponsorship processing. It will always do all Fee Types to maintain the order of sponsorship. When re-assigning sponsorship for the person, fee calendar, course and sponsor, the sponsorship is applied to system Fee Types in the following order: 1. TUITION or VET-TUIT (with loan fee rule attached to context fee period)
And within system fee_type by fee type ASC, unit_cd ASC and payment due dt DESC person payment schedule sequence_number ASC. If a sponsor sponsors a student in two courses with the same institution fee, the first course sponsorship (course cd Ascending) will sponsor the institution fee, unless a sponsor limit prevents this. If a limited amount is assigned to the institution fee, this sponsorship will stand even though the second course sponsorship may be able to sponsor the fee to a greater amount. If no sponsorship is assigned to the institution fee from the first course sponsorship, the second course sponsorship may sponsor that fee. Where the first sponsorship sponsors the fee. If the second sponsor has a sponsorship limit defined, the amount of the first sponsor’s sponsorship may also appear to be applied from the second sponsorship. For example, the institution fee sponsorship may also be deducted from the second sponsorship. This is due to the fact that when processing the second sponsorship it cannot determine which course sponsorship has been allocated to the institution fee. This will only be an issue where:
This issue is remote and a work-around is achieved by manipulation of the sponsorship at the fee_liability sponsorship level. i.e. excluding the institution fee type from the sponsorship of the second course. If different sponsors sponsor a student in two courses with the same institution fee the first sponsor (sponsor_cd Asc) will sponsor the institution fee unless a sponsor limit prevents this. If a limited amount is assigned to the institution fee this sponsorship will stand even though the second sponsors sponsorship may be able to sponsor the fee to a greater amount. If no sponsorship is assigned to the institution fee from the first sponsor the second sponsor may sponsor that fee. If a student is in two courses and has two fee categories, and the job is run for a specific fee category. So long as one of the students fee categories matches the job parameter, the student will be processed and sponsorship for BOTH fee categories will be removed and re-assigned. SA-HELP Fees The Person Payment Schedule determines which course attempt created the student's SA-HELP fee. Once the course is determined, the Person Payment Schedule looks at ENRF3240 for that course attempt and if the Declaration Date and End Date straddle the fee period census date, then the student's SA-HELP debt is assigned to the loan scheme. This will occur unless:
|
Different Lowest Level
If the SCAFS level sponsorship limit is null and percentage contribution is 100% (i.e. the default values), the sponsorship limit/percentage contribution at the lowest levels at which data is entered are used and the sponsorship limit and percentage contribution at other levels are ignored. For example:
Note that there may be more than one ‘lowest level’, for example if two fee types TUITION and SERVICE are specified, and units are specified for the TUITION fee type, then the lowest level is the unit level for TUITION fees and fee type level for SERVICE fees. This is illustrated in the following diagram:
Get Student Configured Sponsorship Details
The following process takes into account the assignment of sponsors.
Last modified on 1 June, 2012 12:09 PM
History Information
Release Version | Project | Change to Document |
13.0.0.3, 14.0.0.2, 15.0 | 1834 - Service and Amenities | Added note about SA-HELP fees. |
13.0 | 1577 - Unit Fee Payment Matching | Added information re: altered Payment Due Dates for Loan Scheme fee types, and a note about GENJ1100. |
12.0.0.2 | 1617 - VU - SV Fee-Help | Added VET_TUIT in the list of system fee types in the Rules/Notes section. |
10.1.0.0.0.0 | 1348 - Job Error Handling Part 1 | Added details re Job Error handling and Run Log details. |