How to Compare Source and Target Data After a Sync

To compare source and target data after a sync, match records by a stable key, compare only the fields that matter, and classify each result as OK, Missing, Different, or Duplicate.

This gives you a data-level answer to a question process monitoring cannot fully answer: did the expected data actually arrive correctly?

1. Choose the matching key

Use a value that identifies the same record in both systems.

Examples include order ID, account ID, invoice number, or another unique business key.

2. Choose the fields that should match

You usually do not need to compare every field.

Focus on the values that matter for the workflow, such as status, quantity, total, date, or another business-critical field.

3. Classify the result

OK — the expected record exists and selected values match.

Missing — a source record cannot be found in the target.

Different — both records exist, but selected values do not match.

Duplicate — the same key appears more than once where a unique record was expected.

4. Review issues separately from successful rows

A useful reconciliation result should make problems easy to isolate instead of forcing teams to inspect every record manually.

The point is to reduce the dataset to the rows that need attention.

5. Keep the verification independent

The integration system can continue doing the sync.

The reconciliation layer should run afterward and independently verify the result.

Integration moves the data. Reconciliation verifies the outcome.

Where Verirow fits

Verirow adds this independent source-to-target verification step after an integration run.

It is designed to help teams detect records that are missing, duplicated, or different after synchronization.

See the Verirow case study for the wider product workflow.

Related verification workflows

See how to detect missing records after an integration and how to verify API data synchronization.