Beginning on September 13, APRA will require entities to submit in the APRA Connect production environment. It expects entities to:
APRA will launch a test environment on June 17, which will be a permanent feature to help entities become familiar with the interface and functionality of APRA Connect and to trial submission of entity information and data.
Entities can prepare for the test environment by educating themselves on changes resulting from APRA Connect, and any potential impacts to entity submission processes. They also need to commence planning ahead of the transition, and initiate the process of authorising users with myGovID and RAM to act on behalf of their business.
From June 17, the regulator expects entities to:
APRA stated that each organisation will be responsible for managing their APRA Connect users and assigning roles in line with their governance processes.
“Each ABN must have at least one person assigned to the regulatory reporting administrator role, which is the only role with permissions to manage user access,” APRA said. “Each ABN is required to nominate a regulatory reporting administrator via the D2A form: RRA : APRA Connect test nomination.”
APRA administrators will assist entities by assigning the initial regulatory reporting administrator with their permissions upon their first interaction with APRA Connect. It will also require a regulatory reporting administrator nomination for each ABN to enable entities to access the external test environment in June.