Skip to main content

College ERP

College ERP software
for Indian institutions.

CampusNexus keeps student and faculty records, attendance, fees, examinations, payroll, transport, hostel and library on one system — so the attendance a lecturer marks is the same record that drives academic reporting and staff salary.

Explore CampusNexus ↗

In short

CampusNexus is a cloud college ERP that keeps a college’s student and faculty records, attendance, fees, examinations, payroll, transport, hostel and library operations in one system, with every module reading from the same institutional record.

It is built and operated by Polynexus, a software company in Nagpur, Maharashtra, and is sold to colleges and universities in India on a per-student subscription. The Starter tier is ₹60 per student per month; larger module sets are quoted per institution.

At a glance

Product
CampusNexus — college & university ERP
Category
Higher-education ERP / campus management software
Delivery
Cloud, isolated workspace per institution
Built for
Colleges and universities in India
Operated by
Polynexus, Nagpur, Maharashtra
Starter pricing
₹60 per student per month
Higher tiers
Quoted per institution by module set
Data rights
DPDP Act 2023; institution owns its data

Who it is for

Colleges where the registers have stopped agreeing with each other

The problem is rarely one department. It is that four departments each keep their own version of the same student.

  • Degree and professional colleges running multiple programmes where attendance, fees and examination records currently live in different places.
  • Autonomous institutions that conduct their own examinations and valuation, and therefore carry the full weight of result processing themselves.
  • Affiliated colleges that must supply consistent records upward to a university and cannot afford them to disagree with the internal ones.
  • Institutions with hostels and bus routes, where transport and boarding charges need to reach the same fee ledger as tuition instead of being tracked separately.

Problems it solves

What actually goes wrong

  • Proxy attendance. A register passed down a row proves nothing. Face verification, a classroom location zone and a lecturer-controlled session timer have to pass together.
  • Fee reconciliation by hand. When a student part-pays, someone decides which head it lands against. Proportional splitting rules make that automatic and consistent.
  • Attendance re-keyed into payroll. Staff check-ins already exist in the system, so absence deduction and leave balances follow from them rather than from a monthly typing exercise.
  • Evaluator bias in valuation. Anonymous valuation hides candidate identity from the evaluator, so the mark is awarded on the script.
  • Accounts that cannot be separated. Each institution gets an isolated workspace, so one college’s registers are not reachable from another’s account.
  • Logins from anywhere. Authorised-device locks verify device and browser parameters before an account can sign in, and registration is restricted to the institution’s own email domain.

Modules

What is in the system

Every module below is live functionality. Where a module belongs to a higher tier, that is stated.

Registrar hub

The student and faculty directory the rest of the system reads from — profiles, roles and registrar records, kept in a workspace isolated per institution so one college’s registers are never visible from another’s account.

Onboarding is done by secure verification link rather than shared passwords.

Attendance

Face-verified check-ins constrained to classroom location zones, with lecturer-controlled session timers that open and close the window for a given class.

Three independent checks — face, place and time — make proxy attendance impractical.

Fees & accounts ledger

Fee heads defined per institution for tuition, transport, hostel and lab, bulk invoice rollout across a cohort, proportional splitting of a part payment across heads, and bank integrations for collection.

Reconciliation follows from the splitting rules rather than manual allocation.

Examinations

Exam scheduling, and valuation that hides candidate identity from the evaluator so marks are awarded without the evaluator knowing whose script it is.

Available in the Professional and Enterprise tiers.

Payroll

Salary templates mapping basic pay, allowances and deductions, fed directly by the same attendance records staff already check in against, with absence deduction and leave balance tracking.

Removes the monthly re-keying of attendance into a payroll sheet.

Transport

Route maps with live bus positions, transit cost accounting against the fee ledger, and digital boarding passes carrying the institution’s own colours and logo.

Hostel & mess

Hostel and mess boarding management, with the associated charges flowing into the same fee ledger as tuition rather than being tracked separately.

Library

Library circulation — issue, return and the record of who currently holds what — inside the same student record.

Institutional email

Custom-domain email addresses for students and faculty on the college’s own domain, with registration restricted to that domain so outside sign-ups are blocked.

Included at no additional cost on the Starter tier.

Academics & scheduling

Class schedules and assignment management, so the timetable a lecturer teaches to and the attendance session they open are the same object.

Inventory

Stock records with reorder handling for departmental and laboratory consumables.

Available in the Enterprise tier.

Reporting & access control

Institutional reports across the modules in use, plus authorised-device locks that verify browser and device parameters before an account can sign in.

Workflow

How attendance actually works

Attendance is the module institutions are most sceptical about, so it is worth being specific.

Attendance is not a register anyone can quietly sign for a friend. The lecturer opens a session for a specific class with a fixed time window; the student checks in with interactive face verification from inside a defined classroom location zone; and when the window closes, that record is what feeds academic reporting for students and absence deduction for staff payroll.

See the full attendance workflow, step by step, including how the same records reach payroll.

Deployment & security

Where it runs and how it is protected

Isolated institutional workspace

Each college’s registers sit in their own workspace. Tenant-level isolation means one institution’s data is not accessible from another institution’s account.

Encryption and access control

AES-256 encryption at rest and in transit, role-based access control, and audit trails on administrative actions.

Authorised-device locks

Accounts can be restricted to verified devices, and registration is limited to the institution’s own email domain so outside sign-ups are blocked.

Hosting and ownership

Polynexus builds, hosts and operates the infrastructure itself rather than outsourcing data handling. Hosting can be pinned to an Indian region, with dedicated instances for enterprise deployments. The institution owns its data.

Implementation

Getting a college onto it

Academic years do not pause for a software rollout, which is what dictates the sequence.

  1. 01

    Scoping and module selection

    Which modules you actually need, in which order, and what your existing records look like. A college with an autonomous examination load has a different critical path from one without.

  2. 02

    Registrar data first

    Students, faculty, programmes and departments come across first, because everything else references them. Onboarding uses secure verification links rather than distributed passwords.

  3. 03

    Attendance and scheduling

    Class schedules, then attendance sessions. This is usually where staff first use the system daily, so it is worth getting right before anything financial depends on it.

  4. 04

    Fees and accounts

    Fee heads, outstanding balances and bank integration. Best done at a term boundary so opening balances are clean.

  5. 05

    Examinations and payroll

    Layered on once the underlying records are trusted — examination scheduling and valuation, and payroll driven by the attendance already flowing.

  6. 06

    Parallel running and handover

    Fees and payroll run alongside the existing process for a defined period, so discrepancies appear while there is still a fallback.

Our college ERP implementation guide covers the full sequence and the pre-switch checklist.

Pricing

What it costs

The Starter tier is ₹60 per student per month and covers the registrar hub, face attendance, schedule and assignment management, custom-domain email, authorised-device locks and basic reports. The Professional tier adds fee collection and the accounts ledger, bus routes with live tracking, hostel and mess, examination scheduling and library circulation. The Enterprise tier adds staff payroll, valuation and anonymous grading, inventory reorders, a dedicated account manager and a custom SLA. Professional and Enterprise are quoted per institution.

The CampusNexus platform page has a cost estimator that sizes the Starter tier against your enrolment, and our guide to college ERP cost in India explains the pricing models you will encounter elsewhere and what sits outside a licence fee.

FAQ

College ERP software — common questions

Can CampusNexus support more than one college under the same trust or society?
Yes. Each institution gets its own isolated workspace — registers, fee ledgers and accounts are segregated per college, not pooled into one shared account — so a trust running several colleges can onboard each one separately while keeping their records apart.
Does CampusNexus handle admissions?
CampusNexus onboards students and faculty into the registrar hub through secure verification links, and that is where a student record begins. A full admissions and enquiry pipeline is not part of the current module set — if admissions is central to your requirement, tell us during the demo so we can be precise about what is in scope.
How is attendance kept honest?
Three checks have to pass together: interactive face verification rather than a photograph, a location zone limited to the classroom block, and a session timer the lecturer opens and closes. Marking attendance for an absent friend fails on at least one of them.
Can we use only some modules?
Yes. The platform is modular and the tiers reflect that: the Starter tier covers the registrar, attendance, scheduling, institutional email, device locks and basic reports, with fees and accounts, transport, hostel and mess, examinations and library circulation in the Professional tier, and payroll, valuation, inventory and a dedicated account manager in the Enterprise tier.
What does CampusNexus cost?
The Starter tier is ₹60 per student per month. The Professional and Enterprise tiers are quoted against the modules and deployment a given institution needs. The cost estimator on the CampusNexus page will size the Starter tier against your enrolment.
Who owns the data and where is it hosted?
The institution owns its data. Polynexus builds, hosts and operates the infrastructure itself rather than outsourcing data handling, on cloud infrastructure that can be pinned to an Indian region on request, with dedicated instances available for enterprise deployments.
Does CampusNexus produce NAAC, NBA or NIRF reports?
It does not generate accreditation submissions. What it does is keep the underlying records — enrolment, attendance, examination results, faculty records, fee and payroll data — in one consistent system, which is the part institutions usually spend the most time reconstructing at submission time. Our guide to NAAC, NBA and NIRF data explains which records map to which requirement.

See it against your own college

Tell us your programmes, your fee structure and whether you run your own examinations. We will demo the modules that matter to you.

Explore the modules

HAVE A PLATFORM IN MIND?