fsao-13.html : v04.1.0.0

Each account type may have multiple Payment Agreements.

Rule of the sections:

Section two and three is for internal use only.
All account transactions must have the following values:

Student Number, Account Type and Payment Agreement.

The reason why fee/deposit is not a part of this, is that, fee/deposit is an attribute of the Account Type definition {FCSC-21}.

The minimum requirement per fee and/or deposit account is that each must have one account type and payment agreement link.

Account Types are defined in option {FCSC-21} for the subsystem SD.
Payment Agreement definitions are done in option {FSAM-24}.
In this option the student, account type and payment agreement is linked and only when linked, student account transactions can be processed on the student account.

Background programs will create this link whenever it is required, if the combination does not exist.
The user must create the link in this option if it does not exist, before manual transactions can be process.
The default account types that are linked to the system operational definition (Codes SC, SL, SM of subsystem SD) {FSAM-1}, will be linked in this option but will not have a payment agreement because the system controls that these account balances are either zero or a credit balance.

The option allows the user to search either per student, account type or agreement code or any combination thereof.

Field	Type & Length	Description
Student Number	N9	To see all the account type agreement codes linked to the student, use the student number to query the records and student name will be displayed as defined in option {SREGB-1}.
Account Type	A4	SD- Account type, as defined in option "Maintain Account Types" {FCSC-21}. Student journals can only be processed against an account type if a record for the account type/payment agreement exist in this option. Account type/agreement code combinations are automatically created when a student is registered. The account type description will be displayed next to the field.
Agreement	A2	Agreement code as defined in the option "Create Payment Agreements" {FSAM-24}. Account type/agreement code combinations are automatically created when a student is registered, according to the default payment agreements as defined per academic block in {FSAM-25} or linked to system operational definition (Codes SE, SF, SG, SF of subsystem SD) in {FSAM-1}. The agreement description will be displayed next to the field.
Effective Date	DD-MON-YYYY	This date will be calculated according to the system parameter SB / SD (Use Block or student Registration date) on {FCSM-1b2}, when the student is registered. Registration date, the effective date will be the same as the date of registration. Block date, the effective date will be the start date of the block. If the payment agreement is defined with fixed dates then this field can be null as the agreement date will be used. Should the agreement be based on days and the effective the date is updated on an existing account type / payment agreement, the student's account aging will be affected.
End Date	DD-MON-YYYY	Display only field and is calculated by the system. It is the date when the payment is 100% payable.
Balance	N15.2	The balance of the student / account type / payment agreement combination.

Date	System Version	By Whom	Job	Description
22-Feb-2007	v01.0.0.0	Amanda Nell	t135426	New manual format.
26-May-2007	v01.0.0.1	Ernie van den Berg	t157364	Review the manual.
09-Nov-2015	v04.0.0.0	Marchand Hildebrand	t193911	Convert to ADF
06-Dec-2019	v04.1.0.0	Isaac Matshela	T241040	Correction of manual and updating correct image

Maintain Student Payment Agreements {FSAO-13}