ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 15th of September 2022

CDR Implementation Call Banner

Agenda & Meeting Notes

When: Weekly every Thursday at 3pm-4.30pm AEST
Location: WebEx, quick dial +61-2-9338-2221,,1650705270##

Meeting Details:

Desktop or Mobile Devices https://treasuryau.webex.com/treasuryau/j.php?MTID=m9614a7c6166155d3d950a8999e437f9f Once connected to your meeting remember to start your audio and video
Please mute when you are not speaking.

Video Conferencing (VC) Rooms
Use the remote control or touch panel and dial the number indicated below:
External VC Room: [email protected]

Phones - AUDIO ONLY

Primary Australia: +61-2-9338-2221
Quick Dial: +61-2-9338-2221,,1650705270##
Other Global Numbers: https://treasuryau.webex.com/cmp3300/webcomponents/widget/globalcallin/globalcallin.do?MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&serviceType=MC&serviceType=MC&serviceType=MC&siteurl=treasuryau&siteurl=treasuryau&siteurl=treasuryau&apiname=globalcallin.php&apiname=globalcallin.php&apiname=globalcallin.php&rnd=6124483603&rnd=6124483603&rnd=6124483603&tollFree=0&tollFree=0&tollFree=0&ED=1403111402&ED=1403111402&ED=1403111402&needFilter=false&needFilter=false&needFilter=false&actappname=cmp3300&actappname=cmp3300&actname=/webcomponents/widget/globalcallin/gcnredirector.do&actname=/webcomponents/widget/globalcallin/gcnredirector.do&renewticket=0
Meeting Number/Access Code: 165 070 5270

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.19.0 Published on 13th of September 2022	Link to change log here
Maintenance	Maintenance Iteration 12	Last meet on 14th of September 2022 Agenda for the Final meeting here
Maintenance	Decision Proposal 259 - Maintenance Iteration 12	Changes, meeting notes and updates for the iteration can be found here
TSY Newsletter	To subscribe to TSY Newsletter	Link here
DSB Newsletter	To subscribe to DSB Newsletter	Link here
TSY Newsletter	31st of August 2022	View in browser here
DSB Newsletter	9th of September 2022	View in browser here
Consultation	Normative Standards Review (2021)	No Close Date Link to consultation
Consultation	Decision Proposal 229 - CDR Participant Representation	Placeholder: no close date Link to consultation
Noting Paper	Noting Paper 255 - Approach to Telco Sector Standards	Link to consultation
Noting Paper	Noting Paper 258 - Independent Information Security Review	Link to consultation
Consultation	Decision Proposal 263 - Telco Accounts Payloads Feedback closes: 16th of September 2022	Link to consultation
Consultation	Decision Proposal 267- CX Standards Telco Data Language Feedback closes: 15th of September 2022	Link to consultation
Feedback	Feedback on the CDR Implementation Call Seeking informal feedback on the CDR Implementation Call. What we can improve, what you find value with and any other ideas This will close tomorrow 16th of September 2022	Link to survey
End of year	Starting to plan out end of year shut down period.	The DSB will issue a survey in October to get your feedback into when the CDR Implementation Call should pause in 2022 and recommence in 2023
Public Holiday	Next week on the 22nd of September 2022 the CDR Implementation Call will be cancelled	Working on a written update format for the Q&A, updates and actions
Product Comparator	New URL! We've updated the Banking Product Comparator to the Product Comparator Demo. Please update your bookmarks. The driver for this change is to remove the sector specific nature and begin to expand it's support. Apologies for any inconvenience experienced as we make the change.	Please find the new url here: https://consumerdatastandardsaustralia.github.io/product-comparator-demo/
Feedback	We're looking for feedback and input on the next iteration of the Product Comparator! If you have ideas, feature requests or feedback on how we might take the platform to the next level: please reach out to: [email protected] or [email protected]	The DSB is keen on your usage as well and how this can enhance your experience

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 Harvey
ACCC	CTS	Andrea Gibney
ACCC	CDR Sandbox	Andrew Grady
DSB	CX Standards	Michael Palmyre
DSB	Technical Standards - Energy	Hemang Rathod
DSB	Technical Standards - Telecommunications	Brian Kirkpatrick
DSB	Technical Standards - Banking & Register	Mark Verstege
DSB	Technical Standards - Engineering	Sumaya Hasan

Presentation

None.

Q&A

Questions will be received by the community via WebEx 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
1263	This article seems to be ambiguous or conflicts with another related to ineligible accounts. The assumption above is that when a participant dies they become ineligible, however ineligibility is outlined in the other article as a revocation (not an expiration). Should the Holder be sending notifications (via the ADR) to a dead person?	The ACCC's view is that after a CDR consumer dies they become ineligible for the purpose of the CDR Rules. This is on the basis that the definition of “eligible” in rule 1.10B(1)(a)(ii) refers to an “individual”, which we interpret to mean a living, natural person. This means that when a CDR consumer dies their authorisations expire (see rule 4.26(1)(c)). Note that the CDR Rules do not provide for authorisations or consents to be ‘revoked’, but we note this terminology is used in the Data Standards. DSB has confirmed with us that from a technical perspective the term ‘revoke’ in the Data Standards is the equivalent of ‘withdrawal’ in the CDR Rules. We will liaise with DSB to review the other articles you have highlighted with a view to ensuring consistency.
1695	Population of validFromDate for EnergyServicePointDetail <br? Clarification on validFromDate and lastUpdateDateTime will be the the max updated date for all standing data records.	Captured it in the MI12 holistic thread - https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/530#issuecomment-1243566389
1707	We are currently in discussion with a Data Holder which refuses to share the original description of shared transactions through CDR channel after the relevant customer explicitly provides authorisation/consent for the relevant data cluster (i.e. bank transaction data). WE have attached a screenshot of sample transactions (and their descriptions) which our system received from CDR channel. As you can immediately notice, there are transactions with masked descriptions - such as BILL PAYMENT and RETAIL PURCHASE - which does not provide the level of information available from the data holder's other digital channel (such as the data holder's internet banking, mobile app, etc.). Would you be able to advise: - whether it would be right for the customer to expect the same information via other digital channel to be shared via CDR channel? - whether there is an article we could refer to for clarification on this?	Data holders must comply with the relevant CDR Rules and Standards in sharing this information, including the Banking APIs within the Standards. The Banking APIs contain a mandatory requirement that the description field should show the transaction description as applied by the financial institution. The knowledge article on Transaction Fields: Description and Reference clarification clarifies this and states that the description field intends to capture the description of the transaction as it would be presented in Internet Banking or on a statement. We encourage you to seek independent advice if you require additional information about the application of the rules to a specific scenario as the ACCC cannot provide specific compliance advice.
1715	This query is re a new entrant in the market i.e where an entity receives a new ADI license the CDR obligations will need to be met if they have eligible products and eligible consumers. Presume the compliance timeframes will be managed via a rectification schedule as per usual process however is there any guidance for entities that are working towards getting an ADI license for the first time.	We note that ADIs do not need to undergo an accreditation process to become a data holder however, if a data holder wishes to receive CDR data, it must apply for accreditation as a data recipient. Please refer to the knowledge article titled ‘Is accreditation needed for ADIs as data holders?’ for further information. As an ADI, an entity may have data holder obligations if they have eligible products and eligible consumers. The knowledge article on Assessing whether a product is in scope for CDR may also be helpful as it includes information regarding whether a particular banking product is in scope for sharing under the CDR. The Compliance guide for data holders in banking then provides a range of information in relation to the obligations of data holders in the banking sector which should provide guidance to a new entrant in relation to the obligations. It is the responsibility of the entity to assess if they have banking products which are in scope and that they can meet the requirements of Data Holders under the CDR framework.