The reporting client moves while the collection stays steady

APRA says it will migrate all remaining D2A collections to APRA Connect, but is not changing the collections as part of the migration. There are no plans to change the data scope, format, grain or frequency in the data collection forms. APRA's migration support material

APRA says the timeline has been brought forward because of the early decommissioning of D2A client vulnerabilities. APRA had announced a plan to migrate all remaining D2A collections to APRA Connect by December 2027. It describes APRA Connect as a single, modern data submission portal that will remove the need to maintain the aging D2A client on industry infrastructure.

That creates a reasonable question for a financial planning business: does the migration require a practice-wide response, or can it be ignored? The official material does not support either assumption on its own.

Start with scope, not systems

The material establishes a migration of APRA collections and a change in the reporting client. It does not establish that advice practices, platforms, administrators, product data feeds, portfolio reconciliations or client reporting processes are affected.

That distinction matters. A practice may have no role in an APRA collection and no need to respond to the migration. Alternatively, a provider used by the practice may be an entity maintaining the D2A client on industry infrastructure. In that case, the practice may need provider‑specific information about the transition. The official record does not establish which advice businesses, platforms or administrators fall into that category.

APRA's migration page specifically refers to a letter to industry confirming the end dates for the Alternate Submission Process for relevant ADI and RFC reporting collections as part of the transition to APRA Connect. It also provides FAQs, key support materials and links to further information to assist entities.

For an advice business, the first question is therefore whether it is itself an entity involved in an affected collection, or whether a relevant provider has confirmed that it supports an affected collection or maintains the D2A client. APRA's material refers to remaining D2A collections and relevant ADI and RFC reporting collections, but it does not establish that every entity or collection is affected in the same way.

Separate the collection from the implementation

The unchanged data specification answers one question. It does not answer every question about how an affected entity will implement the move to APRA Connect.

If a provider confirms that it is affected, the practice should ask which collection is involved, what transition detail applies, whether the practice receives information from that process and whether the provider requires anything from the practice. Those are conditional implementation questions. They should not be presented as confirmed changes to advice‑business systems.

The same discipline applies to APRA's taxonomy artefacts. APRA says they include the collection name, schema properties, elements, data types, enumerations, Form Set, Folders where relevant, Forms and Rules. A full list of rules across all collections is available in the Validation Rules spreadsheet.

Those materials are relevant to an entity working through an affected collection. They are not evidence that every financial planning practice needs to review its own data structures or reporting processes. A practice should establish the connection first, then use the relevant APRA material or provider information to understand what follows.

Do not infer more than APRA has said

It would be easy to read the unchanged scope, format, grain and frequency as proof that no operational attention is required. That may be the correct conclusion for a practice outside the affected reporting arrangements. It is not a conclusion that can be applied to an entity whose D2A client is being replaced by APRA Connect.

The reverse error is equally important. APRA has not stated that advice‑business credentials, interfaces, validation responses, exception paths or contingency arrangements will change. Those matters remain provider‑specific implementation questions unless an affected entity confirms otherwise.

For financial planning businesses, the accurate takeaway is conditional. Confirm whether the practice or a connected provider is an affected entity before allocating systems or compliance work. Until that link is established, the announcement supports no broader claim about the operation of financial planning practices.¹