Exams, Fees & Reports

Finance / Fee

Manage fee heads, structures, generation, ledger, collections, receipts, reminders, late fees, and reports.

Audience: Accountants, admins, and authorized fee users
Last reviewed: September 2, 2026

Overview

Manage fee heads, structures, generation, ledger, collections, receipts, reminders, late fees, and reports.

Before you start

Academic session and classes configured
Fee permissions assigned

Main screens

Fee Heads Fee Structures Student Ledger Payment Collection Receipts Reports Receipt Settings

Step-by-step workflows

Configure fees

Create fee heads.
Create fee structures for classes/sessions.
Generate or assign fees to eligible students.

Collect payment

Open student ledger or collection screen.
Select payable items.
Record payment using the normal fee flow.
Generate receipt and review reports.

Operational detail

Permission requirements

Fee setup, fee generation, collection, receipt view, receipt settings, and fee reports require separate permissions.
Module integrations such as transport or hostel must not modify fee tables directly; they should follow the approved fee integration boundary.
Receipt and ledger actions are server validated even when opened from a student profile shortcut.

Fee head

Use clear fee heads for tuition, admission, exam, transport, hostel, or other school-approved charges.

Fee structure

Assign structures to the correct academic session and class so dues are generated for the intended students.

Student ledger

The ledger is the authoritative place to review generated dues, paid amounts, balances, receipts, and adjustments.

Collection amount

Enter only valid payment amounts and confirm the selected payable items before saving the receipt.

Receipt settings

Configure receipt text, signatures, numbering, and print options before production collection begins.

Reports

Use collection, due, receipt, and class-wise reports to reconcile finance activity after daily collection.

Validation and system feedback

The selected structure must match the school, session, class, and applicable student set.
Amounts must be positive and cannot exceed the rules enforced by the fee collection screen.
Receipt generation should happen only through the normal fee collection workflow.
Direct database changes to fee ledgers, receipts, or payments are outside supported use.

Common mistakes to avoid

Generating fees for the wrong academic session.
Collecting payment before reviewing the student ledger balance.
Trying to integrate another module by altering fee tables directly.
Printing receipts before receipt settings and signatures are reviewed.

Safe use

Keep documentation and support privacy-safe

These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.

Generating fees for the wrong academic session.
Collecting payment before reviewing the student ledger balance.
Trying to integrate another module by altering fee tables directly.
Printing receipts before receipt settings and signatures are reviewed.