ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 30th 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.1 published 22nd of March 2023	Version 1.22.1 Change Log
Maintenance	Iteration 14 Working Group agenda for 22nd of March 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	21st of March 2023	View in browser here
DSB Newsletter	24th of March 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 7th of April 2023 Link to consultation Video 54 of DP288
Consultation	Noting Paper 280: The CX of Authentication Uplift	UPDATE: See NP296 for continuation of consultation
Consultation	Noting Paper 296 - Offline Customer Authentication	Feedback 17th of April 2023 Link to consultation Video 55 of NP296
Consultation	Noting Paper 289 - Register Standards Revision	Feedback 28th of April 2023 Link to consultation Video 56 of NP289
Easter	NOTE: Next weeks CDR Implementation Call is Cancelled Invitation cancellations will be issued shortly	Have a great and safe Easter break!

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	Eva
ACCC	CTS	Andrea
ACCC	Participant Tooling	Andrew
DSB	CX Standards	Eunice
DSB	Technical Standards - Banking & Infosec	Mark
DSB	Technical Standards - Energy	Hemang
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
1887	In relation to rule 4.6A(a)(ii) and the guidance published in Dec-2022 , should banking data holders plan to build / enhance solution as per current guidance esp around blocking ADR? Or, do we hold-off on this part till the rules are clarified by Treasury?	Please refer to the Article Ceasing Secondary User Sharing for information about 4.6(a)(ii). Noting the complexities involved in complying with the current provision, Treasury is considering whether rule changes are necessary. Unfortunately, we don’t have an update on the timing of any possible rule changes. However, If you are concerned about compliance, we encourage you to contact the ACCC compliance team at accc-cdr.gov.au.
1891	In regards to point 2, I would agree we are the data holder for account data but the rules indicate we are only the data holder for ‘tailored tariff data’ and we don’t tailor our plans, Ergon only offers standing plans. Therefore electricityContract in EnergyAccountDetailV2 should be optional?	Question: Duplicating EnergyPlanTariffPeriod 5 times is possible but too be honest this seems like a poor design. Each EnergyPlanTariffPeriod will be 99% identical with 1 value changing per object. To answer your question, it's possible for the supply charge to change each billing period, particularly for customers that have usage close to the boundary. For example, if in Jan they use 20,000 kWh/y (pro-rated), the bill will have a supply charge of 123.140c. If in Feb, they use 20,001 kWh/y (pro-rated), the bill will have a supply charge of 152.798c Answer: Having multiple daily supply charge for a single plan/connection is a new scenario, I haven't come across this before (don't think It has been bought up in any of the previous consultations). Your point about duplicating EnergyPlanTariffPeriod being inefficient seems valid. The best way to deal with this would be to raise a change request describing the problem (and any potential solution options). It can then be prioritised and publicly consulted via the standards maintenance process so other participants can review and provide feedback as well. Question: In regards to point #2, I would agree we are the data holder for account data but the rules indicate we are only the data holder for ‘tailored tariff data’ and we don’t tailor our plans, Ergon only offers standing plans. Therefore electricityContract in EnergyAccountDetailV2 should be optional? Answer: Note that one of the key differentiating factor between product reference data and consumer data (for which the retailer is accountable) is the consumer. For consumer data, the intent is to represent information about accounts/plans that a consumer has signed up to with a retailer. The electricityContract object captures plan information depending on the context - If its PRD request its about the plan, if its Consumer API request its about the plan the consumer has signed up for. If your concern is about the interpretation of the rules language, we recommend you seek your own legal advice if you have any doubt about how the rules should be interpreted as its each participants responsibility to implement compliant solutions. For your reference you may also find ACCCs revised Compliance guide for data holders in the energy sector useful.
1892	In addition to having a local Agent/representative for services of notices and liaise with ACCC . Are there requirements for a foreign entity ADR to have in country Local representation resources or functions and a physical office.	Thank you for your question. We hope the following information will assist: - A foreign entity may apply to be an accredited person. If the applicant is a foreign entity, the application must state the applicant’s local agent, and the local agent’s addresses for service (rule 5.2(2)(c)). ‘Addresses for service’ is defined under Rule 1.7 to include both a physical address for service in Australia, and an electronic address for service. - Under Rule 5.12(2)(a) an applicant must be a fit and proper person to be accredited, having regard to the fit and proper person criteria at rule 1.9. When considering whether an applicant would be considered a fit and proper person the ACCC will also have regard to associated persons (see definition of “associated person” in rule 1.7(1)). To assist in identifying associated persons, a current organisational chart must be provided. - For more information we recommend reading the CDR accreditation guidelines including the sample application forms. The sample application forms set out what documents/information are required when submitting an application. - Note, while the ACCC can advise on legislative requirements of the CDR, the ACCC does not advise on other non-CDR legislative requirements that may be relevant to a foreign entity seeking to provide services in Australia. - For a list of current accredited persons, including foreign ADRs, go to https://www.cdr.gov.au/find-a-provider.