Common Entity Correction Functionality

The following topics highlight functionality common to all entity correction use cases.

Creating Entity Corrections

Entity corrections are created via an interface. The expectation is that analysis is performed using an appropriate reporting or analysis tool to determine the records that require a special action to be performed. The appropriate records for the use case in question are selected in that tool and interfaced to the system.

Entities Linked to the Entity Correction

The types of records (referred to as Entities here) linked to the entity correction depend on the type of entity correction. For example, an entity correction for mass cancellation of tax forms expects tax forms to be linked to the entity correction. An entity correction for mass suppressions of taxpayers expects person IDs to be linked.

Some types of records have an external reference. For example, a tax form has a DLN; a person has an ID number. If the algorithms for the particular use case support it, the external ID may be provided when creating the entity correction.

Entity Link Status

The Link Status refers to the status of a particular entity to a particular entity correction. The following points highlight the status values.

Approving Entity Corrections

Once the entity correction and its list of entities are validated, the system transitions the record to Approval in Progress and a To Do entry is created to alert the appropriate user(s). At this point, the reviewing user may Approve or Reject the record.

Performing the Mass Action

Once a user approves an entity correction, a batch process processes the linked entities to perform the mass action. The action performed depends on the business use case.

The expectation is that this process is part of the nightly batch cycle. As such there may be a delay from the time that an entity correction is approved to the time its related entities are impacted by the action that is performed.