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 topics

When are records are 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. Once a provider supplies the necessary information to resolve the SV error, then the message will be deleted from the notifications table so that at any point in time, the notification table will only have scheduled validation messages that relate to data that is still incomplete or inconsistent. That is, SV messages will only appear on the notifications table by exception. 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 system-generated scheduled validations executed?

System generated scheduled validations are executed overnight. For example, if the trigger date for a record is 24 March, the relevant scheduled validation will be executed overnight (between 6pm, 24 March and 6am and 25 March) so that the results of the scheduled validation are available for action by users from 6am, 25 March.

If a provider amends a record that has been subject to a scheduled validation, the re-execution of scheduled validations will also occur overnight. So, if the record was amended before 6pm on 28 March, the results of the re execution will be available from 6am on 29 March, at the latest.

Scheduled Validations search

ITSP Error Code	Title	Element No	Event
SV00056	Scheduled Validation SV00056	E661	OS-HELP Debt Incurral Date
SV00057	Scheduled Validation SV00057	E319	OS-HELP Debt Incurral Date
SV00058	Scheduled Validation SV00058	E347	OS-HELP Debt Incurral Date
SV00059	Scheduled Validation SV00059	E572	OS-HELP Debt Incurral Date
SV00060	Scheduled Validation SV00060	E612	OS-HELP Debt Incurral Date
SV00061	Scheduled Validation SV00061	E573	OS-HELP Debt Incurral Date
SV00062	Scheduled Validation SV00062	E574	OS-HELP Debt Incurral Date
SV00063	Scheduled Validation SV00063	E416	OS-HELP Debt Incurral Date
SV00066	Scheduled Validation SV00066	E315	SA-HELP Debt Incurral Date
SV00067	Scheduled Validation SV00067	E316	SA-HELP Debt Incurral Date

Report data

Scheduled Validations topics