Fee workspace
See collections and outstanding fees together.
Review fee totals, pending installments, and recent payments in the school’s fee workspace.
Edvora Fees and Payments
From fee setup to a complete student ledger.
Edvora connects fee structures, installments, collections, receipts, payment history, and role-aware visibility around the same student record.
Fee lifecycle
Structure, collect, receipt, and continue.
Select a stage to inspect the connected progression. Nothing advances automatically, and every stage remains visible.
CONFIGURED
Define the school fee foundation.
Fee heads and class-section plans establish applicable amounts in the academic-session context.
Record continuity
Student · Academic session · School
Inside Edvora
A closer look at the workspace.
Real product screens, shown with sample school data. Open a full view to explore the details.
Fee structure and governance
Start with the school’s academic fee context.
Fee heads and versioned class-section plans define applicable amounts for an academic session before obligations are assigned to students.
01
Fee heads
Use active school fee categories as the building blocks.
02
Class plans
Attach amounts to class-section plans in the academic session.
03
Student assignment
Apply plan items or controlled individual fees to the student.
04
Installment policy
Generate one, two, or four installments with due dates and balances.
Collection workspace
Collect against the installment, not a disconnected entry.
Manual collection records the amount, mode, optional reference, note, and collector. Online payment appears only when the school’s payment route is configured.
Sample student ledger
Illustrative amounts · sample data
Installment 1
Paid
Paid₹12,500
Balance₹0
Installment 2
Partial
Paid₹7,500
Balance₹5,000
Installment 3
Pending
Paid₹0
Balance₹12,500
Receipt and ledger
Preserve every recorded payment chronologically.
The payment creates a receipt record, updates installment and fee balances, and remains available in student history and protected PDF outputs. Admission financials retain their transfer context.
Receipt
Unique receipt number, paid date, mode, amount, collector, and optional reference.
Student ledger
Fee heads, discounts, installments, payments, paid amount, and remaining balance.
Documents
Scoped receipt, fee statement, and fee certificate data with school branding.
Role-aware financial context
Finance
Record collections, review balances, and open protected receipts.
Office
Use student and admission context while supporting fee operations and reports.
Leadership
Review collected, outstanding, pending, and overdue operational context.
Parent
See linked children’s installments, balances, payment history, and receipts.
Student
Access their own fee documents and history when student access is enabled.
Controls and safeguards
Scoped records
Fee data is constrained to the school, student, and relevant academic context.
Permission-aware work
Fee setup, collection, receipt access, printing, and reporting have defined role access.
Locked foundation
After initial save, the school installment schedule stays fixed; the admission-fee suggestion remains separately editable.
Balance protection
A collection cannot exceed the current installment balance or target a fully paid installment.
Collector trail
Recorded payments can retain the collecting user, payment mode, date, receipt, reference, and remarks.
Protected documents
Receipts, statements, and certificates resolve through scoped document services.
Connected School OS outcome
One financial record, carried through the school.
Admission payment, student fees, installments, receipts, family access, reporting, and leadership visibility continue from shared school and student context.