RG 271
Internal Dispute Resolution.
ASIC Regulatory Guide 271 sets minimum standards for internal dispute resolution by financial firms. Replaces RG 165 with a broader definition of 'complaint,' shorter response timeframes, and mandatory IDR data reporting to ASIC.
ASIC publishes IDR data publicly. Your firm's complaint volumes, resolution times, and outcomes become a discoverable signal for regulators, investors, and competitors. A pattern of late or unresolved complaints is one of ASIC's strongest leading indicators of broader compliance issues, and it triggers targeted reviews.
What RG 271 requires.
How BackPro handles each obligation.
Definition of complaint
Treat as a complaint any expression of dissatisfaction made to or about the firm, about its products, services, staff or complaint handling, where a response or resolution is expected or legally required. That includes complaints made on social media channels the firm owns or controls.
Acknowledgement of complaint
Acknowledge receipt of each complaint promptly. ASIC expects acknowledgement within 24 hours (or one business day) of receiving it, or as soon as practicable.
Maximum response timeframes
Give an IDR response no later than 30 calendar days after receiving a standard complaint. The maximum is 45 days for superannuation and traditional trustee complaints and 21 days for credit default notice and hardship complaints, and complaints closed within five business days follow separate rules.
Final response standard
The IDR response is written and must tell the complainant the final outcome, their right to take the complaint to AFCA, and AFCA’s contact details. If the complaint is rejected in whole or in part, it must set out the reasons, the firm’s findings on material questions of fact, and enough detail for the complainant to decide whether to escalate.
Systemic issues identification
Analyse complaint data to identify possible systemic issues, escalate them promptly, and investigate them, with clear accountability set by the board.
IDR data reporting to ASIC
Report IDR data to ASIC every six months, covering January to June and July to December, lodged between 1 January and the end of February and between 1 July and 31 August. A firm with no complaints lodges a nil submission.
What BackPro produces for RG 271.
The artifacts your auditor expects. Hashed, signed, timestamped, exportable. Generated continuously while you work, not assembled in the week before the audit.
All complaints across every channel with timestamp, customer, substance, and disposition.
Per-complaint acknowledgement record with channel, timing, and miss-rate trend.
Live view of open complaints with remaining-window clocks and escalation status.
RG 271-formatted responses with mandatory-content checks and dispatch evidence.
Cluster analysis across the register with proposed root cause and remediation.
Six-monthly submission file in ASIC schema, generated from the underlying register.
RG 271, in plain words.
Take this with you · Whitepaper · PDF, 11 pages
Where the data sits: in-tenancy AI under APRA and ASIC expectations
What the Privacy Act, CPS 230, CPS 234 and the licensee obligations actually require of an AI deployment, what they do not, and the questions to put to any vendor. Every obligation cited to its source.
Sent to your inbox. No call, and nothing else unless you ask.
See RG 271 mapped to your own controls.
Forty‑five minutes with our team. We take your existing control register, map it against RG 271 obligations, and show you which gaps BackPro closes automatically. The mapping is yours to keep whether you proceed with us or not.