ACCC & DSB | CDR Implementation Call Agenda | 3 July 2025 - ConsumerDataStandardsAustralia/standards GitHub Wiki
Sign up: Sign Up
When: Fortnightly on Thursday's at 3pm-4:30pm (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: 426 030 545 881 4
Passcode: 5d7Kp73X
Download Teams | Join on the web
Dial in by phone
+61 2 9161 1229,,538826932# Australia, Sydney
Find a local number
Phone conference ID: 538 826 932#
Join on a video conferencing device
Tenant key: [email protected]
Video ID: 135 792 992 7
- 5 min will be allowed for participants to join the call.
- This call is jointly facilitated by the ACCC and the DSB, and we welcome observers from APRA, OAIC and the Treasury.
We acknowledge the Traditional Custodians of the various lands on which we meet today and pay our respects to their Elders past and present.
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.
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.
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
| ACCC |
ACCC Compliance Audit Report
|
Ursula |
| DSB |
Decisions made by the Data Standards Chair on 30 June 2025
|
Hemang |
| DSB |
Consumer Experience update
|
Michael |
| DSB |
CDR Participant Journey Map Registration is open for a series of workshops on the CDR Participant Journey Maps to be held August. The focus will be on the key touchpoints, needs, pain points, and the types of support participants rely on or struggle with at different stages of their CDR journey.
|
Sumaya |
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards | Version 1.34.1 | Published: 11 April 2025 Change log |
| Standards |
Future Dated Obligations From 14 July 2025, the following Future Dated Obligations will take effect: |
|
| Standards ⭐ |
Consultation Draft 369 Decision 369 (Redirect to App - Draft Standards) was made by the Data Standards Chair on 30 June 2025. These changes will be incorporated into a new release of the data standards. |
|
| Standards ⭐ |
Consultation Draft 370 Decision 370 (Amendment of Banking Decision 338 Obligation Date) was made by the Data Standards Chair on 30 June 2025. These changes will be incorporated into a new release of the data standards. |
|
| Consultation |
Consultation Draft 364 The draft standards arising from Maintenance Iteration 22 have now been published for a further 28 Days of consultation, feedback welcome. The closing date is Today, 3 July 2025 |
|
| Maintenance |
Maintenance Iteration 24 Maintenance Iteration 24 will commence on 9 July 2025 and conclude on 3 September 2025. First call will select candidates for consultation. Consultation Draft 373 has been created for the community to provide candidates for consideration. Candidate change requests nominated by the community will be posted on the issue as the iteration progresses. |
|
| DSB Newsletter ⭐ | The DSB Newsletter is published fortnightly, the next edition will be published on July 11 | |
| CDR Summit 2025 | FinTech Australia will host CDR Summit 2025 on 17 July 2025. Please note that there will not be a CDR Implementation call on this day to avoid the clash. The Summit will bring together key stakeholders to unlock the value and full potential of Consumer Data Right (CDR), offering insights, discussions, and innovative solutions to navigate the evolving landscape of data privacy and empowerment. |
None this week.
Next presentation scheduled for 31 July 2025 on the CDR Participant Journey Map.
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.
| Ticket # | Question | Answer |
|---|---|---|
| N/A |
Filter articles in the support portal Verbal question in the Implementation Call 26/06/2025 Is there a way to filter all articles/artifacts in the support portal that has been changed within a selected period/days so that it can be reviewed in case it is something that needs to be considered, implemented or be made aware of? |
There is no option in ZenDesk to be able to filter articles but there is an “Articles changed in last 7 days” page, but the date range is limited to 7 days. A new page has been created to capture the Articles changed in last 31 days as an alternative. |
| 2544 |
DP338 - New Fee Types - old version of API called DP338 introduces several new fee types and removes 'Variable'. Can you please advise of the expected behaviour for Get Product Detail and Get Account Detail if one of the new fee types is configured, but the pre DP338 version of these APIs is called.For example:
|
The earlier version should respond with the closest fee type that was available in that version. For example, you may find that a VARIATION fee would have most closely aligned with an EVENT type in the previous version, but it would be up to the Data Holder to determine the most appropriate value.If the fee value is truly variable, but the conditional fields in the fee schema require "One of amount, balanceRate, transactionRate and accruedRate" to be provided, then the most appropriate of those fields with a minimum or typical value could be specified. The additionalInfo field could explain the variable nature of the fee as best as possible. |
| 2514 |
Overlapping time of use tariffs We have identified an issue in a data holders CDR energy plan data where overlapping time-of-use periods are being returned for the same tariff, creating ambiguity in determining the applicable rate. For example, A "Night Saver EV Plan" includes an "OFF_PEAK" rate from 12:00 am to 6:00 am and additional overlapping time slots from the general usage network tariff. While the description states that the Night Saver EV rate overrides others during this period, the data holder asks us to rely on the description field where a free text paragraph explains this. We believe that free text descriptions makes it challenging for automated systems to interpret and determine applicable rates. Could the standards provide clarification on whether overlapping time-of-use periods are permitted, and, if so, how automated solutions should interpret and prioritize such overlaps? We seek clarification on how time of use rates are supposed to be structured? We believe they should be non overlapping so that an automated system can select the right time, based on parsing timestamps |
The standards currently do not explicitly prevent sharing of overlapping time of use rates. The DH is expected to share rates aligned with how they would have them defined on their plans, which they share with AER as well. In response to a valid consumer data request, CDR Rule 4.6 requires a primary data holder to disclose the requested ‘required consumer data’ it is authorised to disclose in accordance with the standards. Under Schedule 4, clause 3.2 of the CDR Rules, ‘required consumer data’ in the energy sector includes ‘tailored tariff data’ for a relevant account that is open. ‘Tailored tariff data’ is defined by Schedule 4, clause 1.3, item 8 as ‘product specific information in relation to the plan that applies to, and as tailored to, the arrangement to which the account relates’. The Standards also differentiate between basic energy account information and tailored tariff information. The description of Detailed Energy Account Data in the Standards states that Detailed Energy Account Data ‘includes basic energy account information plus tailored tariff information including charges included in the account or plan’. In response to a request for Detailed Energy Account Data, a data holder should therefore share tariff data that it is authorised to disclose which reflects the actual operating tariffs and charges that currently apply to the account. |
| 2520 |
Consumer dashboard - data holder The consumer dashboard must contain the details of each authorisation to disclose CDR data specified in CDR Rule 1.15(3), including the period for which the CDR consumer gave the authorisation. For authorisations that expire prior to the scheduled expiry date, are data holders required to display the original period for which the CDR consumer gave the authorisation? |
The data holder’s dashboard needs to display the original period for which the CDR consumer gave the authorisation (as required by r 1.15(3)(c)). This is regardless of whether the authorisation expires before or in accordance with the scheduled expiry date. However, there is some flexibility in how a data holder may choose to implement this requirement, as long as the dashboard is simple and straightforward to use (as required by r 1.15(1)(e)). |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
31 July 2025
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 | |
| Advisory Committee | CX Guidelines | Calendar | |
| Support Portal | |||
| YouTube | |||
| GitHub | |||
| Newsletter |