---
title: "Rejected by ASIC, Twice. Then Not Submitted at All."
url: "https://getcurium.com/news/asic-idr-data-reporting/"
published: "16 November 2026"
author: "Louise Andrews, Head of Partnership and Growth"
publisher: "Curium"
description: "Firms send ASIC their IDR data twice a year. See who reports, when it is due, why files fail deep validation and how to avoid it."
---

# Rejected by ASIC, Twice. Then Not Submitted at All.

Firms send ASIC their IDR data twice a year. See who reports, when it is due, why files fail deep validation and how to avoid it.

Twice a year, firms have to send ASIC their [internal dispute resolution (IDR) data](https://getcurium.com/news/asic-idr-data-hy1-2025-the-real-risk-isn-t-complaints-it-s-not-seeing-them/). For some it takes up to three days to put the report together. The file then fails ASIC's deep validation, often more than once, and each failure means finding the error and starting again. We have seen firms leave it close to the deadline, get rejected and end up not submitting at all.

Most of that trouble starts earlier. The report is only as good as the data captured on each complaint when it came in, and that is usually typed in by hand. So here is one complaint, start to finish: what Curium does, and where a person still decides.

## The ASIC IDR report in short

- **Who reports:** all AFS licensees that provide financial services to retail clients, and all Australian credit licensees. A firm with no complaints in the period still lodges a nil submission.
- **When:** twice a year, for 1 January to 30 June and 1 July to 31 December. Each report is due in a two-month window after the period ends: by the end of February and by 31 August.
- **How:** through the ASIC Regulatory Portal, as a machine-readable IDR data file that follows ASIC's IDR data reporting handbook.
- **Next due:** the report for 1 July to 31 December 2026 is due between 1 January and 28 February 2027.

Source: [ASIC, Internal dispute resolution data reporting](https://www.asic.gov.au/regulatory-resources/financial-services/dispute-resolution/internal-dispute-resolution-data-reporting).

## 1. It comes in

**Curium:** reads the description and decides whether it is a complaint, an incident or both. It fills in the fields ASIC requires from the text, so nobody retypes them, and it flags signs that the customer may be vulnerable.

**A person:** checks what Curium filled in and confirms it.

## 2. It is checked against the rules

**Curium:** runs the complaint against the firm's own obligations and flags a possible breach, with its reasoning.

**A person:** confirms the flag or dismisses it. Curium never decides that a breach happened.

## 3. The clock starts

**Curium:** sets the deadline that applies, lays out the steps that must happen, and sends reminders before the date. A traffic-light view shows the manager where every complaint stands, and a complaint can be handed to a colleague if the handler is away.

**A person:** decides how to handle the complaint and does the work.

## 4. Everything sits in one place

**Curium:** keeps the emails, calls and texts on the complaint in order. It can send the acknowledgement from a template, and it stamps every action with the time, so the record is ready when someone asks for it.

**A person:** writes the replies that need judgement.

## 5. Patterns and the response

**Curium:** shows similar complaints automatically, so [a pattern is seen early](https://getcurium.com/news/super-complaints-management-asic-report-844/). The Ask AI button reads the complaint, its documents and its messages, suggests what went wrong and can draft the internal dispute resolution (IDR) response from the documents.

**A person:** reads the draft, changes it, decides the outcome and signs it.

## 6. The report to ASIC

**Curium:** captures the fields ASIC asks for as each complaint moves, in the structure ASIC expects, so the six-monthly IDR report is prepared in one click and is built to pass ASIC's deep validation.

**A person:** reviews it and submits it, with time to spare.

## What this is worth to you

- **Days back.** The report is prepared in one click, not assembled over up to three days.
- **No failed submissions.** The data is captured in the structure ASIC expects as it is entered, so the errors that cause rejections are stopped at the start.
- **No missed deadline.** A report that is ready early is not submitted at the last minute, and the clock and reminders keep every complaint on track.
- **More done with the same team.** Less typing, sorting and day counting leaves time for the complaints themselves.
- **A record that is ready.** Every action is stamped, so the answer is there when ASIC or an auditor asks.

To count it for your own team, add up the hours spent typing complaints in, the days spent on the last IDR report, and the number of times it was rejected.

## What stays with a person

Reading the complaint, deciding whether a breach happened, choosing the outcome, signing the response and submitting the report all stay with your team. Curium takes the typing, the sorting, the counting of days and the report preparation, which is the work that fills a complaints manager's week and leaves little time for the complaint itself.

## Questions about the ASIC IDR report

### Who has to report IDR data to ASIC?

All AFS licensees that provide financial services to retail clients and all Australian credit licensees. This includes insurers, underwriting agencies (MGAs) and brokers that hold an AFSL.

### When is the next ASIC IDR report due?

The report for 1 July to 31 December 2026 is due between 1 January and 28 February 2027. The report for 1 January to 30 June is due between 1 July and 31 August.

### Why does an IDR file fail ASIC's deep validation?

ASIC checks each file against the data dictionary and validation rules in its IDR data reporting handbook. When complaint data is typed in by hand, a field or heading in the wrong format can fail the check, and the firm has to find the error and submit again. ASIC publishes a submission checklist and examples of lines that pass and fail.

### What if a firm had no complaints in the period?

It still lodges a nil submission through the ASIC Regulatory Portal.

### How does Curium help with ASIC IDR reporting?

Curium captures the fields ASIC asks for as each complaint moves, in the structure ASIC expects. The six-monthly IDR report is prepared in one click and is built to pass ASIC's deep validation. A person reviews it and submits it.

**See it on your own complaints**

Curium is an insurance-native compliance and risk platform for insurers, underwriting agencies (MGAs) and brokers.

[See it in action](https://getcurium.com)

**Author:**

Louise Andrews, Head of Partnership and Growth, Curium. [LinkedIn Profile](https://www.linkedin.com/in/louiseandrews38/).
