Consultation Group for 2018 Super Measures

This short term group is an opportunity to provide information to industry on the emerging administrative design of the super measures announced in and around the 2018-19 Federal Budget. It is also an opportunity for industry to raise questions and issues. The measures to be included in this group for discussion are:

  • Re-versioning the Rollover MIG (including SMSF rollovers)
  • Protecting your super package – unclaimed superannuation and proactive reuniting
  • Better integrity over deductions for personal contributions
  • Work test exemption for recent retirees
  • Preventing inadvertent concessional cap breaches by certain employees
  • SG Amnesty
  • Three-yearly audit cycle for some self-managed superannuation funds
  • Increasing the maximum number of allowable members in self-managed superannuation funds and small APRA funds from 4 to 6.

This short term group is an opportunity to provide information to industry on the emerging administrative design of the super measures announced in and around the 2018-19 Federal Budget. It is also an opportunity for industry to raise questions and issues. The measures to be included in this group for discussion are:

  • Re-versioning the Rollover MIG (including SMSF rollovers)
  • Protecting your super package – unclaimed superannuation and proactive reuniting
  • Better integrity over deductions for personal contributions
  • Work test exemption for recent retirees
  • Preventing inadvertent concessional cap breaches by certain employees
  • SG Amnesty
  • Three-yearly audit cycle for some self-managed superannuation funds
  • Increasing the maximum number of allowable members in self-managed superannuation funds and small APRA funds from 4 to 6.

Ask your questions about proposed new super measures in the Q&As section below. Help us direct your question to the right area by adding the most relevant hashtag from the following list to the end of your post:

  • #RolloverMIG
  • #UnclaimedSuper
  • #NOI
  • #WorkTest
  • #CapBreaches
  • #Amnesty
  • #SMSFAudit
  • #4to6Members

This Q&A is specific to the topic of proposed new super measures. If your question relates to another topic search or ask the ATO Community.

Super measures 2018 Q&As

Ajax loader transparent
Didn't receive confirmation?
Seems like you are already registered, please provide the password or use a different email ID
  • #RolloverMIG Can you please advise how 'versioning' will be handled with the SMSF services. The current FVS is used to identify the 'version' of a message that should be sent for a USI however there is nothing similar for the SMSF service. At the moment it is assumed to be V3.

    DavidAms asked 4 months ago

    At this stage the transitional period to cutover to Rollover MIG V3 is onlyavailable for APRA funds to assist them as they manage multiple versions. The version control will be orchestrated by a certification value on the FVS – as per the move from V1 to V2.

    Currently there is no method for a Superfund to determine if an SMSF is certified for Rollover V3 and no method for SMSF’s to advise us of their status.

    Our expectation is that Software Providers would build to meet the Nov 30 2019 effective date so we could then assume that any SMSF with a valid ESA would be certified.

    However this discussion is not formalised and will be a critical part of the next stage of our consultation where we delve into on-boarding and how we move
    to introduce SMSFs.

  • #RolloverMIG URGENT Electronic Service Address (ESA) and Bank Details We are finalising the design of our SuperStream Rollover v3 solution. To assist with this could you clarify the following please: 1. Electronic Service Address (ESA) and Bank Details: Could you clarify why ESA and Bank Details appears in the header as well as in the body of Rollover v3 messages which involve SMSF’s please? Are these ever expected to ever be different from each other – if so, please describe the business scenario where this would occur? Thank you for your assistance.

    MrsCoops3099 asked 4 months ago

    In the Rollovers MIG two main transaction patterns are defined: Initiate Rollover Request (IRR) and Rollover Transaction Request (RTR).

    The IRR pattern is shared by the IRR, EPF and S20c messages.

    The IRR pattern has three context specifications (and matching content data):

    1. Message Sender
    2. Message Receiver
    3. Member Rollover Transaction.

    The RTR pattern is shared by the RTR and USM messages.

    The RTR pattern has four context specifications (and matching content data):

    1. Message Sender
    2. Message Receiver
    3. Rollover payment
    4. Member Rollover Transaction.

    When receiving fund is an APRA fund:
    The Financial Institution Account (FIA) details of
    the receiving fund for an RTR are carried in the Rollover payment content data along with payment amount and PRN.

    The FIA information is populated by the transferring fund in the RTR after retrieving the receiving fund information from the FVS using
    the receiving fund’s USI.

    The transferring fund also retrieves the receiving fund Electronic Service Address (ESA) from the FVS.
     
    When receiving fund is a SMSF:
    If the receiving fund for an RTR is a SMSF it is not possible to retrieve the FIA details or ESA from the FVS as described above.

    In this scenario the receiving SMSF FIA and ESA information required for the resulting RTR must be supplied in one of the following ways:

    1. The FIA and ESA details are supplied directly to the transferring fund by the member.
    2. The FIA and ESA details are carried the Member Rollover Transaction content data in an IRR or EPF sent to the transferring fund.

    The ESA details for the sending and receiving parties for any actual ebMS message are carried in the SourceElectronicServiceAddress and TargetElectronicServiceAddress ebMS part properties of the message.

  • #RolloverMIG Fund and Member not Verified It appears from the MIG that the ATO will be matching the SMSF details to the request before attempting to match the member to the SMSF and the request. Presumably if the SMSF is not verified a “fund not verified” response will be sent and the ATO will not attempt to match the member. Therefore our current assumption is only one response per request will be received. Could you confirm this is correct please? Thankyou

    MrsCoops3099 asked 4 months ago

    The SVS will only send one response about why the verification failed. It will check the SMSF details first, and if that fails it will report it as “not verified” without continuing to check the member relationship and details.

  • #RolloverMIG Typo in death benefit tax code SuperannuationRollover.DeathBenefitTax.Code is incorrectly listed in the MIG as SuperannuationRolover.DeathBenefitTax.Code (L is missing).

    MrsCoops3099 asked 4 months ago

    This was an error in the December consultation version and ‘L’ has now been corrected in V0.7.

    Question: Is v0.7 available yet please?

    Answer: On 26 February we published the updated Rollover MIG v3 on the Software Developer website.

    The SuperStream Standards page on the software developers website had been updated to include a new link to a Rollover standard v3.0 page: https://softwaredevelopers.ato.gov.au/SuperStreamStandard

    The Rollovers v3 page contains the latest “draft build” version of the following documents which include all feedback received during the consultation period:

    • Schedule 4a Rollover Message Implementation Guide V3 (MIG) v0.7.
    • Schedule 6 Error code Management v2.1.
    • Rollovers V3 Change log v0.2.

    The documents, along with the relevant SuperStream Change Request are scheduled for discussion and approval at the next SSTC meeting on 6th March.

    The Rollover standard v3.0 page will be used for ongoing publication of documentation relating to the implementation of Rollovers v3.0. https://softwaredevelopers.ato.gov.au/rolloverV3 

    The two Services are also being updated and will be published shortly on the SBR.gov.au website. This includes the updated Business Implementation Guide for both services.

  • #RolloverMIG Can you please advise when the technical artefacts for RolloverMIG 3 & SMSF services will be emailed. There is a dependancy on these artefacts to confirm development start dates

    DavidAms asked 4 months ago

    On the 27 February we published the updated Rollover MIG v3 on the Software Developer website.
     
    The SuperStream Standards page on the software developers website had been updated to include a new link to a Rollover standard v3.0 page: https://softwaredevelopers.ato.gov.au/SuperStreamStandard
     
    The Rollovers v3 page contains the latest “draft build” version of the following documents which include all feedback received during the consultation period:

    • Schedule 4a Rollover Message Implementation  GuideV3 (MIG) v0.7.
    • Schedule 6 Error code Management v2.1.
    • Rollovers V3 Change log v0.2.

    The documents, along with the relevant SuperStream Change Request are scheduled for discussion and approval at the next SSTC meeting on 6th March.

    The Rollover standard v3.0 page will be used for ongoing publication of documentation relating to the implementation of Rollovers v3.0. https://softwaredevelopers.ato.gov.au/rolloverV3

    The two Services are also being updated and will be published shortly on the SBR.gov.au website. This includes the updated Business Implementation Guide for both services.

  • #UnclaimedSuper Have you got any insight as to whether the legislative date will change from 1 July 2019 to a later date?

    compliance asked 4 months ago

    The Treasury Laws Amendment (Protecting Your Superannuation Package) Bill 2018  passed both Houses of Parliament on 18 February 2019 with a start date of 1 July 2019 and is awaiting Royal Assent. While Parliament did accept some amendments to the original legislation they chose not to change the start date. The start date remains at 1 July 2019.

  • Hi Again - were you thinking of adding a link to the compassionate release consultation papers on one of the super community pages?

    Natasha_ASFA asked 7 months ago

    Yes, a message regarding the issues paper will be added to the Super Community page on Let’s Talk.

    Review of the early release of superannuation benefits

  • How did the agenda get circulated for today's meeting???

    Natasha_ASFA asked 7 months ago

    Good afternoon

    The agenda referred to in the meeting was a reference to the following page on Let’s Talk with the list of topics to be covered

    https://lets-talk.ato.gov.au/SuperMeasures/key_dates#39029

  • #CapBreaches The existing explanatory statement appears to focus on employees exceeding a base salary that would cause them to exceed the concessional cap if they have multiple employers assuming 9.5% SG and the maximum contribution base. However, various EAs and funds require an employer to pay in excess of SG (i.e. 10%, 15.4%) and as a result these are considered to be Mandatory contributions. Is there any considerations being made to accommodate these situations as some individuals would exceed their concessional cap well before they reach the $263k salary requirement for this measure. #CapBreaches

    ATowner asked 9 months ago

    The $263K figure is a notional or guide amount based on SG of 9.5%. It is not a threshold specified as a criterion in the draft law. As you note, where the required contribution rates are greater than 9.5% the income causing a breach of the concessional cap limit will be lower.  

    Assuming other criteria are met, an employee will need to show that they are likely to breach the concessional contributions cap ($25,000).

    Please note that an employer shortfall exemption certificate is for SG purposes only and cannot override any super contribution that is required to be made under a workplace award or agreement.