Alternative submission arrangements for D2A collections

These can be found in APRA Connect in line with APRA’s guidance issued on 8 April 2026, as the following returns.

Entities without XML or XBRL reporting capability may submit using Excel. If an entity submits using Excel they must use the D2A Excel templates published on the APRA website.

APRA is developing a method to provide entities access to previously submitted returns. Until this is available entities should direct urgent requests to the Data Analytics team.

Refer to the guidance below to uninstall D2A.

APRA will issue due date reminders the day after the end of the reference period and seven days before data is due.

Existing reporting due dates remain unchanged. APRA will monitor impacts during the transition period.

Entities must submit returns using XML (preferred), XBRL or Excel, noting that multiple returns can be attached and submitted together in one ad hoc submission.

Submission requirements are as follows:

XML and XBRL

Submissions are made at the return (suite) level, with all required forms included.

Must be uploaded as a ZIP file, as APRA Connect does not accept standalone XML or XBRL files.

Excel

Must be provided as a single Excel workbook containing all forms for the return, with each form in a separate worksheet.

For Excel submissions, entities should ensure the following:

• Submissions should use the template provided on the APRA Website.
• Entity name and ABN are completed in each form.
• Values are entered using the correct scale factor, as indicated in PET.
• Values entered in drop-down fields match the drop-down options and the values specified in PET.
• Percentage values are entered as numbers (do not use the ‘%’ symbol).
• Zeros are entered as numeric values (do not use dashes ‘-’).
• Negative values are entered as numbers (do not use parentheses).

Where issues are identified, APRA will require the entity to correct and resubmit the data. This may delay processing.

APRA will process submissions and contact the entity where issues are identified. On successful submission, APRA will email a D2A submission receipt number to the Regulatory Reporting Administrator(s).

Warning messages will be added to the entity’s data queries list and managed through the standard data query process.

Historical data resubmissions must be submitted as an ‘Ad hoc file upload’ return. Resubmissions must be made at the return level (not form level) and provided as a single ZIP file using the naming convention below.

ZIP file naming format

• “D2A_<resubmission> <return_name>_<period_end>”.zip

Example

• “D2A_resubmission_ Monthly_EFS_Return_31Dec25”.zip
• “D2A_resubmission_ Quarterly_Return_30Sept25”.zip

MyID is required to access APRA Connect to ensure only verified individuals act on behalf of regulated entities. Where overseas personnel cannot meet identity requirements, entities must contact the Australian Taxation Office (ATO) regarding options to establish myID and RAM access from overseas.

ATO contact details are provided below:

Phone Number: +61 2 6216 1111

Operating Hours: 8:00 am to 5:00 pm (AEST), Monday to Friday

Note: Request transfer to the myID support line or RAM support line.

The APRA Connect Test environment is used to trial submissions and become familiar with the submission process.

Submissions made in the APRA Connect Test environment cannot be further processed by APRA. To meet reporting obligations, D2A returns must be submitted in the APRA Connect Production environment.

Returns should be submitted via APRA Connect. Where SecureDoc is used, the corresponding return must also be submitted in APRA Connect (without an attachment) to support reconciliation.

Entities should note that files submitted via SecureDoc are automatically deleted after 30 days.

Only at a technical level. APRA Connect taxonomies align to the same reporting requirements and data definitions as D2A.