College ERP vs school ERP: what colleges need that school systems miss

A school result is final once it is published. A college result is not. A student who fails a course carries it as a backlog, sits it again in a later examination, and either clears it or runs out of permitted attempts. The transcript has to show both the original result and the re-attempt, and whether the student can progress or graduate depends on what is still outstanding.

Software built for schools usually stores one result per student per examination. It cannot express a backlog as a state, so colleges using it keep the backlog register in a separate spreadsheet — and that spreadsheet is the one that decides who graduates.

Most Indian universities report results as a semester grade point average (SGPA) and a cumulative grade point average (CGPA), calculated from the credits each course carries and the grade point earned in it. In outline:

1. Each course carries a number of credits.
2. The grade earned in the course maps to a grade point on the university's scale.
3. SGPA is the sum of credits × grade points for the semester, divided by the total credits for that semester.
4. CGPA applies the same calculation across every semester completed so far.

The scales, the rounding and the treatment of failed or re-attempted courses vary between universities. That is why these rules should be configuration the college can see and check, not a formula buried in code. Where a university publishes a formula for converting CGPA to a percentage, that conversion is the university's own rule and should be applied as such.

A single campus commonly runs semester programmes alongside annual ones, and some professional courses use trimesters. A college ERP has to let each programme keep its own term structure rather than imposing one calendar on the whole institution.

Colleges organise students by programme, year and department, with elective choices that split a cohort across courses. These are the questions to put to a vendor:

• How are programmes and departments modelled, and can a student take a course offered by another department?
• How are elective choices recorded, and does marks entry follow the elective rather than the section?
• Can a student's programme or specialisation change part-way through without losing their history?

Beyond marksheets and transcripts, colleges issue migration, provisional, course completion, bonafide and character certificates — usually on request, and often years after the student has left. Each one needs to be traceable to the student's record and verifiable by the employer or university receiving it, ideally without a phone call to the office. A QR code linking to a verification page the college controls is the usual approach, and it is how AcadiFlow's certificates work.

College fees are commonly charged per semester or per year, with separate examination fees, fees for re-examination attempts, and scholarships that arrive from government schemes after the fee is due. The fee record has to hold a scholarship as a concession against the invoice with its source, so the balance a student owes is right while the scholarship is pending and after it arrives.

• Show a student who failed a course, re-attempted it and cleared it. What does the transcript show?
• Compute SGPA and CGPA for a real student from last year and compare the result with the university's.
• Set up one semester programme and one annual programme on the same campus.
• Issue a migration certificate for a student who left three years ago, then verify it from a phone.
• Record a scholarship that arrives after the fee due date, and check the student's balance before and after.

AcadiFlow's approach — a university semester rule set, SGPA and CGPA as a result format, and backlogs tracked as pending, cleared or exhausted — is described on the colleges and universities page.