APRA Connect Taxonomy Artefacts
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.
APRA has released draft technical information and supporting material relating to superannuation taxonomies to help entities prepare superannuation data for submission on APRA Connect data. Final versions of these documents will be available before the external test environment is released to entities in June 2021.
APRA has engaged industry through our regular forums to gain feedback on the approach to publication of artefacts. Whilst our proposal to release a package of artefacts was welcomed by entities, they asked to view draft artefacts in advance of the final release, to guide the commencement of data preparation work.
The draft artefacts include the data dictionary, validations, reporting taxonomy and XSD (to validate files). While every effort has been made to ensure accuracy, entities can expect further changes before APRA Connect go live.
Final versions of this information will be available prior to the release of the external test environment in June. Additional taxonomy information will be progressively released for other new collections on APRA Connect.
You can access the artefacts below.
Alignment of the draft taxonomy artefacts and the final reporting standards
Draft taxonomy artefacts are based on the current version of APRA Connect, which does not yet reflect the full final version of the reporting standards. The differences between the draft artefacts and the final reporting standards are minor in nature and will be reflected in the next version of the artefacts. For the avoidance of doubt, entities should note that final reporting standards should be referenced for final versions of definitions and reporting instructions.
The differences between the reporting standards and the draft artefacts can be categorised into: material and cosmetic differences (described below). APRA anticipates that entities may decide to manually account for these differences when progressing the build of data collections.
The differences are:
- Material change to expenses collection: the reporting standard contains a new element in Table 1 that is not in the current artefacts, called Service Provider Identifier. The Service Provider Identifier also replaces the Service Provider Australian Business Number in Table 2 and 3 of this form.
- Cosmetic changes to all collections: there will be minor wording differences between the reporting standards (including SRS 101.0 definitions) and the description and/or guidance in the elements and enumerations tabs for the data dictionary and the elements tab of all reporting taxonomies.
The following explanatory notes are to assist entities in using the artefacts.
The draft 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.
The current draft version of the data dictionary is applicable only to the new superannuation collections.
The draft 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 restrictions spreadsheet 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.
- ‘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 non-business rules relating to the structure of the table relevant to XML or XBRL (if applicable) uploads. Refer to the Draft Validation Rules spreadsheet for a full list of rules.
- ‘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.
- ‘SRF_#’ displays the layout of the specific forms in the selected collection. This worksheet can be used as a template for entities uploading via Excel.
The draft 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.
- ‘Error Message’ is the failure message that will be displayed when the rule triggers; APRA Connect syntax is used to dynamically change the test 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.‘.
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 contained within the zip file.
|Reporting Standard||Collection name||XSD file name|
|SRS 605.0||RSE structure||Draft SUP_uSTRUCT.xsd|
|SRS 606.0||RSE profile||Draft SUP_uPROFILE.xsd|
|SRS 611.0||Member accounts||Draft SUP_uMEMAC.xsd|
|SRS 705.0||Performance components||Draft SUP_uPERFCOMP.xsd|
|SRS 705.1||Performance benchmark||Draft SUP_uPERFBENCH.xsd|
|SRS 550.0||Asset allocation||Draft SUP_uAA.xsd|
|SRF 251.0||Insurance arrangements||Draft SUP_uINSAR.xsd|
|SRS 706.0||Fees and costs||Draft SUP_uFEECO.xsd|
|SRS 332.0||Expenses||Draft SUP_uEXP.xsd|