OnSIS Compliance: Ontario School Information System Guide

OnSIS reporting can feel technical, but it starts with something simple: accurate school data. This guide explains what Ontario independent schools need to report, when submissions happen, and what privacy and compliance principles schools should keep in mind.

Table of Contents

1. What Is OnSIS?

2. Why OnSIS Compliance Is Important

3. Who Does OnSIS Apply To?

4. What Data Does OnSIS Collect?

5. The Ontario Education Number (OEN)

6. The Ministry Educator Number (MEN)

7. OnSIS Submission Deadlines

8. Key OnSIS Compliance Principles

9. How MySchool Supports OnSIS Compliance

Ontario’s provincial reporting requirements for education have changed in several ways over the past few years.

Changing privacy obligations, updated enrolment reporting requirements, and a more complex regulatory environment mean that schools need a clearer understanding of what OnSIS (Ontario School Information System) compliance involves. That applies to public and private schools alike, though their legal and reporting contexts are not always the same.

If your school is still working from guidance written a few years ago, now is a good time to review the process, check what has changed, and make sure your reporting practices are still current.

Here’s what Ontario independent schools need to know.

What Is OnSIS?

The Ontario School Information System, or OnSIS, is the province-wide data collection platform used by the Ministry of Education to gather information from public and private schools across Ontario.

OnSIS collects data at both the individual and aggregate level. That includes information about students, educators, schools, boards, courses, enrolment, achievement, and other education records.

This data supports Ministry records, policy decisions, public reporting, long-term education analysis, and funding calculations in publicly funded contexts.

OnSIS replaced several older reporting mechanisms, including the October and March Reports, Postal Code Report, Course Enrolment Report, and Class Size Report. Instead of submitting these through separate processes, schools now report through one submission framework.

Schools usually submit OnSIS data in one of two ways: manually through the OnSIS portal, or by uploading XML batch files generated by their student information system.

Why OnSIS Compliance Is Important

OnSIS compliance is not only an administrative requirement.

Accurate submissions support Ministry records, policy decisions, public reporting, and education funding calculations in publicly funded contexts. They also affect how your school is represented in Ministry data.

Errors, late submissions, or mismatched data can create serious follow-up work for schools. In publicly funded contexts, they can affect funding calculations. For private schools, they can trigger correction work, audit questions, or concerns around a school’s reporting practices.

For private schools, compliance also connects to their broader relationship with the Ministry of Education and their registered operating status.

There is also a wider system-level reason to take OnSIS seriously. The data submitted by each school becomes part of the evidence base the Ministry uses to understand education across Ontario and make decisions that affect students across the province.

Clean reporting helps the province work from a more accurate picture.

Who Does OnSIS Apply To?

OnSIS applies to both publicly funded and private schools in Ontario.

The reporting responsibility is shared, but the legal and regulatory context is not always the same.

Publicly funded schools and school boards are generally subject to the Municipal Freedom of Information and Protection of Privacy Act, known as MFIPPA. This governs how they collect, use, retain, and disclose personal information, including information submitted through OnSIS.

Private and independent schools are generally not subject to MFIPPA or FIPPA. Many private schools’ operations are instead covered by PIPEDA, the federal Personal Information Protection and Electronic Documents Act. It governs how private sector organisations handle personal information in commercial activity.

If you operate an independent school, it is worth confirming which privacy legislation applies to your data practices.

This is especially important because privacy expectations are becoming more formal, more visible, and more closely connected to day-to-day school administration.

What Data Does OnSIS Collect?

OnSIS requires a broad range of information from schools.

The exact requirements depend on the school type, reporting cycle, and Ministry guidance for the school year. In general, schools should expect to report information across the following categories:

The Ontario Education Number (OEN)

Every elementary and secondary student enrolled in Ontario’s education system is assigned a unique nine-digit Ontario Education Number (OEN) by the Ministry of Education.

The OEN is randomly generated and linked to stable student information, including the student’s name, gender, and date of birth.

The OEN follows the student through their education in Ontario. It appears on education records and serves as the main student identifier in OnSIS submissions.

For schools, this makes OEN accuracy essential.

If an OEN is missing, entered incorrectly, or connected to inconsistent student information, the issue may need to be corrected before the school can complete a clean submission.

The Ministry Educator Number (MEN)

The Ministry Educator Number, or MEN, is a unique identifier assigned to educators in Ontario.

This applies whether or not the educator holds Ontario College of Teachers certification.

The MEN may apply to OCT members, teachers working under a letter of permission, non-teaching professionals such as speech-language pathologists, para-professionals such as oral interpreters, and teachers at private schools who do not hold OCT qualifications.

The MEN allows the Ministry to collect educator data consistently across Ontario’s education system.

For schools, this means educator records need the same level of care as student records. Missing or inconsistent staff information can create reporting issues, especially where educator assignments, qualifications, or course responsibilities need to be reported.

OnSIS Submission Deadlines

Many OnSIS problems begin around timing.

The Ministry sets specific dates for reporting, and missed or inaccurate submissions can have compliance implications. In publicly funded contexts, they can also affect funding calculations.

There are three primary reporting points in the school year:

• Last school day of October — the main enrolment count date, especially important for publicly funded school board funding calculations
• Last school day of March — the second enrolment count date, used to update and verify enrolment data
• Last school day of June — used for year-end reporting, including final course, achievement, and independent study data where applicable

For the October and March count dates, the Average Daily Enrolment or Full-Time Equivalent reported in OnSIS must match what appears in the school’s enrolment register for each pupil on that day.

Discrepancies between these two records are one of the most common causes of submission errors and later corrections.

Key OnSIS Compliance Principles

OnSIS compliance depends on more than submitting data by the deadline.

Schools need a consistent process for collecting, checking, protecting, submitting, and correcting information.

1. Data Accuracy

Accurate data is the foundation of the entire reporting process.

Schools should regularly review what their student information system records before each submission window. Waiting until submission day creates unnecessary pressure and makes errors harder to trace.

Student records, enrolment details, course information, educator records, and attendance data should all be reviewed before the reporting period closes.

2. Privacy Compliance

The privacy obligations around education data are becoming more formal.

For school boards governed by MFIPPA, Bill 97 received Royal Assent on April 24, 2026, and introduced amendments that will come into force in stages. These include new requirements related to privacy impact assessments, breach reporting, and oversight by the Information and Privacy Commissioner of Ontario.

For private schools covered by PIPEDA, the focus should be on clear consent practices, responsible handling of personal information, internal access controls, and appropriate protection of data submitted to the Ministry.

Regardless of which legislation applies, every school should be able to answer four basic questions:

• What personal information do we collect?
• Why do we collect it?
• Who can access it?
• How do we protect it?

Those questions are simple, but they reveal whether the school’s privacy practices are clear enough to support provincial reporting.

3. Matching Records

The FTE and enrolment data reported in OnSIS must match the school’s internal enrolment register at each count date.

This should be a formal verification step before every submission.

If OnSIS and the enrolment register show different information, the school may need to investigate, correct, and resubmit data. That can create extra work during an already time-sensitive reporting period.

4. Submission Format

Where schools submit OnSIS data through batch files, the files must follow the Ministry’s required XML format.

Formatting errors can lead to rejected submissions, even when the underlying information is correct.

If your student information system generates OnSIS batch files, confirm that it uses the current schema. Format requirements can change, and old templates or outdated exports may no longer meet Ministry expectations.

5. Secure Transmission

Every OnSIS submission should be treated as a sensitive data transfer.

Schools should use approved submission methods and maintain internal access controls so that only authorized staff can prepare, review, and submit data.

This is especially important because OnSIS data may include personally identifiable student and educator information.

6. Prompt Error Correction

If a submission contains errors, schools should correct and resubmit the data as quickly as possible.

Leaving inaccurate information uncorrected can affect both the school’s records and the wider provincial data set.

A clear correction process also helps schools respond faster when the Ministry flags an issue or requests clarification.

7. Staff Training

The staff members responsible for student information systems and OnSIS submissions need to understand both the technical requirements and the regulatory context.

This includes knowing where the data comes from, how it is checked, which fields are required, how submissions are validated, and what to do when errors appear.

The Ministry provides training resources inside the OnSIS portal. Schools should revisit those resources when new school year guidance is published.

8. Data Retention

Schools should maintain records of every OnSIS submission.

Accessible submission records are important for audits, discrepancy resolution, internal review, and future reporting cycles.

Retention practices should align with Ontario’s applicable data retention requirements and the school’s own privacy obligations.

9. Small School Considerations

Small schools should be aware that the Ministry suppresses data in public-facing reports when fewer than 10 individuals are represented in a given category.

This is a privacy protection. It is not a reporting exemption.

The school still submits the required data. The Ministry controls how that data appears publicly.

How MySchool Supports OnSIS Compliance

Managing OnSIS compliance manually can be demanding.

Schools need to track reporting dates, keep student and educator records accurate, check enrolment and attendance data, prepare information in the required format, review errors, and keep submission records accessible.

MySchool’s Provincial Reporting module is built to support this work.

It helps schools automate data collection, prepare reporting data, and reduce the risk of errors by pulling information from connected SIS, attendance, and tuition modules into pre-built templates. The module also includes validation tools, error checking, compliance dashboards, secure data handling, direct SIS integration, and export features that support the school’s OnSIS submission process.

For Ontario schools, this means OnSIS reporting can sit closer to the data schools already manage every day.

Student records, enrolment information, attendance data, and achievement records do not need to be managed as disconnected reporting pieces. When the data is connected and easier to check, the reporting process becomes more controlled and less dependent on manual work.

If your school is navigating the 2025–26 submission cycle or preparing for 2026–27, MySchool can show how its platform helps schools prepare reporting data for Ontario reporting requirements.

Request a Demo →