Education ERP
Admissions, fees, attendance, timetable, examinations, transport, hostel, library, inventory, and accounts on a single registry — so the enrolment number in the fee ledger, the attendance register, the exam form, and the transfer certificate are the same number, checked once. Four editions, one spine.
Built for
§ 01
Most institutions do not lack software. They have a fee package, an attendance system that came with the biometric device, a spreadsheet the exam cell guards, a separate register for transport, and a library system from 2014. Each one works. The problem is that a student exists five times, with five slightly different spellings of their name and five different ideas of which section they are in.
The cost of that shows up as a tax on every question worth asking. How many students actually attended more than 75 percent and are eligible to sit the exam — a question with a statutory answer — requires exporting from two systems and matching by hand. Which fee defaulters are also in the hostel. Whether the transfer certificate says what the exam record says. Every one of those is a person-week per term, spent producing a number that was already in the building.
An ERP is worth having only if it collapses that. The test is not the module count — it is whether the admission number issued on day one is still the primary key when the degree is printed four years later, and whether any department can be given a view of the record without being given the ability to change it.
§ 02
Present in every edition. Each edition adds its own statutory and academic modules on top — see the edition pages for those.
The single record everything else references. Created once at admission, carried to the degree or transfer certificate, never re-keyed.
Enquiry to enrolled, with the documents, the seat, and the first payment all accounted for before a record is confirmed.
Where most institutions lose the most money and the most goodwill. Heads, concessions, instalments, dues, receipts, and reconciliation in one ledger.
Period-wise or day-wise, from a device or an app, with the shortage rules that actually decide exam eligibility computed continuously.
Generated against real constraints — room capacity, lab availability, faculty load ceilings, and the subjects that cannot clash.
Forms, seating, marks entry, moderation, and the result — in the format the board or the university actually accepts.
One outbound channel with a record of what was sent to whom — instead of six staff members with the parent WhatsApp group open.
Routes, stops, allocation, fees, and where the bus actually is — with the safety questions answerable rather than reassuring.
Rooms, allotment, occupancy, mess billing, gate movement, and leave.
Catalogue, circulation, and fines — connected to the same student record, so a no-dues certificate is generated rather than collected.
Purchase to disposal for uniforms, books, lab equipment, and fixed assets.
The financial truth, and the reports the management committee, the auditor, and the regulator each ask for in a different shape.
§ 03
Each step writes to the same registry. Nothing below requires re-entering a student's details.
New session created, structures rolled over, fee heads and calendar set, staff and scopes carried forward with changes applied.
Application, verification, merit or quota allotment, offer, acceptance, and first payment — producing one registry record with its documents attached.
Section, elective, transport route, hostel bed, and library membership assigned. Each allocation posts its own fee head automatically.
Timetable published, attendance captured daily, instalments falling due with reminders, circulars going out with delivery recorded.
Eligibility computed from attendance and dues, forms filled, seating and hall tickets issued, marks entered under double-entry lock.
Moderation applied by policy, result published, report cards issued in the prescribed format, and promotion or detention recorded.
Books closed, no-dues resolved, statutory returns assembled from the live record, and the session archived without leaving the registry.
§ 04
Scope is the point. Every role below is bounded by campus, department, section, or route — the accountant sees every ledger and no marks; a class teacher sees their section and no fees.
| Role | Can see | Can do |
|---|---|---|
| Class teacher / faculty | Own sections or subjects: attendance, marks, remarks, guardian contact | Mark attendance, enter marks before lock, record remarks, raise leave and substitution |
| Head of department | Department strength, faculty workload, result analysis, attendance shortage list | Approve timetable and substitutions, moderate within policy, sign off eligibility |
| Admissions office | Applications, documents, seat matrix, waitlist, admission collections | Verify documents, allot seats, issue offers, process cancellations and refunds |
| Accounts | Every fee ledger, receipt, concession, and reconciliation — no academic marks | Define heads and concessions, post receipts, reconcile, close books, export to accounting |
| Examination cell | Eligibility, forms, seating, marks entry status, moderation history | Lock and release marks, apply moderation, publish results, run revaluation cycles |
| Principal / management | Consolidated dashboards across every campus in scope, plus drill-down to any record | Approve policy, concessions above threshold, and statutory sign-off |
| Parent / guardian | Their ward only — attendance, marks, fees due, transport status, circulars | Pay fees, apply for leave, acknowledge circulars, update contact details for approval |
§ 05
The records that outlive every module. Retention is set per class, and deletion is executed rather than promised.
§ 06
Each integration is monitored and retried, with failures raised as alerts carrying the payload — not swallowed.
Payments & finance
Statutory & public
Devices & campus
Communication & identity
§ 07
An education ERP holds children's personal data, guardians' financial data, and records that are legally required to be producible years after a student has left. Under the Digital Personal Data Protection Act, 2023, data concerning children carries the heaviest obligations of any category — verifiable guardian consent, purpose limitation, and no behavioural tracking, without exception.
Alongside that sit the returns. Schools file UDISE+ annually; higher education files AISHE; both are assembled from the same operational records the ERP already holds. Building the return out of live data rather than a parallel spreadsheet is the difference between a two-day exercise and a two-week one, and it is also the only version that is actually true.
Implemented against
§ 08
Compared against the stack most institutions run today — several systems that each work and none of which agree.
| Aspect | Several systems, one spreadsheet each | One registry |
|---|---|---|
| The student | Exists five times, spelled four ways | One record, one identifier, from enquiry to alumnus |
| Exam eligibility | Two exports matched by hand, per term | Computed continuously from attendance and dues |
| Fee dues | A ledger reconciled at month end, chased by phone | Live, reconciled against the bank, reminded automatically |
| Statutory returns | A two-week assembly from four sources | Generated from the live record and reviewed |
| A parent's question | Three staff members and a callback | Answered in the parent app without staff involvement |
| Audit | "Someone changed it" | Actor, timestamp, previous value, and reason |
| Multi-campus view | Each campus reports its own numbers, differently | One consolidated view, drillable to any record |
§ 09
Module by module against your calendar, never as a single cutover. Windows are indicative and depend on data quality in what you run today — which is almost always the long pole.
Talk to an engineer
Bring a term's records and we will show the migration, the reconciliation, and what the registry looks like afterwards. Reply within one business day.
§ FAQ
It follows your statutory reporting and your academic unit. A school files UDISE+ and works in classes and sections. A college works in semesters with an affiliating university's exam formats and files AISHE. A coaching institute has no board but has batches, instalments, and test series. A university sets its own papers and issues its own degrees. Pick the edition that matches — the spine is identical underneath, so a school group that later adds a degree college does not start again.
Yes, and most institutions should. The registry is mandatory because everything references it; beyond that, fees and attendance are the usual first two because they pay for themselves fastest. A module that is off does not appear for any role — it is not a greyed-out menu item.
It is migrated, de-duplicated, and reconciled — and we issue a data-quality report before anything goes live, because the honest finding is usually that the existing records disagree with each other. Opening fee balances are reconciled line by line against your existing ledger. That reconciliation is the single most common reason a rollout takes longer than the estimate, which is why it is phase one and not an afterthought.
No, and you should not. A single-cutover ERP rollout in the middle of a term is the classic way these projects fail. Modules go live in sequence against your academic calendar, with the old system still readable until the module replacing it has run a full cycle.
The custom ERP service starts from a blank page and builds to your processes — the right answer when your operations genuinely are unusual. This is a platform that already runs the operations described above; you configure it, we extend it where your processes differ, and you see it working before committing. Most institutions do not need a bespoke ERP; they need this one configured properly.
You own the data outright. Deployment runs in your own cloud tenancy if you want it there — keys, backups, and residency under your control — or in ours if you would rather not run infrastructure. Exports are available on demand in open formats either way, because an ERP you cannot leave is a liability you have not priced.
Yes. Roles are scoped to a campus, so a principal sees their own institution while the trust or group management sees the consolidated view with drill-down. Fee structures, calendars, and report-card formats can differ per campus without splitting the registry.
Primary sources
Elsewhere in the suite