Running two branches feels manageable. Three starts to stretch things. By four or five, the operational overhead of fee collection alone can consume a significant part of the week — because the information that should be in one place is spread across multiple files, multiple people, and multiple informal systems.
This is the multi-branch fee problem. Not the payment technology — that part is largely solved. The visibility and coordination problem.
What multi-branch visibility actually means
When we talk to directors who run multiple branches, the most common request is not "help me collect fees." They can collect fees. The request is: "show me what is happening across all branches in one place."
Specifically, they want to know:
<strong>Collection rate by branch.</strong> Is Kondapur at 90 percent collection this month while Kukatpally is at 72 percent? That difference has a cause — a coordinator behaviour difference, a batch-level issue, a concentration of late-paying families — and it is invisible unless you can compare branches side by side.
<strong>Outstanding by student, cross-branch.</strong> If a family has students at two different branches — which happens frequently in well-established academies — their combined outstanding should be visible together. Managing them as separate students in separate files means two separate coordinators potentially sending conflicting messages to the same family.
<strong>Pending follow-up, total.</strong> How many students across the entire institute have outstanding fees right now? Not by branch, but total — so you can assess the magnitude of the problem in one glance.
<strong>Fee revision impact.</strong> If you raise fees by ₹200 next term, what is the projected revenue impact across all branches? This question requires consolidated data to answer quickly.
How most multi-branch institutes handle this today
The most common approach is a master Excel that the director or senior coordinator maintains — pulling numbers from branch-level files or WhatsApp updates from each branch coordinator, and manually constructing a combined view.
This works. It takes two to four hours every week, introduces human error at each update, and is always slightly out of date. The branch coordinator who forgot to update their file last Thursday means the master view is wrong.
Some institutes use a shared Google Sheet. This helps with real-time visibility but does not solve the data entry burden at the branch level — someone still needs to update it, and if payment data and reminder data are both maintained manually, the workload is similar.
What consolidated fee management looks like in Feezy
Feezy treats branches as a first-class concept. When you set up a multi-branch institute through Spark, you define each branch as a separate location under the same organisation. Students, batches, and fee structures are configured per branch, but the director sees all of them in one dashboard.
The branch-level roll-up on the dashboard shows:
Total collected vs total outstanding per branch
Collection rate percentage per branch
Number of students with outstanding fees per branch
Month-on-month trend per branch
Below the roll-up is the full student list — filterable by branch, by outstanding status, by batch. A director looking for all students with fees more than 15 days overdue, across all branches, gets that list in one filter.
Coordinators at each branch have access to their own branch view — they see only their students, manage their own follow-ups, and cannot see other branches. The director sees everything.
What this does to coordination overhead
The biggest operational change is that coordinators stop needing to report upward. The director does not need a WhatsApp update from each branch every Monday because the data is already in the dashboard.
This removes a layer of coordination that consumes time at both ends — the coordinator compiling the update and the director reading and processing it. Multiply that by four branches and you recover several hours a week.
It also removes the inconsistency in follow-up that comes from each coordinator running their own informal reminder system. Pulse sends reminders based on the same logic for every branch — same timing rules, same tone escalation, same stopping criteria. Parents across all branches get a consistent experience, regardless of which branch their child attends.
For institutes considering a second branch
The operational cost of a second branch is typically underestimated. The teaching overhead — more space, more teachers, more scheduling — is visible in advance. The fee collection overhead often is not.
If your current fee process works because you personally know which parents need following up, that knowledge does not replicate automatically when you open a second location. The coordinator you hire knows their branch — not the patterns across the whole institute.
Setting up consolidated fee management before you open the second branch, rather than after, is the lower-stress path.
<em>Praveen GSVN is Co-Founder at Feezy, built by ConvertEdge Tech in Hyderabad.</em>