Rollover User Guide v1 0
Contents
1. If this message is not sent by the transferring entity then the sender of the Initiate Rollover Request message may assume it has been processed successfully 3 Rollover Transaction Request The Rollover Transaction Request message provides the transaction details of the rollover benefit and is sent by the transferring entity to the receiving entity The message includes a payment reference number that will enable reconciliation with the matching payment by the receiving entity UNCLASSIFIED PAGE 8 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE The member must have supplied the transferring entity with sufficient information in the Initiate Rollover Message as governed by the Standard to enable them to process the rollover request successfully 4 Rollover Payment The Rollover Payment contains payment values and reference details of the benefits paid by the transferring entity to the receiving entity The Rollover Payment must be made using an approved payment method set out in the Standard Exchange of money and information between financial institutions and the delivery of the bank statements to the receiving entity will use existing transfer protocols and is out of scope of the Standard 5 Rollover Transaction Outcome Response The Rollover Transaction Outcome Response message must be sent by the receiving entity once they have processed the Rollover Transaction Request message The Rollover Transaction Outcome Response indicates whether2. Start of instance document lt link to initiaterollover request 02 00 report xsd gt Facts give additional information ABN 11 2g about the company identified in context State or Ter amp Pt Period start 01 Q Period end 30 0 lt context gt lt context ID ID1 gt lt context ID ID2 gt ABN 55 666 Period end 06 2012 lt context gt End of instance document Conceptual Representation of Facts 6 2 Contexts in the Rollover MIG 6 2 1 XBRL Context Specifications This section defines the context specifications that may be used by all messages specified within this Rollover MIG The rules surrounding optionality mandatory etc and cardinality are also defined 6 2 2 Context Specification Message Sender This context uniquely identifies the entity that will be sending the message It is important to note that this is not necessarily the originating APRA regulated superannuation entity this allows for intermediaries such as fund administrators or clearing houses to participate in the transaction 6 2 3 Context Specification Message Receiver This context uniquely identifies the entity that will be receiving the message It is important to note that this is not necessarily the receiving APRA regulated superannuation entity this allows for intermediaries such as fund administrators or clearing houses to participate in the transaction 6 2 4 Context Specification Ro
3. aligns with the agreed processing mode before sending the message The processing modes may be varied by mutual agreement however the agreement must continue to meet the requirements of the relevant profile refer to section 4 of this guide Further information about processing modes can be found at the Oasis website https www oasis open orq 6 4 ConversationID All messages which make up a Rollover Transaction Request that is the request and associated response must be linked via a shared value for the ConversationID attribute Further information about ConversationID can be found in the Rollover MIG It is the responsibility of the entity that sends the first message within the interaction that is the sender of either the Initiate Rollover Request or Rollover Transaction Request message to allocate the ConversationID according to the Standard ConversationlD will be common across messages within an interaction however should not be assumed to be common across different interactions The ConversationID is not able to be used to provide end to end tracking of individual member rollover requests as there is no guarantee of a one to one correlation between the set of members in the originating Initiate Rollover Request and any ensuing Rollover Transaction Request To manage end to end tracking of rollovers for individual members funds will need to build logic into their systems The design of the Standard is founded on the principl
4. contains actual business data and is created in accordance with the rules prescribed in both the relevant Rollover MIG and taxonomy There are several essential components of an instance document These are e References e Context e Facts It is important to remember that an instance document is created to be used automatically by the computers that send and receive the electronic messages rather than for humans to read and understand A conceptual representation of an instance document is UNCLASSIFIED PAGE 14 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE Start of instance document dlink to initiaterollover request 2 00 report sd context ID ID4 ABN 11 222 333 444 State or Territory NS Period start 01 07 2011 Period end 30 06 2012 zicontext context ID ID 2 ABN 55 666 777 888 State or Territory QLD Period start 01 07 2011 Period end 30 06 201 2 zicontext Name contextRef ID1 Company A Names lt Address contextRef 2 ID1 1 Main St Sydney 2000 Address Phone cantextRef 01 gt 239993888 lt Phone gt Name contextRef ID2 Company B Names lt Address contextRef D2 gt 99 First Ave Brisbane 40004 Address Phone contestRef Ip2 0799999999 Phones End of instance document Conceptual Representation of an Instance Document UNCLASSIFIED PAGE 15 OF 25 U NCLASS Fl E D ROLLOVER USER GUIDE 6 1 2 References References identify which particular taxonomi
5. if there is one to enable fund details lookup without examining payload b e UN A business document may be an XBRL Instance described in the Schedule 4b document Rollover Message Implementation Guide Rollover MIG Alternatively a business document may be an XML message event structure as described in the Schedule 6 document Error Code Management Message Package or Envelope The Message Envelope consists of two components 1 The Message Header 2 The Message Payload The Message Header carries the information necessary to facilitate message exchange without needing to interrogate the Message Payload it contains The Message Header is specified by international standards with some customisation and is used to e communicate essential details between the from and to parties without unpacking the envelope e ensure that details include who it is from where it is going and what type of content it contains e allow tracking and traceability of related messages over time UNCLASSIFIED PAGE 13 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE The Message Payload is specified by the Rollover MIG and is comprised of business documents relevant to the contained transactions 6 UNDERSTANDING INFORMATION IN THE MESSAGE 6 1 XBRL Concepts 6 1 1 Instance Document An instance document is the specific set of information that has been compiled for electronic information exchange under the Standard It
6. responses required for APRA regulated superannuation entities to rollover or transfer a member s benefits to another APRA regulated superannuation entity Some parts of the end to end process such as member notification are outside of the scope of the Standard and are not included in the Rollover MIG 2 2 Other Schedule Documents that Provide Information for the Rollover MIG The Superannuation Data and Payment Standards 2012 Legislative Instrument incorporates by reference documents as existing from time to time Updates to any of the documents incorporated by reference in the Schedules to this Standard will be made available on the ATO website once finalised following consultation Within this user guide these documents are referred to as Schedule documents for example the Rollover MIG is the Schedule 4b document The Rollover MIG is supported by other Schedules These documents must be read in conjunction with the Rollover MIG in order to comply with the Standard and include e Schedule 2 document Data and Payment Standards Superannuation Terms and Definitions This document specifies the data elements associated with the rollover interaction e Schedule 3 document Data and Payment Standards Payment Methods This document specifies the payment methods associated with the rollover interaction e Schedule 5 Data and Payment Standards Message Orchestration and Profiles This document specifies the message transport
7. the Rollover Transaction Request message was successfully processed or alternatively what errors and warnings were discovered The Rollover Transaction Outcome Response message may be sent e as a single response to a Rollover Transaction Request once processing is completed for all members included in the Rollover Transaction Request or e multiple times for a single Rollover Transaction Request for any subset of members and errors discovered or successful outcomes encountered during processing of the Rollover Transaction Request 6 Member Notification Notifications required by law to be sent to the member by the transferring entity or the receiving entity are not covered in the Rollover MIG and rely on existing processes UNCLASSIFIED PAGE 9 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE 3 OBLIGATIONS OF APRA REGULATED SUPERANNUATION ENTITIES e Information must be sent and received electronically e Use the minimum data set in the specified message format o using the standard terms and language of the taxonomy o Using the transport protocols associated with their chosen profile e Receive and make payments electronically as described in the Schedule 3 document Payment Methods e Ensure payments and data are linked by payment reference numbers as per the Standard e Transferring APRA regulated superannuation entities must ensure that all Rollover Transaction Requests are successfully processed on behalf of their members as they ar
8. ROLLOVER USER GUIDE Start of instance document link to initiaterollover request 02 D0 report xsd 7 context Information that context ID ID1 gt uniquely ABN 11 222333 444 identifies an State or Territory NSW entity item or Period start 01 07 2011 other abstract Period end 30 06 2012 concept lt context gt context ID ID2 gt Context Information ABN 55 666 777 888 that uniquely identifies an State or Territory QLD PES PA C HER Period start 01 07 2011 abstract concept Period end 30 06 2012 lt context gt zName contextRef ID1 gt Company A lt Name gt lt Address contextRef ID1 gt 1 Main St Sydney 2000 lt Address gt lt Phone contextRef ID1 gt 0288888888 lt Phone gt Name contextRef ID2 gt Company B lt Name gt lt Address contextRef ID2 gt 99 First Ave Brisbane 4000 lt Address gt Phone contextRef 2 ID2 0799999999 lt Phone gt End of instance document Conceptual Representation of Context 6 1 4 Facts A fact is a piece of data contained in an instance document and it provides additional information about a particular context identified elsewhere in the instance document For example if a particular instance describes a context as being the combination of company ABN state or territory of operation and applicable period relevant facts may be name address and phone number UNCLASSIFIED PAGE 17 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE
9. SSIFIED ROLLOVER USER GUIDE 7 ERROR MESSAGES 7 1 General The Schedule 6 document Error code management sets out the error codes that are required to be used in conjunction with messaging to ensure efficient exchanges and compliance with the Standard An entity may implement organisation specific error codes for errors not included in the Standard in accordance with the specified convention Error messages are categorised into e Errors processing failed e Warnings processing was successful however unexpected problems may result and the data should be reviewed e Information processing was successful and other details may follow 7 2 Error Message Notification The example below shows two of the error messages and when they will occur XBRL fact Instructions Rules Msg Code ElectronicContact ElectronicMail 1 Mandatory 1 SUPER GEN GEN 4 Usage Code 2 Must be set to 03 for 2 SUPER GEN GEN 5 Contact Msg Code Short Description 1 SUPER GEN GEN 4 Mandatory data element not supplied 2 SUPER GEN GEN 5 Data element contained an unexpected value If there is no value supplied for electronic mail usage code then the system must generate an error message indicating that it is a mandatory entry If the value supplied for electronic mail usage code is not 03 then the system must generate an error code indicating that the supplied value is not correct Errors will be pass
10. UNCLASSIFIED PAGE 25 OF 25
11. USER GUIDE EXTERNAL 18 MARCH 2013 UNCLASSIFIED FORMAT AUDIENCE DATE CLASSIFICATION M Australian Government Australian Taxation Office FILE REF FILE NO Rollover User Guide What you need to know to implement the Data and Payment Standards the Standard o e UNCLASSIFIED For further information or questions email SuperStreamStandards ato gov au UNCLASSIFIED ROLLOVER USER GUIDE ENDORSEMENT VERSION CONTROL CURRENT VERSION NUMBER v1 0 DATE 28 March 2013 VERSION CONTROL Version Revision date Summary of changes 0 1 draft 21 November Original draft for comment 2012 0 2 draft 26 November Incorporated internal SBR business technical 2012 feedback 0 3 draft 6 December 2012 Incorporated feedback at close of consultation phase 2 November 2012 0 4 draft 21 January 2013 Following registration of Legislative Instrument and as published on www ato gov au 0 5 draft 31 January 2013 Incorporated feedback from Superstream Project Implementation team 0 6 draft 18 February 2013 Incorporated feedback from technical meeting 0 7 draft 12 March 2013 Incorporated feedback from APRA review 1 0 28 March 2013 Version release for publication UNCLASSIFIED PAGE 2 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE TABLE OF CONTENTS RADIO OD Goes aute aea te ics edn eee ceca ean emcee Sc rats 3 UU SERT ETC 4 Tolo NUIBO D 2 02 cotes eb cedes adcud dedos Te SEM abc A ue Ja ood dapc Ro
12. ated superannuation entity will need to determine its transition in completion date There are other profiles that apply to Employers and to organisations providing a gateway service on behalf of participating superannuation funds but do not apply to APRA regulated superannuation entities UNCLASSIFIED PAGE 11 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE Profile Name Key Features Supported o o o c E 5 5 5 o c D 2 e a o D o 3 0 no o o o o 9 a 2G 599 260 7 8 ES o oc Lao O do oO Oo E o o n EG c nD coo oco E c o O50 ONG 82a CNG o o o coo OZ o oo0 c o a o0 SEO Reo 00 E E g me nO Pus o Pus nes 5 D o G 2 558 G8 ABO S oo gt amp o o 98920 noo oo o 900 c o 2 ene dcc cEzt doc G a 2 5 oo 00 o 0 S c n S 355 a 23 3733 3025 o o o G t B68 B05 w B05 w 2 225 Oo 9 g o S o 2020 L o0o2o00 gt DoOO gt l oo E o G E c COG vccO gcco goco B o o gt a S 289 S50 S55 amp 2too8 Fa a c E 7T E ons od Dw oo022060 og30 B85 E oa s 5 5 o oo oo o cok cooo cooo cCootc or o o EE Em n OEL OgEE OgEE Oott co O 20 a Entry Ultra light x x x x x Y x Light x Y x x 4 x x Y x Advanced High end 4 v v v x v Y x Y Y Large 4 4 4 Y x Y 4 4 v Y volume Application Gateway Application vV v x v Y vV v vV Y Y Gateway Profiles Default Agreements will still require some final configuration between the two APRA reg
13. e error condition One of Error Max Severity Partial code Warning Infor mation Progressive Message Severity Code One of Error i arnind Infor mation Short Description TITII Parameter ID Parameter Text Legend Mandatory Location Instance Identifier Location Path Error Message Structure UNCLASSIFIED PAGE 22 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE 8 PAYMENT METHODS The Schedule 3 document Payment Methods defines the payment methods that APRA regulated superannuation entities must use to comply with the Standard and specifies the method of generating a unique reference number This requirement ensures that e electronic payments which flow via the banking system and e the related superannuation transaction details which flow via the data messaging system can be reconciled efficiently by the APRA regulated superannuation entity that receives the rollover superannuation money Acceptable payment options for Rollovers are based on the Bulk Electronic Clearing System Direct Entry BECS DE maintained by the Australian Payment Clearing Association APCA To comply with the Standard e Payment must be by electronic transfer payment by cheque is not allowed e Data and money must be linked by unique transaction identifier if there is no unique identifier then it is non compliant Money flow via banking protocol Fund Fu
14. e legally the liable parties e The trustee of the receiving APRA regulated superannuation entity who receives a Rollover Transaction Request from a member must give specified information to the transferring APRA regulated superannuation entity e The trustee of the transferring APRA regulated superannuation entity must process the Rollover Transaction Request as soon as practical or within three business days following receipt of message as long as no additional information is required e f additional information is required then the Rollover Transaction Request must be processed as soon as practicable or within three business days of receiving the additional information e The trustee of the transferring APRA regulated superannuation entity who rolls over the whole or part of a member s benefit must give specified information to the receiving APRA regulated superannuation entity in relation to the Rollover Transaction Request or transfer e Trustees of the transferring and receiving APRA regulated superannuation entities must meet rollover performance standard timeliness e Members rights to information on entitlements must be satisfied Note These obligations can be met through internal operations or an external service partner such as an administrator or clearing house UNCLASSIFIED PAGE 10 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE 4 PROFILES AND CAPABILITY The Schedule 5 document Message orchestration and Profiles def
15. e that natural identifiers should be used wherever possible to facilitate tracking In practical terms both the Initiate Rollover interaction and Rollover Transaction interaction include a number of identifiers for the member that UNCLASSIFIED PAGE 19 OF 25 UNCLASSI FI ED ROLLOVER USER GUIDE are intended to be used for end to end tracking These include the Tax File Number or substitute where TFN is not included and the MemberlD The diagram below explains the use of ConversationID across instances Super Fund Super Fund Transferring Receiving Initiate L Rollover Interaction 1 Initiate Initiate Rollover L Rollover Request and subsequent Initiate response Rollover Request ConvlD common Initiate in an interaction Rollover Error Response ConvID should not be assumed to be common across interactions only within interactions Interaction 2 Rollover ConvID common in an interaction Transaction Request and subsequent response 6 5 Part Properties Part properties are provided in the ebMS header Their purpose is to support the efficient routing of business messages including multi part messages to their final destination without the need to examine the data contained inside the message Part properties typically replicate key business facts such as an Australian Business Number ABN and a unique superannuation identifier Each property has a name and a value UNCLASSIFIED PAGE 20 OF 25 UNCLA
16. ed through using the Message Event structure This will only be used when there is a requirement to pass a business response 7 3 Message Event Structure The Message Event structure provides two levels of error reporting maximum severity and item severity Maximum severity occurs only once in a Message Event and reports the highest level of error condition Error Partial Warning Information Progressive All levels of error can be reported at this level These do not necessarily apply to all items in the original message Item severity is UNCLASSIFIED PAGE 21 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE reported for each error condition that must be reported Item severity can only be Error Warning or Information When used this will be a separate part of the ebMS envelope Identification and location of errors will be facilitated through the following mechanisms e The response envelope carrying the Message Event will have the same ConversationID as the request envelope that originated the conversation o This allows identification of the originating message e The Location Instance Identifier is used as the instance identifier for the Message Event o This allows the error conditions to be linked to the specific Part and therefore business document within the originating message e The Location path within the Message Event will provide the link to the element within the identified business document that has triggered th
17. es are applicable to this instance An example follows Start of instance document lt link to initiaterollover request 02 00 report xsd gt lt context ID ID1 gt ABN 11 222 333 444 References information that State or Territory NSW identifies which particular Period start 01 07 2011 taxonomies are applicable to Period end 30 06 2012 this instance lt context gt context ID ID2 ABN 55 666 777 888 State or Territory QLD Period start 01 07 2011 Period end 30 06 2012 lt context gt Name contextRef ID1 gt Company A lt Name gt Address contextRef ID1 gt 1 Main St Sydney 2000 lt Address gt Phone contextRef ID1 gt 0288888888 lt Phone gt Name contextRef ID2 gt Company B lt Name gt Address contextRef ID2 gt 99 First Ave Brisbane 4000 lt Address gt Phone contextRef ID2 gt 0799999999 lt Phone gt End of instance document Conceptual Representation of References 6 1 3 Context A context is a set of variables that when brought together uniquely identifies an entity item or other abstract concept For example an instance document might include a context described by company ABN state or territory of operation and applicable period The electronic exchange of information will now show a set of data called facts that applies to that company in the relevant state for the period in question UNCLASSIFIED PAGE 16 OF 25 U NCLASS Fl E D
18. ess interaction obligations and exceptions and e provide an overview for creating data messages when processing a rollover using the Standard 1 1 Audience This guide is intended to support those who will use the Standard to develop compliant systems and processes when sending and receiving a rollover or transfer This group may include e APRA regulated superannuation entities funds other than self managed superannuation funds SMSFs who may need to update their systems to comply with the Standard e fund administrators superannuation clearing houses intermediaries and service agents who will need to comply with the Standard on behalf of funds and employers and e software developers in house or commercial and system integrators 1 2 Background 1 2 1 Rollovers According to Superannuation Industry Supervision Regulation 1994 part 5 01 Rollover means monies paid as a superannuation lump sum other than by way of being transferred within the superannuation system Transfer means member s benefits paid out of or received by a regulated superannuation fund or approved deposit fund means paid to or received from a another regulated superannuation fund or approved deposit fund or b an RSA provided by an RSA institution or c an EPSSS Within the Standard the term Rollover includes Transfer The Standard outlines the approved way to exchange rollover information in the superannuation industry It also desc
19. f an APRA regulated superannuation entity the receiving entity receives a request from the member of another APRA regulated superannuation entity the transferring entity to rollover or transfer funds the receiving entity is required to use an Initiate Rollover Request message to initiate the rollover or transfer The transferring entity must be able to receive that message electronically regardless of whether the message is initiated electronically by another APRA regulated superannuation entity a member including through an intermediary acting on the member s behalf or the ATO While a member can initiate a rollover manually via a paper form the Initiate Rollover Request electronic message is mandatory for an APRA regulated superannuation entity 2 Initiate Rollover Error Response An Initiate Rollover Error Response message must be sent from the transferring entity to the sender of the Initiate Rollover Request message if the Initiate Rollover Request message could not be processed due to an error If the Initiate Rollover Request message is processed successfully then this message will not be sent This message may be sent e asa single response to an Initiate Rollover Request for all errors discovered once processing is complete for all members included in the Initiate Rollover Request or e multiple times for a single Initiate Rollover Request for any subset of errors discovered during processing of the Initiate Rollover Request
20. ines the messaging services and interaction patterns that entities must use to comply with the Standard 4 1 Agreement APRA regulated superannuation funds must select a profile that reflects their capabilities and is compatible with the profile adopted by the other APRA fund in the rollover transaction as described in the Schedule 5 document Message orchestration and profiles When profiles have been selected the default agreements will apply unless the funds in the transaction mutually agree to change the terms of one or both of the default agreement s that would otherwise apply Default agreements contain processing modes P modes that establish the configuration parameters on which a sender and receiver must agree when exchanging messages Processing modes may be varied by mutual agreement however the agreement must continue to meet the requirements of the relevant profile If parameters are not provided in default agreements it is because they are not relevant to the associated profile Following their transition in completion date as described in Schedule 1 to the legislative instrument there are two defined Profiles that are available to be selected by an APRA regulated superannuation entity These are the High End and Large Volume profiles and are detailed in the Schedule 5 document Message orchestration and profiles Whilst the transition in period begins on 1 July 2013 and ends on 31 December 2013 each APRA regul
21. ir t zx ms User me ged mi rr ctim le ree M cee ro The Pci 7 Security Wercifeceipt Pm ia T Weary arsi cap Ra py Pacer U PLIZATION Piece T RaraptionAaarara s1 H DE ETION The PEE 1 ITREBETITTAMNTRTR 03 LIT EUST RR Maur eset EETEERR Pace pil t Piece 7 Cupless Cina Heri Panmatre Example of Default Agreement UNCLASSIFIED ROLLOVER USER GUIDE 5 MESSAGE CONSTRUCTION AND PACKAGING 5 1 The Message Package or Envelope eb ConversationID provides a link between related business messages sical eet eeu ep even when messages are joined and MESSAge CNVelOpe Will Nave a split All messages in response to the Member Client Identifier initial message in an interaction will carry the same ConversationID ebMS 3 0 header due ae ES m Part PartProperties within eb Payloadlnfo facilitate routing of message of the request envelope will contain envelopes 7 Part ID providing a unique ID for a The ABN of Gatewavs should not Part business document within a message TargetABN SourceABN ABN of the The business document reflects entity will be replicated in the header to enable fund details lookup without part of the message payload Part_ P dun examining payload WAN E payload there can be one TargetUniqueSuperannuationlden or more business documents tifier SourceUniqueSuperannuationldentifi er will be replicated in the header
22. llover Payment This context will uniquely identify the following e The transferring APRA regulated superannuation entity for the rollover and the Unique Superannuation Identifier USI of the APRA regulated superannuation entity that the rollover comes from UNCLASSIFIED PAGE 18 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE e The receiving APRA regulated superannuation entity for the rollover and optionally the destination USI of the receiving APRA regulated superannuation entity 6 2 5 Context Specification Member Rollover Transaction This context will uniquely identify the followings e The member on whose behalf the rollover is being made and their MemberlD in the transferring APRA regulated superannuation entity e The transferring APRA regulated superannuation entity for the rollover and optionally the USI of the APRA regulated superannuation entity that the rollover comes from e The receiving APRA regulated superannuation entity for the rollover and optionally the destination USI of the receiving APRA regulated superannuation entity It is important to note that not every context is relevant for every message The Rollover MIG prescribes the rules for determining which contexts apply to particular messages 6 3 Processing Modes The processing modes in an agreement establish the configuration parameters on which entities must mutually agree when exchanging messages The entity that sends the message must ensure their message
23. nce DOCUIT eroi aa ects sid accu ds aad ocu da rude cacti uaa Ch t PETEERE ERS 14 8T 2 Pieter Brie BSc asi e dodoiecadetada crap e e enn A EAE do vidas dU P capa Ua dap E EEE E OR Di 16 is cn dro qj OPEP 16 SN ALCHEMY 17 6 2 Contexts in the Rollover MIG cccccssssscccccccceceecceceeceeceeeececececeeseceeeeeeeeeeseeeeeeeeeseess 18 6 3 PROCESSING Modes Sei ce otto to eee ere o Hte semet soto nee ap suse edt EE AREE CM e ER duh 19 6 4 Conversation D ereere feet rere rar Cece nnrcn rere rrr ee rer rater teen pert fon renee grrr ere 19 6 5 Part Properties s dpt here cea vats enc ER bre dasa conve tee ood Po dagen eared once 20 7 Error Messages obe ete tene ker rli aces id stout edu re acer iud ra emere 21 He Genera bm CT M 21 7 2 Error Message Notification user eoa tee aeo ON aces te dox eR Rte rae eredi 21 7 3 Message Event Str ct re o ae ettet fe Ree a t eR etn o ELIO rM dE REL 21 8 Payment Methods cr Es 23 9 Exceptions SpBclal Gases 5 5 Gon ies eed seit Ceca is sed eoe de euet e coded cgi 25 UNCLASSIFIED PAGE 3 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE 1 INTENT The Rollover User Guide is to assist users in understanding the business obligations and interactions relevant to the Standard and how to use and understand the relevant Schedules and associated documents incorporated by reference to those Schedules when processing a rollover The scope of this guide is to e explain the busin
24. nd LINKED BY UNIQUE iD Data flow via data transport protocol Payment Representation Note The fund may have a service agent handling data and or money transactions on their behalf The legal responsibility under the Standard remains with the sender and or receiver irrespective of the role of these intermediaries UNCLASSIFIED PAGE 23 OF 25 UNCLASSI FI ED ROLLOVER USER GUIDE The message design supports 1 many or 1 1 relationships between money and data flows Rollover for members X Y and Z from Fund A to Fund B 1 many Fund A Fund B Financial Financial Institution Institution Data Exchange Payment Instruction out of channel Payment _ Ref 123 1 many Payment Transaction UNCLASSIFIED PAGE 24 OF 25 UNCLASSI FI ED ROLLOVER USER GUIDE Rollover for members X Y and Z from Fund A to Fund B 1 1 Fund A Fund B Financial Financial Fund B Institution Institution Data Exchange Massage 1 Payment Instruction out of channel Payment Ref 455 Data Exchange Message 2 Payment Instruction out of channel Payment Ref 789 Data Exchange Message 3 Payment Instruction out of channel Payment Ref 890 1 1 Payment Transaction 9 EXCEPTIONS SPECIAL CASES Exceptions that apply during the transition in period are described in Schedule 1 to the Superannuation Data and Payment Standards 2012 legislative instrument
25. protocols associated with the rollover interaction e Schedule 6 document Data and Payment Standards Error Code Management This document specifies the error codes and messages associated with the rollover interaction Transmission error codes are defined in the international standard UNCLASSIFIED PAGE 6 OF 25 UNCLASSI Fl ED ROLLOVER USER GUIDE 2 3 Standard Business Reporting SBR Taxonomy Reference The SBR Definitional Taxonomy http sbr gov au taxonomy must be used in conjunction with the Rollover MIG and associated Schedules 2 4 The Rollover Business Interaction Financial Financial Super Fund Institution Institution Receiving Transferring Receiving Fund Fund Electronic message exchange T Manual exchange via Paper Form Postal UNCLASSIFIED PAGE 7 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE 1 Initiate Rollover Request The transferring APRA regulated superannuation entity could receive the request to initiate a member rollover from any of the following entities e the member or their Power of Attorney not shown in diagram above e intermediary broker e g Financial Planner not shown in diagram above e receiving APRA regulated superannuation entity e ATO The business interaction diagram above illustrates how the rollover process can be initiated manually or in electronic form There are security authentication conditions that must be met for this message to be processed electronically I
26. ribes the situations in which the Standard must be used The Standard is used by superannuation funds to exchange information about member rollovers The need to use the Standard can be triggered in any of the following ways e the member initiates a rollover directly with the transferring fund e the member requests a rollover from the receiving fund the receiving fund contacts the transferring fund to initiate the rollover or UNCLASSIFIED PAGE 4 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE e the member requests a rollover through the ATO portability form the ATO forwards the request to the receiving fund to initiate the rollover 1 2 2 Superannuation Data and Payment Standard the Standard The Standard specifies the minimum requirements for dealing with payments and information relating to certain transactions within the superannuation system including employer contributions rollovers and transfers between superannuation entities and associated reporting obligations for superannuation purposes The purpose of establishing the Standard is to enhance the interests of beneficiaries of superannuation entities by improving the efficiency and productivity of the superannuation system as a whole In relation to rollover and transfer transactions and the associated payments the Standard applies to APRA regulated superannuation entities other than Pooled Superannuation Trusts PSTs The requirements in relation to rollover and transfer transac
27. set drawdown The processes around these matters are dealt with under the default rules of the APRA regulated superannuation or under instructions from the member to the APRA regulated superannuation Rollover amendments and cancellation are not within the scope of the Standard and all amendments must be managed via other processes between relevant parties The Standard also does not apply to in specie rollovers which can be managed via a process deemed relevant between the parties concerned or internal fund rollovers i e where preferred by a fund rollovers between products of the same fund may be handled by relevant accounting and registry entries UNCLASSIFIED PAGE 5 OF 25 UNCLASSIFIED ROLLOVER USER GUIDE The Standard has five aspects designed to increase efficiency and productivity across the Superannuation industry as a whole and include e astandard set of business terms and definitions the Definitional Taxonomy e astandard set of data message formats the Reporting Taxonomy set out in relevant message guides e messaging services standard which sets out requirements for message packaging transport security and receipting of messages e astandard format for electronic payments e enabling services 2 BUSINESS PROCESS AND INTERACTION 2 1 Understanding the Rollover Business Transaction The Rollover Message Implementation Guide Rollover MIG defines the business interactions message payloads and associated
28. tions and the associated payments do not apply to trustees of self managed superannuation funds The requirements prescribed by the Standard for such transactions apply to an APRA regulated superannuation entity from 1 July 2013 in relation to conduct that occurs on or after that date To allow an APRA regulated superannuation entity time to conform to the Standard a rollover transition in period operates from 1 July 2013 to 31 December 2013 inclusive By no later than 31 December 2013 all APRA regulated superannuation entities will be required to have transitioned to full compliance with the Standard for rollover transaction messages rollover initiation messages and associated electronic payments unless a notice in writing from APRA adjusting the transition in completion date to an alternative date has been received APRA regulated superannuation entities are required to work out their transition in completion date and ensure full compliance with the Standard by that time The Standard does not apply to an APRA regulated superannuation entity in relation to a closed product A closed product for the purposes of the Standard means a product that does not receive any contributions or rollovers whether from an existing member or any other person but may rollover or transfers a member s withdrawal benefit to another superannuation entity In the case of a partial rollover the Standard does not include rules concerning preservation components or as
29. ulated superannuation entities for example whether one entity will initiate a pull request for receipt of messages or be ready to respond to a pushed message before full interoperability is achieved The example below shows the configuration for the Light profile lt Ugh gt Prata Rum ary Dempa ba gu Lgl travel HT PSTI SOAF 12 Jusacrcd b Mz dme aoe Htm daw uus minaman araa arme mmi an NB More advanced profiles have additional elements In the Agreement which configure compression and split join features UNCLASSIFIED PAGE 12 OF 25 1 General parameters How aif messages in an agresc sxchaage peten occur 4 Errer handling How erora ave hercle anc reported 5 Reliability What degree ot message reliability ia supported B Security Wall secorily eve arn Cortes Jut dato ue uec a Protocol MWratiransport protocols to be weect 3 Businessinfo The business prota of amp Perici message eovelore A header and payload contente 7 Reception wnrenasa What cocar Icvo and context info ja do ke woed Each profile has its own pre defined Agreement Sampie shown is the Light Profile ae fe he md oo Pilea T Rar sos gree Pare T Marr ES Merete aganna Hiera y aerun yaan are Pacca T aucun U arra ma Tor p Pieca T Baruri Urram Taian ugut Mass 7 Banari U arrama Tutar Guid Bacon 7 Becuri PCR A
30. voda c SN dabc A Uo Ja e Nod dabo RO Vedere oU 4 12 Backgro nd sesen re ete soe oe boc br gece tenute datos tone stt ned meander seas 4 12 1 RollOVOES 1i rii aen snp o FL ne FLA A laa tenda wenn A RA E FA dU RA ARA RR a AE NAAR ERA RA Mu A rAR 4 1 2 2 Superannuation Data and Payment Standard the Standard 5 2 Business Process and Interaction ts scsessoncrcadctacnckeeenguciectewnctvessuacttdnidecsvesteenseltnteesteerwanets 6 2 1 Understanding the Rollover Business Transaction ccc cccceeeeeeeeeeeeeneeeeeeeeeeeeeeenaaees 6 2 2 Other Schedule Documents that Provide Information for the Rollover MIG 6 2 3 Standard Business Reporting SBR Taxonomy Reference eueeessuuss 7 2 4 The Rollover Business Interaction cccccccccccccccccccceccccecccececceeeeeeeeseseceeeeeeeseseeeeseeess 7 3 Obligations of APRA regulated superannuation entities seeeesssssssssssssss 10 2 Brotiles and Gapabllily 5c tee teret Crore ae netomat neste tees dees valet Gosche eet uade 11 AT zug aso stone ca p 11 5 Message construction and Packaging code co teeth ettet e codeine i eter tpud ta 13 5 1 The Message Package or Envelope ssseeeeeeennneemennnnnnn 13 6 Understanding Information in the Message sssssssemee 14 e T ABMs COlICSDISe e vae os tenete iade nate e emits ciuis 14 5 1 1 a nsta
Download Pdf Manuals
Related Search