Skip to content

ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 23rd of September 2021

CDR API Stream edited this page Sep 23, 2021 · 4 revisions

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: 1650705270@webex.com

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 contact@consumerdatastandards.gov.au 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 Agenda from the 22nd 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 17th of September 2021 View in browser here
Consultation Decision Proposal 190 - Candidate Generic Tariff End Point 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 Decision Proposal 197 - Candidate Account End Points Link to consultation
Consultation Decision Proposal 198 - Candidate Billing & Invoicing End Points Link to consultation
Consultation Normative Standards Review (2021) Link to consultation

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 Christine Atkins
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
1073 Our Core Banking System doesn't currently capture the "financialInstitution" for Direct Debits for any type of account (not just credit card accounts). As such, we cannot disclose this value in the BankingAuthorisedEntity.
Since, the "financialInstitution" is 'conditional', should we always leave it blank, since we don't have the data available?
The only condition which allows financialInstitution to be optional is if the direct debit is via a credit card scheme. For all other direct debits the FI is mandatory and leaving this blank would not be compliant.
Under the original consultation for direct debits it was determined that there were not many fields that were consistently obtainable for direct debits but that this was one of them as the FI is contained in the direct debit that the customer institution receives via BECS and this value is retained in the transaction history.
Note that the records to be responded to under these APIs are expected to be derived from transaction history rather than a database of authorisations held by the bank as there was broad industry consensus that the FI for the end customer would not usually have any of the details of the direct debit authorisation and would only be able to derive the authorisations from the debits received via industry mechanisms.
As to the value of the field, that is no longer a consideration unless you wish to raise a change request to remove the fields from the standards. The fields are now a binding component of the standards due to a decision of the Chair.

Useful Links

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

Clone this wiki locally