Guidance on lastUpdated and lastUpdateTime fields

The following guidance supports the Data Quality Guidance prepared under a joint effort among the Consumer Data Right agencies. 

Sector applicability: This guidance applies to all Sectors where the fields listed below are included in a sector specific payload.

lastUpdated

The purpose of the lastUpdated field is to enable product reference data users to optimise their data request processes and only make data requests where new data has become available. A data holder should change this date whenever it updates the data contained in the disclosure, to notify users to make a new request. Notably, this includes updates to any and all fields, and changes to correct the data within the payload, rather than just changes to the underlying product data.

For example, if a data holder,

• changes the interest rate for a product, it should reflect this in the Get Product Details response for the product, and update the corresponding lastUpdated value
• is notified that it has a missing or outdated value in a field, and corrects the data to address this notification, it should update the lastUpdated value,
• changes the URIs associated with documents provided in the PRD, it should update the lastUpdated value, and
• changes terms or conditions of a product that are not included in the product reference data (such as detailed terms and conditions drafting contained in a linked document), it should not update the lastUpdated value.

See:

• CDS BankingProductV4
• CDS EnergyPlan
• CDS TelcoProduct

CommonOrganisation - lastUpdateTime field

The CommonOrganisation lastUpdateTime field refers to the time the Data Holder last updated any data for the customer record. This indicates the customer has actively maintained their data up to this date.

The lastUpdateTime field is not limited to updates of only the information returned by APIs.

This field is optional because it may not be possible to track when customer data was last updated. In accordance with the definition of optional fields, if the Data Holder has the data, they must supply it.  

See:

• CDS CommonOrganisation
• CDS Guide, Data formats - schemas, Mandatory, Optional and Conditional fields