TCSI Notifications Feature
Meshed TCSI Notifications Feature
When a provider submits data, TCSI tries to respond (in near real time) with error or warning messages if the data is incorrect or inconsistent with what’s in the system.
Some notifications are not real-time (e.g. when checks rely on external systems like the ATO in those cases messages are posted to the provider’s notification table for later retrieval.
The Notifications page is now available under the TCSI tab on the homepage. This can be used for clients where there is TCSI API integration being used to report data to TCSI. The notifications set on the provider table can be directly retrieved using the Meshed system without a need to check the data manually in the TCSI portal.
To access the Notifications Page, go to TCSI tile on the homepage >> Notifications
The page allows users to retrieve real-time notifications or validations from TCSI based on the notifications that TCSI generate for the reported data. Any scheduled validations that TCSI provides can be retrieved using this feature.
There are 2 types of notification filters available for the users, Real-Time Notifications and Offline Notifications.
The Real-Time Notifications bring data directly from TCSI API as shown below. The user is also able to export the TCSI Notifications using the Export Button as shown below
The Offline Notifications will bring any notifications data that was already checked and is now stored in the database.
If a provider has more than one reporting type such as a combination of VSL and HEP, they must select the correct reporting type when running the notifications.
The table below contains a list of columns along with their descriptions
Column Name | Description |
Date Added | This indicates the date the notification was added for the provider |
Date Accessed | The date and time when a provider first retrieved or viewed a specific notification |
Notification Category | The type or category of the notification such as SVE |
Notification Text | The actual message or notification |
Notification Status | Status reflects the current state in the data issue lifecycle — i.e., whether it has been seen, resolved, or still requires action |
Origin | The source or system that generated the notification. For example, USI_VERIFICATION |
Packet | This specifies the packet the notification is generated for |
Entities UID | These are the UIDs or TCSI reference number of the records that have the respective validation error. You can now use the entities UID to search directly in the main reporting grid |
Meshed TCSI Reference | This field shows the respective data field name in Meshed. Based on the TCSI Entities UID, if the data exists in Meshed, the Meshed TCSI reference column will show a value |
Types of notifications & what they mean
The following are some examples of notifications that the user may see:
Scheduled Validation Errors: data that was supposed to be reported is missing or the element is past deadline.
TFN Verification Errors: Tax File Number mismatches or verification failures.
USI Verification Errors: mismatches or invalid USIs (Unique Student Identifiers).
Loan Rejections / Adjustments: notifications about student loan record validity, limits, or rejections under HELP / VSL etc
Warnings / Loan Limit Warnings: alerts before errors are fatal, e.g. approaching caps.
CHESSN errors / allocations (although CHESSN is being phased out) — earlier, notifications about CHESSN being allocated or errors in CHESSN.
The Notifications appear till the user has acted upon them and the related data packet has been updated.
For example, a TFN message is removed once the TFN is verified or a new TFN is reported. Scheduled validation messages are removed after overnight processing if the issue is fixed.