EVENT SUMMARY / CONSULTATION / 11/15/2015 / UNCLASSIFIED
format / EVENT TYPE / ISSUE Date / Classification
industry consultation Summary
Version 1.1 / File Ref: / [FILE NO.]
Title: / ABR API Development Software Developer Consultation
Venue: / Teleconference
FORMAT / Phone Hook-Up
Event Date: / 11 May 2015 / Start: / 14:00 AEST / Finish: / 14:35 AEST
Chair: / John Madelly / Facilitator:
Contact: / John Madelly / Contact Phone: / 02 6216 3477
Participants:
/ Listed below
Apologies:
/ Listed below
next Meeting: / Meetings agreed for early June 2015
PURPOSE
The Australian Business Register (ABR) is proposing to develop Application Programming Interfaces (APIs) to enable third party software vendors to access and implement ABN/TFN registration and maintenance processes through externally-facing APIs, resulting in users being able to access these services through natural systems.
End users of ABR services will be able to connect and interact with ABR services without having to navigate to the ABR transaction site. This will achieve broader accessibility for ABR users registering and maintaining registration details through external providers.
Software vendors will be able to deliver complete and valid ABN applications for registration and ABN maintenance processes within their products.
Key Messages
1. Introduction
2. Background
3. ABR API Development
4. ABR API Registration
5. ABR API Maintenance
6. Next Steps
7. Attachment A – Proposed ABR API Scope
topic/QUESTION / outcome, decision and/or action and due date /The ATO is looking to expose the ABR registration and maintenance functionality – will these services be useful to software developers? / Several software developers present at the consultation phone hook-up stated the services would be useful as they would provide a complete management service within the software. They suggested that it should be as comprehensive as possible to include maintenance (updates and cancellations) as well as registering for tax roles.
Are these API’s a replacement for the ABN Look Up service? / It was advised by the ATO that the ABN Look Up service had not been discussed yet and that the ABR Look Up is only a subset of the ABR data (i.e. ABR Look Up only provides public data).
Will the Industry Codes be affected? / The ATO advised no, not in the present format.
Timeframe for implementation of these services if software developers consume. / The ATO envisages that the ABR Registration and Maintenance API’s will be available for software developer consumption within the next 6 - 12 months. Implementation by software developers will then be at their discretion.
Will the ABR API functionality encapsulate all the services currently available via the ABR? / The ATO confirmed that the functionality being delivered would provide a comparable level of functionality to that currently available via the ABR.
The development of these services are not tied to legislation mandating the usage etc. so software developers can chose to implement the services (once released by the ATO) whenever they choose.
To note, it will be up to the software developers to decide whether to build partial or whole services.
Will AUSkey be the authentication mechanism for these services? / The ATO confirmed that AUSkey will be authentication mechanism.
Will AUSkey in the Cloud also be used for the authorisation/ authentication layer? / The ATO confirmed that AUSkey in the Cloud would also be able to support these services.
Agenda Items 4 and 5 [Proposed ABN Registration and Maintenance pathways] were not discussed in detail at the initial phone consultation. / Action Item:
Software Developer’s to review the proposed user pathways and provide further comments via:
· SIPO mailbox and / or
· At the next scheduled co-design workshops.
Due date: Approximately early June 2015.
Next Steps: Schedule Co-design workshops / Schedule 3 x co-design sessions, SYD, BRI, MEL.
One session will also provide Video/PHU conference facilities in order to include others who cannot attend a co-design workshop in person.
ACTION ITEMS SUMMARY
1. Agenda Items 4 and 5 [Proposed ABN Registration and Maintenance pathways] were not discussed in details at the initial phone consultation.
Action: Software Developer’s to review the proposed user pathways and provide further comments via:
o SIPO mailbox and / or
o At the next scheduled co-design workshops.
ATTENDANCE
ATTENDANCE: CompanyCompany / Representative / Attended /
Tim Wright / Xero / Y
Nagaraj Veerachettiar / GovReports / Y
Azizi Khan / Insyght / Y
Brett Hillier / Pillar / Y
Adam Parkes / Pillar / Y
Ross Thompson / SuperCorp / Y
Mark Ellem / SuperCorp / Y
Barry Males / CCH / Y
Mike Behling / MYOB / Y
Andrew D Smith / MYOB / Y
Tony Cottis / Sage / Y
Joanne @ CCH / CCH / Y
Matthew Addison / Institute of Certified Bookkeepers / Y
Sandeep Gopalan / Impact / Y
Tim Wright / Xero / Y
Nagaraj Veerachettiar / GovReports / Y
Azizi Khan / Insyght / Y
Kate Sheringham / Class / N
Reni Thomas / Oracle / N
Adam Parkes / Pillar / N
Joel Shapcott / View9 / N
ATTENDANCE: ATO / NAME / Attended /
BRR / Lisa Masin / Y
SIPO / Glen Wellington / Y
EST / Brian Shepherd / Y
BRR / Stuart Reed / Y
CAS / Michael Horvath / Y
BRR / John Madelly / Y
BRR / Karen Jackson / Y
EST / Quyen Nguyen / Y
SIPO / Edwina Johnson / Y
ABR / Tom Scott / Y
UNCLASSIFIED / PAGE 5 OF 5