up accesses and authorisations. This is to be provided out of session (SIPO to publish as part of the outcomes). 28/03 – 06 The ATO to provide an update on the Client Update fixes that were scheduled for March (i.e. information on the proposed deployment date and scope etc.). Chris Thorne Danielle Welsh Closed 11 April 2017: A TFN/ABN fix in EVTE is scheduled for 21 April 2017, with PROD to follow a couple of weeks later, and account managers and working with you to prioritise other client update fixes. 28 March 2017: Mike Behling (MYOB) raised a concern regarding the expected Client Update fixes that were scheduled for March. The fixes were due this weekend but have been postponed due to the SAN work and new date has not been scheduled. An update on the proposed deployment date and scope etc. is to be provided ASAP. 14/03 – 01 Request for SBR taxonomy to be released on the same schedule as the updated ELS specifications (releasing 6 April 2017). Chris Thorne Closed 26 April 2017: The ATO advised that these issues need to be managed on a case-by-case basis and as such, a standing agenda item has been added where members can raise any issues regarding efficiency and effectiveness of the current defect management process. 11 April 2017: The ATO advised that every effort was made to release the SBR specifications, which are more complex than the ELS specs, as early as possible. ELS release 2017.3 is planned for ANZAC day and the still holds. Software developers raised concerns about the impacts the timeframes would have on the quality of their software. 28 March 2017: The ATO was unable to provide an update on this item as Chris Thorne was unable to attend. Mike Behling (MYOB) advised the ATO that this advice is required before the next
17 January 2016: Planning is on track to consult agents. 13 December 2016: Agents will be consulted early in 2017. 29/11 – 03 Produce a document to give advice about how to manage errors – This is in regard to the current state of generic errors like “EM0001 error- please try again”. Craig Woodburn Closed 14 February 2017: Advice has now been distributed to developers. 13 December 2016: A document was provided with the agenda for the meeting of 13th December 2016. Action 13/12-02 Software developers to review and comment on the . 29/11 – 04 Contact Ross Thompson regarding ELS extension matters. Gary Warne Closed 13 December 2016: Completed. 29/11 – 05 Clarify messaging about when developers are required to implement Cloud Authentication and Authorisation (CAA) by addressing it as a document and future agenda item at the roundtable. Yon Halder Closed 28 February 2017: Yon advised that all the discussions with Reckon in regard to when to use CAA have been completed. 14 February 2017: A number of meetings have occurred over recent weeks. Reckon have provided some data to the ATO (Yon) however, more is still to be provided. Once all data has been received the ATO will be able to provide a response. Account Managers were asked to assist in providing some clarity for developers. 31 January 2017: Developers still seeking clarity around when CAA is required – ATO to provide a position on this. 13 December 2016: Yon (Reckon Account Manager) has consulted with Reckon. Reckon and MYOB would like to see this closed with some document giving clarity about when CAA is needed. See follow up action item #13/12 – 03 29/11 – 06 Confirm publication of the details of the next Future and Services Meetings. Gary Anderson Closed 13 December 2016: Completed These are advertised via the Software Services
developers to be involved in the task force to redesign the Client Update (CU). Current CU issues will be managed by the incident process. CU redesign will be managed by the software services project. Software developers will be engaged for co-design through the software services group engagements. 14/11 – 09 Advise via SIPO or Account Managers of their interest to be involved in the task force to re-design the Client Update (CU). Software Developers Nicole Moutia Closed 28 November 2016: Some software developers had submitted interest. Details will be provided to the software services team. Same as for action #14/11-08. 01/11 – 01 Investigate a concern raised by agents about having to give their staff lodge permissions for pre-fill and pre-lodge. *Clarified 29/11 – to provide a mapping document showing the levels of access permissions for forms. Anne Soe Closed 31 January 2017: In the absence of any feedback it was decided to close this action item. 13 December 2016: An XLS document provided with the Agenda for 13th December confirms that pre-fill and pre-lodge functions are available under ‘View’ and ‘Prepare’ permission settings. This means that practitioners do not need to provide lodgment (or ‘Submit’) permission to allow staff to perform these functions. Information outlining the functions that sit within permission groups (a simplified version of the attachment) will be will be added to existing Access Manager and PLS web content to guide tax professionals when setting permissions. Action: All developers were asked to consider the mapping document (see action #13/12-01). 28 November 2016: The rules are that: A prepare permission allows a user to prefill (IITR) and pre-lodge. A submit permission allows a user to lodge, pre-lodge and prefill (IITR). The IITR Business Implementation Guide (BIG) will be
26/07 – 01 ATO to arrange a version of the confidence indicators with some indicative data and explanatory notes. Danielle Welsh Closed 31 August 2016: Based on feedback from software developers we have designed these indicators to report on the PLS. This is the first version of the lodgement indicators and will be tabled for feedback at the next PLS roundtable discussion. We plan to publish updated reports monthly, or as required. 26/07 – 02 Identify the incident number of the Microtax EVTE issue and ask Microtax’s Account Manager to verify the priority. Craig Woodburn Danny Figueiredo Closed 19 September 2016: For INC000019470986 (i.e. delays for ELS-tag prior years), analysis of the provided data and information supplied by Microtax and other software developers established that the design of BBRP for ELS-tagged forms is such that there is a delay before the validation report is received back from ELS processing. 2 September 2016: All Activity Statement action items and CTR issues are closed with resolutions returned to Microtax (via their Account Manager).