Maintain Contracts {FSAC-10}

This option allows the user to create and maintain a contract definition. Contracts are used when a student applies and/or registers for a qualification. It allows the user to define up to 3 entities (including the student) that will be responsible for paying the student account.

The following should be taken in consideration before the client starts using this functionality:

It is not a mandatory function

If it needs to be mandatory on institutional level, the system operational definition SN of subsystem SD must be set to Yes in {FSAM-1}.

A contract is link to an application and/or qualification registration, when an application and/or qualification registration is processed in {SNAPPA-1}, {SREGAR-1} and {SDREGA-1}. The student iEnabler also allows for a contract to be used.

If not mandatory on institutional level, contracts can still be used when required but the system will not force the use of a contract at application and/or registration.

Contract characteristics

A contract can be defined to cater for both:

Internal business rules

Formal and informal contracts with external parties

If a formal contract with an external party exists, it can be to complex to be defined as one contract in this option. Split the external contract into as many different contract definitions as needed in order to cater for the full context of the external contract.

A contract works together with the academic structure and student fee structure. Processing an application or registering a student against a contract will not override any of the rules that are applicable for an application or registration with regards to the academic structure and student fee structure. The only difference between processing an application or registering a student against a contract versus not using a contract is that the tuition fee that is charged on the student account will be divided into different account types as per the contract definition if a contract is used.

A contract is valid for a specific period (start and end date), which can be for a short period of time, or can run over years.

The contract contains a student type which need not be the same as the student type linked to the student biographical record. If the contract contains a student type and student type is also one of the fields used to determine the fee value on the fee structure, the contract student type will be used to determine the fee value.

System operational definition SO for subsystem SD must be set to Yes {FSAM-1} to make student type mandatory for contracts.

The contract definition can be set up to control the following maximums (it is optional):

Monetary Value (total value of fees that can be raised on student accounts against he contract)
Number of Heads (students)
Number of Qualification Enrollments
Number of Subject Enrollments

A contract can be restricted to specific qualifications and also the number of enrollments for the qualification under the contract.

The contract/qualification combination can be restricted to specific subjects and also the number of enrollments for that subject under the contract/qualification combination.

Part of the contract definition is to specify the entities of the contract. As already stated, a contract can have up to three entities or payee types responsible for paying the student account. These payee types are the student, a contractee and a contributing employer. The contributing employer need not be the student's actual employer.

The contractees and contributing employers are defined as AR debtors in the AR system. An AR debtor can be used in more than one contract.
Any number of contractees and/or contributing employers may be linked to the contract.
On application/registration, a student is linked to a contract and one of the contractees and/or one of the contributing employers defined on the contract definition.

Tuition fee that is generated against the student account during a contract application and contract registration, is distributed between the payee types selected at this time, according to specific user defined rules on the contract definition.

All transaction types used for registration (event 03), qualification (event 05), subject (event 07), residence (event 13) in {FSAM-1}, are available on a contract to link to distribution rules. Every transaction type can be defined to distribute the cost differently between the payee types. If a subject, for example, is linked to more than one transaction type on the fee structure in {FSAM-1}, the applicable transaction types can be linked to different distribution rules on the contract.
In addition, for subjects only, the distribution rules on the contract can differ per subject code plus a distinction can be made between first and thereafter enrollments for the same subject.
The basis of the distribution rules can be percentage based or amount distribution.
The contract can also add a premium and/or discount on each of the transaction types. Premiums and discounts are processed as separate transactions on the student account and use the same distribution rules as the original transaction type.

Transactions for all the payee types are generated on the student account, but the contractee and contributing employer student account records does not form part of or is not revealed to the student. The student account only caters as a medium to post invoices to the AR system per debtor in summary (More than one student for a contract per invoice.)

Expenses against the contract can also be recorded by linking a cost centre to each contract and payee type for which this functionality is necessary. The cost centres that are linked for this purpose must be unique throughout all contracts and should be used for this purpose only.
The aim is to produce a detailed income and expense statement per contract.
The user has the choice of transferring all tuition fees generated against the contract and debtor to the costs centre or generate AR invoices for the costs incurred against the cost centre against the AR debtor. A combination of these options is also possible.
AR invoices can be generated using

the expense budget processed against the cost centre
the actual expenses incurred against the cost centre
Quantity * unit price as defined on the contract definition

Any of the above combinations can be used per contract but only one method per contract and debtor is possible.

Contract AR debtors can also assist in the student service centre activities {SDSERC-6}.

Certain fields on the contract definition are sensitive to and not updateable if a quotation or registration was confirmed for a student.

The information below identifies the main characteristics of the contract.

Fields in the option:

Block 1: Contract Definition

Field	Type & Length	Description
Contract Number	A4	Enter a unique code to identify this contract. Once a contract has been used on a student application/registration the user cannot delete it. If the contract code can be deleted (not yet used elsewhere in the system) then all records in the following tables of this option will also be deleted.
Description	A40	Enter a mandatory description for this contract. Tip: Do not give more than one contract the same description.
Service to Bad Debtor	A1	This field is equal to yes if checked and will default to yes. This field is used in conjunction with the bad debtor field on the AR biographical record of the debtor in {FARO-21}. If checked the contract will ignore the AR bad debtor status. If not checked: The application/registration system will only allow using a contractee or contributing employer where the AR debtor status is not a bad debtor status. If all the contractees and contributing employers on the contract are AR debtors with a bad debtor status, the contract cannot be used. If the debtor did not have a bad debtor status during the application process, but was flagged as a bad debtor before the registration is processed, the debtor will not be allowed and must be changed for the registration.
Use in iEnabler? Application Registration	A1 A1	This fields is equal to yes if checked and will default to not checked. If checked, the contract will be available for use in the checked process, application and/or registration.
Qualifications Restricted	A1	If the contract is set to qualification restricted, the qualification code(s) to which the contract is restricted to, must be entered on the next tab (Contract Qualification Definition). If the contract is qualification restricted and there are no records entered on the next screen, a warning will be displayed to notify the user. This is a warning only and the user will still be allowed to exit the option without entering qualification codes.
Copy Contract	Button	This is a facility to copy the active contract and all its underlying structures to a new contract code. A pop up screen will be displayed where the user must enter the contract number and description of the new contract. On <SAVE>/<COMMIT>, all information regarding the active contract will be duplicated for the new contract code. The contract code and description will be changed to the values of the fields in the pop up screen where applicable. All the normal validations of this application will be done for the new contract code as if entered by the user. If there are no validation errors, the record will be committed and displayed to the user. The user may change where applicable.
Loan/Allowance Indicator		Valid values are: L - Loans A - Allowance B - Both Loans and Allowance N - None Null This indicator has no other function or validation than to be set on this contract definition.
Student Type	A2	A system operational parameter ‘STUDENT TYPE MANDATORY Y/N’ for subsystem ‘SD’ and code ‘SO’ exists on {FCSM-1b2} that must be set by the user and will determine if this field is mandatory or not. If entered by the user, the value must be a valid student type as on the student type code structure in {SCODE3-5}. A <List of Values> is available and the user can drill down to the student type code structure from this field on right click of the mouse.
Start Date End Date	(DD-MON-YYYY) (DD-MON-YYYY)	The start and end date defines the period for which the contract is valid. These are mandatory fields. Application quotations can be issued and/or registrations can be performed between the start and end dates of the contract, relative to the system date. This start date cannot be changed once a quotation is issued and/or a student is registered against the contract. The end date is updateable and must be greater than or equal to start date.
Contract Monetary Value Maximum	N17.2	This is the maximum amount for which students can enroll under this contract, all payee types inclusive. Not mandatory. Enrollments may span over different years and blocks. When this maximum is reached, an error message will be displayed and the user will not be able to process any more applications or registrations against this contract. This is a collective value for all students linked (applications as well as registrations) to this contract. The value must be greater than zero if not null. If the user changes this value, the system will calculate the total value of students quoted (where the quote did not expire (quote is valid for 30 days from date of issue)) and registered against this contract. This calculated value must be less than or equal to this changed contract maximum amount. When the maximum is reached the system will sent a notification, for more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract monetary maximum validation is not necessary, it will save time during student application and registration process. Note that you cannot use the contract monetary value threshold % and threshold value if maximum is null .
Contract Monetary Value Minimum	N17.2	A minimum amount can also be entered, but this value will only be used for reporting purposes. This is not a mandatory field. It can be used at the end of the contract period to determine if this minimum requirement was reached. If entered, this value must be greater than zero and less than or equal to contract maximum value, if contract maximum value is inserted or updated. If the contract maximum value changes, the system will validate that this minimum amount is less than or equal to contract maximum value.
Contract Monetary Value Threshold %	N5.2	This is a percentage (%) that can be specified. An early warning report will calculate if this % of the contract maximum value has been reached and print it on the report. This is the total value of the quotations generated and students registered against the contract, excluding canceled quotations and canceled enrollments. If this field is null and the user entered the contract maximum value, then this field will default to 80.00. If entered, this value must be greater that 0 (zero) and less than 100. Edit only item, but must be completed if contract maximum value is entered. When the threshold is reached the system will sent a notification, for more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract monetary threshold % validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
Contract Monetary Value Threshold Value	N17.2	This is an amount that can be specified. Value must be less than contract maximum value. When this total value of offers has been reached, it will be printed on the early warning report. Again, canceled quotation and canceled registrations will be excluded. If this field is null and the user entered the contract maximum value, this value will default to the contract maximum value times 80%. If not null, then this value must be greater that 0 (zero) or less than the contract maximum value. Edit only item, but must be completed if contract maximum value is entered. When the threshold is reached the system will sent a notification, for more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract monetary threshold validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
No. Heads Maximum	N6	This is the maximum number of students that can enroll under this contract. Not mandatory. Enrollments may span over different years and blocks. When this maximum is reached, an error message will be displayed and no more applications or registrations can be processed under this contract. This is a collective value for all students under this contract. If not null the value must be greater than zero. If the user changes a value that is not null, the total number of heads of students quoted (where the quote did not expired (quote is valid for 30 days from date of issue)) and registered under this contract will be calculated. This calculated value must be less than or equal to this changed contract maximum number of heads. If not, an error message will be displayed: The contract is already committed to the value of (calculated value), cannot change contract maximum number of heads to a smaller value. When the maximum is reached the system will sent a notification. For more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract head maximum validation is not necessary, it will save time during student application and registration process. Note that you cannot used the contract head threshold % and threshold value if maximum is null .
No. Heads Minimum	N6	The minimum expected student enrollments under this contract. Not mandatory. This can be used at the end of the contract period to determine if this minimum requirement was reached. If entered, the value must be greater than zero and less than or equal to contract maximum number of heads if contract maximum number of heads is not null.
No. Heads Threshold %	N5.2	This is a percentage (%) that can be specified. An early warning report will calculate if this % of the maximum number of heads has been reached and print it on the report. This is the total value of the offers made and would exclude canceled quotations and canceled enrollments. If this field is null and the user entered the contract maximum number of heads, then this field will default to 80.00. If not null, then this value must be greater that 0 (zero) or less than 100. Edit only item, but must be completed if contract maximum number of heads value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract head threshold % validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process
No. Heads Threshold Value	N17.2	This is an number of heads that can be specified. Value must be less than maximum number of heads. When this total value of offers has been reached, it will be printed on the early warning report. Canceled quotations and canceled registrations will be excluded. If this field is null and the user entered the contract maximum number of heads, then this field will default to the contract maximum number of heads times 80%. If not null, then this value must be greater that 0 (zero) and less than the contract maximum number of heads. Edit only item, but must be completed if contract maximum number of heads value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract head threshold validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
No. of Qualification Enrollments Maximum	N6	This is the maximum number of qualifications that can be linked to this contract. Not mandatory. Enrollments may span over different years and blocks. When this maximum is reached, an appropriate error message will be displayed and no more applications or registrations can be processed under this contract. This is a collective value for all students under this contract. The value must be smaller than or equal to maximum of enrollments if used. If not null the value must be greater than zero. If the user changes a value this value, the total qualification enrollments of students quoted (where the quote did not expired (quote is valid for 30 days from date of issue)) and registered under this contract will be calculated. This calculated value must be less than or equal to this changed contract maximum number of qualification enrollments. When the maximum is reached the system will sent a notification. For more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract qualification maximum validation is not necessary, it will save time during student application and registration process. Note that you cannot used the contract qualification threshold % and threshold value if maximum is null.
No. of Qualification Enrollments Threshold %	N5.2	This is a percentage (%) that can be specified. An early warning report will calculate if this % of the maximum number of applications and qualification enrollments has been reached and print it on the early warning report. This is the total value of the offers made and would exclude canceled offers and canceled enrollments. If this field is null and the user entered the contract maximum number of qualifications enrollments, then this value will default to 80.00. If not null, then this value must be greater that 0 (zero) or less than 100. Edit only item, but must be completed if contract maximum number of qualification enrollments value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract qualification threshold % validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
No. of Qualification Enrollments Threshold Value	N17.2	This is a number of qualifications that can be specified. Value must be less than maximum number of qualification enrollments value. When this total value of offers has been reached, it will be printed on the early warning report. Again, excluding canceled quotations and canceled registrations. If this field is null and the user entered the contract maximum number of qualification enrollments, then this field will default to the contract maximum number of qualifications enrollments times 80%. If not null, then this value must be greater that 0 (zero) or less than the contract maximum number of qualifications enrollments value. Edit only item but must be completed if contract maximum number of qualification enrollments value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract qualification threshold validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
No. of Subject Enrollments Maximum	N6	This is the maximum subjects for which students can enroll under this contract. Not mandatory. Enrollments may span over different years and blocks. When this maximum is reached, an appropriate error message will be displayed and no more applications or registrations can be processed under this contract. This is a collective value for all students under this contract. If not null the value must be greater than zero. If the user changes this value, the total subject enrollments of students quoted (where the quote did not expired (Quote is valid for 30 days from date of issue)) and registered under this contract will be calculated. This calculated value must be less than or equal to this changed contract maximum number of subject enrollments. When the maximum is reached the system will sent a notification. For more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract qualification maximum validation is not necessary, it will save time during student application and registration process. Note that you cannot used the contract qualification threshold % and threshold value if maximum is null.
No. of Subject Enrollments Threshold %	N5.2	This is a percentage (%) that can be specified. An early warning report will calculate if this % of the maximum has been reached and print it on the report. This is the total value of the offers made and would exclude canceled offers and canceled enrollments. If this field is null and the user entered the contract maximum number of subject enrollments, then this value will default to 80.00. If not null, then this value must be greater that 0 (zero) and less than 100. Edit only item, but must be completed if contract maximum number of subject enrollments value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract subject threshold % validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
No. of Subject Enrollments Threshold Value	N17.2	This is a number of subject that can be specified. Value must be less than maximum number of subject enrollments value. When this total value of offers has been reached, it will be printed on the early warning report. Canceled offers and canceled registrations will be excluded. If this field is null and the user entered the contract maximum number of subject enrollments, this field will default to contract maximum number of subject enrollments times 80%. If not null, then this value must be greater that 0 (zero) and less than the contract maximum number of subject enrollments value. Edit only item, but must be completed if contract maximum number of subject enrollments value is not null. When the threshold is reached the system will sent a notification. For more detail on the topic, see field "Early Warning Notification Route Number" Tip: set this value to null if the contract subject threshold validation is not necessary (NB the maximum must be null as well), it will save time during student application and registration process.
Communication		Communication value: O - Online Campus only M - Request Material only B - Both N - None The communication indicator will be used to exclude enrollment records where enrollment is defined as 'O' or 'N'. N - None: No material requests to be generate for the qualification enrollment and / or subject enrollment M - Request Materials only: Requests to be generated for material for the qualification enrollment and / or subject enrollment. O - Online Campus only: No Material requests to be generated for the enrollment. B - Both: Requests to be generated. If the contract is linked to indicator 'B' or 'M', the items on {SDGUIM-1} marked as Mandatory / Critical will be generated.

Example:

Page 2: of Block 1: Contract Definition

Field	Type & Length	Description
Approval Required	A1	Valid values: (O)nce, (E)very time or (N)ever. This is a mandatory field and will default to (N)ever. This field is used in {SNAPPA-1} 'Academic Applications' TAB Contracts field Approval Received. If Approval is required: (O)nce - Set the field Approval Received to Yes only for the first application that uses the contract. (E)very time - Set the field Approval Received to Yes for each application that uses the contract.
Dist. Ed. Issue Postal Address	A1	Enter the distance education issue postal address requirement as student, contractee or contributing employer. Valid values: (S)tudent, (C)ontractee, Contributing (E)mployer. This field is used by {FPMO4-25} "Issue Request (Postal List)" when printing the issue documents (also called the issue pack) using the programs of {FPMOR4-11, 12 or 13}.
Print Invoice	A1	This fields is equal to yes if checked and will default to not checked. {FSAO1-10} 'Transfer of Transactions from SD to AR' creates the AR invoices/credit notes and the documents are printed from {FAROR1-1 or 2} for the payee types contractee and/or contributing employer. In some cases, the AR invoices/credit notes should not be sent to the debtor. In these cases, set this field to not checked else to sent set to checked.
Billing	A1	Valid values (P)eriodic or (A)ctual. This is just an indicator to indicate that under this contract the invoicing to the debtor is based on actual usage or whether periodic billing is applicable. It can be used for reporting purposes and is just a characteristic of the contract. Not used in any other program.
Contract Invoice Code	A4	The contract invoice code schedules the invoice process for the contractee and contributing employer in {FSAO1-10} 'Transfer of transactions from SD to AR'. This value must exist in the contract invoice code definition {FSAC-11}. A <List of Values> is available and the user can drill down to the contract invoice code option {FSAC-11}. Contract invoice code scheduling is done in {FSAC-12}
Allow Results to Involve 3rd Party	A1	Valid values Y/N. All exam results programs will be sensitive to this indicator. It determines whether the results of a student can be made available to the contractee and/or contributing employer of the contract. If checked, the system will allow results to the contractee and/or contributing employer.
Source of Funding	N2	Valid values as per SDR field 2.11 table. This is used in the SDR returns. The row code of table 88010 (SDR returns) is used as the source of funding for the latest version. A <List of Values> is available.
Report to External Body	A1	Valid values Y/N. This flag is used for example in the SD 3rd party payments subsystem (option {FSATPP-5}) to determine whether the info for students enrolled under this contract must be reported to the external body. If checked, the system will allow report to external body.
Marketing Account Manager	N9	The marketing account manager (personnel member {PBOP-1}) that is responsible for the contract. The marketing account manager and academic contract manager for the contract must be different. This must be a personnel member where the start date of employment is less than or equal to system date and the resignation date is greater than system date. A <List of Values> is available.
Academic Contract Manager	N9	The academic contract manager (personnel member {PBOP-1}) that is responsible for the contract. The marketing account manager and academic contract manager for the contract must be different. This must be a personnel member where the start date of employment is less than or equal to system date and the resignation date is greater than system date. A <List of Values> is available.
Prevent Transfer	A1	This fields is equal to yes if checked and will default to not checked. This flag, if checked, will exclude the contract from the transfer of transactions from the SD subsystem to the AR subsystem ({FSAO1-10} 'Transfer of transactions from SD to AR). The flag is to be set if something is wrong with the contract setup, its data to be transfer or any other reason not to transfer.
Early Warning Notification Route Number	N10	A display only field. This field will be updated by the system, with the latest Early Warning Notification Route Number {GROU-2}, if the contract has reached one of it threshold's. The route {GROU-1} that the system used is coded "CON1" with description "Contract Early Warn Notification". The routing system will sent notification via email to the marketing account manager and academic contract manager. The route will auto complete in option {GROU-2}. Make sure that both managers has a primary email address, correct and valid, in option {PBOP-1} in TAB Communication. While this field is not null no further early warning notifications will be sent and the contract threshold validation is stopped. If the user make a valid change to any maximum or threshold field then this field will be set to null and that will start the contract threshold validation.
Maximum Threshold Notification Route Number	N10	A display only field. This field will be updated by the system, with the latest Maximum Threshold Notification Route Number {GROU-2}, if the contract has reached one of it maximum's. The route {GROU-1} that the system used is coded "CON2" with description "Maximum Threshold Notification". The routing system will sent notification via email to the marketing account manager and academic contract manager. The route will auto complete in option {GROU-2}. Make sure that both managers has a primary email address, correct and valid, in option {PBOP-1} in TAB Communication. While this field is not null no further maximum threshold notifications will be sent and the contract maximum validation is stopped. If the user make a valid change to any maximum or threshold field then this field will be set to null and that will start the contract maximum validation.

Example:

Block 2: Contract Qualification Definition

This table identifies the valid qualifications that can be taken under this contract, if any qualification restrictions apply. This is the second screen of the contract definition. The user must maintain this only if indicated in the 1st block that the contract is qualification restricted.

This is a two block screen. The user can only navigate to this block when click on the TAB Contract Qualification Definition and a contract record is active in block 1. The system will default the contract code of block 1 in this screen, navigate to block 2 and do an automatic query of all qualification/s linked to the contract. The user cannot navigate to any other TAB of the contract definition, use <EXIT> to navigate back to the contract and then other TAB's can be accessed. While in the screen the user may navigate to the first block of this screen and query any other contract code and maintain its qualifications in the second block.

The user may NOT delete a qualification record, IF students have application quotes (where the quote did not expire (quote is valid for 30 days from date of issue)) and/or students are registered under this contract for the qualification

Field	Type & Length	Description
Contract Number	A4	The contract code of the active contract code when the user moved to this block. Query of any other contracts are allowed. A <List of Values> is available.
Description	A40	Display field only. The system will display the description of the contract code.
Qualification Code	A6	Enter the Qualification {SACADO-1} the contract is restricted to.
Qualification Description	A40	Display field only. The description of the qualification code will be displayed.
Subject Restricted	A1	This fields is equal to yes if checked and will default to not checked. This field indicates whether only selected subjects are valid under this contract and qualification. If yes, the subjects that the contract and qualification are restricted to must be specified on TAB - Contract Qualification Subject. If no records are specified in the contract qualification subject definition TAB, for the contract and qualification, a warning will be displayed.
Max Enrolled	N6	This is not a mandatory field. Sometimes there may be a restriction in the contract regarding the maximum number of students that may enroll for a specific qualification under the contract. This field indicates that maximum. If not null the value must be greater than zero. If the user changes this value, the total number of student applications (where the quote did not expire (quote is valid for 30 days from date of issue)) and student registrations under this contract and qualification will be calculated. This calculated value must be less than or equal to this changed contract qualification maximum number of enrollments. When the maximum is reached the system will sent a notification, for more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract qualification maximum validation is not necessary, it will save time during student application and registration process.

Example:

Block 3: Contract Qualification Subject Definition

This table identifies the valid subjects that can be taken under this contract and qualification, if any subject restrictions apply for a contract qualification. This is the third block of the contract definition. The user must maintain this only for contract qualifications where it is indicated in the 2nd block that the qualification is subject restricted.

This is a three block screen. The user can only navigate to this block when click on the TAB Contract Qualification Subject Definition and a contract record is active in block 1. The system will default the contract code in block 1 of this screen and navigate to block 2, default the first qualification for the contract, navigate to block 3 and do an automatic query of all subjects linked to the contract qualification. The user cannot navigate to any other TAB of the contract definition, use <EXIT> to navigate back to the contract and then other TAB's can be accessed. While in the screen the user may navigate to the first and second block of this screen and query any other contract code and/or qualification and maintain its subjects in the third block.

The user may NOT delete a subject record, IF any students were were quoted (where the quote did not expire (Quote is valid for 30 days from date of issue)) and/or registered under this contract, qualification and subject.

Field	Type & Length	Description
Contract Number	A4	The contract code of the active contract code when the user moved to this block. Query of any other contracts is allowed. A <List of Values> is available.
Description	A40	Display field only. The system will display the description of the contract code.
Qualification Code	A6	The system displays the first qualification code of the contract when the user moves to this block. Query of any other qualification for the above contract is allowed. Use <NEXT RECORD> or <PREVIOUS RECORD> to view the different qualifications of the contract.
Description	A40	Display field only. The system will display the description of the qualification code.
Subject Code	A7	This must be a valid Subject {SACADO-10} for the Qualification {SACADO-1}. The system will allow Subjects linked to the Qualification in the Curriculum in {SACADO-17} for the academic year where the contract start and end dates match the block start and end dates in Census Dates {GOPS-1}. All Offering Types of the Subject for the Contract's Student Type should be set to active in {GCS-5} TAB - Offering Type - Student Type Link
Subject Description	A45	The description of the subject will be displayed.
Max Enrolled	N6	This is not a mandatory field. The maximum number of students that may enroll for this subject under this contract and qualification can be specified. If not null the value must be greater than zero. If the user changes this value, the total subject enrollments of students applied (where the quote did not expired (quote is valid for 30 days from date of issue)) and registered under this contract, qualification and subject will be calculated. This calculated value must be less than or equal to this changed contract qualification subject maximum number of enrollments. When the maximum is reached the system will sent a notification, for more detail on the topic, see field "Maximum Threshold Notification Route Number" Tip: set this value to null if the contract qualification subject maximum validation is not necessary, it will save time during student application and registration process.

Example:

Block 4: Contract Payee Type Definition

This table identifies which of the three payee types/entities/parties are valid for the contract. This is the fourth screen of the contract definition.

This screen:

Can have a maximum of three records, one for each payee type namely student, contractee and/or contributing employer.
The student is always a payee type of a contract, regardless of its existence on this screen. If no records exist in this screen it means that the contract has one payee type, the student.
If the contract require payee types contractee and/or contributing employer, they must exist on this screen.
Only payee types defined on this screen can be used in the next three TAB's of the contract definition, namely Contract Payee Type AR Debtor Definition, Contract Rules to Generate AR Invoices for Expenses and Contract Payee Type Transaction Type Definition.
Cannot delete a payee type if the payee type exists in TAB's Contract Payee Type AR Debtor Definition, Contract Rules to Generate AR Invoices for Expenses and Contract Payee Type Transaction Type Definition.

This is a two block screen. The user can only navigate to this block when click on the TAB Contract Payee Type Definition and a contract record is active in block 1. The system will default the contract code in block 1 of this screen and navigate to block 2. An automatic query is performed and all defined payee types for the contract are displayed. The user cannot navigate to any other TAB of the contract definition, use <EXIT> to navigate back to the contract and then other TAB's can be accessed. While in the screen the user may navigate to the first block of this screen and query any other contract code and maintain its payee types.

Field	Type & Length	Description
Contract Number	A4	The contract code of the active contract code when the user moved to this block. Query of any other contracts is allowed.
Description	A40	Display field only. The system will display the description of the contract code.
Payee Types	A1	Valid values for this field are (S)tudent, Contributing (E)mployer or (C)ontractee. A contract can only have up to three of these records (one for each payee type). These payee types identify which parties are active on the contract.
SD Account Type	A4	Enter the SD account type to be used when transactions are generated for the payee type on the student account. The account type field is mandatory for payee types contributing employer and contractee. Each payee type must have a different account type. Duplication is not allowed. Only account types defined for subsystem SD where the Show Y/N indicator on the account type definition in {FSAC-21} is set to no, can be linked to payee types contributing employer and contractee. This field is not mandatory for payee type Student. If entered for payee type student, only account types defined for subsystem SD where the show Y/N indicator is set to Y can be linked. It will also, if entered, override the account type as defined on the fee structure (regardless of where the account type is defined - Curriculum {FSAM-4}, Fee Structure {FSAM-1} or Transaction Type {FCSO-7}). If null, the fee structure account type will be used. A <List of Values> is available and will only list account types defined for subsystem SD where the show Y/N indicator is set to no for payee types contractee and contributing employer and set to yes for payee type student. The user will be able to drill down to the account type definition table {FCSC-21}.
Description	A30	The description of the account type will be displayed.
Agreement Code	A4	Enter the payment agreement to be used when transactions are generated for the payee type on the student account. This is a optional field for the three payee types. Payment agreement codes that can be used here must be valid on the payment agreement table {FSAM-24}. The user will be able to drill down to the payment agreement table {FSAM-24}. If this field is null, the system will use the agreement code as defined in {FSAM-25} or the default agreement code as defined on the system operational definitions {FSAM-1}. Agreement codes for payee types contributing employer and contractee do not have a purpose. It is used because it is mandatory in the SD subsystem. All transactions generated against the contributing employer and contractee, only use the SD subsystem as a stopover before these transactions are transfered to the AR subsystem {FSAO1-10}
Description	A30	The description of the payment agreement will be displayed
Priority	N5	This is a mandatory field. Valid values can only be 1, 2 or 3. No two records for the same contract can have the same priority. The priority is the sequence in which the fee amount will be debited/credited to different payee account types per contract. This priority is critical when amount distribution is used in TAB - Contract Payee Type Transaction Type Definition. If the fee amount (to be distributed) is more than the defined distribution amount in TAB - Contract Payee Type Transaction Type Definition, the residual rule of TAB - Contract Payee Type Transaction Type Definition will be applied. If the fee amount (to be distributed) is less than the defined distribution amount in TAB - Contract Payee Type Transaction Type Definition, the priority rule will be applied. The system will distribute the fee amount, starting with priority 1 up to 3. This means that the payee types with the lowest priorities may have a fee raised that is less than the distributed amount defined or even zero. See distribution examples.

Example:

Block 5: Contract Payee Type AR Debtor Definition

This table identifies the valid debtors in the AR subsystem for a contract and only payee types contractee and/or contributing employer can be linked to a debtor. This is the fifth block of the contract definition.

This screen:

The payee type must be defined in TAB - Contract Payee Type Definition before using it in this block.

A payee type may have more than one debtor linked to the contract.

When a student application or registration is processed, only one debtor per contract payee type can be linked.

A debtor linked as a contributing employer must also be linked to an employer code, in {GCS-22}, before it can be linked when a student application or registration is processed.

Cannot delete a debtor if it was used in any student application or registration.

This is a two block screen. The user can only navigate to this block when click on the TAB - Contract Payee Type AR Debtor Definition and a contract record is active in block 1. The system will default the contract code in block 1 of this screen and navigate to block 2. An automatic query will be performed and all defined AR debtors per payee type for the contract will be displayed. The user cannot navigate to any other TAB of the contract definition, use <EXIT> to navigate back to the contract and then other TAB's can be accessed. While in the screen the user may navigate to the first block of this screen and query any other contract code and maintain the AR debtors for the contract.

If only tuition fees need to be recorded against the contract, the fields Financed by CC and AR Invoice both must be No and the cost centre field must not be entered. Should other expenses also be recorded against the contract, the fields Financed by CC and/or AR Invoice must be Yes and the cost centre must be entered. By completing these fields, additional functionality is available that will allow the user to identify additional costs (other than tuition fee) incurred against a contract. The user will be able to produce a detailed breakdown of all income and expenses that were incurred against the contract.

To identify additional expenses for a specific contract, the contract and debtor code must be linked to a cost centre. If more than one AR debtor code is linked to the contract, a cost centre for each AR debtor code must exist. The cost centre linked to an AR debtor code must be unique throughout all contracts. The same cost centre may never be linked more than once throughout all defined contracts.

The user now has the choice of:
transferring the class fees generated against the contract to the cost centre (Financed by CC) OR
to generate AR debtor invoices for costs incurred against the cost centre (AR Invoice) OR
both - generating additional AR invoices for the contract expenses and/or to transfer the class fees generated against the contract to the cost centre indicated.
These rules can be defined per contract and debtor code (different rules for each debtor linked to the contract)

To transfer costs from the Payroll System to the contract cost centre, {FPRI-1} Split Payroll Costs and {FPRN-9} Generate Cost Splitting Journals can be used.

Field

Type
&
Length

Description

Contract Number

The contract code of the active contract code when the user moves to this block. Query of any other contracts is allowed.

Description

A40

Display field only. The system will display the description of the contract code.

AR Debtor

Enter the AR debtor numbers to be linked to the payee type contractees and/or contributing employers for the contract. If not null, then this value must be equal to a debtor number in the AR system where the debtor is active and not an alias debtor. A <List of Values> is available.
The user will be able to drill down to:

The full description of the debtor
AR Debtor Definition {FARO-21}.
Debtor Service Centre {SDSERC-6}
User access rules apply to these two options.

Payee Types

Valid values are contractee and/or contributing employer and must be defined in TAB - Contract Payee Type Definition.
The same AR debtor number can be used for both payee types.

An invoice/credit note per contract and AR debtor will be transfered to AR {FSAO1-10}.

AR Account Type

Enter the AR account type {FSAC-21}, to be used when an invoice/credit note is generated for the debtor in AR FSAO1-10}. This account type must be for the subsystem AR, active and of AR Category "N - Normal Debtor". A <List of Values> is available.
The user will be able to drill down to:

The full description of the account type
Account Type Definition {FSAC-21}.
User access rules apply to the option.

Financed by CC

Financed by cost centre, if yes, indicates that student fees that were generated against the debtor must be transferred to the cost centre

AR Invoice

AR Invoice if yes, indicates that a second invoice must be generated for the debtor for all expenses that were incurred against the cost centre. Different combinations of Financed by CC and AR Invoice will result in different actions

The cost centre is mandatory if contract financed by cost centre is yes. If entered, it must be a unique value throughout all contracts.

Contract financed by cost centre

If Yes, CC may not be null. AR Invoice may be Y or N

If No, CC may be null or not null

If CC not null, AR Invoice must Y

If CC null, AR Invoice must be N

AR Invoices

If Yes, AR invoices must be created using the rules as defined

If No, AR invoices will not be created

Financed by CC	AR Invoice
N	N	Only one invoice will be generated against the debtor for all student fees that were incurred against the contract and debtor during registration.
N	Y	An invoice will be generated against the debtor for all student fees that were incurred against the contract and debtor during registration, as well as a second invoice for all costs that were incurred against the cost centre linked to the contract and debtor.
Y	N	An invoice will be generated against the debtor for all student fees that were incurred against the contract and debtor during registration. A credit note will be generated at the same time, clearing the debtor and transferring the transaction to the cost centre. No invoice will be generated against the debtor for expenses on the cost centre, thus giving a complete picture of the contract on the cost centre, providing all other expenses are processed against the cost centre
Y	Y	An invoice will be generated against the debtor for all student fees that were incurred against the contract and debtor during registration. A credit note will be generated at the same time, clearing the debtor and transferring the transaction to the cost centre. A second invoice for all costs that were incurred against the cost centre linked to the contract and debtor will also be generated.

Cost Centre

This must be a unique cost centre for each contract and debtor.

Example:

Block 6: Contract Rules to Generate AR Invoices for Expenses

The rules will define when an invoice must be generated. All records for a contract and debtor code must be either specific dates or according to subject credits achieved. If this block is completed, AR invoices will be generated when {FSAO1-12} is run.

The user can choose if invoices must be generated on

Specific dates

AR invoices will be generated on the dates specified by the user

If a record exists where the date is smaller than or equal to system date that is not flagged as generated yet, an invoice must be generated

If more than one record exists where the date is smaller than or equal to the system date, the system will generate one invoice for the maximum date, using the rules on the record with the maximum date
The factor defined on the rule must be in ascending order (cannot be smaller than factor defined on previous date)
All records will be flagged as processed

% of the subject credits achieved

generate invoices when students registered against the contract achieved the % of subject credits as defined by the user

Select the next record not yet generated. Calculate the % of subjects achieved by registered students

If the % achieved is greater than or equal to the % on the record selected, an invoice must be generated

If more than one record, generate one invoice for maximum credits, using rules on maximum record, but flag all records as processed

If no rules are defined, the user will get a warning

It will also define how the invoice must be generated. The user will have a choice between.

Expense budget

the system will use the processed budget against the cost centre and

generate an AR invoice for expense budget * user defined factor
excluding the invoice that was generated when tuition fees were transferred

Actual expense

the system will use all actual expenses that was processed against the contract cost centre and

generate an AR invoice for the actual costs * user defined factor
including the invoice that was generated when tuition fees were transferred

Quantity * unit price

the system will use the quantity and unit price as defined on the contract definition and

generate an invoice for the quantity and unit price defined by the user
excluding the invoice that was generated when tuition fees were transferred

AR invoices will be generated when {FSAO1-12} Generate AR Invoices for Contracts is run
By using the GL report writer, the user will be able to produce a detailed breakdown of all expenses on a consolidation of all the cost centres linked to the contract. The GL report writer will also give the user the functionality to create different types of reports.

Field	Type & Length	Description
Contract Number	A4	The contract number will default from block 5
Debtor Code	N9	The debtor code will default from block 5
Cost Centre	A6	The cost centre will default from block 5
VAT Inclusive / Exclusive	A1	AR invoices will be generated as indicated in this field.
VAT Rate	N3.3	The VAT rate that will be used when AR invoices are generated
Invoice on	A1	Multiple records can exist per contract / debtor code but they must all have the same value. If user chooses to pay on ‘Dates’, all records for the contract / debtor code must be per date. If the user chooses ‘% of Subject Credits Achieved’, all records for the contract / debtor must be defined as ‘% of Subject Credits Achieved’. If ‘Dates’, the next field, ‘Date’, is mandatory and ‘% of Subject Credits Achieved’ cannot be inserted by the user. If ‘% of Subject Credits’, the next field, ‘% of Subject Credits Achieved’, is mandatory and the user cannot enter values for ‘Date’.
Date	DD-MON-YYYY	Must be a valid date between the contract start and end dates. Mandatory if user indicated that the invoice must generate on ‘Dates’ and unique for contract / debtor / cost centre.
%of Subjects Achieved	N4	Must be between 1 and 100. Mandatory if user indicated that the invoice must generate on % of Subject Credits Achieved and unique for the contract / debtor / cost centre.
Generate AR Invoice Based on	A1	The user needs to indicate if the AR invoice must be generated according to the expense budget processed on the cost centre or the actual costs that were incurred against the cost centre or if the quantity and unit price defined on the rule must be used. If expense budget or actual expense, quantity and unit price cannot be entered and generation factor is mandatory. If quantity, generation factor cannot be entered and quantity and unit price is mandatory. All records for the contract / debtor code must be the same – if expense budget, all records for contract / debtor code must be expense budget etc.
Generation Factor	N10	The user needs to indicate what part of the expense must be invoiced. Mandatory if generation of invoice is based on expense budget or actual expense above.
Quantity	N7	Mandatory if generation of invoice is based on quantity. The user must define a quantity that must be invoiced at the specific stage of the contract.
Unit Price	N17.2	Mandatory if generation of invoice is based on quantity. The user must define the unit price that must be invoiced at the specific stage of the contract.
Unit Description	A30	Mandatory if generation of invoice is based on quantity. The user must define the unit price that must be invoiced at the specific stage of the contract.
Date Invoiced	DD-MON-YYYY	Will be updated with system date when invoices are created
Invoice Number	A12	Will be updated with invoice number when invoices are created

Example:

Block 7: Contract Payee Type Transaction Type Definition

This table identifies the distribution (percentages / amounts) payable per contract, payee type and fee transaction type. This is the sixth block of the contract definition.

This screen:

The payee type contractee/contributing employer must be defined in TAB - Contract Payee Type Definition before using it in this block.

Only transaction types defined in the fees structure {FSAM-1} for all events and financial code structure {FCSO-7} event PD can be used in this block.

If the transaction type, describe above, is not define in this block it will be 100% for the payee type student SD account.

To define a premium/discount on a transaction type (TAB - Contact Premium/Discount Transaction Type Definition) it must have a record in this block for the contract.

Each transaction type can be distributed between any combination of the contract payee types.

If percentage distribution then all records with the same transaction type and rule indicator must add up to 100%.

This is a two block screen. The user can only navigate to this block when click on the TAB Contract Payee Type AR Debtor Definition and a contract record is active in block 1. The system will default the contract code in block 1 of this screen and navigate to block 2 and do an automatic query of all defined AR Debtors per payee types of the contract. The user cannot navigate to any other TAB's of the contract definition, use <EXIT> to navigate back to the contract and then other TAB's can be excess. While in the screen the user may navigate the the first block of this screen and query any other contract code and maintain its AR debtors.

Field

Type
&
Length

Description

Contract Number

The contract code of the active contract code when the user have moved to this block. Query of any other contracts is allowed.

Description

A40

Display field only. The system will display the description of the contract code.

Payee Type

Valid values Student, Contractee or Contributing Employer. Each transaction type can be split into these three payee types depending on the contract rules. If the value is Contractee and/or Contributing Employer then it must be defined in TAB - Contract Payee Type Definition.

SD Trans. Type

Only transaction types defined in the fees structure {FSAM-1} for events 03, 05, 07, 13 and financial code structure {FCSO-7} event PD can be used in this field. A <List of Values> is available.
The user will be able to drill down to:

The full description of the debtor
Financial Debit {FSAM-1}.
Transaction Type Definitions {FCSO-7}.

User Access rules apply to the two options.

Ind and
Subject Code

A1
A7

"Ind" is rule indicators, valid codes and rules are:

Functionality has been built in, to enable the user to set up different discount/premium structures for subject registrations (Events 07 and 17), based on whether a student has been previously enrolled for this subject.

"F" is the default for previously enrolled subjects,
"P" can be used to override individual subjects previously enrolled.
"D" is used for subjects not previously enrolled as a default.
"E" is used to override this per subject.

If no distinction is needed according to "previously enrolled", only indicator "D" is to be used.

FOR the processing of Events "07" and "17"
Test is performed to see if a Student has been previously enrolled for this Subject is as follows:

For Student and Subject IAHSUB is read where IAHDATE < than the system date and is not canceled.
if found, then indicator will be set to a "P"
Then a check is performed to see if infact, a "P" indicator record exists for the Contract, Transaction Type, Payee Type and Subject. If not, the indicator will be reset to "F", and if no "F" record exists for the contract, Transaction Type and Payee type, it will be treated the same as if it was not previously enrolled.
When the Student has not been previously enrolled, the default indicator will be "E", but if a record does exist for the contract, Payee Type, Transaction Type and Subject, the Indicator used will be set to a "D". If no "D" record is found for the contract, Transaction Type and Payee Type (Nothing is therefore set up on the table as shown in the image below), the whole fee will be charged against the student payee type only, and, if no further 'splitting" or discount/premium calculation will be performed.

IF NO events "07" or "17"

Indicator is defaulted to a "D".
If nothing is setup on table FIW as shown in image below, no contract processing and whole fee transaction will be generated against the student payee type only.

D - First Time/No Exception

If the transaction type is from event 03, 05 or PD then "D" is the only rule indicator that the user can use. The system will default ‘XXXXXXX’ into the subject field, as event 03, 05 or PD does not relate to subjects.

If the transaction type is from event 07 the rule indicator is "D" then it for subject with the following rules:

The system will default ‘XXXXXXX’ into the subject field and stands for: all subject in the fee structure that use the SD transaction type of this record. also known as the default distribution.
This rule for an SD transaction type must exist before rule indicators "E" and "F" ("F" must exist before "P") can be used for the same transaction type.
It is for first time enrollment on the subject (Student was not previous enrolled for the subject)
If rule "F" or ("E" or "P" for a specific subject) does not exist for the SD Transaction Type then rule "D" will be used for second time enrollment or more, for the subject.

E - First Time/Exception

Only for event 07 SD transaction types and rule "D" must exit for the SD transaction type.
It is for first time enrollment on a specific subject (Student was not previous enrolled for the subject) and the distribution in not the same as the rule "D"
If rule "F" or ("P" for a specific subject) does not exist for the SD Transaction Type then rule "E" will be used for second time enrollment or more, for the subject.
Enter a valid subject code into the subject field:

This must be a valid Subject {SACADO-10} for the Qualification {SACADO-1}.
The system will allow Subject {SACADO-10} linked to the Qualification {SACADO-1}. in the Curriculum in {SACADO-17} for the academic year where the contract start and end dates match the block start and end dates in Census Dates {GOPS-1}.

F - Second Time/No Exception

Only for event 07 SD transaction types and rule "D" must exit for the SD transaction type.
The system will default ‘XXXXXXX’ into the subject field and stand for: all subject in the fee structure that use the SD transaction type of this record. also known as the default second time distribution.
Will be used if the student enroll for a second time for the subject.

P - Second Time /Exception

Only for event 07 SD transaction types and rules "D" and "F" must exit for the SD transaction type.
It is for second or more time enrollment on a specific subject and the distribution is not the same as the rule "F".
Enter a valid subject code into the subject field:

a different view of this rule indicators process sequence:

If an SD transaction type is not defined in this screen for the contract
then

The student payee type will be debited/credited with the full fee structure amount.

else if not first time subject enrollment and the subject and SD transaction type is linked to the rule "P"

then

The payee types will be debited/credited using the rule "P" distribution.

else if not first time subject enrollment and the subject and SD transaction type not linked to rule "P", but the SD transaction type is linked to the rule "F"

then

The payee types will be debited/credited using the rule "F" distribution.

else if the subject and SD transaction type is linked to the rule "E"

then

The payee types will be debited/credited using the rule "E" distribution.

else

The payee types will be debited/credited using the rule "D" distribution.

Rules of fields Payable % and Amount:

Per Contract, SD Transaction Type, Rule Indicator and Subject Code combination you may either use Payable % or Amount. The system will not allow the user to use both in the combination.

Payable %

N5.2

This field identifies which portion of the fee (as retrieved from the fee structure) is payable by which payee type for the combination. If not null, then the value must be between .01 and 100.00. The system will validate the the payable % for the combination add up to 100%. See distribution examples.

Amount

N17.2

This field identifies which amount (also called the distributed amount) of the fee (as retrieved from the fee structure) is payable by which payee type for the combination.

If the fee amount is more than the distributed amount then the residual rule of combination will be applied.
If the fee amount is less than the distributed amount then:

The system will distribute the fee amount, according to the distributed amount, starting with priority 1 up to 3 . This meant that some of the payee type priorities may have a fee raised that is less than distributed amount or even zero.

No validation can be performed at setup time.
If amount is not null then the this value must be greater than zero. See distribution examples.

Pay Residual Amount

Within the combination only one payee type must be identified as being responsible for the remainder of the fee after the distributed between the payee types of the combination.
Valid values are :

Checked

Will received the residual amount if exist during distribution.

Not Checked

Will not receive more than what was allocated in payable % or amount.

See distribution examples.

Example:

Block 8: Contract Premium/Discount Type Transaction Definition

This table identifies the premium or discount per transaction type that can be charged on the student account under this contract. This is the seventh screen of the contract definition. See distribution examples.

Field	Type & Length	Description
Contract Number	A4	The contract code of the active contract code when the user have moved to this block.
Description	A40	The description of the active contract code when the user have moved to this block.
Ind	A1	The user can indicate a different discount / premium percentage for a subject if the student is enrolling for that subject for the second time. Valid values are ‘D’, ‘E’, ‘F’ or ‘P’. ‘D’- Default value for subjects that do not have an exception – first time enrollment. All subjects that are not defined with an indicator ‘E’ will follow this rule. ‘E’- Subjects that do have an exception – first time enrollment. If a subject does have an exception rule, the user must specify the subject code in the next field. A different % or amount can now be specified for this subject code. ‘F’- Default for subjects that do not have an exception – not first time enrollment. All subjects that are not defined with an indicator ‘P’ will follow this rule. ‘P’- Subjects that do have an exception – not first time enrollment. If a subject does have an exception rule, the user must specify the subject code in the next field. A different % or amount can now be specified for this subject code.
Subject Code	A7	This value will default to ‘XXXXXXX’ if the indicator in the previous field is set to ‘D’ or ‘F’ and the user will not be able to update this value. If the indicator in the previous field is set to ‘E’ or ‘P’, the user will have to specify the subject code for which an exception exists.
SD Trans. Type	N4	Enter a valid transaction type for subsystem SD. This field identifies the transaction type (as retrieved from the fee structure) for which a premium or discount transaction must be generated. Only transaction types used in block 6 of the contract definition may be entered here.
Description	A30	The description of the transaction type selected above will be displayed.
Discount/Premium %	N5.2	This is a numerical value that indicates a percentage. Can be a negative or a positive value. This field indicates whether the value retrieved from the fee structure must be discounted with or whether a premium must be added to the individual transactions. The original value and the second calculated value will be written to the database as two separate transactions. A negative amount indicates a discount and a positive amount indicates a premium. If not null, then the range is .01 up to 99.99 positive or negative
SD Trans. Type for Discount/Premium	N4	This is a mandatory and the value entered must be a valid transaction type for subsystem SD. This is the transaction type that will be used for the additional transaction. This transaction uses the value as retrieved from the fee structure type to apply the discount or premium. The user will be able to drill down to the transaction type definition table {FCSO-7}.
Description	A30	The description of the transaction type selected above will be displayed

Example:

Processing Rules
	No special processing rules

Date	System Version	By Whom	Job	Description
13-Dec-2006	v01.0.0.0	Charlene van der Schyff	t133246	New manual format.
04-Apr-2007	v01.0.0.0	Amanda Nell	t133246	Images for manual
16-Apr-2009	v01.0.0.1	Ernie van den Berg	t157364	Review the manual.
01-Mar-2010	v02.0.0.0	Christel van Staden	t158686	Add generation of AR invoice for expenses
17-Feb-2011	v02.0.0.1	Bea Swart	t163477	All Offering Types of the Subject for the Contract's Student Type should be active on {GCS-5} TAB - Offering Type - Student Type Link. T165727
07-Apr-2011	v02.0.0.2	Christel van Staden	t173832	Correct links for images
01-Sep-2011	v02.0.0.3	Magda van der Westhuizen	t165835	Insert new field 'Communication'.
30-Jan-2012	v02.0.0.4	Christel van Staden	t180311	Add event 13 to be included for distribution between entities of contract
09-dec-2014	v03.0.0.0	Charlene van der Schyff	t202085	Added Clarity for:Functionality has been built in.
11-Feb-2016	v04.0.0.0	Clinton Naidu	t200827	Replaced events 03, 05, 07 & 13 with all events in block 7
26-Jun-2019	v04.1.0.0	Frans Pelser	t237245	Change SACAD-15 to SACADO-17