ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 22nd of September 2022

CDR Implementation Call Banner

Agenda & Meeting Notes

The CDR Implementation Call is CANCELLED this week.

Please see the written updates below.

Updates

Type	Topic	Update
Standards	Version 1.19.0 Published on 13th of September 2022	Link to change log here
Standards	Version 1.20.0 will contain changes from Maintenance Iteration 12
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
Maintenance	Maintenance Iteration 13 Commences 5th of October 2022	Moved by one week to accommodate public, school holidays and leave absences
Maintenance	Maintenance Iteration 13 Schedule	MI #13 Kick-off and backlog review - 5th of October 2022 @2pm AEDT for 2 hours MI #13 Consultation - 12th of October 2022 @2pm AEDT for 2 hours MI #13 Proposal Checkpoint - 26th of October 2022 @2pm AEDT for 2 hours MI #13 Approvals and Documentation - 9th of November 2022 @2pm AEDT for 2 hours MI #13 Retrospective and feedback - 23rd of November 2022 @ 2pm AEDT for 2 hours
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	16th 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 264 - Telco Invoice Payloads	Link to consultation
Consultation	Decision Proposal 265 - Telco Billing Transactions Payloads	Link to consultation
Consultation	Decision Proposal 266 - Telco Balance and Usage Payloads	Link to consultation
Consultation	Decision Proposal 267- CX Standards Telco Data Language Feedback closed - open for comment while Rules v5 consultation is open	Link to consultation
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
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: contact@consumerdatastandards.gov.au or support@cdr-support.zendesk.com	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	Update
ACCC	CDR Register	No update for this week.
ACCC	CTS	The CTS team has released an updated test plan for data holders, V4.0.1. The new test plan has improved functionality which provides support for an increased range of Register API versions. As with all CTS Test Plans, please contact your on-boarding officer to determine the appropriate version for your situation.
DSB	CX Standards	Authentication The team is currently working on research synthesis and progressing with a noting paper on CX metrics. Consent review CX research currently in progress to identify opportunities for simplification in the consent flow (ADR-side aspects). Telco With the v5 Rules out for consultation, the DSB will leave the DP267 open for comments while considering existing feedback. The first round of CX research (qualitative) wrapped up last week and a second round of research (survey) is currently in progress. Findings from research and existing feedback will inform the development of version 2 of DP267. DP229 CX is wrapping up the decision proposal on CDR Participant Representation and plan to publish it soon.
DSB	Technical Standards - Energy	Maintenance Iteration 12 Decision Proposal is being drafted
DSB	Technical Standards - Telecommunications	Three new Decision Proposals have been published: Decision Proposal 264 - Telco Invoice Payloads Decision Proposal 265 - Telco Billing Transactions Payloads Decision Proposal 266 - Telco Balance and Usage Payloads
DSB	Technical Standards - Banking, Infosec & Register	No update for this week
DSB	Technical Standards - Engineering	Please remember to submit feedback on the Product Comparator to contact@consumerdatastandards.gov.au

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
1610	Can I please have some guidance on where I can find the standards or information for best practices around incentivising consumers to share their data example: to encourage consumers to share their data with us as an ADR we would like to offer bonus points, lower interest rates or gift vouchers etc	We sought input from various teams/ departments due to the interest in this topic and the response has been posted as a knowledge article here: https://cdr-support.zendesk.com/knowledge/articles/5511527614351/en-us?brand_id=360003444372
1712	Couple of weeks back, while we're doing a Production Verification Test through an ADR, For Get Transaction Detail API and for an NPP payment, we're (Data Holder's) sending the a value "X2P1.04" for the service property under the extendedData JSON Object. While rendering/exporting the data to the PDF, the ADR is doing a schema validation and in that step the Transaction details are not rendering on the PDF because the ADR is expecting a value "X2P1.01" while we're sending "X2P1.04". With that validation from the ADR, the Transaction detail on the PDF is throwing a warning message which is a bad customer experience. Is ACCC considering to include the latest values to the "service" property ENUM? I could not able to find the latest DP / GitHub Consultation regarding to raise a change request, if you could please direct me towards that, that'd be very much appreciated.	Currently the only version of the Osko service the data standards support is X2P1.01
1719	In Get Account Detail, a requirement of the BankingProductLendingRate schema is to map loans to either INVESTMENT or OWNER_OCCUPIED. However, we have property-related business loans with purposes such as renovating property & non-building structures inc.: 1. Strata Improvement Loans (SILs) to both Residential and Commercial Strata Plans 2. Loans for all structural, non-structural changes or improvements to existing: commercial property, non-residential buildings & non-building structures to any entity 3. Loans to trading entities for all structural, non-structural changes or improvements to existing residential property These scenarios do not appear to have been catered for in the loanPurpose mapping. Given these are business-related we will map them to INVESTMENT unless we are advised otherwise. Will this mapping be updated in the future to cater for these business scenarios?	If there are other loan purposes specific to your business, we encourage you to raise a change request on Standards Maintenance so you can accurately reflect your loan data.
1720	We previously offered a product that capitalised Interest Accrued onto the balance of the loan. After this Interest Capitalisation period the borrower had the ability to switch to either Principal & Interest or Interest Only. This product is no longer offered, can you please advise how we should be categorising these loans as they do not fit the current definitions for P&I or IO. Given this scenario is currently not catered for we will leave as null unless advised otherwise.	Please refer to these articles on grandfathered products: Grandfathered products Grandfathered products and PRDs Product Reference Data in Consumer Data payloads If you have additional loan repayment methods that you would like to be reflected we encourage you to raise a change request on Standards Maintenance.