Nils Berge

This change has been [staged](https://github.com/ConsumerDataStandardsAustralia/standards-staging/pull/421/files) for review.

Incorporated into Standards v1.32.0.

Hi @anzbankau Feedback to date suggests that a change to the Standards may not be a preferred solution to the stated issue. Do you consider it should remain open for...

For reference, timezone-related concerns have also been raised in #539, and explored in relation to energy endpoint date filtering in the last block of [this comment](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/511#issuecomment-1152032924).

As this issue could be relevant to changes being considered in MI19 (#636), is it still a valid concern?

The following values could be specified in the [SSA Definition](https://consumerdatastandardsaustralia.github.io/standards/index.html#ssa-definition) table as minimum field lengths that Data Holders could be required to support for DCR, as they are the limits...

Related issue for reference - [#229 - Service field in the Get Transaction Details API](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/229#issuecomment-1689275222)

While discussions relating to NFRs are underway, the detail below simply aims to summarise the options described in previous comments, with some additional questions/considerations. Options discussed: 1. **Current state**: Make...

To summarise the above comments, in addition to potential [data quality issues](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/636#issuecomment-2126944110) that may need to be addressed, it appears discussion is leaning towards: - _payer_, _payee_, _extendedDescription_ and _endToEndId_...

Discussion on this issue in the MI call today included: - An initial incremental change could be to include the _payer_, _payee_, _extendedDescription_ and _endToEndId_ fields in the existing Get...