Show download pdf controls
  • CRT Alert 024/2018

    26 March 2018

    Final preparation for MAAS implementation

    In April 2018, the first tranche of super funds will begin transitioning to the new event-based reporting service, MAAS. This alert provides important advice and assistance to help you prepare for MAAS implementation.

    We have recently published additional guidance and support products.

    • The MAAS Foundation Data Handbook, initially released on 12 February 2018, has been revised to incorporate further industry feedback.
    • The MAAS Questions and Answers includes our response to your queries about MAAS implementation. We will continue to update this document with new questions and answers unless they're available elsewhere, such as in the Foundation Data Handbook.
    • The Fund Onboarding and Implementation Approach sets out the requirements for testing, production cutover and initial foundation data upload as well as details of the support available during implementation.

    Consistent with previous SuperStream releases we'll publish a production readiness checklist soon. You should complete and return this to us to indicate your production systems are compliant, permissions and personnel are in place, and that you're comfortable with the level of testing you've completed. We will write to all trustees to advise them of the requirement to complete this checklist.

    The MAAS Business Implementation Guide (BIG), first published on 11 April 2017, will also be updated and republished by 29 March 2018, providing more certainty around system performance.

    As part of our approach to readiness and onboarding we'll be providing you with weekly updates about implementation progress.

    See also:

    Messaging performance and capacity

    Transaction record limit and concurrency

    We can now confirm transaction record limits for files sent through MAAS have been separated into two distinct implementation phases.

    Pre-July 2018

    As specified in the BIG the maximum transaction record limit for a business document within an SBR ebMS3 message is 10,000.

    This means any files exceeding 10,000 must be placed in separate SBR ebMS3 messages. Before attempting to send multiple files to us concurrently (ie using a multi-threading process from a single implementation where there is no dependency on receiving a technical receipt before sending another file), please email At this stage you should contact us each time you plan to send concurrent files.

    Post-July 2018

    As part of our SBR2 to Gold program of work, which is focused on improving the availability, resilience and performance of the platform, we will implement software, configuration and infrastructure changes.

    These changes will allow us to catch and hold messages, increase processing batch speed and reduce outages. This will increase the maximum transaction record limit and improve our capacity to accept concurrent messages.

    We are currently working through our performance testing strategies and are confident the maximum transaction record limit for a business document within an SBR ebMS3 message will be 100,000. We're also validating up to 200,000 records per transaction.

    SBR MAAS intermediate and delayed response patterns

    Intermediate and delayed response criteria

    ATO's ‘Intermediate’ and ‘Delayed’ response time service levels are as follows.

    • A batch or bulk transaction with less than or equal to 1,000 logical or child records is classified as having an ‘Intermediate’ response time service level.
    • A batch or bulk transaction with more than 1,000 logical or child records in the same transaction is classified as having a ‘Delayed’ response time service level.

    Technical receipt

    For MAAS bulk requests, SBR will first send back a generic technical receipt after it successfully authenticates the incoming request. This receipt will confirm that the SLA obligations have been discharged for that message.

    Following the technical receipt an intermediate request message will then result in one single validation and business response.

    A delayed request message will result in two separate responses – a validation response followed by a business response – regardless of how often you poll. These must be picked up in order.

    In both instances you will need to pull these responses from SBR.

    See also:

    More information

    You can find information about MAAS readiness and implementation on the SuperStream Readiness and Implementation Let's Talk communityExternal Link.

    Email us at if you have questions about MAAS foundation data or onboarding.

      Last modified: 26 Mar 2018QC 54858