For TCSI Data Entry users

Services Australia (SA) and the department are conducting TCSI Data Entry testing internally.

Providers can test TCSI Data Entry by creating file templates for Higher Education and VET Student Loans data packets, and sending the templates to TCSIsupport@education.gov.au. The TCSI Data Collections team can upload these templates on your behalf using a test account.

For providers who are conducting TCSI testing using an API method, please see our For API users page.

You can access these Higher Education and VET Student Loans templates using the following links:

A video tutorial to prepare TCSI Data Entry templates is available in our News Centre.

After you have submitted a TCSI Data entry template to the TCSI Data Collections team, we will provide you a response file with the status of the data you have submitted.

If your submitted data returned any errors, you can use the resolving real-time validations guide to help you correct these errors.

Topics related to testing in TCSI

Testing file uploads using TCSI Data Entry

TCSI Data Entry file uploads can ONLY be tested via TCSI Support. There are four steps to testing with us:

1. Nominate a test account

If you tested with TCSI in the past: please nominate the provider code for your test account.

If you only plan to test file uploads and do not have a test account, please proceed to step 2.

If you plan to test an API solution: follow the Setting up a test account guidance.

2. Email TCSI Support with your test files attached

Prepare files following the guidance on the Using TCSI Data Entry page and email with the provider code to TCSIsupport@education.gov.au.

Ensure you safeguard private information by applying the Test data considerations

3. Check the response file

It can take one to two business days for TCSI Support to submit the file on your behalf and return a response file by email.

The response file will detail the outcome of each record and list validations returned in the test environment.

4. Check the stored data

You can send a data extract request to confirm the data stored in your test account.

Make sure you use the same provider code as in step 1 (select 'other' if your test account is not in the list) and select the 'test environment' option in the form.

Establish test data

Whilst actual live or production data should not be used for testing purposes, providers can consider using de-identified data, with the acknowledgement and confirmation of certain conditions. These conditions are:

The provider is sufficiently satisfied that the data has been de-identified in such a way that it cannot be un-scrambled or re-identified
In the event that this data is published or exposed externally, the provider maintains no concern to its privacy or security sensitivity. Essentially, the government will treat this data as unclassified material
In the event that data is able to be un-scrambled or re-identified, the provider holds all responsibility for this and any associated implications.

The department strongly advises providers to seek internal legal advice prior to exploring the usage of de-identified production data for testing in the TCSI test environment.

Mock CHESSN, TFN and USI

Commonwealth Higher Education Student Support Number (CHESSN)

Mock CHESSNs will be allocated in the test environment according to the CHESSN Management in TCSI guide. Reporting sufficient information against a student record will result in a mock CHESSN being allocated.

Tax file number (TFN)

Providers and developers can generate mock TFNs for testing. To reduce interaction between test accounts, the TFN must begin with the test provider code assigned for your test account. TFNs will verify if the final digit is an even number (2, 4, 6, or 8). All other final characters will return verification fail messages.

TFN must start with test provider code and end with an even number to verify

Unique Student Identifier (USI)

For assistance acquiring mock USIs, please see the System Developers - USI System and Support page via the Office of the Student Identifiers Registrar.

Report data

For TCSI Data Entry users

Topics related to testing in TCSI