SuperStream Technical Committee
minutes
File ref: [File ref #]
Title:
SuperStream Technical Committee
Issue date:
4 July 2016
Venue:
Australian Taxation Office – 52 Goulburn Street, Sydney
Event date:
8 June 2016
Start: 10:00
Chair:
Ty Winmill
Facilitator:
Ty Winmill
Contact
Louise Ison
Contact phone:
02 62164545
Attendees:
names/section
Ty Winmill, Matt Cheeseman , Graham Dawson, Chao Wang, Ian Colhoun,
Leo Cheung, Walter Divissi, Michael Corrigan, Yong Zhang, Grant Doherty,
Reba Kearns, Gary Jacobs, John Kennedy, Brett Hillier, Matt Rea, Carmen
Kearney, Rodney Bedser, Samantha Smith, Craig Jarmen, David Kerr, Jamie
Hancock
Apologies:
name/section
Matt Giuliano, Paul Larsen
Next meeting
21 June 2016
Agenda item: 1 – Welcome and acceptance of minutes
The minutes from May 2016 were accepted
EXTERNAL
UNCLASSIFIED
Finish: 12:00
Agenda item: 2 – Action Items and next meeting
Action items were reviewed in master action items list. Ty updated the members on future
meetings and advised that we would stay committed to the Wednesday timeslot .
Agenda item: 3 – Services and dashboard – New platform
Walter Divissi updated the group on the Services Dashboard
The following key points were raised in the discussion

There was a meeting with Accenture regarding requirements, performance and
availability. The outcome was a fresh mock-up of the dashboard which will be run past
the SSTC and the GOG

The implementation schedule will be SuperTICK 1, 2 and 3 first followed by FVS and
SuperMatch2

SuperMatch - there have been some issues with the processing of bulk files, it is
crashing on certain types of TFN’s, and ATO are trying to get the priority raised by EST
to get it resolved. Some examples of the issues were end dated TFN’s and compromised
TFN’s

Reba raised a query regarding SuperTICK v3 and the response times. The SLA
mentions that the expected response time for a single response would be a few seconds
but up to five minutes is being seen. Walter responded that the response is meant to be
5 seconds 95% of the time. Ian clarified that the SLA for a single is five seconds not five
minutes however if there are significant amount of transactions taking 90 seconds then
an incident should be raised.

Grant raised concerns with SuperTICK v3, specifically response codes. Grant explained
that SuperTICK was essentially a query, you would send some data and you got back a
response from the ATO. Now with opening and closing of accounts its considered more
transactional in the sense that not only are you providing data to the ATO you are
expecting the ATO to do something with that data and the way the service design has
been made there is no different response that you get back. Grant explained that if he
provides TFN information to the ATO and flags it as being the opening of a new account
potentially he gets back a corrected TFN value so there is nothing to say ATO has
registered this as an open account on our system. It seems as though the design has
been overloaded and needs to have different response codes. Grant advised he would
put a paper together for the SSTC to understand if there is an agreement that there is a
problem with the design.
Agenda item: 4 – Rollovers implementation
Michael Corrigan updated the group on the Rollovers implementation
The following key points were raised in the discussion:

EXTERNAL
UNCLASSIFIED
B2B – industry readiness dates to be distributed, we have received responses back from
the funds about their readiness dates and it is now published on the SIPO site.

Funds that have notified the ATO that they are yet to determine a test partner for B2B
peer to peer testing can use these published readiness dates to assist them in identifying
others that have also not found a partner.

The ATO would like gateways to liaise with funds regarding production cutover dates by
the end of June 2016. For B2B the cutover will be from October 2016 and a draft cutover
plan will be available should be available by the 21 st of July. After feedback has been
received a final version will be published by the 31 st of July 2016.

G2B – we expect our EVTE environment to be available early July, and then we have
processes in place to support EVTE testing. Defects will be addressed through monthly
updates on the EVTE environment.

ASP is developing test scenarios for B2B and we would like to use the same members
for our G2B peer to peer testing.

Carmen asked if ATO or the funds update the FVS certification date? Michael responded
that long term we want everyone to update it. This will be discussed internally and then a
definite answer will be given. John commented that ideally from a funds perspective we
would prefer to have control and the access to make updates to the FVS and if the ATO
wants to limit our ability to receive then that is an issue for the ATO to remedy.
Agenda item: 5 – Guidance notes update

Graham Dawson updated the group on Guidance notes.

The following key points were raised in the discussion:

No new guidance notes have been issued for this meeting

There are currently six guidance notes in progress following the last meeting, two of
which have been published, GN 45 and GN 46

CTER without refund: We need to be very clear in the release notes about the
expectation around the implementation of the guidance note. This refers to something
specified in another guidance note about refund total payment parameter. In that
guidance and the response messaging framework it is noted, because of the transitional
approach to implementation, that parameter is defined as optional but mandatory in
MIG2 (the reference should probably be to Schedule 6 though).

Rollover MIG 2 reconciliation rules: We have added in a table as requested showing the
components. The main discussion is around the provision of error messages. Graham
suggested if you think about the process look at the lowest level there is a requirement
between the two kiwi saver components to be equal. Depending on where an error
occurs, it will probably mean that the other levels will fail so if the kiwi saver components
aren’t equal then the member totals won’t be equal. The first error level should be the
level of processing and the first error level will determine the fact it’s failed and we don’t
need all three levels of error. Reba advised that if the payment doesn’t match then most
people will do payment reconciliation first.

Allowable characters for record count: We will need to rewrite under a new title of
“Validation of record count” and see if we can come up with an approach that’s agreed
about the severity and the expectation when there is a problem with record count either
formatting the validation or a mismatch in the record count versus the actual number of
records
Linkage rules for source ABN and source USI: The only thing that has to be checked is the
impact on the government transactions. Graham will need to talk to Michael and Ian about
that whether the linkage is going to cause a problem with any of the government upcoming
transactions and that will require some further discussion


EXTERNAL
UNCLASSIFIED
DB Funds: There is follow up work to be done from the ABSIA conference and the
Agenda item: 5 – Guidance notes update
working group. No recommendations have been sent to the group.
Agenda item: 6 – Response Messaging
Ty Winmill updated the group on Response Messaging.
The following key points were raised in the discussion:

We have published a list of funds and their compliance with their response messaging
obligation. There are a small number of funds that are taking a couple of additional
months to implement so we are monitoring those in partnership with APRA. Basically the
intent is to get everyone transacting, The key issue is really adoption of the response
messaging framework. We are producing a picture of who is implementing that and will
have a better understanding probably by the next phone hook-up and will distribute it out
of session.

We want to ensure that everyone is implementing the response messaging capability
where the sender flags that they can receive a message and the issue is that we can’t
enforce that because it is not in the regulations but we are trying to get adoption as it has
been around for some time,
Agenda item: 7 – Other business
The following key points were raised in the discussion:

Farewell to Matt Cheeseman, he has been a valued member of the team and his efforts
have been appreciated.

David Kerr sought information on SuperTICK3 and what the next lot of changes look like.
Ian Colhoun advised that this will be covered at the Business Engagement Forum.

John Kennedy would like Duplicate Messages added to the next meeting agenda, we
need to come up with a principle on what duplicate messages are and what we have
responsibility for.
Meeting closed at 12:05pm
EXTERNAL
UNCLASSIFIED