USI Registry System: Access, authentication & system requests
The USI Registry System provides secure access for:
- Education providers using the Organisation Portal
- System developers integrating via web services
This page explains how to access, authenticate, and request system access.
Accessing the USI Registry System
Functions Available in the USI Registry System
Organisations can:
- Create USIs
- Verify and bulk verify USIs
- Find USIs
- Use the Document Verification System (DVS) override
- View and update account holder details
- View organisational reports
Access levels by organisation type
| Function | RTO | VAB | VRB | HEP | TAC |
|---|---|---|---|---|---|
| Use DVS override | ✅ | ❌ | ❌ | ❌ | ❌ |
| Verify USI | ✅ | ✅ | ✅ | ✅ | ✅ |
| Bulk verify | ✅ | ✅ | ✅ | ✅ | ✅ |
| Find/locate USI | ✅ | ❌ | ❌ | ✅ | ✅ |
| View VET transcript | ✅ | ❌ | ❌ | ❌ | ❌ |
| Update details | ✅ | ❌ | ❌ | ❌ | ❌ |
| View organisational reports | ✅ | ✅ | ✅ | ✅ | ✅ |
Requesting system access
Who needs to apply?
Entities listed under Section 14 of the Student Identifiers Act 2014 must submit a System Access Request form to:
- Set up initial access
- Update provider details
- Apply for web services for an SMS
How to apply:
Submit a System Access Request
Updating organisation contact details
To update your organisation email or display name, email IT@usi.gov.au with:
- Organisation code
- Full name & position of requestor
- Authorising person's details
Authentication & Authorisation
How the USI Registry System authenticates users
The USI Registry System verifies Organisation ABN & Org Code before granting access.
Authentication methods:
- Organisation Portal Access – Requires a Digital ID (e.g., myID & RAM).
- Web Services Access (SMS Integration) – Requires M2M authentication.
For more information, visit: Digital ID & RAM Authentication Guide
Connecting to the USI Registry System
Option 1: Organisation Portal
For education providers accessing USI Registry via the website.
Option 2: Web Services (SMS integration)
For Student Management System (SMS) users integrating directly with USI Web Services.
Requirements:
- M2M authentication
- Developer testing before going live
Before Connecting:
- Ensure your organisation is listed on the correct government registers:
- Registered Training Organisations (RTOs) – Check training.gov.au (TGA)
- Higher Education Providers (HEPs) – Check the TEQSA National Register
- Your Australian Business Number (ABN) must match your registration details.
- If your ABN has changed, update your regulator's records before requesting access.
Read our full guide on accessing the USI Registry System
Obtaining developer & authentication kits
Step 1: Digital Partnership Office (DPO) authentication kit
Before applying for the USI Developer Kit, system developers must first obtain the DPO Authentication Kit.
For DPO Kit enquiries: Email dpo@ato.gov.au
Step 2: USI Developer kit
- After obtaining the DPO Kit, apply for the USI Developer Kit, which includes:
- Technical service contract
- Security Token Service (STS) definitions
- Checksum algorithm
- M2M authentication credentials for testing