13 August 2021

What are notifications?

Notifications are generated by Submissions and acronym taxi to provide the following information:

Submissions
Notifications from Submissions provide information on the status of various processes and may include messages relating to problems with data.
acronym taxi
Notifications from acronym taxi are generated when acronym taxi needs to call on other systems, such as the acronymATO, to verify or perform completeness checks on submitted data.

Notifications are updated automatically every five minutes. However, you can manually refresh the notifications to retrieve the latest notifications at any time.

You can download notifications to Excel files for distribution, reporting, error correction, and so on.

Some example notifications are as follows:

  • Updates regarding student loan validations
  • acronymCHESSN allocations and updates
  • acronym taxi outages such as planned maintenance
  • System errors from Submissions. You can use information in these notifications when logging issues with Tribal Support.
Attention. Error and warning messages: You may also receive near real-time error or warning messages from acronym taxi if your submitted data is either incorrect or inconsistent with information already submitted. Error and warning messages are displayed on the records of data groups and are not notifications.

You can sort and filter the notifications to view the notifications of interest. For example, you can display all notifications showing when a student has been allocated a Commonwealth higher education student partnership number by filtering the notification Category by category code c h a.

The image Notifications page illustrates the layout of the Notifications page after you log in to Submissions.

Notifications page
Notifications page

Example: acronymTFN reporting and notifications

The diagram acronymTFN reporting scenarios illustrates the reporting flow from when the acronymTFN is recorded in the student management system, reported in Submissions, submitted to acronym taxi, then sent to the acronymATO. The diagram also illustrates when notifications are sent from acronym taxi to the acronymATO for verification, and when the acronymTFN passes and fails verification.

acronymTFN reporting scenarios
Acronym TFN reporting flow between the student management system and the acronym ATO, including when notifications are sent from acronym taxi to the acronym ATO for verification, and when the acronym TFN passes and fails verification.