What are the CDR Data Holder reporting requirements? - Energy

Fiskil has been involved in the CDR from the very beginning, helping energy clients get their CDR strategy right and meet their regulatory deadlines. See our list of reporting requirements we have compiled that will help Energy Data holders stay on top of their reporting requirements.

Explore in more detail what ‘open energy’ is and how CDR is playing a pivotal role in shaping the future of the energy industry in our blog “The Power of Open Energy”.

Biannual CDR Reporting

Data holders in the energy sector must submit CDR reports twice a year to the ACCC and OAIC. The reporting periods are as follows:

• January 1 to June 30: Report due by July 30
• July 1 to December 31: Report due by January 30

Reporting Obligations Commencement

Reporting obligations begin when data holders start sharing consumer data under CDR Rules. Even if sharing starts before compliance dates, reporting kicks in from the earlier date, including pilot phases.

CDR Complaint Data Summary

CDR complaint data for a data holder includes:

• Total CDR consumer complaints received
• Categorisation of CDR complaints (per data holder's systems)
• Total resolved CDR consumer complaints (either reported in the current or previous period)
• Average days for internal dispute resolution
• CDR complaints referred to external resolution
• CDR complaints resolved externally
• CDR product data complaints received, reported individually

CDR Data Requests Received

The report mandates separate counts for:

• Product data requests
• Direct consumer data requests
• Accredited persons' consumer data requests on behalf of consumers, within the relevant reporting period.

'Received' means requests reached the data holder's system with potential responses. The report should cover 'successful' and 'unsuccessful' CDR data requests, including rejected ones due to exceeded traffic thresholds. If requests don't reach servers, reporting isn't needed, e.g., requests blocked by a global firewall without CDR identification.

Refusals to Disclose CDR Data

Data holders typically share required data upon valid requests, though refusals are possible in certain cases. Refusals must be communicated to the requester, using data standards error codes. Permissible refusal cases are identified via HTTP error codes. For example requests received may cause physical, psychological, or financial harm or abuse, shown by HTTP error code ‘403 Forbidden’.

Reporting isn't needed for attacks or non-CDR-related requests, or those due to maintenance, outage, or instability. Data holders don't have to record/report refusals for authorisation requests based on safety, abuse, or other reasons outlined in CDR Rule 4.7.

Updating the Register

Data holders must promptly inform the Accreditation Registrar if provided information needs amendment or is outdated.

Reporting to the CDR Register

The ACCC receives information about performance and availability of data from data holders in the CDR report, as outlined in the Consumer Data Standards. On a daily basis, the dashboard shows updated banking and energy data provided by active data holders. View the performance dashboard.

Reporting Form Submission

Data holders use an online web form on the CDR Participant Portal to submit reports. The approved reporting template covers consumer data for energy sector data holders.

How can Fiskil assist your business in staying up-to-date with regulatory changes?

Fiskil offers two key solutions: a secure SaaS Data Holder and robust Data APIs. Trusted by top Energy Retailers and Banks, our Data Holder solution ensures safe and compliant data sharing. Our Data APIs extend this capability, covering over 97% of Australia's Banking and Energy sectors, enabling secure customer data access. Our commitment to innovation empowers enterprises and startups alike with tools for strategic growth and effective data management. Get in touch.