If you have decided to develop SBR-enabled software you can follow the SBR Software Developer Journey.
Download a full view of the SBR Software Developer Journey.
The SBR Software Developer Journey will assist you to identify the tools or services to facilitate each step from Discovery of SBR through to delivery of an SBR-enabled product. These steps are illustrative only, the journey may differ according to your circumstances.
The software developer journey
There is information available that may help you to identify commercial opportunities:
Register for SBR
Once you have determined that you can develop SBR-enabled products, you can register for SBR by completing the online registration form.
After your form has been received and processed, you will receive an email with instructions on how to download the Software Developers Kit (SDK).
If you would like the opportunity to discuss what reports/services you are interested in developing and ask any questions about the process then please contact the SBR Service Desk. The SBR Service Desk will then engage the applicable SBR Agency to get in contact with you.
Design, build and test
To SBR enable your software, you may need to refer to the following information:
- SBR AU (definitional) Taxonomy
- SBR Software Developers Kit
- SBR Web Services Implementation Guide (WIG)
- Sample Web Services Definition Language (WSDLs), and
- Self-certification testing guide.
To begin the build phase of the journey, you may need to refer again to the resources listed in the Design phase, as well as refer to the information provided in the following documents:
- MIG documents for a specific reporting obligation
- the conformance suite for the corresponding reporting obligation, and
- relevant Schematron files for a specific reporting obligation.
As a software developer, you will need to:
- enable your product to use the SBR Taxonomy
- test the end-to-end process (i.e. from the time the user initiates a reporting transaction to the time it is successfully completed)
- undertake compliance testing of your product, in accordance with the SBR compliance regime, and
- execute the test cases in the conformance suite.
The SBR Program will provide you with the support and infrastructure needed to participate effectively in the testing of your software.
The SBR Program have created an external test environment that simulates the SBR production environment, which will covers the component parts of SBR, including the generic facilities and agency specific services connected to them.
The SBR Program has also defined all SBR testing boundaries (including interfaces), entry criteria for each boundary interface and provides an SBR test coordinator for first level management and support of all boundary interfaces for the interconnected testing environments.
The SBR Program will also ensure that SBR agencies have tested their own services to a standard sufficient for software developers to engage in their own testing, and provide a suite of test services that can be used to test both the technical (i.e. web service) and business (e.g. activity statement) implementations.
To support the test services, a library of test credentials, Australian business numbers (AUSkey) and test data is provided to software developers that will be recognised by agencies during testing.
The SBR Program offers a simple message connectivity test ('message.ping') designed as an end-to-end connectivity test from business software, through core services, to agencies and back
It is important to obtain solid knowledge of the SBR Solution Overview, SBR Taxonomy AU, ReadMe files in the SDK, the Message Implementation Guide and the SBR Self Certification Testing Guide.
The SBR Program follows a self-certification model which is based on the current ATO process for software developer certification. Software developers will need to:
- establish the minimum criteria that the software must meet
- declare that they have achieved the required testing results.
The declaration is a self-certification of compliance with no implied approval or endorsement by the SBR Program or any Australian Government agency. Therefore the testing results are not reviewed by the Australian Government or by a third party. However, on a risk basis, the SBR Program will undertake a targeted compliance audit of a software developer's adherence to the agreed processes.
The self-certification testing packages are designed to provide technical assurance that your implementation of SBR has been done correctly. You should note that the self-certification testing artefacts are designed to provide technical assurance only. As a software developer you are responsible for conducting your own quality reviews and tests to your own satisfaction, prior to commencing any conformance testing.
To be eligible to complete the self-certification declaration you must complete the required testing for the relevant reports.
Once this has been completed you can certify a service by completing the online certification form.
When accepted, your SBR-enabled products will be allowed to use the production environment.
Further information about the process can be found in the Self-certification testing guide.
Developing or testing SBR-enabled software and require assistance?
Contact the SBR Service Desk on 1300 488 231 or via SBRServiceDesk@sbr.gov.au - available between 8:00am and 7:00pm AEST Monday to Friday - excludes public holidays and the SBR Christmas shutdown period.
Last updated: 25 Nov 2016
Page ID: 12469