D2A's reporting content stays put as the platform moves

APRA has brought forward its plan to migrate all remaining D2A collections to APRA Connect. It says the timeline was brought forward because of early decommissioning of D2A client vulnerabilities. APRA also says it is not changing the collections as part of the migration, with no plans to change data scope, format, grain or frequency in the data collection forms. APRA's migration update

That is a platform change while specified reporting attributes stay the same. For financial planning practices and licensees, the first question is whether the business has a reporting role in an entity covered by the D2A migration. APRA's page does not describe a change to advice obligations or client entitlements. If the business has no such reporting role, the notice is not an advice rule change for it. If it does, the issue becomes practice and licensee operations, rather than advice strategy.

The safe assumption that fails

The obvious prediction is that no new work is needed. If the data scope, format, grain and frequency are unchanged, why change a familiar reporting process?

That prediction confuses the collection with the platform used to submit it. APRA has changed the submission environment and brought forward the timetable, while its statement about unchanged reporting attributes concerns the collections themselves. The migration page does not set out how an affected entity should assign ownership, test its process or manage the transition.

For an advice business with a reporting role, unchanged content is therefore not evidence that the transition can be ignored. It is a reason to preserve the controls that already support the return while examining how those controls will operate through APRA Connect.

Why the timing matters

APRA had announced a plan to migrate all remaining D2A collections to APRA Connect by December 2027. It now says that timeline has been brought forward because of early decommissioning of D2A client vulnerabilities. The previously announced date should not become a reason to wait for a change to the form before preparing for a change to the platform.

APRA also says it has issued a letter confirming the end dates of the Alternate Submission Process for relevant ADI and RFC reporting collections. Entities in those categories should use the transition information that applies to their collections, rather than infer a timetable from the earlier plan. APRA's migration support material

What an affected practice should check

The following is editorial operating advice, not a list of requirements stated by APRA.

• Confirm scope and ownership. Establish whether the practice or licensee has a reporting role in an entity submitting D2A collections. If it does, identify the person responsible for coordinating reporting, technology, operations and any external provider involved in the process.
• Preserve the content controls. APRA says it has no plans to change data scope, format, grain or frequency in the data collection forms as part of the migration. Existing reconciliations and review controls should therefore remain the reference point, while the organisation checks how they will be applied through APRA Connect.
• Use the taxonomy material to define the test. APRA's APRA Connect taxonomy material describes the elements and their properties, data types, forms and rules relevant to selected collections. It also says a full list of rules across all collections is available in the Validation Rules spreadsheet. An affected entity should use those materials to identify which elements, forms and validation rules apply, and who will review any issue found during testing. APRA Connect taxonomy artefacts
• Document the fallback. Record who can complete the process if the usual person or provider is unavailable, what review must occur before lodgement and what evidence the organisation will retain to show that the return was checked. These are controls proposed for transition management, not additional APRA requirements identified on the migration page.

The operating conclusion

APRA's announcement is a platform transition with no planned change to data scope, format, grain or frequency in the forms as part of the migration. For financial planning practices and licensees, the response depends on whether they have a reporting role in an affected entity. Where they do, unchanged collection content is a reason to preserve existing reporting controls while planning and testing the APRA Connect transition, not a reason to assume the work is finished.