GUIDANCE
EXTERNAL
1 OCTOBER 2014
UNCLASSIFIED
FORMAT
AUDIENCE
DATE
CLASSIFICATION
VERSION 1.0
FILEREF:G017
SENDING MEMBER REGISTRATION OUTCOME
RESPONSE MESSAGES
PURPOSE
The purpose of this document is to provide additional guidance on the use of the Member
Registration Outcome Response message (MROR) in response to member registrations and
updates under the SuperStream Data and Payment Standard (the Standard).
BACKGROUND
This guidance note provides an alternative approach to the use of the MROR in responding to a
variety of scenarios of member registration and updates, particularly when they are combined.
This guidance has been prepared in consultation with the SuperStream Standard Technical
Committee.
The intent of this guidance is to improve the efficiency of the data standard by removing the
mandatory requirement to send messages that are not expected to provide value to employers or
funds.
This guidance note must be read in conjunction with the Superannuation Data and Payment
Standard Schedule 4(a) document Data and Payment Standards – Contributions Message
Implementation Guide, and the Schedule 6 document Data and Payment Standards – Error Code
Management.
DEFINITION OF NEW REGISTRATION AND MEMBER UPDATE
For the purposes of this guidance a new registration is defined as the registration of a member with
an employer in a default fund.
A member update is defined as the provision of changed information for a member that is either:
 already registered with an employer and default fund, or
 registered with a choice fund.
This means that when an employee joins a new employer, an initial MRR sent by that employer to
their default fund should be treated by the fund as a new registration and an MROR sent, even if
that employee is already a member of the fund.
UNCLASSIFIED
PAGE 1 OF 4
MROR NOT MANDATORY FOR MRR UPDATES
In order to improve the efficiency of the data standard the following rules should be applied in
determining how to respond to an MRR message. For the purposes of these rules, an MRR is
defined as a complete XBRL business document, specified in the Message Implementation Guide.

Where an MRR contains only new registrations, it is mandatory that the fund sends an MROR.

Where an MRR contains only member updates, it is optional whether to send an MROR. This
option is exercised at the discretion of the fund (as the responding party).

Where an MRR contains a mix of new registrations and member updates it is mandatory to
send an MROR.
-
If the fund uses a progressive response pattern for the MROR it is mandatory that
responses are sent for all new registrations in the MRR. It is at the option of the fund
whether responses are sent for member updates in the MRR.
-
Where a non-progressive response pattern is used, the interpretation and assumptions
of the maximum severity code should be applied only to the new registrations in the
MRR. No assumptions should be made about the member updates. For example, the
maximum severity code ‘Error’ should be interpreted to mean that errors were found
and reported in relation to all new registrations, and no assumptions made about the
outcome of member updates.
Implications
This will reduce the number of MROR messages that would normally have been sent in response
to MRR.
As the option to send an MROR for member updates rests with the fund, employers and their
service providers will potentially receive MROR messages for some member updates and not
others.
Reference to published standard
The current requirement is that an MROR must be sent once the receiving entity has processed
the MRR.
Reference: Schedule 4a document Data and Payment Standards – Contributions MIG, section 5.a.
RECOMMENDED GUIDANCE
Funds should consider this guidance note and determine whether it is suitable for their solution. If
funds choose to implement the alternative options they should consult with their key stakeholders,
especially employers and their service providers, to help ensure interoperability.
Employers and their service providers should consider this guidance note and determine how to
address the potential not to receive a response in accordance with the Standard.
ATTACHMENT 1 – EXAMPLE SCENARIOS
UNCLASSIFIED
PAGE 3 OF 4