school erp · 8 min read
School Fees Collection Software: What Accounts Teams Need After the Counter Closes
Fee season is not a dashboard problem. It is cash, UPI, concessions, and a parent who swears they paid. Software only helps if the receipt and the defaulter list tell the same story.
Updated 24 September 2026
The 8 a.m. queue is a software requirements document
Stand in a Lucknow school office in April. Parents hold cash and UPI screenshots. The clerk has three fee heads on a paper slip, a concession the principal approved verbally, and a sibling discount that exists only in one notebook.
If your fees software cannot print a receipt that matches that mess—tuition, transport, exam, late fee, concession—staff will keep the notebook. The software becomes a decoration used for inspections.
Kiash Infotech’s Fees Management System is built around that counter, not around a generic “payments module” slide.
Fee heads, not a single number
Schools do not charge “fees.” They charge a bundle that changes by class, stream, optional subjects, and whether the child takes the bus. One blended amount is how disputes start at the gate.
The item master should let accounts add a head without calling a developer. Transport routes especially: the amount changes when a child shifts stop, and it must not silently alter last term’s paid receipt.
Concessions need a reason and an approver. “Madam said 20% off” with no log is how two children in the same section pay different dues and nobody can explain why in July.
UPI, cash, and the screenshot problem
Online collection is not “a payment gateway.” It is a match between a UTR and a student. If parents pay the school UPI ID from a personal chat, your software still needs a way to book that money against the right child—or you will chase ghosts at month-end.
Cash will not vanish. Receipts should work offline-enough for a power cut, then sync. Accounts should see cash vs online in a daily close, the same way a shop closes a till.
Refunds and bounce-backs need a status. Silently deleting a receipt to “fix” a mistake destroys the audit. Reverse it, with a name and a time.
Defaulter lists that teachers will not be asked to collect
The useful report is not total collection. It is who is pending, by class, with phone numbers, before the next PTM. If generating that list takes an Excel export and a VLOOKUP, you do not have fees software.
Parent apps that show dues cut the “how much do I owe?” calls. They do not replace the office. They stop the office from being a calculator.
When a school is ready, the same student record should sit inside a full school ERP—attendance, exams, notices—so fees is not an island. Until then, a focused fees product is better than a half-configured 50-module suite.
How to trial this without disrupting term
Pick one class or one fee cycle. Migrate that set of students, run parallel receipts for a week, and compare the defaulter list to the register. If they disagree, stop and fix mapping—do not “go live for the whole school on Monday.”
Bring last term’s concession list and transport roster to the demo. Those two files expose whether the product is serious.
See Kiash Infotech’s Fees Management System, or the full School Management Software when you want ERP. Call +91 956 571 5557 and ask to walk through a sample class with your actual heads.
Questions people ask
- Can school fees software handle cash and UPI together?
- It should. Receipts must record the mode, match a UTR to a student when parents pay online, and still print for cash at the counter. A gateway demo without a daily cash close is incomplete.
- Is a fees-only product enough, or do we need full school ERP?
- Fees-only is enough if the pain is collections and defaulter lists. Take full ERP when you also want attendance, exams, and parent notices on the same student record.