How a 6-Campus CBSE Chain Closed Fee Gaps and Fixed Payroll with Zoho
Challenge
Six campuses ran fee collection and staff payroll on disconnected spreadsheets.
Solution
Zoho People unified HR across campuses; Zoho Books automated fee invoicing and reminders.
Tools
Zoho PeopleZoho Books
Case Study · K-12 Education
How a 6-Campus CBSE Chain Closed Fee Gaps and Fixed Payroll with Zoho
Industry
K-12 Education, CBSE
Revenue Band
₹8–14 Cr annual fee collection
Company Size
180–240 staff across campuses
Tools Deployed
Zoho People, Zoho Books
The Problem
Running six campuses from a single administrative office sounds manageable until each campus keeps its own attendance register, its own fee ledger, and its own copy of the salary sheet. By the time figures were consolidated at month-end, reconciliation alone consumed three to four working days, and discrepancies between campus records were routine.
Fee Leakage at Scale
Each campus tracked outstanding fees in its own spreadsheet, with no shared visibility. Follow-up reminders were sent manually and inconsistently, allowing balances to age past 90 days before the central accounts team even knew they existed.
Fragmented Attendance and Leave
Teaching and non-teaching staff attendance was recorded on paper at each site and keyed into a central spreadsheet after the fact. Leave approvals went through WhatsApp messages, creating no auditable trail, and payroll inputs were routinely contested by staff who disputed the counts.
ESI and PF Compliance Risk
With headcount spread across campuses and no unified employee master, ESI and PF contribution calculations were done manually each month. Errors in gross salary inputs or new-joiner onboarding dates created compliance gaps that carried financial penalty risk under ESIC and EPFO audit.
The Solution Stack
Two Zoho products replaced the spreadsheet layer entirely: one for people, one for money. Both were configured to treat the group as a single entity while still allowing campus-level reporting.
Single employee master covering teaching, non-teaching, and administrative staff, with campus as a department attribute
Biometric-integrated attendance sync replaced paper registers; exceptions flagged automatically for campus coordinators
Leave requests and approvals moved to the self-service portal, creating a timestamped audit trail for each transaction
Monthly payroll generated from attendance actuals, with ESI and PF contributions calculated against the correct gross figures and exported in statutory formats
Chart of accounts configured for fee heads with GST applicability flags
Student contacts and outstanding balances migrated from campus spreadsheets
Automated reminder workflows tested end-to-end with dummy accounts
Payment gateway connected; bank feed reconciliation rules set for each campus account
4
Parallel Run and Handover Weeks 9–11
First live payroll cycle run in Zoho People alongside manual check; variances resolved
Campus admins trained on fee enquiry, receipt reprint, and overdue escalation workflows
Finance manager trained on cross-campus dashboards and monthly closure reports
Handover sign-off after second live payroll cycle with no manual reconciliation required
Results
By the end of the second full term on the new system, overdue fee balances had fallen substantially and monthly payroll processing had moved from a multi-day exercise to a same-day task. The compliance risk from ESI and PF calculation errors was fully resolved once the employee master was cleaned and locked into Zoho People. School groups facing similar challenges can explore Zoho implementation services for education to map out the right configuration for their structure.
67%
Drop in fee collection gaps across campuses
5×
Faster monthly payroll processing
₹11L
Annual ESI/PF penalty risk eliminated
Outstanding Fee Balance by Aging Bucket: Before vs. After (% of total dues)
Monthly Payroll Processing Time (Days): Before vs. After
What This Means for Multi-Campus School Groups
When fee collection and payroll run on separate spreadsheets at each site, the real cost is not just collection delays. It is the staff hours spent reconciling, the compliance errors that accumulate invisibly, and the decisions made on stale data. Connecting both functions in one system removes those costs at the source.
Frequently Asked Questions
Can Zoho Books handle multiple fee structures across campuses that charge differently?
Yes. Zoho Books supports separate fee heads per contact group, so each campus can carry its own schedule for tuition, transport, exam, and activity charges. Invoices pull from the correct fee structure for each student, and reporting can be sliced by campus or consolidated at the group level. You do not need a separate Zoho Books organisation for each campus.
How does Zoho People handle ESI and PF when staff join mid-month across different campuses?
Zoho People calculates ESI and PF contributions on a pro-rated basis from the date of joining entered in the employee record. Once the employee master is accurate, the system picks up new joiners automatically in the payroll cycle for that month. The statutory export files it generates, ECR for PF and the monthly ESI challan data, are formatted to EPFO and ESIC requirements, so there is no manual re-entry before filing.
What happens to fee reminders when a parent has paid partially against an invoice?
Zoho Books tracks partial payments against each invoice and updates the outstanding balance in real time. The automated reminder workflow fires only on the remaining open amount, not the original invoice total. Parents receive an accurate balance figure in the reminder, which reduces disputes and avoids the situation where a family that paid the first instalment receives a full-balance overdue notice.
How long does it take to get six campuses live on Zoho People and Zoho Books together?
A realistic timeline for a group of this size is ten to twelve weeks from kickoff to handover, with the longest work concentrated in the data audit and employee master cleanup phase. The configuration itself is straightforward once the source data is correct. Running one parallel payroll cycle before going fully live is strongly recommended to catch any component or attendance mapping issues before they appear in actual salary payments.
