Interim guidance for TCSI address validations

As G-NAF relies on government-supplied data, some addresses, particularly those associated with new developments, subdivisions, or private campuses with internally managed addresses, may not yet be included or fully matched. As a result, an address may be commonly used but unavailable within G-NAF. 
 

G-NAF validates physical addresses using official government address datasets and does not validate whether an address appears in third-party mapping services or is recognised for mail delivery purposes. Services such as Google Maps and Australia Post use different data sources and may recognise addresses not currently included in G-NAF. 
 

Where this occurs, providers should ensure addresses are recorded in their official format and, where possible, use the address recognised by the relevant state or territory address authority.

Example

A student commencing Semester 2, 2026, reports a residential address in an apartment building completed and occupied in July 2026. Whilst the building may already be recognised by navigation and postal services, the address may not yet be reflected in the version of G-NAF available to TCSI. In these circumstances, the address may receive a low confidence score.

Addresses associated with new subdivisions, recently completed developments, or private roads may not always be available in G-NAF, as the dataset relies on address information supplied by government authorities and may not immediately reflect recent changes. Similarly, large private campuses, such as universities, hospitals, and business parks, may use internally managed roads or address schemes that differ from officially registered addresses. As a result, an address may be commonly used but not yet included in, or fully matched by, G-NAF. Where an address cannot be validated, providers may wish to confirm whether an alternative officially registered road name, property number, or address format is available for the location. Providers should ensure the address is recorded in its official format and, where possible, use the address recognised by the relevant state or territory address authority.

G-NAF is designed to validate physical locations and does not contain Post Office (PO) Box addresses or other postal delivery information. As a result, PO Box addresses cannot be geocoded and will not meet address validation requirements. Providers should ensure the Residential Address Street (E410) reflects the student's physical residential address, rather than a postal address, temporary accommodation, or PO Box. 
 

Scheduled Validations will correctly trigger where a PO Box has been reported as a residential address. Where a student has only supplied a PO Box address, providers should contact the student and obtain their residential address prior to reporting.

Suburbs are an officially recognised locality used in Australian addresses, whereas districts are broader geographic or administrative areas that contain multiple suburbs and may not pass G-NAF validation checks. Providers should ensure that addresses reported to TCSI use suburbs and not districts. Where a district has been provided, providers should contact the student to obtain the correct suburb and address information.

Example:

A student reports their suburb as "Coastal Plains" when the residential address is actually located within the suburb of "Seabrook" (which is locally considered to be contained within the Coastal Plains district).

Providers should ensure that residential addresses are reported in the correct format and accurately reflect the student's residential address. Incorrect formatting, spelling errors, inconsistent street naming conventions, or differences between reported addresses may result in lower G-NAF confidence scores and address validation notifications. Where an address receives a low confidence score or fails validation, providers should review the reported address and, if necessary, contact the student to confirm and correct the address details.

Example: 

A student's address is reported as "15 Smith Streeet" (‘e’ x3) instead of "15 Smith Street", or "25 River-Gum Road" instead of "25 River Gum Road". Whilst the addresses may still refer to the same physical location, spelling errors and formatting differences can affect address matching and confidence scores returned by G-NAF.

G-NAF maintains a standard list of street types and their accepted abbreviation codes (for example, Place and PL). Providers should ensure street names and street types are reported using a G-NAF-recognised format, as non-standard street types, abbreviations, or formatting may affect address validation outcomes. Where an address fails validation, providers should review the reported street type and ensure it aligns with the corresponding G-NAF street type or accepted abbreviation. 
 

TCSI Support is currently investigating an issue where some accepted street type abbreviations may receive different validation outcomes or confidence scores despite referring to the correct street type. Whilst this issue is being investigated, providers may wish to report either the full street type or the accepted abbreviation code to determine whether this improves the confidence score. Alternatively, providers may choose to wait for the outcome of the investigation before making any changes to affected records. 
 

Providers should note that this issue has only been observed in a relatively small number of cases throughout the on-going investigation. Where an address continues to receive a validation notification regardless of whether the full street type or accepted abbreviation is reported, providers should review all other address components to confirm they have been reported correctly. Providers should not automatically assume that the issue with the reported street type and its accepted abbreviation is the cause of the Schedule Validation.

Some non-standard address types, including lot addresses and community addresses, may not be readily recognised by G-NAF and can require additional investigation to identify a corresponding physical location. These address types often occur in rural, remote, or developing areas where standard street numbering or address arrangements may not exist or may differ from conventional address practices. TCSI Support is currently investigating these address types and will provide further information and guidance as it becomes available.

Providers that have made all reasonable efforts to resolve low address validation scores should note that a previously geocoded result with a high confidence score from an earlier reporting period may be used if available. If no high-confidence geocoded result exists, the postcode of the student's reported residential address (either first or current) will be used to determine SES status. Providers should nevertheless continue to resolve address validation issues wherever possible, noting that postcode-based assignment will be applied where addresses remain unvalidated in TCSI.
 

Address validation notifications are intended to support data quality improvements and are not designed to prevent providers from reporting data where reasonable efforts have already been undertaken to obtain and report a valid residential address.

Addresses associated with newly constructed properties, recent address changes, or newly created subdivisions may take time to be reflected within G-NAF datasets. Where a provider has confirmed an address with a student, but validation issues remain, providers should ensure the address has been reported correctly and monitor future validation outcomes as address reference data is updated.

Example: 

A property previously reported as "2 Parkview Road" is subdivided into two newly created residential lots, resulting in addresses "2A Parkview Road" and "2B Parkview Road". Whilst subdivision works have recently been completed, the newly assigned addresses may take time and not yet be reflected in all address reference datasets and may receive address validation notifications until updates occur.