ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 2nd of March 2023

CDR Implementation Call Banner

Agenda & Meeting Notes

When: Weekly every Thursday at 3pm-4:30pm AEDT
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
[email protected]
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

Agenda

Introductions
Actions
CDR Stream updates
Presentation
Q&A
Any other business

Introductions

5 min will be allowed for participants to join the call.

Acknowledgement of Country

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, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

House Keeping

Recording

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 [email protected] should they have any further questions or wish to have any 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.

Updates

Type	Topic	Update
Standards	Version 1.22.0 published 23rd of December 2022	Version 1.22.0 Change Log Release video 1.22.0
Maintenance	Iteration 14 Working Group agenda and minutes for 22nd of February 2023 published	Check out the agenda here
Maintenance	Iteration Candidates are in consultation	Check out the Project Board See "Iteration Candidates" column for the list
TSY Newsletter	To subscribe to TSY Newsletter	Link here
DSB Newsletter	To subscribe to DSB Newsletter	Link here
TSY Newsletter	13th of February 2023	View in browser here
DSB Newsletter	24th of February 2023	View in browser here
Consultation	Decision Proposal 229 - CDR Participant Representation	Placeholder: no close date Link to consultation
Consultation	Decision Proposal 267- CX Standards Telco Data Language	Feedback extended with an end date to be determined pending the making of the telco rules. Link to consultation
Consultation	Decision Proposal 275 - Holistic Feedback on Telco Standards	No Close Date Link to consultation
Consultation	Noting Paper 276 - Proposed v5 Rules & Standards Impacts	No Close Date Link to consultation
Consultation	Noting Paper 279 - Accessibility Improvement Plan	No Close Date Link to consultation
Consultation	Decision Proposal 288 - Non-Functional Requirements Revision	Feedback 31st of March 2023 Link to consultation
Consultation	Noting Paper 292 - Approach to developing Data Standards for the Non-Bank Lending Sector	Feedback 24th of March 2023 Link to consultation
Workshop	7th of March 2023 Action Initiation Workshop 01	Registration for Workshop
Workshop	Canvas PDF	Found on Noting Paper 291
Tools	Test documentation 1.0.4 released	Link to Test Documentation
Survey	CDR Implementation Call over April 2023 There are a number of public holidays in the month. We would like to know if the Community would like to cancel some of the Calls during April 2023	Vote on your preferred option

CDR Stream Updates

Provides a weekly update on the activities of each of the CDR streams and their stream of work

Organisation	Stream	Member
ACCC	CDR Register	Emma
ACCC	CTS	Andrea
DSB	CX Standards	Eunice
DSB	Technical Standards - Banking & Infosec	Mark
DSB	Technical Standards - Energy	Hemang
DSB	Engineering	Sumaya
DSB	Technical Standards - Register	James

Presentation

None this week.

Q&A

Questions on Notice

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.

Answer provided

Ticket #	Question	Answer
1655	Following your response to our Zendesk question #1655 regarding a data holder with two or more brands in the CDR ecosystem - "does eligibility in one brand mean the data holder is obligated to share closed accounts in another brand if there are only closed accounts in that other brand?". Your response suggests "yes, this is required". This has very significant ramifications for all multi-brand data holders. Using a well-known example - Westpac and St George - both are brands of the Westpac Banking Corporation, both operate under the same ABN and AFSL and credit licence. Does this make them the same Data Holder? If it does, then your response to #1655 suggest that a PAST client of St George that has closed their last eligible St George account (within the past 24 months), but that client is still eligible for data sharing to Westpac (has Westpac online banking and an open Westpac account), then they must be able to data share their closed St George accounts. Is this right? As if this isn't difficult enough, the challenge becomes even worse with Joint Accounts. Say one of the Joint Account Holders is eligible in Westpac, but the other does not have online Westpac access. But what if the other is eligible in his/her own right on their own individual account in St George. According to your logic, each joint account holder is 'eligible to the data holder' (albeit across separate brands), so - somehow - Westpac's open banking eligibility rules engine would have to 'reach across' into the St George (and indeed any other Westpac-owned brand such as BOM, RAMS, etc) to verify if each joint account holder is eligible to the Westpac data holder somewhere amongst all brands. In real-time, and within the strict NFR response time constraints. It will dramatically simplify data sharing eligibility checking if the ACCC/DSB add clarification that 'within any digital channel, WITHIN A SINGLE BRAND'. This clarification will also not limit data sharing generally. Tightening up further, please clarify and distinguish between 'channels' and 'brands'.	Thanks for your patience with this. We have updated our guidance on this topic. See link here: https://cdr-support.zendesk.com/hc/en-us/articles/4871126055567 If the approach outlined in the guidance raises implementation challenges we are encouraging those affected to provide feedback to Treasury at [email protected]. Alternatively, if you are concerned about compliance, you can contact the ACCC on [email protected].
1866	We seek your clarification regarding these 2 matters: 1. Would you be able to elaborate the definition of account vs balance vs purse in the Banking API? Why do both balance and purse have a currency field? We might have multiple interpretations to consider. 2. For our Organisation, if the customers just signed up, they will not have any bank/ account number details with us, until they make their first balance top up, in such case will CDR expect this customer can still connect their user account to ADR with empty/ no accounts or shall we prevent this to happen?	Question 1. Why do both balance and purse have a currency field? We might have multiple interpretations to consider. Answer 1. The account balance fields may represent the only balance for a single currency account, or the default balance for a multi-currency account such as a travel card. All currencies in a multi-currency card or account should also be described as a 'purse' in the balances schema of the account, each with its own balance amount and currency. This is described a bit further in this article - https://cdr-support.zendesk.com/hc/en-us/articles/900004041986-Travel-Money-Card-Balance Question 2. For our DH, if the customers just signed up, they will not have any bank/ account number details with us, until they make their first balance top up, in such case will CDR expect this customer can still connect their Wise user account to ADR with empty/ no accounts or shall we prevent this to happen? Answer 2. Unless I've misunderstood your question, it seems like you may be wondering how to determine whether a consumer is eligible for sharing. The CDR rules provide a definition for an eligible consumer under 1.10B Meaning of eligible, and provide a further reference for the banking sector.