Frequently Asked Questions - D2A to APRA Connect Migration
Updated: 9 March 2026
1. Migration and Timeline
1.1: Has APRA factored into the timelines the effort to migrate vendor solutions from XBRL to XML and Excel (which I assume differs in format for APRA Connect)?
Given the XML currently used in D2A will work in APRA Connect, entities can start preparing for the migration now. APRA will provide adequate time for industry to test and will incorporate industry feedback on timing.
Vendors can access the test environment to aid in migration preparation. If your vendor does not have access, please email dataanalytics@apra.gov.au.
1.2: When will the XML specifications for the Large Exp be provided?
APRA Connect will use the same structure as D2A. APRA will provide further information on methods of submissions at a later date.
1.3: When will D2A be fully decommissioned?
Submission of data using D2A will cease on or before December 2027.
1.4: Why the long lead time to migrate to APRA Connect considering there is no change in regulation or data fields?
APRA are working with our vendor to convert the D2A collections into a format that can be consumed by APRA Connect. The associated development requires testing to ensure the collection function in same way as in D2A, and to test the new Excel upload. In addition, the timeline needs to incorporate sufficient time to allow for industry readiness.
1.5: What is the timeframe for migrating Statistical reporting entities, for example non-bank lenders?
Reporting for Registered Financial Corporations (RFCs) will commence for the reference periods of 31 August 2026 for monthly returns and on 30 September 2026 for quarterly returns. Returns for annual reporters will be for financial years that end on or after 30 September 2026. APRA will provide further information for general insurance intermediaries later in the year (2026).
1.6: When will cross form validation be implemented within APRA Connect?
Returns migrated from D2A to APRA Connect will contain all the same validations including cross form validations. The reporting taxonomy artefacts will contain a worksheet with the rules and the syntax for the expressions. Each taxonomy artefact will become available as per the schedule outlined in the consolidated plan.
As of February 2026, you will have access to the EFS and Market Risk rules via the Migrating D2A Collections Support Material webpage.
1.7: When will the granular Data collection timeline be updated?
Work on the granular Comprehensive Credit Collection has ceased.
1.8: We have 3 more forms in D2A for the life insurance industry. When will this be moved?
The plan for the three remaining life insurance forms in D2A and the two superannuation forms heavily impacted by the super data transformation is to rebuild them in APRA Connect. APRA will consult on the relevant reporting standards in the first half of 2026, with the finalised standards to be released before the end of 2026. Collections are expected to commence in the second half of 2027. This will follow the standard process of making changes to a collection.
1.9: Majority of GI forms are in APRA Connect, the lead time for migrating the remaining forms seems to be quite long, any prospect of migrating earlier or early adopting APRA Connect as the reporting tool for remaining GI forms?
As the largest number of forms to be migrated are ADI forms, APRA has chosen to develop those first. We expect to migrate the Insurance forms in mid-2026 to early 2027.
1.10: Will we still have access to D2A once collections go live in APRA Connect?
APRA is not planning on removing access to D2A until late 2027.
1.11: Does each return have parallel run?
There are no parallel runs for the collections migrating from D2A to APRA Connect; i.e. once a collection has migrated to APRA Connect, entities will not have access to submit that collection in D2A.
1.12: How will APRA manage changes to migrated D2A forms?
APRA is not planning on making changes to the forms once they are migrated. APRA will instead rebuild them in APRA Connect.
1.13: What is the plan for form 701?
Form 701 will be made available in the APRA Connect test environment as part of the General Insurance batch for returns in August 2026. APRA will provide more information for general insurance intermediaries later in the year (2026).
1.14: Will forms be grouped in APRA Connect similarly to D2A?
The D2A collections that are migrating to APRA Connect will be grouped into the same returns currently in D2A.
2. Functionality and Features
2.1: Would the current functionality to retrieve submitted forms, amend at a later date, and resubmit still be available in APRA Connect?
Please refer to the APRA Connect guide on information with regards to resubmissions and viewing submitted data.
2.2: Will you be introducing the quarterly packs that are currently in D2A into APRA Connect?
Yes - as much as possible we will try to retain the same forms structures within the same returns.
2.3: Can we safely assume that the historical XML files would work in APRA Connect?
APRA is confident that a D2A generated XML file will work in APRA Connect. However, unlike APRA Connect, APRA does not have visibility of the files that are uploaded by entities to D2A. APRA recommends early testing to ensure that entity generated files will continue to work.
2.4: Will there be any forms that will be retired due to or as part of the migration plan, as iterative forms have been introduced in APRA Connect (e.g., 332 vs 331)?
As part of the migration, APRA is considering if any parts of the current collection can be ceased rather than migrated.
2.5: Will APRA Connect still have the functionality in place that exists in D2A where you can load multiple returns as part of the same pack in one upload?
APRA is investigating this function and will advise the industry of the outcome in the future.
2.6: Will APRA Connect automatically submit the uploaded data as it does with ARS112 and 110 if it successfully passes validation during the upload process?
APRA is investigating the no auto-submit option for migrated forms and will advise industry of the outcome in the future.
2.7: Will there be appropriate testing to ensure APRA Connect performance and availability is adequate prior to go-live given the significant increase in users and data?
APRA will be conducting a range of performance tests before migrating the D2A collections to APRA Connect.
2.8: Will APRA maintain the SBR taxonomy?
Updates to the SBR taxonomy will not be made once a D2A form is migrated to APRA Connect.
2.9: Will Superannuation Taxonomy Artefacts template still be in use after change?
The Superannuation collections that are currently in APRA Connect and their associated taxonomy artefacts will not be affected by the migration of D2A collections to APRA Connect. APRA will separately publish supporting files for the migrated collections.
2.10: Will APRA make the Excel forms available for ADIs for upload purposes on APRA Connect?
Yes, APRA will make the excel templates available as the forms are being made available in test.
2.11: Will XML specifications be provided separately for all the returns being migrated to APRA Connect?
APRA is investigating this function, and will advise the industry of the outcome in the future.
2.12: Will APRA Connect support automation and bulk validation capability or are you keeping D2A open this year for multiple Small APRA Funds Lodgements?
All forms currently submitted via D2A will continue to do so until migrated to APRA Connect. APRA will notify the industry when the forms are migrated to APRA Connect.
2.13: Will APRA Connect support the volume of additional forms since now it is very slow during peak periods?
APRA will be conducting a range of tests before migrating the D2A collections to APRA Connect.
2.14: When will the API be released in APRA Connect?
APRA is actively investigating an API solution for APRA Connect and will be reaching out to industry to provide more information towards the end of 2026.
2.15: What changes to the reporting framework, reporting items, definitions and formats are expected for returns submitted in APRA Connect compared with current D2A returns?
APRA aims to minimise any changes when migrating collections from D2A to APRA Connect. Therefore, you should expect the forms you see in PET and D2A to look the same in APRA Connect. APRA has been using the XML files generated in D2A as part of its testing and encourages entities to use the same (non-XBRL) files that you currently use to load data into D2A in the APRA Connect test environment.
But please remember, it is important to note that entities should be following CPG 234 Information Security regarding segregation of test and production environments, therefore you should be desensitising sensitive production data when used for testing.
2.16: Does APRA Connect support XSD files?
XSD files are not available for the D2A collections migrating to APRA Connect.
The structure of the D2A collections are quite different from the collections APRA have designed solely for APRA Connect. Because of this design difference, it means that the XSD is also quite different and doesn't provide the information you would normally expect.
2.17: Will the number format (scale factor) be the same in the with APRA connect vs D2A for ADI?
The forms that have been migrated from D2A to APRA Connect will maintain the same scale factors.
2.18: For GI entities, some D2A forms still reference old accounting standards (e.g., GRS114_4, GRS310.3, form 701). Will these forms be updated or amended?
APRA is not updating the reporting standards as part of this migration.
2.19: If an RSE entity has exemptions for certain tables (e.g., SRF 001, SRF 610.0), will these exemptions also apply in APRA Connect?
All existing exemptions will continue to apply in APRA Connect.
2.20: For ADIs, will the FAR executive need to attest compliance for each report when first submitting through APRA Connect?
APRA will not seek any additional attestation for the first reporting of migrated returns.
2.21: With submitting suites of returns, will there be the flexibility to submit a suite in "parts" prior to deadlines to enable load balancing?
Individual sections of a return can be loaded and validated separately but a return must be submitted as in D2A.
3. Testing and Validation
3.1: Does an ADI need to register for testing the large exposure return?
No. The large exposure forms are available for ADI's to test in the external test environment. If you do not have access to the external test environment, then you will need to be set up in test environment. Please refer to APRA Connect guide for details.
3.2: Do we have D2A test forms available for general and life insurance for testing purposes?
All remaining general insurance forms in D2A will be available in the APRA Connect test environment from August 2026. The three remaining life insurance forms are being rebuilt in APRA Connect with collections starting in the second half of 2027.
3.3: For entities that are RFCs, when do we expect to be given access to the test environment?
If you are and RFC and do not have access to APRA Connect test environment, please contact us via dataanalytics@apra.gov.au.
3.4: Will there be a detailed roadmap for each ARF when they are rolled over into the UAT so we can prepare?
APRA will look to provide the roadmap for the reporting forms later in the year.
3.5: Will there be an option to export a list of all return errors when it is uploaded?
Please refer to the APRA Connect guide for information on Exporting validation error and warning messages.
3.6: What is the proposed approach to replicate existing D2A cross form validation checks as part of APRA Connect?
The D2A collections that have been migrated to APRA Connect are grouped by the same returns that you are familiar with in D2A.
The cross-form validations within those returns will work the same way in APRA Connect. However, D2A and APRA Connect are not linked in any way - so there won't be any validations between the two systems.
On a related note, for cross return rules, if all the forms are being migrated from D2A, you can expect to see those rules in APRA Connect. Cross period rules will apply once the necessary periods are present in APRA Connect.
3.7: If we submit through the APRA Connect external test environment, does that mean we do not have to submit through D2A?
The APRA Connect test environment is purely for familiarisation. You are required to continue using D2A to submit returns until they migrate to APRA Connect.
3.8: Previously, superannuation returns in D2A and APRA Connect did not cross validate (e.g. Member benefits balance under 320 did not cross validate with forms like 606). Will cross-validation now be enabled?
There won’t be any cross return validations as we won’t be meshing the migrated D2A collections and APRA Connect collections.
3.9: Will we be notified once the forms are available in test environment?
APRA will notify entities when forms become available in the APRA Connect test environment.
3.10: How can we arrange a refresh of our APRA Connect test environment so that portal users match the production environment?
APRA does not have access to undertake this activity. Entities are responsible for overseeing and managing this process themselves.
3.11: When testing the Large Exposures form, APRA Connect only validates some errors rather than validating the entire file. Is this the expected behaviour?
APRA Connect validates data in stages. The first stage is to ensure the structure of the data aligns with the reporting taxonomy. If the file is failing at this stage, the structural issues will need to be addressed before APRA Connect will run the plausibility validation rules.
3.12: Can the APRA Connect test environment be used to test all forms- including existing APRA Connect forms, SDT Phase 2 forms, and future D2A-migrated forms-using actual data, so that validation issues can be identified and resolved before production submissions?
All relevant forms will be available in the APRA Connect test environment, and entities may use actual data for testing if they choose to do so. It is up to entities to decide which data they test, with consideration to CPG 234.
4. User Experience and Support
4.1: We currently have a process where one person prepares the forms (manually) and then a reviewer checks it has been entered correctly and then they approve it by submitting. So, does that mean we can do this process with the no auto submit option?
APRA is investigating the no-auto option which would facilitate this process to migrated forms and will advise industry of the outcome in the future.
4.2: Would Banks be able to access historical submissions in APRA Connect i.e., the ones that were done in D2A?
APRA will not migrate previously submitted returns into APRA Connect. However, this data will remain accessible in D2A until the system is decommissioned in December 2027. APRA expects entities to retain and maintain access to their own historical data.
4.3: Will you be sharing this presented document after the workshop?
Yes, the presentation will be made available on APRA's website.
4.4: Will you be releasing a list of the collections that are under consideration/consultation and may or may not change? Would be very handy for our planning purposes.
Please refer to APRAs Corporate plan for details on APRA’s policy priorities.
4.5: Will APRA Connect team support be available if users experience issues, so those can be resolved quickly?
APRA will continue to offer the existing support channels.
4.6: What is the engagement plan for third party providers (e.g. Nasdaq) so they can update their reporting tools?
APRA recognises the RegTech community as an important stakeholder in the transition from D2A to APRA Connect. RegTechs will be invited to all D2A to APRA Connect information sessions, and APRA will also hold separate sessions for RegTechs as required.
4.7: Will any deadline extensions be available during the migration if we experience issues submitting through APRA Connect?
APRA aims to resolve any issues with reporting and will consider the request for extensions on a case-by-case basis.
4.8: When will the next information session for new APRA Connect users be held?
The next information session for new APRA Connect users will be held in April 2026. Invitations will be sent to new users closer to the date.
4.9: If an RSE entity has multiple defined benefit plans reported in SRF 160.1 (currently over 60 reports in D2A), how will this be handled in APRA Connect after migration?
APRA is currently working with the vendor on the design of these types of forms and will provide more information at a later date.
4.10: Post migration to APRA Connect by end 2027, will APRA still retain other reporting platforms such as SecureDoc (for file/doc uploads) and Extranet (for breach reporting) as backup?
Entities will be informed of changes to SecureDocs and the Extranet if and when they occur.
5. System Access
5.1: To access the APRA Connect test environment, do we use the same login and password as APRA Connect?
The APRA Connect test environment and production environment operate independently. Entities must set up their login credentials and access permissions separately in each environment.
5.2: If we have any issues or questions about accessing the APRA Connect test environment, who do we reach out to?
Please refer to the APRA Connect Guide for information on accessing the APRA Connect test environment. If you experience any issues or are unable to obtain access, please contact dataanalytics@apra.gov.au for assistance.
5.3: Can a person that does not have a MyID access APRA Connect?
MyID validation is a mandatory requirement for using APRA Connect.
5.4: As a foreign branch relying on external reporting software, how should we coordinate with our vendor to ensure they have access to the APRA Connect test environment and technical artefacts?
Third parties can do testing in the APRA Connect test environment. For more information, please refer to the RegTech access to APRA Connect test page on the APRA website.
Technical issues?
- Please refer to the Common D2A errors page.
- Additional information can be found in the:
- Log a support request with the D2A Help Desk at support@apra.gov.au.
- For urgent issues call +61 2 9210 3400 between 9am and 5pm AEST weekdays.
Need help with myID?
Refer to the ATO myID website.
Need help with data validation rules?
The D2A Help Desk cannot assist with validation errors or warnings in D2A returns. For information on validation rules and guidelines, refer to your industry's Reporting requirements page.
For further enquiries about validation rules, please contact: dataanalytics@apra.gov.au.