When a client is linked to Xero Practice Manager (XPM) or BGL (CAS 360 / Simple Fund 360), Nagaris compares its own record against the integration's record and flags anywhere the two disagree. These differences appear on the client's Data Conflicts tab (staff only).
The tab has two views, Conflicts and Ignored, and a Show Resolved toggle to reveal decisions you've already made.
Field conflicts. A single field on the client itself differs between systems, for example the company name or ABN. Each row shows the Nagaris value and the integration's value side by side.
Membership conflicts. A person is a director, officer, member or similar on one side but isn't linked as one on the other. These are grouped by role (Director(s), Officer(s), and so on) and count how many people still need to be placed.
Detail conflicts. A person exists on both sides, but a detail about them doesn't match, for example their date of birth, mobile number, email or residential address. Nagaris bands every mismatched detail for that person under their name, so three problems with one director read as one thing to look at rather than three unrelated rows. Click the person's name to open their contact details.
Every row that needs a decision offers:
Use This under whichever value you want to keep. Depending on the field, this either pulls the integration's value into Nagaris or pushes the Nagaris value out to the integration.
Ignore to leave both values as they are and stop flagging that difference.
Once resolved, the row shows who resolved it and when. A badge tracks the row's state: Unresolved, Push Pending (queued to send to the integration), Pulled to Platform, Pushed to Integration, Ignored, or Auto-resolved. If a resolution attempt fails, the row shows "Last attempt failed" with the error.
Pulling a value into Nagaris and pushing a value to the integration are independent actions per conflict, so you can accept some values from the integration and send others back to it on the same client.
The Data Conflicts tab only appears when the client is linked to XPM or BGL.
A membership row only appears when someone is missing from one side. A person both systems already agree exists shows up as detail rows instead, not as a membership row.
Resolving a detail conflict updates the client's People & Roles card (and the page header, for a client-level field) once the change goes through.
