SuperStream Technical Committeeminutes

/ File ref:[File ref #]
Title: / SuperStream Technical Committee
Issue date: / 3 June 2016
Venue: / Australian Taxation Office – 52 Goulburn Street, Sydney /
Event date: / 12 May 2016 / Start:10:00 / Finish:12:00
Chair: / Ty Winmill / Facilitator: / Ty Winmill /
Contact / Louise Ison / Contact phone: / 02 62164545 /
Attendees:
names/section / ATO – Ty Winmill, Graham Dawson, Chao Wang, Ian Colhoun, Leo Cheung, Walter Divissi, GBST- Yong Zhang, Qvalent- Grant Doherty, Superchoice- Reba Kearns, BT Financial Group- Gary Jacobs, CBA- John Kennedy, Pillar- Brett Hillier, Compliance Test- Michael Leditschke, IQ Group- Matt Giuliano, Link Group- Matt Rea, Morse- Darren Binskin, NAB Rodney Bedser /
Apologies:
name/section / Matt Cheeseman /
Next meeting / 26 May 2016 /
Agenda item: 1 – Welcome and acceptance of minutes
A special welcome to Walter Divissi. Walter will now be attending the SSTC and will talk through things like the Services Dashboard that the ATO is producing and as we are developing and bringing various products online it is important that we bring the Services Team into the process. The team is looking to fix up some of the current communication processes that we have around the services outages, we have initiated those processes internally and it is expected that over the coming meetings we will be able to provide more detail. The minutes from April 2016 were accepted. /
Agenda item: 2 – Action Items
Action items were reviewed in master action items list /
Agenda item: 3 – Services Dashboard
Walter Divissi updated the group on the Services Dashboard /

Thefollowing key points were raised in the discussion

  • Updates have been made to the Services Dashboard these include –

Added a feedback section

Modified such that SuperTICK label includes reference to version 1 and version 2 SuperTICK v3 and EmployerTICK v2 are also included

Added ‘dashboard availability’ component (i.e. the availability % drops as the ‘error rate’ increases)

Added system maintenance information

Removed reference to Sandbox

Removed reference to real-time

Reinstated hover-over question mark

Changed text such that it’s clear that the dashboard relates to Interactive services

  • Availability – Is measured by number of errors within a 10 minute average, every five minutes. Every five minutes a result is posted and average of errors within the previous ten minutes. Version one is based on external calls, we don’t have synthetic transactions and it’s going to be a process that will take a bit longer to put in place, we need to convince IT Security that it won’t cause problems and in addition will are looking at other alternatives. If the system is unavailable it will show as a gap as there won’t be any activity for it to measure.
  • Test environments – Are being looked at separately by another area
  • Walter discussed feedback and responses and approximate timeline
  • The intent is to keep this group updated through the SSTC to where we are at regarding delivery. Walter to decide out of session if there is anything he would like clarified.

Agenda item: 4 – RM Compliance Guide

Ty Winmill updated the group on the Response Messaging Compliance Guide

The following key points were raised in the discussion:

  • A note has been sent around that describes what you need to do to be compliant with Response Messaging, no additional information has been added, we are just bringing to the fore what is already published - Schedules and the Response Messaging Framework
  • There has been a survey done to understand everyone’s compliance with the Response Messaging Framework so we can get a sense of who has picked up those processes. The key is we want response messaging on by the 31stof May 2016.
  • Grant raised the point, if someone is not following the framework then there responses are useless because they are essentially counterproductive, it is requiring us to take action to contact the fund to say what do you actually mean by this. If a fund is not following the framework then we may be reverting to an out of band process until they can align with that. Grant advised he will be sending out an email to recipients we will be offering to assist the sender getting the fund to align with it.
  • Ty reiterated that the implementation cannot be enforced. There is a plan to get out to the group a picture off who is adopting it and who is not and then we can deal with those who are not picking it up.
  • The RM compliance Guide is published on the SSTC page

Agenda item: 5 – Response Messaging Framework
Graham Dawson updated the group on Response Messaging Framework.
The following key points were raised in the discussion:
  • Version 1.1 was sent out a couple of weeks ago and we have not received any comments back. This will be published as V1.1 on Monday morning providing we have no comments back, this will replace V1.0 on the website
  • There were some corrections, updating examples as well as adding some examples for rollovers and just to make it more readable we took out the Guidance Notes and just left the links to the Guidance Notes
  • Grant had some typo’s that he will send through

Agenda item: 6 – Rollovers Conformance Testing
Graham Dawson updated the group on Rollovers Conformance Testing.
The following key points were raised in the discussion:
  • The conformance testing guide V2 was sent out for review. Comments back by the latest end of next week if possible
  • The conformance testing guide represents the minimum set of tests that needs to be done. Through the document the section 20c notice isn’t there at the moment and will be added in a later version. There were some test cases that were removed relating to payment reconciliation and a note was added on the optional test for the use of other tuples.
  • Feedback to the Super Stream Standards Mailbox

Agenda item: 7 – Schematron
Chao Wang updated the group on Schematron.
The following key points were raised in the discussion:
  • Rollover Schematron on track for zero defects by next Wednesday which means if we got the final drop on Wednesday we can do the final check then publish it
  • Contributions 1.4 and 2.0 we definitely have a draft for both of them but at the moment we are looking at some performance questions before we distribute it any further

Agenda item: 8 – DB additional elements

Graham Dawson updated the group on DB additional elements.

The following key points were raised in the discussion:

  • A paper was distributed for review which represents documentation of the additional elements that were identified by the working group, so it is a separate document for the moment just to avoid the clutter of Guidance Note 19
  • These are the additional elements proposed. Feedback was received pointing out some errors which will be corrected.
  • SSTC members were asked to review the elements in the document in terms of agreement that they will be added to the existing set of harmonised Guidance Notes
  • Feedback will be circulated. In relation to the existing list of elements in the Guidance Notes this set is an additional set that will be added to the harmonised set in Guidance Note 19. This also has an impact on Guidance Note 15
  • There is another whole discussion that will be put in a separate Guidance Note, which is the rules around the other details tuples and also around the other amounts tuples particularly in relation to financial amounts. There is a whole section in Guidance Note 15 that needs to be brought into that single Guidance Note, particularly rules around other amounts and if we publish a separate Guidance Note we can deal with a lot of those issues together.
  • The additional data elements will go into Guidance Note 19, there will be implications for the SAFF. There are some additional elements that would have to be added to the SAFF. We can improve the documentation by adding a straight listing of the elements as an additional reference. We will supersede Guidance Note 15 then we will publish an additional Guidance Note on rules around tuples. Timeline will be discussed

Agenda item: 9 – Guidance Notes

Graham Dawson updated the group on Guidance Notes.

The following key points were raised in the discussion:

  • There was an action from last meeting to publish a list of Guidance notes that are in process, it is a simple list at the moment. It includes values of not started, started, draft (internal draft) ready to go to SSTC and SSTC means the group has seen it and it is being discussed
  • At next PHU everything listed as draft will be presented
  • PRN for direct debits to be added to GD list of things to do (has been added to defect list)
  • Multiple employer with same ABN (has been added to defect list)
  • Grant introduced SourceABN+USI for IRR and RTR messages. This will be added to the agenda at next SSTC
  • Grant sought clarification around SuperTICK v3 trustees have received a letter around opened and closed accounts needs to be reported by SuperTICK v3. Where in the legislation does it say this? It is understood that the ATO has not released a legislative instrument to explain what trustees specifically have to do and under what timeframes.
  • Reba has requested some sample messages of the SuperTICK format and has not heard back, Ty advised Reba to email him.

Agenda item: 10 – Other Business
The following key points were raised in the discussion:
  • Responsibility for duplicate messages, if it is a resend of a message you use the same message id and the same conversation id and it is recognised as duplicate there are some instances when the same message id is being used and they are new messages, the payment has arrived and the messages on the queue are duplicates. ATO to follow up.

Meeting closed at 12:08pm

External

unclassified