DSB Maintenance Iteration 22: Meeting Notes (2 April 2025) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Notes

  • This was the last meeting for MI 22. The purpose of this meeting was to confirm the candidates that will be proposed in MI 22.
  • The Decision Document with approved candidates will be drafted and sent to the Chair for approval.

Release Plan

  • Current version is 1.34.0 incorporating decision 338 for Banking and Decision 361 LCCD for Energy.
  • An 1.34.1 patch release is planned to align the NBL Candidate Standards with the current banking changes.
  • Changes resulting from this MI will be published in version 1.35.0 or later.

Discussion Notes on MI 22 Candidates

Note: To allow standards maintenance consultation to focus on the detail of unresolved issues, it is assumed that proposed solutions can be taken forward in a Decision Document for the Chair unless there are opposing views raised before the final call of the iteration. The DSB encourages participants to post their views on issues as early as possible.

Breaking changes

Security

#650 - Weaken JARM Encryption Requirements for ADRs

  • No concerns raised by participants.
  • Changes will be recommended to Chair as a breaking change with FDO of 6 months (November 10th 2025).

Non-breaking changes

MI22

#683 - Maintenance Iteration 22 Holistic Feedback

  • DSB noted that the specific issue of default value for BankingBalancePurse.currency will require further consideration. As a result, it will be dealt with via a separate CR.
  • ACTION DEECA will review and suggest alternative or improvements to the suggested descriptions (e.g. use of time band instead of _time window) DEECA clarified with DSB directly that the suggested descriptions are good with no concerns of misinterpretation.
  • No concerns raised by participants on other issues.
  • Changes will be recommended to Chair as Non breaking changes.

Register

#682- Spec alignment - OpenID Provider Configuration and issuer value

  • Change will be recommended to Chair as Non breaking change.

#671 - Remove deprecated Register scope detail

  • Change will be recommended to Chair as Non breaking change.

Energy

#677 - Energy transaction fields should be conditional

  • Change will be recommended to Chair as Non breaking change.

Banking

#656 - A status of POSTED should indicate the final update for a transaction

  • ANZ noted that whilst they support the change the proposed description of POSTED may need minor adjustment to ensure there is no ambiguity in sequencing of pending vs posted. They will comment with revised proposal.
  • DSB noted they will update the proposed change incorporating ANZs feedback once posted. Note: The proposal has been updated - https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/656#issuecomment-2771571308.
  • ACTION ANZ supportive of proposed solution and will comment on the issue. actioned.
  • OUTSTANDING ACTION Biza to review and comment on proposed change - No feedback provided.
  • Change will be recommended to Chair as Non breaking change.

#681 - Retirement date for Get Transaction Detail V1

  • Change will be recommended to Chair as Non breaking change.

No change

Energy #662 Extend Get Generic Plan Detail to include a new field: tariffCode

  • ACTION DSB will raise issue with TSY to assess if change can be pursued via other channels. This has been raised with TSY.
  • The CR will be left open where the DSB/TSY can update on any progress of if/how this issue can be raised via other channels. It will also allow members to raise alternative solution options to resolve the issue.

Banking

#678 - New Error Code for Product Data Requests where the Data Holder does not hold the required Product Reference Data

  • This CR will be closed with no change.

#642 - Update guidance for Banking account rate detail

  • DSB noted current guidance will be updated to resolve the issue.
  • This CR will be closed with no standards change.

Completed

CX

#674 - CX Guidelines - Updates stemming from 2024 Consent Review changes

  • The issue is resolved with a guidance update. Refer to this comment for details.
  • This CR will be closed with no standards change.

Carry over to next MI

CX

#684 - CX Guidelines - ADI or NBL to hold CDR data as a DH

  • CX team noted draft guidance has been prepared and shared for community feedback.
  • CR will be carried over to the next MI.

Register

#679 - Update SSA specification

  • ACCC noted it would be worth considering removal of non technical SSA as many DHs still refer to standards.
  • DSB suggested to carry over CR to next MI.
  • CR will be carried over to the next MI.

NFR

#660 - Revise the Availability Requirements NFRs

  • CR will be carried over to the next MI.

Energy

#680 - Jurisdiction Code of ISO

  • DSB noted that the TSY and ACCC are progressing the assessment of whether voluntary data sharing by consumers of ISO NMIs is allowed via CDR.
  • As a result, this CR will be carried over to the next MI. Any updates will be posted as a comment in the CR thread.

Banking

#687- Bank account balance calculation time is indeterminate

  • CR will be carried over to the next MI.

Potential new issue relating to issue #471 - Additional credit card fields

  • Recent comment by SISS Data Systems was discussed.
  • A recipient participant noted another DH plans on raising a CR in this space because they don't store balance data down to individual card level.
  • Participants agreed this issue should be closed and a separate issue would still need to be raised to discuss the issue noted in comment.
  • ACTION SISS Data Systems to create a more specific CR to be considered as a candidate in a future MI.
  • CR471 will be closed.

Potential new issue relating to banking issues included, but deferred in Decision 338

  • ACTION Frollo to summarise of key aspects from issues #283, #284, #567 and #569 in a new CR to be considered as a candidate in a future MI.
  • Issue will be carried over to next MI.

Other Business

Item 1:

  • A participant raised an issue where number of business customers who are unable to give CDR consent as they have extra security requirements on their existing DH logins (e.g. use of hardware tokens, 1up on passwords, etc).
  • Some banks have noted they can't do much to help resolve the issue and some have instead suggested ADRs request the customers to lower their security settings to enable CDR data sharing.
  • ACTION: Participant (SSIS Data Systems) to email DSB outlining the problem in more detail.

Item 2:

  • Another participant noted a similar issue where customers of smaller data holders do not have Id's preventing them from participating in CDR data sharing as they can't authenticate/authorise. They raised the following points:
    • Given this is a compliance issue, it should be on the non-conformance (rectification schedule) register.
    • If an ADR raises a compliance issue and the DH state they will raise standards CR as it does not align with their system, the DH should be on non-conformance register so ADRs can point their clients to something.
    • A related issue is entry in non-conformance register with no resolution dates
    • How long should it take for issues to be captured and to be resolved in the non-conformance register?
  • DSB noted that its a legal issue and not in the scope of an MI, but we do have observers from ACCC on the call.
  • ACCC noted there is no correct forum to raise such issues but requested the participant to send them an email ([email protected]) so they can follow up on this issue.
  • Participants noted it would be good to have ACCC compliance forum similar to MI.

Item 3:

  • A participant questioned the timeline between when MI call concludes and when the Decision Document comes out for chair approval.
  • DSB clarified the process and estimated timelines.