eCommerce SWD TWG - Minutes - Software developers homepage

Software Developer Technical Working Group
Unclassified
Minutes
File ref: N/A
Title:
Software Developer Technical Working Group (SwD TWG)
Issue date:
17 January 2017
Venue:
Phone Conference call: 1800 857 853, then 82135263#
Event date:
18 August 2016
Start: 14:00 AEST
Co-Chairs:
Brian Hughes
Andrew D Smith
Secretary:
Publications:
http://softwaredevelopers.ato.gov.au/eCommerce-SWD-TWG
Email:
SwD TWG [email protected]
Contact
SIPO
Attendees:
STP SwD Community
Apologies:
N/A
Next meeting
TBA
EXTERNAL
Contact phone:
Finish: 15:00
Samantha Chudzinski
1300 139 052
PAGE 1 OF 3
Software Developer Technical Working Group
Unclassified
Agenda item: 1 – Introduction
Brian H
Welcome and brief rundown of the session intent
Agenda item: 2 - Business Design






Michael Karavas
Started by outlining the role of the DWG and the TWG:
DWG – focus on the What and When
TWG – focus on the How to make that happen
The focus on this TWG is on the pay event services so far and the timetables for the other services
coming out
An opportunity to raise issues and concerns for the next TWG that we can address in more detail and in
more time
The design for the pay event report has been based around the existing data that’s collected from the:
- payment summary;
- TFN declaration form; and
- super guarantee reporting.
Reporting at the employee level – year to date figures with the correction to be made in the next report,
not having requirement to go back when an employer finds an error and has to go back and amend
previous reports.
Reporting at the employer level – period amount withholding data
Note – MYOB stated they had submitted questions on the Payroll Event documentation.
Action – MYOB asked to resend to the TWG mailbox.
Action – ATO to record issues from this meeting in the minutes.
Agenda item: 3 - Release Schedule
Mick Ferris
Mick walked through the STP Implementation document specifically the release schedule on page 7.
Documentation provided with the agenda (can be found on SwD site).

A cloud environment has been bought up to compensate for the EVTE environments being down. The
cloud environment has been loosely called EVTE3 for the EVTE delivery. This means anyone who was
in the EVTE2 environment has been placed into the EVTE3 environment (standard inbound
transactions, we are still working on outbound. Payroll event is fine but some other services we are
delivering later may be impacted).
Agenda item: 4 - Solution Implementation
(aimed at new starters)
Mick Ferris
Mick continued to walk through the rest of the STP Payroll Implementation document.
 Any developer who doesn’t have an account manager is to contact the SwD TWG inbox, via the SwD
site etc.

Training for new comers will be provided via the On-Boarding team engagement process
Question raised by the software providers.
1.
SDK – is this new for STP or the Tax Agent?
A: It is the standard SDK. Note – imbedded clients for PLS cannot be used for STP.
2. Validation what technology will this be used to be provided to the software developers?
A – will be in C#.
3. Training – Will this be provided and how?
A – yes through your on boarding and account manager.
EXTERNAL
PAGE 2 OF 3
Software Developer Technical Working Group
Unclassified
4. Where is the documentation being published?
A – use the SBR pages to get the information for developers – SBR.GOV.AU.
Does the SBR site have old documents?
A – Has the SBR1 and SBR2 information. Can use the SIPO Site. But you should identify where the
information is in conjunction with your Account Manager.
Action Item – The site to be used to published to be decided. Could be SIPO to Software Developer Page.
Mick Ferris to consult with STP project team.
Software Provider questions on the schedule.
5. Wholesale onboarding, where is it?
A – this is still in design and is on the schedule.
6. PayEvent Ids for ebms3 messages?
A – this is an action for Mick F to follow up.
Action – Mick Ferris to follow up what on the ebms3 PayEvent message ids.
7. XBRL and XML – do the software providers need to do both?
A – No only one is required.
Agenda item: 5 – Action Items
All
Action items for the STP component have been collated into the regular action item register for ease of use.
Agenda item 6 – Issues
All
Issues for the STP component have been collated into the regular issues list for ease of use.
Agenda item: 7 – Other Items

Brian H
Next regular SwD TWG on the 09/02/2017
Action – Next meeting items to be sent to the TWG mailbox.
o
EXTERNAL
Contact SwD TWG [email protected] for any feedback or issues and please copy SIPO
[email protected] into all communication with the SwD TWG inbox.
PAGE 3 OF 3