Data Hygiene finds clients whose record in Nagaris disagrees with a linked integration record, field by field, and lets you resolve each disagreement without leaving Nagaris. Today this covers clients linked to BGL (CAS 360 and Simple Fund 360). Only staff can see it; client-portal users don't have access.
Click Data Hygiene in the sidebar, under the same section as your other work queues. The list shows every client with at least one open conflict:
Client - links to that client's own conflicts view.
Integrations - a badge per linked integration showing how many fields disagree, for example BGL CAS360 (3).
Unresolved - the count of conflicts still awaiting a decision.
Last Changed - when the disagreement was last detected as different. This stays at an old date for a conflict that hasn't changed since it appeared, since detection only writes something when a value actually changes.
Any client linked to BGL also gets a Data Hygiene tab on their client page, badged with its open conflict count. Opening it (or the sidebar list) shows a table with:
One row per field that disagrees, for example ABN, company name or incorporation date.
A column for your Nagaris value (labelled Nagaris / XPM if your organisation also syncs with Xero Practice Manager).
One column per linked integration record. A client linked to two BGL records gets two columns, each showing the record's name so you can tell them apart.
If a client has no conflicts at all, the tab shows a confirmation that everything tracked on the client matches the linked integration records.
Each value that can be applied has its own Use This button, so you pick the value you want rather than a direction:
Use This under your Nagaris value pushes it out to the disagreeing integration record(s). If your organisation has automatic BGL sync turned off, this queues the change instead of sending it immediately.
Use This under an integration's value pulls that value into the client's Nagaris record.
Ignore leaves both values as they are and stops flagging that particular disagreement.
Some fields only support a subset of these actions. For example, a field BGL doesn't let you write to only offers pulling into Nagaris and ignoring, with no push option.
Once a conflict is resolved, its row shows a status badge: Push Pending, Pulled to Platform, Pushed to Integration, Ignored or Auto-resolved (the values matched again on their own), along with who resolved it and any notes. Resolved rows are hidden by default; use Show Resolved at the bottom of the table to bring them back.
Pulling a value updates the client's record straight away, so other tabs and the page header reflect it immediately.
Pushing a value doesn't touch Nagaris, and ignoring touches neither side.
If a push fails, for example BGL rejects an invalid value, the row shows the error message from the last attempt.
