Loading page
Fee structures, bulk vouchers, instalments, concessions, fines and reconciliation — with a defaulter list that is current enough to act on.
Fee collection is where most education institutions lose money quietly. Not through fraud, but through friction: vouchers generated late, concessions applied verbally and never recorded, bank deposits reconciled by eye, and a defaulter list that is a fortnight out of date by the time anyone reads it.
A fee system fixes that by making each step an ordinary record. Structures are defined once, vouchers generate in bulk, every concession has an authoriser, and reconciliation compares what the bank received against what you issued.
Session-versioned fee structures per class or programme, with bulk voucher generation and due dates.
Part payments, instalment plans, scholarships and concessions with a recorded authoriser.
Gateway or bank challan collection with automatic closure of paid vouchers where integrated.
Bank statement import matched against issued vouchers, with exceptions flagged rather than absorbed.
SMS and WhatsApp dues reminders driven from the live defaulter list, not a stale export.
Collected versus billed by class, campus and head, plus ageing on outstanding fees.
Each stage is auditable, which is what makes the totals trustworthy.
Online payment is only useful if it reconciles automatically. Where a gateway or bank integration is available, paid vouchers close themselves and the student ledger updates without anyone retyping a transaction reference.
Where the practical route is a bank challan, the system generates it with a scannable reference and imports the bank's daily statement to match deposits, flagging what does not reconcile rather than silently absorbing it.
The awkward cases are what break spreadsheet-based fee tracking: a student leaves mid-session, a concession is granted retrospectively, a duplicate payment arrives, a voucher was issued at the wrong structure. All of those are handled as recorded adjustments with an authoriser, so the closing balance can always be explained.
Straight answers, including the ones that rule us out.
The pages people read next, and the products that connect to this one.
The systems we build most often, each described by the workflow it manages rather than by a feature list — because the workflow is what decides whether it fits.
Read moreAdmissions, attendance, timetables, exams, results, fees and staff records in one system — with a parent portal so the office stops fielding the same calls.
Read moreAttendance, results, fee status, timetables, notices and documents — online, per student, so the office stops answering the same three questions by phone.
Read moreBatches instead of classes, monthly or course-wise fees, teacher payouts and attendance — built for coaching centres, institutes and training academies.
Read moreSchool, college and academy systems, student and parent portals, fee management and admissions — built so the office still uses them in month eight.
Read moreSchool software is abandoned more often than replaced, and almost always for the same reason: daily entry is slower than the paper it replaced.
Read moreDescribe your operation and we will come back with a written scope, a fixed price and a delivery date.