Claim Transaction Versioning Example

The following example illustrates the versioning of claims in the transaction repository.

The scenario that leads to the illustrated versions is as follows:

1. The Claim is Finalized on 1-Mar

This leads to version 1 being created in the repository based on the values as they are in the working copy at the moment of finalization.

2. Claim is Unfinalized on 10-Mar

This leads to a transaction label being added to version 1 and a reversal transaction being created for version 1.

3. Claim is updated and reprocessed (from 10-Mar through 1-Apr)

This leads to the working copy data being overwritten with new values. The original values are only preserved in the repository.

4. Claim is Re-finalized on 1-Apr

This leads to version 2 being created in the repository based on the values as they are in the working copy at the moment of refinalization. The version 1 regular and reversal transactions remain in the repository unchanged and can still be read (for example, the reversal could be read for use by a downstream system to reverse the effects of version 1 when version 2 is processed).