Complete error code register from the ATO Data and Payment Standards — Error Code Management document (CD 01). Covers all Section 6 Generic SBR codes, Section 7 Standard Specific codes, and inactive codes. Search, filter and click any row for full detail and resolution guidance.
| # | Error Code | Severity | Response Type | Short Description | Detailed Description | CTR | MRR | MVR | RLVR | GCTR | GCTAR |
|---|
CTR = Contribution Transaction Request · MRR = Member Registration Request · MVR = Member Verification Request · RLVR = All Rollover message types (IRR, RTR, GROLL, USM, RA etc.) · GCTR = Government Contribution Transaction Request · GCTAR = Government Contribution Transaction Amendment Response
Transaction could not be processed. Sender must correct and resubmit. MaximumSeverity may be Error or Partial depending on whether any components succeeded.
Transaction accepted but advisory notice returned. Sender should investigate — no resubmission required unless corrective action is needed.
Processing was successful for all components. A single EventItem must be reported. No action required by sender.
Relates to message structure, schema, data format or XML element rules. For the original message constructor to evaluate and action.
Relates to business rules, identifier matching or fund-specific validation. Must be forwarded to employers to notify them of unsuccessful processing events.
Values in {braces} are dynamic parameters replaced at runtime. The parameter value must appear in the message payload — NOT embedded in the description text.
⚠️ Source: ATO Data and Payment Standards — Error Code Management, CD 01, Version 3.0, November 2025. Applies from 1 July 2026. For questions email [email protected].