Certified Microsoft Dynamics 365 Partner - Est. 1993 - Melbourne - Sydney

Open Banking Solutions

Open Banking Solutions Enable A Simpler Approach ToFinancial Data Access

Open banking in Australia gives eligible businesses and consumers new options and opportunities to share financial data through authorised digital platforms. DHRP supports businesses to investigate banking integration solutions, such as its Dynamics 365 Banking Connector, which presently makes use of Plaid's banking connectivity APIs and does not function within Australia's Consumer Data Right (CDR) framework.

Get in Touch
Banking data and Microsoft Dynamics 365 Finance integration

Trusted By Government,
Non-Profit & ASX-Listed Companies

  • Wilson Group
  • Pepperstone
  • Pacific HVAC
  • IPH
  • NPS MedicineWise
  • Pacific Ventilation
  • Microsoft

Open Banking · DHRP

What is Open Banking in Australia?

Open banking in Australia lets consumers securely and consistently access and share certain financial information with selected organisations. This process is regulated by the Consumer Data Right (CDR) Australia framework, which provides guidelines for consent, access to data and participating organisations.

The open banking system in Australia provides opportunities to leverage financial data that has been shared with other applications for financial management, reporting and more. Open banking data sharing gives access to data, and applicable rules and permissions will depend on the provider, type of data and purpose.

Instead of using Australia's CDR architecture, the DHRP Banking Connector now makes use of Plaid's banking connectivity APIs. When evaluating their needs, businesses should make a distinction between services running on the CDR framework and general banking API interfaces.

Consumer Data Right Consent. Access. Participation.
Authorised data sharing With consent

Your bank

Permitted financial data

API

Selected application

Financial workflows

Access depends on permissions, provider and purpose.

Dynamics 365 Banking Connector financial workflows

Open Banking & Dynamics 365 Finance

For businesses running Microsoft Dynamics 365 Finance, banking integrations could be advantageous in reducing manual processes for accessing bank information and generating statements.

Dynamics 365 Finance and Operations are currently integrated with DHRP's Dynamics 365 Banking Connector. It can create bank statements, link bank accounts, and retrieve daily feeds and historical data. The connector does not presently function under Australia's CDR architecture; instead, it uses Plaid for banking connectivity.

Currently, DHRP's development virtual machine hosts the connector's.NET middleware centrally in an on-premises setting as opposed to Azure. After being transferred to Dynamics 365, account and transaction data are kept in encrypted form on SQL Server.

Additionally, on-premises Dynamics 365 Finance and Operations deployments are supported by the connector. Custom security roles, the Cash and Bank Management module, and a Dynamics 365 Finance license are needed. As of right now, Business Central is not supported.

When considering Australian open banking solutions, businesses should evaluate their banking data requirements, supported financial institutions and integration needs. The present Plaid-based version of the DHRP Banking Connector does not employ the CDR framework, so businesses particularly looking for a CDR-based solution should confirm the provider's CDR status and responsibilities.

Explore the Dynamics 365 Banking Connector

Open Banking - DHRP

What are the Business Benefits of Open Banking?

Open banking data sharing can enable businesses to minimise manual handling of financial information and use the data as allowed by the laws and regulations. Depending on the integration and available data/business requirements, the benefits will vary.

Reduce Manual Data Processing Tasks

When the integration provides automated banking information retrieval, with API-based access, this can help minimise the need to download and transfer banking data manually.

Improve Financial Visibility

Through the information they can access via their authorised integration, account and transaction data can be used to review banking activity and complete financial reports.

Enable Financial Workflow Automation

Where the connected application offers the functions, banking data can be used in banking processes like transaction imports, accounting and reconciliation.

Create more connected business applications

APIs can be standardised to enable compatible apps to share authorised banking data without having to handle it multiple times on supported platforms.

Open Banking - DHRP

How Does Open Banking Work?

Banking integration and authorised data access

Australian open banking solutions involve using APIs and authorised data-sharing agreements to provide access to banking data that is authorised for specified use to compatible applications. The Consumer Data Right (CDR) Australia system requires customers to go through the appropriate authorisation procedure before their customer can access covered data by an eligible organisation.

Select a Banking Data Provider.

Find a provider or integration to accommodate the banks, data types and applications you need. Verify its technical features and possible access options.

Get Required Authorisation

The customer complies with the applicable consent and authentication procedures. This helps to ensure that data is being shared only as per the permissions and conditions.

Access To Permitted Banking Data

The authorised application queries for the data within the customer's permissions. The data available will vary based on the bank, provider and API and applicable framework requirements.

Apply Data In Business Applications

Depending on the functionality of the application and the available information, retrieved data can be used to assist in financial reporting and transaction analysis and accounting workflows.

DHRP Services

Open Banking Use Cases for Businesses

Open banking data sharing can enable a variety of business activities depending on the type of data available, the customer permissions and the capabilities of the connected application.

Accounting and Financial Management

Banking information can be used to help with transaction imports, financial record-keeping, and reporting. Specific functions are dependent on the integration and accounting system.

Bank Reconciliation

Bank information can be used to compare bank activity with accounting data and detect discrepancies in transactions, if the integration is in place for transaction imports.

Cash Flow Visibility

Having access to allowed account and transaction details can enable the business to review incoming and outgoing funds and grasp their cash position.

Financial Analysis

Depending on the information and application capabilities, authorised transaction data can be used for spending analysis, financial insights and income assessment.

DHRP Services

Australia's Open Banking Compliance and Secure Data Sharing

Whether data is accessible for open banking purposes depends on the data, the organisations accessing the data, and the regulatory structure in which open banking falls. If the Consumer Data Right applies, the relevant participants are required to comply with the requirements of the Consumer Data Right regarding consent, access, handling and security of the data.

To ensure that consumer data can be shared in Australia, there must be clear authorisation mechanisms and appropriate protections for personal information. Before implementing an Open Banking service, businesses should evaluate a provider's security measures, data management protocols, and regulatory compliance.

Consent revocation now prohibits the production of bank statements, daily feeds, historical data retrieval, and new account connection operations for the DHRP Banking Connector. Nevertheless, after consent is withdrawn, the connector's SQL Server database still contains the current data. There is currently no automated retention logic or data-retention timeframe in place.

SQL Server stores the connector's account and transaction data in an encrypted format. Voccus is utilised for disaster recovery, and the current development environment is housed on-site at Micron21. When evaluating the product's hosting and data handling procedures, these arrangements should be taken into account.

When deciding on a provider, think about:

  1. Consent and permissions

    Know how access is given, controlled and revoked if these are applicable.

  2. Security of data

    Discuss the security of banking data when accessed, transferred, and stored.

  3. Provider eligibility

    Ensure that the provider has the appropriate authorisation or accreditation (where applicable).

  4. Data access scope

    Validate access to banking data and its usage.

  5. Privacy commitments

    Know how the service processes personal information pursuant to the applicable laws and requirements.

FAQs

Open Banking Questions

Find answers about banking data access, Dynamics 365 integration and the requirements to consider.

Get in Touch

Open banking in Australia supports consumers to consent to sharing their financial data with certain financial institutions under a data sharing arrangement that has been authorised. Covered Data Sharing is governed by the Consumer Data Right (CDR). Access is subject to the requirements, the data concerned, and the organisations involved.

The Consumer Data Right is an Australian initiative that gives consumers the right to choose where certain data is shared, rather than having it shared to everyone. In banking, it refers to specific data that is stored in the participating banks. Access is subject to the relevant consent and eligibility, and regulatory requirements.

Consent, access and data handling are all part of the requirements with regard to Open Banking under the CDR framework in Australia. But security also relies on the organisations and systems in play. Prior to sharing financial information, companies should check a provider's security measures, privacy policies and related regulatory compliance.

DHRP's Banking Connector supports the following controls: HTTPs/TLS communications, access control in Dynamics 365, authentication via Microsoft Entra ID or Dynamics 365 authentication services, audit logging, and encryption of banking data in SQL Server.

Requirements vary depending on the service, the nature of the data and the organisations concerned. If applicable, relevant participants need to fulfil applicable requirements for consent, access to data, security and privacy. It is important for businesses to confirm the status and responsibilities of a provider instead of assuming that all banking APIs are CDRs.

Authorised banking information can be utilised by businesses for accounting, transaction analysis, financial reporting, cash flow visibility and reconciliation. The functions available are dependent on the data source and application. Before these advantages can be realised, an integration must support the necessary data and use case.

Get in Touch with us Today!

We'd love to hear from you. Please fill out this form.

Security Check3 + 7 = ?