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.

Entities should submit one consolidated Excel workbook per return, with each required form included as a separate worksheet within that workbook.

No. Submissions in D2A are made at a Return level. Entities should ensure that all the forms related to a return are submitted together either as an XML (Preferred), XBRL or Excel file.

Please note that incomplete submissions will not be accepted and processed. Entities should ensure that all the forms (including Nil forms) are submitted together for each return.

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.

Yes. For tables where additional rows may be required, entities may insert rows directly into the spreadsheet as needed.

Adding rows will not affect the template, provided that:

• existing columns, headers and formatting are retained, and
• additional rows follow the same structure as the original table.

Entities must not delete any columns or alter the layout of the template, as doing so will impact submission process.  

Where a reporting form is required to be submitted multiple times for different reporting units (e.g products, funds, investment options etc.), entities should create a separate worksheet (tab) for each reporting unit within the same Excel workbook.

Each worksheet should use the same form template and be clearly labelled to identify the reporting unit. All required worksheets must be included in a single consolidated Excel workbook for submission.

Yes. Entities can include multiple returns within a single ZIP file when uploading data to APRA Connect, provided that each return is correctly prepared in line with APRA’s submission requirements.

For XML or XBRL submissions, all required files must be included within a ZIP file, as APRA Connect does not accept XML or XBRL upload files.

For Excel submissions, entities should continue to submit one consolidated workbook per return, with each required form included as a separate worksheet. Multiple Excel workbooks (each representing a different return) may be included together within a single ZIP file where required.

No. Entities must not use APRA Connect taxonomy artefacts when preparing submissions for D2A returns.

APRA Connect taxonomies and artefacts are designed solely for preparing and submitting data via APRA Connect and should not be used for generating files for submission using D2A.

For D2A returns, entities should use the D2A Excel templates that are available on the APRA website¹

The Plain English Taxonomy (PET) is the source of truth for preparing D2A submissions. Entities must rely on PET for reporting definitions, allowable values, table structures, and validation expectations when completing D2A returns.