Ask most school platforms how fees get paid and the answer assumes a card or a bank debit. For a huge number of schools, that assumption quietly breaks. Fees arrive as cash at the front desk, as bank transfers a parent made this morning, or against a printed challan carried to a branch. A product that treats those as edge cases makes the accountant's job harder, not easier.
Build for how money actually moves
Qalamaly's fee engine starts from the real behaviour:
- A cash kiosk for the front desk — search a student, take payment, print a receipt, and reconcile at cash-close.
- Bank-transfer claim verification: a parent submits proof, an accountant verifies it against the statement, and the ledger updates.
- Challan, receipt and statement PDFs — branded per campus, generated on the server.
- CSV and bank-statement imports with a staging queue, so a day's transfers reconcile in minutes instead of being keyed by hand.
A ledger you can trust
Underneath it all is an append-only student ledger — every charge, credit and payment is a posting, never an in-place edit. A balance is the sum of its history, which means it's auditable by construction. For a school owner who has been burned by a spreadsheet, that's not a technical nicety; it's the reason to switch.
Gateways come later, reality comes first
Online card gateways are useful, and they're on the roadmap. But leading with them — and treating cash and challan as afterthoughts — gets it backwards for a lot of schools. We built the messy, physical, real-world side first, because that's where the money actually moves today.