What this module is for
Manage fee heads, structures, generation, ledger, collections, receipts, reminders, late fees, and reports.
Prerequisites
- Academic session and classes configured
- Fee permissions assigned
Main screens
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 checkpoints
- 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.
Field guidance
Use clear fee heads for tuition, admission, exam, transport, hostel, or other school-approved charges.
Assign structures to the correct academic session and class so dues are generated for the intended students.
The ledger is the authoritative place to review generated dues, paid amounts, balances, receipts, and adjustments.
Enter only valid payment amounts and confirm the selected payable items before saving the receipt.
Configure receipt text, signatures, numbering, and print options before production collection begins.
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.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.