Applied corrections

Every correction in force on this migration, and the approved change request that put it there.

Corrections sit on top of the legacy data, never inside it

The imported rows are never edited or deleted. What you see here is a layer of approved decisions applied over them, which every run re-applies from scratch. That is why each row names the change request that authorised it, and why undoing one is not an edit either: it is another change request, needing the same approvals.

Record overrides

One staged record corrected. The source line keeps its original text permanently; the override is applied on top of it each time the pipeline runs.

Normalized record

0 record overrides
Record	Correction applied	Reason and authority	Status	Revert
None yet. A record override appears here only once a change request proposing it has been approved and applied.

Entity decisions

Merges and keep-distinct decisions about parties the engine flagged as possible duplicates. The legacy customers and vendors are never rewritten; the decision sits on top of them.

Normalized record

0 entity decisions
Decision	Reason and authority	Status	Revert
None yet. These appear here only once a change request proposing one has been approved and applied.

Dispositions

Real misstatements in the legacy books, accepted with a documented reason and follow-up rather than silently corrected in migration history.

Normalized record

0 dispositions
Decision	Reason and authority	Status	Revert
None yet. These appear here only once a change request proposing one has been approved and applied.