The BGL integration brings your CAS 360 company data and Simple Fund 360 (SF360) SMSF data into Nagaris, so corporate details, officers, members and addresses appear directly on the matching client records.
In the sidebar, open Settings, choose Integrations, and select the BGL tab. The BGL card reads Connect your organisation to BGL to manage client data.
Click Continue with BGL. You're taken to BGL to sign in and authorise Nagaris, then returned to Nagaris.
If your Nagaris login is already signed in with BGL, the button reads Connect BGL Account instead, clicking it links BGL to your organisation straight away (BGL organisation connected successfully.).
Once connected, the card shows a Connected badge with the Connected since date, plus two sync switches:
Nagaris automatically updates BGL - changes made in Nagaris are pushed to BGL.
BGL automatically updates Nagaris - changes made in BGL flow into Nagaris.
Flick either switch at any time; Nagaris confirms with Sync settings updated successfully. To disconnect, open the three-dot Extra Actions menu and choose Disconnect BGL (BGL organisation unlinked successfully.).
The two switches control direction independently, so any combination is possible. Nagaris keeps comparing your data against BGL either way, the switches only decide whether a mismatch is applied automatically or left for you to act on.
Toggles | What happens when the two sides disagree |
|---|---|
Both on | Nagaris pushes your changes to BGL and pulls BGL's changes into Nagaris automatically. Matching fields stay in sync without you doing anything. |
Only "Nagaris automatically updates BGL" on | Your edits in Nagaris push to BGL automatically. A change made in BGL doesn't pull in on its own, it shows up as a conflict on the client's Data Hygiene tab for you to resolve. |
Only "BGL automatically updates Nagaris" on | A change made in BGL pulls into Nagaris automatically. Your edits in Nagaris don't push on their own, they show up as a conflict on the client's Data Hygiene tab for you to resolve. |
Both off | Nagaris doesn't move data in either direction. Every mismatch is flagged as a conflict on the client's Data Hygiene tab, and you decide field by field whether to push, pull or ignore it. |
See Resolving data conflicts and duplicate suggestions with Data Hygiene for how to work through a flagged or queued mismatch.
If BGL rejects the connection with an authorisation or not authorized error, the fix is on the BGL side: the BGL user you're connecting with needs third-party app access enabled for their BGL role (in BGL's Apps and Integrations settings). Ask your BGL administrator to enable it, then retry Continue with BGL. If it still fails, send support the BGL product (CAS 360 or SF360), your BGL role and the exact error text.
Clients that are linked to a BGL record get a BGL tab on their client page (visible to your team, not to client-portal users). Depending on whether the record comes from CAS 360 or SF360, you'll see cards including:
BGL Company - CAS 360 company details such as ACN, Business Number, Incorporation Date, Annual Review Date and status, Registration State, Jurisdiction, Company Type/Class/Sub Class, ABN and ASIC Agent Number. The company name and BGL ID link straight to the record in CAS 360.
BGL SF360 Entity - fund details such as Entity Code, Entity Type, SF Code, ABN, TFN Provided, Fund Email, financial year dates, GST Registered, ESA, trust deed details and addresses. The name and BGL ID link to the entity dashboard in SF360.
Members and Contacts - the people attached to the entity, grouped by role (members, trustees, auditors and others), plus BGL SF360 Entity Members, BGL CAS 360 Addresses, BGL Company Officers, and the company's shareholdings and share transactions.
Opening the BGL tab on a CAS 360 company automatically triggers a fresh sync of that company's data, so what you see reflects BGL's latest records.
This card shows one entry per address type (for example Registered Office, Postal, and Principal Place of Business), each labelled with our own address wording rather than CAS 360's. Every entry shows only the address currently in effect.
If a type has more than one address on file, past or future-dated, the card's actions menu gets a View History option. It opens a table of every address of that type with its effective date and a Current, Upcoming or Past status badge.
A type whose only address is dated in the future shows No current address until that date arrives, but you can still open View History to see it.
You can delete an individual address from the card itself or from the History table.
The BGL Company Officers card lists only appointments that are in force today, so a director who resigned years ago doesn't clutter the card alongside someone appointed last week. An officer counts as current when their position status isn't Resigned, Removed or Deceased, and their appointment has started and hasn't ended yet.
If the company has any officer history at all, a clock icon button (View Officer History) appears in the card header. It opens the full record, with each officer's appointed and ceased dates and a status badge:
Current — in force today.
Upcoming — appointed with a start date that hasn't arrived yet.
Past — resigned, removed, deceased, or otherwise ended. The reason CAS 360 recorded (for example Resigned or Deceased) shows next to the badge.
You can delete an officer record from the History dialog using the trash icon on its row.
The BGL Company Officers card lists only the appointments in force today, one card per officer with their position, contact details and any alternate or nominator contact. An officer whose appointment is scheduled to end shows its Cease Date right there on the card.
Officers who have resigned, been removed or died, and appointments filed for a future date, don't clutter the current list. Instead, click the History button in the card header (it only appears once there's history to show) to open Officer History: a table of every officer CAS 360 has ever recorded for the company, each tagged Current, Upcoming or Past, with their appointed and ceased dates. For a past officer, the table also shows the CAS 360 reason the appointment ended, such as Resigned or Deceased. You can delete an officer record from this history view as well as from the card.
If a company has officers on record but none are currently in force, the card says so and points you to the history rather than showing an empty list with no explanation.
A BGL-linked client also gets a Data Hygiene tab that lists every field where Nagaris and BGL currently disagree, with a button to pull BGL's value in, push your Nagaris value out, or ignore the difference. This is the fastest way - fix a mismatch like an out-of-date address without leaving Nagaris. See the Data Hygiene article for details.
You can also edit many BGL cards directly in Nagaris using each card's edit button (for example Edit BGL SF360 Entity) — with Nagaris automatically updates BGL switched on, this keeps both systems aligned. Or correct the value in BGL itself and let it sync back.
When a field holds different values in Nagaris and BGL, it shows up as a conflict with both values side by side. For each conflicting field you can:
Click Use This under Nagaris's value to push it to BGL, or under BGL's value to pull it into Nagaris.
Mark it as ignored to leave both values as they are and stop it being flagged.
Addresses work a little differently, since a client can hold more than one address of the same type (for example two registered office addresses during a move):
If Nagaris holds several addresses of that type, each one gets its own Use This button, so you choose exactly which address goes to BGL.
Pushing an address to BGL asks for the effective date it takes effect in CAS 360, and lets you choose whether to prepare the ASIC form for the change. If you tick that option, Nagaris shows an Action required in CAS 360 dialog afterwards: BGL has the data, but you still need to open CAS 360 and generate and lodge the ASIC form yourself, Nagaris has no way of telling you once that's done.
Pulling an address from BGL asks whether it should replace the address Nagaris already holds of that type, or be kept alongside it as an additional address.
Nagaris never prepares or lodges an ASIC form on its own. Preparing one is a checkbox you tick yourself each time you push an address change, and even then Nagaris only flags that CAS 360 needs a form, you still generate and lodge it in CAS 360.
You can also sign in to Nagaris itself with Continue with BGL on the sign-in page.
Connecting BGL is organisation-wide; the sync switches affect all linked clients at once.
The organisation-wide Data Hygiene page (in the sidebar) lists every client with a BGL conflict, across your whole client base, not just one at a time.
