ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 27th of July 2023

CDR Implementation Call Banner

Agenda & Meeting Notes

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
[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
Updates
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

⭐ indicates change from last week.

Type	Topic	Update
Standards	Version 1.25.0	The latest version, 1.25.0 was Published on 8 July 2023.
Maintenance	Maintenance Iteration 16 ⭐	Meeting #2 was held yesterday 26/07/2023, minutes will be available in the next day or so, check here. Email [email protected] to request an invitation
TSY Newsletter	To subscribe to TSY Newsletter	Link here
DSB Newsletter	To subscribe to DSB Newsletter	Link here
TSY Newsletter	27th of June 2023	View in browser here
DSB Newsletter	21st of July 2023	View in browser here
Consultation	Decision Proposal 229 - CDR Participant Representation	Placeholder: 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	Noting Paper 280: The CX of Authentication Uplift	No Close Date Link to consultation
Consultation	Decision Proposal 306 - Updates to Banking Product and Account Detail ⭐	Feedback extended now closes on: 11th of August 2023 Link to consultation
Consultation	Noting Paper 307 - LCCD Consultation Approach	No Close Date Link to consultation Video
Consultation	Noting Paper 308 - Categories of Standards	No Close Date Link to consultation
Consultation	Decision Proposal 314 - Last Consumer Change Date (Phase 1)	8 August 2023 Link to consultation
Consultation	Decision Proposal 316 - Non-Bank Lending sector alignment ⭐	25 August 2023 Link to consultation

CDR Stream Updates

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

Organisation	Stream	Member
ACCC	Register and Accreditation Application Platform	Eva
ACCC	Conformance Test Suite	Christian
ACCC	Compliance	Seamus
DSB	Consumer Experience	Bikram
DSB	Technical Standards - Energy	Hemang
DSB	Technical Standards - Register	James

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
1920	Part 1 We have reviewed the Zendesk article in relation to the notification to account holders for secondary user data sharing https://cdr-support.zendesk.com/hc/en-us/articles/6694655881871-Rule-4-28-Notification-requirements-Frequency-of-notifications As we are using email as notification mechanism and will be notifying the account holder every time data is shared for an authorisation set-up by secondary user, we wanted to check the following Can we provide account holder an option on our digital channel to suppress the emails, similar to the joint account notification rules? For example, a toggle button (ON / OFF), if they want to receive the data sharing notifications every time the data is being shared. We think that there will be too many notification emails to the account holder, hence wanted to check if we can provide above control to them. The article doesn’t provide that level of information, hence seeking clarity. Part 2 Based on the wording in the updated guidance, we wanted to confirm if the following understanding is correct, We need to send notification to the account holder when the following happens, a secondary user amends or withdraws an authorisation; or an authorisation given by the secondary user expires. We don’t need to send notification to the account holder, whenever an accredited person makes a consumer data request on behalf of a secondary user. For example, whenever the ADR makes an API call to getTransactions	Part 1 The knowledge article concerning rule 4.28 has been updated. The revised article clarifies that the notification requirements apply if an accredited person makes a consumer data request on behalf of a secondary user and one of the following occurs: - a secondary user amends or withdraws an authorisation; or - an authorisation given by the secondary user expires. Part 2 Yes, a data holder is not required to notify an account holder every time an accredited person makes a consumer data request on behalf of a secondary user. The notification requirement only arises if an accredited person makes a consumer data request on behalf of a secondary user and: a secondary user amends or withdraws an authorisation; or an authorisation given by the secondary user expires. Therefore, if an accredited person makes a consumer data request on behalf of a secondary user and there is no change to the secondary user’s authorisation (i.e no amendment, withdrawal or expiry), the data holder would not be required to notify the account holder.
2030	With regard to item #1965 recorded in the ACCC & DSB CDR Implementation Call Agenda & Meeting Notes 1st of June 2023 meeting, specifically item 2 which relates the Metadata Update API The last published information that we can find is described in the following links, which suggest that the API has yet to be implemented 1) https://github.com/ConsumerDataStandardsAustralia/register/issues/43 2) https://github.com/ConsumerDataStandardsAustralia/register/issues/53 Further, the following advice regarding Metadata refreshing makes no mention of a forced refresh through the Metadata Update endpoint. https://cdr-support.zendesk.com/hc/en-us/articles/4411345019791-Data-Holder-cache-update-periods Could you please clarify if there was formal advice regarding the implementation of the endpoint?	Please refer to the Metadata Update section of this guidance - Metadata Update.
2038	We are currently reviewing any potential implications arising from the approval of Decision proposal #585 relating to the Deposit and Lending Adjustment Rate type clarification that has been introduced into Consumer Data Standards version 1.25.0. The requirements in relation to Adjustment Rate Types raises a number of questions in relation to extract and reporting of some elements of Rate data and in particular in relation to items such as Honeymoon and/or Introductory rates which are stored as the applicable Interest Rate and not a rate to be deducted from the base rate. Reviewing the DSB Product Comparator tool indicates this is an issue across a number of Data Holders. In order to be fully compliant with the interpretation for Adjustment Rate types will require system changes to perform a calculation between the stored value and the base rate in order to convert back to an adjustment rate. This appears to deviate from the intention of the standards for Data Holders to deliver available stored data and not “manufactured” data. Is it the expectation that Data Holder will perform calculations against stored data as a result of the clarification included in the standards version 1.25.0? Is a Honeymoon rate considered to be an Adjustment rate type or is it a Fixed rate type that applies for a specific “Honeymoon” period similar to fixed rate loans where both would revert to a “variable” type at the end of the agreed period?	As there would be minor adjustments required for nearly all fields depending on the variety of source systems used by data holders, translating or calculating values to meet the requirements of the Data Standards is not considered manufacturing data. The clarification in 1.25.0 was to ensure data quality and consistency, but the descriptions of the fields did not change, therefore the requirement to calculate, if necessary, did not change. It is up to data holders to determine the correct way to present their data, but I think there could be at least three ways to describe a 'honeymoon' rate a VARIABLE base rate (e.g., currently 5%) with an INTRODUCTORY discount (-1% for 12 months) = 4% a FIXED base rate (e.g., 5% for 2 years) with an INTRODUCTORY discount (-1% for 12 months) = 4% a FIXED base rate (e.g., 4% for 2 years, which may revert to a different VARIABLE rate) = 4% An alternative to the INTRODUCTORY discount type could be DISCOUNT, but the Standard only accommodates a 'period of time' to be specified in the additionalValue field for the INTRODUCTORY type.