Skip to main content

APRA Connect Taxonomy Artefacts

Last updated: 19 August 2021

APRA Connect taxonomy artefacts are provided to help entities prepare data for submission on APRA Connect. 

The artefacts include the data dictionary, validations, reporting taxonomy and XSD (to validate files).

Artefacts should be used in conjunction with the relevant reporting standard. Where there is a difference between the artefacts and the reporting standard, the reporting standard should be referenced for final versions of definitions and reporting instructions.


On 25 March 2021, APRA released the response paper and 10 final reporting standards for the first phase of its multi-year Superannuation Data Transformation (SDT). The Response Paper and finalised reporting standards are available at: Consultation on APRA's Superannuation Data Transformation.

These new collections will be reported through APRA Connect

Published 19 August 2021

Private Health Insurance

HRS 605.0 Private Health Insurance Reform Data Collection, commenced in March 2021, collects information on a private health insurer’s (PHI’s) implementation of the Government’s private health insurance reforms announced in October 2017.

Published 19 August 2021

Provides an overview of the APRA Connect taxonomy artefacts. 

Expression Functions Guide

The Expression Functions Guide describes the Expression function used in the validation of data submitted via APRA Connect and should be used in conjunction with the published taxonomy artefacts.

Expression functions execute standard logical/mathematical/date/string functions. Each type of expression is described in detail.

Updated 15 June 2021

Explanatory Notes 

The following explanatory notes are to assist entities in using the artefacts.

Data dictionary

The APRA Data Dictionary contains all the elements and their properties used in the collections in APRA Connect. The Excel based data dictionary includes detailed properties of data types and enumerations; this information can be used by entities when setting up their own systems and processes for defining data. 

Reporting taxonomy

The Reporting Taxonomies contain all the elements and their properties, relevant to the selected collection. The Excel based reporting taxonomy includes the following worksheets:

  • 'Schema’ contains the collection name, schema properties and the embedded hole constraint file which displays each table and the allowed values that are relevant in the selected collection.
  • ‘Elements’ contains only the elements and their properties that are relevant in the selected collection.
  • ‘Data types’ contains the data types that may be used for each of the defined elements within the selected collection. Each data type is either based on a specific base data type or is an enumeration.
  • ‘Enumerations’ contains the enumerations in the selected collection, along with all of the allowed values (regardless of the selected collection).
  • ‘Form Set’ contains detailed information for the return name and label (used throughout APRA Connect to identify the return).
  • ‘Folders’ contains (where relevant) detailed information for a return that can include multiple instances of the same form (for example, State based forms).
  • ‘Forms’ contains properties for the forms in a return.
  • ‘Rules’  contains rules relating to the selected collection. A full list of rules – across all collections - is available in the Validation Rules spreadsheet.
  • ‘Entity Details’ displays the layout of the form that captures the entity specific Name, ABN and Reporting End Date. This worksheet can be used as a template for entities uploading via Excel.
  • Form layouts for each of the specific forms in the selected collection. This worksheet can be used as a template for entities uploading via Excel. For example, the worksheet may be titled SRF_705_0_Table_1 in the Performance Components collection for Superannuation.

Validation file

The Validation Rules file contains details of the validation rules, relevant to the selected industry, including:

  • ‘Rule ID’ is a unique identifier for each rule.
  • ‘Rule Name’ will be shown in APRA Connect when a rule is triggered (if APRA hasn’t provided a name, the Rule ID will show instead).
  • ‘Rule Version’ will indicate the version of the rule.
  • ‘Schema Name’ references the schema name specified in the corresponding Reporting Taxonomy.
  • ‘Business Description’ is a simple, plain English description of the validation rule.
  • ‘Error Message’ is the failure message that will be displayed when the rule triggers; APRA Connect syntax is used to dynamically change the text displayed. The syntax is based loosely on the Excel formula syntax.
  • ‘Section rule applies to’ references the specific table or List (which can be found on the Elements tab of the corresponding Reporting Taxonomy) that the rule relates to. If the rule is evaluating multiple tables, this field will reference the entire form.
  • ‘Rule Type’ indicates if the rule is an Error and has to be resolved before submitting or a Warning that entities must provide an explanation for the discrepancy in order to submit the return.
  • ‘Rule Expression’ is the failure expression that is evaluated; APRA Connect syntax is used to define the rule. If the expression returns false, it means the rule has failed and the failure message will be displayed.
  • ‘Rule Constraint’ is an expression that will restrict the rule from evaluating in certain circumstances; APRA Connect syntax is used to define the constraint. If the constraint expression returns true or is empty the validation rule will execute.

XSD files

The purpose of the XSD file is to validate the XML file being uploaded to APRA Connect. Each draft XSD file contains important information including:

  • GUID is the unique identifier for the collection and should be included in the header of any XML file that will be uploaded into APRA Connect.
  • Version number identifies the version of the collection and should be included in the header of any XML file that will be uploaded into APRA Connect.
  • The XSD can be used by entities in third party software to generate and validate XML files.
  • The XML schema is W3C compliant.

Summary of XSD files and corresponding reporting standard and collection name. 


Reporting Standard

Collection name

XSD file name


SRS 605.0

RSE structure



SRS 606.0

RSE profile



SRS 611.0

Member accounts



SRS 705.0

Performance components



SRS 705.1

Performance benchmark



SRS 550.0

Asset allocation



SRF 251.0

Insurance arrangements



SRS 706.0

Fees and costs



SRS 332.0




SRS 605.0 and SRS 706.0



Private Health Insurance

HRS 605.0

Private Health Insurance Reform Data Collection


Subscribe to our APRA Connect updates

You can register for APRA Connect email updates straight to your inbox.  

Contact us

You can contact us at