When a school says it needs "an ERP," the underlying ask is rarely procurement workflows or general-ledger journals. The real ask is: one system that owns the student, knows what's owed and what's paid, tells the parent when something happens, and gives the principal an honest answer when someone asks how many students were absent last Tuesday. JEduManage is built for that ask.
What people actually mean by "school ERP"
Business ERPs revolve around vendors, purchase orders, and assets. Their data model is wrong for schools. A student is not an asset, a parent is not a vendor, an exam is not a project. Trying to map school workflows onto invoice schemas creates a permanent layer of friction between the staff room and the tool.
School ERP is the term we use when we mean: one system covering everything a school's office cares about — admissions, attendance, exams, fees, transport, communications, and role-aware visibility for teachers, parents, and the principal. JEduManage is the purpose-built version of that: one product, one tenant, one audit log. See the school management software page for the operational view and the pricing page for how a tenant gets set up.
Cloud-based, multi-tenant, isolated by default
JEduManage is hosted SaaS. There is no installation step, no on-premise database to babysit, no patch window to coordinate. Every school is a fully isolated tenant inside the same hosted application: separate students, separate staff, separate fee structures, separate audit log, separate branding. Cross-tenant reads are impossible by construction — the database query layer injects each tenant's account_id automatically into every query.
For a trust running multiple schools, this means each school sees only its own data. The platform admin role (the trust office or headquarters) gets a cross-tenant view for monitoring and onboarding new schools, but never sees anything inside an individual school's records.
Role-aware portals from the same data
School ERPs that staple separate apps together for admin, teachers, and parents end up with the same data in three places and three ways to get it out of sync. JEduManage is one application with per-role views of one database. The same student record, viewed by the admin, the class teacher, and the parent, never disagrees with itself.
- Super-admin — platform operator. Cross-tenant onboarding, SMS usage, branding, audit.
- Admin — school office. Admissions, fee structures, user management, exams, attendance, full audit.
- Principal — leadership view. Same operational read access, plus leave approvals and marks publishing.
- Teacher — classroom view. Class roster, attendance marking, grading sheets for their subjects.
- Parent — family view. Each child's attendance calendar, fee breakdown, report cards.
Modules covered out of the box
The ERP ships with every module a typical school needs. There is no plug-in store to navigate; every feature ships as part of the standard tenant.
- Student information — admission records, parent linkage, transfer/promote/withdraw, history. See the student information system.
- Daily attendance — section-by-section marking, absentee SMS automation, calendar holidays. See attendance management.
- Fee management — per-class fee structures, per-student adjustments, online payment recording, SMS reminders, optional bus-route transport fee. See fee management.
- Exams and grading — exam scheduling, subject-wise grading sheets, configurable grade bands per school, report-card generation with PDF export
- Bus route management — per-tenant route catalogue with a frozen fee snapshot per student so route-fee edits never silently restate students' bills
- SMS & communications — DLT-compliant templates via MSG91 (admission welcome, login OTP, holiday announcement, absentee notification, fee-due reminder, fee-pending reminder)
- Branding — per-tenant school name and logo across every portal sign-in
- Audit log — immutable record of every administrative action, queryable by user, date, and module
Security designed at the data layer
Tenant isolation isn't a UI convention; it's enforced at the database query layer. Authentication uses JWT access tokens with the user's role and account_id encoded. Passwords are hashed with argon2id before they reach storage. Staff login by email + password (with optional MSG91 OTP for admin/principal); parents log in by phone number + password — the same phone can legitimately belong to a staff member and a parent without creating portal ambiguity.
Every administrative action is recorded in an immutable audit log with actor, timestamp, before-and-after data. Schools recovering from a "who did this?" question now reach for the audit panel first, not the email thread.
Built for the Indian school context, not retrofitted to it
Most ERPs sold in India started somewhere else and were translated. The artefacts show: fee structures that don't model term-wise payments, attendance modules that don't know about half-yearly holidays, SMS pipelines that don't speak DLT compliance, calendar assumptions that don't match the Indian academic year. JEduManage was built around the workflows that actually happen in Indian schools. The fee structure is per-class per-academic-year. The SMS pipeline is DLT-compliant via MSG91 with the templates Indian schools actually send (admission welcome, login OTP, fee reminder, absentee, holiday announcement). The academic year runs April to March by default but is configurable per tenant. Bus routes, transport fees, and parent phone authentication are first-class — not afterthoughts.
Reports that match what the office prints
Every school's office generates a familiar set of documents — fee receipts, fee-pending lists, attendance reports, report cards, transfer certificates, ID cards. JEduManage's reporting surface covers each of these as a one-click export, with the school's branding and PDF formatting that survives a print run on the same inkjet printer the office has been using for years. The PDF layout is deliberately conservative — no aggressive colour blocks that eat ink, no fonts that won't render on older Acrobat installs, no orientations that surprise the printer's auto-feed.
For schools that want to take the data out and analyse it themselves, every report has a CSV download alongside the PDF. Office staff who live in Excel can keep living in Excel; the ERP just gives them clean data to work with instead of stitched spreadsheets.
Pricing that's predictable, not per-user
JEduManage is priced per school, not per user. Adding the twenty-third teacher to a tenant doesn't increase the bill. Adding a hundred parent logins doesn't increase the bill. The price the school sees during evaluation is the price they pay six months in. SMS is a separate metered cost (because MSG91 charges per message), but every other module — students, attendance, fees, exams, reports, audit, parent portal — sits inside the base tier. Full pricing breakdown is on the pricing page.
Onboarding is a single day, not a six-month project
A school comes online in three steps: super-admin creates the tenant, the school admin receives credentials over SMS and email, the admin uploads the school's logo and starts admitting students. There is no on-prem install, no configuration project, no consulting retainer. Trusts running multiple schools onboard each new school the same way — the tenant boundary makes adding a school feel like adding a folder, not adding an installation.
When you're ready, reach out and we'll spin up a real tenant with your school's branding. There's no salesperson stage and no demo data muddying the picture — you log in to your own school's workspace and start admitting students.