Understanding Biannual ACCC CDR Reporting for Data Holders
Learn what each question in the ACCCβs biannual CDR report means, why itβs required, and which information is typically provided by Biza versus your organisation.
Why the ACCC/OAIC collects this informationβ
The ACCC/OAIC requires biannual reporting under Rule 9.4 of the CDR Rules to monitor how the Consumer Data Right (CDR) is operating in practice. At a high level, this helps the ACCC/OAIC to:
- Assess whether consumers can reliably access and share their data
- Monitor data quality, availability, and security
- Identify systemic issues such as increased error rates or access refusals
- Understand complaint volumes and resolution performance
- Track the uptake and usage of CDR
The biannual report provides regulatory oversight of ecosystem health and compliance trends.
How to read this guideβ
This guide is designed to explain each field in the ACCC/OAIC biannual CDR reporting form for Data Holders, including context for Data Holders using our HaaS product.
Whilst Biza fulfils most of the operational and technical obligations on your behalf, the legal obligation to submit the biannual report remains with you as the Data Holder.
Each of the explanations includes:
- What the ACCC is asking
- Who typically provides the data (Biza vs you).
It is designed to be used as a reference when fulfilling your reporting obligations.
CDR Complaint Dataβ
As the data holder, it is your responsibility to provide answers to the following series of questions.
1. Total number of CDR complaints relating to product dataβ
What this means
The total number of complaints received during the reporting period that relate specifically to product reference data (PRD) (e.g., incorrect product fees, features, eligibility or availability to the CDR ecosystem).
Example response:
- 0 (where no PRD-related complaints were received)
- 3 (if three complaints referenced incorrect product attributes)
2. Total number of CDR complaints relating to consumers or consumer dataβ
What this means
The total number of complaints received about consumer data, such as account data, transaction data, consent handling, or data sharing outcomes.
Example response:
- 0 (where no CDR consumer complaints were received)
- 5 (if five complaints relating to consent or data accuracy)
3. Number of CDR consumer complaints by complaint typeβ
What this means
A breakdown of the complaints from Question 2 (if any), categorised according to your internal complaints handling framework. Each complaint type should be listed on a separate line.
Example response:
- Data accuracy = 2
- Consent management = 1
- Service availability = 0
4. Total number of CDR consumer complaints resolvedβ
What this means
The total number of consumer complaints that were resolved during the reporting period.
4.1 Resolved complaints reported in this period (optional)β
The number of complaints that were both received and resolved during the current reporting period.
4.2 Resolved complaints reported in previous periods (optional)β
The number of complaints that were received during earlier reporting periods but were resolved in the current reporting period.
5. Average number of days to resolve CDR consumer complaints through internal dispute resolutionβ
What this means
The average number of calendar days taken to resolve consumer complaints through internal dispute resolution.
6. Number of complaints referred to external dispute resolution (EDR)β
What this means
The number of CDR-related complaints escalated to a recognised EDR scheme (e.g., Australian Financial Complaints Authority/AFCA, Energy and Water Ombudsman Victoria/EWOV, etc.).
Number of complaints resolved by external dispute resolution (EDR)β
What this means
The number of CDR complaints resolved through EDR during the reporting period.
CDR Data Requestsβ
The answers to the following series of questions will be provided to you by Biza 1-2 weeks before the ACCC/OAIC deadline.
8. Number of product data requestsβ
What this means
The total number of CDR product data requests received via CDR APIs during the current reporting period.
9. Number of consumer data requests received from eligible consumersβ
What this means
The number of requests made directly by consumers (not via an accredited data recipient) for their CDR consumer data.
10. Number of consumer data requests received from accredited persons on behalf of CDR consumersβ
What this means
The number of consumer data requests made by accredited data recipients (ADRs) on behalf of eligible consumers.
Refusals in response to product data requestsβ
The answers to the following series of questions will be provided to you by Biza 1-2 weeks before the ACCC/OAIC deadline.
11. Refusals to disclose product data requests?β
A yes/no indicator
11.1 Total number of product data refusals (if any)β
The number of times product data was refused in response to a valid request.
11.2 Refusals due to 403 - security threat (if any)β
The number of times a 403 error code was returned in response to a potential threat to:
- the data holder,
- the CDR Register, or
- the consumer.
11.3 Refusals due to 429 - traffic thresholds/Denial-of-Service (DoS) protection (if any)β
The number of times a 429 error code was returned in response to traffic thresholds being exceeded, or a potential denial of service attack.
11.4 Refusals relying on other rules or standards (if any)β
The number of refusals not covered by the above categories but where other rules or data standards were relied upon to refuse a product data request. The relevant rules or data standards must be stated if the value is greater than 0.
Refusals in response to consumer data requests made by eligible CDR consumersβ
The answers to the following series of questions will be provided to you by Biza 1-2 weeks before the ACCC/OAIC deadline.
12. Refusals to disclose consumer data to a consumer directly?β
Important context: This section only applies to requests made directly by consumers under Rule 1.13(1)(a)(i). Some obligations may not be in force for all sectors.
Did the data holder refuse to disclose consumer data in response to a consumer data request made by an eligible consumer? A yes or no indicator.
12.1 Total number of consumer data refusals (if any)β
The number of times the data holder refused to disclose consumer data in response to a request by an eligible CDR consumer.
12.2 Refusals due to 403 - security threat (if any)β
The number of times a 403 error code was returned in response to a potential threat to:
- the data holder
- the CDR register, or
- the consumer.
12.3 Refusals due to 404 - blocked or suspended account (if any)β
The number of times a 404 error code was returned in response to a request regarding a blocked or suspended account. A 404 Not Found error is used when the resource does not exist or is unknown.
12.4 Refusals due to 422 - blocked or suspended accountβ
The number of times a 422 error code was returned in response to a request regarding a blocked or suspended account. A 422 Unprocessable Entity is used if the account does exist, but the request canβt be processed (e.g., the account is suspended).
12.5 Refusals due to 429 - traffic thresholds/Denial-of-Service (DoS) protectionβ
The number of times a 429 error code was returned in response to traffic thresholds being exceeded, or a potential denial of service attack.
12.6 Refusals relying on other rules or standards (if any)β
The number of refusals not covered by the above categories, but where other rules or data standards were relied upon to refuse a product data request. The relevant rules or data standards must be stated if the value is greater than 0.
Refusals in response to consumer data requests made by accredited persons on behalf of eligible CDR consumersβ
The answers to the following series of questions will be provided to you by Biza 1-2 weeks before the ACCC/OAIC deadline.
13. Refusals to disclose consumer data requests made by an ADRβ
Did the data holder refuse to disclose consumer data in response to a request made by an accredited person on behalf of an eligible consumer? A yes or no indicator.
13.1 Total number of refusals (if any)β
The number of times a data holder refused to disclose consumer data in response to a request made by an accredited person on behalf of an eligible consumer.
13.2 Refusals due to 403 - security threat (if any)β
The number of times a 403 error code was returned in response to a potential threat to:
- the data holder
- the CDR register, or
- the consumer.
13.3 Refusals due to 404 - blocked or suspended account (if any)β
The number of times a 404 error code was returned in response to a request regarding a blocked or suspended account. A 404 Not Found error is used when the resource does not exist or is unknown.
13.4 Refusals due to 422 - blocked or suspended accountβ
The number of times a 422 error code was returned in response to a request regarding a blocked or suspended account. A 422 Unprocessable Entity is used if the account does exist, but the request canβt be processed (e.g., the account is suspended).
13.5 Refusals due to 429 - traffic thresholds/Denial-of-Service (DoS) protectionβ
The number of times a 429 error code was returned in response to traffic thresholds being exceeded, or a potential denial of service attack.
13.6 Refusals relying on other rules or standards (if any)β
The number of refusals not covered by the above categories but where other rules or data standards were relied upon to refuse a product data request. The relevant rules or data standards must be stated if the value is greater than 0.
Key takeaways for HaaS customersβ
- Biza provides system-generated metrics for request, refusal, and error-code-based fields.
- You are responsible for providing complaints and classification data and this will usually require confirmation from your internal complaints team.
The final responsibility for accuracy and submission of the biannual report remains with you as the data holder.