Payment Management (PMTMGT)

Payment Management is a sub-domain of Obligation Management (OBLMGT). This page contains information and artefacts for Digital Service Providers (DSPs) who have or are interested in developing web services that enable a business or their intermediary to manage their payments to the ATO. The services described below are only deployed on the SBR ebMS3 platform.

For ease of use, services have been organised into the following business processes:

• Set or cancel a direct debit – Allows users to request for the ATO to initiate a single direct debit (DD) of a client's nominated bank account where a Direct Debit Authority is already be in place or to cancel a single DD without cancelling the Direct Debit Authority.
• Payment plans – Allows users to view an account’s eligibility to a payment plan and calculate, create, recalculate, update, cancel, list and view payment plans.
• Generate payment reference number – Allows users to proactively manage their debt by providing the ability to generate PRN details for available accounts and roles.

Image

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.

Set or cancel a direct debit

Direct Debit (2018)

Direct Debit (2016)

Back to top

Payment plans

Service Suite:  Payment Plan (PMTPLN) 2020
Service Name: Payment Plan Eligibility (PMTPLNELG)

Service Name:  Payment Plan (PMTPLN)

Back to top

Generate payment reference numbers

Service Name:  Payment Reference Number (PRN)

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).