Using the change log and triage outcomes
The change log lists every bank detail change LedgerWatch has detected for an organisation, newest first, with the old and new values, when Xero recorded the change, and when LedgerWatch detected it.
Filtering
You can filter the list to all changes, suppliers only, changes not yet reviewed, or by a specific outcome. Each contact also shows how many times it's ever been flagged over the life of the connection, so a contact with a history of repeated changes stands out rather than blending into the list.
Outcomes
Every change starts with no outcome set. You record one once you've checked it:
- Not yet reviewed. The default state. Nobody has recorded a decision yet.
- Reviewed - legitimate. You checked, and the change is genuine.
- Under investigation. You're still checking; not resolved yet.
- Confirmed unauthorised. The change was not made or approved by the supplier or your organisation.
You can add a short note alongside any outcome, useful for whoever looks back on the decision later, including you.
Correcting a mistake
If you set the wrong outcome and correct it within about a minute, the earlier entry is marked as corrected rather than replaced outright. It stays visible, just labelled as a misclick rather than a considered decision. Outside that window, a later outcome is simply added alongside the earlier one. Nothing is ever deleted.
Why nothing is ever deleted
The change log and its outcomes are meant to work as an audit trail. Every outcome anyone sets is kept permanently, even once corrected, so the record can answer not just what changed, but who reviewed it, when, and what they decided. If you need this in a file to hand to someone, see Producing a CSV for an auditor.