APRA Connect support material
Last updated: 26 October 2021
APRA Connect Guide
The APRA Connect Guide provides comprehensive information to assist users accessing, navigating and using APRA Connect. The guide should be used in conjunction with taxonomy artefacts when preparing and submitting data to APRA.
APRA Connect webinars provide overviews of key subjects and demonstrations. See all APRA Connect related videos, and supporting materials.
Frequently Asked Questions
These frequently asked questions (FAQs) provide timely guidance on commonly asked questions about APRA Connect.
Do I need to set up users in APRA Connect if I am already set up in the test environment?
Yes. The APRA Connect test and production environments are distinct and separate environments and there is no data transfer between the two environments. All users will need to be set up in the production environment. Key steps:
- Nominate initial Regulatory Reporting Administrator (RRA) and request additional roles if required via D2A form (RRA_PROD: APRA Connect nomination for 13 September go live)
- Login to APRA Connect and authenticate through myGovID/RAM to create your account
- Await role assignment by an APRA Administrator
- Once RRA role is assigned, the RRA can then assign roles to other users as they log in to APRA Connect
Do I need to set users up again in RAM?
No. If your users have already been authorised in RAM as part of the process of onboarding in the test environment, or using other APRA services, you will not need to make any changes. Any new users will need to be authorised in RAM to act on behalf of an entity.
Please note that authorisation in RAM for APRA Services covers all APRA systems including APRA Connect test and production environments and Extranet.
What is the role of the Regulatory Reporting Administrator?
The Regulatory Reporting Administrator (RRA) is responsible for:
- granting access to other RRAs, Preparers, and Service Providers
- managing user roles and permissions to ensure users remain current. This involves updating users' permissions when a user departs the organisation.
APRA requires one RRA to be nominated for each reporting entity (ABN). An RRA cannot assign additional roles to themselves, therefore in the event that the RRA is the only APRA Connect user for an entity, APRA will facilitate all required roles for the RRA in the production environment.
RRAs are able to complete, validate and submit returns.
See more information on user roles and permissions in the APRA Connect Guide.
How do I nominate someone as the initial Regulatory Reporting Administrator?
You can nominate the initial RRA through the D2A forms for either APRA Connect test environment (RRA: APRA Connect test nomination) or APRA Connect production environment (RRA_PROD: APRA Connect nomination for 13 September go live). For APRA Connect you will also need to nominate any additional roles for the RRA.
If you don’t use D2A contact us at email@example.com.
I’ve been nominated as the Regulatory Reporting Administrator via the D2A nomination form, why can’t I see anything when I log into APRA Connect?
Nominating an initial Regulatory Return Administrator informs APRA who should be assigned the initial role in APRA Connect, however it does not create an account in APRA Connect. Account creation occurs through the first transaction of authenticating through myGovID. An APRA Administrator will then assign the RRA role to the user if the new account is created for a nominated RRA.
I can see a number of entities’ returns when I log into D2A. Why can I only see details for one entity in APRA Connect?
Users must log in independently for each entity to view details for that entity. This means having a separate relationship established in RAM for each entity, and logging in and authenticating for each entity. You will need to log out and log back in selecting the next entity/ABN in RAM to view details for another entity.
I’ve logged into APRA Connect for the first time, why can’t I see anything in the Home menu?
When you login for the first time, you will not have any roles assigned to you and therefore will not be able to access functionality.
If you are the first user onboarded for your entity, an APRA Administrator will assign your roles if you are a nominated RRA. If you are not a nominated RRA, you will need to wait until your entity’s nominated RRA logs into APRA Connect and has their roles assigned, so that they can proceed to assign you with your appropriate roles.
Assigning a role is a manual step and there will be a lag between the time your user account is created and the time your role(s) are assigned. You will receive a notification once your roles have been assigned.
Why am I receiving emails from APRA Connect in my personal email address?
When a user is authorised to access APRA services on its behalf in the Relationship Authorisation Manager (RAM), the email address used is the email that the APRA Connect user account will be created with. The email address that is used in RAM can be different from the email address used for your myGovID digital identity. When setting up authorisations in RAM for an entity, APRA requests the use of a business email address as this is the email address that will be used for APRA Connect notifications.
Can I use a shared email address for APRA Connect?
APRA recommends against the use of shared email addresses because it removes the ability to identify individual users who have interacted with APRA Connect. We understand there are some instances where a shared email address is preferred however there are limitations for use. Users need to be aware that email addresses must be unique to a user, therefore if a second user attempts to login to APRA Connect using a shared email address already assigned to a previous user’s account, they will be unable to access APRA Connect.
My organisation provides regulatory reporting software. Can I access the APRA Connect test environment to test output files and various processes?
Yes, see more information on RegTech access to APRA Connect test and how to request access.
Why can’t I see any returns allocated when I have logged in as a trustee or administrator?
You will need to log in at fund level with the relevant ABN to see allocated returns
The Superannuation Data Transformation returns are all submitted at the fund level, by logging in with the fund’s ABN. This is different to D2A and the SRF_001 form which allowed details for each fund to be submitted collectively by the trustee or administrator.
Do I need to complete new Superannuation Data Transformation (SDT) returns in any particular order?
Yes, SRS 605.0 RSE Structure (SRS 605.0) return should be submitted before attempting to upload and submit all returns except data under SRS 332.0 Expenses (SRS 332.0). RSE Structure defines:
- Superannuation products
- Investment menus
- Investment options
- Fees and costs arrangements
This sets up each of the entity’s business operations in APRA's system so that they can lodge a range of regulatory returns.
SRS 605.0 needs to be submitted and up-to-date before submitting the returns under:
- SRS 251.0 Insurance Arrangements (SRS 251.0)
- SRS 550.0 Asset Allocation (SRS 550.0)
- SRS 606.0 RSE Profile (SRS 606.0)
- SRS 611.0 Member Accounts (SRS 611.0)
SRS 605.0 and SRS 606.0 both need to be submitted and up-to-date before submitting the returns under:
- SRS 705.0 Performance Components (SRS 705.0)
- SRS 705.1 Performance Benchmark (SRS 705.1)
- SRS 706.0 Fees and Costs (SRS 706.0)
I cannot see the RF 520.0 Responsible Persons return in APRA Connect
The Responsible Persons return is part of the Company Profile in APRA Connect and will not be allocated; instead users with the Corporate Profile User role will be able create a return when your entity profile needs to be updated. For more information on the Company Details and Corporate Profile refer to Chapter 5 of the APRA Connect Guide and for more information on permissions refer to 3.2.3 User roles.
I am getting errors that one of my RSE superannuation products/investment menus/investment options/fees and costs arrangements are already registered, what should I do?
The RSE Structure return updates the following sections of the Company Profile:
- Superannuation products
- Investment menus
- Investment options
- Fees and costs arrangements
The first time this return is submitted all the records will need the status of New; likewise when any new superannuation products/investment menus/investment options/fees and costs arrangements the status of New must be reported.
After the initial submission an entity will need to create an ad hoc submission when an RSE licensee wishes to make changes to an RSE’s products, investment menus, investment options or fees and costs arrangements. Entities will create their own RSE Structure return via the Create Return function.
When should I upload via XML instead of Excel?
Generally, entities are able to make this choice based on their own organisation’s needs and technical capabilities; however if the data being uploaded exceeds the row limits allowed in Excel then entities must use XML.
Why can’t I see any APRA returns in APRA Connect?
Most current data collections will remain on D2A. As APRA replaces existing collections, they will be introduced on APRA Connect in line with industry consultation. The first data collections on APRA Connect are Private Health Insurance HRS 605 and the Superannuation Data Transformation collections.
If my entity’s reporting remains on D2A for now, why do I need to onboard to APRA Connect?
All entities are required to keep entity information current in APRA Connect. This includes entity profile details such as addresses, contact person details, and Responsible Persons and Accountable Persons (where applicable). Entities are able to submit documents to APRA via the Ad Hoc return. See the APRA Connect Guide on Ad Hoc Return for more information.
What type of documents can I upload into the Ad Hoc return?
The Ad Hoc return allows users to attach and submit documents through to APRA. A user must have the Ad Hoc Return permission to create and submit this return. The types of documents to be submitted through this return include:
- Aggregate Risk Exposures
- Information Security
- Intra Group Transaction and Exposures
- Margining and Risk Mitigation for non-centrally cleared derivatives
- Outsourcing/Business Continuity Management
- Risk Management
- Risk Management & Business Plan
Note: The Ad Hoc Return should not be used to submit data that is intended for upload into a data collection return.
See the APRA Connect Guide on Ad Hoc Return for more information.
How do I request the approval step for validated data returns to be applied?
An optional approval step in the form of a validation rule (a warning) prior to submission of a completed data return is available. Entities may elect to activate the rule for all data returns by notifying APRA at firstname.lastname@example.org. Once activated for an entity, the rule will apply to all data returns.
Currently this rule only applies to the Superannuation Data Transformation collection and Private Health Insurance HRF 605.0 return.
Using APRA Connect
Log a support request with the Service Desk at email@example.com and ensure that you include the ABN of the entity the issue relates to.
For urgent issues call +61 2 9210 3400 between 9am and 5pm AEST weekdays.
Need help with myGovID or RAM?
Refer to the myGovID website.