October 2008 release note
Cycle 2.2 taxonomy release
Purpose
The Cycle 2.2 taxonomy release provides software developers with an opportunity to collaborate with the SBR Program during development of the TFN declaration pilot. It also provides a mechanism for other interested stakeholders to provide feedback about the taxonomy as it is being developed.
Compared to previous releases, this taxonomy features improved quality and maturity in the taxonomy architecture and content. For example, business definitions and references have been improved and new data classification concepts have been introduced.
SBR’s Cycle 2.2 taxonomy builds on the lessons learned from both the Cycle 1 prototype taxonomy, as well as the Cycle 2.1 TFN declaration taxonomy. It incorporates feedback from software developers, accountants, bookkeepers, participating agencies and other SBR stakeholders.
What is the 2.2 taxonomy?
The Cycle 2.2 taxonomy is a structured list of reporting definitions, rules and relationships that support 20 of the 95 SBR forms in scope. This structured list will enable efficient, reliable communication between business and government.
This taxonomy reflects:
Scope
The Cycle 2.2 taxonomy comprises both a definitional taxonomy as well as reporting taxonomies for certain forms/reports in scope.
The definitional taxonomy contains a complete set of harmonised data elements and associated definitions for data that is exchanged between business and government within the scope of all the SBR forms/reports. The definitional data elements are defined once and then re-used on various different agency reports.
The definitional taxonomy consists of the following forms/reports:
| Agency | Form Name |
| ATO | Tax File Number Declaration |
| OSR - QLD | Payroll Tax Annual Return |
| ATO | Activity Statement |
| ABS | Economic Activity Survey |
| ASIC | Copy of Financial Statements and Reports |
| APRA | Statement of financial performance |
| APRA | Statement of financial performance |
| APRA | Interest income and Interest Expense |
| APRA | Interest income and Interest Expense |
| ATO | Individual non business PAYG payment Summary |
| ATO | PAYG Payment Summary - Voluntary Agreement |
| ATO | PAYG Payment Summary - Labour Hire and other specified payments> |
| ATO | PAYG payment summary– personal services attributed income |
| ATO | PAYG payment summary– Employment termination payment summary data record |
| ATO | PAYG payment summary– Superannuation income stream payment summary data record |
| ATO | PAYG payment summary– Superannuation lump sum payment summary data record |
| ATO | PAYG payment summary– Departing Australia superannuation payment summary data record |
| ATO | PAYG withholding from interest dividend and royalty payments paid to non residents - Annual Report |
| ATO | PAYG Payment Summary- withholding where ABN not quoted |
| ATO | PAYG withholding annual report - payments to foreign residents |
The reporting taxonomy defines the specific interface for relevant agency reports. This is achieved by importing and re-using data elements and their associated definitions from the definitional taxonomy. The reporting taxonomy determines: what data elements are needed on each report; how the data elements should be structured for the report; what optionality is required for each data segment and data element; and what rules and validations should apply to the report. At this point, only one reporting taxonomy has been created for the ATO’s Tax File Number Declaration. The following forms will also be available in the “reporting” taxonomy over the coming weeks:
| OSR - QLD | Payroll Tax Annual Return |
| ABS | Economic Activity Survey |
| ASIC | Copy of Financial Statements and Reports |
What is not in scope
The Cycle 2.2 taxonomy does not utilise all of the XBRL technologies. For example, formula linkbase and rendering specifications have not been incorporated into the Cycle 2.2 taxonomy
What SBR is asking software developers to do
SBR is inviting software developers and interested stakeholders to provide feedback on the Cycle 2.2 taxonomy.
In relation to the “definitional” taxonomy, SBR would like your views on:
taxonomy content:
- the method, approach and systems that are expected to be employed in future SBR taxonomy developments
- improvements to the architecture, which are based on information classification (as opposed to the form/agency view of the data used in the Cycle 1 prototype taxonomy release) and subsequently builds on the Cycle 2.1 TFN declaration taxonomy
- an enhanced understanding of how to identify and resolve complex taxonomy architecture and engineering issues (e.g. use of tuples and dimensions)
- work on the alignment and suitability of standards (e.g. Australian Standard 4590 for identity, name and address information, International Financial Reporting Standard (IFRS) for financial data)
- Is the information classification structure appropriate for your needs?
- how the metadata is organised and presented:
- Are the definitions adequate and meaningful?
- Are the references adequate and appropriate?
- Are the labels adequate and appropriate?
- Is the presentation adequate and appropriate?
- mapping the taxonomy to software:
- Can you readily find the concepts in your business systems that can be mapped to this taxonomy?
- In relation to the other artefacts that will support the TFN Declaration Limited Release, SBR would also like your feedback on the following:
- SBR Taxonomy architecture document
- TFN declaration validation rules
- TFN declaration limited release implementation guide
- Example TFN declaration instance
- TFN declaration limited release Web Service Description Language (WSDL)
Please note, some of these artefacts will be released with the taxonomy. Other artefacts* are still being finalised and will be made available via the SBR collaboration environment over the coming week or will be emailed to you. The supporting specifications to enable message exchange are currently under development with the assistance of software developers and other interested parties. Accordingly, at this stage of taxonomy development SBR is not expecting developers to create XBRL instances using this taxonomy, (with the exception of software developers who are involved in the TFN declaration pilot.)
Please forward any comments/feedback to SBR by Friday, 7 November 2008.
Last updated: 19 Feb 2012
Page ID: 8446