Scheduled Validations

Scheduled Validations (SVs) are about ensuring that records are complete and correct.

These completeness checks cannot be done through real time validations (RTVs) because the fields are effectively optional until the deadline date for higher education reporting and VET student loans reporting. Further scheduled validation checks are required because the sequence of reporting is incompatible with an RTV.

The scheduled validations work in conjunction with the RTVs. The scheduled validation prompts the provider to supply the data by the deadline and, once the data is submitted, the RTVs will check whether the values that have been reported are acceptable.

Scheduled Validations download

The links in this table will download the attachment
Attachment	Size
TCSI Notification Messages V1.0 (29 April 2025).xlsx (35.9 KB)	35.9 KB

Scheduled Validations topics

When are records first checked against the SV rules?

Records come into scope for being checked by SVs when the relevant trigger date is reached. This trigger date will be a set number of days before the deadline date for reporting. For example, the deadline for Unit enrolment data is 14 days after the census date. Completeness checks for Unit enrolment records will commence 7 days before the census date. This establishes a 'lead-in' of 21 days.

A diagram to demonstrate the 'lead in' time of 21 days for records being checked against scheduled validation rules.

Within the diagram, there is a trigger date, then after 7 days is a census date, and then after 14 days is a deadline date.

Once a record reaches a trigger date, that record and all records that are linked to it will be subject to the relevant scheduled validation rules.

What happens when an SV rule finds incomplete data?

Where a record fails a scheduled validation check, a message will be placed on the provider's notification table to indicate what data is missing or is inconsistent. Providers will need to update their records in TCSI to resolve the SV error. If there are no SV messages on the provider's notifications table, this means that the system has not identified any incomplete or inconsistent records for that provider.

When are scheduled validations re-checked?

Scheduled Validations search

ITSP Error Code	Title	Element No	Event	Packet
SV00116	Scheduled Validation SV00116	E558	Unit Enrolment Census Date
SV00119	Scheduled Validation SV00119	E592	Course Completion/USI verification
SV00121	Scheduled Validation SV00121	E339	Course Completion
SV00122	Scheduled Validation SV00122	E339	E534_CourseOfStudyCommencementDate
SV00123	Scheduled Validation SV00123	E490	E600_UnitofStudyCommencementDate
SV00124	Scheduled Validation SV00124	E392	Unit Enrolment Census Date
SV00126	Scheduled Validation SV00126 - Temporarily Disabled	E358	Unit Enrolment Census Date	Student packet 2025, Student packet (VET) 2025
SV00126	Scheduled Validation SV00126 - Temporarily Disabled	E358	Unit Enrolment Census Date	Student packet 2025, Student packet (VET) 2025
SV00127	Scheduled Validation SV00127	E584	Unit Enrolment Census Date	Student packet 2025, Student packet (VET) 2025
SV00127	Scheduled Validation SV00127	E584	Unit Enrolment Census Date	Student packet 2025, Student packet (VET) 2025

Report data

Scheduled Validations download

Scheduled Validations topics