The information on this page will help DSPs to identify the tools or services required to deliver an SBR-enabled product. The steps outlined are illustrative only and may differ according to your circumstances.
Find out about:
This information may help you identify commercial opportunities:
You can register to develop SBR-enabled products through Online services for Digital service providers (DSPs).
The service enables you to self-serve and transact with us in real time. You can access support, log and track requests, share and store information and communicate and collaborate in a secure environment.
Once registered, you will receive further guidance via Online Services for DSPs.
You can email SBRServiceDesk@sbr.gov.au or phone 1300 488 231 if you would like to discuss the reports/services you are interested in developing and ask any questions about the process. The SBR Service Desk will then organise for the applicable SBR agency to contact you.
To SBR-enable your software, you may need to refer to the following information:
- ATO SBR Logical Artefact Map
- SBR Core Services Web Services Implementation Guide (WIG)
- SBR ebMS3 WIG
- ATO ebMS3 Implementation Guide
- SBR AU (definitional) Taxonomy
- SBR Core Services Software Develop Kit (SDK)
- SBR Core Services Web Services Definition Language (WSDLs)
- SBR Authentication Developer Kit (ADK)
- Cloud software Authentication and Authorisation SDK (CAA)
- Developer Tools
- ATO Service Registry
- ATO common artefacts and reference documents
To begin the build phase, you may need to refer again to the resources listed in the Design phase, as well as:
- Service artefacts for a specific reporting obligation (Message Structure Tables, Validation Rules, Service Business Implementation Guide)
- the conformance suite for the corresponding reporting obligation
- relevant Schematron files for a specific reporting obligation
- Building SBR into my application
- Developer tools.
You will need to:
- enable your product to use the SBR Taxonomy
- test the end-to-end process (ie 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
- 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 has created an external test environment that simulates the SBR production environment. It 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 (ie web service) and business (eg activity statement) implementations.
A library of test credentials, Australian business numbers (ABNs) and test data provided to software developers 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 MIG and the SBR program self-certification testing guide (PDF, 456KB).
The SBR Program follows a self-certification model based on the current ATO process for software developer certification. Software developers will need to:
- establish the minimum criteria 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 DSP you are responsible for conducting your own quality reviews and tests to your own satisfaction, prior to commencing any conformance testing.
You must complete the required testing for the relevant reports to be eligible to 'Request production access' in Online services for DSPs.
Once this declaration is accepted, your SBR-enabled products will be allowed to use the production environment.
For support you can phone the SBR Service Desk on 1300 488 231 or email SBRServiceDesk@sbr.gov.au. Support is available between 7.00am and 7.00pm EST Monday to Friday (excludes national public holidays and the end-of-year shutdown period).