format / Audience / Date / Classification
/ File Ref: / [G042]
MEMBER ID PARAMETER IN MEMBER REGISTRATION OUTCOME RESPONSES
Purpose
This document supersedes guidance note G040 and providesupdated guidance on dealing with an issue identified in the Member Registration Outcome Response (MROR)message when notifying that a new membership has been successfully registered.
Background
TheContributionsMessage Implementation Guide (MIG) v1.3 has the following statement included in Section 5 – Member Registration Outcome Response (MROR) under the message structure table:
The response MUST include an EventItem parameter with Parameter.Identifier set to
“Superannanuation.Fund.Details.Member.Client.Identifier”, along with Parameter.Text containing the member ID of the member registered.
The Parameter.Identifier, however, is misspelt in the published MIG (i.e. ‘Superannanuation’ instead of ‘Superannuation’).
There are also extraneous full stops in the parameter identifier value before the words “Fund”, “Details” and “Client”.
This will be rectified in the next scheduled release of the Contributions MIG.
issue
Some sending and receiving solutions have implemented the spelling as per the MIG (i.e. with the spelling error) while others have implemented the correct spelling for ‘superannuation’.This can result in interoperability issues.
RECOMMENDED GUIDANCE
- Until corrected within MIG2, new implementations should use the correct spelling of ‘Superannuation’ for the Parameter.IdentifierSuperannuationFundDetails.MemberClient.Identifierand remove the full stops before “Fund”, “Details”’ and “Client”when noting the successful registration of a new membership.
Note: This is the intended spelling which is consistent with the name of the element defined at item 8 in the Superannuation fund member details in the Contributions Transaction Request in the MIG.
- Existing sending solutions using incorrect spelling must discontinue use of the incorrect spelling before the implementation of MIG2.
- Existing sending solutions using the correct intended spelling do not need to change.
- Receiving solutions should implement a solution capable of receiving:
a)the correctly speltParameter.Identifier (SuperannuationFundDetails.MemberClient.Identifier),
b)the incorrect spelling with extraneous full stops as currently detailed in the MIG (Superannanuation.Fund.Details.Member.Client.Identifier), and a third possibility
c)the corrected spelling but still with extraneous full stops (Superannuation.Fund.Details.Member.Client.Identifier).