How to Detect Missing Records After an Integration

To detect missing records after an integration, compare the source and target datasets using a stable record key and flag source records that have no matching target record.

An integration can finish without an obvious process error while still leaving records behind.

That is why process monitoring and data verification should be treated as two different checks.

Start with a stable matching key

The reconciliation needs one value that identifies the same logical record on both sides.

Depending on the workflow, that might be an order ID, customer ID, invoice number, product ID, or another unique key.

Compare source records with target records

The basic check is simple:

Source → Match by key → Target → Flag unmatched source records

If a source record has no matching target record, classify it as Missing.

Do not confuse a missing record with a field mismatch

A record can exist in both systems and still contain incorrect data.

Missing means the expected target record cannot be found at all.

Different means the record exists, but one or more selected values do not match.

Make the check repeatable

For recurring integrations, the comparison should not have to be rebuilt every time.

Define the source, target, matching key, and fields once, then run the same verification after future syncs.

Where Verirow fits

Verirow is a B2B data reconciliation SaaS built for independent post-sync verification.

It compares source and target data and separates results into OK, Missing, Different, and Duplicate states so teams can review what actually arrived after an integration run.

For the full product architecture, see the Verirow case study.

Related verification workflows

See how to verify data after a Boomi process run and how to compare source and target data after a sync.