ACCC & DSB | CDR Implementation Call Agenda & Minutes | 19 November 2026 - ConsumerDataStandardsAustralia/standards GitHub Wiki

imp-call_header

Agenda

Sign up: Sign Up
When: Third Thursday of the month at 3pm-3:45pm (Canberra time)
Location: Microsoft Teams (dial in details are below)

Join on your computer, mobile app or room device
Click here to join the meeting
Meeting ID: 487 742 173 354 95
Passcode: AN6KY2Lp
Dial in by phone
+61 2 9161 1229,,665346196# Australia, Sydney
Find a local number
Phone conference ID: 665 346 196#


Agenda

  1. Introductions
  2. House Keeping
  3. General Updates
  4. CDR Stream updates
  5. Q&A
  6. Any other business

Introductions

imp-call_intro

  • 1 min will be allowed for participants to join the call.
  • This call is jointly facilitated by the ACCC and the DSB.

Acknowledgement of Country

We acknowledge the Traditional Custodians of the various lands on which we meet today and pay our respects to their Elders past and present.

House Keeping

imp-call_house-keeping

Recording

The Consumer Data Right Implementation Calls are recorded for note taking purposes only. Recordings and transcripts are kept securely. No identifying material is provided without the participant's consent. Participants may email [email protected] with any questions or a request to have material redacted from the record.

Community Guidelines

By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.

General Updates

imp-call_updates

⭐ indicates change from the last call.

Type Update Links
Standards Current version of the CDR Data Standards is v1.36.0 (published 4 December 2025).
Consultations ⭐ Current Consultations
The DSB is currently seeking feedback on three consultations supporting the ongoing development of the CDR Standards:
  • FAPI 2.0 Alignment: proposed changes to align the CDR information security standards with FAPI 2.0. Closes: 26 November 2026
  • Minimum Baseline Authentication: proposed minimum authentication requirements to support a secure and consistent approach across the CDR. Closes: 26 November 2026
  • NPP Service Values Alignment: proposed changes to align NPP service values with the service model introduced through NPP Release 10, update relevant terminology and support consistent representation of NPP payment services. Closes: 16 December 2026
  • Survey on implementation effort for CDR Data Standards changes to better understand the time, effort and impacts involved in implementing standards changes across the CDR ecosystem. Closes: 15 February 2027
Survey Implementation Call Survey
A short survey is now open seeking participant feedback on the future direction of the CDR Implementation Call in 2027. Insights gathered will help shape the future format, frequency, content and purpose of the series.
Complete the survey here by 17 January 2027.
Information DSB Domain and certificate changes
The consumerdatastandards.gov.au and cds.gov.au domains and their associated certificates are being retired on 1 January 2027. Organisations should review any references to these domains and update bookmarks, systems, integrations and documentation before this date to avoid potential disruption.
The domains currently redirect to dsb.gov.au and will continue to do so until their retirement. All references should be updated to dsb.gov.au prior to 1 January 2027.
DSB Newsletter ⭐ Subscribe to the DSB newsletter for the latest news on consultations, workshops and key updates.

CDR Stream Updates

imp-call_stream-updates
Provides an update on the activities of CDR streams.

Organisation Topic Member Minutes
AEMO API Uplift - URL Change Project Tommy Siu, Change Analyst
DSB In conversation with the Data Standards Chair
  • Opening reflections from the Data Standards Chair
  • Q&A with the Data Standards Chair and DSB Director
  • Audience Pulse Question: What is the one improvement to standards development or implementation that would make the greatest practical difference to your organisation?
Scott Farrell, Data Standards Chair
Clare McGrath, DSB Director

Q&A

imp-call_q+a

Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.

In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.

To view questions and answers from previous CDR Implementation Calls, click here.

Q&A

Ticket # Sector Question Answer
2760 Energy (Data Holder) Last Consumer Change Date (LCCD) processing and historical electricity usage data

1. The standards state:
The primary Data Holder MUST ensure that the data requested and then shared with the Data Recipient is not outside the bounds of control of the specific CDR Consumer.
For an open account where AEMO holds an LCCD that predates the current retailer’s FRMP commencement date, this requirement seems to prevent the sending of the full requested time period to AEMO and hence negates the intent of the Decision 361 changes.

2. Under Schedule 4, clauses 3.2(2) and 3.2(3) of the CDR Rules, where AEMO electricity usage data relates to the consumer’s association with the premises but predates the current retailer becoming the FRMP, is that data considered voluntary consumer data because it is not “AEMO data in relation to a relevant account”?
LCCD processing

The existing LCCD guidance addresses this scenario.

For an open account, the Data Holder should confirm that the authorising consumer is currently linked to the National Metering Identifier (NMI) and then pass the requested usage period to AEMO without modifying the period.
AEMO then applies the Last Consumer Change Date (LCCD) when determining the usage period to return. The Data Holder should therefore not use its own Financially Responsible Market Participant (FRMP) commencement date alone as the historical boundary where an LCCD is available.

For this scenario, the flow is:
ADR requests the relevant historical usage period → Data Holder verifies the current consumer/NMI relationship → Data Holder forwards the requested period unchanged → AEMO applies LCCD handling → appropriate usage data is returned.

The data returned remains subject to the consumer’s association with the premises and the applicable historical limits. This approach is consistent with the purpose of the LCCD changes to support the sharing of historical usage data where a consumer has changed retailers but remains associated with the same premises.

Historical electricity usage data

A related question was whether historical electricity metering data held by AEMO for a period before the current retailer became the Financially Responsible Market Participant (FRMP) for the consumer’s premises would constitute voluntary consumer data.

Based on the information provided, the requested consumer data appears to be required consumer data. However, whether particular data is required consumer data depends on the specific facts and circumstances, including whether the relevant conditions in the CDR Rules are met. As the ACCC cannot provide compliance advice on individual cases, CDR participants should consider obtaining their own compliance advice where appropriate.

To be required consumer data, the CDR Rules do not require AEMO data to relate only to:

  • an account held with the current retailer; or
  • a period during which the current retailer was the FRMP.
Whether the data is required consumer data depends on whether the relevant requirements in the CDR Rules are met. Under Schedule 4, clause 3.2(2) of the CDR Rules, AEMO data is required consumer data if it:

  • is energy sector data;
  • relates to one or more CDR consumers;
  • relates to a time at which an account holder was associated with the premises to which the request relates;
  • relates to a transaction or event that occurred less than two years before the date of the request; and
  • is held in digital form.
Additional information

For further information on AEMO data, CDR participants may wish to refer to relevant background material, including:

2766 General (Data Holder) Access token grant types included in sessionCount
Should Data Holders include access tokens issued via Client Credentials Grant in the sessionCount figure, or is this metric intended to capture only Consumer-initiated sessions established through the Authorization Code Grant (and, if relevant, decoupled/CIBA flows)?

The Guidance on metrics support article, states:
In the Get Metrics API response schema, a session is counted as the successful provisioning of an access token. The sessionCount is the number of times an access token has been provided.

This definition is flow-agnostic , it doesn't distinguish between access tokens issued via the Authorization Code Grant (i.e. a Consumer completing the consent/authentication journey) versus tokens issued via the Client Credentials Grant (machine-to-machine, no Consumer present, e.g. for calling admin/register-type endpoints).
The current Get Metrics definition describes a session by reference to the successful provisioning of an access token and does not expressly distinguish between access tokens issued under different grant types.

On that basis, for the purposes of calculating sessionCount, the relevant consideration is whether an access token has been successfully provisioned, rather than the specific grant type or authentication/authorisation flow through which the token was obtained.

Accordingly, the current definition should be applied as follows:

Token event: Access token successfully provisioned through Authorization Code Grant
Treatment for sessionCount: Count

Token event: Access token successfully provisioned through Client Credentials Grant
Treatment for sessionCount: Count

Token event: Access token is not successfully provisioned
Treatment for sessionCount: Do not count

Therefore, under the current wording, an implementer should include successful access-token provisioning through both the Authorization Code Grant and Client Credentials Grant when calculating sessionCount.

Applying the definition at the level of successful access-token provisioning, rather than tying sessionCount to a specific grant type or authentication/authorisation flow, also provides a more technology-neutral approach. This avoids requiring the metric definition to enumerate individual flows and reduces the need to update the standard solely because supported authentication or authorisation mechanisms change or additional mechanisms are introduced in the future.

In other words, the determining factor for sessionCount is the successful provisioning of an access token, rather than the particular mechanism used to obtain that token.

We note that the existing definition does not expressly list individual grant types as included or excluded. The above treatment therefore follows the current access-token-based definition rather than interpreting sessionCount as being limited to consumer-initiated or consent-associated sessions.
2791 Banking (Data Holder) Expected response for GET /banking/product API for invalid brand parameter
What should be the correct response for the GET /banking/product API when the "brand" parameter is an invalid one? The term "invalid" could mean a value that does not exist in the system or even can be some random string as the "brand".

How should the response be constructed?
Where the brand parameter contains a value that satisfies the type and constraints defined by the interface contract but does not correspond to an existing brand, the Data Holder should return 200 OK with the standard Get Products response containing no matching products.

A 400 Invalid Field response applies where the supplied parameter has an invalid type or violates constraints defined by the interface contract.

Any Other Business

imp-call_any-other-business

Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.

The Next CDR Implementation Call

The Next CDR Implementation Call

This is our final call for the year. Information, including registration, for next years series will be communicated through the DSB Newsletter.

Minutes from the previous Implementation Call (15 October 2026): https://github.com/ConsumerDataStandardsAustralia/standards/wiki/ACCC-&-DSB-%7C-CDR-Implementation-Call-Agenda-&-Minutes-%7C-15-October-2026

Implementation-related queries may be submitted at any time via the CDR Support Portal. These queries will be reviewed and responded to by an appropriate subject matter expert.

Useful Links

imp-call_useful-links View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.

Data Standards Body Consumer Data Right Digital ID Contact & Media
Chair Standards Accreditation Standards Website
News Maintenance Iteration AGDIS Standards Email
Advisory Committee CX Guidelines Calendar
Support Portal LinkedIn
YouTube
GitHub
Newsletter
⚠️ **GitHub.com Fallback** ⚠️