Gaurav Vageriya
Gaurav Vageriya Integrations Product Manager

BGL - Practice Management Partner Guide

BGL - Practice Management Partner Guide

Practice Management Integration Guide

Last Updated 07th April 2020


This documentation provides assistance with developing the integration between your Practice Management solution and BGL products, CAS360 & Simple Fund 360 (SF360). All integration requirements are set in this guide to ensure development meets BGL requirements. The Integrations Team at BGL specialises in Practice Management Integration and to assist with any questions or additional requirements. If you need any assistance, please contact Gaurav Vageriya (Product Manager) or BGL Integrations Team

Integration Overview

BGL recommends two-way integration that synchronises all contacts between CAS360 and/or Simple Fund 360 and contact data in external Practice Management Solution. This contact integration will allow users to add, update or delete contact data within a product and provides the change data to multiple databases. This is to help the user to reduce entry times and creating data efficiencies across multiple databases.

In addition, CAS360 will automatically produce the required ASIC forms (Form 484) where there is a change of address/name associated with any directors or shareholders of companies. Please see below the diagram which outlines the workflow:



When a user activates the integration, we will use the BGL Integration database to collate and pass contact data to all products that have been activated. The integration for contacts involves two distinct processes being the Initial Sync and Post Sync.

Initial Sync

Flow Example

The normal flow for this is as follows:

  1. BGL retreives client list from the Practice Management Solution using your API.
  2. BGL retrieves all contacts listed in CAS360 and/or Simple Fund 360 and imports into the BGL Integration database.
  3. BGL Integrations DB matches contacts where possible and creates a link between them.
  4. BGL user is prompted to resolve any matching conflicts. Matching Example

The following additional flows is available

  1. Clients/Contacts which exist in BGL but not in Practice Management can be inserted via your API.
  2. Contacts which are missing data in Practice Management can be updated via your API.

Please see the minimum requirements needed to match contacts during the initial sync process in the table below:

Type Minimum Requirements to match Matching Criteria
Individual Contact Type, Name, & Address Matches on Date of Birth and Surname. If no DOB will use First Name and Surname
Company Contact Type, Name & ACN Matches on Name and ACN
Self-Managed Superannuation Fund Contact Type, Name, ABN Matches on Name and ABN
Trust Contact Type & Name Matches on Name only
Partnerships Contact Type, Name Matches on name only

Once the initial data syncing process has been completed, the integration database will be connected. The following data fields will be linked across all integrated databases:

  • First Name
  • Last Name
  • Title
  • Address
  • Date of Birth
  • Phone
  • Mobile
  • Email
  • ACN
  • ABN

Post Sync

There are several options on how we can integrate with your Practice Management application for Post-Sync

Option Description
1. Send BGL Updates (one way) Your application sends updates for clients/contacts to BGL’s API.
2. BGL reads updates BGL reads updates for clients/contacts from your API
3. Both send updates Your application sends updates for clients/contacts to BGL’s API. BGL also sends updates to your API.

Details for BGL’s Practice Management API can be found here.

Pre-requisite Requirements

Prior to enabling a Practice Management integration we instruct clients to export a report from CAS 360, SF 360 and their Practice Manager to remove and potential duplicates and clean up the databases prior to contacts being synced.

Security Requirements

BGL has implemented an Information Security Management System (ISMS) that complies with the ISO27001 standard as part of our obligations as a Digital Service Provider (DSP) with the ATO. As your application is looking to integrate with our API to access data we need you to confirm that your application meets a certain standard. Please see BGL Third-Party Security Questionnaire.

Authentication Requirements

BGL supports you using one of the following Authentication methods:

  • OAuth 2.0 - “Authorization Code” grant type (Preferred Option)
  • OAuth 1.0
  • Basic Authentication

BGL’s API uses OAuth 2.0 - “Authorization Code”

Authentication Workflow

Where an integration uses both BGL’s API and your API the client would need to:

  1. Authorize BGL to gain access to your API .
  2. Authorize your Application to gain access to BGL’s API.

BGL can organise for BGL’s authorization URL to be called automatically once the handshake has been completed with your API.

Connect Example

Data Requirements

Business structures/types

The supported business structures/types, which BGL supports & integrates with, are listed below:

Type CAS 360 Simple Fund 360
Individual Yes Yes
Company Yes Yes
Self-Managed Superannuation Fund Yes No
Trust Yes No
Partnerships Yes No

Contact Fields

Based on the above business structures/types, please see below a list of supported contact fields, mandatory requirements & format limitations for the above.

Field Name Format Mandatory*
Contact id Int Yes
Related contact id Int Yes
relationship type varchar (45) Yes
Number of shares int (11) No
percentage int (11) No
Start date Datetime (6) No
End date Datetime (6) No

*Mandatory fields must be met for the contact, in order to sync with BGL.

BGL Media

BGL’s media kit can be foundat . Here you’ll find our updated logos and brand colour information to use in your applications and webistes.

Make sure you download our BGL Branding guide for more information about our branding style and restrictions.

BGL Sample Buttons

================================================== -->