Use the audit trail
Find, filter and export the ClaimDS audit trail — the tamper-evident record of every change across the product — for an internal review, an auditor or a compliance check.
The audit trail is what lets you answer "who changed this, and when?" without reconstructing it from memory. It's a tamper-evident record of every write across ClaimDS, designed to satisfy an auditor — and it's verified by a hash chain so it can't be quietly altered after the fact.
What makes it trustworthy
Two design choices make the trail dependable. It's append-only — entries are added, never edited or removed — and its integrity is hash-chain verified, so any tampering would be detectable. That's the same principle behind ClaimDS reversing settlements instead of deleting them: the history stays complete.
Find what you need
Follow the numbered steps below to scope the trail to a period and a subject and export it. Access to the audit trail is role-gated — if you can't open it, see fixing access errors.
Step-by-step
Open Audit
Go to Audit. The trail records every write across every part of ClaimDS — who did what, and when — in one auditor-ready place.
Set the period
Choose the date range you need. An empty or out-of-range period simply returns no rows, so widen the range if you expected to see activity.
Filter to what you're checking
Narrow the trail to the area, record or actor you're reviewing — for example the changes to a particular agreement or settlement — so you see only the relevant history.
Read the change history
Each entry shows the change in context. Because settlements and amendments are recorded rather than overwritten, you can follow exactly how a figure reached its current state.
Export for an auditor
Export the filtered trail when you need to hand it to an auditor or attach it to a compliance pack. The export reflects the same tamper-evident record you see on screen.
Frequently asked
Can entries in the audit trail be edited or deleted?
No. The trail is append-only and tamper-evident — its integrity is verified by a hash chain — so it stands up as evidence rather than being something that can be quietly changed.
Why does a reversed settlement still appear?
Because ClaimDS reverses rather than deletes. The original settlement and its reversal both remain in the trail, so the history is complete.
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.