PAGE LAST UPDATED:

Regulated entities use multiple systems managed by us and the Department of Infrastructure, Transport, Regional Development, Communications, Sport and the Arts (the department) to meet their obligations under the New Vehicle Efficiency Standard Act 2024(Opens in a new tab/window) (NVES Act). These are:

  • ROVER
  • Register of Approved Vehicles (RAV)
  • NVES Portal
  • NVES Unit Registry.

We cover these systems below.

ROVER

ROVER(Opens in a new tab/window) is the administration system for the Road Vehicle Standards Act 2018(Opens in a new tab/window) (RVSA) and is managed by the department. Regulated entities and their authorised users use ROVER to:

  • Submit and pay for a ROVER application.
  • Monitor the progress of a ROVER application.
  • Authorise other users to act on their behalf through an ‘authority to act’.
  • Enable an NVES management permission.
  • Access the NVES Portal.
  • Receive and respond to requests for information on a ROVER application.
  • Receive ROVER application decision notifications.
  • Submit NVES-specific vehicles to the Register of Approved Vehicles (RAV).

Register of Approved Vehicles (RAV)

The RAV is managed by the department and sits within ROVER. It is an online publicly searchable database of vehicles that have met the requirements of the RVSA and been approved for provision to the Australian market.

All road vehicles must be entered on the RAV before being provided to the market for the first time.

Regulated entities enter NVES-specific data on the RAV as part of their obligations under the NVES Act, this data is used to calculate an entity’s interim emissions value (IEV) at the end of each performance period. The data entered on the RAV will become available in the NVES Portal for an entity to manage their compliance with the NVES.

Watch this video learn more about how to enter NVES-specific data on the RAV:

NVES Portal

We manage and maintain the NVES Portal (the portal) which is accessible via ROVER. It is a central online portal where entities can fulfil a number of functions to support their compliance obligations under the NVES Act. Entities access the NVES Portal by logging into ROVER: Welcome to ROVER(Opens in a new tab/window).

It is through the portal a NVES Unit Registry (unit registry) account can be applied for. This includes the fit and proper person (FPP) declaration required for completion as part of their application for a unit registry account.

In the first release the portal allows entities to:

  • Access to the portal.
  • Apply to open a unit registry account, including submitting your FPP declaration.
  • View your NVES vehicle data as entered on the Register of Approved Vehicles (RAV).
  • View your emissions performance over time.
  • View requests for information from us.
We are still developing the portal’s functionality with more releases planned over the coming months. There are limitations on what you can currently do in the portal.

In the first release users won’t be able to:

  • Assign unit registry permissions. This will become available once your organisations’ unit registry application is approved by us.
  • Use your unit registry account to make transactions. This will become available prior to units being issued from February 2026.
  • Reply to requests for information from us in the notifications page. Instead entities will need to email their responses to us at NVESRegulator@infrastructure.gov.au.
  • Update executive officer and secondary contact details.
    • Save progress of your unit registry application forms. You will need to complete and submit your application in one session. We encourage you to read the FPP guidance before starting your application, to help you complete and submit it in one short session.

You can download the NVES Portal user guide – Version 1 (Word 6.83 MB | PDF 3 MB) for guidance on accessing and navigating the portal.

Watch this video to learn more about the functionality in the NVES Portal:

Roles and access in the portal

Roles and permissions in the portal draw on existing roles and permissions in ROVER(Opens in a new tab/window).

To access the NVES Portal, entities must have an active ROVER account and an ‘NVES management’ permission enabled under their authorised user’s ‘authority to act’.

Entities can assign more than one authorised user in ROVER, including an agent to act on their behalf. If their authority to act expires (this is a default of 2 years) or is removed, they will also lose their NVES management permission and access to the portal.

NVES Unit Registry

The unit registry sits within the portal and will be made available from February 2026. The first units will be issued when entities receive their first interim emissions value (IEV) from February 2026 for the 2025 performance period.

We manage and maintain unit registry operations and access to ensure fair participation and to prevent misconduct. It is where units are issued, transferred and extinguished.

To receive units, entities need to beat the requirement for the performance period. To be able to receive, transfer and extinguish units, they will need to apply to open a unit registry account in the portal. Access to the unit registry is pending upon successful application and approval from the NVES Regulator and passing an FPP declaration.

Unit registry permissions

There are 4 main permissions types for unit registry accounts, they are:

  1. Registry viewer: a registry viewer can only view unit transactions and unit balances. If assigned this permission a user cannot hold any other permission.
  2. Transfer initiator: a transfer initiator can view the unit registry and initiate unit transactions for their account.
  3. Transfer authoriser: a transfer authoriser can view the unit registry and authorise unit transactions created by a different user. They cannot authorise a unit transaction they make. They will then submit the authorised transaction to the regulator.
  4. Registry account admin: a registry account admin can view the unit registry and add or remove users to the unit registry account. They must make sure any new users complete the FPP declaration to gain access.

Entities can also choose to assign an optional contact role in the unit registry, this is a unit trading contact. This is where a user is assigned as a point of contact for unit trading for an entity they represent. They can be nominated by email to their NVES Account Manager who will set it up.

These permissions allow entities and their authorised users to undertake a variety of actions. Users can hold more than one permission, unless they have been allocated as a ‘registry viewer’. In this case they cannot hold any other permission.

While one user may hold both transfer Initiator and transfer authoriser roles, they cannot authorise the transfers that they have initiated.

The roles can be assigned in the unit registry once the account has been opened from February 2026.

Opening a NVES Unit Registry account

Apply

Regulated entities and their authorised users can apply to open a unit registry account. This application is done via the NVES Portal.

The application includes an FPP declaration. The applicant will need to fill out the NVES Unit Registry account application form, which requires them to make 2 legal FPP declarations. These are for:

  • The regulated entity (as the legal person holding the registry account).
  • Themselves (as the individual authorised to apply for the account).

The FPP questions relate to aspects of financial and company management, convictions, and behaviour. Answering ‘yes’ to any of these questions does not automatically result in an entity being ineligible to open a registry account.

Assess

Once submitted, we will assess all registry account applications. We may ask the applicant to provide further information to support their application.

Before we can decide to open an account, we have to be satisfied the entity and the applicant:

Decide

Based on our assessment of the application, we will decide whether to open a registry account for the regulated entity. We will notify the entity of our decision in writing.

Once an entity’s registry account is opened, the user with a ‘registry account admin’ role can provide access to additional authorised users. The registry admin must ensure each user has completed an FPP declaration.