ACCC & DSB | CDR Implementation Call Agenda & Minutes | 6 November 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 | Minutes |
|---|---|---|---|
| DSB | Maintenance Iteration Scheduling | Clare | Clare has recently joined the DSB as the new Director for the CDR Data Standards. Clare provided an update on the timing of the maintenance iteration non-breaking changes. Public consultations for the non-breaking changes remain planned for before the end of 2025. However, at this stage the dates are still unconfirmed, please note that the recent newsletter had stated that consultation would be going out in November, but there may be a delay to that consultation. |
⭐ indicates change from the last call.
| Type | Updated | Links |
|---|---|---|
| Standards ⭐ | CDR Data Standards v1.35.1 was published 8 October 2025. The release contains changes from Decision 377 (Amendments to certificate management section). A reminder that there are 6 Future Dated Obligations approaching on November 10 2025: |
|
| Consultation ⭐ |
Energy Switching Experiment report published A report has been published, detailing the issues, opportunities, and findings related to the energy plan switching experiment. The report and accompanying appendices can be found in Consultation Paper 368 on GitHub. |
|
| Survey ⭐ |
End of Year Survey A survey is open to help plan around the holiday period and coordinate the end/recommencement dates of the Implementation Calls and Newsletters. Please complete the survey by 14 November 2025. |
|
| DSB Newsletter ⭐ | The DSB Newsletter is published fortnightly, the next edition will be published on November 14 2025 | |
| Workshop ⭐ | Before we mark the end of 2025, the ACCC will be hosting another CDR NBL workshop on Friday 21 November from 11am to 12pm AEDT. We encourage you to register and/or send any questions you wish to submit prior to the workshop to [email protected]. |
None this week.
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.
| Ticket # | Question | Answer |
|---|---|---|
| 2606 |
Get Account Details v4 March change For Get Account Details v4 DP#338 Decision Paper Banking Products and Accounts, under Eligibility, Features & Constraints, the fifth item listed states for the change: Make the following breaking change (change of format) to address the related aspects of issue #595 - Use of additionalValue field in Product Eligibility Types. Can you please confirm if this change is actually for Get Account details OR only Get Product Details? |
The Get Product Detail endpoint includes the eligibility object which refers to Product Eligibility Types. Both Get Product Detail and Get Account Detail include the fees object which refers to fee discounts and then fee discount eligibility. This object refers to Product Discount Eligibility Types. The change in #338 was to update and align the PENSION_RECIPIENT and STUDENT detail in both Product Eligibility Types and Product Discount Eligibility Types. |
| 2595 |
Rate range in BankingProductLendingRateV3 Many of the non-bank lenders will quote a rate for a lending product based on the assessed risk of the specific applicant. This means that the products essentially have a rate range (dependent on credit worthiness) rather than a specific rate. The IP used to assess credit risk is also very proprietary. How should this be handled in PRD when the specifics of the applicant is not known? Should the minimum rate (offered to lowest risk applicants) be used? Should the tailored flag be set? |
This topic came up in the last maintenance iteration through this issue - #707 - Change to BankingProductLendingRateV3 to support a RANGE. During the iteration, some banking participants suggested that previous guidance or a consensus among participants was that for a product of that nature, the highest rate should be specified, with detail noting that the actual rate may be lower based on application details (as opposed to the other way around). The use of the isTailored flag was also discussed, but that flag typically means that no rate detail would be made available at all, which may not be desirable. No final position has been put forward on issue #707, so if you have any other suggestions or preferences from the options discussed, please add a comment for review. |
| 2607 - 1 |
Personalised pricing for non bank lenders (pre-submitted question) Non bank lenders frequently have personalised pricing. The rate for the product depends on tens of parameters. As such, there is no single rate for the product. However, BankingProductLendingRateV3 has a mandatory field for rate, which is a RateString. This is a single number as a percentage. This prevents a range to be entered. Will there be changes to this standard prior to NBL go-live, or will there be further guidance on what number should be used (cap, collar, mid-point, other)? |
Response for 2595 is relevant to this topic |
| 2607 - 2 |
Campaigns and special offers (pre-submitted question) Non bank lenders frequently run campaigns for discounted rates/fees/etc. These often provide specialised rates based on the specific asset or individual for which the loan is being originated. A given product (e.g. car loan) can have multiple campaigns running at a time (e.g. a discounted rate for a specific car make/model for a 2 month campaign). The standards do not easily allow the discounts/rates/fees for the special pricing to be tied to eligibility (specific make/model of car). Are there planned changes to the standards to allow for this common non bank lending feature, should special offers be excluded or will further guidance be provided on how this should be handled (e.g. to duplicate products for each in-flight campaign)? |
Question taken on Notice to include a technical response and include information from the ACCC, will be brought forward to the next implementation call. |
| Verbal Question 1 | Please can you point me in the direction of the information that a (DH NBL) needs to provide to start their registration on the CDR Portal |
|
| Verbal Question 2 | Are there any recommended vendors for CDR? | No details about vendors for CDR |
| Verbal Question 3 | Under the fees ENUM for Product Reference Data there is no fee type of third party fee and are forced to use "other", is that correct? There is a requirement to capture the fees that are associated with product reference data and there is no ENUM type of third party fee. Is there any work that's being done on adding that as one of the ENUM because it will be commonly used? (eg Broker service fees, channel fee) | Response from an attendee on the call: Once the money gets charged to the account, how that is recovered by the financial institution is not really relevant to the ADR. It is more about the purpose, mechanism and other characteristics of the fee that matter, not the mechanics of where the money goes (eg upfront fee). An example a fee is passed on to a customer that is the same fee from the titles office for a mortgage but is just called the functional meaning of the fee such as a state titles fee, not the mechanics that go on behind the scenes. Event and Upfront are both in the CDR ENUMs so could both be options. If there are a lot of fees in the product (eg 5 of them were broker fees and another 5 were some other third party fee) then there may be a case to raise a change request and have a new type that would catch those common things that happen frequently which would be more useful for data recipients. Some references to some previous requests and discussions about different fees and fee types and how they can be presented: |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
| Member | Minute |
|---|---|
| Tim Ryan | Tim Ryan is a Consumer Representative that has been appointed to the DSAC from 1st August 2025. He is sitting in on a couple of these sessions and other sessions and wanted to let people know that on these calls that all the work that people are doing is directed towards consumer benefits. He is happy to discuss things about issues that participants have got or things they would like to raise from a consumer perspective. You can contact Tim via [email protected] |
Minutes from 23 October Implementation Call: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/ACCC-&-DSB-%7C-CDR-Implementation-Call-Agenda-&-Minutes-%7C-23-October-2025
Thursday, 3:00pm (Canberra Time)
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 |