Compliance hub

SA regulatory compliance, done routinely.

SA-SAMS, LURITS, DHET, HEMIS, QCTO, NLRD, SETA, NSFAS, CHE, POPIA — ten frameworks, one platform, zero last-minute scrambles. Records are audit-ready every day, not just submission week.

Aligned with SA-SAMS · LURITS · DHET · HEMIS · QCTO · NLRD · SETA · NSFAS · CHE · POPIA

The shift

From submission-week panic to routine compliance.

South African institutions don't fail compliance because they don't care — they fail because the data is fragmented, the validation happens too late, and the submission tool is the wrong shape. eduSYMS fixes the order.

Without eduSYMS

  • Submissions assembled the week before deadline
  • Mismatched learner IDs caught at the regulator, not at source
  • POPIA consent tracked in side spreadsheets — or not at all
  • QCTO PoE, SETA evidence, NLRD records in three different folders
  • Audit prep is a project, not a state

With eduSYMS

  • Submission packages generate from live, validated data
  • Learner IDs validated against LURITS rules at registration
  • POPIA consent captured at source, audit-logged automatically
  • QCTO, SETA, NLRD evidence linked to one learner record
  • Audit-ready is the default, not an event

The regulatory stack

Ten frameworks. All aligned by default.

Every framework South African schools, TVETs, universities, and skills providers must hit. Not bolt-ons, not export-only conversions — aligned at source so audits, submissions, and inspections become routine.

Aligned

SA-SAMS

South African Schools Administration & Management System

Native imports, learner record mapping, and submission-ready exports for DBE schools. Termly cycles, 10-day and 30-day windows handled at source.

Aligned

LURITS

Learner Unit Record Information & Tracking System

Unique learner ID generation, validation, and lifecycle tracking. ID conflicts caught at registration, not at submission.

Aligned

DHET / HEMIS

Department of Higher Education & Training · Higher Ed MIS

HEMIS-aligned reporting for universities and TVET colleges. Bi-annual submission packages generated, validated, and packaged.

Aligned

QCTO

Quality Council for Trades & Occupations

Digital PoE, MIS exports, assessor and moderator workflows for occupational qualifications. Per-cohort sign-off trails, audit-ready.

Aligned

NLRD

National Learners' Records Database

Generated, validated, and packaged from your live data — not stitched at deadline. Certification records flow end-to-end.

Aligned

SETA

Sector Education & Training Authorities

Learner certification and training data ready for SETA verification on demand. Per-programme reporting cycles supported.

Aligned

NSFAS

National Student Financial Aid Scheme

Funded learner registration, allowance tracking, and reconciliation. Attendance-driven disbursement workflows wired to one record.

Aligned

CHE

Council on Higher Education

Quality-assurance reporting for accredited higher-ed programmes. Programme-level evidence linked to learner outcomes.

Aligned

POPIA

Protection of Personal Information Act

Consent capture, data minimisation, audit-ready access logs, and POPIA-aligned retention — baked into every module.

Aligned

DBE

Department of Basic Education

Reporting, circulars, and inspection-ready records for SA basic-education institutions. Audit trails that match what inspectors look for.

How compliance happens here

Four stages, every framework.

The same workflow runs whether you're submitting SA-SAMS, HEMIS, NLRD, or CHE. Same shape, same rigour, same audit trail — only the destination changes.

  1. 1

    Capture

    Records, attendance, fees, evidence, and consent captured at source — tied to one learner identity from registration onward.

  2. 2

    Validate

    Framework rules applied at the input. LURITS validation, QCTO qualification specs, POPIA consent, DHET HEMIS structures — checked at source, not at submission.

  3. 3

    Approve

    Sign-off trails per role — assessor, moderator, registrar, principal, finance. Every decision logged with timestamp, author, and reason.

  4. 4

    Submit

    Submission-ready exports per framework, packaged in the format the regulator expects. Generated, not stitched. Re-runnable end-to-end.

Submission cadence

Different cycles, same calendar.

Each framework has its own rhythm. eduSYMS surfaces the next deadline for whichever frameworks apply to your institution — so submissions become routine ticks, not all-hands fire drills.

Compliance for

Pick your institution — we'll show you the mix.

Different institutions face different regulators. Click through to your audience page for a tailored read on which frameworks apply and which products handle them.

Audit-ready by default

What inspectors look for. What we deliver.

An auditor's checklist isn't a mystery. eduSYMS is built around the things they always ask for — so when an inspection arrives, you don't pivot.

Common questions

Compliance · FAQ

Does eduSYMS replace SA-SAMS?

It works alongside or in place of SA-SAMS depending on your school type. For most schools, eduSYMS becomes the day-to-day operational system and generates SA-SAMS-ready exports for the cycles where SA-SAMS is still the official submission tool. Submission week stops being a crisis.

How do you handle LURITS validation?

LURITS rules are applied at registration. ID conflicts, duplicate generations, and historical lookups all happen at the moment a learner is added — not weeks later when a submission is being assembled.

Is the audit trail enough for inspectors?

Yes. Every record carries a full change history (who, when, why), every regulated action carries a sign-off trail, every submission package is archived with the data version it captured. Inspectors get answers in minutes.

Does eduSYMS make me POPIA-compliant on its own?

It does the heavy lifting — consent capture, access logs, data minimisation, retention windows, subject-access workflows. POPIA-compliance is also about your institution's policies and processes, which eduSYMS supports but doesn't replace. Read our Privacy Policy for our role as a sub-processor.

What if a framework I need isn't on the list?

Tell us. The frameworks above cover what most South African institutions need. Where a customer needs a specific extra (provincial education department flavours, sector-specific SETAs, niche programme accreditors), we extend with structured rules — not bespoke code.

What about data residency?

Customer data is resident in South Africa by default. Limited operational data (e.g. WhatsApp Business platform messaging) may transit Google or Meta infrastructure outside SA — with contractual safeguards as POPIA requires. Full detail in our Cookie Policy and Privacy Policy.