A school ERP (enterprise resource planning) system in India is the central software for admissions, fee collection, attendance, timetables, exams and report cards, transport, HR and payroll, and parent communication, usually delivered as a cloud subscription with parent and teacher mobile apps. For most K-12 schools the right choice is a product that gets fee management, attendance, examinations and the parent app right, fits your board's report-card format (CBSE, ICSE or state board), and handles children's data in line with India's Digital Personal Data Protection (DPDP) Act. Pricing is mostly quote-based and tied to student count, so compare vendors on a per-student-per-year basis with implementation and SMS/WhatsApp costs included.
Executive summary
- The core buying test is fees, attendance, exams and the parent app. Timetabling, library and hostel modules matter, but schools abandon ERPs mostly because fee reconciliation or report cards fail.
- Digital readiness has risen but is uneven. The Ministry of Education's UDISE+ 2024-25 release reports that schools with computer access rose from 57.2% in 2023-24 to 64.7% in 2024-25, and that India's teacher count crossed one crore for the first time. Many schools still need mobile-first, low-bandwidth software.
- Children's data raises the compliance bar. The DPDP Act, 2023 treats personal data of children with extra safeguards, including verifiable parental consent. Your ERP contract needs clear processor obligations.
- Few vendors publish prices. Classe365 publishes pricing in US dollars from $100/month for 1–100 students. Most Indian school ERPs (Entab CampusCare, MyClassboard, Edunext, Teachmint) quote per school.
- Implementation is a term-calendar problem. Go live at the start of an academic session or a fee cycle. Budget six to twelve weeks, most of it on data migration and staff training.
App Advisor is not affiliated with any vendor named here.
Market context
India runs one of the world's largest school systems, and its size and variety shape the software market. According to the Ministry of Education's release on the Unified District Information System for Education Plus (UDISE+) 2024-25, the total number of teachers crossed the one-crore mark for the first time, and schools with computer access rose from 57.2% in 2023-24 to 64.7% in 2024-25 (PIB release on UDISE+ 2024-25). UDISE+ itself is the national school data system that every recognised school reports into (UDISE+ portal). School ERPs increasingly need to produce data in UDISE+-compatible structures, such as enrolment by class, gender and social category, and teacher details, so administrators are not keying the same numbers twice.
Three features of the Indian context matter more than feature checklists:
- Fee complexity. Indian schools collect admission fees, term fees, transport, hostel, activity and exam fees in instalments, with sibling concessions, scholarships, RTE seats and late fines. Reconciling UPI, card, cheque and cash collections against these schedules is the most common reason schools buy an ERP.
- Board-specific assessment. CBSE, CISCE and state boards differ in grading scales, co-scholastic areas and report-card layouts. An ERP that cannot configure these forces teachers back to spreadsheets.
- Parents on mobile. Parent communication happens on phones. Circulars, homework, attendance alerts and fee reminders go through an app, SMS or WhatsApp, and message volume often carries its own charges.
Data protection is now a board-level issue. The Digital Personal Data Protection Act, 2023, administered by MeitY, sets obligations for organisations that process personal data and adds specific protections for children's data, including verifiable consent of a parent or lawful guardian. A school is the data fiduciary. The ERP vendor typically acts as a processor. Contracts, access controls and breach procedures should reflect that.
Evaluation framework
App Advisor methodology: criteria and weights reflect the needs of a typical private K-12 school with 500–3,000 students. Group schools should increase the weight of multi-campus consolidation.
| Criterion | Weight | What good looks like |
|---|---|---|
| Fee management and payments | 20% | Instalment schedules, concessions, online collection, auto-reconciliation, receipts, defaulter reports |
| Academics and examinations | 15% | Board-configurable grading, marks entry by teachers, report cards, promotion rules |
| Attendance and timetable | 10% | Student and staff attendance (app, RFID or biometric), substitution, timetable generation |
| Parent and teacher apps | 15% | Circulars, homework, attendance alerts, fee payment, two-way messaging, regional languages |
| Admissions and CRM | 10% | Enquiry capture, application forms, entrance tests, seat allocation |
| Data protection and security | 10% | Role-based access, audit logs, consent records, data residency and processor terms |
| Transport, HR and payroll | 10% | Route and GPS tracking, staff payroll or clean payroll integration |
| Reporting and statutory data | 5% | UDISE+-ready exports, management dashboards |
| Price transparency and exit | 5% | Clear per-student pricing, message charges disclosed, full data export |
Vendor comparison
| Product | Positioning | Published price | Notable modules | Source |
|---|---|---|---|---|
| Entab CampusCare | Indian K-12 school ERP with parent app | Not published on the page we could access (Quote) | Fees, academics, parent app, transport | entab.in |
| MyClassboard | Indian school ERP | Not published on the page we could access (Quote) | Fees, admissions, exams, communication | myclassboard.com |
| Edunext | Indian school ERP | Not published on the page we could access (Quote) | Fees, academics, HR, transport | edunext.co |
| Teachmint for institutes | School platform plus interactive-board hardware (Teachmint X) | Not published on the page we could access (Quote/demo) | Connected classroom, school operations | teachmint.com |
| Classe365 | Global student information system | Core: from $100/month for 1–100 students; add-on modules $75/month each; 10% saving on annual billing; 15-day free trial (prices in USD as published) | SIS, LMS, CRM, fee and invoicing add-ons | classe365.com/pricing |
| PowerSchool | Global K-12 platform | Quote | SIS, assessment, analytics | powerschool.com |
Notes on the comparison:
- Classe365 is the only vendor in this list with a public rate card, and it is in US dollars. We have not converted it. Add-on modules such as fees and invoicing, LMS and finance are priced separately, so a full ERP configuration costs more than the core price.
- Indian school ERPs usually quote per student per year, sometimes with a minimum annual fee, plus one-time implementation and optional hardware such as RFID or biometric devices and GPS for buses. Ask for SMS and WhatsApp message charges separately.
- Teachmint's current site leads with its interactive display hardware. If you want the ERP only, ask whether it is sold without the board.
Browse the full school software category. If you are also evaluating teaching platforms, see LMS software and our guide to LMS software for coaching and courses.
Total cost of ownership
Illustrative model — assumptions stated. Not a quote from any vendor.
School profile: one CBSE school, 1,200 students, 80 staff, 10 buses.
| Cost element | Assumption | Year 1 | Years 2–3 (each) |
|---|---|---|---|
| ERP subscription | P per student per year (obtain quotes; varies widely) | 1,200 × P | 1,200 × P, plus contracted escalation |
| Implementation and data migration | One-time fee F | F | 0 |
| Parent messaging | 1,200 families × 4 SMS/WhatsApp messages per week × 40 weeks × message rate m | 1,92,000 × m | 1,92,000 × m |
| Payment gateway | Gateway MDR on online fee collections (see your gateway agreement) | Collections × MDR | Collections × MDR |
| Hardware (optional) | RFID readers, bus GPS devices | H | Maintenance |
| Internal time | Admin staff 2 people × 60 hours of training and migration | 120 hours | 20 hours refresher |
Worked sensitivity. If P is ₹300, subscription is ₹3,60,000/year. If P is ₹600, it is ₹7,20,000/year. At a message rate m of ₹0.20, messaging adds ₹38,400/year. Messaging and gateway charges are frequently omitted from ERP quotes and can change the vendor ranking. The per-student amounts here are placeholders for modelling, not market prices.
Savings to model against cost: fewer fee defaulters through automated reminders, reduced manual reconciliation (typically one accounts clerk's time), and faster report-card generation at term end.
Implementation roadmap
| Phase | Weeks | Activities | Owner |
|---|---|---|---|
| 1. Requirements and board mapping | 1–2 | Fee structures, concessions, grading schemes, report-card formats, user roles | Principal, accounts head |
| 2. Vendor configuration | 2–4 | Classes, sections, subjects, fee heads, transport routes, timetable rules | Vendor + ERP coordinator |
| 3. Data migration | 3–6 | Student master, parent contacts, outstanding fee balances, staff records; clean duplicates | Admin office |
| 4. Payments and communication | 5–7 | Payment-gateway onboarding, message templates, app rollout plan | Accounts + IT |
| 5. Training | 6–9 | Teacher attendance and marks entry; accounts reconciliation; front-office admissions | Vendor trainers |
| 6. Parent launch | 8–10 | App download drive at PTM; first fee cycle through app | Class teachers |
| 7. First term close | 10–12+ | Exams and report cards in ERP; review defects | Exam cell |
Tip: start the fee module first if you are mid-year, and move exams at the next term boundary.
Risks and compliance checklist
- Children's personal data: document the purpose of each data field, collect parental consent where required under the DPDP Act, 2023, limit staff access by role, and set retention rules.
- Processor contract: the vendor contract should cover security safeguards, breach notification, sub-processors, data location and deletion on exit.
- Fee refunds and receipts: make sure receipts carry correct school entity details, and refunds follow the school's published policy.
- UDISE+ data consistency: reconcile ERP enrolment and teacher records with what the school reports to UDISE+.
- Biometric and CCTV integrations: treat these as sensitive. Collect only what you need.
- Message consent and DLT: SMS templates in India must be registered on DLT platforms by the sender. Confirm who registers them, you or the vendor.
- Vendor viability and exit: insist on a full export of student, fee and academic history in open formats.
- Uptime at peak: results day and fee deadlines create traffic spikes. Ask for historical uptime data.
KPIs to track
| KPI | Target direction | Notes |
|---|---|---|
| On-time fee collection rate | Up | % of billed fees collected by due date |
| Fee reconciliation time | Down | Hours per month to match gateway settlements |
| Parent app activation | Up | % of families with an active login |
| Teacher attendance marking compliance | Up | % of periods marked within the day |
| Report-card turnaround | Down | Days from last exam to published report cards |
| Admission enquiry-to-enrolment | Up | Conversion of enquiries captured in ERP |
| Support tickets per month | Down after term 1 | Signals training gaps |
| Data export tested | Yes/No annually | Proves you can exit |
How to choose
- Write your fee rules down first. Give every shortlisted vendor the same fee structure, including concessions and late fines, and ask them to configure it in the demo.
- Run a report-card test. Give vendors last term's marks for one class and your board's format.
- Test the parent app on a basic Android phone with a slow connection and in the regional language your parents use.
- Ask for all-in pricing: per-student subscription, implementation, messaging, gateway, hardware, annual escalation and exit costs.
- Check data protection answers in writing: where data is hosted, who can access it, how consent is recorded, and how deletion works.
- Call two reference schools of your size and board, ideally ones that switched from another ERP.
Payroll for teaching staff can also run through an HRMS. See HRMS software options in India and our list of HRMS software in India.
Vendor demo script
Sales demos of school ERPs tend to show dashboards. Your school's risk sits in fee rules, report cards and data handling. Send this script to vendors a week in advance, with anonymised sample data, and ask them to run it live.
Scenario 1: A realistic fee year. Configure a Class 6 fee structure with an admission fee, four quarterly tuition instalments, a transport fee by route, a 10% sibling concession, an RTE seat with zero tuition, and a late fine after the due date. Then:
- Collect one instalment by UPI through the parent app and one by cheque at the counter.
- Record a bounced cheque and show how the fine and reminder behave.
- Produce a defaulter list for the section and a day-book for the accounts office.
- Show how the gateway settlement is reconciled against receipts.
Scenario 2: Term report card. Upload marks for one section across scholastic subjects and co-scholastic areas in your board's format. Generate report cards, lock marks after approval, and show the audit log if a teacher changes a mark after locking.
Scenario 3: Attendance and alerts. Mark attendance from a teacher's phone, trigger an absence alert to parents, and show the monthly attendance register that the office prints.
Scenario 4: Admissions. Capture an enquiry from the website, schedule an interaction or test, admit the student, and convert the enquiry into a student record without retyping.
Scenario 5: Data protection. Ask the vendor to show:
- Role-based access: can a class teacher see another section's fee dues or medical notes?
- Where parental consent is recorded and how a parent's request to correct data is handled.
- How long data is retained after a student leaves, and how deletion or export works.
- Where the data is hosted and which sub-processors (messaging, cloud, payment) receive it.
Scenario 6: Statutory and management reports. Generate enrolment by class, gender and category, and staff lists in a structure your UDISE+ coordinator can use. Show a principal's dashboard with fee collection, attendance and admissions trends.
Scoring the demo
Score each scenario from 0 to 3 (0 = not possible, 1 = workaround, 2 = works with configuration, 3 = works out of the box) and multiply by the weights in the evaluation framework above. Do not let a vendor skip a scenario by promising it "in the next release". Ask for that promise in the contract, with a date and a remedy, or score it as zero.
Contract clauses worth negotiating
- A cap on annual price escalation.
- Service levels for uptime during fee deadlines and result days.
- Named implementation resources and a training plan for teachers.
- Data processing terms aligned with the DPDP Act, including breach notification timelines.
- Free export of all records in open formats at exit.
FAQs
What is school ERP software?
School ERP software is an integrated system that manages a school's admissions, student records, fees, attendance, timetables, exams, report cards, transport, staff and communication in one database, with apps for parents and teachers.
How much does school ERP software cost in India?
Most Indian school ERP vendors do not publish prices and quote per student per year, plus implementation. Among the vendors we checked, Classe365 publishes pricing from $100/month for 1–100 students, with add-on modules at $75/month each. Always ask for messaging and payment-gateway costs separately.
Is school management software the same as an LMS?
No. A school ERP runs administration: fees, attendance, exams and records. An LMS delivers learning content, assignments and online classes. Some products bundle both. Many schools use an ERP plus a separate LMS such as Google Classroom.
Which is the best school ERP for CBSE schools?
There is no single best product. Choose one that can configure your CBSE grading and report-card format, handles your fee rules, and has a parent app your families will use. Test these with your own data in a demo.
Does the DPDP Act apply to schools?
Yes. The Digital Personal Data Protection Act, 2023 applies to processing of digital personal data, and provides additional safeguards for children's data, including verifiable parental consent. Schools should review consent, access and vendor contracts with legal advice.
Can a school ERP generate UDISE+ data?
Many ERPs offer exports of enrolment and staff data that help with UDISE+ reporting, but formats vary. Ask the vendor to show a UDISE+-oriented report and reconcile it with last year's submission.
How long does it take to implement a school ERP?
Typically six to twelve weeks for a single school, depending on data quality and the number of modules. Align go-live with the start of a session or a fee cycle.
Can parents pay school fees through the ERP app?
Yes, most school ERPs integrate a payment gateway so parents can pay by UPI, cards or net banking. The gateway charges a merchant discount rate set in its own agreement. See our payment gateway charges comparison.
