Tax Practitioner - Practice Management (TPPM)

This page contains information and artefacts for web services that enable a Tax Practitioner (TP) to manage their practice information with the ATO.

The ATO provides a number of common artefacts and reference documents to support DSPs (such as the ATO Service Registry and the ATO Service Support Versioning Strategy). These can be found here.

Manage Agent Trust (MAT)

The Manage Agent Trust (MAT) service allows a Tax Agent to create, maintain and remove a Tax Practitioner's trust account, which are then made available to employers and intermediaries through the SBR ebMS3 platform.

Upon providing details of their trust account, this will then enable the Tax Practitioner to receive the EFT reconciliation report which shows details of each EFT refund sent to the tax agent's or BAS agent's nominated trust account. Refer to the Tax Practitioner Client Management Reports MIG (TPCMR) for EFT reconciliation report for implementation details.2014

Name Version number StatusSize Published date
ATO MAT.0001 2015 Package v0.4 Contents.docx0.4Draft212KB16 July 2015
ATO MAT.0001 2015 Package v0.4.zip0.4Draft517KB16 July 2015

Back to top


SBR ebMS3 webservices artefacts

The Australian Taxation Office has developed an ebMS/AS4 implementation extending on the SBR initiative to simplify Business to Government reporting obligations and aligning with the messaging standards chosen for Superannuation Reform. While this implementation replaces the existing SBR message wrapping, it does not replace the eXtensible Business Reporting Language (XBRL) body provided in SBR web services, in fact the ATO implementation of the new system reuses the existing SBR XBRL message body for the majority of the services provided in the new format.

The following information describes how to implement web services consuming the ebMS3/AS4 messaging standard (SBR ebMS3). 

  • SBR ebMS3 web service implementation guide
    The SBR ebMS3 web service implementation guide (WIG) describes common technical components and services that are re-used by all business services. The common services include whole of government gateways that expose services and supports the protocol for message exchange, standard message types, standard response time service levels, standard message structures, a security token service, and a standardised approach to handling business error conditions and transport exceptions.

    There is a separate SBR Core Services WIG. 
  • SBR ebMS3 software developer kit guide
    The SBR ebMS3 software developer kit (SDK) guide identifies the key components and functionality that comprise the SDK solution. Some of these components are re-used from the previously released SBR Core Services SDK and hence the reader is pointed to the reference for existing documentation. For the new components, this document will outline the usage details and the API specification (where applicable).
NameVersion numberStatusSizePublished date
SBR ebMS3 Web Services Implementation Guide.docx1.7Final1.96MB14 December 2017
SBR ebMS3 SDK Developer Guide.docx1.3Final1.80MB18 June 2015


SBR Core Service webservice

The web services components that are available online include:

  • Web Services Description Language (WSDL) files
  • Web Services Implementation Guide (WIG) 
  • Web services policy files
  • Security token message samples
NameVersion numberTypeSizePublished date
SBR web services implementation guide (WIG)2.2dPDF1.5MB18 February 2016
SBR web services description language (Java)  12.1 KB28 March 2013
SBR web services description language (dotnet)  10.2 KB28 March 2013

Last updated: 23 Nov 2017
Page ID: 40962