ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 23 January 2025
When: Weekly every Thursday at 3pm-4:30pm AEST
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
teams@vc.treasury.gov.au
Video Conference ID: 133 133 341 4
Alternate VTC instructions
Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney
Phone Conference ID: 715 805 177#
Find a local number | Reset PIN
Learn More | Meeting options
- 5 min will be allowed for participants to join the call.
We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past and present, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may contact@dsb.gov.au should they have any further questions or wish to have any 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.
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards | Version 1.33.0 | Published: 18th of December 2024 Change log |
| Maintenance | Iteration 22 to commence in February 2025 | Registration open |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 17 January 2025 | View in browser here |
| Consultation | Decision Proposal 361 - Energy LCCD Phase 2 | Feedback closes: 4 February 2025 Link to consultation |
| Consultation | Noting Paper 363 - Applicability of Authentication Frameworks | Link to consultation |
| Feedback | Request for Community Feedback on Issue 674 Note: this is pertinent for Accredited Data Recipients |
Standards Maintenance Issue 674 |
| Guidance | The ACCC has updated fact sheets on CDR representatives and CDR outsourcing arrangements, as well as Guidance for CDR representative principals on ensuring compliance of their CDR representatives to reflect changes made by the v7 CDR Rules package. The revised guidance is available on the CDR website. | - |
| Tooling | JSON schema tools: updated to align with the latest version of CDS (1.33.0) | Repository |
| Standards ⭐ | Transaction Security Ciphers FDO. Ensure your systems support only BCP195 recommended ciphers to meet compliance requirements by March 17 2025. | Future Dated Obligations page |
| Video | 132: Noting Paper 352 - narrated by Neale Morison (12/12/2024) | DSB YouTube Video |
| Video | 133: Noting Paper 360 - narrated by Neale Morison (16/12/2024) | DSB YouTube Video |
| Video | 134: Maintenance Iteration 21 Outcomes - narrated by Neale Morison (24/12/2024) | DSB YouTube Video |
| Video | 135: CDS 1.33.0 Release Walkthrough and Changes - with Jarryd Judd (02/01/2025) | DSB YouTube Video |
| Video | 136: Decision Proposal 361 - narrated by Jarryd Judd (08/01/2025) | DSB YouTube Video |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
| DSB | Energy | Hemang |
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.
| Ticket # | Question | Answer |
|---|---|---|
| 2473 | The option 2 change to the "Get Transaction Detail" in the "new Enums for voluntary disclosure of additional service overlays" #664 proposes the following NPP payment service types. X2P1 BSCT CATSCT IFTI It is our understanding that IFTI payments are not an NPP Payment service type. BRDR is the domestic NPP payment of an IFTI payment (being the actual International Funds Transfer which is a SWIFT payment). Could you confirm whether you are expecting data holders to translate BRDR NPP payments to be represented in CDR Get transaction details as an IFTI nppPayload service type? What is the expectation on the mapping of BRDR to IFTI? Are the additional enums considered voluntary? Do we have the option of not including IFTI? |
An excerpt from a statement in the change request: "An NPP payment may be used as the final leg of an 'inward' IFTI - that is, a payment originating overseas, sent through an NPP participant as an intermediary on the way to another NPP participant as the final destination." As far as we're aware, IFTI is the code recognised/provided by AP+ for international instructions. If your systems or provider/vendor use BRDR as a kind of subset of the IFTI type, then the transactions should still be provided as IFTI. The payment service details are mandatory, even if they require a level of mapping to conform to the standards, similar to most other mandatory fields. |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |