Source-to-Target Data Reconciliation Explained
Source-to-target reconciliation compares the records in the originating system with the records that exist in the destination after data has moved between them.
The basic model
The source represents what should exist. The target represents what actually arrived. A reconciliation process matches records by a shared identifier and then compares selected values.
Four useful outcomes
- OK: the record exists on both sides and selected values match
- Missing: the source record has no corresponding target record
- Different: the record exists on both sides but one or more compared values differ
- Duplicate: the same logical record appears more than once where only one was expected
Why targeted comparison is useful
Teams rarely need to compare every property in every system. A targeted reconciliation can focus on the fields that actually determine whether the integration result is operationally correct.
When to run reconciliation
It can be run manually during investigation, scheduled for recurring verification, or triggered automatically when an integration workflow finishes.
Do not stop at integration success.
Compare the actual source and target data after the workflow finishes.
Start verifying→