ato logo
Search Suggestion:

Message level conformance and interoperability checklists

Scenarios for the types of test cases for interoperability testing and rollover peer-to-peer scenarios.

Last updated 15 January 2018

Interoperability test case summary

This section lists the types of test cases for interoperability testing. Interoperability test cases are listed in detail in Gateway interoperability test scenario catalogue and in Interoperability test case detail.

This checklist below provides a summary of the functional requirements for test cases that will test the interoperability within a rollover transaction sequence:

  • Fund Gateway to Fund Gateway  
    • Transport Layer connectivity
    • Message Service Handler (MSH) Layer connectivity
    • Application Layer connectivity – all gateways
     
  • Fund Gateway to/from ATO  
    • Transport Layer connectivity
    • Message Service Handler (MSH) Layer connectivity
    • Application Layer connectivity
     

Peer-to-peer test case summary

This section provides a summary of the Rollover peer-to-peer test case scenarios for fund to fund testing and ATO to fund testing.

Fund to Fund scenarios

  • Fund to Fund (B2B) sending IRR  
    • XBRL message construction
    • ebMS message transmission
     
  • Fund to Fund (B2B) receiving IRR  
    • ebMS message receipt
    • XBRL message deconstruction
    • IRR processed and either RTR or IRER generated
     
  • Fund to Fund (B2B) sending IRER  
    • Error response generated
    • XML message construction
    • ebMS message transmission
     
  • Fund to Fund (B2B) receiving IRER  
    • ebMS message receipt
    • XML message deconstruction
    • Error response message processed
     
  • Fund to Fund (B2B) sending RTR  
    • XBRL message construction
    • ebMS message transmission
     
  • Fund to Fund (B2B) receiving RTR  
    • ebMS message receipt
    • XBRL message deconstruction
    • RTR processed to registry and outcome response generated
     
  • Fund to Fund (B2B) sending RTOR  
    • Outcome response generated
    • XML message construction
    • ebMS message transmission
     
  • Fund to Fund (B2B) receiving RTOR  
    • ebMS message receipt
    • XML message deconstruction
    • Error or outcome response processed
     

ATO to Fund scenarios

  • Government to Fund (G2B) – ATO sending USM  
    • XBRL message construction
    • ebMS message transmission
     
  • Government to Fund (G2B) – Fund receiving USM  
    • ebMS message receipt
    • XBRL message deconstruction
    • Unclaimed Superannuation Money processed and outcome generated
     
  • Government to Fund (G2B) – Fund sending USMOR  
    • Error response generated
    • XML message construction
    • ebMS message transmission
     
  • Government to Fund (G2B) – ATO receiving USMOR  
    • ebMS message receipt
    • XML message deconstruction
    • Error or outcome response processed
     
  • Government to Fund (G2B) – ATO sending EPF  
    • XBRL message construction
    • ebMS message transmission
     
  • Government to Fund (G2B) – Fund receiving EPF  
    • ebMS message receipt
    • XBRL message deconstruction
    • EPF processed
     

QC50524