Student Payment - Zayeen Documentation

Used By

Operational users and finance team

Data Type

transaction

Search Keys

Code, Division

When to Use This Form

When users need to create, review, or update Student Payment.
When the transaction needs to become part of reports, balances, journals, or the next workflow.
When existing data needs correction because policies, accounts, prices, contacts, or operating rules have changed.

Before You Start

Make sure the user has access to this menu and the related reference data has already been prepared.
Check required fields first, especially codes, names, dates, accounts, customers, suppliers, products, divisions, or departments.
If the form uses active status, confirm the status before saving so the data appears in the correct selections.

Workflow

Open Student Billing / Billing Transactions / Student Payment.
Create a new record, or select an existing record when the data needs to be corrected.
Fill in the required fields and complete supporting information that helps search, reporting, or transaction processing.
Review detail lines, totals, payment information, taxes, discounts, and notes before saving.
Click Save. If the application shows a validation message, follow the message until the data is saved successfully.

Key Fields

Field	User Explanation	Status
Code `id`	Unique code used to identify Student Payment. Use a consistent pattern so users can search and sort the data easily.	Required
Division `division`	Business unit or branch related to this record. Choose the correct division before saving.	Required
Invoice `jtid`	Invoice stores information needed by Student Payment. Fill it in according to the company data standard.	Required
Transaction Date `transdate`	Date used for recording, filtering, or reporting this data. Check the period before saving.	Required
Subclass `schoolsubclass`	Subclass stores information needed by Student Payment. Fill it in according to the company data standard.	Required
Student ID Number `schoolstudent`	Unique code used to identify Student Payment. Use a consistent pattern so users can search and sort the data easily.	Required

Details and Relationships

If the form contains detail lines, each line affects totals, balances, stock, journals, or follow-up documents.
Audit fields are filled in automatically by the application and help support teams trace changes.

After Saving

The transaction can be used by reports, audit checks, and the next related process.
Changes are normally used for new activity. Historical documents remain available for review.
If required data is incomplete or inconsistent, the application rejects the save and shows a validation message.

Common Issues

Data cannot be saved: complete required fields and read the validation message shown by the application.
Data does not appear in selection or search: check active status, access rights, filters, and the search keyword.
Duplicate code or name: use the existing record when it should be corrected, or use a different code for a new record.
Report values do not match: recheck reference data, accounts, dates, transaction status, and related filters.

Available Fields

The list below summarizes the fields available in this form. Field labels follow the English UI language file used by the application.

Field	User Explanation	Status
Code `id`	Unique code used to identify Student Payment. Use a consistent pattern so users can search and sort the data easily.	Required
Division `division`	Business unit or branch related to this record. Choose the correct division before saving.	Required
Invoice `jtid`	Invoice stores information needed by Student Payment. Fill it in according to the company data standard.	Required
Transaction Date `transdate`	Date used for recording, filtering, or reporting this data. Check the period before saving.	Required
Subclass `schoolsubclass`	Subclass stores information needed by Student Payment. Fill it in according to the company data standard.	Required
Student ID Number `schoolstudent`	Unique code used to identify Student Payment. Use a consistent pattern so users can search and sort the data easily.	Required
Name `schoolstudentname`	Name shown in selections, transactions, and reports. Use wording that is clear for daily users.	Required
Auto Pay All Payments `btnimport`	Amount used in calculation and reporting. Review the value before saving.	Required
Student Payment Input `schoolstudentpaymentdetail`	Amount used in calculation and reporting. Review the value before saving.	Optional
Payment Type `paymenttype`	Amount used in calculation and reporting. Review the value before saving.	Required
onlinepaymentspaynow `onlinepayments`	Amount used in calculation and reporting. Review the value before saving.	Optional
Total Payments `totalpayment`	Amount used in calculation and reporting. Review the value before saving.	Optional
Last Updated `updatetimestamp`	Audit timestamp filled in automatically by the application.	Optional
Type `kind`	Type stores information needed by Student Payment. Fill it in according to the company data standard.	Optional
QR Code `btnqrcode`	Unique code used to identify Student Payment. Use a consistent pattern so users can search and sort the data easily.	Optional
Received `accepted`	Received stores information needed by Student Payment. Fill it in according to the company data standard.	Optional
Created By `usercreate`	Audit information filled in automatically when the record is created.	Optional
Updated By `useredit`	Audit information filled in automatically when the record is updated.	Optional

Menu Location

Student Billing / Billing Transactions / Student Payment
/form/schoolstudentpayment