Correct Transaction Explained

This page describes in details what happens in Verne when data on the register is corrected using the Correct Transaction CTR feature. It covers the following:

how a typical create or maintain business service creates a service transaction and how the information provided by the user via an online form gets applied to the entity data, transaction details and filing,
what constitutes content of a filing,
what information Correct Transaction allows to correct,
how Correct Transaction creates a correction service transaction and how the information provided by the corrector via an online form gets applied to the entity data, transaction details, filing settings, previous correction details and notice of rectification filing settings.

Step 1. Register a company

Verne displays an online form with the:

empty entity fields that are to be provided during registration (subset of entity domain data.)
empty transaction details fields that collect information specific to registration service (e.g. presenter details, any related court orders.)

The user fills in the required details and submits the form. Verne activates this transaction:

the first version of the entity data becomes active.
a filing is generated based on filing instructions configured for this business service.

Step 2. Maintain a company

Verne displays an online form with the:

entity domain fields that can be changed within this service, details are pre-populated from the first entity version E1 (a subset of entity domain data.)
empty transaction details that are specific to this maintain service.

The user fills in the required details and submits the form. Verne activates this transaction:

transaction ST2 is created and activated, it points to ST1 as the previous version and transaction ST1 points to ST2 as the next version.
a filing is generated based on filing instructions configured for this business service. Filing displays the comparison (a.k.a. ‘diff’ or ‘differences’) between the entity details in version E1 and entity details in version E2. This helps the user to quickly understand what changes were introduced by this maintain service.

Step 3. Maintain a company

The Company is maintained again and transaction ST3 is created in the same manner as above.

Step 4. Correct transaction ST2

An error was discovered in the second transaction ST2 and it was corrected using Correct Transaction feature.

Note: In this example, the correction was not manually cascaded to the third transaction ST3. If one of the "previous entity versions" is corrected, in a real-life scenario it will in most cases require cascading of corrections to the entity version data all the way to the current version. So technically there won’t be an impact on the filing of the next version, as the internal user will have to cascade same changes manually. If the correction is not required to be cascaded all the way to the current entity version, then the filing that reverts corrected value back to the current value at some point in the past can be created using Insert Transaction service.

Verne displays an online form with:

the empty fields with correction presenter details and settings for the notice of rectification filing.
all entity domain fields pre-populated from the entity version E2.
all transaction details pre-populated from the second transaction metadata T2.
all filing settings pre-populated from the second filing F2.

The user fills in the required fields. Verne activates this correction:

transaction ST4 is created as a clone of transaction ST2 with corrections applied and additional details about the correction recorded.
transaction ST2 now points to ST4 as the next sibling, ST2 is no longer a current version of the second service instance.
transaction ST1 is re-linked to point to ST2 as the next version, and ST3 is re-linked to point to ST4 as the previous version.
content in filings F2 and F3 reflects corrected entity data.
filing F2 is displayed in accordance with updated filing settings.
Notice of Rectification filing F4 is created, it reflects all corrections made to the entity data, transaction details and filing settings.

Step 5. Correct transaction ST2 second time

Another error was discovered in the second transaction ST2 and it was corrected using Correct Transaction.