School ERP FAQ for Indian schools

The product is organised into functional areas Organisation, Academic, Admission, Student and Parent Management, HR & Staff, Finance & Fees, Communication, Library, Transport, Hostel, Facilities & Inventory, Reports & Analytics, Dashboard & Insights, Security & Authentication, and Support each with its own page on this site. Depth sits in the workflows inside those areas, not in a marketing feature count.

Academic attendance, timetable, examinations, assignments, curriculum, class diary, discipline, houses and parent-teacher meetings all live there. HR & Staff, Security & Authentication, and Finance & Fees follow closely for schools that run those operations in-house.

No. A day school with no boarding does not need Hostel Management, and a school that outsources buses does not need Transport. We enable the areas you run and price accordingly, and you can add areas later in the session.

One student record feeds everything. The admission record becomes the student profile; attendance, fees, exams, transport and hostel all read from that same profile rather than keeping their own copy. That is why reporting is reading rather than collecting at the end of a term.

Fee structures, grading systems, exam weightage, report formats, roles and permissions, and school and session settings are all configurable. There is also a custom report builder for board and trustee formats. Deeper custom development is scoped separately as a project.

The platform works in any modern phone browser today, and the parent and student portals are built for that. A native parent app is in development and will be announced when it ships we do not list it as available now.

No. KIDUART needs a connection to record attendance, collect a fee or publish a result, because those actions write to the shared record other people are reading. Plan for basic connectivity in the front office and staff room.

Ten role panels ship with the product: system admin, organisation, director and leadership, school admin, academic coordinator, teacher, finance and accounts, HR and staff, parent, and student. Every panel reads from the same database a panel is a view, not a separate product.

No. Pricing is per active student. Staff, teacher, student and parent logins are included, so a large teaching team does not change your bill.

Not unless you give them that permission. Access is decided by role, and the sidebar itself reflects those permissions, so people do not navigate to screens they cannot open.

A parent sees each linked child: attendance, fee dues and receipts, results and report cards, notices, and transport or hostel details where those modules are in use. They see their own children only.

Yes. Trusts and school groups run an organisation panel above the individual schools, with campus-wise reporting, consolidated fee collection views, and central control over roles and session policy. That is the Group plan.

Pricing is per active student per month, in INR. Staff, teacher, student and parent logins are included there is no per-user charge, so a large teaching team does not change your bill. Which plan you need depends on which functional areas you switch on. Book a demo and we will price it against your actual student count and area list.

Core covers the areas every school runs daily: organisation setup, admissions, student records, academics (attendance, timetable, exams, report cards), fees, communication and role-based security. Complete adds HR and payroll, library, transport, hostel, facilities and the full reporting and dashboard layer. Group is for trusts running several campuses under one organisation with consolidated reporting.

No. A day school with no boarding does not need Hostel Management, and a school that outsources buses does not need Transport. We switch on the areas you use and price accordingly. Modules can be added later in the session and billing adjusts on a prorated basis.

Onboarding and data migration from your existing system are included on Complete and Group. On Core, a one-time setup fee may apply depending on how much historical data needs importing. We confirm the exact figure during the demo, before you commit.

Setup follows the same order as the product: organisation and session structure first, then classes, sections and subjects, then student records, then the fee book and staff accounts. Most single-campus schools are running attendance and fee collection within a few weeks; timelines depend on how clean the existing data is.

Yes. Groups with multiple campuses or high student counts move to volume pricing under a single organisation account, with one invoice and campus-wise reporting. Contact our team for a quote.

Your school's data belongs to your school. You can export student records, fee ledgers, attendance and exam data in standard formats (CSV, Excel, PDF) at no cost, and we remove it from our systems on request.

Yes, the parent portal on web is included in every paid plan, with attendance, fees, results and notices for each linked child. The native parent app is in development and will be announced separately.

The same order the product is built in: organisation and academic session first, then classes, sections and subjects, then student records, then the fee book, then staff accounts and roles. Setting it up in this order means each step has the data the next one needs.

Most single-campus schools are running attendance and fee collection within a few weeks. The variable is data quality clean class lists and a settled fee structure move fast; a decade of inconsistent spreadsheets takes longer to map.

Yes. Student records, guardian contacts, fee structures and staff data can be imported in bulk, whether they are currently in spreadsheets, another ERP, or both. We map your existing structure before importing anything.

Yes, and it is run per role rather than as one long session. Front office, teachers, accounts and leadership each learn their own panel, which is the whole point of role-based panels the training is short because the screen matches the job.

Schools do join mid-session. We start with the modules that give immediate relief usually student records, attendance and fees and bring the rest in over the following weeks rather than pausing the school year.

Six layers: verified logins with hashed passwords and optional authenticator-app MFA, role-based permissions, tenant-level separation so each school's data sits in its own database, session and token control you can revoke, optional IP and location restrictions, and audit logging of sensitive actions. Our security page walks through each one.

No, and we will not imply otherwise. We describe the controls implemented in the product today. When formal audits are completed, they will be published with dates.

No. Each school runs in its own tenant database and every request is resolved to a tenant before any query executes, so the boundary is structural rather than a filter someone could forget.

Authenticator-app based (TOTP) with backup recovery codes. SMS-based second factor is on the roadmap and is not available today.

Only roles with permission on that record. A class teacher does not automatically get a student's identity or financial documents.

You export student records, fee ledgers, attendance and academic data in standard formats at no cost, and we remove school data from our active systems after the agreed wind-down. We do not sell school data or train models on student records.

Razorpay and Stripe are live. Parents pay from the portal, the gateway confirms through a signed webhook, and KIDUART writes the payment against the student's fee record with a receipt. Settlement goes to your own bank account under your own merchant agreement. PayPal is a roadmap item.

Yes, through the WhatsApp Business API using approved template messages from the school's own number. SMS and email delivery are also supported, which matters because not every guardian uses WhatsApp.

Yes. Google Workspace and Microsoft 365 sign-in are both supported. Identity comes from the account your IT team manages; permissions still come from the KIDUART role.

Those are roadmap items, not live integrations, and our integrations page labels them that way. Google Meet, Zoom and Microsoft Teams meeting creation are available today for online classes.

Yes versioned REST endpoints with managed, scoped API keys rather than a shared staff login, plus webhooks for live events such as a confirmed payment. Documentation is at /integrations/api-docs.

Current versions of Chrome, Firefox, Safari and Edge on desktop and mobile. There is nothing to install.

Email and the in-product support ticket module, plus the guided help centre on this site. Schools on Complete and Group also get a named contact for escalation.

Yes. Support Ticket Management is a module, so a raised issue carries context which school, which module, which user instead of arriving as an ambiguous email. Organisations can also raise tickets at group level.

Working-day coverage over email and tickets, with the exact window confirmed during onboarding so it is written down rather than assumed. Fee-collection and exam periods get priority attention because that is when a delay actually hurts.

Raise a support ticket in the product or email support@kiduart.com. Include the module and what you expected with role-based panels, the same action can look different depending on who performed it.