DSB Maintenance Iteration 24: Meeting Notes (23 July 2025) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Notes

  • The second meeting for MI 24 aimed to finalise candidates for consultation in this iteration.

Release Plan

Requirements Analysis

CX

  • TBA CX Guidelines - ACCC Onboarding - White Labelling Scenarios
    • In consultation with partner agencies on requirements.
    • No further information to share at this time.

Banking

Register

  • 706 Client authentication for Get Data Holder Brands
    • OUTSTANDING ACTION: Participant thoughts on whether the API could be made public or if there are particular concerns or sensitivities around that information are welcomed.
    • Potential options include:
      • adding detail to Get Data Holder Brand Summary;
      • adding a new end point; and
      • removing authentication from Get Data Holder Brands.

MI24 Proposed Candidates

Holistic

CX

All of the following CX issues are in progress, with no specific update to provide. All issues will be considered as candidates for MI24 and can be carried over into MI25 if there is insufficient feedback from the community or capacity to complete them.

Register

  • 665 - Review Register error code documentation
    • ACTION UPDATE: ACCC to provide detail on which codes will change to confirm impact. This may support a non-breaking change.
      • ACCC and DSB are working through permutations of errors and will post the outcomes for review shortly.
    • ACTION UPDATE: ACCC to advise anticipated release of endpoints with updated error codes, and the subsequent deprecation of the current versions.
      • New errors for Register APIs will be incorporated into the changes required for NBL, a release date has yet to be set.

Banking

  • 173 - Behaviour where posted transactions only have an associated date
    • No progress to report.
    • DSB will contact Data Holders impacted by this change in the coming fortnight.
    • More information will be provided in the next call.
  • 696 - BankingAccountV2: productName
    • The outcome arising from discussion in the MI call has been posted in this comment.
  • 707 - Change to BankingProductLendingRateV3 to support a RANGE
    • Current schema requires loans with a min and max rate to be duplicated increasing PRD maintenance effort.
    • One participant suggested:
      • applicability conditions could be used to express criteria required to achieve a lower rate through a customer negotiation.
      • indicated a preference to maintain a less precise structure of the data to provide data holders with flexibility.
      • support for the issue to be considered as a candidate if there is no way to convey factors that enable rate discounting through customer negotiation.
    • Benefits to reduce effort to maintain lending data and provide better quality of data.
    • The group reiterated this change isn't intended to create a relationship between product reference data and consumer data.
    • This topic affects lending and deposit rates.
    • Is tailored flag, based on customer, but that would mean we don't supply lending rates at all.
    • The general approach for PRD is to record the worst case, i.e. highest lending rate or lowest deposit rate.
    • Supported as a candidate for this MI.

Energy

NOTE: As the Iteration progresses, 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 Consultation Draft for the Chairs approval 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.

Any other business

None

⚠️ **GitHub.com Fallback** ⚠️