Academic core
Student master and matriculation, course catalogue and curriculum versions, registration with eligibility and approvals, coursework and marks, exams, result moderation and multi-level approval, graduation.
University Management Solution
One system of record for the whole university — admission to graduation.
EduCore UMS owns the single academic truth — and the finance, admissions, HR and identity around it — for African universities operating at national scale.
- 100,000
- students modelled
- 5,000
- lecturers and staff
- 1
- system of record
The promise
A university is judged on one thing.
A result that has been approved cannot be silently changed, and a transcript can always be reproduced from locked records.
Everything else in EduCore UMS is a feature. That guarantee is the product. Every approval is recorded, every record that must not change is protected at the database level, and every official document can be re-issued, byte-for-byte, and independently verified years later.
What UMS owns
Not a result portal bolted onto spreadsheets.
EduCore owns the single academic truth for every student — and the operations around it.
Transcripts and verification
Signed, reproducible transcripts and statements of result, a public QR verification portal, and graduating lists.
Finance and tuition billing
Fee schedules with maker-checker approval, invoices and batch generation, payment plans, waivers, scholarships and sponsors, holds and clearance, transcript-payment gating, reconciliation and ledger exports.
Admissions CRM
Applicant capture and bulk JAMB/CAPS import, configurable screening and department review, versioned offers, acceptance, document clearance, and an immutable conversion to the student master.
HR and staff operations
Staff master, department assignment, teaching allocation that gates mark upload, active and inactive status, and the access lifecycle that follows.
Analytics and regulatory returns
Enrolment, gender and level breakdowns, result read models, dashboards, and the statutory returns Nigerian universities must file.
Identity and access
Single sign-on, multi-factor authentication, fine-grained roles, delegated administration, and enterprise SSO federation.
Every module is a feature. The integrity of the record is the product.
Why it is different
Guarantees that are enforced, not promised.
01
The record protects itself
Approved results and applicant-to-student mappings are append-only, enforced by database triggers — not by hoping the application behaves. An auditor's first question has a structural answer: no.
02
Every write is on the record
A single, immutable audit log captures who did what, when, and the before-and-after values, across every module. Built in from day one, not bolted on when an auditor asks.
03
Segregation of duties is enforced
Fee policy is maker-checker: the bursar who proposes a fee schedule cannot approve it. Only an allocated, approved lecturer can submit marks. The rules live in the system, not a policy binder.
04
Money is exactly-once
Payment callbacks are cryptographically signed and de-duplicated, so a gateway that retries a notification can never double-credit or double-charge a student.
05
Transcripts are verifiable
Each official document is signed and carries a QR code resolving to a public verification page. A tampered archive fails signature verification — an employer confirms authenticity without calling the registry.
06
It fits the university you already are
Every domain sits behind a stable interface with a feature flag. Run the built-in billing engine, or keep your existing ERP and let UMS read finance clearance through an adapter.
The buyer's worry, answered
“Can someone quietly change a grade after approval?”
Approved results are append-only, enforced by database triggers. It is structurally impossible, and every attempt is logged.
“Can we reproduce a transcript from five years ago?”
Transcripts are generated from locked records and re-issued byte-for-byte, each signed and QR-verifiable.
“Will a payment gateway retry double-charge a student?”
Payment callbacks are signed and de-duplicated — exactly-once by construction.
“Can we prove segregation of duties to an auditor?”
Maker-checker is enforced: the bursar who proposes a fee cannot approve it; only an allocated lecturer can submit marks.
“Do we have to rip out our existing ERP?”
No. Keep it and read finance clearance through an adapter, or switch on the built-in billing engine. Feature-flagged, your choice.
“Will regulatory returns be another manual scramble?”
NUC returns are generated from live operational data, not re-keyed into a separate template.
Built for African higher education
Designed around how your university actually works.
Regulatory returns
National Universities Commission returns generated from the same data that runs operations — not re-keyed into a separate template.
JAMB and CAPS
Admission references preserved end-to-end, from applicant capture through to the student master record.
Modelled natively
Matriculation numbers, naira billing, and the faculty, department and campus structure of a Nigerian university.
SMS-first notifications
Because student email usage is variable — with email fallback and a delivery log, so a returned document or a released result actually reaches the student.
How it is engineered
Proof it works, not just claims.
Modular monolith, service-shaped
Clear domain modules with boundaries enforced at build time — simple to operate now, splittable exactly where load later demands.
Event-driven from day one
Domain events flow over a real message broker, so notifications, analytics and integrations attach without entangling the core.
Standards-based integration
LTI 1.3 and OneRoster for the LMS, SMTP and SMS gateways for messaging, and a clean finance adapter for ERP.
Container-native operations
Continuous integration, health and readiness probes, service-level metrics, load testing at scale, alerting and rehearsed disaster-recovery drills.
Integrity behaviours are proven end to end and re-tested on every build: an approved result resists tampering, a duplicate payment makes no second credit, an uncleared applicant cannot become a student, and a tampered transcript fails verification.
Delivered in phases, pilot-first
A pilot faculty goes live before the wider programme completes.
- Phase 01
Academic core, pilot faculty
Student master, catalogue, registration, marks, moderation and approval live for one faculty — the record-critical slice first.
- Phase 02
Transcripts, clearance and gating
Signed transcripts and QR verification, plus the finance and HR slices that gate the academic record: holds, clearance and teaching allocation.
- Phase 03
Billing engine and admissions CRM
The full tuition billing engine and the applicant pipeline, delivered as complete products rather than afterthoughts.
- Phase 04
Analytics and regulatory returns
Dashboards, read models and statutory NUC exports generated from live operational data across the whole institution.
Talk to us
Book a walkthrough of the whole record.
We will show admissions, registration, results, transcripts, billing and regulatory returns working end to end — and the audit trail underneath all of it.