ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 16th of September 2021 - ConsumerDataStandardsAustralia/standards GitHub Wiki

ACCC & DSB | CDR Implementation Call 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

Agenda

  1. Introductions
  2. Actions
  3. CDR Stream updates
  4. Presentation
  5. Q&A
  6. Any other business

Introductions

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

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.

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.

Updates

Type Topic Update
Standards Version 1.11.0 Published Link to change log here
Standards Version 1.11.1 Drafted Standard-staging Version 1.11.1 Change log for Version 1.11.1
Maintenance 9th Maintenance Iteration Kicked-off Agenda from the 8th of September 2021 meet
Maintenance Decision Proposal 212 - Banking Maintenance Iteration 9 Link to consultation
Maintenance 9th Maintenance Iteration Meeting Details Now included on Decision Proposal here
DSB Newsletter To subscribe to DSB Newsletter Link here
TSY Newsletter To subscribe to TSY Newsletter Link here
TSY Newsletter 13th of September 2021 View in browser here
DSB Newsletter 10th of September 2021 View in browser here
Consultation Decision Proposal 190 - Candidate Generic Tariff End Point Link to consultation
Consultation Decision Proposal 194 - Candidate NMI Standing Data End Points Link to consultation
Consultation Decision Proposal 195 - Candidate Usage End Points Link to consultation
Consultation Decision Proposal 196 - Candidate DER End Points Link to consultation
Consultation Normative Standards Review (2021) Link to consultation
Community Regional Australia Bank would like to share the results of their recent survey. Link to the CDR Support Portal Community Hub LinkedIn Post Direct PDF download from Regional Australia Bank

CDR Stream Updates

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

Organisation Stream Member
ACCC CDR Register (Technical) Ivan Hosgood
ACCC CTS Andrea Gibney
ACCC Onboarding Jonathon Ingle
DSB CX Standards Michael Palmyre
DSB Technical Standards - Banking Mark Verstege
DSB Technical Standards - Energy & Engineering James Bligh

Presentation

None this week.

Q&A

Questions will be received by the community via WebEx chat before the questions are opened to the floor. Participants can pre-submit questions to the DSB mailing box.

We are trialling Sli.do for Question and Answer. Join our Q&A live here: https://www.sli.do/ Code: #169517

Answer provided

Ticket # Question Answer
1056 Where the country is not Australia, the State field is expected to be free text but is also mentioned as mandatory in the Common Address Schema. There are many countries which do not have states. Can the DH send an empty string in State field for countries other than Australia where the State is not present in the customer data? Yes, if no data is available then an empty string is appropriate.
1059 I asked previously why the FI details of the remitter sending in the direct debit was required, and I'm on the same topic here, just wondering what if the remitter changes banks? As I mentioned in my last communication, we don't store the name of the bank generating the debit, we store everything else about the debit. If the remitter changes banks, we'd have to be checking this and updating it accordingly. Is that your expectation? The expectation is that the data presented in the Direct Debit APIs, like all of the APIs, should be accurate at the time of the invocation. If a merchant has changed FI and migrated their direct debits then this should be communicated via the Direct Debit APIs as soon as the data holder can reasonably know (ie. you won't know until the next debit actually occurs in most instances).
1061 Which fees should be disclosed as part of the Account Details API? Certain loan products have some fees identified during the origination stage of a loan - eg the Establishment Fee - but when the loan is actually created in the product system, this fee is aggregated into the overall loan amount, not stored in our core banking system and no longer separately identifiable by type or value from the loan amount. What is the expectation in these circumstances with regard to the fee disclosure as part of the Account Details API? All fees should be included if they are going to be incurred in the future. Past fees that will no longer recur are not in this category. For instance, a break fee should be included but an establishment fee for an account that is already established does not need to be included.

Useful Links

View a number of informative and useful links in the Consumer Data Standards Implementation Guide on Information Links.