CDS Future Dated Obligations and Dates

Introduction

When a version of the Consumer Data Standards (CDS) is published, Data Holders and Data Recipients may be obliged to implement the changes by a specified date. This guide explains how to determine the dates on which these obligations must be fulfilled.

Exemption Register

The exemptions register indicates participants for whom exemptions have been granted, and what those exemptions are: 

• https://www.accc.gov.au/public-registers/consumer-data-right-exemptions-register

Future Dated Obligations

The Consumer Data Standards (CDS)  Future Dated Obligations section describes the obligations for all technical specifications and API Endpoints. This sections includes statements indicating that a specific section of the standards will not take effect until a future date, or may cease to have effect on some future date.

In addition, the CDS section for each API endpoint may contain a Future Dated Obligations subsection.

The date provided is the date the participants MUST have the Endpoint implemented and available in production for consumer/ participant use.

If there is no date on either the API endpoint section, or in the Future Dated Obligations section, then there is no current obligation date for the endpoint.

If, in the case of the financial sector, there is no distinction made between major banks and non-major banks in a statement of an obligation, then the obligation applies equally to major banks and to non-major banks. 

For FDOs grouped by topic, see:

• Future Dated Obligations (FDOs) by topic

Consumer Experience

Consumer Experience changes in the Standards align with the Phasing Table described in the ACCC Phasing Schedule. Each of the core features within the Consumer Experience and Guidelines maps to a known Phased deliverable.

Endpoint Scheduling

The Endpoint Version Schedule provides a table of endpoints and dated obligations, with headings for DHs (Data Holders) and ADRs (Accredited Data Recipients).

Obsolescence 

When an API Endpoint is required to be obsolete on a specified date, the information can be found in:

• CDS API Endpoint section
• Endpoint Version Schedule

For an example, see the V1 of the GET Product Detail endpoint. The CDS specifies that this endpoint can be decommissioned by data holders as of August 29th 2020. The endpoint is now out of date, with more recent versions published and implemented. 

Subsections