Audience: SWD TWG
13th April 2017
IMPLEMENTATION UPDATE
ATO XBRL generated reporting taxonomies
The purpose of this document is to provide an update on the generation of ATO XBRL schemas (along with C#
instead of Schematron for technically consumable rules) and the standardisation of ATO contract schema
names.
Background




On the 8th December 2016, the ATO tabled at the TWG a strategy for moving forward with schema
naming (tabled as FYI only).
On the 28th February 2017 the information above was re-tabled along with the ATOs XBRL taxonomy
generated information.
The ATO Taxonomy Architecture and Naming Conventions document was formally published on 2nd
March 2017 here.
The intention was to move to the new ATO generated XBRL where a change was being made. ATO
XBRL reports generated by SBR prior to January 2017 that were not being updated would remain as
is.
Where we are at April 2017
At a glance

A number of messages have had changes applied to the structure for Tax Time 2017.

Schemas that were scheduled for the new ATO architecture had the schema naming as per the
documented standard in the Service Registry (i.e. ato.[message acronym].[collaboration].[year].
[action].[response].[major version].[minor version].report.xsd).

Due to the impacts of 1st July 2017 delivery caused by the ATO outages experienced in December
2016 and again in February 2017, eCSD has been unable to apply the ATO XBRL architecture to some
(five in total) messages that have undergone change.
Note:
Identifying the difference between SBR and ATO XBRL schemas is explained via the naming conventions (link in
point three of ‘Background’ above). To do this in the Service Registry, simply navigate to the ‘Message’ tab,
filter by Format (deselect ‘all’ and select ‘XBRL’), filter by schema (deselect ‘all’ and select those that start with
‘ato.’).
In detail
The following schema references in the Service Registry (due for publication Thursday 20th April 2017) have
been reverted to reflect SBR XBRL generation and the technical rule implementation will be Schematron.
Information
Domain
Client
Management
Client
Management
Employer
Obligations
Employer
Obligations
Income Tax
Returns - Nonindividual
Income Tax
Returns - Nonindividual
External
UNCLASSIFIED
Product
Interaction
cu
cumasadd.0003.2017.lodge
cu
cumascancel.0003.2017.lodge
ps
Request/
Response
Request
Collaboration
Schema
cumasadd.0003
cumas.0003.add.request.02.00.report.xsd
Request
cumascancel.0003
cumas.0003.cancel.request.02.00.report.xsd
ps.0004.lodge
Request
ps.0004
ps.0004.lodge.request.02.00.report.xsd
ps
ps.0004.prelodge
Request
ps.0004
ps.0004.lodge.request.02.00.report.xsd
trt
trt.0006.2017.lodge
Request
trtamis.0002
trtamis.0002.lodge.request.02.00.report.xsd
trt
trt.0006.2017.prelodge
Request
trtamis.0002
trtamis.0002.lodge.request.02.00.report.xsd
Page 1 of 2
Audience: SWD TWG
13th April 2017
Information
Domain
Income Tax
Returns - Nonindividual
Income Tax
Returns - Nonindividual
Income Tax
Returns - Nonindividual
Income Tax
Returns - Nonindividual
Product
Interaction
Request/
Response
Collaboration
Schema
trtami
trtami.0001.2017.lodge
Request
trtami.0001
trtami.0001.lodge.request.02.00.report.xsd
trtami
trtami.0001.2017.lodge
Request
trtamis.0002
trtamis.0002.lodge.request.02.00.report.xsd
trtami
trtami.0001.2017.prelodge
Request
trtami.0001
trtami.0001.lodge.request.02.00.report.xsd
trtami
trtami.0001.2017.prelodge
Request
trtamis.0002
trtamis.0002.lodge.request.02.00.report.xsd
What will happen post 1st July 2017?
In general

eCSD is still committed to:
o
Moving away from SBR XBRL generated reports where possible to the ATO generated
standard and technically de-coupling from the SBR AU Definitional taxonomy.

o
The ATO implementation will continue to use, and contribute to, the definitional
taxonomy terms to specify elements for an ATO reporting taxonomy.
Providing C# as the technical rule implementation moving forward.

This means Schematron changes will not be supported for non B2G transactions.
Tax Time 2018

Due to the relationships between Income Tax Returns (ITRs) and shared schedules, the ATO would
like to discuss an approach of SBR XBRL conversion to ATO architecture (or other format) at the May
2017 TWG.
Significant known/emerging projects

eCSD would like to propose a ‘domain’ approach of reviewing existing/emerging services, platform
deployments and formats, with a view (if feasible) to have more cohesive industry approach. This
approach is something that could be discussed at a high level in the May TWG or later.
Questions or concerns?
Please contact your Account Manager directly or email the TWG secretariat.
External
UNCLASSIFIED
Page 2 of 2