Individual challans
Create student-specific fee challans with tuition, concession, billing month and due date.
Manage the school fee cycle with individual and class-wide challans, payment entry, printable documents and financial visibility.
The accounts team selects a billing month and due date, generates a student challan or a class-wide batch, and prints bank-style vouchers. When a payment is received, staff record the amount and reference, then issue a printable receipt and review any outstanding balance.
For accountants: connect challans and payment records. For leadership: understand outstanding dues without relying on disconnected registers.
These are concrete functions represented in the inspected ERP interface—not a list of aspirational integrations.
Create student-specific fee challans with tuition, concession, billing month and due date.
Generate fee challans for enrolled students in a selected class.
Open printable three-part bank fee voucher layouts.
Record received amounts, payment method, reference and notes against a challan.
View and print receipts associated with recorded payments.
Filter challans by status and review paid, outstanding and overdue amounts.
Prepare billing → Issue challans → Record payment → Print & reconcile
Select the billing month, due date and relevant student or class; confirm the fee amount and concession.
Create an individual challan or generate a class-wide batch, then print the available three-part bank-style vouchers.
When money is received, enter the amount, method and transaction reference against the relevant challan.
Print the receipt and review paid, unpaid or overdue fee records to identify remaining balances.
A realistic operational example, showing the sequence of work and the information staff can review.
The accounts office is issuing challans for a class and tracking payments received.
Choose the month and due date, then generate individual or bulk challans.
Print the three-part fee challan for the relevant student.
Enter received amount, payment method and reference, then print a receipt.
The accounts team can review the challan and its recorded payment status; this is not an online payment gateway.
Understanding the records behind a workflow helps a school plan implementation and staff responsibilities.
Student; billing month; due date; tuition amount and concession
Challan; payment amount; method; reference; receipt
Paid, outstanding and overdue status; collection and dues views
Representative fields and actions drawn from the inspected application screens. Availability depends on role and school configuration.
School administrators, accountants and authorised staff. The actual controls visible depend on account permissions and school entitlements.
A live payment gateway is not verified. The system supports manual recording of received payments.
No. The inspected reminder action is simulated, so external delivery is not advertised.
Yes. Printable bank-style vouchers and payment receipts are present.
A fee reminder button currently simulates WhatsApp/SMS notifications. Live reminder delivery and payment gateway processing are not claimed.
Tell us about your school's needs and we'll discuss the workflows and modules that matter most.