Cycle 2.1 Tax File Number (TFN) declaration taxonomy release
- Introduction
- Cycle 2.1 TFN declaration taxonomy downloads
- Cycle 2.1 TFN declaration taxonomy architecture & harmonisation
- Taxonomy architecture overview
- Summary of taxonomy architecture key features
- Key differences from SBR's Cycle 1 prototype taxonomy
- Harmonisation
- Glossary
Purpose
The Cycle 2.1 TFN declaration taxonomy has been developed to enable software developers to further work with the SBR Program to develop the TFN declaration pilot release. It also provides a mechanism for other interested stakeholders to provide feedback about the taxonomy as it is being developed.
This taxonomy reflects improved quality and maturity in the taxonomy architecture and in the taxonomy content compared to the Cycle 1 prototype taxonomy released on 31 March 2008. For example, business definitions and references have been improved and new data classification concepts have been introduced.
The TFN declaration pilot will commence in January 2009, prior to delivery of the production version of the TFN declaration in June 2009.
SBR's Cycle 2.1 TFN declaration taxonomy builds on the lessons learned from the Cycle 1 prototype taxonomy, incorporating feedback provided by software developers, accountants, bookkeepers, participating agencies and other SBR stakeholders.
Pending feedback received and the results of a planned review, the content of this taxonomy is not expected to change significantly leading up to the release of Cycle 2.2 taxonomy in September 2008. Additional supporting specifications, including a Message Implementation Guide to support the message exchange for this taxonomy, are currently under development in consultation with interested software developers. It is anticipated that these specifications will be available with future releases.
What is the TFN declaration taxonomy?
The Cycle 2.1 TFN declaration taxonomy is a structured list of reporting definitions, rules and relationships that will support the TFN declaration pilot. This structured list will enable efficient, reliable communication between business and government.
The TFN declaration taxonomy reflects:- 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);
- an enhanced understanding of how to identify and resolve complex taxonomy architecture and engineering issues (e.g. use of tuples and dimensions)
- developing skill and expertise in the multi-agency SBR development team; and
- work on the alignment and suitability of standards (e.g. Australian Standard 4590 for party identity, name and address information).
Scope
The TFN declaration taxonomy is limited to the metadata content of the Australian Taxation Office's TFN declaration. Metadata for other forms in scope of SBR will be included in future versions.
The Magnetic Information Processing Services (MIPS) / Electronic Commerce Interface (ECI) specification for electronic lodgement has been used as the basis for the development of the taxonomy.
SBR's TFN declaration taxonomy utilises the XBRL dimensions specification version 1.0.
What is not in scope
The TFN declaration taxonomy does not utilise all of the XBRL technologies. For example, formula linkbase and rendering specifications have not been incorporated into the Cycle 2.1 TFN declaration taxonomy.
What SBR is asking software developers to do
SBR is inviting software developers and interested stakeholders to provide feedback on the TFN declaration taxonomy. In particular, SBR would like your views on:
- taxonomy structure and architecture:
- Is the structure and architecture of the taxonomy intelligible and usable?
- Is the information classification structure appropriate for your needs?
- taxonomy content:
- 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?
The supporting specifications to enable the message exchange are currently under development with the assistance of software developers. Accordingly, at this stage of taxonomy development SBR is not expecting developers to create XBRL instances using this taxonomy.
Please forward any comments/feedback to SBR by Friday, 15 August 2008.
