Audience
The audience for this document is any fund, digital service and solution providers that will be developing or extending their software to make it compliant with the Superannuation Data and Payment Standard 2012 (The ‘Standard’).
This document has been written for an audience expected to be familiar with the following:
- XBRL – xbrl.orgExternal Link
- ebMS3.0/AS4 – oasis-open.org/standardsExternal Link
- SuperStream program – ato.gov.au/datastandards
- SBR Program – sbr.gov.auExternal Link
Document content
The document provides sample test cases for execution by digital service providers as part of a self-certification process up to and including peer to peer testing. This document contains a list of test cases to assist in validating the following:
- AS4 ebMS message conformance and testing supporting Superstream business to business exchange of data.
- The application code complies with the business rules defined in the corresponding Message Implementation Guide (MIG) for the transaction.
- The application code generates an XBRL message instance that complies with the XBRL Definitional and Report Taxonomies and associated Schematron rules.
- The application code correctly processes a message received including exception handling.
- Versioning scenario testing (v1 & v2).
Document structure
The detailed content of this document is divided into the following four major sections and an overview of the content of each is provided below:
- Conformance testing
- focuses on the different solution scenarios and the many components involved in the messaging implementations that will be developed by funds, gateways and solution providers to support SuperStream Rollover MIG v2
- an overview of integration testing, interoperability and peer-to-peer testing for both fund and government transactions
- Message level conformance and interoperability testing – a summary of the test cases and conformance criteria that will test the interoperability within a rollover transaction sequence
- Rollover V2 test cases – an overview of rollover v2 testing requirements and lists the test cases that form the basic requirement for integration testing, gateway interoperability and peer-to-peer testing for both funds and government
- Peer-to-peer (P2P) test scenarios
- Fund to Fund transactions (B2B) – the tables in this section provide a catalogue of the rollover v2 tests and then specify the detailed messaging steps involved in each of the peer-to-peer test sequences listed for IRR and RTR messages and for the corresponding IRER and RTOR response messages
- Government to Fund transactions (G2B) – the tables in this section provide a catalogue of the rollover v2 tests and the steps involved in each of the peer to peer test sequences listed for USM and EPF.
Other related documents
This document is to be used in conjunction with these related documents:
- Data and Payment Standards Rollover Message Implementation Guide v2.0
- Supporting XBRL reporting taxonomy
- Data and Payment Standards Terms and Definitions (Draft Schedule 2)
- Data and Payment Standards Payment Definitions (Draft Schedule 3)
- Data and Payment Standards Message Orchestration and Profiles (Draft
- Schedule 5)
- Data and Payment Standards Error Code Management (Draft Schedule 6)
- SuperTICK User Guide v2.0
- Fund Validation Service (FVS) User Guide v 3.1
- Business Response Messaging Framework User Guide Final v1.1
- Rollover Transition Guide