Regulatory Reporting

How to prepare six-monthly CDR data holder reporting using Fiskil Console Analytics.

CDR Data Holders are required to submit a compliance report to the ACCC every six months via the CDR Portal at portal.cdr.gov.au. This guide explains how to use the Fiskil Console to find the numbers you need, and provides context on what each question in the reporting form is asking.

This guide is general information only and is not legal advice. Always confirm your reporting position against the latest CDR Rules and ACCC guidance.

---

Using the Analytics Tab

Most of the data you need for regulatory reporting is available directly in the Fiskil Console under the Analytics tab. Follow these steps each reporting period.

Step 1 — Open Analytics

1. Open the Fiskil Console and select your Data Provider workspace from the top-left selector.
2. Click Analytics in the top navigation bar.
3. You will see tiles for:
   • Consumer Data Requests
   • Product Data Requests
   • Refusals (Total, 403, 404, 422)

Step 2 — Select the correct environment

Use the environment selector in the top right to choose Production.

Staging is used for testing and should not be used for regulatory submissions.

Step 3 — Set your reporting period

In the Period section on the left, set the date range that matches your reporting period:

Reporting Period	Date Range to Enter
1 January – 30 June	01/01/YYYY → 01/07/YYYY
1 July – 31 December	01/07/YYYY → 01/01/YYYY

Note: The date range picker excludes the end date. To capture data up to and including 31 December, enter 1 January of the following year as the end date. The same logic applies for the June period.

The tiles will update automatically once you set the date range.

---

What to Report — Question by Question

The tables below map each question in the reporting form to where you can find the answer in the Fiskil Console, and explain what the question is asking.

Complaints (Questions 1–7)

Complaint data is managed through your own internal complaints handling system. Fiskil does not capture complaint intake or resolution — you will need to compile these figures independently.

Question	What it’s asking	Where to find it
Q1 — Product data complaints	Total CDR complaints received relating to product data (for example, errors or gaps in your product data feed).	Your internal complaints system. Energy data holders: enter 0 — product data obligations do not apply.
Q2 — Consumer complaints	Total CDR complaints relating to consumers or consumer data (data sharing issues, consent problems, data quality).	Your internal complaints system.
Q3 — Complaints by type	A breakdown by category used in your internal complaints process (for example, “Data accuracy”, “Consent”, “Access issues”). Add one row per type.	Your internal complaints system.
Q4 — Complaints resolved	Total CDR consumer complaints resolved during the reporting period.	Your internal complaints system.
Q4.1 (optional) — Resolved, received this period	Of Q4, how many were received and resolved within this same period.	Your internal complaints system.
Q4.2 (optional) — Resolved, received prior period	Of Q4, how many were received in a previous period but resolved this period.	Your internal complaints system.
Q5 — Average days to resolve (IDR)	Average calendar days from complaint received to resolved via internal dispute resolution.	Your internal complaints system.
Q6 — Referred to EDR	Complaints referred to an external dispute resolution scheme (for example, AFCA for banking or the relevant energy ombudsman).	Your internal complaints system.
Q7 — Resolved by EDR	Complaints resolved by the external dispute resolution scheme.	Your internal complaints system.

---

Data Requests (Questions 8–10)

Most data request figures come directly from the Analytics tab in the Fiskil Console.

For Q9 specifically, Fiskil primarily handles requests made by accredited data recipients or intermediaries (for example, apps or services your customers authorise). Fiskil does not generally handle direct consumer-to-data-holder request channels, so this metric is usually sourced from your own systems and often 0 unless your sector supports this flow and it has occurred.

Question	What it’s asking	Where to find it
Q8 — Product data requests	Total requests received by your product data APIs during the period.	Product Data Requests tile in Analytics. Energy data holders: enter 0 — product data obligations do not apply.
Q9 — Consumer data requests from eligible CDR consumers	Requests made directly by consumers to your APIs (rule 1.13(1)(a)(i)). Fiskil does not generally participate in this direct-consumer flow, so this metric should come from your own direct request channels. This obligation has not yet commenced for most data holders — if that applies to you, enter 0.	Your internal systems for direct consumer requests (not Fiskil Analytics).
Q10 — Consumer data requests from accredited persons	Requests made by accredited data recipients or intermediaries on behalf of consumers. This is the standard flow Fiskil facilitates and is usually your primary non-zero figure.	Consumer Data Requests tile in Analytics.

---

Product Data Refusals (Question 11)

Energy data holders: this entire section does not apply. Enter 0 / No for all fields.

Question	What it’s asking	Where to find it in Fiskil
Q11 — Did you refuse any product data requests?	Yes/No.	Review the refusal tiles in Analytics for the reporting period.
Q11.1 — Total product data refusals	Count of all product data request refusals.	Total Refusals tile in Analytics.
Q11.2 — 403 errors	Refusals due to a detected threat to the data holder, CDR Register, or consumer.	Refusals (Error code 403) tile in Analytics.
Q11.3 — 429 errors	Refusals due to traffic thresholds exceeded or denial-of-service detection.	Contact Fiskil Support if you need a 429 breakdown — this is not currently shown as a separate tile.
Q11.4 — Other refusals	Any other CDR Rule or Data Standard relied upon to refuse a request, with the rule cited. Under Fiskil’s current implementation, this is not supported as a separate refusal pathway and is expected to be 0.	Enter 0 from Fiskil-supported flows. If you have non-Fiskil channels, verify through your own internal systems.

---

Consumer Data Refusals — Direct from Consumers (Question 12)

Fiskil primarily handles requests made by accredited data recipients or intermediaries (for example, apps or services your customers have authorised). Fiskil does not generally handle direct API requests from individual consumers or business consumers to you as a data holder.

That means Question 12 metrics are usually sourced from your own direct consumer request channels/processes, not from Fiskil Analytics.

For most data holders this will be uncommon and often 0, but if your sector supports direct consumer requests and you have received them, you should report them.

Question	What it’s asking	Where to find it
Q12 — Did you refuse consumer data requests from eligible CDR consumers?	Yes/No. If your sector has not commenced direct consumer API access, answer No.	This should usually be No / 0 unless you received and refused direct consumer requests. Not provided by Fiskil Analytics.
Q12.1 — Total refusals	Count of all refusals to direct consumer requests.	This should usually be 0 unless you received and refused direct consumer requests. Not provided by Fiskil Analytics.
Q12.2 — 403 errors	Refusals due to a detected threat.	This should usually be 0 unless you received and refused direct consumer requests with this refusal type. Not provided by Fiskil Analytics.
Q12.3 — 404 errors	Refusals returned for a blocked or suspended account.	This should usually be 0 unless you received and refused direct consumer requests with this refusal type. Not provided by Fiskil Analytics.
Q12.4 — 422 errors	Refusals returned for a blocked or suspended account (alternative code used in some standards contexts).	This should usually be 0 unless you received and refused direct consumer requests with this refusal type. Not provided by Fiskil Analytics.
Q12.5 — 429 errors	Refusals due to traffic thresholds or denial-of-service detection.	This should usually be 0 unless you received and refused direct consumer requests with this refusal type. Not provided by Fiskil Analytics.
Q12.6 — Other refusals	Any other CDR Rule or Data Standard relied upon, with the rule cited. Under Fiskil’s current implementation, this is not supported as a separate refusal pathway and is expected to be 0.	This should usually be 0. Not provided by Fiskil Analytics.

---

Consumer Data Refusals — From Accredited Persons (Question 13)

This section mirrors Question 12 but covers requests made by accredited data recipients or intermediaries on behalf of consumers — the standard flow Fiskil facilitates. This is where most data holders will have non-zero figures.

Question	What it’s asking	Where to find it in Fiskil
Q13 — Did you refuse consumer data requests from accredited persons?	Yes/No.	Review refusal tiles in Analytics.
Q13.1 — Total refusals	Count of all refusals to accredited-person requests.	Total Refusals to share consumer data tile in Analytics.
Q13.2 — 403 errors	Refusals due to a detected threat.	Refusals (Error code 403) tile in Analytics.
Q13.3 — 404 errors	Refusals returned for a blocked or suspended account.	Refusals (Error code 404) tile in Analytics.
Q13.4 — 422 errors	Refusals returned for a blocked or suspended account.	Refusals (Error code 422) tile in Analytics.
Q13.5 — 429 errors	Refusals due to traffic thresholds or denial-of-service detection.	Contact Fiskil Support if you need a 429 breakdown.
Q13.6 — Other refusals	Any other CDR Rule or Data Standard relied upon, with the rule cited. Under Fiskil’s current implementation, this is not supported as a separate refusal pathway and is expected to be 0.	Enter 0 from Fiskil-supported flows. If you have non-Fiskil channels, verify through your own internal systems.

---

Sector Applicability Summary

Question Group	Banking & Non-Bank Lenders	Energy Data Holders
Q1 — Product data complaints	Required	Not applicable — enter 0
Q2–7 — Consumer complaints	Required	Required
Q8 — Product data requests	Required	Not applicable — enter 0
Q9–10 — Consumer data requests	Required	Required
Q11 — Product data refusals	Required	Not applicable — enter 0 / No
Q12–13 — Consumer data refusals	Required	Required

---

Common Questions

What if a value is zero? Enter 0. Do not leave numeric fields blank.

What counts as a CDR complaint? Any complaint that relates to your CDR obligations — product data availability, consumer data sharing, consent and authorisation, or CDR-related service issues. General complaints unrelated to CDR do not need to be counted.

What is the difference between Q12 and Q13? Q12 covers requests made directly by consumers to your APIs. Q13 covers requests made by accredited data recipients or intermediaries on behalf of consumers — this is the standard flow Fiskil facilitates and where most data holders will see activity.

I need more detail than the Analytics tiles provide. The Logs tab in the Fiskil Console provides a full request-level log that you can use to verify or investigate the totals shown in Analytics. If you need data that is not available in the Console, contact Fiskil Support.

---

Further Resources

• CDR Portal
• CDR Rules — Rule 9.4 (Reporting obligations)
• Consumer Data Standards
• Fiskil Support