School Management System for South Africa

Yes. CAPS subject codes, weighting, and phase progression rules are configurable for Foundation Phase (Gr R to 3), Intermediate Phase (Gr 4 to 6), Senior Phase (Gr 7 to 9), and Further Education and Training (Gr 10 to 12). Assessment codes 7 down to 1 and their percentage bands are recorded per subject per learner in line with the Programme of Assessment requirement. Umalusi-referenced External Assessments and School-Based Assessment weightings can be modelled.

OpenEduCat can run alongside SA-SAMS during a transition or replace it entirely. Learner records, staff records, and financial records are structured to export in the field layouts SA-SAMS and provincial education departments typically request. Schools moving away from a legacy SA-SAMS installation get a migration path: bulk-import learner data via CSV, remap subject codes to CAPS, and reconcile fee balances. Independent schools that never ran SA-SAMS can operate directly against DBE reporting requirements.

The Protection of Personal Information Act (POPIA) requires that learner and parent personal information is processed lawfully with appropriate safeguards. OpenEduCat supports two deployment postures: self-host inside South Africa (Teraco, Africa Data Centres, on-premise) which keeps all data physically in-country and simplifies the Information Regulator conversation, or AWS af-south-1 (Cape Town) which is the nearest hyperscaler region. The school remains the responsible party and Information Officer under POPIA; the platform provides the technical controls.

Yes. Fees billed in ZAR through openeducat_fees with 15% VAT applied where the specific service qualifies (most tuition is exempt or zero-rated; uniforms, transport, and catering are typically VAT-applicable). Payment gateways: PayFast, Peach Payments, Yoco, Ozow instant EFT, SnapScan for QR-based mobile payment. Debit-order integration through Netcash and Sage Pay for the many parents on monthly-instalment plans. Reconciliation against learner accounts is automatic.

Yes. The South African Schools Act Section 39 fee-exemption workflow is built as a parent portal submission: parents upload income evidence, the School Governing Body fees committee reviews and approves full or partial exemption, and the exemption applies to the learner's fee ledger with a retained audit trail. Exemption-granted, exemption-refused, and partial-exemption categories all report to provincial education department returns when required.

For no-fee schools operating under the NSNP, the platform records per-learner daily meal counts, meal-type breakdown (breakfast, lunch), cost per meal, and Volunteer Food Handler stipend tracking. Monthly returns feed the district NSNP co-ordinator without a separate spreadsheet. The DBE Approved Menu framework guides meal-type configuration. Feeding-programme data is separable from private-fee learners in mixed-quintile schools.

Parent communications, fee statements, and report-card labels are templatable per language. Each parent chooses a preferred language in the parent portal, and their notifications render in that language. An isiZulu-speaking parent in KwaZulu-Natal receives attendance and fee reminders in isiZulu; an Afrikaans-speaking parent in the Western Cape receives Afrikaans; an English-speaking parent in Gauteng receives English. Dual-medium schools can render report cards bilingually. Coverage varies by language; the biggest South African languages have the deepest translation support.

A single South African school with 500 to 1,500 learners typically goes live in 8 to 14 weeks: two weeks learner data migration (often out of SA-SAMS or a legacy fees system), two weeks CAPS subject-code and Programme of Assessment configuration, two weeks fee-framework and payment-gateway setup, two weeks staff training, and two to four weeks parallel run. Independent schools sitting IEB typically move faster; public schools with quintile-based NSNP and Section 39 workflows take a bit longer.