How ClaimDS handles changes
ClaimDS edits forward and reverses or cancels rather than deleting — documents are immutable, history stays frozen, and every change is on the audit trail.
ClaimDS handles change in a deliberate way, because it's a financial system of record. The short version: it edits forward, reverses or cancels rather than deletes, and never quietly rewrites the past. Once you understand that principle, the specific rules all follow from it.
Edits go forward
When you change a setting — a price, an agreement's rate, a partner's details — the change applies from now on. It doesn't reach back and rewrite what already happened. Past transactions keep the values they were created with (see what changing master data affects).
Documents don't change
Anything ClaimDS generates as a record — a factsheet, a credit note — is frozen once created and carries a fingerprint so it can be verified. It's never edited in place. A correction is a new document, not an altered one.
Reverse and cancel, don't delete
The same goes for what's been booked. An accrual is reversed, not deleted. A settlement is reversed (before payout), not deleted. A claim is cancelled with a recorded reason. Each leaves a complete, paired trail rather than a gap.
History stays frozen
Business volume lines snapshot their prices, classifications and partner details at the moment they're loaded. So editing master data later doesn't silently change old invoices or the accruals built from them.
It's all recorded
Every change, reversal and cancellation lands in the audit trail with who did it and when. That's what lets you answer "what changed, and why?" at any point — which is the whole reason ClaimDS works this way.
Related
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.