
Student Lifecycle
Integrated admissions, registration, academic management, assessment and reporting, from application to graduation.
PSET connects admissions, academic management, facilities, research, finance and student engagement in sixteen integrated modules, so a student record, an invoice and a timetable slot all refer to the same thing.

Universities, colleges and training institutes running registration on spreadsheets, finance on a separate system, and timetabling on somebody's laptop.
Faculties, research administration, alumni and donor relations, and a finance function that has to reconcile all of it. PSET is the only module set here that covers research compliance alongside student billing.
High intake volume, short cycles, and a registration process that breaks every semester. Admissions, timetabling and student finance are the modules that pay for themselves first.
Where each campus has invented its own process. One database, one chart of accounts, and shuttle, meal and facilities management that finally reconcile at group level.
Nobody switches on all sixteen in one go. We usually start with admissions, student finance and timetabling, then add modules by semester.

Integrated admissions, registration, academic management, assessment and reporting, from application to graduation.

Student billing, payments, account tracking and financial reporting, reconciled against the general ledger.

Facilities, infrastructure, resources and maintenance, so campus operations stop running on email.

Research administration, collaboration, reporting and compliance management in one place.

Graduation workflow, alumni records, career services and the fundraising pipeline that follows.

Transport booking for students, with route planning and scheduling that adjusts to the timetable.

Identify donors, run campaigns and cultivate relationships without a separate CRM licence.

Requisition to purchase order, supplier records and approval workflows tied to budget.

Faculty and staff records, payroll and performance, on the same system as the finance ledger.

Optimised schedules for students and faculty, aware of room capacity and lecturer availability.

Dining services, meal plans and pre-booking, which is what actually reduces catering waste.

Enquiry to enrolment, plus service communication across every educational service you offer.

Institutional goals, initiatives and progress tracking for organisation and people planning.

Legal compliance, contract records and dispute resolution tracking.

Institution-level accounting, budgeting and forecasting across faculties and campuses.

Evidence, controls and reporting for compliance with statute and internal standards.
Campus ERP projects fail when everything switches on at once, in the middle of a semester. We phase around your academic calendar instead.
We walk registration, billing and timetabling as they actually happen, including the workarounds, and map them onto PSET modules.
Student records, programme structures, fee schedules and open balances migrate and get reconciled before anyone logs in.
A single intake cycle runs end to end on PSET, with the legacy process still standing, so problems surface while there is a fallback.
Remaining modules switch on by semester, staff are trained by role, and reporting is wired into whatever the board already reads.
No. PSET is built by Profecia, whose product it remains. Mphando implements it, integrates it with the rest of your systems, and supports it locally. You can read about the product itself at pset.tech.
Odoo is a general business ERP: excellent for finance, inventory and operations, with no concept of a semester, a programme structure or a research grant. PSET is built for education, so admissions, timetabling, academic records and research compliance are native rather than custom modules you pay to maintain. If your institution is mostly a business with students attached, Odoo may still be the right answer, and we will say so.
No, and you should not. Most institutions start with student lifecycle, student finance and timetabling, because those three carry the most manual work. The rest switch on semester by semester.
It migrates and gets reconciled before go-live: student records, programme structures, fee schedules and open balances. Where the source data is inconsistent, which it usually is, we surface the conflicts as a report for your registry to decide on rather than guessing.
Yes, and we recommend it. One intake cycle runs end to end on PSET with the legacy process still standing. If it does not hold up, you have lost a cycle of parallel effort rather than an academic year.
Bring the spreadsheet you actually run admissions on. A demo against real institutional data is worth more than a feature list.